Surface Navy Combat Systems
Engineering Strategy
Kathy Emery, Chief Architect
PEO Integrated Warfare Systems
4 March 2010
Open Architecture (OA) is a key enabler
for meeting the CNO’s objectives
Naval OA is a
multi-faceted business and
technical strategy for
acquiring and maintaining
National Security Systems
(NSS) as interoperable
systems that adopt and
exploit open-system design
principles and architectures
NAVAL OA CORE PRINCIPLES
Modular design and design
disclosure
Reusable application software
Interoperable joint warfighting
applications and secure
information exchange
Life cycle affordability
Increased competition and
collaboration
2
Implementation of OA across the
enterprise will yield many benefits
Reduction in
Time to Field
Increased
Performance
Improved
Interoperability
 Decreased development and acquisition cycle times to
field new warfighting capabilities
 Faster integration of open standards based systems
 Improved operator performance thru delivery of cutting
edge technologies and increased bandwidth capabilities
from spiral developments and technology insertions
 Use of common services (e.g. common time reference)
 Use of common warfighting applications (e.g. track mgr)
 Use of published interfaces to standardize collaboration
 Leverage proven reusable components
Reduction in Risk
 Test early and often in the developmental cycle to
minimize risk of delivering non-interoperable products
 Cost avoidance from software re-use and use
Cost Avoidance
commodity COTS products at optimum prices
 Reduced training and streamlined lifecycle support
3
Top Level Acquisition Process View
Product
Development
Product Line Engineering
Requirements
Mission Archs
Funding
Regulations
Policies
PEO IWS Level
Requirements
Analysis
JFCOM
NNWC
Product Line
Architecture/
Interface Mgmt
OPNAV
DASN
Modeling and
Simulation
Requirements|
Interfaces
Technology
System Integration
and Test
Directorate Level
Platform Specific
Capabilities
Component
Component
Requirements
Component
Requirements
Definition
Requirements
Definition
Definition
Combat /
Warfare
System
Integration
Component
Component
Development
Component
Development
Development
System
Test &
Evaluation
Component
Component
Test
Component
Test
Test
CVN
Aegis
DDG
Aegis
CG
Certification
International
Science and
Technology
FMS Management
Capability
Capability
Integration
Capability
Integration
Integration
Capability
Capability
Test
Capability
Test
Test
PEO SHIPS/
CARRIERS/
Int’l Customers
DDG
1000
LCS
ONR
Integrated
Warfare Systems
& Capabilities
Installation
ILS &
Training
Fleet
AMPHIB
FMS
Readiness
Assessment
4
PEO IWS Organization
5
Implementing Open Architecture:
Strategy, Interfaces and Open Standards
 Treat computing environment as a commodity
– Select commercial mainstream COTS products
that conform to well-established open system
interface standards
Applications
Middleware
Commercial
Products
Operating System
– Bundle specific COTS products for a given
timeframe and revisit selections on a regular basis
Hardware
 Isolate applications from high rate-of-change
COTS through selection of standard APIs
– Upgrade H/W and S/W Independently and
on different refresh intervals
 Transform application development from single-
platform development to multi-platform portfolio
– Objective architecture defines key interfaces that
support extensibility and reuse goals based on
common data model
“Build
Once”
Track
Mgmt
Display
Command
Sensor Weapon Vehicle
&
Mgmt Mgmt Control
Control
Middleware
Operating System
Hardware
– Eliminate redundant software development efforts
6
Information-Oriented Architecture Is Key to
Defining Reusable, Extensible Components
•
•
•
•
•
Define a common data model and information standard
Component-to-network interfaces, not component-to-component
Component interfaces are coordinated* and authenticated**
Expose information and post for any authorized subscriber to access
Producers of information don’t have to be aware of consumers
Component
Component
Component
Component
Attributes
Attributes
Attributes
Attributes
Services
Services
Services
Services
Data-Oriented API (Publish/Subscribe Model)
Information Architecture
Transport Services
*Coordinated = fully-specified IDD, Gov’t CM via ICWG
**Authenticated = interface compliance test before acceptance
7
Surface Combat System
Network-Based Architecture
Controlled
Vehicles
External Comms
(Air,
surface,
DDS
CDL-N
ADNS
JTT
METOC
C2/ISR
JPALS
Planning
TDL
Air Traffic
Control
underwater)
Weapons
Sensors
Radar
IFF
ES
•
•
•
•
•
•
Sensor Management (local)
Track Management (Common Tactical Picture)
Combat & Control (incl. Tactical Mission planning)
Weapon Management
Vehicle Control (air, surface, underwater)
Display / User Interface
EO/IR
NCTR
Launchers
Common Core Software
Missiles
Decoys
Torpedoes
Computing Environment*
Guns
Computing Equipment
(processors, displays, networks,
storage, physical interfaces)
Infrastructure Services
EA
Acoustic
TTWCS
Combat
System
Trainer
Color Coding
Combat
System
Readiness
Nav Data
ECDIS-N
Fusion System
IWS
AIR
C4I
* Computing environment could be
combat system specific or total ship
C2
Trainers
Support
Aviation
Trainers
Logistics
Systems
Total Ship
Training System
Time
AIS
Nav
Trainer
Nav
Sensors
GPS
Wind
Navigation
8
Transitioning to Objective Architecture
Based Combat System
Required warfighting capabilities determine
components modified
9
Aegis Weapon System Hardware
Architecture Roadmap
Pre-Aegis
B/L 1/2/3/4/5
1960
Year
B/L 6 Ph I/III B/L 7 Ph I
DDG 51-78
CG 47-73
1980
DDG 79-90
CG 66 & 69
1994
DDG 91-112
ACB 08/TI 08
Advanced Capability
Build (ACB)
Technology Insertion (TI)
2002
2009
ACB 12/TI 12
2012
Weapon
System
ACB 16/TI 16
2016
CPS
MIL Spec Design
Processors
UYK-7
MIL Spec Design
UYK-7 UYK-43
UYK-20 UYK-44
Normalized
Equivalent 2 UYK-43
Capability
Displays
Connectivity
UYH-4
4 UYK-43
UYH-4
All NTDS
UYQ-21
(TGC)
Point-to-Point
Mixed COTS and
MILSpec Design
UYK-43/44+
Adjunct COTS
Mission Critical
Enclosure (MCE)
All COTS computers
COTS
SMP’s
(MCE)
Common Processing
Common Processing
A Scaleable Pool of System (CPS) & MCE
System (CPS) & MCE
Interchangeable
A Scaleable Pool of
A Scaleable Pool of
Processors
Interchangeable Processors Interchangeable Processors
COTS
Blades
120 UYK-43
270 UYK-43
875 UYK-43
UYQ-21/UYQ-70
Thin Client
Displays
Thin Client
Displays
Point-to-Point
CPS
Point-to-Point
COTS
Blades
COTS
TBD
~2500 UYK-43
TBD
Common Display Systems (CDS)
All Network
Pub Sub
All Network
Pub Sub
Increased computing power and network-based performance will enable
significant combat system warfighting improvements
10
Evolution of Open Architecture
We are now focused here
COTS Infrastructure
I
Characteristics:
• Separation of
Application/
Infrastructure
• Commercial Standards
• Commodity Products
Key Engineering
Activities:
• COTS Performance
Characterization
Benefits/
Evidence:
Component-Based
Software
II
• Component-Based
Designs
• NetworkedApplications
• Configurable Test
Environments
Common Core
Architecture
III
IV
• Open Business Practices • Common Objective
Architecture / Interfaces
• Rapid Transition of New
Capabilities to Systems
• Open Disclosure / Data
Rights
• 3rd Party Developers
• Multi-Level Test
and Evaluation
• Prototypes / EDMs
• KPP Validation
• Planned Refresh
Cycles
• Increased Reuse
 Increased
Performance /
Bandwidth
 Decreased Dev Time
 Reduced Cost
Open Business
Model
 Improved Testability
 Reduced Cost (Reuse)
 Scalability, Extensibility,
Testability, …
• Peer Reviews and
Independent Assess
• Mentoring
• Common Components,
Frameworks, Services
• Common Precepts/
Patterns/Standards
• Align Existing Arch /
Roadmaps
• Establish/Publish
“Objective Arch”
• Fleet Involvement
• Establish/Publish
Common Data Model
o Increased Number of
Vendors/Opportunities
o Improved
Interoperability
o Improved Transition of
S&T to Fleet
o Cost Avoidance
o Reduced
Training/Support
11
PEO IWS Responsible for Achieving
OA Objectives for Combat Systems
Coordinate architecture and
overarching interface principles for
developing combat systems
Oversee design, construction and
maintenance of all ship combat
systems
Coordinate combat system
acquisition programs across PEOs
Leverage combat system software
components across programs
“We must change
from an approach
that is optimized by
program and
platform to one that
can solve the
challenges of
integrated systems
that cross many
platforms and
functions…”
– ASN(RDA) MSG DTG 112123ZOCT02
We are transforming to a product line acquisition approach
12
Surface Combat System
Top Level Objective Architecture
Operational Command & Control
GCCS, NECC, NCCT
Platform Adaptation
External Communications
Domain
Link 16
S TDL J
JRE
Link 11
Link 22
TDL Interface
Controller
CDL-N
CDL Interface
Controller
DDS
DDS Interface
Controller
SIPRNET
NIPRNET
JTT / IBS
SPY-1
DBR
AMDR
SPQ-9B
SPS-49A
SPS-48E
SPS-67
SPS-73
SPS-74
UPX-29
UPX-37
CIWS
MK 9
SLQ-32
EDO ESM
SEWIP
EO/IR
FLIR
MH-60R
Towed Sonar
Hull Sonar
Bridge System
SATCOM
Router
Display
Domain
Common Core
Training
Training
Common
Dev Env
Dev Env
GUIs
Comms
Domain
Manager
External
Comms
Coordinator
Sensor
Sensor
Control
Sensor
Control
Controller
(one per sensor)
Navigation
Domain
Bridge
Interface
Controller
GPS
Inertial / Gyro
Water Speed Log
Depth Sounder
Magnetic Compass
METOC Sensors
AIS
Track Mgmt Domain
Above Water
Sensor
Coordinator
Below Water
Sensor
Coordinator
Ship
Movement
Coordinator
Chart Server
Navigation
Data Fuser
Consoles
Operator
Task Mgmt
Vehicle
Domain
Manager
Vehicle
Coordinator
Vehicle
Sensor
Coordinator
Vehicle
Scheduler
Vehicle
Weapon
Coordinator
Vehicle
Comms
Coordinator
Weapon Mgmt
Domain
Collaboration Mgmt
Weapon
Domain
Manager
Combat Control
Domain
Engagement
Scheduler
USW
Coordinator
Support Domain
MultiSource
Integrator
Combat
ID
Tactical
Decision
Support
Tactical
Mission
Planning
Link Data
Manager
Geodetic
Registration
Tactical
Decide &
Assess
Ship
Resource
Manager
CC Support
Services
Composite
Tracker
Infrastructure
Component
Domain
Framework
C.S.
Network
Security
C.S. LAN
Mgmt
C.S.
Interior
Comms
Readiness
Assessment
Training
Domain
(one per missile)
Sensor
Sensor
Control
Weapon
Control
Controller
Strike
Coordinator
Training
Dev Env
ASW
Trainer
Planning
Core
Data
Collector
Nav,
Position
& Time
Data
Mediation
Services
Data
Extraction /
Recording
After Action
Reviewer
Computing
Environment
Distributed
Objects
Messaging
Services
Data
Mgmt
C.S Security/
Info Assur.
Performance
Analyzer
Processors
Data
Reduction
Combat
System
Trainer
Computing
Resource
Mgmt
Cabinets
Logistics
Support
Scenario
Controller
SOA Core
Services
Displays
Sensor
Sensor
Control
Missile
Control
Controller
SUW
Coordinator
Knowledge
Manager
Storage
Vehicles
Fixed Wing
MH-60R
Small Boats
UAV
UUV
USV
Asset
Vehicle
Controller
Controller
(one per weapon)
System Track
Manager
Sensor
Tracker
Asset
Launch/
Controller
Recovery
Module
IAMD
Coordinator
Track Server
ECDIS-N
Computing Equipment Domain
Audio/
Video
Support
Display
Renderer
Sensor
Domain
Manager
Common
Display
Apps
Remote
Display
Controller
GUI
Display
TACSIT
Display
IBS Interface
Controller
Sensor Mgmt
Domain
Vehicle Control
Domain
Platform
Specific
Display
Apps
Platform
Specific
GUIs
Missiles
SM-2
SM-3
SM-6
ESSM
RAM
ASROC
Weapons
MK 41 VLS
MK 57 VLS
MK 29 GMLS
RAM GMLS
SeaRAM
MK 160 AGS
MK 160 GFCS
CIGS
CIWS
TTWCS
Harpoon
MK 36 DLS
Nulka
SLQ-32 EA
OTST
ATT
NIXIE
NLOS
Sensor
Sensor
Sensor
Sim/Stim
Sim/Stim
Simulator/
Stimulator
Weapon
Weapon
Simulator
Weapon
Simulator
Simulator
EW
Trainer
Weapon
Weapon
Simulator
Ext. Comms
Simulator
Simulator
Ship
Control
Trainer
Computer
Based
Training
Nav System
Simulator
Networks
13
Navy Technical Reference Model
User Groups
COI
COI
COI
COI
Application Services
Support Systems
ISR
Aviation Systems
Command & Control
COI
Ship Control
Combat Systems
Platform Training
Common Services
SOA Core Services
(Tactical Edge)
Basic Services
Enterprise Services
Common Computing Environment
Hosting Environment
Computing Hardware
Communications & Networks
WANs
LANs
Network/ Circuit Mgmt
SATCOM
Wireless
Security
14
Notional Joint UAS Control Segment
Software Framework
HCI
Display
Display
Integrated
App
GIG
Integrated
App
GIG
Integrated
App
HCI
Distributed
Local
Local
Local
Integrated
App
Integrated
App
Integrated
App
Supporting Services
UA Control Services
Payload Control Services
PLD Control
PLD Status
Local
ATC
Comm
Link Mgt
Weapons Control Services
Weapon
Status
Weapon
Control
Find, Fix,
Target
Combat System Focus
Media
Recording
Track
Storage
Collection
Planning
Task
Planning
Navigation
Weather
Planning Services
System
Access, Info
Product
Ass
Output
Content Management Services
Chat
Tactical
Msging
Collaboration
Audio
Comm
GIG
COMM Link to UAV
Navigation
Local
Comm
Link Mgt
Supporting Services Bus
Handover
Sense &
Avoid
GIG
Vehicle Status
Mission Control Services Bus
Auto T-O/L
Vehicle
Control
Threat
Route
Planning
Task
Processing
Track
Correlation
Exploit
Product
Link 16
Blue Force
Tracker
AIS
Geodetic
Display
Mgt
Environment
Feedback
Find, Fix,
Target
Training
Network
Mgt
Sys Health,
Maint.
C4I Focus
15
Today’s Shipboard Environment
(Direct interfaces, unique solutions, weak cross-domain integration)
MCCP
RF
Gertrude
WQC-2A
RF
RF
AIMS
MK XII
UPX-29
MIDS
MOS
URC-141
RF
RF
RF
RCS
Turnkey
CDL-S
AN/USQ-167
CDLMS
UYQ-86
RF
DBR
PEO IWS
SSTD RF
SLQ-25A
HFRG RF
URC-131
HSFB RF
SSR-1
DMR RF
SRC-61
MUOS RF
Terminal
RF
RF
ARC-210
NMT
JTT-M RF
USQ-151
SSES/ RF
SCI COMMS
14TV
SSEE INC
(X)
CEC
RF
EWS
SSDS
MK2
TISS **
CANES
Coalition
CV-TSC
SSQ-34C
RF
RAM
MK31
GMLS
MK29
TCS
USQ-171
27TV
GCCS-M
SCI
BFTT
USQT46
GPS
TBMCS
NN
DSVL
WQN-2
RLGN
WSN-7
SPS-73
Lite
CANES
(Genser)
GCCS-M
Genser
JMPS
RF
JWARN
DCRS
AIAS
RF
TCS
USQ-171
JSF ALIS
NITES
UMK-4(V)
(Genser)
DMS
Proxy
IBS
(SCC)
CATCC/RF
DAIR
TPX-42A
RF
ACLS
SPN-46
SEA RF
BASED
JPALS
AIS
(URN-31)
ILS
SPN-41
NAVAIR
6TV
TC2S
CANES
(SCI)
NAVSEA
NAVSSI
Bk 4.X
CIWS MK15
MOD21&22
DCGS-N
SCI
Radiant
Mercury
Fathometer
UQN-4A
DAS
IRST **
TV-DTS RF
OE-556U
GBS RF
USR-10
ADNS
USQ-144
TVS
USQ-155
ARC III
USQ-162
RF
RF
SMQ-11
UASS
UMQ-12
DCGS-N
(Genser)
IA
SATCC
VTS
ILARTS
ADMACS
BK III
CANES
(Unclassified)
Announcing
MC
IFLOLS
MWS
NITES
UMK-4(V)
(Unclass)
RF
BFEM
TACAN
URN-25
LRLS
MCMS
DMRT **
NTCSS
BK2
TMIP-M
PEO C4I
PPLAN
LSODS
MOVLAS
JSLSCAD
JCAD
AAG
DMS
Proxy
EMALS
PDR-65A
RADIAC
MFR
RADIAC
IPDS
MK26
MD0
IA
TCS
USQ-171
MLAN
JBPDS
SVDS
SXQ-10B
Non-Warfare Systems
Internal WS Interfaces
External WS Interfaces
**
Space & Weight
Network
Distribution Bus
16
Desired Shipboard Environment
(Networked interfaces, common/interoperable solutions,
significant cross-domain integration)
External Comms Systems
MIDS
CDL-S
GBS
CDLMS
PLATFORM
Gertrude
RCS
Turnkey
JTT-M
ARC
210
ARC
III
MCCP
HFRG
SMQ-11
DMR
MUOS
SSES/
SCI COMMS
NMT
HSFB
TVS
TV-DTS
ADNS
Functional Enclave
CATC
C
DAIR
ILS
ILARTS
DCGS-N
SCI
GCCS-M
SCI
ACLS
JPALS
ADMACS
Blk III
LRLS
DMRT
IFLOLS
MWS
Radiant
Mercury
Ship
Network
LSODS
AAG
SSEE
INC
CANES
(SCI)
MOVLAS
EMALS
GCCS-M
CANES
Coalition
NITES
TBMCS
TCS
Aviation Systems
TC2S
DCGS-N
JWARN
CANES
(Genser)
Functional Enclave
DCRS
UASS
DMS
Proxy
JSF ALIS
JMPS
IA
IRST
SGS/AC
CV-TSC
DMS
Proxy
NTCSS
Functional Enclave
TACAN
TISS
EWS
TMIP-M
SPS-73
IFF
CST
SSDS
CEC
GMLS
TCS
AIAS
CANES
(Unclassified)
RLGN
DSVL
NAV
DBR
IBS
VTS
RAM
AIS
Fathometer
SSTD
NAVSSI
Tactical Systems
Functional Enclave
Nav and HM&E
Systems
Functional Enclave
CIWS
BFEM
MLAN
NITES
IA
C4I Systems
Interface Control
Network Management
17
CANES Services supports CS data exchange with C2
Applications (whether onboard and offboard)
Direct and LOS
CORB-Defined
Baselines / Full IA
• HF Internet Protocol
SWTRG-Defined
Baselines / Platform IT
• Digital Multichannel Radio
• Milstar terminal-to-terminal
• Display
• Track Management
• SATCOM
• Combat Control
• LOS communications
• Weapon Management
• Vehicle Control
• External Comms Mgmt
• Navigation
• Training
• Support
Unclass
GENSER
Domain Boundary
• WAN gateway
Domain Boundary
• Sensor Management
Ashore
C4I Network & Services
• Afloat internal ship networks
• Afloat Core Services
Domain Boundary
• DISN
• NIPRnet
SIPRnet
• NMCI
C4I Applications
DDS, CDL-N, TDLs, JTT/IBS
NOC
Domain Boundary
C4I External
Communications
• Infrastructure
Domain Boundary
Domain Boundary
Combat System
• Allied
networks
• GCCS-M
• DGCS-N
Information Assurance is a Significant Hurtle to Resolve:
PEO IWS and C4I will coordinate inputs to consolidated C&A activity
18
Common Component Requirements Flow from
Combat System Requirements – PSEAs Involved
SYSTEM DEFINITION
AND DESIGN
SYSTEM & SUBSYSTEM
DEFINITION AND DESIGN
FUNCTIONAL
BASELINE
SOFTWARE
IMPLEMENTATION
SUBSYSTEM
TESTING
SYSTEM INTEGRATION
ALLOCATED
BASELINE
PRODUCT
BASELINE
OPERATIONAL / CAPABILITY
REQUIREMENTS DEFINITION
(TLR / CDD / NCD / KPPs)
OPERATIONAL TESTS
(DT&E / OT&E)
SYSTEM
REQUIREMENTS DEFINITION
(A SPEC / SSS / TPMs)
NAVY COMBAT SYSTEM TEST
(SIT / DT)
(Level 5)
SRR
SYSTEM TEST & EVALUATION, TRR
MULTI-ELEMENT INTEGRATION
& TEST (MEIT) (Level 4/5)
SUBSYSTEM
REQUIREMENTS DEFINITION
(B1 / B2 SPEC)
SDR
SOFTWARE ELEMENT
REQUIREMENTS DEFINITION
(B5 SPEC / IDS)
PSEAs
SYS
CDR
ENGINEERING TEST &
EVALUATION (ET&E)
(Level 3)
SYS
PDR
SSR
ELEMENT
INTEGRATION & TEST
(Level 2)
COMPONENT SOFTWARE
REQUIREMENTS DEFINITION
(B5 SPEC / SRS / IDS)
SOFTWARE
DETAILED DESIGN
(Design Model)
SOFTWARE COMPONENT
UNIT AND COMPONENT TEST
(Level 1)
Design
Reviews
Code
Reviews
Software
Component
Developers
CODE
19
Process Definitions Needed for Each Phase from
Strategic Planning to Delivery / Sustainment
SYSTEM DEFINITION
AND DESIGN
Strategic Planning
Mission
Analysis
Int. Product
Roadmaps
Integrated
POM Planning
SOFTWARE
IMPLEMENTATION
SUBSYSTEM
TESTING
PRODUCT
BASELINE
OPERATIONAL TESTS
(DT&E / OT&E)
SYSTEM
REQUIREMENTS DEFINITION
(A SPEC / SSS / TPMs)
Enterprise
CCP
SRR
SUBSYSTEM
REQUIREMENTS DEFINITION
(B1 / B2 SPEC)
SDR
SOFTWARE ELEMENT
REQUIREMENTS DEFINITION
(B5 SPEC / IDS)
ACB
Execution /
Combat
System
Integration
NAVY COMBAT SYSTEM TEST
(SIT / DT)
(Level 5)
SYSTEM TEST & EVALUATION,
MULTI-ELEMENT INTEGRATION
& TEST (MEIT) (Level 4/5)
ENGINEERING TEST &
EVALUATION (ET&E)
(Level 3)
SYS
PDR
SYSTEM
SYSTEM DEFINITION
REQUIREMENTS
REQUIREMENTS
DEFINITION
(A SPEC / SSS
/ TPMs)
(A SPEC / SSS / TPMs)
SOFTWARE ELEMENT
SOFTWARE ELEMENT
REQUIREMENTS
DEFINITION
REQUIREMENTS
DEFINITION
(B5 SPEC
/ IDS)
(B5 SPEC / IDS)
COMPONENT SOFTWARE
REQUIREMENTS DEFINITION
(B5 SPEC / SRS / IDS)
SW
PDR
SOFTWARE
DETAILED DESIGN
(Design Model)
SYS
CDR
SOFTWARE
DETAILED DESIGN
(Design Model)
Combat
System
T&E / Cert
SOFTWARE COMPONENT
UNIT AND COMPONENT TEST
(Level 1)
Design
Reviews
SUBSYSTEM
SUBSYSTEMDEFINITION
REQUIREMENTS
REQUIREMENTS
(B1 / B2DEFINITION
SPEC)
(B1 / B2 SPEC)
Code
Reviews
CODE
SOFTWARE ELEMENT
SOFTWARE ELEMENT
REQUIREMENTS
DEFINITION
REQUIREMENTS
DEFINITION
(B5 SPEC
/ IDS)
(B5 SPEC / IDS)
SSR
COMPONENT SOFTWARE
REQUIREMENTS DEFINITION
(B5 SPECCOMPONENT
/ SRS / IDS)
SOFTWARE
UNIT AND COMPONENT TEST
(Level 1)
SW
PDR
SW
IBR
CODE
Feeder Program /
Common Asset
Development
TRR
SSR
SUBSYSTEM
SUBSYSTEMDEFINITION
REQUIREMENTS
REQUIREMENTS
(B1 / B2DEFINITION
SPEC)
(B1 / B2 SPEC)
SSR
ELEMENT
INTEGRATION & TEST
(Level 2)
COMPONENT SOFTWARE
REQUIREMENTS DEFINITION
(B5 SPEC / SRS / IDS)
SYSTEM
SYSTEM DEFINITION
REQUIREMENTS
REQUIREMENTS
DEFINITION
(A SPEC / SSS
/ TPMs)
(A SPEC / SSS / TPMs)
SYSTEM INTEGRATION
ALLOCATED
BASELINE
OPERATIONAL / CAPABILITY
REQUIREMENTS DEFINITION
(TLR / CDD / NCD / KPPs)
ACB
Definitions
S&T
Management
SYSTEM & SUBSYSTEM
DEFINITION AND DESIGN
FUNCTIONAL
BASELINE
Delivery & Sustainment
SOFTWARE
DETAILED DESIGN
(Design Model)
SOFTWARE COMPONENT
UNIT AND COMPONENT TEST
(Level 1)
SW
IBR
Ship
Integration
Integ. Fielding
Schedules
Fleet
Outreach
Readiness/
Perf. Asmnt
CODE
SE CONOPS
20
Combat System Objective Architecture
Component and Interface Definition
Legacy Components
RCIP
3rd Party Development
AMOD
S&T Rapid Development
Aegis
Objective Architecture
Component Development
SSDS
SSDS
DDG 1000
DDG
1000
• Defined superset component requirements
• Establish interfaces IAW objective architecture
• Develop/deliver authenticated components
A component is a bounded module with:
• Associated requirements (in DOORS)
• Design description
• Defined Interface (modeled in UML)
Common
Assets
Library
(CAL)
Available for
fielding in
CG(X) and
backfit in 2014
& beyond
21
PEO IWS Product Line Approach
for Surface Combat Systems
Aegis Development
DDG-1000
Development
CVN / Amphib
Development
rd Party
3rd3rdParty
Party
3
Development
Development
Development
Common Asset Library (CAL)
Based on a common architecture, with
Artifacts include:
- Common data standards and APIs
- Requirements (functional, performance, interface, design)
- Common services APIs
- Design models, engineering studies and papers
- Reusable software components (core assets) - Source code, compile and build scripts, configuration files
- Test plans, procedures, harnesses, execution results, metrics
Destroyers
Carriers
DDG-1000
Cruisers
Amphib
22
Benefits of Componentized
Objective Architecture
 Common allocations and interfaces allow components to be reused
across Combat Systems
– Reuse reduces integration and test costs for new development
– Improves interoperability and eases operator cross-decking
 Componentization localizes changes
– Reduces Test / Cert costs for subsequent upgrades for component level
changes
 S&T and new developers know how and where their products can fit in
– Improved transition of new technology into Programs-of-Record
 Extensible to accommodate upcoming new warfighting capabilities:
-
Threat-D
MH-60R Integration
Netted Surface Tracking
Ship Protection Systems
Improved Surface and
Underwater Pictures
- Net-centric Services
- Joint IFC / DWC
- Hardkill / Softkill
Coordination
- Common Air Control
- Fleet Synthetic Training
- Distance Support
- Maintenance Free
Operating Periods
- Optimized Manning
Initiatives
23
Product Line Approach
Way Ahead Perspectives
Technical Precepts
•Architecture
• Component Based
• Common Data Model
• Network-based interfaces
• Common framework for
reqmts allocation
•Design for reuse / extensibility
•Extensive use of M&S and
automated code, documentation
and test tools & techniques
Technical
•
•
•
•
•
Architecture Precepts
Objective Architecture
Component Boundaries
Key Interfaces
Open Standards
Programmatic
•
•
•
•
•
•
Arch. Description
Doc. (ADD) V1.0
July 2009
Funding
Schedule/Milestones
People
Requirements
Platform Obligations
Warfighting Commitments
Programmatic Precepts
•Spiral evolution process
• Bi-annual Advanced
Capability Builds (ACBs)
•Decouple new capability
development from ACB dates
•Rapid transformation to
common core software
•Rapid Capability Insertion
Process (RCIP) development
•Integrated POM Inputs and
program roadmaps
•Product Line Tasking &
Funding to field activities
Acquisition
Governance (Formalized)
• IWS Systems Engineering Board
• Cross-Program Coordination
• Approval and Decision Process
• Architecture and Interface Control
• Enterprise Configuration Management
• Open Peer Review Process
• Common Asset Mgmt & Reuse Library
• Facilitate Information Transfer
• S&T Roadmaps and Transition Plans
• Org. Roles and Responsibilities
•
•
•
•
•
Number/Types of Participants
Contracting Approaches
Peer Review Processes
Roles and Responsibilities
Incentivizing “Enterprise”
Behavior
Sys Engr Mgmt
Concept of Ops
April 2010
Acq Mgmt Plan
(AMP) V1.0
Dec 2009
Acquisition Precepts
• Open Business Model
• Data Rights and OA incentives
• 3rd party development of
components and capabilities
• Platform System Engineering
Agents (PSEAs) for end-toend C.S. engineering
• Competition at all levels
24
Business Characteristics of OA
OPEN BUSINESS MODEL
CHARACTERISTICS
 OA language in contracts
 Appropriate Data Rights
 Design artifacts disclosed
 Design artifacts published in
repositories
 Collaboration / Peer Reviews
 Continuous competition
 Rapid capability insertion
OPEN SYSTEM MODEL CHARACTERISTICS
 Modular architecture
 Widely accepted/supported
standards
 Use of commodity COTS
 Published Interfaces
 Isolated proprietary components
process (RCIP)
 Fleet involvement
25
PEO IWS System Engineering Guidance
Product line
systems
engineering
processes
Process for planning
and specifying
combat system
upgrades for biannual Advanced
Capability Builds
Describes
software
architecture for
combat system
product line with
focus on Combat
Management
software
April 2010
Executive plan to
build and maintain
Open Architecture
Combat Systems
Provides objectives
for stake holder
alignment
Integrated
configuration
management of
overall portfolio of
26