Curso Systems Engineering WKS - 0 Conceito

Systems Engineering
no DIP
Jun 2015
Wellington Martins
VTE/DTE/GSW
FUNDAMENTOS
O QUE NÃO É SYSTEMS ENGINEERING
O QUE É UM SISTEMA
QUAL O OBJETIVO DO SISTEMA?
Esta informação é propriedade da Embraer e não pode ser usada ou reproduzida sem autorização por escrito.
Processo de Desenvolver Sistemas
Systems Engineering não é Engenharia de Sistemas (...)
Para nosso contexto: É um processo de Desenvolvimento de produto

Processo de Desenvolver Sistemas
Systems Engineering não é DIP (Desenvolvimento Integrado de Produto)
Integrated Product Development Team (IPDT)
Sequential A multidisciplinary group of people who are collectively
Engineering responsible for delivering a defined product.
INCOSE HANDBOOK V4 (p 199)
Integrated Process and Product Development (IPPD)

Concurrent The process of using IPDTs to simultaneously develop the
Design for a product or systems and the methods for
Engineering manufacturing a product
INCOSE HANDBOOK V4 (p199)
Systems Engineering (Em uma de suas perspectivas)

é um processo que faz a Gestão Técnica do DIP
Systems engineering is a multidisciplinary

approach to develop balanced system solutions
in response to diverse stakeholder needs.
Systems engineering includes the application of

both management and technical processes to
achieve this balance and mitigate risks that can
impact the success of the project.
PERSPECTIVAS
Systems Engineering pode ser “apresentado” na perspectiva de:
Systems Engineering Management
GDP (BR) / Chief Engineer (U.S))
Systems Integrator (Systems Engineer)
Systems Architect (“Technology”)
Research Development Team
Mas não pode se executado somente em uma perspectiva!
COMPOSIÇÃO COMPLETA DE UM SISTEMA
Conceito - O produto é um Sistema
Avião Comercial
Alta complexidade tecnológica:

Funcionalidades Integradas
Complexidade dos cenários de operação
Caça

Sistemas de Defesa
Alta complexidade extrema
(Aerodinâmica, construtiva, materiais)
Sistemas de Sistemas
Quantidade relativamente alta de: complexos
Funcionalidades integradas Tecnologia

Inúmeros subsistemas componentes Funcionalidades
que interagem funcionalmente Cenários complexos
SW
Conceito - O produto é um Sistema
Prótese
Materiais e tribologia
Sem componentes
Pás Eólicas Rolamento
Alta complexidade tecnológica: Alta complexidade
(Aerodinâmica e construtiva) tecnológica:
Quantidade relativamente Materiais e
pequena de: tribologia
Funcionalidades Complexidade
Subsistemas componentes que construtiva
interagem funcionalmente
QUAL VALOR O SISTEMA ENTREGA?
Systems Engineering vai além da Proposta de Valor

Proposta de valor: Declaração dos valores essenciais ao mercado (Diferencial)
Adiciona-se a essa declaração o ambiente operacional onde o produto irá

operar e qualquer outra consideração operacional especial, numa perspectiva do
ciclo de vida.
Adiciona-se o entendimento entre o desenvolvedor (produto) e os stakeholders

presentes em todo o ciclo de vida
QUAL O OBJETIVO DO SISTEMA?
Operational Scenario
is sequence of steps taken by known types of user, active stakeholders to achieve a GOAL
Operational Environment
is composed by Operational Scenario plus Environment and Stakeholders
Function
is an action that compose the step in a Operational Scenario
Now we can write (compose) a REQUIREMENT !!

Requirement is a formal statement of need
COMPOSIÇÃO – OBJETIVO SISTEMA
VALUE
STAKEHOLDER
AMBIENTE CICLO
OPERACIONAL DE VIDA
FUNDAMENTOS
PRINCIPAL CARACTERÍSTICA DO SISTEMA:
HIERAQUIA…
Conceito - Definição de Sistema
Hierarchy
Why is it Important?
Basic ability to understand and
to deal with complex systems
It is a way of thinking
that gives us the freedom to
identify root causes of problems
and see new opportunities.
“
First of all, what level of the system are you going to map?
How sure are you that you are mapping at the right level, or will you
need to map the system at several levels?
Where are we drawing the boundaries of the system? Do we need to
make the boundary of the system under consideration wider?”
Exemplos:
Kerr, David (2012-07-27). An Introductory Guide to Systems Thinking (Kindle Locations 435-438).
eBookIt.com. Kindle Edition.
Conceito - Definição Sistema
O PENSAMENTO SISTÊMICO
Hierarchical Relationships for Systems of Interest
Aircraft
System of Interest
System A System B
System of Interest
System of Interest
Subsystem A1 Subsystem A2
Subsytem A1.1 Subsystem A1.2
An Aircraft with Enabling Systems
Enabling Systems Systems of Interest
Sistema
Sub(Sistema) 1 Sub(Sistema) 2
ENABLING SYSTEM
Relação:
PMBOK® Guide
Lean
Systems Engineering
PERSPECTIVAS
Systems
Engineer
(Chief E.)
Systems Specialty
Architect Engineer
SEMP – Systems Engineering Management Plan Compliance
Guidelines
1 ABBREVIATIONS AND ACRONYMS
2 INTRODUCTION
3 PART 1 – TECHNICAL PROJECT PLANNING AND CONTROL 4 PART 2 – SYSTEMS ENGINEERING PROCESS
3.1 Responsibility and Authority 4.1 Top Level Requirements Analysis and Definition
3.2 Reference Documents and Standards 4.2 Functional Analysis
3.3 Program Risk Analysis 4.3 Requirements Allocation
3.4 Work Breakdown Structure 4.4 Systems Requirements, Allocation/Analysis and Verification and
Validation
3.5 System Specification
4.5 Design Analysis Cycle
3.6 Technical Design Review
4.6 Risk Analysis and Assessment
3.7 Technical Interchange Meetings
4.7 Logistics
3.8 Technical Design Verification/Validation
4.8 Documentation control
3.9 Requirements Verification Matrix
4.9 Simulations and Other Tools
3.10 Verification/Validation Testing
4.10 Qualification and Acceptance Process
3.11 Document Control
3.12 Change Control
5 PART 3 - ENGINEERING SPECIALTY INTEGRATION
3.13 Technical Baselines
5.1 Engineering Program Integration
3.14 Program Schedule and Milestones
5.2 Specialty Engineering
3.15 Technical Performance Management
5.3 Integrated Validation Plan
3.16 Other Plans and Controls
Conceito - PMI & Lean & Systems Engineering
Systems engineering é um dos pilares do
desenvolvimento de sistemas complexos Abordagem dos Principais Players
Técnico Negócios Melhoria

Planejamento Continua DoD
•Maior Comprador do Mundo
•Impõe Systems Engineering como
Systems PMI - PMBok Lean filosofia de integração aos seus projetos
Engineering
Abordagem de fornecedores
Project Management Institute (PMI)
• PMI is the world’s leading not-for-profit association for the
Project management profession.
• Project Management Body of Knowledge (PMBOK® Guide)
lexicon for discussing, writing, and applying project management.
• Project Management Professional (PMP ®) Certification
Project Management Institute Knowledge Areas
Integration Management / Scope Management / Time Management

Cost Management / Quality Management / Human Resources Management
Communications Management / Risk Management
Procurement Management
The Standard for Program Management - PMI
The Standard for Program Management - PMI
Systems Engineering relationship with Project
Management
PROJECT MANAGEMENT
TECHNICAL
MANAGEMENT
SYSTEMS ENGINEERING
the PMBOK ® Guide does not directly address the technical dimension nor
associated designs. Scope management practices may/may not be applicable to the
technical dimension.
Ensure highest possible

degree of applicability and
practicality
key challenges
Management of Large-Scale
Engineering Programs: DOD
Example
• Total cost growth:

$296 billion
• Average schedule overrun:

22 months
• Similar situation in other

industries
Sources: GAO 06-368, Bloomberg, GAO 10-374T
1. Reactive Program Execution

2. Lack of stability, clarity and completeness of
requirements
3. Insufficient alignment and coordination of the extended enterprise
4. Value stream not optimized throughout the entire enterprise
5. Unclear roles, responsibilities and accountability
6. Insufficient team skills, unproductive behavior and culture
7. Insufficient Program Planning
8. Improper metrics, metric systems and KPIs
9. Lack of proactive management of program uncertainties and risks
10. Poor program acquisition and contracting practices
How bad are unstable requirements?
Increase of R&D Cost in DoD Programs
90%
80%
70%
60%
50%
Source: GAO-11-233SP
40%
30%
20%
10%
0%
Decreased, deferred or New or enhanced Stable requirements
deleted requirements requirements
Domain Representation of “the Example: New aircraft development

stakeholder problem”
Increased flight economy by 20% /

Lean Thinking Value
passenger
Program Global market leadership in hub-to-hub
Benefit
Management connections
Project
Deliverable Deliver engine for $16 million on May 10
Management
The new engine must have over 300kN take-
off thrust, weigh less than 6 tons, must be
Systems
Requirements manufacturable on existing assembly lines,
Engineering
cost not more than $15 million to produce
and FAA certified May 9.
PM - Systems Engineering (Issues)
Risk
Risks are tracked thru the life of the project

The PM is responsible for the project risk, the SE is responsible for the technical
risk
Risks Requiring Mitigation
Staff Turnover
Replacement project Management
Change of Scope
Incomplete Requirements review
Failed design Review
No requirement Tracing
No CONOPS document
Contract option declined
Corporate Management
The SE Manager is a buffer between management (including project) and

technical operations
Prevent the PM or other corporate level stakeholder from directly working with
the technical staff
Translate technical issues to non-technical terms decision make
Control technical assignments
PM - Systems Engineering
Project Management
SE Management is an interface to project management
Ensure that the project schedule aligns with the actual work
Participate in technical discussions with the clients (s) resulting in work product
or execution decisions
Keep the PM informed of technical issues
Keep the staff informed of any impacting decisions or discussions
Subcontractors
Subcontractors should have all the regulatory and systems requirements

necessary,
SE Management should ensure that the subcontractors is completely
knowledgeable about their deliverable, including schedule, requirements,
execution and integration,
It is important to track subcontractor progress, so that there are no delivery (or
lack thereof) surprises,
Establishing and managing a warranty (…)
The warranty is considered a non-functional requirement that impacts the

architecture, design, installation, and operation
Very much dependent on reliability
May result in significant losses if not considered during architecture/design
Systems Engineering em
Sistemas de Defesa
Conceito - Systems Engineering em Sistemas de Defesa
The Defense Acquisition University (DAU) is a Department of Defense (DoD) training

establishment authorized by Congress under the Defense Acquisition Workforce
Improvement Act of 1990 and established by DoD Directive 5000.57 on October 22,
1991, that trains the approximately 150,000 military and civilian DoD personnel in
the fields of acquisition, technology, and logistics (AT&L).
PART 1 – TECHNICAL PROJECT PLANNING AND CONTROL
“Responsibility and Authority
While the Project Manager has full responsibility and

accountability for the execution of the project, in order to
meet these requirements it is clear that it will take support
from the Systems Engineer. This section will delineate the
responsibilities of the Systems Engineer to effectively plan,
support, control, and deliver products to meet the
requirements.”
Kansa Univ. SE Course
Systems Engineering em
Sistemas Civis
Conceito - Systems Engineering em Sistemas Civis
Course Overview Module
Space Systems Engineering, version 1.0
Sistemas de Sistemas
“Systems of Systems”
SoS
Conceito – System of Systems em Sistemas de Defesa
THE BATTLEFIELD
Conceito – System of Systems em Sistemas Civis
System C System D
System B
System E
Funcionalidades
System A Independentes
Opera separado
Sistema A, B, C
System of D, E tem
Systems funcionalidades
Funcionalidades Independentes do
SoS SoS
Podem operar
separdos!
Desenvolver olhando para o Ciclo de Vida
Conceito – Desenvolver para o ciclo de vida
Life Cycle Scenarios
Custom Parking
Logistic Line Maintenance
Servicing Non Planed Line Maintenance
Optimization Route Heavy Maintenance
Transferring data to aircraft Non Planed Heavy Maintenance
... …
STAKEHOLDERS STAKEHOLDERS STAKEHOLDERS
STAKEHOLDERS STAKEHOLDERS STAKEHOLDERS STAKEHOLDERS STAKEHOLDERS STAKEHOLDERS
environment environment environment
Desenvolver do “todo” para as “partes”
Conceito – Desenvolver do todo para as partes
Interiores
MELHORA A INTEGRAÇÃO Propulsão
Sist. Eletrico Estruturas
Avionica Outras….
Conceito – Das partes para o todo
HOJE
GAPS nos requisitos de alto nível
Requisitos abordados em tecnologias
Interiores
Propulsão
Sist. Eletrico Estruturas
Avionica Outras….
As várias Definições do Processo
de Systems Engineering
Conceito – Definição do Processo – Scott Jackson
Systems Engineering
ANÁLISE FUNCIONAL ANÁLISE DE REQUISITOS DESIGN
NÍVEL AVIÃO NÍVEL AVIÃO NÍVEL AVIÃO
Requisitos FUNÇÕES REQUISITOS DA DESIGN

de AERONAVE AERONAVE (ARQUITETURA
BÁSICA)
Clientes
NÍVEL AVIÃO
FUNÇÕES REQUISITOS DESIGN

SUB-SISTEMA SUB-SISTEMA SUB-SISTEMA
NIVEL SUB-SISTEMA
Source: Jackson 1997
Conceito – Definição do Processo – DoD (U.S)
System Analysis
and Control
Requirements Analysis
Requirement LooP
Functional Analysis
Design Loop
Verification Loop Synthesis
Conceito – Definição do Processo – DoD (U.S)
System Engineering Process
DATA
System
DATA
Sub-System
DATA
Sub-System
Component
Systems Engineering Process
FUNCTIONAL REQUIREMENTS DESIGN
Flow down Flow Down Detail
CUSTOMER
REQUIREMENTS Design LOOP (Trade-off)
AIRCRAFT AIRCRAFT DESIGN

(Top Level)
Aircraft FUNCTIONS REQUIREMENTS
Requirement LOOP (Trade-off) Verification
Flow Down & Allocation
Design LOOP (Trade-off)
SYSTEMS SYSTEMS DESIGN

Sistema FUNCTIONS REQUIREMENTS (System)

Subsistema
Componente
Systems Engineering Process
Customer
Requirement
FUNCTIONAL REQUIREMENTS DESIGN

Flow down Flow Down Detail

ft
Aircra
AIRCRAFT AIRCRAFT DESIGN

FUNCTIONS REQUIREMENTS (Top Level)
Requirement LOOP (Trade-off) Verificationt

System
SYSTEMS SYSTEMS DESIGN

FUNCTIONS REQUIREMENTS (System)

tem
Subsys

nent
Compo
Conceito – Definição do Processo – Model Based SE
Req Req Req

Validation Validation
Aircraft Model Model
Validation
Aircraft
Model
requirements Verification Verification Verification integration
Integrated Integrated - flight test -
Model Model Model
Req
System Req
Validation Validation
- a/c ground test -
requirements Model Model System integration
Verification Verification - HIL rig test -
Integrated
Model Model
Req
Equipment Validation
Equipment test
requirements Model
- at a/c manufacturer -
Verification
Model
Component Component test

requirements - at supplier -
Implementation

Curso Systems Engineering WKS - 0 Conceito

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Curso Systems Engineering WKS - 0 Conceito

Enviado por

Direitos autorais:

Formatos disponíveis

Systems Engineering

O QUE NÃO É SYSTEMS ENGINEERING

QUAL O OBJETIVO DO SISTEMA?

Para nosso contexto: É um processo de Desenvolvimento de produto

Integrated Process and Product Development (IPPD)

Systems Engineering (Em uma de suas perspectivas)

Systems engineering is a multidisciplinary

Systems engineering includes the application of

Systems Engineering pode ser “apresentado” na perspectiva de:

Systems Engineering Management

GDP (BR) / Chief Engineer (U.S))

Systems Integrator (Systems Engineer)

Systems Architect (“Technology”)

Research Development Team

Mas não pode se executado somente em uma perspectiva!

Alta complexidade tecnológica:

Alta complexidade tecnológica:

Funcionalidades integradas Tecnologia

Systems Engineering vai além da Proposta de Valor

Adiciona-se a essa declaração o ambiente operacional onde o produto irá

Adiciona-se o entendimento entre o desenvolvedor (produto) e os stakeholders

Now we can write (compose) a REQUIREMENT !!

PRINCIPAL CARACTERÍSTICA DO SISTEMA:

Basic ability to understand and

to deal with complex systems

that gives us the freedom to

identify root causes of problems

and see new opportunities.

need to map the system at several levels?

Where are we drawing the boundaries of the system? Do we need to

make the boundary of the system under consideration wider?”

Hierarchical Relationships for Systems of Interest

Subsytem A1.1 Subsystem A1.2

An Aircraft with Enabling Systems

Enabling Systems Systems of Interest

Técnico Negócios Melhoria

• PMI is the world’s leading not-for-profit association for the

Project management profession.

• Project Management Body of Knowledge (PMBOK® Guide)

lexicon for discussing, writing, and applying project management.

• Project Management Professional (PMP ®) Certification

Project Management Institute Knowledge Areas

Integration Management / Scope Management / Time Management

Ensure highest possible

• Total cost growth:

• Average schedule overrun:

• Similar situation in other

Sources: GAO 06-368, Bloomberg, GAO 10-374T

1. Reactive Program Execution

Domain Representation of “the Example: New aircraft development

Increased flight economy by 20% /

Risks are tracked thru the life of the project

Risks Requiring Mitigation

The SE Manager is a buffer between management (including project) and

Translate technical issues to non-technical terms decision make

Control technical assignments

SE Management is an interface to project management

Keep the PM informed of technical issues

Keep the staff informed of any impacting decisions or discussions

Subcontractors should have all the regulatory and systems requirements

The warranty is considered a non-functional requirement that impacts the

Very much dependent on reliability

May result in significant losses if not considered during architecture/design

The Defense Acquisition University (DAU) is a Department of Defense (DoD) training