Applying CORBA in Military Combat System_Presentation-FINAL

Applying CORBA in a Contemporary Embedded Military Combat System

(A Submarine Combat System Perspective)

OMG's Second Workshop onReal-time And Embedded Distributed Object Computing

June 4-7, 2001

Louis DiPalma / Robert KellyRaytheon Electronic Systems

Naval & Maritime Integrated SystemsWarfighter Information Center Subsurface Systems Engineering Department

401.842.5592 / [email protected]/[email protected]

1

Naval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated SystemsNaval and Maritime Integrated Systems

2


OMG WORKSHOP ON REAL-TIME And EMBEDDED DISTRIBUTED OBJECT COMPUTING

CORBA: Submarine Combat Control SystemsThe US Navy has fully and openly embraced CORBA. CORBA has been endorsed throughout the entire US Navy Submarine fleet. This infusion of CORBA is not limited to future system upgrades, but also includes several potential backfit platforms.

CORBA has been designated as the technology of choice for integrating the many subsystems onboard the submarine platform. CORBA is being employed on virtually all the inter-subsystem interfaceson the New Attack (Virginia) Class Submarine.

- CCS Mk 2 Block 1C Sell-Off- Virginia Combat Control Sell-Off

1/00 08/01 /07

Schedule

- Virginia Initial Operational Capability (IOC)

- Virginia Dockside Trials

/04

3



ARCHITECTURE SUBSYSTEM ATM LAN

PSCU

NDDDARCHSCS

RADAR

ARCHOBTT

SCS

PHOTONICSNDDDOBTTPSCUSRWSSONARTSDTSMSCKT-DDAWGLWR

LWR

SRWS

ACINTARCHCCNDDDOBTTNTDPSSCSSONARTSD

TACS

TSS

ARCHCCECSNDDDNTDPSSCSSRWSSONARTSMS

TSMS

ARCHNDDDNTDPSCSSONARTSD

DAWG

PHOTONICS

ACINT

ARCH

NDDDSCSSONARSRWS

NDDD

NDDDCCARCH

IFF

ACINTCCECSESMPHOTONICSNDDDNTDPSOBTTRADARSONARSCSSRWS

CC

ARCHECSESMPHOTONICSNDDDNTDPSOBTTSONARSCSSRWSTSDNAV

CKT-D ECS

ARCHCCPHOTONICSNDDDOBTTSCSNTDPSTSD

ESM

ARCHCCPHOTONICSNDDDOBTTSCS

IC

IMAGING

ACINTARCHCCECSESMNDDDNTDPSOBTTSCS

ARCHCKT-DDAWGICCPLWRPSCUSOFTSDTSMSNAV

ARCHCCECSPHOTONICSNDDDOBTTSRWSTSDTSMS

OBTT

ARCHCCECSESMPHOTONICSNDDDNTDPSRADARSONARSCSSRWS

SONAR

ACINTARCHCCNDDDOBTTSCSSRWSTSDTSMS

NDDD

ARCH W/ NDDD NAV

NDDDCC

NTDPS

SOF/ASDS

NDDDARCHSCS

ACINTARCHCCECSESMICCP

SOF/ASDS

All Subsystems Are Physically Connected to the Architecture ATM LAN.Logical Connections (Established at IPL) Provide Data Pathways Among Subsystems

Non-Propulsion Electronic Subsystem Interfaces

ACINT - Acoustic Intelligence CKT D - Circuit DDAWG - Deployable Array Working GroupECS - Exterior Communication SystemESM - Electronic Warfare Support MeasuresHFCA - High Frequency Chin ArrayIC - Interior CommunicationsIFF - Identification Friend or FoeLWR - LIDAR Warning ReceiverLWWAA - Light Weight Wide Aperture ArrayND3 - Navigation, Data, Distribution and DisplayNTDPS - Non-Tatical Data Processing SubSystemOBTT - On-Board Team TrainerPSCU - Portable Ship Control UnitSCS - Ship Control SystemSOF - Special Operations ForcesSRWS - Submarine Regional Warfare SystemTACS - Tactical Acoustic Communications SystemTSMS - Total Ship Monitoring SubSystemTSS - Tactical Support Subsystem

4



CORBA Data Organization

• Data shared between systems was organized into CORBA and Non-CORBA Groups

• CORBA data was grouped by like objects– Orientation is shared data v.s. supplier-consumer view– Most involved subsystem assigned as lead to define interface– Interface designed as superset of all user needs– Modules logically organized within an interface

• Interfaces employ Push/Push event channel – Supports shared data view with multiple suppliers and consumers– Naval Undersea Warfare Center OMG CORBA compliant

implementation event channel developed due to lack of COTS• Redundant CORBA Name Servers custom designed and

implemented for availability– Name Servers monitor each other as hot spares

5



NSSN Combat Control (CC) Block Diagram

ATM 2

ATM 3

ATM 4

ATM 1

CCSVRunit 5100

FDDI

CCSVRunit 5110

Serial

FDDIFDDI FDDI

FDDI

TCP

TWS

Ethernet

StbdWPNIF

PortWPNIF

RS-232

WLCIE

STBDWDATC

PortWDATC

CCSSS#1

CCRTS#2

CCSSS#2

CCPWR#1

CCPWR#1

CCPWR#2

CCPWR#2

WLSWLS

AN/CYZ-10

CCRTS#1

CCADS#3

CCADS#3

CCADS#1

CCADS#1

CCADS#4

CCADS#4

CCADS#2

CCADS#2

CMDWS

CMDWSSTBD

CMDWSSTBD

CMDWSPort

CMDWSPort

HLGSDHLGSD

ATWCS#2

ATWCS#2

ATWCS#4

ATWCS#4

ATWCS#3

ATWCS#3

ATWCS#1

ATWCS#1

NETBRNETBR

CCOBS#1

(ADS 2)

CCOBS#1

(ADS 2)

CCOBS#2

(ADS 4)

CCOBS#2

(ADS 4)

CCCMD#2

(ADS 3)

CCCMD#2

(ADS 3)

ASCM#2

(CWS P)

ASCM#2

(CWS P)

CCCMD#1

(ADS 1)

CCCMD#1

(ADS 1)

ASCM#1

(CWS S)

ASCM#1

(CWS S)GCCS-M

#2GCCS-M

#2GCCS-M

#1GCCS-M

#1NIPSNIPS 9 GIG

SCSI

WPNSWPNS

SCRLSCRLIMAGIMAG ESMESM OBTTOBTT

TSSTSS

TSMSTSMS NTDPNTDP

SONARSONAR ACINTACINT SRWSSRWS ARCHARCH RLGNRLGNNDDDNDDD

RADRRADR

Architecture

Switches

LWRLWR

ECSECS

FDDI

IRIG

CORBA-based Network Interfaces toother Ship’s Systems

ISLMMISLMM

CombatControl

= COTS component

6



CC Middleware Was Influenced by Many Factors

• Virginia CC development was based on extensive reuse• Weapon Interfaces Have Unique Demands

– real-time constraints– resource limitations and resource requirements

• Existing In-house middleware for distributed systems (Realtime Distributed Environment for POSIX (RADEX))

• Compatibility with other SoS subsystems, particularly Architecture subsystem

• DII COE Components• Maturity level of CORBA products and standards when the

system architecture was established• Benefits of CORBA in a heterogeneous distributed

environment (anticipating ever-present interface issues)

7



Infrastructure Profile

Combat Control System Shared Processing

⇐ X Windows, CDE, Application remote launch, DII-COE

⇐ RADEX Registration & Control Flow, DII-COE, Network Node Manager

⇐ CORBA Data Servers, RADEX Data Tables, RADEX Messaging, DII-COE Data Services

⇐ HP-UX, SNMP, NTP, DII-COE, TCP/IP, UDP, LANE

⇐ HP Processors, FORE ATM, Q-70 Consoles, VME, FWD SCSI

Operating System & Services

DII-COE Combat Control System Shared Data Env

Combat Control System Shared Display Environment

Combat Control System Common Operating EnvironmentDII-COE

8



Support Server (HP)

HP-UX, SNMP, NTP,...

CORBA RADEX RADEX

Wea

pons

Ser

ver

Sens

or S

erve

r

Com

man

d I/O

Ow

nshi

p Se

rver

Con

tact

Ser

ver

CO

RB

A/R

ADEX

Net

wor

k M

gr

OB

T

Dat

a G

athe

ring

Display Console (HP)

HP-UX, SNMP, NTP,...

RADEXRADEX

CD

Snap

shot

X

CDM

issi

le F

/G

X

CD

TMA

Fore

grou

nd

X

CD

ADC

AP F

/G

X

CD

Sys

Mgr

F/G

X

CD

OB

T Fo

regr

ound

X

CDLa

unch

er F

/G

X

• CORBA External Interfaces• RADEX Internal Data Services & Run-time Management

Real Time Server (HP)

HP, SNMP, NTP,...

RADEX RADEX

Mis

sile

B/G

TMA

Bac

kgro

und

ADC

AP B

/G

Laun

cher

B/G

Virginia FCS Software Profile

“Real organizations have to use multiple middlewares,” Andrew Watson

9



Lessons Learned• ORB Selection• Common to all embedded COTS . . .

– Plan vendor support, monitor vendor directions, plan version migrations

– Not all ORBs or ORB vendors are equal– Not all ORBs are equally inter-operable

• Due diligence required in crafting IDL– Per object methods (accessor functions)– Aggregate (batch) methods for performance efficiency

• CORBA Services, especially Event and Naming Service, are critical to the systems we build

– Events act primarily as notifications to minimize throughput• Size of executables are a concern

10



Lessons Learned (cont.)

• Develop robust interface early with initialization, error recovery leading application integration

• Create auxiliary functions once and share across classes• Learning Curve - Training and Mentoring needs

11



Information System Shared ProcessingReal Time OS & Services, SNMP, IRIGNon-Real Time OS & Services, SNMP, NTP

DII-COEInformation System Common Operating Environment

Mis

sion

Dat

aH

andl

ing

Offb

oard

Con

tact

Dis

trib

utio

n

Exte

rnal

Mes

sagi

ng

Sens

or P

erf.

Pred

ictio

n

Con

tact

Man

agem

ent

Dat

aFu

sion

Tact

ical

Pic

ture

Gen

erat

ion

Vuln

erab

ility

Asse

ssm

ent

Tact

ical

Sce

neEv

alua

tion

Tact

ical

Plan

ning

Plat

form

Empl

oym

ent A

ids

Wea

pons

Empl

oym

ent A

ids

Wea

pons

Ord

er G

ener

atio

n

Combat System Shared Display Environment

• Common Shared Data Exchange Mechanisms• Common Coordinated Run-Time Environment• Common But Architecturally Isolated Tactical Control

and Weapon Control Functions

W C

Information System Shared Data Environment RealTime

Non-RealTime

ECS

Goal System Model for Combat System

12



Next Steps

• Mk 2 Combat Control System Open System Enhancement ECP 004 takes the next evolutionary step

– Migrating to more current ORB, selected within constraints of system of systems

• Long term goal is to move to common middleware for CC internal and external communications

• RT-CORBA– Real-time performance– QoS guarantees

• Fault Tolerance– Common COTS based solution/ dynamic reconfiguration– Avoid re-implementing unique system solutions– Investigating use of FT-CORBA

13



Contact Information

Louis P. [email protected]

401.842.5592

Robert E [email protected]

401.842.2853

Raytheon Electronic Systems CompanyNaval & Maritime Integrated Systems

SubSurface Warfighter Information Center Systems Engineering Department

Mail Stop 1421847 West Main RoadPortsmouth, RI 02871

Applying CORBA in Military Combat System_Presentation-FINAL

Documents

Transcript of Applying CORBA in Military Combat System_Presentation-FINAL