AJAX - the ‘NOT the CR2 upgrade’ thread

The Wiki may be inaccurate, but perhaps equally likely is the people doing the procuring just didn't understand the base networking technology. Which isn't surprising once you've met a few Royal Signals officers. Anyone else discussed this during this thread? You'll be shocked to know I haven't read the previous 350 pages.
I mentioned it back in January (post 5217?). But it's not a new question, it has been raised within the project and certainly within BCIP, but no sensible answers were forthcoming, not while I was involved.
 
Indeed. It was caught at the fit-out stage.

The original spec was HF. Someone with little or no knowledge changed it, and then it was changed back.
ALBN has HF, VHF, UHF and SatCom.

I can imagine there being a move to cut HF “because old fashioned and we’ll always have SatCom”.
 

Sarastro

LE
Kit Reviewer
By the way, for anyone vaguely interested in IT stuff, I just found an absolutely hilarious slide from the MORPHEUS brief: Wayback Machine

See if you can spot the flaw.

This is how industry does it:
full


This is how the MOD could do it:
full


Except...quite a lot of those are the same company, aren't they? And you've just moved them around the box. Perhaps this might be more accurate:
full
 

Sarastro

LE
Kit Reviewer
I mentioned it back in January (post 5217?). But it's not a new question, it has been raised within the project and certainly within BCIP, but no sensible answers were forthcoming, not while I was involved.
As I was looking through the MORPHEUS brief above, I see it's aiming at 0.1 Gb/s (100 Mb/s) for the deployed network backbone (TRINITY) - this is the shiny new BOWMAN replacement for the next however many decades. That is surprisingly low even given the constraints.

20Gb/s internal system for one vehicle on a 0.1Gb/s backbone for the entire network. Those vehicles aren't going to be sharing very much of what they collect in real time, unless they bring a very long USB cable.

Does nobody bring a calculator to these project meetings?
 
By the way, for anyone vaguely interested in IT stuff, I just found an absolutely hilarious slide from the MORPHEUS brief: Wayback Machine

See if you can spot the flaw.

This is how industry does it:
full


This is how the MOD could do it:
full


Except...quite a lot of those are the same company, aren't they? And you've just moved them around the box. Perhaps this might be more accurate:
full
I attended that brief at AHQ, seems like a lifetime ago!

One of the points being made was to try and get away from using proprietary standards, something Evo was supposed to address at the tactical level.

If I recall correctly, the other big takeaway was data capture and the value of that data, data analysis etc. Looking at the likes of Amazon and Google for example, I think even supermarket loyalty schemes were also mentioned.
 
As I was looking through the MORPHEUS brief above, I see it's aiming at 0.1 Gb/s (100 Mb/s) for the deployed network backbone (TRINITY) - this is the shiny new BOWMAN replacement for the next however many decades. That is surprisingly low even given the constraints.

20Gb/s internal system for one vehicle on a 0.1Gb/s backbone for the entire network. Those vehicles aren't going to be sharing very much of what they collect in real time, unless they bring a very long USB cable.

Does nobody bring a calculator to these project meetings?
100Mb/s is significantly more than is available now via the 'High' Capacity Data Radio.
Barring the use of some significant and as yet undiscovered compression techniques or a change in the laws of physics, the data pipe will remain small compared with what can be achieved with fibre or point to point comms. Neither of the latter are ideal for a recce vehicle well in advance of friendly forces.
 

Sarastro

LE
Kit Reviewer
I attended that brief at AHQ, seems like a lifetime ago!

One of the points being made was to try and get away from using proprietary standards, something Evo was supposed to address at the tactical level.

If I recall correctly, the other big takeaway was data capture and the value of that data, data analysis etc. Looking at the likes of Amazon and Google for example, I think even supermarket loyalty schemes were also mentioned.
I agree with the premise, which is simply stuff that their own (Defence) people had internally been telling them (Army Information Directorate / Royal Signals) a decade previously and which was generally rodded off: I was in a job that meant we attended a couple of the expert opinion panels. They are still, however, more than a decade behind the curve.

What I'm less impressed by is:
  • Attention to detail - e.g. the network bandwidth is a pretty major fundamental to everything else they are attempting, if it's that low, they simply won't be able to do a lot of it.
  • Lack of coordination - e.g. not appearing to join the above dots between different projects.
  • Lack of fundamental understanding - e.g. the 'platform connectivity concept' in that deck is almost meaningless, I'd expect a GCSE IT student to do better.
  • Impression of control they don't have - e.g. they clearly have no ability to substantially change the MOD policy of preferring massive suppliers, so the architecture I linked above will be limited at best, and probably functionally impractical.
Overall, the sense that 90% of this is getting maximum buzzwords into the PowerPoint but without any real understanding of what it all means. Alternatively, hiding a what they understand to be a distinctly unambitious set of belated upgrades with maximally soporific staff-speak about how it's new and shiny.

In 2005 this might have been new and shiny. In 2020 it's already outdated.
 
ALBN has HF, VHF, UHF and SatCom.

I can imagine there being a move to cut HF “because old fashioned and we’ll always have SatCom”.
HF is still a viable means to achieve BLOS comms, though it is susceptible to atmospheric conditions, and data throughput is very small.
 

Bubbles_Barker

LE
Book Reviewer
As I was looking through the MORPHEUS brief above, I see it's aiming at 0.1 Gb/s (100 Mb/s) for the deployed network backbone (TRINITY) - this is the shiny new BOWMAN replacement for the next however many decades. That is surprisingly low even given the constraints.

20Gb/s internal system for one vehicle on a 0.1Gb/s backbone for the entire network. Those vehicles aren't going to be sharing very much of what they collect in real time, unless they bring a very long USB cable.

Does nobody bring a calculator to these project meetings?
I was at an Industry day at Lyneham a few years ago about this but am the first to say it's not my bag. What I do know though is that TRINITY is not the BOWMAN replacement as you seem to infer. MORPHEUS replaces/evolves BOWMAN and TRINITY replaces FALCON, both TRINITY and MORPHEUS are sub-programmes of LE TacCIS.

Perhaps a much maligned RSigs type could explain further.

Then again...
 
I was at an Industry day at Lyneham a few years ago about this but am the first to say it's not my bag. What I do know though is that TRINITY is not the BOWMAN replacement as you seem to infer. MORPHEUS replaces/evolves BOWMAN and TRINITY replaces FALCON, both TRINITY and MORPHEUS are sub-programmes of LE TacCIS.

Perhaps a much maligned RSigs type could explain further.

Then again...
Morpheus being the Greek god of sleep and dreams. Very appropriate!
 

Bubbles_Barker

LE
Book Reviewer

Sarastro

LE
Kit Reviewer
100Mb/s is significantly more than is available now via the 'High' Capacity Data Radio.
Barring the use of some significant and as yet undiscovered compression techniques or a change in the laws of physics, the data pipe will remain small compared with what can be achieved with fibre or point to point comms. Neither of the latter are ideal for a recce vehicle well in advance of friendly forces.
Yep, I recognise there are genuine technical and practical challenges to getting a high data rate. I would be surprised if they achieved it and don't expect it.

Where I differ is that my "so what" to that is: they need to develop different, more efficient formats of data transmission. Hoping that industry will find a new way to compress FMV is a fool's game, as anyone who has worked on the difference between urban (fibre) and rural (wireless) broadband will know. The tech sector is blinkered and assumes everyone has 5G or fibre connections, so develops all their software and formats accordingly, which is why video formats continue to occupy ever larger file sizes and more bandwidth.

I did a project a while back to demonstrate that you could run a full multi-company HUD with situational location for each individual and a command net, using just a single TCP packet (64k) per node per second. (For those who don't understand, the smallest, fastest unit within the standard TCP/IP networking protocol that this all needs to be compatible with). In other words, you can get all of the information from a radio and GoPro, but at a fraction of the bandwidth (therefore a fraction of the weight, a fraction of the signal profile, many times more reliable, etc). The point was that if you could do this, then the bits where you really needed an FMV stream would actually have sufficient capacity to work.

I couldn't get anyone to understand that this might be a requirement when the default answer was "we want to stream FMV between headcams". The understanding that a) they couldn't, and b) the various advantages of efficiency, were all totally in hock to the "but I want my iPad" approach. There seems to be no appreciation that the universal experience of hating their comms because they don't work is directly linked to overloading them with unrealistic expectations.
 

Sarastro

LE
Kit Reviewer
I was at an Industry day at Lyneham a few years ago about this but am the first to say it's not my bag. What I do know though is that TRINITY is not the BOWMAN replacement as you seem to infer. MORPHEUS replaces/evolves BOWMAN and TRINITY replaces FALCON, both TRINITY and MORPHEUS are sub-programmes of LE TacCIS.

Perhaps a much maligned RSigs type could explain further.

Then again...
Hmm, not quite.

TRINITY is the proposed deployable bearer network, which replaces FALCON (the present bearer network which is primarily based on static radio nodes to which individuals and vehicles join, the nodes linked by high speed direct microwave, to central gateways connected to the rest of the world via satcom). The home-base stuff uses the normal bearer network (BT infrastructure) just like everyone else, just often with separate dedicated lines. There are some other specialised bearer networks for secure stuff. All three of these are connected by various gateways.

BOWMAN and MORPHEUS work over FALCON / TRINITY to provide all the other IT elements: computer terminals, handhelds, software, etc.

Or to use the US Senate's superlative explanation: TRINITY is the series of tubes. MORPHEUS is all the other stuff.

PS I don't think my post confused the two, but I did assume understanding that you use devices over a network, so talking about MORPHEUS inherently involves the capability of TRINITY.
 
If you think AJAX has screwed the pooch, wait til you see LeTacCIS…
 
Hmm, not quite.

TRINITY is the proposed deployable bearer network, which replaces FALCON (the present bearer network which is primarily based on static radio nodes to which individuals and vehicles join, the nodes linked by high speed direct microwave, to central gateways connected to the rest of the world via satcom). The home-base stuff uses the normal bearer network (BT infrastructure) just like everyone else, just often with separate dedicated lines. There are some other specialised bearer networks for secure stuff. All three of these are connected by various gateways.

BOWMAN and MORPHEUS work over FALCON / TRINITY to provide all the other IT elements: computer terminals, handhelds, software, etc.

Or to use the US Senate's superlative explanation: TRINITY is the series of tubes. MORPHEUS is all the other stuff.

PS I don't think my post confused the two, but I did assume understanding that you use devices over a network, so talking about MORPHEUS inherently involves the capability of TRINITY.
Morpheus doesn't work over anything, it doesn't exist, and won't exist anytime soon.
Bowman or more correctly BCIP, is an enclosed system, IT, applications etc are supplied as part of the CIP piece.
Bowman 'puddles' can be linked via gateways using Falcon.
 

Sarastro

LE
Kit Reviewer
Bullsh1t refined to an art form


I like how their initial graphic features a progressively more complicated buffering icon that...keeps on buffering. Truth in advertising.

Goes downhill from there.
 
I like how their initial graphic features a progressively more complicated buffering icon that...keeps on buffering. Truth in advertising.

Goes downhill from there.
Also a red headed female recent resident of Merville Bks?
 

Latest Threads

Top