1. Systems Engineering Processes for Developing Unsynchronized System of Systems Systems Engineering Processes for Developing Unsynchronized System of Systems Miri Sitton, Eran Reuveni, Dr. Moshe Weiler GORDON CENTER FOR SYSTEMS ENGINEERING

2. Research Objective 2 Jan. 18 th, 2012 Systems Engineering methodologies evaluation for Unsynchronized Large Scale Integration of Systems (LSIOS)

3. Applicable Eco-systems 3 Military Transportation Health Care Financing Jan. 18 th, 2012

4. Unsynchronized systems integration Option 1: Systems were developed before integration idea Option 2: Design one system on top of existing system Option 3: Design systems interoperability before development

5. Integration Scope Jan 18th, 2012 5 Cross wide Coordinated Architecture Standards & Common practices Project Management Constitution & Agreements obstacles Cross- organization Coordination Cross- organization Engineering processes Unsynchron ized Systems Integration

6. שיגורים פלוטים שו"ב פלוטים שו"ב נדיב תמונת שיגורים DL שקנאי UL שקנאי תמונ"א DL שקנאי שו"ב DL רומח נ"צ תמונ"א UL שקנאי שו"ב מטרות שו"ב נ"צ תמונת עקבות תמונת שיגורים DL שקנאי שו"ב DL רומח UL שקנאי נ"צ Complexity: Arrays of systems Range of technologies Distributed development Numerous projects End users diversity Main Issues: Partial utilization of information assets Inefficient use of resources Unacceptable deployment pace Cross-wide failures The Challenge To create an integrated systems engineering processes for a cross- wide coordinated architecture Example – Defense Forces

7. C 4 I Concept Command Intelligence Control Sensors Fighters The 80’s: Development of local systemsThe 90’s: Information sharing within domains 21th Century: Network Centric Warfare Cross-domain interoperability 7 Jan. 18 th, 2012

8. “Spaghetti” – unmanaged architecture

9. Major Issues Result of unmanaged enterprise architecture Lack of information to support cross- enterprise decisions (e.g. IT portfolio investments vs. IT growing budget) Overloading connectivity infrastructure Significant integration time & effort 9 Jan. 18 th, 2012

10. Major Issues (cont.) Emerging behavior Run time cross-wide systems failures –Upon installation of new versions –Increased vulnerability –Information safety events 10 Jan. 18 th, 2012

11. 11 The HKM Framework Jan. 18 th, 2012 Built-in system engineering done at project level

12. State of the Art Product, system and SOS engineering – Built-in Business systems engineering – Enterprise Architecture – ZACHMAN Framework – TOGAF – DODAF Supply Chain Systems Engineering ? 12 Jan. 18 th, 2012

13. Major Gaps Product, system and SOS engineering – Based on a synchronized effort Business systems engineering – Very complicated to implement – Highly abstract and generic – Not driven from specific operational processes – Several static architecture views Supply Chain Systems Engineering – No methods designed 13 Jan. 18 th, 2012

14. Increasing interoperability for both operational and project management by creating integrated systems engineering Solution Concept 14 Systems Engineering Operational req. End users Jan. 18 th, 2012

15. Operational View The Vision Operational View 15 The operational processes are carried out by utilizing all sensors and platforms and by sharing the relevant information and knowledge in the correct extent and time. Jan. 18 th, 2012

16. Technical View The Vision Technical View 16 The systems and infrastructure that support these processes are developed with a wide operational view, with the flexibility required to handle the changing environment and in a framework of defined standards and an over-all systems engineering. Jan. 18 th, 2012

17. Projects & Processes 17 Projects Project A Project B Project C Project D Project E C4I Project Engineering document C4I Project Engineering document C4I Project Engineering document C4I Project Engineering document C4I Project Engineering document Process A Process B Building Intelligence Picture Building Air Situation Picture C4I Process Engineering document Strategic Guidance : Continuous Enterprise Systems Engineering Jan. 18 th, 2012

18. FOUO 18 Processes DB Integrated Team Architecture Road Maps Operational concept Identifying the Gaps Process Eng. Doc Analysis & Integration of the big picture Information Strategy...

19. Major Outputs 19 Common language Accessible engineering data base Declaring operational vision Solving main conflicts within and between operational processes and systems Defining core principles & high level plan Better operational processes in a managed way by Better coordination between unsynchronized systems Jan. 18 th, 2012

20. Engineering Data Base 20 Processes map (today) Operational architecture (today & in vision) Enterprise systems architecture (today & in vision) Plug & Play standards Strategic plan for migration Knowledge Center Flexibility amid changing OP needs Improved ability to cope with cross-wide failures Jan. 18 th, 2012

21. Major Insights Team Work between operational and engineering workgroups is essential C 4 I Engineering key elements: –Architecture –Monitoring –Integration –Security –Information Safety Reuse of enterprise’s assets 21 Jan. 18 th, 2012

22. 6. Knowledge sharing The LSIOS coordination 3. Systems Architecture development 7. Cross-Organizations Coordination & Communication 8. Systems Integration processes 5. Mutual Agreements Processes 1. Definition of SE Processes 2. Requirements development 4. Project Architectural Guidance 9. Dissemination of new capabilities Jan. 18 th, 2012

23. ITS Ecosystem example 23 Traffic Control Public Transp. Content Services Transp. Ministry Main problems: Non coherent S.E. culture Multiple effort on business interest points Lack of users-value activities Unclear cut between Private & Public investments areas Complexity: Arrays of systems Different technologies (Vehicle, Roads) Unmanaged development End users diversity Several entrepreneurs for same functional niche The challenge Creating cross-organizational SE environment to support continues development, integration & dissemination of ITS projects within coherent architectural design, social governmental & business policies

24. Private Sector Interviews Not aware of government road-maps No official engineering guidelines Unused of residential assets 24 Jan 18th, 2012 A growing need for coordination between government and private sectors either For operational processes & engineering guidance

25. Recommendations Define enterprise systems engineering framework based on practical experience of a government enterprise Validate and improve it for business and industrial levels Case study Implementation in Transportation (ITS) industry 25 Jan. 18 th, 2012

26. Summary Information age has created new opportunities and challenges as well These challenges involve in the phenomenon of unsynchronized development of LSIOS - Large Scale Integration of systems This research points out the necessity of new systems engineering processes We propose to develop SE processes, based on methods and practice under governmental enterprise We propose to apply those SE processes on a real world example - ITS Ecosystem 26 Jan. 18 th, 2012

27. C 4 I as a Culture 27  Cross Organizational S.E. Processes  Coordinated effort  Common Situational Awareness  Cross Organizational Teams  Information Sharing Jan. 18 th, 2012