How A Systems Engineer
Starts……?
Two Practitioners
Speaking for Themselves, ergo the ‘A’
Herm Migliore
1977 - 1997
1997 – Present
Portland State University
International Council on Systems Engineering (INCOSE)
Mechanical Engineering Senior Design Projects
Advisor to Systems Engineering Masters Projects
• Small to Medium Sized, Wide Variety of Companies & Agencies
• Often Not an End -- Always a Beginning
John Blyler
1993 – 1996
Advisor & Prof
Editorial Director at Extension Media
Editor in Chief, ‘Chip Design’ and ‘Embedded Intel ‘ magazines
IEEE
Systems Engineer, Hanford
Hardware-Software Integration
Systems Engineering Management
Starts…?
What ?
Project?
consisting of a team and project manager?
• systems engineer is part of team
• or, may not be a ‘systems engineer’ on team
Process?
what steps for developing an engineered system
• includes implementation
• development of product, process, or service
Method?
how do we perform steps in development process
• tailored to the project/product
Thinking?
•
•
•
about Fuzzy-Front-End
‘as-is’ situation is troubling
stakeholders vision on use of new system
before functions, before requirements
Systems Engineering? What’s That?
is the practice of creating
the means of performing useful functions through
the combination of two or more interacting elements
Norm Augustine
retired Chairman and CEO, Lockheed Martin Corp
INCOSE “INSIGHT” Oct 2009 Vol 12 Issue 3
Systems Engineering
Systems Engineering focuses 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 --Performance -- Test-- Manufacturing -- Cost &
Schedule--Training & Support--Disposal. 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 technical needs of all stakeholders with the goal of
providing a quality product that meet the users needs.
International Council on Systems Engineering (INCOSE)
Twelve Systems Engineering Roles
Sarah Sheard
Requirements Owner
System Designer
System Analyst
Validation/Verification Engr.
Logistics/Ops Engineer
Glue Among Subsystems
Customer Interface
Technical Manager
Information Manager
Process Engineer
Coordinator of Disciplines
Classified Ads SE – software systems
Systems Engineering
Kossiakoff and Sweet
Principles and Practice
Wiley Interscience 2003
Cost Control
Project Management
Systems Engineering
Stakeholders?????
Customer
Sponsor
User
All Responsible and Affected Parties
THE INTERFACE
between PM and
Engineers
Technical
Specialties
Cost Control
Science
Project Management
Systems Engineering
Technical Support
Sponsor
Program Life Cycle – Vee Model
User
Need
Product
Release
system test plan
System
Requirements
HW-SW
Requirements
System
Testing
HW-SW test plan
HW-SW
Testing
integration plan
HW-SW
Design
Integration
Testing
unit plan
HW-SW
Implementation
time
Unit
Testing
CUSTOMER REQUIREMENTS
Analyze
Assess
Verify
Architecture
Outcomes
and
Problem
&
Select
Decisions
Synthesize
Architecture
Technical Process
Specification-Requirements
Product System
Analyze
Organization
Plans &
Direction
Verify
Planning
Assess
and
Select
Synthesize
Activities
Management Process
SEMP –Systems Engineering Management Plan
Process System
PRODUCT DEFINITION
Brian W. Mar, Emeritus Professor UofW
Bernard G. Morais, Synergistic Applications
Differences Between PM and Systems Engineering
Program/Project Management
Cost, schedule, organization, business-side
Policy decisions
Program risk management
Allocate programmatic resources
Trained in Organization/Management Theory
Project Management Institute, Etc
Systems Engineering
Owner of Requirements and Architecture (high level design)
Interface between PM-technical specialists
Uses process to design, build, test and other product life cycle activities
Technical resource allocation
Technical risk management
Trained as an Engineer
INCOSE, IEEE, NASA, DOD, Etc
Function-Requirements-Architecture-Test
“The Engineering of Complex Systems”, Morais and Mar, 1997
FRAT Method May Be Combined with Other Process Models
Heading Down Pyramid – Maturity of Development
Proposal / Marketing
Development Objectives
Preliminary Design
Detailed Design / Manufacturing
One Level:
Next Level:
F  R  A  T and FR  A
F  F1, F2, F3; Differences in Timing, Dependencies and Utility
R  R1, R2, allocate/assign to A
Eye of the
Stakeholder?
Upper Level FRAT Data Provides
Scope For Next Level
Lower Level Must Roll - Up
and Map to Upper Level
Each Level of FRAT Establishes
a BASELINE
ConOps
jack.ring
@incose.org
Community Has Problem Symptoms from As-Is Situation:
Unacceptable and Preferable Aspects
Consensus on:
•Problem System
•Intervention Strategy
•Stimulus:Response Scenario(s)
•Accountabilities
Value Generated by
Developed/Operational system
Design and
Architecture
Assay and
Adaptation
Assembly/
Deploy
Components
Buy/Make
Measures of Effectiveness
effects that suppression
system must exhibit
Standards of Acceptance
value of as-is and could-be
Unacceptable Discomfort felt by Stakeholders
Consensus of All Responsible and Affected Parties:
•Problem System – generates problem symptoms
•Intervention Strategy - comprehensive view of intended use
•Stimulus:Response – all possible scenarios of ‘To Be’ system,
that suppress (amplify?) problem symptoms, intervention system
•Accountabilities- what are we/you willing to do to make
problem go away
Problem & Intervention Systems
Will Change
Eye of
Stakeholders
Tom
As-Is Situation
•Viable recycling - Legacy hospitals
•Contacts with suppliers/recyclers
•Active recycling in Portland
•Cost gasoline -up $4.25 down $2.50
•Tom wants help with promotion
•Masters student, Neil interested in
- Fuzzy Front End
- ConOps
Urine Bottles and Sorting Operation
Blue wrap polypropylene film used
for sterilizing surgical instruments
Recycling Bags
Existing Benefit to Legacy Hospital – Cost Avoidance
Labor Costs were small
Problem Suppression Systems – Intervention System
Neil’s Guidelines for Starting a Healthcare Recycling Center
Motivate Other Hospitals, Recyclers and Manufacturers
Tom Now a Consultant
Neil Earns Masters Degree
Synthesis - Write the story – ConOps For Stakeholders to Use
Accept , Don’t Accept, Start of New Systems, But ConOps Not Same Structure as IS
System performance upgrade
•
•
•
•
•
•
•
•
•
Minimize force outages
Address the concern of the End-Users
Meet and exceed the various Standards set by the industry
Meet the needs of the organizations that regulate the day to day system operations
Address the public outcry for loss revenue and inadequate system performance
Address the findings from an independent Technical Audit Review group
Make the evolutionary changes that will allow the system to evolve with time, such as
Human to Man Interfaces (HMI)
Machine to Man Interface (MMI)
Programmable logic controller (PLC)
Maximize the system output capacity in Megawatts and revenue
Extend the Life Cycle of the system
The tests & controls that were used to
deliver the forecasted benefits are:
•
•
•
•
Boiler nozzle calibration test & gross boiler efficiency test
Thermal Heat Rate (THR) Test
Supervisory Control and Data Acquisition (SCADA)
Programmable Logic Controller & Machine to Man Interface (MMI)
Systems Engineering
Traditional
Body of Knowledge, Handbooks, Publications, Certification
Structured and experienced development processes
Technical and Organizational
Requirements and Interface management
Tailored development processes, adaptive
Stakeholders part of development and use
Thinking
Describe not Prescribe (Herm needs a mnemonic , FRAT)
Stakeholders part of problem-system-use (Jack Ring’s ConOps)
Stakeholders’ knowledge and motivation will change
Combination of established and other perspectives
Uncertainty and risk
Change and evolution