US Navy Brieifng to HFIA

1
HF in the US Navy Update
2
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

3
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

4
HF Data System in the US Navys SPAWAR
Organization
PEO C4I S
AMR/JTRS

Networks and Enterprise Services
Command Control
Communications
INMARSAT
Link 16 / Link 22
CENTRIXS
Transformational Communications
HF Data System (BFEM66)
Portable Radios
Automated Digital Network Systems (ADNS)
5
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
• SPAWARs Integrated Product Team assembles the
  detailed ramifications and reports to the
  integrated schedules
• The team manages risks together to assure success
  and timeliness of

See back-up 1 for full report
6
Performance Service to the Fleet
Average Data Rates
Down Time Reports
Pre-Set Modem Speeds for Shipboard Systems
lt12 SNR
12-18 SNR
19-24 SNR
gt25 SNR
If Modem SNR
MIL110B
MIL110B
MIL110B-F
MIL110B-F
With Function
4.8 Kbps
9.6Kbps
12.8Kbps
19.2Kbps
At Datarate
253K Word
12.2 minutes
10.9 Minutes
7.0 Minutes
3.0 minutes
document
259K PDF File
15.2 minutes
13.7 minutes
10.0 minutes
7.1 minutes
SNR Signal to Noise Rating on modem front
panel
Requirements
Interoperability Level
7
Technical Baseline Upgrade Planning

• Increment 0 (FY00 FY01)
• 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 (FY02-FY03)
• 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 (FY04 FY06)
• 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 (FY07 FY08)
• BFEM66 grows into HF Data System (ORDs mature
  design state) by expanding IP capability to
  include web replication and adaptive modem
  control for lights-out operation
• HF-WAN (Token Ring) networking between partner
  nations with performance in accordance with Cop
  GIG objectives

8
Sustaining BFEM66 Capability

• Increment II upgrades are in process
• Modem upgrade to 19.2Kbps is performing well
• Fleets 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 improve speed, usefulness and inter
  Battle Group networking
• Low cost for chat environment, database
  replication services and multi-national network
  connectivity

9
HF Design Configuration Migration by Fleet Ship
Count

• Migration within BFEM66 addresses aged
  technology, computing platform refresh and IP
  upgrades via the
• HF-IP Capability
• (HF-IPC)
• Fleets capability for
• Allied Interoperability
• over HF increases
• to 195 Ships
• by FY05

185
185
195
195
195
195
Total Allied Inter-Operable Ships
10
Technical Roadmap for BFEM66

• BFEM Spiral Upgrades From Baseline to JTRS
  Inclusion

11
Summary

• HFDS used within Military IT architectures is
  addressing the U.S. Navys 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 Navys HF programs are
  compatible with JTRS implementation

12

• Back up Slides

13
Program Goals
Independent of Funding wed 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