Royal Navy HF Data Capability:
Royal Navy HF Data Capability Overview of Royal Navy’s current HF data programmes
Interoperability Issues
HFDS (BFEM-66):
HFDS (BFEM-66) UOR procured to provide Allied interoperability
US BFEM-66
Secure point-to-point email between coalition ships
Based on STANAG 5066 CFTP client
Operates at 4k8 bps (MIL-188-110B)
400NM range using 100W
Military Task Equipment
32 Marconi MDH sets
Fitted as MTE to ships on deployment
NATO & East of Suez (Gulf)
SR(S)7397 – Outfit 4KMA:
SR(S)7397 – Outfit 4KMA NATO BRASS Phase II
Ship/Submarine HF Transmit Upgrade
ALE – Mil Std 188 141B
ARQ – STANAG 5066
ACP127 and ACP123 clients
Email client (CFTP/HMTP)
Thales Communications (UK) Ltd
First ship fit commissioned Jan 05
Some 30 ships now fitted
Last fit (~ 90) scheduled for 2008
SR(D)2024 - DHFCS:
SR(D)2024 - DHFCS Defence HF Communications Service
PPP contract let July 2003 to VT Communications
ALE and ARQ ship-shore services IOC Aug 2005
Working up procedures for ship-shore-ship ‘Rear Link’ services
Equipment based on USAF SCOPE Command system
Rockwell Collins prime sub-contractor
Interoperability Issues:
Interoperability Issues Rockwell-Collins vs Thales vs Marconi
DHFCS not fully interoperable with Outfit 4KMA
Data Rate Change Mechanism
Rockwell Collins providing fix
ALM
No solution
Outfit 4KMA not fully interoperable with BFEM66
90EB configuration issue
Solution available from Thales
Funding for fix not yet identified
Interoperability seems likely to be lost
Questions?:
Questions? First Officer John Perkins RFA
CINCFLEET N6 Strategic Radio SO2
john.perkins253@mod.uk
+ 44 2392 625628
Capability Gaps:
Capability Gaps ALE not fitted to MilSatCom ships
Unable to use ALE ship-to-ship
HF Email - limited versatility
Point to point. No ‘chat’. Not IP capable.
No Email link into shore infrastructure
Emerging Gap with US?