PMW 160 - PowerPoint PPT Presentation

1 / 28
About This Presentation
Title:

PMW 160

Description:

'We Are the Navy Acquisition and Technical Authority for Networks, Information ... Seamless cross-domain access and data exchange. ... The NAVY's Future WAN will be: ... – PowerPoint PPT presentation

Number of Views:1456
Avg rating:3.0/5.0
Slides: 29
Provided by: MHi59
Category:
Tags: pmw | exchange | navy

less

Transcript and Presenter's Notes

Title: PMW 160


1
PMW 160 Networks, IA Enterprise
Services Overview for NDIA
Mr. Rob Wolborsky Program Manager PMW
160 Networks, IA, Enterprise Services (619)
524-7909 robert.wolborsky_at_navy.mil
10 August 2005
2
PEO C4I Space Organization
3
PMW 160
PMW 161 Information Assurance
PMW 165 Afloat Networks
PMW 166 Naval Messaging
PMW 179 ADNS
PMW 157 JCDX/Radiant Mercury
4
PMW 160Program/Project Alignment
PM Mr. Rob Wolborsky
DPM CAPT (sel) Bob Parker
Afloat Networks PMW 160-1
CRYPTO Key Mgt. PMW 160-2
Enterprise Services PMW 160-3
Network Security PMW 160-4
KG-3X KG-40AR DMS Infosec CAW Crypto
Products EKMS PKI Biometrics Secure Voice Crypto
Mod
  • DMS
  • Tactical Messaging
  • NGDS
  • NMCP
  • COMPOSE
  • TDAMS
  • Network Management
  • NREMS
  • FSI

JCDX CND CDS DII Guards IA Readiness
Services NMCI IA Radiant Mercury ONE NET 1A
ISNS ADNS SCI Networks SubLAN CENTRIXS-M VIXS Work
stations (PCs)
Aligned to Develop and Field Capabilities!
5
PMW 160Mission Vision
  • Mission Statement
  • We Are the Navy Acquisition and Technical
    Authority for Networks, Information Assurance,
    and Enterprise Services. We Provide Affordable,
    Interoperable, and Secure Net-Centric Enterprise
    Capabilities to the Navy, Joint, and Coalition
    Warfighters.
  • Vision Statement
  • We Will Deliver Information Superiority to the
    Warfighter Through Integrated Net-Centric
    Enterprise and Seamless Information Assurance
    Services.

6
PEO C4I SpaceOverarching Afloat Framework
PMW160 Is Responsible For A Significant Portion
of the Afloat C4I Architecture
7
PMW 160 FY 06 Outlook
  • Fleet/Customer C4I Needs/Requirements
  • Efficiently and Effectively Execute PMW 160
    Programs
  • Transformational Capabilities to the Warfighter
  • Network Consolidation
  • FSI

8
C4I Focus Areas
Fleet FY-05 Top Ten
Net Connected Improved decision making
  • Improved High Data Rate Throughput
  • Improved Standards Throughout C4I Community
  • Coalition Communications
  • Antenna Capability and Reliability
  • Data Link Enhancements
  • Computer Network Defense
  • Multi-Level Security/Cross-Domain Solutions
  • Real-Time Collaboration/Next Gen KM
  • Network Life-Cycle Management
  • ISRT Applications
  • Web-based services
  • Improved network reliability and performance
  • Increased bandwidth
  • Improved coalition operations and data sharing
  • Tailorable situational awareness tools
  • Standardized data exchange between domains
  • Defense in depth

Level 1 - FY07
Fleet Priorities PEO C4I Priorities
FY14
FY10
Today
FY07
9
Fleet C4I NeedsFY-06 Numbered Fleet N6 Top Ten
Requirements
PMW 160 PMW 170 All PMW 160 PMW 160 PMW 150 PMW
150 PMW 160 PMW 150 PMW 160
10
An Example of PMW 160 Supporting the Fleet
IMPROVED HIGH DATA RATE THROUGHPUT
PMW 160 Addresses this area with ADNS
11
ADNS Today and Tomorrow
  • Today's NAVY WAN
  • Single Path Access, No Restoral, Best Effort,
    Limited BW, No Guarantees
  • No Network Insight, Little Visibility, Limited
    Decision Making Tools
  • The NAVYs Future WAN will be
  • Bandwidth Efficient, Possess Multiple Survivable
    Paths, Contain Quality of Service Guarantees and
    Provide Network Visibility to Remote/Local Users.
  • PMW 160 Challenge is to Provide the Fleet a Means
    to Use Bandwidth More Efficiently.

ADNS is the NAVYs POR for WAN Networking and The
Mechanism to Accomplish this Vision
12
ADNS Increments
Increment I
Pre Incr I
Increment III
Increment II
1988-1997
1997-2005
2008
2005-2008
IP over RF
Increment I Capabilities plus
Increment II Capabilities plus
Transition from Proteon to Cisco Routers
Traffic Distribution Over Multiple SATCOM Paths
Black Core(CT)Routing IPv4/IPv6 Converged IP
Integrated Transport of Multiple Security Over
Single SATCOM Path
Shipboard IP Network
Fully Meshed Joint Network
Dynamic Fail-over Between Links
Flexible Bandwidth Guarantee
Router Architecture
IP
USMC Amphibious Network Support
Application Prioritization
25/50 Mbps Throughput
TC, HAIPE, and JTRS Interface
EOC II
Network Management Monitor
Application Level Monitoring
AN/USQ-144B(V)2/4 AN/USQ-144C(V)2/3/4 AN/USQ-144D
(V)1/2/3/4 AN/USQ-144E(V)2/4 AN/USQ-144F(V)2 AN/US
Q-144G(V)2/4 AN/USQ-144(V)5
AN/USQ-144D(V)1 AN/USQ-144H(V)2/4 AN/USQ-144J(V)2/
4
TBD
13
Increment I ADNS Provides
High Speed Internet Provides T1 to a Single
Residence
  • Limited Bandwidth
  • 512 or 768 IP Kbps to a US Navy Aircraft Carrier
  • 128 IP Kbps to a DDG/CG
  • 32 IP Kbps (Shared) to an SSN
  • Afloat Units Maintain Course, Speed to Optimize
    IP Connectivity (Single RF Path Dependency)
  • Ships Limit Capability in a Trade off to Maximize
    IP Capability Legacy IP Implementation
  • Network Performance Issues Isolated via Manual
    Voice Circuits Subject to Operator Intervention

INCREMENT I Solved 1998 Issues, Now Obsolete
14
Increment I Typical POTS Use
Operation Unified Assistance Peak line use 25
out of 47 lines Peak b/w use 408 out of 698
Kbps Average b/w use 12 of available b/w
47 POTS lines 698 Kbps allocation
Wasted Bandwidth
Voice is not the Only Culprit Serial Data and
VTC Circuits Consume Major Portions of Static BW
15
Increment II BW GuaranteesJCA Unclass via CWSP
(1024 kbps)Secret via DSCS (512 kbps), SI via
EHF (384 kbps)
Data Throughput Rate
Higher Priority Imagery Traffic starts and NIPR
Declines
Traffic Classes Provide Reusable Bandwidth P
erformance Guarantee
Higher Priority Traffic Ends and NIPR Expands
Timescale
16
ADNS Inc III Capabilities
  • Future Increment III Systems will support
  • 25/50 Mbps Tactical Throughput Capability
  • A Fully Meshed Network
  • Support for Real Time Mission Critical
    Applications requiring increased factors of
    Network Reliability and Availability
  • Network Capable of Supporting both IPv4 and IPv6
    Applications
  • Support for Dynamic QOS and Dynamic Bandwidth
    Allocation
  • Support for Mobile Ad Hoc networking
  • Support for Multi-Cast Applications
  • Align with the Navy Tactical WAN with the DoD GIG
    across a Black Core Backbone

17
Summary
  • ADNS is the Tactical Navy Gateway to the GIG
  • ADNS is delivering a significant amount of
    capability to the
  • Warfighter

18
Another Interesting Question?How do we address
the Fleets need for Speed to Capability
C2F
C3F
C5F
  • Antenna Reliability
  • Coalition Communications
  • Data Throughput
  • COP
  • Real-Time Collaboration
  • CND
  • Network Life-Cycle Mgmt.
  • Standards
  • Next Generation KM
  • Streamlined Fielding Process
  • Data Throughput
  • Antenna Reliability
  • Coalition Communications
  • COP
  • Real-Time Collaboration
  • CND
  • ISRT
  • Standards
  • Next Generation KM
  • Multi-Level Thin Client
  • Coalition Communications
  • Antenna Reliability
  • Standards
  • Next Generation KM
  • CND
  • Real-Time Collaboration
  • Data Throughput
  • Network Life-Cycle Mgmt.
  • COP
  • Streamlined Fielding Process

C6F
C7F
  • Coalition Communications
  • Standards
  • Antenna Reliability
  • Data Throughput
  • CND
  • Data Link Enhancements
  • Multi-Level Thin Client/CDS
  • Real-Time Collaboration
  • Network Life-Cycle Mgmt.
  • Streamlined Fielding Process
  • Antenna Reliability
  • Coalition Communications
  • Data Throughput
  • COP
  • Real-Time Collaboration
  • CND
  • Network Life-Cycle Mgmt.
  • Standards
  • Next Generation KM
  • Streamlined Fielding Process

19
Speed to Capability
  • Numerous examples of Emergent Fleet needs not
    being met by time frame of the budgetary process
    (PPBE/PPBS)
  • Cfn
  • CENTRIXS
  • CAS
  • Etc.

How Can We Do A Better Job???
20
PMW 160 FY 06 Outlook
  • Fleet/Customer C4I Needs/Requirements
  • Efficiently and Effectively Execute PMW 160
    Programs
  • Transformational Capabilities to the Warfighter
  • Network Consolidation
  • FSI

21
Transformational ExampleNetwork Consolidation
  • Today
  • Up to 74 separate networks on a Carrier today
  • Multiple classes of networks varying levels of
    convergence and commonality, and interoperability
  • Physically separate security enclaves (MLS
    Solutions not widespread)
  • Legacy internal comms / separate voice networks
    (POTS/PBX, Hydra)

CAPT Dave Wegman PMW 750
22
Hypothesis
  • Proliferation of Networks on Surface Ships
    Exists.
  • Initial surveys show upwards of 70 different
    LANs
  • Proliferation is Technically Unnecessary
  • Industry has shown that consolidation and
    simplification of the network brings both
    efficiencies, cost savings, security, and
    increased net centricity
  • Proliferation causes Increased Resource Demands
  • At a minimum, it becomes a CM nightmare,
    reality is duplicate efforts and added costs
  • FORCEnet needs a uniform network environment
  • This is not achievable if the networks arent
    connected to one another, the bridging
    consistent, and QoS defined
  • - How can we ever get to a SOA?

Minimize network E2E TCO maximize
interoperability for Fn, BSN, GIG, FSI
23
Industry Trends
  • Convergence
  • Leverages existing Investments rather than Rip
    and Replace.
  • Simplification to reduce complexity, risk, and
    increased security
  • Application Oriented Networking a Paradigm Shift

Commercial Topologies support multiple functions
and networks, logically separated on a single
physical network
24
CHALLENGES
  • STRATEGY
  • Must have an overarching PMW 160 Approach/Vision
  • Refine is the core objective(s) - then
    architecture can follow!
  • CONOPS
  • Given a formal overall 160 strategy embody it
    in a process
  • IT/network governance must be spelled out
    alliances formed
  • Coc/RR/ROE/etc also need to be clearly defined
    somewhere
  • ISSUES FRAMED
  • Common list of critical issues, concerns and
    limitations
  • E2E routing/QoS, black core, IPv6, governance,
    HAIPE, ETC
  • COMMITMENT
  • Make coordinating/resourcing NC a priority a
    win-win overall

25
Current Effects
  • Migration of Voice, Video and Data to IP and into
    the network
  • Includes internal Communications and portables
  • Working with PMW 760 750 to Support Network
    Consolidation on SCN
  • Support and replace SWAN on LPD 17
  • Support DD(x) and help define a mitgration plan
    for its architecture
  • CV 21
  • Also working with DGCS-N and plan to collaborate
    with PEO IWS
  • Actively engaged with NAVSEA 062 (CAPT Hill)

26
PMW 160 FY 06 Outlook
  • Fleet/Customer C4I Needs/Requirements
  • Efficiently and Effectively Execute PMW 160
    Programs
  • Transformational Capabilities to the Warfighter
  • Network Consolidation
  • FSI

27
FSI
  • Goal FORCEnet Services Infrastructure (FSI)
    shall provide the next generation information
    systems, providing robust, non-proprietary
    mechanisms to 1) dynamically add content ,
    sensors, visualization clients and applications
    to the afloat C2 network, and 2) reduce
    redundancy by increasing information sharing
    by providing a single information/C2 system
    backbone for Navy nodes, compliant with DISA
    Core Services.
  • Motive Increase speed of command and reduce
    manning by facilitating an architecture that
    reduces the barrier of entry for new
    applications and sensors to better display,
    analyze and fuse C2 data to the warfighter.

Shortening the Kill Chain
28
PMW 160 Summary
  • Our Mission and Vision connect with the Fleets
    requirements
  • ADNS is Directly addressing a Fleet Priority
  • Network Consolidation network brings both
    efficiencies, cost savings, security, and
    increased net centricity
  • FSI delivers the SOA environment to enable
    FORCEnet

IM COUNTING ON INDUSTRY TO PROVIDE TECHNOLOGIES
TO MEET THE WARFIGHTERS REQUIREMENTS
Write a Comment
User Comments (0)
About PowerShow.com