Applying CORBA in a Contemporary Embedded Military Combat System (A Submarine Combat System Perspective)

Transcription

1 Applying CORBA in a Contemporary Embedded Military Combat System (A Submarine Combat System Perspective) OMG's Second Workshop on Real-time And Embedded Distributed Object Computing June 4-7, 2001 Louis DiPalma / Robert Kelly Raytheon Electronic Systems Naval & Maritime Integrated Systems Warfighter Information Center Subsurface Systems Engineering Department / Louis_P_DiPalma@res.raytheon.com/Robert_E_Kelly--Jr@res.raytheon.com 1

2 CORBA: Submarine Combat Control Systems The 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 interfaces on the New Attack (Virginia) Class Submarine. - S Mk 2 Block 1C Sell-Off - Virginia Combat Control Sell-Off - Virginia Dockside Trials - Virginia Initial Operational Capability (IOC) Schedule 1/00 08/01 /04 /07 2

3 Non-Propulsion Electronic Subsystem Interfaces W/ CKT-D IMAGING DAWG NAV RADAR CKT-D DAWG IP LWR PSCU SOF NAV NAV LWR RADAR ITECTURE SUBSYSTEM ATM LAN IFF IC TACS PSCU RADAR IP PSCU CKT-D DAWG LWR SOF/ASDS SOF/ASDS All Subsystems Are Physically Connected to the Architecture ATM LAN. Logical Connections (Established at IPL) Provide Data Pathways Among Subsystems TSS NTDP - Acoustic Intelligence CKT D - Circuit D DAWG - Deployable Array Working Group - Exterior Communication System - Electronic Warfare Support Measures HFCA - High Frequency Chin Array IC - Interior Communications IFF - Identification Friend or Foe LWR - LIDAR Warning Receiver LWWAA - Light Weight Wide Aperture Array ND 3 - Navigation, Data, Distribution and Display - Non-Tatical Data Processing SubSystem - On-Board Team Trainer PSCU - Portable Ship Control Unit - Ship Control System SOF - Special Operations Forces - Submarine Regional Warfare System TACS - Tactical Acoustic Communications System - Total Ship Monitoring SubSystem TSS - Tactical Support Subsystem 3

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 4

5 NSSN Combat Control () Block Diagram IMAG IMAG SCRL SCRL NTDP NTDP LWR LWR Architecture Switches CORBA-based Network Interfaces to other Ship s Systems TSS TSS RLGN RLGN IRIG RADR RADR Combat Control FDDI FDDI NETBR NETBR #3 #3 FDDI #4 #4 FDDI FDDI ASCM ASCM OBS OBS (CWS (CWS S) S) 2) 2) CMD CMD 1) 1) GS-M GS-M GS-M GS-M ASCM ASCM (CWS (CWS P) P) OBS OBS 4) 4) CMD CMD 3) 3) NIPS NIPS I 9 GIG ATM 1 ATM 3 ATM 2 ATM 4 WPNS WPNS CMDWS CMDWS CMDWS CMDWS Port Port STBD STBD CMDWS ADS ADS PWR PWR ADS ADS RTS SVR unit 5100 FDDI SSS Serial WLS WLS AN/CYZ- 10 SSS SVR unit 5110 ISLMM ISLMM RTS PWR PWR ADS ADS #3 #3 ADS ADS #4 #4 TWS HLGSD HLGSD STBD WDATC RS-232 Port WDATC WLCIE Port WPNIF Ethernet Stbd WPNIF TCP = COTS component 5

6 Middleware Was Influenced by Many Factors Virginia 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 POSI (RADE)) 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) 6

7 Infrastructure Profile DII-COE Combat Control System Shared Display Environment Combat Control System Common Operating Environment DII-COE Combat Control System Shared Data Env Operating System & Services Combat Control System Shared Processing Windows, E, Application remote launch, DII-COE RADE Registration & Control Flow, DII-COE, Network Node Manager CORBA Data Servers, RADE Data Tables, RADE Messaging, DII- COE Data Services HP-U, SNMP, NTP, DII-COE, TCP/IP, UDP, LANE HP Processors, FORE ATM, Q-70 Consoles, VME, FWD I 7

8 Sensor Server Contact Server CORBA Ownship Weapons Server Server CORBA/RADE Command I/O RADE Data Gathering Virginia FCS Software Profile CORBA External Interfaces RADE Internal Data Services & Run-time Management OBT Network Mgr RADE ADCAP F/G TMA Foreground Missile F/G RADE Snapshot Launcher F/G OBT Foreground Sys Mgr F/G RADE ADCAP B/G Real organizations have to use multiple middlewares, Andrew Watson TMA Background RADE Launcher B/G Missile B/G RADE HP-U, SNMP, NTP,... Support Server (HP) HP-U, SNMP, NTP,... Display Console (HP) HP, SNMP, NTP,... Real Time Server (HP) 8

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 9

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 10

11 Goal System Model for Combat System Common Shared Data Exchange Mechanisms Common Coordinated Run-Time Environment Common But Architecturally Isolated Tactical Control and Weapon Control Functions Combat System Shared Display Environment Mission Data Handling Offboard Contact Distribution External Messaging Sensor Perf. Prediction Contact Management Data Fusion Tactical Picture Generation Vulnerability Assessment Tactical Scene Evaluation Tactical Planning Platform Employment Aids Weapons Employment Aids Weapons Order Generation DII-COE Non-Real Time Non-Real Time OS & Services, SNMP, NTP Information System Common Operating Environment Information System Shared Data Environment Information System Shared Processing Real Time Real Time OS & Services, SNMP, IRIG W C 11

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 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 12

13 Contact Information Louis P. DiPalma Robert E Kelly Robert_E_Kelly--Jr@res.raytheon.com Raytheon Electronic Systems Company Naval & Maritime Integrated Systems SubSurface Warfighter Information Center Systems Engineering Department Mail Stop West Main Road Portsmouth, RI