Open Architecture for naval Combat Direction System · PDF fileOpen Architecture for naval...
Transcript of Open Architecture for naval Combat Direction System · PDF fileOpen Architecture for naval...
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Open Architecture for naval Combat Direction System (CDS)
Denis JANER Chauk-Mean PROUM
System Engineer System Architect
DCNS DCNS
CSDM 2013 06/12/2013
2 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
SOMMAIRE
1. OA French vision and approach
2. OA Standards Registry
3. OA Requirements Registry 1. Naval CS Decomposition
2. Requirements for external interfaces
3. Requirements for architecture
4. OA Qualification Definition
5. Perspectives
3 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA French vision and approach
Strong expectation for modern CDS : � Reduce system total cost of ownership
� Improve system flexibility / 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 existing or fu ture systems
To do so an open architecture must be built on :� A modular architecture approach
� Use of Open standard
4 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA French vision and approach
2. OA Requirements Registry• Naval CDS Decomposition (Op & Sys Views)• Naval CDS Technical Architecture• Specification of OA requirements for external interfaces
2. OA Requirements Registry• Naval CDS Decomposition (Op & Sys Views)• Naval CDS Technical Architecture• Specification of OA requirements for external interfaces
1. OA Standards Registry• State of the Art in Open Architecture• Definition of the OA Standards Registry
1. OA Standards Registry• State of the Art in Open Architecture• Definition of the OA Standards Registry
3. OA Qualification Definition• OA Assessment Process• OA Qualification Process• Specification of OA Qualification Tooling
3. OA Qualification Definition• OA Assessment Process• OA Qualification Process• Specification of OA Qualification Tooling
Standards & Standards & RequirementsRequirements
Registries for CDS Registries for CDS specificationspecification
& qualification& qualification
5 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
State of the Art
... in System Architecting and Engineering
Operational Viewpoint System Viewpoint
• System Function• System Module ...
System Architecture
• (Operational) Capability• Organisation• Operational Activity …
Operational Architecture
• Computing Device• Network Device
Hardware Platform
• OS, Virtual Machine
System of Interest
• HCI & Application Foundations• « Middleware »
Software Foundation
• Application Module• HCI Module• Common Module ...
Technical Viewpoint
Software Application
Software Platform
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, i nteroperability, modularity, extensibility, ...) but without their characterisation in those viewpoi nts.
6 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Technical
ViewpointSys
tem
Viewpo
int
OperationalViewpoint
Innovative approach
Categories are defined by:• goodness : architectural / engineering principles & patterns• openness : standards
7 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
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
8 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Technical
Viewpoint
Syste
mVie
wpoin
t
OperationalViewpoint
OA Standards Registry - Operational Viewpoint Catego ries
1. Insufficiently Formalized Operational Architecture
2. Formalized Operational Architecture • Architecture Framework• DoDAF / MODAF / NAF standard
3. Modular Operational Architecture• command & control vs. reporting
9 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Standards Registry – Principles & Patterns
A.5
IDEF0 Function
callmechanism
outputinput
control
IDEF0
• SOA – Service Oriented Architecture:request / reply or command / control
interaction• DOA – Data Oriented Architecture:
publish / subscribe interaction
CentralizedPlanning & Direction
Commands(Goals / Directives)
DecentralizedExecution
Controls(Veto)
Status / Situation Report
10 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Technical
Viewpoint
Syste
mVie
wpoin
t
OperationalViewpoint
OA Standards Registry - System Viewpoint Categories
1. Insufficiently Formalized System Architecture
2. Formalized System Architecture • Architecture Framework• DoDAF / MODAF / NAF standard
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 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
HCI function with:• elements to be visualized (function input) and controlled
(function output).Gateway – interface function with external system via:• standard interfaces (if available) for conventional features• specific interfaces for advanced features of a given equipment
FunctionExternal Sink
External Source
Data Store
output
input
other input / output
Data Flow Diagram
Standard vs. Modularity
Controller
Model
View
MVC Pattern
OA Standards Registry – Principles & Patterns
12 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Technical
Viewpoint
Syste
mVie
wpoin
t
OperationalViewpoint
OA Standards Registry - Technical Viewpoint Categori es
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 ...
5. Plug and Play Technical Architecture• Service Component• Plug-in = HCI part +
Application part
13 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry
Application of the Standards Registry to a Naval CDS :� Operational / System / Technical
Decomposition
� External Interfaces
Identification and specification of openness supports
Results
� CDS Reference Architecture modelling
� Openness support requirements
Technical Viewpoint
System Viewpoint
Operational Viewpoint
14 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry - Naval CDS DecompositionScope and objectives
Capture future naval Command System architecture with :� Force Level Capabilities built on
- Multi-platform interconnexion- Cooperative situation awareness and engagement
� Decomposition addressing both operational and syste m viewpoints- Based on a DoDAF / NAF sub-set of views
Enable the identification of openness supports espe cially regarding external interfaces
15 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry – External InterfacesApproach overview
Command System
CS InternalFunction
TDL Mngt
SIC 21
Other CSS
L11EqptL11Terminal
L16EqptL16Terminal
L22 Terminal
Gateway(s)Connector(s)
Gateway(s)Connector(s)
Gateway(s)Connector(s)
Gateway(s)Connector(s)
SensorYSensor
X
Weapon Sys.YWeapon Sys.
XGateway(s)
Connector(s)
Distant Command System« Interface Genericity »
pursued regarding sensors and weapon systems of interest« Interface Genericity »
pursued regarding cooperative capability
« Interface Genericity »pursued regarding :
TDL EquipmentsTDL Management
« Interface Genericity »pursued regarding
different connectors developed on French
programs
16 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry – External InterfacesApproach overview
Openness Support are identified based on : � a CS point of view
� on external interfaces and related dataflows defined in CS decomposition
� a set of unitary interfaces on which to applied SOL ID Single Responsibilityand 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 p atterns
� A hierarchy between supports and related unitary in terfaces
� Associated unitary interfaces list
17 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry – External InterfacesApproach overview
For each external 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
18 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry – External Interfaces
Support analysis based on the following sensors and effectors of interest :
- SELESMAR and Scanter 2100 Navigation radars - Scanter 4100 and 6002 2D 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 extend this approach to other types of sensor or weapon
19 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Requirements Registry –Sensors and weapon systems External Interface
x
x
x
x
x
x
x
x
x
x
x
x
SOA Standards
Approve engagement planI_0160
Assign Weapons to threats to engageI_0150x
S_506 Missile Weapon Syst
Give particular engagement and firing ordersI_0180
xMonitor engagement execution before kill assessment
I_0170
Set up engagement and firing policiesI_0140
xMonitor weapon states and modesI_0110
x
S_505 Weapons
Command target acquisitionI_0120xS_504 Fire
Control Syst.
Perform radar measurement requestI_0090
xReceive jamming interference reports from radarI_0070
Manage radar frequency usageI_0020
xS_503 Radars
Control sensor states and modesI_0100
Manage extraction zonesI_0080
xReceive sensor tracksI_0050
xReceive sensor plotsI_0040
x
S_502 Sensors
Perform kill assessment requestI_0130
xReceive digital videoI_0060
Manage emission and firing areasI_0030
Stop/Start own ship emissionsI_0010
x
S_501 Sensors and Weapons
DOAInterfaces (called OA)C/S SOpenness supports
20 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
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
OA Requirements Registry – Technical Architecture
21 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Qualification Definition
Definition of a process to check and qualify the degree o f openness of a CDS in relation to the requirements base line
Two steps process:� Openness degree estimation based on a questionnaire
� Openness degree verification based on IADT evaluation me thods
22 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
OA Qualification Definition - Processes
OA RequirementsRegistry
Openness Assessment Process
OA Reference Architecture
Openness Qualification Process
OA qualificationProcess
OA assessment questionnaire
OA qualificationtools
Specific for a program
Related to Standard Registry
Related to Requirements Registry
OA Categories characterisation
Openness scope characterisation : - operational- functional CDS Definition :
- Operational need - System specification - System Architecture and design
CDS estimated Openness degree
Results from opennessqualification processes
CDS effectiveOpenness degree
23 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Perspectives
Work dissemination / promotion� Standardisation organisation
� Industries
On-going work� Update of standard registry
� Application of standard registry to a wider operati onal and system scope
� Adaptation of the qualification process to operatio nal CMS
24 | 06/12/13 | CSDM 2013 – Open Architecture for naval CDS
©D
CN
S 2
013
-al
l rig
hts
rese
rved
/ tod
oslo
s de
rech
osre
serv
ados
/ tou
s dr
oits
rés
ervé
s
MINISTÈRE DE LA DÉFENSE
Questions ?