Successful Engineering of a System

Systems Engineering Introduction

1
What are we going to talk about

• Re-introduction of Systems

2
2
Systems Re-visits

Systems Definition: .. An integrated set of

elements, subsystems, or assemblies that
accomplish a defined objective.

• These elements include products

(hardware, software, firmware),
processes, people, information,
techniques, facilities, services, and
other support elements.

Systems has Architecture

• Architecture is the structure of SOI

components, their relationships, and
WSOI
the principles and guidelines
governing their design evolution over
time

3
Systems is Contextual, Therefore Systems in Systems Engineering are

Type Of Systems Systems in SE

Open or Closed System • Systems Engineering is applied to

open, mostly physical system that
• Does the systems interact with its are human made/modified from
environment largely unprecedented elements
Natural/Man-Made/Man-Modified

• Natural Systems are not made by

human

Physical or Conceptual Systems

• Physical are tangible

Precedented/Unprecedented Systems

• Precedented are system that

developed before

4
 Systems engineering is a profession, a process, and a perspective, that
can be defined as:

Systems Engineering is an interdisciplinary approach and means to enable the

realization of successful systems.

It focuses on defining customer needs and required functionality early in the development
cycle, documenting requirements, then proceeding with design synthesis and system
validation while considering the complete problem:
• Operations • Cost & Schedule
• Performance • Training & Support
• Test • Disposal
• Manufacturing

Systems Engineering integrates all the disciplines and specialty groups into a team effort
forming a structured development process that proceeds from concept to production to
operation. Systems Engineering considers both the business and the technical needs of
all customers with the goal of providing a quality product that meets the user needs.

5
5
Systems Re-visits

Systems Definition: .. An integrated set of • Systems has Hierarchy

elements, subsystems, or assemblies that
accomplish a defined objective. • Systems has Systems (Systems
of Systems)
• These elements include products
(hardware, software, firmware), • System has Life-Cycle
processes, people, information,
• System has Context
techniques, facilities, services, and
other support elements.

Systems has Architecture

• Architecture is the structure of

components, their relationships, and
the principles and guidelines
governing their design evolution over
time

6
Systems has Hierarchy

Work Breakdown Structure ..

deliverable oriented
hierarchical decomposition of
the work to be executed by
the project team.

Bill of Material … product

structure (sometimes bill of
material, BOM or associated
list) is a list of the raw
materials, sub-assemblies,
intermediate assemblies, sub-
components, parts and the
quantities of each needed to
manufacture an end product.

7
7
Systems Hierarchy s just the first step into SOS

8
8
Ant then the hierarchy will translate to Systems of Systems

A SoS is an integration of a
finite number of constituent
systems which are
independent and
operatable, and which are
networked together for a
period of time to achieve a
certain higher goal.
(Jamshidi 2009)

These mean SoS are

contextual.

Issues raised in SoS:

Interoperability, Architecting
SoS – Defining which
Emergent behavior can be viewed as a Systems is part of the SoS
consequence of the interactions and
relationships between system elements rather
than the behavior of individual elements.

9
9
Systems of Systems

• “Systems-of-Systems” (SoS) are defined as an interoperating collection of

component systems that produce results unachievable by the individual systems
alone.

• Challenges with development of SoS:

– System elements operate independently
– System elements have different life cycles
– The initial requirements are likely to be ambiguous
– Complexity is a major issue
– Management can overshadow engineering
– Fuzzy boundaries cause confusion
– SoS engineering is never finished

10
 Systems has Context (Concepts of Operations)
A concept of operations (abbreviated CONOPS, CONOPs, or ConOps) is a document
describing the characteristics of a proposed system from the viewpoint of an individual who
will use that system. It is used to communicate the quantitative and qualitative system
characteristics to all stakeholders.

11
Operational Definitions Sets SOS

12
12
Functional Definitions Sets SOS

13
13
Systems have Life-Cycle
Systems Life Cycle

Conceptual Development Production Utilization Support Retirement

Stage Stage Stage Stage Stage Stage

1. How do you want the systems to operate

and maintain will generate Concepts of Operations
• We called this “projections”

2. Requirements & Architecture

Projected to how you want to
verify and validate

3. Detailed Design
Projected to how you will integrate
The Components, test then and verified the
Integration

4. Implementation, building the systems and its components, based on detailed design
5. Integration, Test, and Verification, reflecting to the detailed design
6. Systems Verification and Validation, reflecting to requirements and architecture
7. Operations and Maintenance, reflecting to concepts of operations

*one way because once you moved to the next stage of vee model, it is generally unwise to return back, since it
would cause “overs” (over-runs and over-cost)

14
To avoid confusion, in order to differentiate the systems that we are
working on is called Systems of Interest (SoI), and the supporting
systems called Enabling Systems
System of Interest is the
system that we have choose
to engineers or re-engineers
within certain context from the
systems of systems (SOS)

Enabling Systems are systems

that facilitate the life cycle
activities of Systems Interest

15
15
Why has Systems Engineering Emerged as A Distinct Discipline?

• The term itself was not

formally used, nor was the
importance of the concepts
recognized, until after World
War II.

• Complexity increased orders

of magnitude with the
creation of coupled mecho-
digital systems, especially in
defense (P-51 Mustang
versus the Trident in 10
years)

• Creation of systems of
systems, with users,
acquisition, training, service,
support, etc.

• Explosions = N!/2(N-2)!

16
16
Analisa vs Analisa Sistem

Analisa Analisa Sistem

• Proses pencarian permasalahan untuk • Proses pencarian permasalahan

mencari komponen yang rusak mencakup tambahan hubungan interaktif
antar komponen disesuaikan dengan
• Satu tingkatan, masalah dibatasi hanya tujuan dan secara endogenus
pada satu tingkatan, dalam satu cara
pandang/ perspektif, dalam jangka waktu • Multi dimensi , Multi tingkatan/skala, multi
saat ini atau sangat terbatas, dalam aktor, dipertimbangkan multi perspektif,,
jangka ruang yang terbatas baik dimensi waktu (dulu-saat ini- akan
datang), maupun geografis (disini atau
disana)

17
 Life Cycle Human
Portfolio Quality Infrastructure Knowledge
Model Resource
Agreement Processes

Management Management Management Management

Management Management

Acquisition
Organizational Project-Enabled Processes

Project
Risk Information Quality Project Decision Configuration
Assessment Measurement
Supply Management Management Assurance Planning Management Management
& Control

Technical Management Processes

2. Stakeholder 5. 6.
1. Business 3. System 4. 7.
Needs and Design System
or Mission Requirement Architectur Implementatio
Technical Processes

Requirements Definition Analysis

Analysis s Analysis al Design n Process
Definition Process Process
Process Process Process
Process

12.
8. 9. 10. 11. 13. 14.
Operatio
Integration Verification Transition Validation Maintenanc Disposal
n
Process Process Process Process e Process Process
Process

Systems Life Cycle

Conceptual Development Production Utilization Support Retirement

Stage Stage Stage Stage Stage Stage

Systems Perspectives and Thinking in Sytems

18
Overviews of Original Processes based on ISO/IEC 15288

Systems Engineering Process Activity Focus When it is most Useful

7.0 Enabling System Engineering - -
7.1 Decision Management Trade studies and project reviews Through Life
7.2 Requirements Management System requirements Through Life
7.3 Risk and Management Recognizing opportunities and risks Through Life
8.0 Systems Engineering Support - -
8.1 Acquisition and Supply Procurement business relationships Through Life
8.2 Architectural Design Technical analysis Development Stage
8.3 Configuration Management Control of changes through life Through Life
8.4 Information Management Project archives and info exchange Through Life
8.5 Investment Management Estimation and analysis of costs Through Life
8.6 Project Planning Managing technical activities Through Life
8.7 Quality Management Product and process assessment Through Life
8.8 Resource Management Skills and resource availability Development Stage
8.9 Validation User concurrence – correct system Through Life
8.10 Verification Requirements met – system correct Through Life
9.0 Specialty Engineering Activities - -
9.1 Design for Acquisition Logistics Integrated logistics support solutions Development Stage
9.2 Electromagnetic Compatibility Electro-magnetic protections Development Stage
9.3 Environmental Impacts Care for the biosphere and humans Development Stage
9.4 Human Factors Human capabilities and well-being Development Stage
9.5 Mass Properties Physical characteristics of the system Development Stage
9.6 Modeling, Simulation, & Prototype Early validation and testing Development Stage
9.7 Safety/Health Hazards Minimum risk to users Through Life
9.8 Sustainment Engineering Continued use of system Through Life
9.9 Training Need Analysis Basis for training requirements Development Stage

19
 Translating this SyE-BOK to Courses
taking to account that some already provided by IEUI Department

Managed by SEMS Lab Provided by IE Department

*Agent Based Modeling, *Policy Systems Modeling,
*Introduction to Health Systems Engineering , *Introduction to Software
Specialty

Systems Engineering , *Introduction to Service Systems Engineering,

*Human Factors , *Chemical Process, *Plant and
*Introduction to Energy Systems Engineering, *Simulation Gaming for
Facility Layout , *Decision Making Process,
Learning *Sustainability Aspects of Systems Engineering, *Advanced
*Supply Chain and Logistics, *Engineering
System Dynamics, *Politic of Policy Analysis, *Systems Integration &
Ethics and Legal Considerations, *Management
Testing, *Optimization by Nature , *Systems Design and Architecture,
of Technology
*Advanced Linear Programming, *Advanced Integer Programming,
*Stochastic Programming, *Nonlinear Programming, *Queuing Theory,
*Revenue and Price Optimization

*Finance, Economics and Cost Estimation,

*Decision, Uncertainty and Risk Management , *Systems Dynamics, *Quality Assurance and Control System ,
*Operation Excellence Management, *Knowledge Management, *Legal *Project Management, *Organization Design
Core

and Contractual Agreement, *Introduction to Policy Analysis, & Analysis, *Information Management,
*Research Methods & Data Analysis, *Object Oriented Programming *Product Design, *Process Design,
Fundamental, *Systems Modeling (Discrete Systems Modeling), *Maintenance Management , *Safety & Health
Industrial Simulation, *Heuristics and Meta-Heuristics Optimization Management.
Foundatio

*Probability and Statistics, *Engineering

*Thinking and Systems Thinking , *Systems Engineering
Economy, *Operations Research, *Computer
n

Fundamentals, *Systems Engineering Management (Life Cycle

Fundamentals (Java Programming).
Management)
*Engineering Drawing etc

20
 Three Generic Cohort of SE Implementation

Product Systems Engineering Service Systems Engineering Enterprise Systems Engineering

Product systems engineering Service System Engineering is Enterprise systems

(PSE) is at the core of the new a multidisciplinary approach to engineering (ESE) is the
product development process manage and design value co- application of systems
(NPDP) that is needed to creation of a service system. It engineering principles,
successfully develop and extends the holistic view of a concepts, and methods to the
deploy products into different system to a customer-centric, planning, design,
market segments. A market end-to-end view of service improvement, and operation of
can be consumer based (e.g., system design. an enterprise.
private enterprises or general
consumers) or it can be public Primary Method is service It is worth noting that an
(not-for-profit). Public markets systems development process enterprise is not equivalent to
address the strategic needs of (SSDP): 1 Service an "organization”
a country or region, such as Strategy/Concept, 2
military, healthcare, Requirements Analysis and
educational, transportation, Engineering, 3 Systems
and energy needs. Design/Development, 4
Service Integration,
The SoS consist of Product, Verification & Validation, 5
Product System, Product Service
Realization System and Transition/Deployment, 6
Product Sustainment System Service
Operations/Continuous
Service Improvement (CSI)

21