New Perceptions in Coping with System of Systems (SoS)

Transcription

1 New Perceptions in Coping with System of Systems (SoS) Dr. Daniel Leshem Corporate Chief Scientist Rafael Armament Development Authority Ltd., Haifa, Israel New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 1

2 New Perceptions in Coping with SoS SoS Definitions OSoS Characterizations, Parameters and Types Rationale for Defense Industry Entry in OSoS Development OSoSE Versus Systems Engineering OSoSE Recommendations OSoS Management Highlights New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 2

3 How to Define SoS? Family of Systems? Enterprise SoS?? Complex System? or Super System? For example: one fighter aircraft incorporates many systems, but SoS refers to entire squadron! To be clear, I propose the term Operational SoS (OSoS ) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 3

4 Operational SoS Definition Ensemble of platforms, armaments, equipment, C 4 I, personnel, training and maintenance facilities. These synergistically work together to achieve set of tasks within a defined mission, according to operational methodologies driven by combat doctrine New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 4

5 OSoS Example FCS (Future Combat System) OSoS includes Platforms Weapons C 4 I2SR Doctrine Training facilities Fighting Units Soldiers Maintenance ILS (Integrated Logistic Support) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 5

6 FCS OSoS - Concept of Operations New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 6

7 OSoS Characterizations Trained personnel are integral part of OSoS OSoS building blocks can be distributed at remote locations and interconnected by communication networks C 4 I systems are critical glue for combining separate systems into OSoS Coordinated operation of all OSoS building blocks is key factor in effective and efficient mission accomplishment OSoS concept, architecture and capabilities are being consolidated in parallel with evolutionary development of its operational methodology New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 7

8 OSoS Types Dedicated vs Virtual OSoS Preplanned vs gradually-developed developed OSoS New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 8

9 Rationale for Defense Industry Entry into OSoS Development Defense market customers new attitude is to deal with OSoS - defining requirements, evaluating and ordering OSoS - and not separate systems Many advantages for main contractor Increasing reputation as leading defense industry Enabling direct interaction with customers including End Users Improving opportunity to incorporate own advanced technologies Improving own capabilities when coping with OSoS Systems Engineering (OSoSE( OSoSE) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 9

10 OSoSE vs Systems Engineering Starting OSoS Program Requirements consolidation and management Functional Analysis Interfaces definition Modeling and Simulation Defining and executing V&V Evolutionary behavior of OSoS Architectural analysis of OSoS Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 10

11 OSoSE vs Systems Engineering Starting OSoS Program Requirements consolidation and management Functional Very Analysis long processes together with Interfaces interested definition parties and customers to to refine Modeling concept and simulation Defining Early and consolidation of executing V&V of Strategic Partners Considerations of of using state-of-the-art or or Evolutionary behavior of OSoS just Foreseen Technologies Architectural Starting Analysis interim developments of OSoS to to reduce Deep risks involvement and/or to to of verify interested new concept parties (usually the proven concepts become constraint in in the full scale program) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 11

12 OSoSE vs Systems Engineering Starting OSoS Program Requirements consolidation and management Functional Analysis Very high level of of complexity in in consolidating Interfaces definition requirements for new OSoS: Modeling, many customers simulation with with different interests, Defining evolutionary and nature executing of of development, V&V and and necessity for for interoperability Evolutionary behavior of OSoS Requirements develop and are updated during entire Architectural OSoS life Analysis cycle of OSoS Connectivity Deep involvement and interfaces of interested with neighboring parties OSoS under development Advanced software tool is is needed to to handle the huge requirements scope (the original + derived ones) and their complex linkages New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 12

13 OSoSE vs Systems Engineering Starting an OSoS Program Requirements consolidation and management Functional Analysis Interfaces definition Modeling, simulation Defining and Processes, executing tasks V&V and scenarios in in OSoS are complex, involving many components Evolutionary behavior of OSoS These create interactive constraints and Architectural mutual Analysis effects of OSoS Deep involvement Conclusion: of interested Methodical parties Functional Analysis is is critical for architectural consolidation of of OSoS New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 13

14 OSoSE vs Systems Engineering Systems Engineering Starting OSoS Program defines mechanical, Requirements consolidation electrical, and management computational - Functional Analysis - connectivity and MMI interfaces Interfaces definition OSoS provides upper Modeling & Simulation layer of of different types of of Defining and executing V&V scenarios and tasks: Evolutionary behavior of Physical: OSoS different Architectural Analysis of configurations OSoS and Deep involvement of interested Logical: parties different tasks Result: Different interface requirements for various applications New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 14

15 OSoSE vs Systems Engineering Starting an OSoS Program Not possible to to produce Requirements consolidation complete and management model of of Functional Analysis OSoSto to simulate all all its its functionality as: Interfaces definition Infinite cases of of Modeling & Simulation possible events and Defining and executing V&V scenarios included Evolutionary behavior of OSoS Very difficult to to Architectural Analysis of OSoS simulate human behavior Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 15

16 OSoSE vs Systems Engineering Starting OSoS Program These situations Requirements consolidation require: and management Functional Analysis Using many models to to Interfaces definition cover all all hierarchy Modeling & Simulation levels Simulating tasks Defining and executing V&V management with Evolutionary behavior of OSoS Humans-in-the-Loop Architectural Analysis of OSoS Developing special Deep involvement of interested simulation parties concepts and tools to to cope with OSoS Example: GES4 New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 16

17 OSoSE vs Systems Engineering Starting an Complex OSoS Program V&V procedures: analysis, simulations, integrations and tests Requirements Verification consolidation of of the design and in in management stages, Functional combined Analysis with risk analysis and plans Interfaces definition Modeling & Simulation Defining and executing V&V Evolutionary behavior of OSoS Architectural Analysis of OSoS Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 17

18 OSoSE vs Systems Engineering Starting an OSoS Program Complex V&V procedures: analysis, Requirements consolidation simulations, integrations and tests management Verification of of the design in in stages, Functional Analysis Interfaces definition Modeling & Simulation Defining and executing V&V Evolutionary Interfaces behavior verification of OSoS at at all all levels, Architectural scenarios Analysis and tasks of OSoS Deep involvement of interested parties Complex V&V procedures: analysis, combined with risk analysis and plans OSoS validation in in series of of high-level preplanned test scenarios New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 18

19 OSoSE vs Systems Engineering OSoS Life Cycle Concept: taking into account existing systems, future development and stages Starting life cycle an OSoS and life Program time Requirements Adaptive development: consolidation considering and management unexpected changes in in directions as as result of of operational Functional Analysis lessens learned by by early fielded models Interfaces Development definition environments: as as teams, Modeling subcontractors, & Simulation knowledge, experts, tools Defining are and changing! executing V&V Evolutionary behavior of OSoS Architectural Analysis of OSoS Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 19

20 OSoSE vs Systems Engineering Definition: Model description (physical, functional, operational, software etc) at at OSoS Starting an OSoS Program upper level in in its its relevant environment, considering its its Requirements evolutionary consolidation and open system and natures management Functional Architectural Analysis of of OSoS require very high level of in Interfaces of professionalism definition in following issues: Methodology Modeling Tools& Simulation Defining Training and executing V&V Evolutionary Experts behavior of OSoS Architectural Analysis of OSoS parties Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 20

21 OSoSE vs Systems Engineering Range of of interested parties usually with contradictory interests! -- including main Starting contractor an OSoS and Program subcontractors, customers Requirements taking part in consolidation in development and and management end users OSoS military aspects require close Functional Analysis involvement of of customer as as early as as Interfaces possible definition with professional teams who can Modeling make & difficult Simulation decisions! Defining Close and cooperation executing with V&V customer and mutual obligations are essential for Evolutionary behavior of successful building of OSoS! Architectural Analysis of OSoS Deep involvement of interested parties New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 21

22 OSoSE Recommendations Methodology New special upper level of Systems Engineering Process to be defined (V model recommended) Interoperability and MOSA (Modular Open System Approach) in OSoS to be adopted Professionalism of OSoS Architecture and function of Chief Architect (compared to Chief Systems Engineer) to be cultivated New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 22

23 OSoSE Recommendations Organization Chief Architect, responsible for all aspects of OSoS Engineering, directly subordinate to Program Manager/Management Working with Integrated SE Team (ISET) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 23

24 Integrated SE Team for OSoS (ISET) System B System A Requirements Team Operational Aspects Team Team Integrations, Simulations & Test Team Functional Analysis Team OSoS Architect Concurrent Engineering Team OSoS OSoS Architecture Team Team System C System D Joint Joint Customer Team Team System E System G System F New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 24

25 OSoSE Recommendations Tools Central database Creating and preserving logical connections with full traceability On-line coordination between all development bodies Automatic documents production Fast transformation from UC analysis to working software implementation Massive supportability Examples: Core, Requisite Pro, Clear Case, Rhapsody, Doors New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 25

26 OSoSE Recommendations Critical technology disciplines and infrastructure required for OSoSE Information (collecting, processing, distribution) Intelligence (collecting, decoding, data fusion, processing, distribution) Sensing (electro- optical, acoustics, RF, ) C 4 I2SR Interdisciplinary and multidisciplinary know-how such as: Image processing with navigation Communication with missile guidance, control and navigation Intelligence with signal processing, pattern recognition; and more New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 26

27 OSoS Managements Highlights Coping with OSoS provides main contractor with many advantages and benefits - and it s s worth it! Spiral development of OSoS ensures use of most updated technologies and capabilities available while dealing with enemy emergent threats, in process that allows step-by by-step fielding New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 27

28 OSoS Management Highlights Recommended to manage OSoS architecture and systems engineering processes through Chief Architect and Integrated SE Team Use specific gates and checklists as necessary management tool in building OSoS Common methodologies, tools and Infrastructure for all parties and bodies involved in development of OSoS is key to success! New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 28

29 New Perceptions in Coping with OSoS Summary OSoS (Operational SoS) ) is proposed as common term to which Defense industry can refer New level of complexity - not just more regular Systems Engineering it requires development of new concepts, approach and methodologies It s s a challenge! It s s worth it! New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 29

30 New Perceptions in Coping with System of Systems Dr. Daniel Leshem Corporate Chief Scientist Rafael Armament Development Authority Ltd., Israel New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 30

31 New Perceptions in Coping with System of Systems Speaker background: Daniel Leshem B.Sc. (1969, Cum Laude), and M.Sc. (1976) in Aeronautical Engineering, Technion -Israel Institute of Technology. Ph.D. in Aeronautics & Astronautics, 1985, Stanford University, California, USA. (Thesis: Composite Barriers and Corner Conditions in Differential Games ) Rafael Armament Development Authority Ltd., Israel: Since 1969: group leader, systems engineer, chief engineer, manager of Antitank missile directorate, VP for R&D, VP Chief Systems Engineer, Corporate Chief Scientist GE Medical Systems, Israel (NM): VP for R&D ( ) Prize: Israel National Defense Prize (1984) New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 31

32 C4I2SR Command Control, Communication, Computers Intelligence, Information Surveillance Reconnaissance New Perceptions in Coping with SoS - D. Leshem Rafael Proprietary 32