HF in the US Navy Update HFIA Conference 3 February 2005 Page 1
Briefing Outline Present Battle Force Email 66 Status Service Level & Program Infrastructure Upgrades Incremental I.T. updates & Adaptive controls Evolving the HF Data System (HFDS) IP Over HF Multicast Networking Summary Page 2
US Navy PEO Objectives Focus on capabilities vice products Align to DoN vision of a networked Force Streamline Fleet, OPNAV and funding processes Become C4I provider for new platforms Currently do fleet modernization almost exclusively Optimize platform solutions for interoperability and sustainability Improve commonality Align to PEO C4I Roadmap Implement C4I portion of FORCEnet Page 3
HF Data System in the US Navy s SPAWAR Organization PEO C4I &S AMR/JTRS ~ Command & Control Communications Networks and Enterprise Services Link 16 / Link 22 INMARSAT Transformational Communications Portable Radios CENTRIXS HF Data System (BFEM66) Automated Digital Network Systems (ADNS) Page 4
Process Management within the BFEM66 Program BFEM66 Program Manager leads a diverse team of experts to deliver Interoperability to the Fleet SPAWAR defines the objectives and leads the team by integrating schedules and cost merit in relation to the Fleet requirements SPAWAR s Integrated Product Team assembles the detailed ramifications and reports to the integrated schedules The team manages risks together to assure success and timeliness of: Programmatic at PM / Sponsor Cost Schedule Performance Compliance CAPT Sherman Metcalf (PMW 179) (619) 524-7530 FY 03 CAPT Dave Markham (N61) (703) 601-1201 CAPT Sherman Metcalf PMW 179 FY 04 CAPT William Hardy OPNAV N61 See back-up 1 for full report Logistics Overall Page 5
Performance: Service to the Fleet Down Time Reports 100 Average Data Rates Pre-Set Modem Speeds for Shipboard Systems 80 East If Modem SNR = <12 SNR* 12-18 SNR* 19-24 SNR* >25 SNR* 60 West With Function = MIL110B MIL110B MIL110B-F MIL110B-F 40 20 0 2000 2002 2004 Interoperability Level: Int'l Partner NATO Coalition FMS/Direct Verified Belg 3 FMS Yes Can 16 Direct Yes Fra 77 Direct Ger 24 FMS Yes Ital 58 Direct Jap 22 FMS Yes Neth 6 Direct Yes via NATO Oman 15 Direct Yes via UK Spn 1 Direct UK 60 Direct Yes US 182 At Datarate = 4.8 Kbps 9.6Kbps 12.8Kbps 19.2Kbps 253K Word document 12.2 minutes 10.9 Minutes 7.0 Minutes 3.0 minutes 259K PDF File 15.2 minutes 13.7 minutes 10.00 minutes 71 7.1 minutes Operational and administrative traffic to include emails and attachments * SNR = Signal to Noise Rating on modem front panel Information Characteristics Requirements Sending Node Afloat platforms, shore sites both U.S. and Allied/ Coalition. Joint aircraft/land based vehicles as appropriate. Afloat platforms, shore sites both U.S. and Allied/ Coalition. Joint aircraft/land based vehicles as appropriate Receiving Node Format Data packets, formatted in accordance with STANAG 5066 in a modulated waveform complying with STANAG 4539/MIL- STD 188-110B Time lines Variable. In two station net, 100KB message in less than 5 mins. Page 6
Technical: Baseline & Upgrade Planning Increment 0 (FY 00 FY 01) Battle Force E-Mail66 (BFEM66) distributes secure tactical information (point to point) with partner nations premised upon conforming STANAG 5066 products (various suppliers) to assure effective situational awareness and threat management using e-mail Increment I (FY 02-FY 03) BFEM66 programmatically established with ILS infrastructure, multi-national security settings addressed and server based installation. E-mail delivery is adaptable to user preferences and flexible to shipboard IT and HF Radio environments. IOC status assigned Increment II (FY 04 FY 06) BFEM66 upgraded to increase modem datarates and contiguous message delivery in congested airwave (collision avoidance) theatre of operations IP capability tested to validate versatility with Joint & Allied environments IP capability installed to create a IRC chat environment. JITC Cert established Increment II (FY 07 FY 08) BFEM66 grows into HF Data System (ORD s mature design state) by expanding IP capability to include web replication and adaptive modem control for lightsout operation HF-WAN (Token Ring) networking between partner nations with performance in accordance with Cop & GIG objectives Page 7
Sustaining BFEM66 Capability Increment II upgrades are in process Modem upgrade to 19.2Kbps is performing well Fleet s BFEM66 have sub-standard computing platform componentry Working to improve through repairs and ISEA replacements Upgrade for MS Windows 2000 and HF Messenger V.3.2 Demand from the users for IP Based services would significantly ifi improve speed, usefulness and inter Battle Group networking Low cost for chat environment, database replication services and multi-national network connectivity Page 8
HF Design Configuration Migration by Fleet Ship Count Migration within BFEM66 addresses aged technology, computing platform refresh and IP upgrades via the 100% 90% HF-IP Capability 80% (HF-IPC) 70% 60% Fleet s capability for 50% 40% Allied Interoperability 30% over HF increases 20% 10% to 195 Ships 0% by FY 05 185 195 Total Allied Inter-Operable Ships= # Ships with HF-IP Cap. 0 0 0 5 24 54 # Ships w/ BFEM66 @ 19.2 BFEM Baseline FY'04 FY'05 FY'06 FY'07 FY'08 24 43 78 92 96 87 # Ships w/ BFEM66 @ 9.6 161 142 113 98 75 54 BFEM Page 9
Technical: Roadmap for BFEM66 BFEM Spiral Upgrades From Baseline to JTRS Inclusion BFEM Upgrade for HF-IPC (realizes ORD nomenclature-hfds) BFEM 66 PC Retrofits BFEM 66 RF Collision Avoidance BFEM 66 19.2 Modem Upgrade HFDS (BFEM) Insertion on Navy Aircraft BFEM 66 Baseline Legend HFDS (BFEM) Multi-Cast Process Increment I Increment II Technologies HFDS Token Passing Network HFDS Insertion at Navy Shore Sites HFDS Upgrade for SNR & SNR Modem HFDS Upgrade for JTRS Modem Page 10
Summary HFDS used within Military IT architectures is addressing the U.S. Navy s needs for data speed, hands-free utility and HF networking HF Data (IP Based) use for allied/coalition naval interoperability is a recognized need Incremental upgrades address retention of IER conformance, HF-IP Capability is needed to increase the effective use of BFEM in Fleet applications Goals within the Navy s HF programs are compatible with JTRS implementation Page 11
Back up Slides Page 12
Program Goals Independent of Funding we d like to: Complete fielding of 195 systems towards meeting inventory objectives of 396 ships Add HFDS utility into airborne platforms pending Joint Staff authorizations for HFDS Program Automated Fault Isolation, OJT & ILS enhancements Automated (hands-off) modem control operation Combining HFDS with non-hf Allied Interoperability systems to set the stage for JTRS interoperability in out-years HF Data System (BFEM66) utility in an Joint/Allied Interoperability environment will drive the degree of authorized improvements in the U.S. Navy Page 13