Upload
ngoquynh
View
246
Download
5
Embed Size (px)
Citation preview
18 October, 2007Steve Bullard
Deputy Program ManagerInternational C4I Integration
(619) 524-7322
Program Executive OfficeCommand, Control, Communications, Computers and Intelligence (PEO C4I)
US Navy C4I Roadmap
Statement A: Approved for public release; distribution is unlimited (17SEPTEMBER 2007)SR-2007-0394
2
• Organization
• C4I Roadmap
• GCCS-M
• Next Steps
• Questions
International C4I Integration Topics
3
Assistant Secretary of the Navy Research Development & Acquisition
ASSISTANT SECY OF NAVY (RDA) Honorable Delores M. Etter
(703) 695 -6315ASN RDA
Deputy Assistant Secretaries
of the Navy (DASNs)
Deputy Assistant Secretaries
of the Navy (DASNs)
Program Executive
Officers(PEOs)
Program Executive
Officers(PEOs)
SYSCOM CommandersSYSCOM
Commanders
NAVAIRNAVAIR
NAVSEANAVSEA
SPAWARSPAWAR
NAVSUPNAVSUP
NAVFACNAVFAC
IntegratedWarfare Systems
IntegratedWarfare Systems
Littoral & Mine Warfare
Littoral & Mine Warfare
InternationalInternational
LogisticsLogistics
Research, Dev, Test & EvaluationResearch, Dev,
Test & Evaluation
AirAir
ShipsShips
Management & Budget
Management & Budget
Chief SystemsEngineer
Chief SystemsEngineer
C4I & SpaceC4I & Space
MARCORSYSCOM
MARCORSYSCOM
Assistant GeneralCounsel
Assistant GeneralCounsel
AcquisitionManagementAcquisition
Management
IntegratedWarfare Systems
IntegratedWarfare Systems
ShipsShips
SubmarinesSubmarines
AircraftCarriersAircraftCarriers
Air ASW Assault& Special MissionAir ASW Assault
& Special Mission
Joint StrikeFighter
Joint StrikeFighter
Strategic SystemsProgram
Strategic SystemsProgram
Enterprise Information
Systems
Enterprise Information
Systems
C4IC4I
Space SystemsSpace Systems
Tactical AirTactical AirLittoral & MineWarfare
Littoral & MineWarfare
Strike Weapons &Unmanned
Aviation
Strike Weapons &Unmanned
AviationONRONR
4
PEOJOINT STRIKE FIGHTER
(JSF)
BGen C. R. Davis (USAF) (703) 602-7640
PEOJOINT STRIKE FIGHTER
(JSF)
NAVAIR NAVAIR
SPAWAR
PEOTACTICAL AIR
PROGRAMS (PEOT)
RADM Dave Venlet(301) 757-7160(301) 757-7163
PEOTACTICAL AIR
PROGRAMS (PEOT)
PEOAIR ASW, ASSAULT AND
SPECIAL MISSION PROGRAMS (PEOA)
Mr. Tom Laux(301) 757-5376(301) 757-5372
PEOAIR ASW, ASSAULT AND
SPECIAL MISSION PROGRAMS (PEOA)
PEOSTRIKE WEAPONS AND UNMANNED AVIATION
(PEOW)
RADM Timothy Heely(301) 757-6332
PEOSTRIKE WEAPONS AND UNMANNED AVIATION
(PEOW)
PEOSPACE SYSTEMS
RDML Victor C. See, Jr(202) 279-5000
PEOSPACE SYSTEMS
PEOLITTORAL AND MINE
WARFARE
Mr. Jim Thomsen (Acting) (202) 781-3900
PEOLITTORAL AND MINE
WARFARE
PEOSHIPS
RADM Charles Hamilton(202) 781-2941
PEOSHIPS
PEOSUBMARINES
RDML William Hilarides(202) 781-4000
PEOSUBMARINES
PEOAIRCRAFT CARRIERS
RADM David Architzel(202) 781-2949
PEOAIRCRAFT CARRIERS
PEOENTERPRISE
INFORMATION SYSTEMS
RDML Tim Flynn(703) 699-3201
PEOENTERPRISE
INFORMATION SYSTEMS
PEO C4I
Mr. Chris Miller (Acting)(619) 524-7358
PEO C4I
DIRECT REPORTINGPROGRAM MANAGER STATEGIC SYSTEMS
PROGRAM (SSP)RADM Stephen Johnson
(703) 601-9000(703) 601-9001
DIRECT REPORTINGPROGRAM MANAGER STATEGIC SYSTEMS
PROGRAM (SSP)
JOINT
NAVSEA NAVSEA NAVSEA NAVSEA
PEOINTEGRATED WARFARE
SYSTEMS
RDML Michael Frick(202) 781-2964
PEOINTEGRATED WARFARE
SYSTEMS
SSP
ASSISTANT SECY OF NAVY (RDA) Honorable Delores M. Etter
(703) 695-6315
PEO C4I Interactions
ASN RDA
Platform
Networks, IA &Ent. Services
PMW 160
Networks, IA &Ent. Services
PMW 160
Ship IntegrationPMW 760
Ship IntegrationPMW 760
Carrier and Air IntegrationPMW 750
Carrier and Air IntegrationPMW 750
ISR and IOPMW 180
ISR and IOPMW 180
DCGS-NPMW 120DCGS-NPMW 120
DJC2PMW 140
DJC2PMW 140
International C4I IntegrationPMW 740
Mr. Jim Churchill
International C4I IntegrationPMW 740
Mr. Jim Churchill
CommunicationsPMW 170
CommunicationsPMW 170
Submarine IntegrationPMW 770
Submarine IntegrationPMW 770
Shore and Expeditionary IntegrationPMW 790
Shore and Expeditionary IntegrationPMW 790
ProductProduct
PEO C4I Organization
PEO C4IMr. Chris Miller
PEO C4IMr. Chris Miller
Command& ControlPMW 150
Command& ControlPMW 150
6
International C4I Integration Description of C4I Systems
• C4I Systems• Command & Control – Systems utilizing sensor and
data input to provide a near “real-time” Common Operational Picture.
• Communications – Wireless communications (data transfer & voice) spanning all frequencies.
• Computers – Computer systems used in Command & Control and Communication systems
• Intelligence – Data gathering systems providing information to Command & Control through various Communication systems.
7
International C4I Integration What is Interoperability
• Interoperability can be defined in a number of ways• Operational Level• Technology Level
• At the Operational Level, Interoperability is about• National Policy• Doctrine• Releasability• Tactics, Techniques and Procedures• Service Culture• Technology
• At the Technology Level, Interoperability is about Common or Compatible systems• Standards• Hardware• Software
• It is not sufficient to have the same or compatible technologies to be interoperable. National Policies, Tactics, Techniques and Procedures and Service Culture must also be appropriately aligned.
8
Defense Security Cooperation Agency Three-Phase Approach
• Phase 1• C4ISR planning that explores the intended
Concept of Operations (CONOPS) and develops an overarching C4ISR architecture
• Phase 2• A Procurement Plan that is a “total package” of
options and recommendations with associated costs, schedules, and risk impacts to the purchaser.
• Phase 3• A procurement strategy through FMS, direct
commercial sales (DCS), and/or cooperative programs.
9
International C4I Integration Challenges
FMS vs. DCS
FMS DCS
Contracting Method
Government to government contract using DoD regulations and competitive processes; DoD assumes contract negotiation and management responsibility
U.S. contractor and foreign government contract; customer assumes contract negotiation and management responsibility
Governance Arms Export Control Act and related legislation
Arms Export Control Act and related legislation
Military Involvement
Direct interaction with DoD civilian and military personnel
None
Lead Times Potentially longer setup time for case development
Determined by Foreign Gov’t to Contractor Timeline
Follow-On Support
Depends on case structure Depends on contract structure
Interoperability Increased interoperability through standardization with U.S. Forces
Deviations from DoD military standard configurations may limit interoperability
PEO C4I Products Delivered FY07 Snapshot
PEOEIS
PEOEIS
Expeditionary Unit (NECE)
- DJC2 - METMF (R) - NCW - NTCSS
Aircraft (NAE) - aADNS - Air NAVWAR - HFIP - Tac/Mobile
Force Level (NAE/SWE) - ADNS - CENTRIXS - CWSP - DCGS-N - EHF - GCCS-M - ISNS
Unit Level (SWE) - ADNS - ISNS - GCCS-M - SHF - CENTRIXS - INMARSAT - NAVWAR SEA - SSEE Incr E/F
PEO Space Systems
PEO Space Systems
Submarine (USE) - CSD - CSRR - NC3LTS - SubHDR - SubLAN
Shore Site (NECE) - DCGS-N - JMINI - NTCSS - Tactical Switching
Infrastructure Reduction & SOA Migration Strategy
Service Oriented ArchitectureCommon Computing Environment
Thin Client access to services
Network Programs ISNS, CENTRIXS,
SCI, SUBLAN
Application ProgramsGCCS-M, DCGS-N, NTCSS
Computing Resources& Clients
Community Of InterestServicesSoftware
Development
Rapid CapabilityFielding
TODAY TOMORROW
Comms Programs Multi Band / Software Defined / IP
Network Infrastructure Migration Strategy
HM&ECENTRIXS
SVDS
Routin
g/Net
Mgmt
SCI LAN
ADNS
UNCLAS LAN (NTCSS)
SCI ADNS
EMSRF Mgmt/
Multiplexing ADNS Incr III
GENSER ADNS
Legacy Voice
VoIP
ADNS – Automated Digital Network SystemSVDS – Shipboard Video Distribution SystemEMS – Element Management SystemVoIP – Voice Over IPNTCSS – Naval Tactical Command Support System
Consolidated Afloat Networks and
Enterprise Services (CANES)
ISNSGENSER LAN (GCCS-M)
Technical Approach Communications Strategy
Navy Strategy is to Pursue Integrated MILSATCOM & Commercial Solutions to Meet Global Communication Needs
Navy Strategy is to Pursue Integrated MILSATCOM & Commercial Solutions to Meet Global Communication Needs
Technical Approach Communications Strategy
Navy Strategy is to Reduce Radio Variants and Footprint To Meet Tactical Communication Needs Navy Strategy is to Reduce Radio Variants and
Footprint To Meet Tactical Communication Needs
10-15 Years Typical Major Acquisition Program Development
C4IRDC
C4I Program Development
Achieving Speed to Capability
B C(E.g., JSF, MUOS, FCS, DDX, CVN 21, etc)
2-3 Years CB
Need to Balance Speed with Programmatic Rigor RisksNeed to Balance Speed with Programmatic Rigor Risks
Innovative Acquisition• Combined DT/OT• Efficient Teamwork in developing JCIDS
Document (1st signed CPD in PEO)• Incremental Development/Fielding of COTS
Based system, MS “C” EntryEXAMPLE: ADNS Incr II Acquisition and
Deployment strategy provided capability to 70% of Fleet population within 12 months of positive MS Decision
Rapid Capability Insertion• Urgent Safety Needs• GWOT Response• Rapid NDI Delivery (70% solution)EXAMPLE: AIS - 162 Fleet installations of AIS
within 9 months of RDC approval
Challenge: Aligning C4I refresh with platform schedules and responding to urgent customer needs
PEO C4I Roadmap Summary
• PEO C4I products provide required capabilities to a broad range of Navy and Joint platforms/sites
• We have embarked on a critical path to achieve a service oriented architecture (SOA), reduce network infrastructure and deliver open systems
• Pace of C4I technology and unique afloat installation challenges require us to push for innovative acquisition practices
18
Operational C2
• Programs of Record• GCCS-M 3.X • GCCS-M 4.0• GCCS-M 4.1
• Initiatives• Small Footprint Architecture (SFA)• Transition to Service Oriented Architecture (SOA)
• Net Enabled Command Capability (NECC)
19
GCCS-M 3.X
• Legacy Program of Record• 1998 Vintage HP-UX Client-Server architecture• PC client capability via C2PC• Little/no integration of Tactical/non-Tactical• Hardware/software End of Life (EOL) issues
• Fleet phase-out by 2011 • Current status - “catastrophic maintenance”
• Limited support available
20
GCCS-M 4.0
• Current Program of Record is V4.0.2• User friendly PC workstations• Enhanced track management capabilities• Targeting management• Persistent ISR and target generation• Web access to important data• Embedded training and performance support• Increased Joint Interoperability
• Fleet fielding in progress
21
GCCS-M 4.1
• Includes all 4.0.2 capability plus• Unlimited Tracks (100K)• Upgraded HW & OS (Solaris 10/Windows XP)• CWS (C4I WEB Services)• Stand-Alone Non Segmented Client• Small Footprint Architecture (SFA)
SFA vs POR Comparison
SFA PROGRAM OF RECORD
Installation Documentation
Server Footprint
24
NECC – A Primer
• Primary future C2 capability provider for DOD• Integrates current GCCS Family of Systems
(FOS) variants within a single Joint POR• Service Component Program Offices will
continue to be responsible for any service unique capabilities
• GCCS FOS 4.1 variants will act as the foundation on which NECC will be built
25
GCCS-M Transition to NECC
Today FY13FY09 FY10 FY11 FY12 FY14
GCCS-M 4.1GCCS-M 4.0.x Future C2 Programs / NECC
S e r v i c e s
Tightly Coupled Capabilities
Maritime C2 Services
Battlespace Awareness
Force Management
FOTCCST
MaritimeTDAs
20K Tracks
MineWarfare
METOCWX
Web Sched
C4I WebServices
Imagery and Intel
100KTracks
AegisBMD
WSM(PMI)
Future C2 Services
Future C2 Services
Future C2 Services
Program Office InfrastructureCommon Services
Common Computing Environment
NECC Governance
JC2CPMOSAE
NECC CPMO
Joint PEO PEO C2C
Joint Forces Command Operational Sponsor
Joint Combat Capability Developer
DISASAE
GCCSPMO
GCCS-JPMO
To be formal at some future date
Formal Lines of Acquisition GovernanceInformal Lines of Communications
DISA Acquisition
Executive (CAE)
CPMO – 5 Component Program Management Offices(DISA, Air Force, Army, Navy, USMC)
C2 Capabilities Integration Board
NECCJPMO
Milestone DecisionAuthority ASD(NII)
27
International C4I Integration Questions