IEEE SoSE Conference, 2018

Transcription

1 IEEE SoSE Conference, 2018 Investigating in SoS Taxonomies to improve Systems Engineering Jean-Luc Garnier

2 Outline 2 q q q q q Systems Engineering context and ongoing developments of standards Lesson learned from studies and developments of systems of systems Visions and Proposed taxonomies Challenges and conclusion Questions

3 Thales Group 3 AEROSPACE EACH OF THE MARKETS THAT THALES SERVES PLAYS A VITAL ROLE IN SOCIETY. SPACE GROUND TRANSPORTATION 15 billion euros DEFENCE Employees 64,000 SECURITY Global presence 56 countries

4 Systems Engineering context and ongoing developments of standards

5 Main international references on Systems Engineering 5 ISO/IEC/IEEE (Standard = requirements for any domain) IEEE Will become an ISO reference soon IEEE Will become an ISO reference soon Do not address Systems of Systems significantly INCOSE SE Handbook (Guide = state of the art for any domain)

6 Engineering within Thales 6

7 ISO/IEC JTC1/SC7 Software and systems engineering published standards (as of May 2018) 35 references under development System life cycle processes Software life cycle processes Life cycle process assessment model Quality management

8 On going developments of ISO/IEC/IEEE references 8 After an ISO/IEC JTC1/SC7 Study Group, in 2016: Systems and software engineering -- System of systems considerations in life cycle stages of a system Life cycle activities of a system belonging (planned to belong) to one or more Systems of Systems Guidelines for the utilization of ISO/IEC/IEEE in the context of System of Systems Engineering Systems activities to sustain System of Systems life cycle processes Taxonomy of systems of systems Kinds and types (Taxa) of Systems of Systems Starting with one taxonomy for short-term release Planned extensions to provide other taxonomies more related to Systems Engineering and Operations

9 Lesson learned from studies and developments of systems of systems

10 4 main European Studies addressed Systems of Systems 10 T-Area-SoS: Towards a SoS roadmap Supply-side driven Top-Down approach Systems Engineering US-EU Danse: Designing for adaptability and evolution in SoS Engineering SoS engineering approaches Use cases: Air Traffic Management; Autonomous Ground Transportation; Water Treatment and Supply Road2SoS: Towards a SoS roadmap Sector/demand-side driven Bottom-up approach Consulting industry experts Use cases: Energy, Manufacturing, Crisis Management, Traffic Control Compass Comprehensive Modelling for Advanced Systems of Systems Model-Based tools Use cases: Emergency Response; Audio/Video/Home; Automation Ecosystem; Integrated Modular Avionics.

11 11 Studies and developments of Systems of Systems involving Thales Air Traffic Management (SESAR, OneSky, MARSHALL) NATO Air Command & Control (ACCS Loc1) NATO Networks (ISAF, NGCS, FMN) Federation of French Land Forces (OE SIC, SIA) Federation of French Land Combats Systems (SCORPION) Global Earth Observation (GEOSS/GMES/GMOSAIC) Border Surveillance (Sysfron) Crisis Management (Isycri) Etc.

12 Lesson learned regarding scientific baselines 12 MAIER s criteria Operational independence of the component systems Managerial independence of the component systems Evolutionary development Emergent behavior Geographic distribution (no shared resource) Considering criteria dependencies Evolutionary development is a learning process WRT integration of component systems Emergent behavior is a consequence of operation of component systems Resource segregation is required for independent systems but never totally possible

13 Lesson learned regarding scientific baselines 13 MAIER s criteria Operational independence of the component systems Managerial independence of the component systems Evolutionary development Emergent behavior Geographic distribution (no shared resource) In reality: these criteria are never totally satisfied John Boardman & Brian Sauser System of Systems the meaning of of v Autonomy (independence) vs Belonging to SoS v Geographical distribution VS Connectivity v Diversity & Emergence VS SoS objectives Compromise have to be reached

14 14 Lesson learned: A System of Systems is always more than a set of systems working together Scheduled processes are necessary for overall behavior System Capabilities and Services Constituent systems Adaptors are necessary for alignment Infrastructure Capabilities and Services SoS Infrastructure / Connectivity E.g. See NATO NC3 taxonomy and NISP (unclassified) Major problems Doctrines Semantic Protocols Interfaces E.g. NCOIC definitions and efforts Governance Contracting Management Engineering Deployment Etc.

15 15 Lesson learned: A System of Systems is always more than a set of systems working together Scheduled processes are necessary for overall behavior Doctrines System Capabilities and Services Constituent systems Adaptors are necessary for alignment Infrastructure Capabilities and Services SoS Infrastructure / Connectivity E.g. See NATO NC3 taxonomy and NISP (unclassified)? Adaptation??? Major problems Semantic Protocols Interfaces E.g. NCOIC definitions and efforts Governance Contracting Management Engineering Deployment Etc.

16 Other Lessons learned 16 Development of Systems of systems can begin before or after the development of constituent systems Most of the time, development and operational phases of systems of systems are overlapping Constituent systems can be added / removed during the life cycle of a system of systems Most critical aspects within systems of systems are: Management of life cycles of systems of systems and constituent systems Stability of the capabilities, services and other interaction elements Contracting and collaboration regarding the systems of systems and constituent systems

17 Visions and proposed taxonomies

18 18 Classification from French MOD Ecole SoS Set of Interoperating systems Federated for circonstance Management styles (how to get them?) cooperative collaborative Various types of SoS have to be considered Single [complex] system Directed Objectives (How to reach them?)

19 One of the proposed Taxonomy Purpose of the current ISO/IEC/IEEE development Based on Dahmann & Baldwin, Virtual SoS Acknowledged SoS Collaborative SoS Directed SoS

20 Another taxonomy under preparation: Degree of anticipation of engineering activities 20 Permanent Systems of Systems Existing when the contract is launched Not expected to end Continuous systems engineering activities to fit for purpose Examples: Border surveillance Smart cities Prepared Systems of Systems Contract for Systems Engineering launched before the operational phase Evolution and maintenance done during operation Examples: Air traffic Management New governmental capabilities Episodic Systems of Systems Most of the constituent systems of prepared for typical scenarios A system of systems is deployed on demand Examples: Crisis Management Military reactive responses Phased Systems of Systems Prepared with a number of valid configurations One of more configuration of instantiated when required Examples: Military force protection Search & rescue

21 Another taxonomy under preparation: Degrees of integration and contracting levels 21 Capability Based Systems of Systems Capabilities sustain the overall processes Contracting on constituent systems capabilities Examples: Contracting between agencies and with PMO in large organisations. Service-Based Systems of Systems Service-based interactions and integration Constituent systems are provided as services Examples: IT based configurations Service-oriented contracts Function-based Systems of Systems Each constituent system exposes one or several functions Interactions via function invocation and functional-flows Examples: Application-based configuration classic Systems Engineering approach Resource-based Systems of Systems Interaction and regulation via production and consumption of tangible and intangible resources (including Data) Examples: Smart grids Transportation

22 Comments on these taxonomies 22 A system of Systems can be analyzed through the different taxonomies. E.g. Systems of systems for Air Traffic Management are directed, highly prepared and service-oriented. A system of Systems can be worked through several taxonomy elements along its life cycle. E.g. Prepared Systems of Systems can become permanent. A Capability-based approach has to be thought from the beginning and require a high-level of maturity. I.e. Currently, only large organizations perform capability-based governance activities Resource-based and functional-based systems of systems can evolve towards a Service-oriented approach. E.g. most of the time, this is the case for enterprise transformation.

23 Challenges and Conclusion

24 Challenges identified in development of systems of systems 24 Challenges 1- Contracting of SoS dynamically defined 2- Multi-layer agile Systems Engineering and agile SoS breakdown 3- Dynamic loose coupling and (re)configuration of constituent systems 4- Flexible paradigms for interaction (mix of services, artefacts, events and streams) 5- Behavior (multi-level consistent scheduling + non-functional properties) 6- Multi-level life cycles management 7- Engineering process to meet both bottom-up; top-down; dynamic system insertion/removal; legacy alignment 8- Run-time Management, Integrated logistic support and training on SoS or system built dynamically 9- Modelling and simulation to estimate feasibility, forecast behaviour and provide a reference for management

25 Conclusion 25 Existing systems of systems can now provide facts on developments and operations. Significant challenges are identified related systems of systems. There is a need to bridge Science and Industry practices. Standards are currently under development; but will certainly evolve to take into account scientific improvement and return of experience from Industry. Stronger definitions, including taxonomies of systems of systems, will help improving the subject. Every Systems Engineer should be concerned because any product, service and system may be part of one or more systems of systems.

26 Questions 26 If you are interested in Systems Engineering of SoS: INCOSE SoS Working Group ISO JTC1/SC7 AFIS 3S-AI Technical Committee

27 Annexes for take away

28 SoS criteria apply to products (systems) 28 Do you think the provider master the life cycle of the components? Operating systems Windows, Linux, Android, etc) Devices (disk drive, hardware pug-ins, etc). Call this managerial independence Do you think we master the life cycle of the applicative components? Office tools On-board and off-boards apps. Call this Operational independence SoS approach is a way to better understand problems in products and systems: Emergent behavior Evolutionary development Dependability (segregation resources and functions) Maier s criteria also work for products!

29 SoS approach is a way to better understand multi-systemic composition 29 Product parts can be studied with a systemic approach: Driving system Energy system Propulsion system Breaking system Navigation system Multi-media system Etc. SoS criteria allow refining the operational analysis, WBS, OBS & PBS.

30 SoS approach is a way to better understand multi-systemic composition 30 Example 1: after Jeep hack, Chrysler recalls 1.4 M vehicles for bug fix. Example 2: In a car, battery is a single point of failure: breakdown consequence? Why not having two? Product parts can be studied with a systemic approach: Driving system Energy system Propulsion system Breaking system Navigation system Multi-media system Etc. SoS criteria allow refining the operational analysis, WBS, OBS & PBS.

31 End 31