Systems Engineering Processes for Developing Unsynchronized System of Systems - PowerPoint PPT Presentation

Title: Systems Engineering Processes for Developing Unsynchronized System of Systems


1
Systems Engineering Processes for Developing
Unsynchronized System of Systems
GORDON CENTER FOR SYSTEMS ENGINEERING

• Miri Sitton, Eran Reuveni, Dr. Moshe Weiler

2
Research Objective
Systems Engineering methodologies evaluation for
Unsynchronized Large Scale Integration of
Systems (LSIOS)
3
Applicable Eco-systems
Transportation
Military
Health Care
Financing
4
Unsynchronized systems integration

• Option 1 Systems were developed before
  integration idea

V
V


Option 2 Design one system on top of existing
system
V
V


Option 3 Design systems interoperability before
development

W
V

V
5
Integration Scope
v
Constitution Agreements obstacles
Standards Common practices
Cross-organization Engineering processes
Unsynchronized Systems Integration
W
Cross wide Coordinated Architecture
Project Management
Cross-organization Coordination
6
Example Defense Forces

• Complexity
• Arrays of systems
• Range of technologies
• Distributed development
• Numerous projects
• End users diversity

The Challenge To create an integrated systems
engineering processes for a cross-wide
coordinated architecture

• Main Issues
• Partial utilization of information assets
• Inefficient use of resources
• Unacceptable deployment pace
• Cross-wide failures

????
7
C4I Concept
Sensors
Fighters
21th Century Network Centric Warfare Cross-domain
interoperability
The 80s Development of local systems
The 90s Information sharing within domains
Control
Command
Intelligence
8
Spaghetti unmanaged architecture
9
Major IssuesResult 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

10
Major Issues (cont.)

• Emerging behavior
• Run time cross-wide systems failures
• Upon installation of new versions
• Increased vulnerability
• Information safety events

11
The HKM Framework
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 ?

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

14
Solution Concept
Increasing interoperabilityfor both operational
and project management by creating integrated
systems engineering
15
The Vision Operational View
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.
16
The Vision Technical View
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.
17
Projects Processes
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
Building Air Situation Picture
C4I Process Engineering document
Strategic Guidance Continuous Enterprise
Systems Engineering
Building Intelligence Picture
C4I Process Engineering document
Process B
C4I Process Engineering document
Process A
C4I Process Engineering document
18
Information Strategy
Analysis Integration of the big picture
Processes DB
Road Maps
Identifying the Gaps
...
19
Major Outputs

• 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
20
Engineering Data Base

• 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
21
Major Insights

• Team Work between operational and engineering
  workgroups is essential
• C4I Engineering key elements
• Architecture
• Monitoring
• Integration
• Security
• Information Safety
• Reuse of enterprises assets

22
The LSIOScoordination
4. Project Architectural Guidance
5. Mutual Agreements Processes
2. Requirements development
9. Dissemination of new capabilities
6. Knowledge sharing
3. Systems Architecture development
8. Systems Integration processes
7. Cross-Organizations Coordination
Communication
23
ITS Ecosystem example

• 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

• 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

24
Private Sector Interviews

• Not aware of government road-maps
• No official engineering guidelines
• Unused of residential assets

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

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

27
C4I as a Culture

• Cross Organizational S.E. Processes
• Coordinated effort
• Common Situational Awareness
• Cross Organizational Teams
• Information Sharing