Evolution of Open System Architecturesin support of T&E for Naval Combat Systems

Ted Mulder, Senior Systems EngineerRobert Mueller, Senior Test Engineer

NAVSEA, Port Hueneme, Surface Warfare Center Division Detachment San Diego

NDIA System Engineering Conference, October 20-23, 2003

Introduction

• NAVSEA PHD DSD Mission– Combat System Integration Testing (CSIT)

– Battle Group Interoperability Testing (BGIT)

– CEC West Coast Land Based Test Site (LBTS)

• Naval Combat Systems – Past & Present– Review legacy systems when proprietary and MIL-STD ruled the day

– Present current systems such as the CVN-76 SSDS MK2

• T&E Tools– Hardware-In-The-Loop (HWIL) Simulation/Stimulation Systems

– Data Collection and Analysis

– Future initiatives

• Benefits of Open System Architectures (OSA)– T&E Benefits

– Tradeoffs

Our Mission

• Land-based reliability testing, integration, and certification of surface ship combat systems and computer networks both prior to initial operation and for in-service systems;

• Design, development, and life cycle maintenance of standardized simulation systems;

• Land-based facilities and services for the analysis of performance of in-service combat systems, subsystems, and equipment for afloat units;

• Provide engineering and technical support for test and development of command and control systems

Performs CSIT & BGIT for non-Aegis Surface Combatants

CSIT/BGIT in the Fleet Response Plan (FRP)

CV/CVNMaintenance

BasicIDTC

IntermediateIDTC

AdvancedIDTC/

SustainDeploy

Emergency Surge

Surge Ready

•TSTA•FEP

•C2X/FBP•Blue Water Cert

•JTFEX

3 – 4 months

Maximum 6 months

Supporting Emergency Surge Is The FocusSupporting Emergency Surge Is The Focus

BGITCSIT

NAVSEA PHD DSD

CSIT Description

• Interface Validation

• Functional Operability

•Multi Platform Interoperability Test

• Single / Multiple Warfare

• Functional Stress

• Performance Test

• Stress and Endurance

Integration Phase

Demonstration Phase

Low level subsystem tests designed to allow for rapid program fault isolation and correction.

Higher level of Combat System Testing that demonstrates that the integration of the Combat System performs IAW governing specification. Program change is not as fluid as in the previous phase.

Definition of an Open System

“A system that implements sufficient open standards for interfaces, services, and supporting formats to enable properly engineered components to be utilized across a wide range of systems with minimal changes, to interoperate with other components on local and remote systems, and to interact with users in a style that facilitates portability. An open system is characterized by the following:

• well defined, widely used, preferably non-proprietary interfaces/protocols;

• use of standards which are developed/adopted by recognized standards bodies or the commercial market place;

• definition of all aspects of system interfaces to facilitate new or additional systems capabilities for a wide range of applications; and

• explicit provision for expansion or upgrading through the incorporation of additional or higher performance elements with minimal impact on the system.”

(OS-JTF 1998)

CV-63 (ACDS BK0) Test Bed (1996)

DDCSATSIM

UYK-44

Shipboard Simulation Analog NTDS Serial NetworkNTDS Parallel

DDCSATSIM

UYK-44

C2PUYK-43

JMCISTAC-3

TAS MK-23UYK-44

SLQ-32(V)4UYK-19

SGS ACUYK-20

ACDSUYK-43

SPS-48CUYK-20

AUTOIDSUN

MOD 370

B

1553B LK-11

LK-11

AC

48C

49

LK-4A

LLS

LLS

NCVSATSIM

UYK-20

TASSATSIM

UYK-20

SDCE

CEESIM

ASWM 4.2UYK-43

A

RBOC SIM

TPX-42(V)13UYK-44

CVNSUYK-44

ASWM 4.3TAC-3

B

Link-16

Link-11

Link-4A

NSSMSSATSIM

SEATNSSMSMK-157/3

RADARVIDEO SIM

(RVS/VSS)

MIL-STD/Closed COTS/non-OSA OSA

A

Combat System Simulation (CSS) UYK-43

CVN-76 (SSDS MK2) Test Bed

L-16

L-4A

L-11

MLST-3L4 LLS

USQ-118

CDLMS(Ver. 3.1)

CV-TSC(Ver 5.1.0.0)

OTH

GO

LD

(CTC

, PO

S,

DE

L)

GCCS-M(3.1.2.1 p1)

IFF SIM(RVS)

TPX-42(V)14(UYK44 OSM)

NAVSSI(BLK 4)NAV IOC

(Partial ICAN)

WSN-7RLGN

GCCS-MLAN

STD NAV& WIND

KCMX

GPS SIM

DIS

Radar VideoSIM (2)

(Telemechanics RVS)

SPS-73

SPS-67

SPN-43C

RS-232

SGS/AC

(MK-162)

STD

Wind

MIL-STD-751B

Satellite RF

NAVLAN

NAVSIM

TSSS

NTDS-A

NTDS-E

ASDS(RADDS &SPQ-14)

DisplayLAN BFTT

STOW

DWMIS

Wy

Wh

a

SPS-73

SPS-67

IDS

-010

WS

N-7

/Ju

l 97

Rev

B(O

D0

+

OD

1)

ASTABSIFF SIM

(RVS)

UPX-29FC4

RAM BLK1EMULATORS(2 Pentium PC)

USIM(VME)

RNSSMS2 LIP, 4 TIP

(Ver 6.8)

SDCEMULATOR

CEESIM

SLQ-32A(V)4 R17

(UYK-19)Cqo, Eio, Wy, Wha

BAND 2/3

SPS-48(V)10

SPS-49A

DDS

CEPWASP(VME &

SUN WKS)

CEP

USG2(VME)

SPQ-9B

Shipboard Integrated Sim Standalone Sim Analog NTDS Digital Network

IOC

DDS

ATM

LA

U B

H1

UPX

48

49

SPQ-9B

DOCTRINE

NAV LAN

DDS

DIS

SSDS

MK-2

Mod 1

LA

U I

C1

TACTICAL

DOCTRINE

TACTICAL

Eio

, Z

do &

Cq

o

BEWT

BFTT Ver. 3.1

CTA

BFTT CTA

BFTTSTOW

DigitalComputer

BFTTSTOW

NAVLAN

PassiveLink Tap

J-Box

RS-232

MIL-STD/Closed COTS/non-OSA OSA

COMMON SCENARIO CONTROL ENVIRONMENT (CSCE)

Test Tools (Data Collection & Analysis)

C & C Sensor

{VME, UNIX, POSIX 1003.1b, NFS}

MILSTD 1397 Parallel

MILSTD 1397 Low Level Serial

MILSTD 1553 Serial

Ethernet / FDDI

Test Tool Network

CSDR

GEM

{WinNT, NFS}

DART

{Linux, NFS}

TheTool

{Linux, NFS}

LAN AnalyzerLogic Analyzer

{IEEE 802.3}

CV-63 CVN-76

Com

bat

Sys

tem

sS

im/S

tim

, T&

E T

ools

UKY-44/43/20/19

PCI

Interface & Standards Evolution

MIL-STD 1553B MIL-STD 1397MIL-STD 1553B MIL-STD 1397

MIL-STD 1553B MIL-STD 1397

MIL-STD 751B

PCM (IEEE 1386.1) SCSI (ANSI)

Ethernet (IEEE 802.3) FDDI (ANSI X3T9.5)

TCP (RFC 793, STD #7) RS-232/422 (EIA/TIA)

DIS (IEEE 1278)

UKY-19Q-70VME (IEEE 1014)

UNIX (POSIX 1,2) VxWorks (POSIX 1003.1b)

Ada95 (ISO 8652)

CORBA (ISO 19500-2)

HP-UX

UML

MIL-STD/Closed COTS/non-OSA OSA

TAC-3/4

PC DEC

43 RSS CMS-2Y

VAX DOS

SUN

43 RSS CMS-2Y

SUN OS HP-UX

UKY-44/43/20/19 PC

DEC

DOS

VAX

PC

WinNT

WinNT

SUN

IP (RFC 791, STD #5)

UDP (RFC 768, STD #6)

C++ (ISO 14882)

VME (IEEE 1014)

MIL-STD 1553B MIL-STD 1397

IP (RFC 791, STD #5) Ethernet (IEEE 802.3)TCP (RFC 793, STD #7)

RS-232 (EIA/TIA)

UNIX (POSIX 1,2) VxWorks (POSIX 1003.1b)

C++ (ISO 14882)

PCMPCI SCSI

Progression towards OSAW

IDE

PRIVATE

LO

WM

ark

et A

ccep

tan

ce

Standards Base PUBLIC

OPENSYSTEMS

Unique Designs,Optimized

Performance

ConsensusStandards

(No Products)

PopularProprietary

Products

Naval Combat Systems

T&E Tools

Future Direction with OSA Middleware

CECCECNAVSSINAVSSI

RNSSMSRNSSMS

CV-TSCCV-TSCGCCS-MGCCS-M

ACDSACDS

ICAN

SLQ-32SATSIM

CEPWASP

RAMEmulators

MLST3

Middleware Middleware Middleware MiddlewareMiddleware

GEM

Middleware

Sim/Stims

Test Tools

CSDR

Middleware

The Tool

Middleware

DART

Middleware

T&E Networks

Combat System

• Incorporate middleware in Sim/Stim and Test Tool environment• Abstraction of interface and communication mechanisms from the hardware• Leverage OODA paradigm (i.e. abstraction, reuse)

{CORBA, NDDS, Java RMI}

CSCE

TPX- 42TPX- 42

SLQ-32SLQ-32 CDLMSCDLMSSSDSSSDS

Scalability Benefits

Current System

(CPU or I/O max’ed out)

New Requirements

(software, processing, additional I/O)

MIL

-ST

D/C

omp

ute

rsC

OT

S O

SA

Solution

(add equipment)

Additional $750K

Additional $15K (VME chassis & SBC)

UYK-43

VME

Interface Affordability

Hub

NTDSVME card

EthernetPMC card

$5000 $200$50

MIL-STD Interfaces COTS OSA Interfaces

Functional Operability23%

Multi Platform Interoperability 3%

Functional Stress9%

Performance Test19%

Single/ Multiple Warfare 10%

Stress and Endurance9%

Interface Validation27%

Functional Operability29%

Multi Platform Interoperability 4%

Functional Stress10%

Performance Test20%

Interface Validation16%

Stress and Endurance9%

Single/ Multiple Warfare 10%

MIL-STD CSIT

Current CSIT with COTS OSA

Reduction in MIL-STD interfaces allows more CSIT time for higher level functionality testing in the application layer.

MIL-STD Interfaces Required each sub-contractor to program and “re-invent” the required interface protocols, thus consuming test time to integrate and debug.

CSIT Benefits from using COTS OSA

OSA T&E Tradeoffs

Pro• Leverage commercial technology• Reduce internal R&D costs • Reduced interface VV&A costs• Plug-In-Play Philosophy• Option of using multiple vendors• Industry upgrades & patches• Repair costs are less• Access to collective knowledge from public and industry sources• Accommodates rapid-prototyping• Allows user to focus on their domain knowledge and subject area

• Controlled by industrial product cycle• Shorter life cycle• Reduce in-house R&D expertise • Reliant on vendors VV&A processes• Plug-In-Play is not what they say• Too many standards to maintain• Reliance on vendor schedule for upgrades and patches• Increased security risk – common knowledge of standards• Unable to negotiate repair costs

Con

Summary

• Evolutionary progression of Naval Combat Systems– Reduction of proprietary equipment and MIL-STDs– Increased usage of open systems and standards

• Evolutionary progression of T&E Tools– HWIL Sim/Stim environments lockstep with the combat systems – Data Collection and Analysis will continue to utilize OSA – Incorporating OSA middleware products

• OSA Benefits and Tradeoffs– Scalability and affordability – Increased reliability of interfaces allows CSIT test events to focus on

the complexity of the application layer

• Comments – “last nickels”– CSIT test approach will evolve to support tech refresh of OSAs– T&E support of future combat systems will require the use of OSAs– Adoption of OSAs will require more government participation in the

standard working groups and conferences to ensure representation

COTS OSA is here to stay - there’s no turning back!

“Jacta alea est” (the die is cast)

BACKUP SLIDES

CSIT & BGIT within the D-30 Process

Collaborative SystemTests (CSTs)

BRBPromulgate

Proposed BaselineConfiguration

BF CCBEstablish

CCB Charter /Membership

COMPTUEX

BRBEstablish

DeploymentBaseline

Configuration

D-30 D-29 D-28 D-27 D-26 D-25 D-24 D-22 D-19 D-18 D-13 D-12 D-9 D-7 D-6 D-5 D-4 D-3 D-2 D-1 D

Platform CSIT/TSIT(Variable)

Assess&

Fix

ShoreBGIT

(Variable)

Assess&

Fix

D-18 D-11 D-10 D-7 D-6

BGSIT(Variable)

Assess& Fix

JITAssess& Fix

D-4 D-3 D-2 D-1

BGI CERT

FLTCINCPromulgate

BF CompositionMessage

JIT

SPM / APMDefine Initial

BaselineConfiguration

SPM / APM/ CSE

ConductFighting Unit

ICRR

TYCOMConduct

DeploymentPlanning Review

Conference

BF CCBPromulgate

FinalBaseline

Configuration

BF CPGQuarterly BFPlanning &SchedulesMeetings

SPM / APMProvide BF CCB

With PostAvailability

Status Report

SPM / APM/ CSE

Fighting Unit Final CSIT

Readiness Review

SPM / APM/ CSE

CommenceShore-Site

CSIT

SEA 05 /SPAWAR 05Battle ForceFinal BGIT

Readiness Review

SEA 05 /SPAWAR 05

CommenceShore-Site

BGIT

TCD

SEA 05 Conduct

Fighting UnitFleet Delivery

Readiness Review

SEA 05 /SPAWAR 05Preliminary

BFICertification

FLTCINCConduct

Battle ForceBGSIT

Readiness Review

FLTCINC

ConductBattle Force

BGSIT

CAPs&LIMs

Design & Development T&E and CertificationDEP

* CINCLANTFLT/CINCPACFLT Instruction 4720.3A of 27 April 00