Principles of Future Architecture for Naval Combat Management Systems

1. Principles of Future Architecture for Naval CMS Systems Principles of Future Architecture for Naval Combat Management Systems Jacek Skowronek, Ph.D. e-mail: jacek.skowronek@nl.thalesgroup.com Innovation Manager System Architecture

2. Principles of Future Architecture for Naval CMS Systems Content • Context of Naval Combat Management Systems • Operational, technical and industrial challenges for system architectures • Principles of future CMS architecture: • segmentation • information backbone • model-driven engineering • components, connectors and containers • Future activities

3. Principles of Future Architecture for Naval CMS Systems Combat System Weapons Combat Management System Command System Command Support System Sensors Context: Naval CMS systems

4. Operational: changes in the nature of conflicts: littoral asymmetric coalition-based (so complex interoperability problems) reduced manning: “do more with less”: less manning, multi-mission platforms but more information at the same time due to littoral context, so “information overload” Network-Centric Warfare Technical: distribution, so need for coordination and control: hierarchic or autonomous (agents) non-functional requirements shape the architecture, not the functional ones focus on models, not on source code: model-driven engineering and code generation build software as “pluggable” components: component-based development Industrial: consortium-based development multi-site development technology cycles much shorter than product cycles Principles of Future Architecture for Naval CMS Systems Challenges for CMS architectures

5. Principles of Future Architecture for Naval CMS Systems Architecture principles • Segmentation to separate different solutions for different problems • Information backbone to abstract from the details of infrastructure • Model-driven engineering to make it stable and interoperable • Components, connectors to make it reusable and and containers efficient in development

6. Principles of Future Architecture for Naval CMS Systems JCTN(CEC) JDN (LINK) JPN (MSG) shooter grid awareness grid planning grid QR-SA QR-R&I SeM Scheduler ... Assign- ments & Cues The allocation of capabilities to segments is just an example Mission data MCCIS NRT-COMS Mission Prep. Doctr.Prep. ... Office Entertainment SA Tact. Link TE R&I Dec. Support ... “warfighting function” “awareness function” “planning function” Eng. status Statusdata Interfaces Interfaces Interfaces CE CC CSS Segmentation

7. Principles of Future Architecture for Naval CMS Systems Reusability, Portability, Extensibility, Operational flexibility, Integrity JCTN(CEC) JDN (LINK) JPN (MSG) Performance (e-to-e and throughput) Safety Dependability Equipment-Interoperability CE Performance (throughput), Tactical-Interoperability Dependability CC Security, Tactical-Interoperability, COTS Interoperability CSS Pre-R&I SeM Scheduler Assign- ments & Cues Mission data MCCS NRT-COMS Mission Prep. Doctr.Prep. Office Entertainment SA Tact. Link TE R&I Dec. Support Statusdata Eng. status Interfaces Interfaces Interfaces ObservationsEngagements ObjectsDecisions DocumentsArchiving

8. Principles of Future Architecture for Naval CMS Systems This slide has been deliberately left blank Diapositive intentionnellement blanche

9. Principles of Future Architecture for Naval CMS Systems W L S G R H C A B T B H G K J I F D E C L G’ Q I J D U P F E K realtime information broker V X Y N M Z P’ M O P N S Y T R Q INFRASTRUCTURE as INFORMATION BACKBONE Traditional client/server Information model D’ A • Spontaneous: , Self-healing: • Redundant & Replicated: , • Shared and guaranteed backbone quality: (peer-to-Peer QoS: realtime, reliability, persistency) Z Z D’ G’ P’

10. Principles of Future Architecture for Naval CMS Systems Notes to Slide 8 5/3 - added shade to data-model ‘bubble’

11. Principles of Future Architecture for Naval CMS Systems Model-driven architecture style • The new strategic direction for CORBA and OMG • Formal platform-independent UML models (PIMs) for different domains (also military) • Rigorous roundtrip mapping to platform-specific models (PSMs) and then to code (through UML profile and generation): • CORBA • Java/Jini • .NET • …

12. Principles of Future Architecture for Naval CMS Systems IDelivery Warehouse Supplier Component-based architecture styles

13. Principles of Future Architecture for Naval CMS Systems Addressing the challenges • Segmentation: • inherently fitting with the concept of NCW grids • helping in smart integration of COTS and legacy • helps formation of consortia • Information backbone: • inherently suitable for realisation of distributed control principles • spontaneous joining and leaving ability fits well within NCW vision • Model-driven engineering: • helps to cope with “brittleness” of code • helps address non-functionals early in the process • useful in consortia and multi-site development • Components, connectors and containers: • separation of functional (in component) and non-functional concerns (in container) • formal definition of interfaces in connectors helps in multi-site development

14. Principles of Future Architecture for Naval CMS Systems Future research • System state in segmented system • Addressing system-wide properties in segmented system • Agents and objects • Modelling non-functionals in platform-independent manner • Automatic translation of non-functionals between platform-independent and platform-specific

15. Principles of Future Architecture for Naval CMS Systems Contributions • Identification of architectural challenges standing before future Naval CMS systems • Four architectural principles addressing those challenges: • segmentation • information backbone • model-driven engineering • components, connectors and containers • Current activities taking place to make this a reality in new generations of Thales CMS products