Transcript שיתוף מידע בחרום הזדמנויות ואתגרים

GORDON CENTER FOR SYSTEMS ENGINEERING
Systems Engineering
Processes for Developing
Unsynchronized System
of Systems
Miri Sitton, Eran Reuveni, Dr. Moshe Weiler
Research Objective
Systems Engineering
methodologies evaluation
for Unsynchronized
Large Scale Integration
of Systems (LSIOS)
2
Jan. 18th , 2012
Applicable Eco-systems
Transportation
Military
3
Health Care
th
Financing
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
Integration Scope
Crossorganization
Engineering
processes
Constitution
&
Agreements
obstacles
Standards
& Common
practices
Unsynchron
ized
Systems
Integration
Cross wide
Coordinated
Architecture
5
Crossorganization
Coordination
Jan 18th, 2012
Project
Management
Example – Defense Forces
Complexity:
• Arrays of systems
• Range of technologies
• Distributed development
• Numerous projects
• End users diversity
‫שיגורים‬
‫שיגורים‬
‫תמונת שיגורים‬
‫שו"ב‬
DL ‫שקנאי‬
‫נ "צ‬
DL ‫שקנאי‬
‫מטרות‬
‫תמונת שיגורים‬
‫שיגורים‬
‫שו"ב‬
‫שו"ב‬
‫תמונת שיגורים‬
‫שיגורים‬
‫תמונת שיגורים‬
‫שיגורים‬
‫שיגורים‬
UL ‫שקנאי‬
‫תמונת שיגורים‬
‫תמונת שיגורים‬
DL ‫שקנאי‬
UL ‫שקנאי‬
‫פלוטים‬
DL ‫רומח‬
‫פלוטים‬
‫תמונת שיגורים‬
The Challenge
To create an integrated
systems engineering
processes for a crosswide coordinated
architecture
Main Issues:
• Partial utilization of
information assets
• Inefficient use of resources
• Unacceptable deployment
pace
• Cross-wide failures
‫פלוטים‬
‫פלוטים‬
‫תמונ"א‬
‫שו"ב‬
‫תמונ"א‬
‫פלוטים‬
UL ‫שקנאי‬
‫שיגורים‬
‫תמונת שיגורים‬
‫נ "צ‬
‫שו"ב‬
‫תמונת שיגורים‬
‫נ "צ‬
DL ‫רומח‬
DL ‫רומח‬
‫נ "צ‬
‫שו"ב‬
‫שו"ב‬
‫נ "צ‬
‫תמונ"א‬
‫פלוטים‬
‫תמונת שיגורים‬
‫שו"ב‬
‫נ "צ‬
‫נ "צ‬
‫תמונ"א‬
‫שו"ב‬
‫שו"ב‬
‫תמונ"א‬
‫תמונת עקבות‬
‫נ "צ‬
‫נדיב‬
C4I Concept
Sensors
Fighters
21th
Network
Centric
Warfare
The
90’s:
TheCentury:
80’s:
Information
Development
sharing
of within
local
systems
domains
Cross-domain interoperability
Control
Command
Intelligence
“Spaghetti” – unmanaged architecture
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. 18th , 2012
Major Issues (cont.)
• Emerging behavior
• Run time cross-wide systems failures
– Upon installation of new versions
– Increased vulnerability
– Information safety events
10
Jan. 18th , 2012
The HKM Framework
Built-in system engineering
done at project level
11
Jan. 18th , 2012
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. 18th , 2012
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. 18th , 2012
Solution Concept
Systems
Operational Engineering
req.
End users
Increasing interoperability
for both operational and
project management by
creating integrated
systems engineering
14
Jan. 18th , 2012
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.
15
Jan. 18th , 2012
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.
16
Jan. 18th , 2012
Projects & Processes
Situation Picture
C4I Building
ProcessAir
Engineering
document
C4I
Strategic
Guidance
:
Project
Project
Projects
A
B
C
D
E
document
document document
document document
Continuous
Enterprise
B document
C4I Process Process
Engineering
Systems Engineering
C4I
Project
Project
Building Intelligence
Picture
C4I
C4I
C4I
Project
Project
Project
C4I
Process Engineering
document
Project
Project
Project
Engineering Engineering Engineering Engineering Engineering
Process A
C4I Process Engineering document
17
Jan. 18th , 2012
18
Processes DB
FOUO
Road Maps
Gaps
theDoc
Identifying
Process Eng.
Architecture
Process Eng. Doc
concept
Operational
Doc
Process Eng.
Doc
Process Eng.
Team
Integrated
Information Strategy
Analysis & Integration of the big picture
...
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
19
Jan. 18th , 2012
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
20
Jan. 18th , 2012
Major Insights
• Team Work between operational and
engineering workgroups is essential
• C4I Engineering key elements:
– Architecture
– Monitoring
– Integration
– Security
– Information Safety
• Reuse of enterprise’s assets
21
Jan. 18th , 2012
1. Definition of
SE Processes
2. Requirements
development
The LSIOS
coordination
4. Project
Architectural
Guidance
5. Mutual
Agreements
Processes
9. Dissemination
of new
capabilities
6. Knowledge
sharing
3. Systems
Architecture
development
7. Cross-Organizations
Coordination &
Communication
8. Systems
Integration
processes
ITS Ecosystem example
Traffic
Control
Complexity:
• Arrays of systems
• Different technologies (Vehicle, Roads)
Public
• Unmanaged
development
Transp.
• End users diversity
The challenge
• Several entrepreneurs
for same
Creating
cross-organizational SE
functional niche
environment to support continues
Transp.&
development, integration
Ministry
dissemination
of
ITS
projects within
Main problems:
coherent
• Non coherent S.E.
culture architectural design, social
& business policies
• Multiple effort on governmental
business interest
Content
Services
points
• Lack of users-value activities
• Unclear cut between Private &
23 Public investments areas
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
24
Jan 18th, 2012
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. 18th , 2012
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. 18th , 2012
C4I as a Culture

Cross Organizational S.E. Processes

Coordinated effort

Common Situational Awareness

Cross Organizational Teams

Information Sharing
27
Jan. 18th , 2012