1 / 20

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

Evolution of Open System Architectures in support of T&E for Naval Combat Systems. Ted Mulder, Senior Systems Engineer Robert Mueller, Senior Test Engineer NAVSEA, Port Hueneme, Surface Warfare Center Division Detachment San Diego. NDIA System Engineering Conference, October 20-23, 2003.

berk-neal
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Evolution of Open System Architecturesin support of T&E for Naval Combat Systems Ted Mulder, Senior Systems Engineer Robert Mueller, Senior Test Engineer NAVSEA, Port Hueneme, Surface Warfare Center Division Detachment San Diego NDIA System Engineering Conference, October 20-23, 2003

  2. 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

  3. 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

  4. CSIT/BGIT in the Fleet Response Plan (FRP) Emergency Surge Surge Ready NAVSEA PHD DSD CSIT BGIT CV/CVN Maintenance Basic IDTC Intermediate IDTC Advanced IDTC/ Sustain Deploy • TSTA • FEP • C2X/FBP • Blue Water Cert • JTFEX 3 – 4 months Maximum 6 months Supporting Emergency Surge Is The Focus

  5. CSIT Description • Interface Validation • Functional Operability • Multi Platform Interoperability Test • Single / Multiple Warfare • Functional Stress • Performance Test • Stress and Endurance Integration Phase Low level subsystem tests designed to allow for rapid program fault isolation and correction. Demonstration Phase 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.

  6. 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-proprietaryinterfaces/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)

  7. Analog MIL-STD/Closed COTS/non-OSA OSA CV-63 (ACDS BK0) Test Bed (1996) DDC SATSIM UYK-44 Link-4A ASWM 4.3 Link-11 B C2P UYK-43 TAC-3 Link-16 1553B LK-11 ASWM 4.2 UYK-43 SGS AC UYK-20 LK-4A LK-11 AC A JMCIS TAC-3 48C AUTOID SUN MOD 370 RADAR VIDEO SIM (RVS/VSS) NSSMS SATSIM SEAT 49 NSSMS MK-157/3 ACDS UYK-43 DDC SATSIM UYK-44 SPS-48C UYK-20 NCV SATSIM UYK-20 TAS MK-23 UYK-44 CVNS UYK-44 TAS SATSIM UYK-20 B LLS TPX-42 (V)13 UYK-44 A SDCE SLQ-32(V)4 UYK-19 RBOC SIM LLS CEESIM Combat System Simulation (CSS) UYK-43 NTDS Serial NTDS Parallel Network Simulation Shipboard

  8. SDC EMULATOR CEESIM Shipboard CVN-76 (SSDS MK2) Test Bed UPX UPX-29 FC4 IFF SIM (RVS) Display LAN ASTABS IOC 48 CEP USG2 (VME) BFTT STOW TSSS 49 SPS-48(V)10 CEP WASP (VME & SUN WKS) SPQ-9B Radar Video SIM (2) (Telemechanics RVS) ATM SSDS MK-2 Mod 1 SPS-49A TACTICAL ASDS (RADDS & SPQ-14) SPS-73 LAU IC1 LAU BH1 SPQ-9B DOCTRINE SPS-67 MIL-STD-751B DDS NAV LAN SPS-73 BFTT CTA MLST-3 L4 LLS USQ-118 SPS-67 NAV LAN DIS NTDS-E L-16 CDLMS (Ver. 3.1) DDS DDS CTA SGS /AC (MK-162) L-4A BFTT STOW DIS J-Box TACTICAL NTDS-A L-11 DOCTRINE RS-232 Passive Link Tap RNSSMS 2 LIP, 4 TIP (Ver 6.8) USIM (VME) GCCS-M LAN CV-TSC (Ver 5.1.0.0) GCCS-M (3.1.2.1 p1) RS-232 KCMX TPX-42(V)14 (UYK44 OSM) RAM BLK1 EMULATORS (2 Pentium PC) SPN-43C IFF SIM (RVS) NAV LAN Eio, Zdo & Cqo Digital Computer NAVSSI (BLK 4) STDNAV & WIND SLQ-32A (V)4 R17 (UYK-19) NAV IOC (Partial ICAN) NAVSIM STD Wind Cqo, Eio, Wy, Wha BFTT STOW WSN-7 RLGN IDS-010 WSN-7 / Jul 97 Rev B (OD0 + OD1) OTH GOLD (CTC, POS, DEL) DWMIS GPS SIM BAND 2/3 Satellite RF BEWT Wha Wy COMMON SCENARIO CONTROL ENVIRONMENT (CSCE) BFTT Ver. 3.1 Network Integrated Sim Standalone Sim Analog NTDS Digital MIL-STD/Closed COTS/non-OSA OSA

  9. Test Tools (Data Collection & Analysis) Logic Analyzer LAN Analyzer MILSTD 1397 Parallel Ethernet / FDDI MILSTD 1397 Low Level Serial MILSTD 1553 Serial C & C Sensor GEM {VME, UNIX, POSIX 1003.1b, NFS} Test Tool Network {IEEE 802.3} The Tool CSDR DART {WinNT, NFS} {Linux, NFS} {Linux, NFS}

  10. MIL-STD/Closed COTS/non-OSA OSA Interface & Standards Evolution CV-63 CVN-76 UKY-44/43/20/19 VME (IEEE 1014) Q-70 UKY-19 PC SUN TAC-3/4 PCI PCM (IEEE 1386.1) SCSI (ANSI) Ada95 (ISO 8652) C++ (ISO 14882) WinNT Combat Systems 43 RSS CMS-2Y UNIX (POSIX 1,2) VxWorks (POSIX 1003.1b) CORBA (ISO 19500-2) SUN OS HP-UX TCP (RFC 793, STD #7) UDP (RFC 768, STD #6) RS-232/422 (EIA/TIA) IP (RFC 791, STD #5) Ethernet (IEEE 802.3) FDDI (ANSI X3T9.5) MIL-STD 1553B MIL-STD 1397 MIL-STD 1553B MIL-STD 1397 MIL-STD 751B VME (IEEE 1014) HP-UX UKY-44/43/20/19 PC WinNT DOS PCI PCM SCSI SUN DEC VAX PC DEC UML C++ (ISO 14882) Sim/Stim, T&E Tools UNIX (POSIX 1,2) VxWorks (POSIX 1003.1b) 43 RSS CMS-2Y VAX DOS DIS (IEEE 1278) TCP (RFC 793, STD #7) IP (RFC 791, STD #5) Ethernet (IEEE 802.3) MIL-STD 1553B MIL-STD 1397 MIL-STD 1553B MIL-STD 1397 RS-232 (EIA/TIA)

  11. Naval Combat Systems Progression towards OSA Popular Proprietary Products T&E Tools OPEN SYSTEMS WIDE Market Acceptance Unique Designs, Optimized Performance Consensus Standards (No Products) LOW Standards Base PRIVATE PUBLIC

  12. Future Direction with OSA Middleware • 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) ICAN NAVSSI TPX- 42 CEC RNSSMS SSDS ACDS Combat System CDLMS SLQ-32 GCCS-M CV-TSC CEP WASP SLQ-32 SATSIM CSCE RAM Emulators MLST3 Sim/Stims Middleware Middleware Middleware Middleware Middleware T&E Networks {CORBA, NDDS, Java RMI} Middleware Middleware Middleware Middleware Test Tools DART The Tool CSDR GEM

  13. Scalability Benefits Current System (CPU or I/O max’ed out) New Requirements (software, processing, additional I/O) Solution (add equipment) MIL-STD/Computers Additional $750K UYK-43 COTS OSA Additional $15K (VME chassis & SBC) VME

  14. Hub Interface Affordability MIL-STD Interfaces COTS OSA Interfaces $50 $200 $5000 Ethernet PMC card NTDS VME card

  15. CSIT Benefits from using COTS OSA MIL-STD CSIT MIL-STD Interfaces Required each sub-contractor to program and “re-invent” the required interface protocols, thus consuming test time to integrate and debug. Current CSIT with COTS OSA Reduction in MIL-STD interfaces allows more CSIT time for higher level functionality testing in the application layer.

  16. OSA T&E Tradeoffs Pro Con • 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 • 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

  17. 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

  18. “Jacta alea est” (the die is cast) COTS OSA is here to stay - there’s no turning back!

  19. BACKUP SLIDES

  20. CSIT & BGIT within the D-30 Process DEP D-4 D-3 D-2 D-1 Design & Development T&E and Certification BGSIT (Variable) Assess & Fix JIT Assess & Fix D-18 D-11 D-10 D-7 D-6 Collaborative System Tests (CSTs) Platform CSIT/TSIT (Variable) Assess & Fix Shore BGIT (Variable) Assess & Fix 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 JIT FLTCINC Promulgate BF Composition Message TCD CAPs&LIMs COMPTUEX BGI CERT BRB Promulgate Proposed Baseline Configuration BRB Establish Deployment Baseline Configuration TYCOM Conduct Deployment Planning Review Conference BF CPG Quarterly BF Planning & Schedules Meetings SPM / APM / CSE Fighting Unit Final CSIT Readiness Review SEA 05 / SPAWAR 05 Battle Force Final BGIT Readiness Review SEA 05 Conduct Fighting Unit Fleet Delivery Readiness Review FLTCINC Conduct Battle Force BGSIT Readiness Review BF CCB Establish CCB Charter / Membership SPM / APM / CSE Conduct Fighting Unit ICRR BF CCB Promulgate Final Baseline Configuration SPM / APM Provide BF CCB With Post Availability Status Report SPM / APM / CSE Commence Shore-Site CSIT SEA 05 / SPAWAR 05 Commence Shore-Site BGIT SEA 05 / SPAWAR 05 Preliminary BFI Certification FLTCINC Conduct Battle Force BGSIT SPM / APM Define Initial Baseline Configuration * CINCLANTFLT/CINCPACFLT Instruction 4720.3A of 27 April 00

More Related