1

System Engineering and Integration for Submarine Combat Systems in

the COTS EnvironmentDennis J. Cooper

SWFTS Program Manager Lockheed Martin Integrated Systems

Joan SienkiewiczSWFTS Program Manager

General Dynamics Electric Boat

Mike OliverSWFTS Program Manager

Lockheed Martin Maritime Systems and Sensors

2

Submarine Combat System Paradigm Shift

• Submarine combat systems employ Commercial-Off-The-Shelf technology and open system standards to provide:– An affordable path to leverage commercial technology in parallel with

the build-test-build development cycle– Asynchronous rapid transition of advanced functional improvements

through modular software builds in a networked environment

• Harnessing this capability required a change to the system engineering, interface, integration, and configuration management processes

This SE&I Model Was Proven Successful on theThis SE&I Model Was Proven Successful on theVirginia Class Combat SystemVirginia Class Combat System

3

Today’s Dynamic Environment

• Varying acquisition “cycle times” between subsystems

• Fleet driven rapid introduction of warfighting capability

• Technology transition from custom to COTS

• Radical reductions and gaps in funding

• Spiral Development

• Increasing system complexity

• Software Intensive Systems

• Desire for commonality across platforms

• Network Centric / Interoperability

• Information Security and Assurance

Business Models have evolved to adapt to the Business Models have evolved to adapt to the changing environmentchanging environment

4

Architecture Contrast

• Use of closely held, private interfaces, languages, data formats and protocols

• Critical importance given to unique design and implementation

• Use of individual company preferences to set and maintain interface specifications

• Vendor and technology dependence• Difficult and more costly integration• Use of sole-source vendor• Expansion and upgrading usually

requires considerable time, money and effort

• Components, interfaces, standards, and implementations are selected sequentially

• Use of publicly available and widely used interfaces, languages, data formats and protocols

• Critical importance is given to interface management and widely used conventions

• Use of group consensus process to maintain interface specifications

• Vendor and technology independence

• Easier and more cost effective to integrate

• Use of multiple vendors• Easier, quicker and less expensive

to upgrade• Components, interfaces, standards,

and implementations are selected interactively

Closed System Open System

Source: ITEA Journal: September/October 2001 (Volume 22, Number 3)

Interface Management is the Key to SuccessInterface Management is the Key to Success

5

Open System Model

• Focus on the network and subsystem to subsystem domains to define and manage:

– Open Architecture / Open System Standards

– Interface Design and Definition• Functional not physical

– Network Design, Services and system performance

– Network software solutions

– Technology Evolution

– Standardized processes and products

This Open System Model has been implemented on the Submarine Functional Interface Baselines by a disciplined and measured approach to interface development and data flow management

6

Virginia Class Submarine Combat System

Need to manage and control the interfaces for the 23 subsystems of the Virginia Class Submarine Combat System

CombatControl

LAN

ArchitectureLAN

Sonar LAN

Guard

SCI

KG

TS

U

S

ECS (Data)

Guar

d

TSN

ULAN

Guard New Standard IP Addressing(Routed Network)

NO STRIKE

ENCLAVE

CombatControl

LAN

ArchitectureLAN

Sonar LAN

Guard

SCI

KG

TS

U

S

ECS (Data)

Guar

d

TSN

ULAN

Guard New Standard IP Addressing(Routed Network)

NO STRIKE

ENCLAVE

7

ANALYZE NEWREQUIREMENTS

FUNCTIONAL DECOMPOSITION &

ALLOCATION OF PLATFORM / INTER SUBSYSTEM LEVEL

REQUIREMENTSAS AN IPT

TRACK

CHANGE ASSESSMENT

Internet

SYSTEMS ENGINEERING IPT

HW/SW TECHNOLOGY INSERTION IPT

PROGRAM MGMT IPT

INTEGRATION TEST & EVALUATION IPT

SUPPORTABILITY IPT

FEDERATED SUBSYSTEM MANUFACTURERS/PARMS

SYSTEMS ENGINEERING IPT EXECUTION AGENTSREQUIREMENTS

Fleet Requested Improvements

APB Requirements

FORCENetRequirements

Sea-Test Results

Technology Improvements

Open Architecture Standards

PARM Input

IA RequirementsFEEDBACK OR

IMPLEMENTATION

Baseline Changes via Change Board

Process

Trade Study Recommendations

Allocated Requirements

SE&I provides Top Level Combat System and Interface requirements. All other requirements are managed by the Federated subsystems

It Starts with Requirements Management

Web Interface Product Tool (WIPT)IDLIDL GRLGRL

A Streamlined System Engineering Approach

8

SUBSYSTEM X-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

-SIGNIFICANT TECH.EXCHANGE

SUBSYSTEM A-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

-SIGNIFICANT TECH.EXCHANGE

SUBSYSTEM B-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

-SIGNIFICANT TECH.EXCHANGE

SUBSYSTEM C-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

-USE COMMON IDL

SUBSYSTEM Y-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

-SIGNIFICANT TECH.EXCHANGE

SUBSYSTEM Z-INVOLVED IN IDL WG- USE COMMON AGREEDTO IRS & IDD FOR DESIGN

- USE COMMON IDL

Traditional Approach

EARLY IDENTIFICATION OF INTERFACE PROBLEMS/EARLY TESTING VIA EIT/WAN

Evolution of Interface Standardization

INTERFACE WORKING GROUPS•COMMON AGREED TO REQUIREMENTS

•GROUP PRODUCTS (GDD, IDL)

COMMON IDL

MINIMUM PLATFORM INTEGRATIONNetwork / Group

Approach

SUBSYSTEM A- INTERPRETS IRS-GENERATES IDD-DESIGNS SUBSYSTEM

SUBSYSTEM B-INTERPRETS IRS-GENERATES IDD-DESIGNS SUBSYSTEM

IRSPROVIDED BY

NAVY

IDD

SUBSYSTEM A

IDD

SUBSYSTEM B

INTERFACE PROBLEMS FOUND DURINGPLATFORM INTEGRATION

SIGNIFICANT $’s AND SCHEDULE

9

System EngineeringNetwork Architecture, Interface Design

Traditional Point to point Design Process

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

IRS

ESM IMG

CSRRVMS

SONAR WC

RLGN

TC

Infrastructure•Architecture•Networking•X-Windows•System Mgmt

Nav Data•Own Ship Nav•Charts

Sonar Data•Sonar Settings•Streams

OBTTHME•HM&E•Environmental•Alerts

COMMS•ECS

ContactsContacts•Misc / CC Settings

ApplicationSoftware

Subsystem A

ApplicationSoftware

CORBA

Subsystem B

ApplicationSoftware

Subsystem C

ApplicationSoftware

Subsystem D

Network

Network / Group Product Design Process

OBTTHME

CONTACTS

COMMS NAVSONAR

CORBACORBA

CORBACORBACORBA

Group Products• Open System Architecture

Requirements and Standards (OSA)

• Group Requirements List (GRL)

• Interface Definition Language (IDL)

• Group Data Dictionary (GDD) • System Network Design

Yesterday Today

Interface Working Groups

10

SE&I Interface Product Definitions

• SE&I Interface Products under Configuration Management:

– Group Requirements List (GRL)• Database that contains all interface requirements for all subsystems.

– Group Data Dictionary (GDD)• Contains definitions for all Interface Data Elements (IDEs) and IDE Assemblies

(IDEAs) produced and consumed by subsystems within a Data Group

– Interface Definition Language (IDL)• IDL provides the standard interface between objects, and is the base mechanism

for object interaction between subsystems. – Interface Integration Data Base (IIDB)

• Provides details of what interfaces are required for each subsystem on a per hull

basis. Grouped by interface types and contains the Interface / method / Name

Space Name (CORBA), Service Name (Services), Subsystems, GRL linkages,

GDD linkages and indications of Provider, Recipient, Originator.

11

SE&I Product Relationships

Sequence No.

GRL

Subsystem Allocations

Method: programmed procedure within an interface

IDLIIDB (CORBA)

GDDSubsystemAllocations

Linked to a particular interface data rate

Auto generated from IDL

Request For Subsystem Requirement

Change/Enhancement

Facilitators develop requirements and products based on request

- Used to verify subsystem I/F

IDL EmbeddedIn SubsystemApplication

Facilitators work with subsystems to generate IDL per requirement

Subsystem Allocation

Sequence No.

GRL

Subsystem Allocations

GRLGRL

Subsystem AllocationsSubsystem Allocations

Method: programmed procedure within an interface

IDLIIDB (CORBA)

GDDGDDSubsystemAllocations

SubsystemAllocations

Linked to a particular interface data rate

Auto generated from IDL

Request For Subsystem Requirement

Change/Enhancement

Facilitators develop requirements and products based on request

Request For Subsystem Requirement

Change/Enhancement

Facilitators develop requirements and products based on request

- Used to verify subsystem I/F

IDL EmbeddedIn SubsystemApplication

Facilitators work with subsystems to generate IDL per requirement

Subsystem Allocation

12

Navigation:Lockheed MartinNorthrop Grumman

• Integrated Product Team structure to develop and maintain interface specifications and products (GRL, IDL, GDD, Network Design, Information Assurance)

• Adopts widely used standards, data formats, and protocols• Defines key attributes of the network and services• Consensus-based interface definition and design

Interface Working Group Participants

Contact Data:RaytheonGD-AISLockheed MartinKollmorganNUWC

On-Board Training:Electric BoatLockheed Martin

Hull/Mechanical Data:Electric BoatNUWC

Communications:Electric BoatLockheed MartinNUWCSPAWAR

Infrastructure:Lockheed MartinProgenyElectric BoatGD-AISNUWC

Environmental Data:Lockheed MartinGD-AISElectric Boat

“The key is in designing an architecture that is going to take advantage of commercial standards, the ability to pull pieces out and reuse them in other

systems and platforms, and that allows third parties access” Delores Etter, Assistant Secretary of the Navy for RDA

13

Interface Layers

Interface Management designed in to streamline integration by reducing/eliminating at each of the layers of the Interface

Generic Data Transfer Model CORBA Data Transfer Model

Shared(System and

Subsystem)Domain

SystemDomain

NTDS Data Transfer ModelSubsystems

Domain

NTDS Protocol / Driver(NTDS Spec)

I/O Application Code(IDS)

Application Code(IDS / SRS)

NTDSNTDS

Subsystem Domain

Network

Time ServicesName Services

Semantic•Data Interpretation

Behavioral•Message Sequencing•Fault/Fail Schema

Syntax•Data Field Definition

Interface Protocol•I/O HW and SW

Network Protocol(Network Spec)

Common IDL

CORBA Application Code(GRL, SIFT, GDD)

Application Code(GRL / SRS / GDD)

NICNIC

Yesterday TodayESM IMG

CSRRVMS

SONAR WC

RLGN

TC

OBTT HME CONTACTS

COMMS NAV SONAR

14

SE&I Toolset

Support

Test

Requirements

Develop

Physical (HW)Physical (HW)Functional (SW)Functional (SW)

Web Integration and Test Tool (WITT)

Supportability Integrated Logistics

Capability (SILC)

Web Interface Product Tool (WIPT)

InternetTest

ICD

Ope

n an

d C

ompl

ete

Acc

ess

Tactical HW Interface Platform D/B (TIPD)

PTRsDebug

Requirements Baseline

GRL

IDL

Fully integrated and web-enabled toolset for SE&I

TIs

15

What’s next?

• It doesn’t end with Interface Management!– Systems engineering processes and products must be

balanced with integration products and processes– There is an inherent relationship between standards,

interface engineering and system integration• System definition• Interface design and development• System test and integration

– The confluence of an open systems architecture, standards and system integration leads to:

• Easier technology insertion• Fielding capability faster• Streamlined system integration

SE&I is a balanced approach between interface SE&I is a balanced approach between interface management, standards and system integrationmanagement, standards and system integration

16

SE&I Process and Products

System Acceptance

Test

Early Interface Functional

Testing

Interface Design

Specifications / Implementation

Subsystem to Subsystem

Testing

Interface Development

System Requirements Specification

Interface Requirement Specification

Fully integrated and web-enabled toolset for SE&I

Web IntegrationAnd Test Tool

(WITT)

Web InterfaceProduct Tool

(WIPT)

Products:• GRL• GDD• IDL• IIDB

Products:• SRVM• Test

Procedures• Test Results• PTRs

17

Test and Integration(The “I” in SE&I)

Networked Labs and Collaboration Provide Mechanisms for Early Networked Labs and Collaboration Provide Mechanisms for Early Integration Testing to Minimize RiskIntegration Testing to Minimize Risk

Approach:• Virtual Integration Facilities to

optimize capital investments• Structured interface testing• Allow collaborative debug of problems

from development lab • Distribution of software builds/patches• Remote access to development

environments• Responsiveness to Fleet needs• Support Certification

Goals:• Achieve a single integrated, cohesive

working Combat System• Risk Mitigation • Cost containment• Schedule Control• Optimize Government and Industry

Lab resources• Early integration and test of interfaces• Pull integration and Lifetime Support

issues from the fleet and solve in labs

18

IDE Web Portals

Requirements

Test Cases

Behavior : Method Calls

PARM Drop Plan

Facilities Plan

Data Dictionary (GDD)

Subsystems

Platforms

Test Schedule

SE

IntegrationProblem Database

Requirements

SRVM / VDD

Test Procedures

Schedule

PTR InfoTest Results

Facilities Plan

Debug Info

Internet

IPT Hierarchy & Information Relationship

PMT (Executive Group)

I/C IPT

Functional Integration JTG/PRB

Physical Integration JTG/PRB

Certification and Delivery

JTG/PRB

3/19

3/1912/1

4/112/1

4/14/1

1/3

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarQtr 1, 2004 Qtr 2, 2004 Qtr 3, 2004 Qtr 4, 2004 Qtr 1, 2005

3/19

3/1912/1

4/112/1

4/14/1

1/3

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarQtr 1, 2004 Qtr 2, 2004 Qtr 3, 2004 Qtr 4, 2004 Qtr 1, 2005

3/193/19

12/14/1

12/14/14/1

1/3

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarQtr 1, 200 Qtr 2, 200 Qtr 3, 200 Qtr 4, 200 Qtr 1, 200

3/193/19

12/14/1

12/14/14/1

1/3

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarQtr 1, 200 Qtr 2, 200 Qtr 3, 200 Qtr 4, 200 Qtr 1, 200 3/19

3/1912/1

4/112/1

4/14/1

1/3

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarQtr 1, 200 Qtr 2, 200 Qtr 3, 200 Qtr 4, 200 Qtr 1, 200

DashboardMetrics

Technical Issues & Direction

Working Technical Data

Web-based Integration and Test Toolkit (WITT) BenefitsBased on OSI Model: Expandable EnvironmentAutomated Test Procedure, SRVM, and ROA: Built-in Test ReuseEarly System T&I Planning Suite with Auto-Lab-UtilizationUniversal Interface Debug Tools Online Test Pass/Fail Recording / Automated V&VDashboard Style, Drill-Down Technical and Programmatic Metrics

Web-based Integration and Test Toolkit (WITT) BenefitsBased on OSI Model: Expandable EnvironmentAutomated Test Procedure, SRVM, and ROA: Built-in Test ReuseEarly System T&I Planning Suite with Auto-Lab-UtilizationUniversal Interface Debug Tools Online Test Pass/Fail Recording / Automated V&VDashboard Style, Drill-Down Technical and Programmatic Metrics

SE IPTLTS IPT

Automated SE&I Toolkit

Web-Enabled SE&I Toolkit Connects all Stakeholders

Web Integration and Test Toolkit (WITT)

Web Interface Product Toolkit (WIPT)

19

System Engineering & Integration Approach: Test What has Changed; When it is ready

InterfaceRequirements

Group Products

Test CaseMatrix

TestSchedule &

Conduct PTR Adjudication

Facilities Plan

R A D A R

T C

W C

S U B L A N

S O N A R E C S

L M R S

Im a g in g

E S M

I AR L G N

T A C L A N

R A D A R

T C

W C

S U B L A N

S O N A R E C S

L M R S

Im a g in g

E S M

I AR L G N

T A C L A N

Facility #2

R A D A R

T C

W C

S U B L A N

S O N A R E C S

L M R S

Im a g in g

E S M

IAR L G N

T A C L A N

R A D A R

T C

W C

S U B L A N

S O N A R E C S

L M R S

Im a g in g

E S M

IAR L G N

T A C L A N

Facility #1

WAIF

•Prioritization•Debug•Problem Isolation•Resolution•Verification

System Integration approach has evolved through several iterations and provides complete management of Requirements, Tests, Facilities, Drops, and PTRs

Subsystem Assessment IT&E

NBCR # Title TC WC

Tacl

anSo

nar

NA

VR

AD

AR

SUB

LAN

RA

DIO

ESM

Imag

ing

Impl

eme

ntat

ion

Sche

dul

e

xxx-750 Update to IPv06 C C P C C C P P C C H L1132- Net-Centric Warfare (NCW) Distance Support P P C C M L1133- Digital Navigation Computer to Computer Information Transfer P C C C C C P C M Lxxxx- Consolidation of Displays PCPC PC PC PC PC PC PC H M968- GRL Mapping in IIDB is incorrect P C M L047-750

Add Transverse coordinate system data elements to sensor and contact reports C C P P P P M M

Other Network Loading M H M M M M M H H LOther Off-Hull Bandwidth M M M H H MOther Taclan Switch Changes L H L L L L L L L L H L

Sche

dule

Impl

emen

-tatio

n

Subsystem Assessment IT&E

NBCR # Title TC WC

Tacl

anSo

nar

NA

VR

AD

AR

SUB

LAN

RA

DIO

ESM

Imag

ing

Impl

eme

ntat

ion

Sche

dul

e

xxx-750 Update to IPv06 C C P C C C P P C C H L1132- Net-Centric Warfare (NCW) Distance Support P P C C M L1133- Digital Navigation Computer to Computer Information Transfer P C C C C C P C M Lxxxx- Consolidation of Displays PCPC PC PC PC PC PC PC H M968- GRL Mapping in IIDB is incorrect P C M L047-750

Add Transverse coordinate system data elements to sensor and contact reports C C P P P P M M

Other Network Loading M H M M M M M H H LOther Off-Hull Bandwidth M M M H H MOther Taclan Switch Changes L H L L L L L L L L H L

Sche

dule

Impl

emen

-tatio

n

Sche

dule

Impl

emen

-tatio

n

SubsystemSchedules

Interface Requirements Change••GRLGRL

Interface ImplementationChange••IIDBIIDB••GDDGDD••IDLIDL••NDDNDD

Change Control Board

Change Control Board

NPES REQUIREMENTS

BASELINEREVISION

NPES REQUIREMENTS

BASELINEREVISION

PTR BoardPTR Board

Implementation ProblemRequirement Change

BCR: Baseline Change RequestPTR: Problem Trouble Report

INTERFACEChange Request

Interface WORKING GROUPS

Interface WORKING GROUPS NPES

IMPLEMETATIONBASELINEREVISION

NPESIMPLEMETATION

BASELINEREVISION

Interface Requirements Change••GRLGRL

Interface ImplementationChange••IIDBIIDB••GDDGDD••IDLIDL••NDDNDD

Change Control Board

Change Control Board

NPES REQUIREMENTS

BASELINEREVISION

NPES REQUIREMENTS

BASELINEREVISION

PTR BoardPTR Board

Implementation ProblemRequirement Change

BCR: Baseline Change RequestPTR: Problem Trouble Report

INTERFACEChange Request

Interface WORKING GROUPS

Interface WORKING GROUPS NPES

IMPLEMETATIONBASELINEREVISION

NPESIMPLEMETATION

BASELINEREVISION

20

Lessons Applied

• Be prepared for a major cultural change and manage it!• Adopt standards widely developed/recognized by industry• Focus on interface management not subsystem development• Strive for consensus-based interface definition on all key interfaces

early• New business models and processes will be required• Link functionality updates (APBs) to bundled interface baseline updates• Be prepared to migrate with technology (standards lag the technology

curve)• All interfaces are not created equal• Consider and develop a strategy for information assurance, fault

management and fail-over early. Most standards ignore these areas!• Plan for change!

Interface management is the key!Interface management is the key!