Open Architecture for naval Combat Direction System (CDS)

Transcription

1 Open Architecture for naval Combat Direction System (CDS) Denis JANER System Engineer DCNS CSDM /12/2013 Chauk-Mean PROUM System Architect DCNS

2 SOMMAIRE 1. OA French vision and approach 2. OA Standards Registry 3. OA Requirements Registry 2 06/12/13 CSDM 2013 Open Architecture for naval CDS 1. Naval CS Decomposition 2. Requirements for eternal interfaces 3. Requirements for architecture 4. OA Qualification Definition 5. Perspectives

3 OA French vision and approach Strong epectation for modern CDS : Reduce system total cost of ownership Improve system fleibility / evolutivity to address operational needs evolutions and technology changes - To maintain operational advantage and capability through whole system life cycle - To improve system maintainability Improve system interoperability with eisting or future systems To do so an open architecture must be built on : A modular architecture approach Use of Open standard 3 06/12/13 CSDM 2013 Open Architecture for naval CDS

4 OA French vision and approach 1. OA Standards Registry State of of the Art in in Open Architecture Definition of of the OA Standards Registry 2. OA Requirements Registry Naval CDS Decomposition (Op & Sys Views) Naval CDS Technical Architecture Specification of of OA requirements for eternal interfaces 4 06/12/13 CSDM 2013 Open Architecture for naval CDS Standards & Requirements Registries for CDS specification & qualification 3. OA Qualification Definition OA Assessment Process OA Qualification Process Specification of of OA Qualification Tooling

5 State of the Art... in System Architecting and Engineering System of Interest Operational Operational Architecture (Operational) Capability Organisation Operational Activity System Function System Module... System System Architecture Technical Software Application Application Module HCI Module Common Module... Software Foundation HCI & Application Foundations «Middleware» Software Platform OS, Virtual Machine Hardware Platform 5 06/12/13 CSDM 2013 Open Architecture for naval CDS Computing Device Network Device Yet, current practices in Open Architecture do not address those different viewpoints: Some approaches only address a single viewpoint (e.g. US Navy OACE) Other approaches define qualities (e.g. openness, interoperability, modularity, etensibility,...) but without their characterisation in those viewpoints.

6 System Innovative approach 6 06/12/13 CSDM 2013 Open Architecture for naval CDS Operational Categories are defined by: goodness : architectural / engineering principles & patterns openness : standards Technical

7 OA Standards Registry OA Standards Registry identifies : Recommended principles, patterns, standards and technologies According to : - Their maturity (established, emerging) - Their diffusion (low, average, large) - The type of standard (de facto, de jure, open) - Supporting entity or Standardisation Organisation Registry addressing : Operational, System and Technical viewpoints Different abstraction layers Both HCI and Application Server aspects Categories are defined by: Modularity : architectural / engineering principles & patterns Openness : standards 7 06/12/13 CSDM 2013 Open Architecture for naval CDS

8 OA Standards Registry - Operational Categories Operational 1. Insufficiently Formalized Operational Architecture 2. Formalized Operational Architecture Architecture Framework DoDAF / MODAF / NAF standard 3. Modular Operational Architecture command & control vs. reporting Technical 8 06/12/13 CSDM 2013 Open Architecture for naval CDS System

9 OA Standards Registry Principles & Patterns Commands (Goals / Directives) Centralized Planning & Direction Status / Situation Report Controls (Veto) SOA Service Oriented Architecture: request / reply or command / control interaction DOA Data Oriented Architecture: publish / subscribe interaction control IDEF0 Decentralized Eecution 9 06/12/13 CSDM 2013 Open Architecture for naval CDS input IDEF0 Function output A.5 mechanism call

10 OA Standards Registry - System Categories Operational 1. Insufficiently Formalized System Architecture 2. Formalized System Architecture Architecture Framework DoDAF / MODAF / NAF standard Technical 10 06/12/13 CSDM 2013 Open Architecture for naval CDS System 3. Modular Computing System Architecture SOA vs. DOA computing function vs. data store (MVC Pattern) 4. Full Modular System Architecture computing vs. HCI vs. gateway function (MVC Pattern) standard interfaces

11 OA Standards Registry Principles & Patterns Controller Eternal Source input Model Function output Eternal Sink View other input / output Data Store MVC Pattern Data Flow Diagram HCI function with: elements to be visualized (function input) and controlled (function output). Gateway interface function with eternal system via: standard interfaces (if available) for conventional features specific interfaces for advanced features of a given equipment 11 06/12/13 CSDM 2013 Open Architecture for naval CDS Standard vs. Modularity

12 OA Standards Registry - Technical Categories Technical Operational 12 06/12/13 CSDM 2013 Open Architecture for naval CDS System 1. Legacy Technical Architecture (~ OACE Hardware Adapter) 2. Layered Technical Architecture (~ OACE Interface) 3. Open Technical Architecture (~ OACE Standards) 4. Modular Technical Architecture (~ OACE Common Functions) Dependency Inversion MVC Pattern MDA Component AOP Plug and Play Technical Architecture Service Component Plug-in = HCI part + Application part

13 OA Requirements Registry Application of the Standards Registry to a Naval CDS : Operational / System / Technical Decomposition Eternal Interfaces Operational Identification and specification of openness supports Results CDS Reference Architecture modelling Openness support requirements 13 06/12/13 CSDM 2013 Open Architecture for naval CDS System Technical

14 OA Requirements Registry - Naval CDS Decomposition Scope and objectives Capture future naval Command System architecture with : Force Level Capabilities built on - Multi-platform interconneion - Cooperative situation awareness and engagement Decomposition addressing both operational and system viewpoints - Based on a DoDAF / NAF sub-set of views Enable the identification of openness supports especially regarding eternal interfaces 14 06/12/13 CSDM 2013 Open Architecture for naval CDS

15 OA Requirements Registry Eternal Interfaces Approach overview Sensor Y Sensor X Weapon Sys. Y Weapon Sys. X Command System Gateway(s) Connector(s) Gateway(s) Connector(s) CS Internal Function TDL Mngt Gateway(s) Connector(s) Gateway(s) Connector(s) Gateway(s) Connector(s) L11 Eqpt L11 Terminal L16 Eqpt L16 Terminal L22 Terminal SIC 21 «Interface Genericity» pursued regarding sensors and weapon «Interface Genericity» systems of interest pursued regarding cooperative capability 15 06/12/13 CSDM 2013 Open Architecture for naval CDS Distant Command System «Interface Genericity» pursued regarding : TDL Equipments TDL Management Other CSS «Interface Genericity» pursued regarding different connectors developed on French programs

16 OA Requirements Registry Eternal Interfaces Approach overview Openness Support are identified based on : a CS point of view on eternal interfaces and related dataflows defined in CS decomposition a set of unitary interfaces on which to applied SOLID Single Responsibility and Interface Segregation principles : - via Common / Specific Segregation pattern : Separation of the part (generic) common to different user/supplier modules from the parts specific to a given user/supplier module. - via Domain Partitioning pattern : Separation of interfaces corresponding to different domains (different functional domains, or functional domain vs quality of service). Each openness support is characterized by : Requirements specifying applicable principles and patterns A hierarchy between supports and related unitary interfaces Associated unitary interfaces list 16 06/12/13 CSDM 2013 Open Architecture for naval CDS

17 OA Requirements Registry Eternal Interfaces Approach overview For each eternal interface : Unitary interfaces are defined based on SOA and DOA patterns : - A CS point of view and related openness support - SOA : to distinguish C&C request and C&C reply interactions - DOA : as a native read and write segregation relying on data publication, data subscription and data query interaction Each unitary interface is characterised by : - Requirements specifying applicable principles, patterns and open standards - Static and dynamic interface definition 17 06/12/13 CSDM 2013 Open Architecture for naval CDS

18 OA Requirements Registry Eternal Interfaces Support analysis based on the following sensors and effectors of interest : - SELESMAR and Scanter 2100 Navigation radars - Scanter 4100 and D Surv. Radar - SMART-S and LRR-S1850 3D Surv. Radar - EMPAR and Herakles MFR - ASTER 15/30 and VL-MICA Anti-air missile weapon systems - MM-40 block 2&3 Anti-ship missile weapon systems Openness supports hierarchy retained : Sensors and Weapons - Sensors Radars Fire Control Systems - Weapons Missile Weapon Systems Work in progress to etend this approach to other types of sensor or weapon 18 06/12/13 CSDM 2013 Open Architecture for naval CDS

19 OA Requirements Registry Sensors and weapon systems Eternal Interface Openness supports C/S S Interfaces (called OA) DOA SOA Standards S_501 Sensors and Weapons I_0010 I_0030 I_0060 Stop/Start own ship emissions Manage emission and firing areas Receive digital video I_0130 Perform kill assessment request S_502 Sensors I_0040 I_0050 I_0080 Receive sensor plots Receive sensor tracks Manage etraction zones I_0100 Control sensor states and modes I_0020 Manage radar frequency usage S_503 Radars I_0070 Receive jamming interference reports from radar S_504 Fire Control Syst. S_505 Weapons S_506 Missile Weapon Syst I_0150 I_ /12/13 CSDM 2013 Open Architecture for naval CDS I_0090 I_0120 I_0110 I_0140 I_0170 I_0180 Perform radar measurement request Command target acquisition Monitor weapon states and modes Set up engagement and firing policies Monitor engagement eecution before kill assessment Give particular engagement and firing orders Assign Weapons to threats to engage Approve engagement plan

20 OA Requirements Registry Technical Architecture Overall technical structure definition Identification of openness supports Possible aggregation Technical architecture modelling : Address the different abstraction layers Identifies : - Applicative modules typologies (application, gateway, repository, HCI) - Traceability between system functions and applicative modules - Typical technical decomposition for each applicative module - Dependency between technical modules Requirements for principles/patterns and standards to apply on openness supports 20 06/12/13 CSDM 2013 Open Architecture for naval CDS

21 OA Qualification Definition Definition of a process to check and qualify the degree of openness of a CDS in relation to the requirements baseline Two steps process: Openness degree estimation based on a questionnaire Openness degree verification based on IADT evaluation methods 21 06/12/13 CSDM 2013 Open Architecture for naval CDS

22 OA Qualification Definition - Processes OA Categories characterisation Openness scope characterisation : - operational - functional CDS Definition : - Operational need - System specification - System Architecture and design OA assessment questionnaire OA Reference Architecture Openness Assessment Process Specific for a program Related to Standard Registry Related to Requirements Registry Results from openness qualification processes CDS estimated Openness degree OA Requirements Registry OA qualification Process OA qualification tools 22 06/12/13 CSDM 2013 Open Architecture for naval CDS Openness Qualification Process CDS effective Openness degree

23 Perspectives Work dissemination / promotion Standardisation organisation Industries On-going work Update of standard registry Application of standard registry to a wider operational and system scope Adaptation of the qualification process to operational CMS 23 06/12/13 CSDM 2013 Open Architecture for naval CDS

24 Questions? 24 06/12/13 CSDM 2013 Open Architecture for naval CDS

25