INCOSE 98 SYMPOSIUM
The Application of a Systems Engineering
Process to the Re-engineering of an Air
Defense System
Claude Y. Laporte - Process Engineering
Alain Guay - Sub-System Engineering
Jacques Tousignant - Systems Engineering
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
AGENDA
Introduction
Organizational Processes
Re-Engineering Project
Lessons Learned
Next Steps
Conclusion
1998 INCOSE SYMPOSIUM
Slide 2
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 3
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
OERLIKON AEROSPACE
System
Integrator of an Air Defense System
Certified as Level 2 - Software Engineering
Institute in 1997
Has also
met 8 of the 17 Level 3 Goals
ISO
9001 since 1993
NATO Secret Organization
Over 120 Systems and Software Engineers
1998 INCOSE SYMPOSIUM
Slide 4
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
ORGANIZATIONAL PROCESSES
Systems & Software Engineering
Document Inspection
Configuration Management
Quality Assurance
Lessons Learned
Staffing, Performance Management
Documentation Management
Contract Management
Procurement Management
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 5
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
ENGINEERING PROCESS ASSET LIBRARY
Policies
Process Descriptions
Guides, Forms and Templates
Examples of Documents Produced
Business Cases
Proposals
Engineering Plans
Specifications
Tailored Processes
Process and Product Measures
Lessons Learned
Charter of Process Engineering Groups
Training Material
Historical Data
1998 INCOSE SYMPOSIUM
Slide 6
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
SYSTEMS ENGINEERING PROCESS (SEP)
Systems Engineering Capability Maturity Model
Generic Systems Engineering Process from Software
Productivity Consortium (SPC)
The SEP activities can be performed:
Concurrently
Iteratively
Recursively
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 7
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
MANAGEMENT ACTIVITIES OF OA SEP
STEP 110
Understand
Context
STEP 120
Analyze
Risk
STEP 130
Plan Increment
Development
STEP 140
Track Increment
Development
STEP 150
Perform Increment
Closure
1998 INCOSE SYMPOSIUM
Slide 8
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
MANAGEMENT ACTIVITIES OF
OA SEP
I9
I1
External System
Definition
I3
User
Req.
I4
Tech.
Base
I6
Incremen
t
Status
I7
Tech.
Baseline
I2
Subsystem/
Component
s
Status
System Context
Understand
Context
O5
Estimate of the Situation ( Approved )
Step 110
Analyse
Risk
Step 120
I5
Risk
Management
Plan ( Approved )
Plan
Increment
Development
Step 130
Increment Plan
( Approved / Updated )
Increment
Plan
( Approved )
System
Implementatio
n
Status
O3
Increment
Plan
( Updated )
Track
Increment
Development
System Definition
( Approved )
O4
Step 140
I8
Tech.
Risk
Increment
Status Report
Incr.
Plan
(Enacted)
Develop
System
Plan
Step 150
System Plan
( Approved )
System Status
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
O1
O2
Slide 9
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
STEP 110 - UNDERSTAND CONTEXT
SEP 111
Define
Approach
SEP 112
Estimate
Situation
SEP 113
Review
Context
1998 INCOSE SYMPOSIUM
Slide 10
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
VIEW OF A PROCESS STEP
STEP 111 - Define Approach
Inputs
Outputs
System Engineering Folder (SEF)
Customer Requirements
External System Definition
Define key system/
increment
objectives
Identify system/
increment
constraints
Identify system/
increment
stakeholders
Develop
alternatives
Subsystem/Component Status
(Feedback)
User Requirements
Technology Base
System Status (Feedback)
Technical Release (Feedback)
System Context (Feedback)
Systems Engineering Folder
(SEF)
Approach Definition
Information Sources (SOW, insights,
historical data, policies, etc.
Entry
Criteria
Signed contract or authorisation
Resources
Stakeholders
Management authorisation
Exit
Criteria
Measures
Effort
To Step 112
Increment-level objectives
Alternatives, constraints, and
stakeholders
Legacy inherited
Appropriate changes
1998 INCOSE SYMPOSIUM
Slide 11
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
TECHNICAL ACTIVITIES OF OA SEP
STEP 210
Analyze
Needs
STEP 220
Define
Requirements
STEP 230
Define functional
Architecture
STEP 240
Synthesize Allocated
Architecture
STEP 250
Evaluate
Alternatives
STEP 260
Verify and Validate
Work Products
STEP 270
Control Tech.
Baseline
1998 INCOSE SYMPOSIUM
Slide 12
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
TECHNICAL ACTIVITIES OF OA SEP
Informal
functional
Hierarchy
(With Tech.
Meas.)
Estimate of
the Situation
I1
System
Context
Analyse
Needs
O4
Step 210
Sys. Requi.
User
Requi.
Alternative
Functional
Architectures
Technical
Performance
Measurements
Performance
Requirements
Define
Requi.
I3
Derived
Req.
Step 220
Define
Functional
Architecture
Step 230
Techno.
Base
Alternative
Allocated
Architecture
I4
Synthetize
Allocated
Architectures
External
System
Definition
I2
System
Solution
(Prefered)
Step 240
Allocated
Req &
Perf.
Estimates
Evaluation
Results
Verify and
Validate
Work
Products
Step 260
I5
Evaluation
Documentation
(Baselined)
O3
O1
Configuration
Control /
Constraints
Step 250
System
Definition /
Process
Requi.
Technical Risk
Increment Status
V & V Test
Procedures
Evaluate
Alternatives
Verification &
Validation
Results
Technical Baseline
O2
System
Definition
(Interim
Updated)
Control
Tech.
Baseline
Step 270
System
Definition
( Interim )
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 13
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
OVERVIEW OF LAUNCHER CONTROL UNIT
Coordinates operation of sensors
Radar, FLIR,TV, wind sensor.
Controls missile launch and guidance
Guides missile flight with laser beam
Tracks missile with infrared detectors
Tracks targets
Controls turret servo systems
Interfaces with other subsub-systems (consoles)
1998 INCOSE SYMPOSIUM
Slide 14
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
MAIN OPERATOR CONSOLES FUNCTIONS
Radar console display and controls:
Radar Operation
C3 Network Management
ElectroElectro-optical console display and controls:
Optical Sensors (FLIR, TV)
Missile Launch/Guidance
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 15
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
RE-ENGINEERING PROJECTS
Divided in Two Increments
Increment One: System Definition Increment
Output:
System Requirement Specifications
Increment Two: Sw/Hw
Sw/Hw Development Increment
Outputs:
Set of Design and Equipment Specifications
Qualified PrePre-Production Unit
1998 INCOSE SYMPOSIUM
Slide 16
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 110 - Understand Context
Sub Step 111 - Define the Approach
Activity 1 - Define Objectives of the Increment
Reduce production, life-cycle costs and part obsolescence
Improve growth potential (e.g. graceful degradation)
Activity 2 - Identify Project Constraints
Interface with existing components (e.g. missile, e-o)
HCI conflicting requirements from users/customers
Activity 3 - Identify Project Stakeholders
Current customer representatives and Current users
Marketing and business development
Senior management and Team members
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 17
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 110 - Understand Context
Sub Step 111 - Define the Approach
Activity 4 - Develop Project Alternatives
Rehost functions on new hardware or incorporate new
requirements
Select a development life-cycle
V ee (Forsberg)
Conduct Pilot project
Select Alternative Technologies (e.g. trade-off analysis)
Identify COTS
communication bus
processors
displays
1998 INCOSE SYMPOSIUM
Slide 18
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 110 - Understand Context
Sub Step 112 - Estimate the Situation
Put project knowledge together by documenting assumptions,
decisions and their rationale
Sub Step 113 - Review Context
Review estimate of the situation with stakeholders
Obtain commitment to go ahead
Go - No Go decision point
Agree on strategy
Commit resource allocation
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 19
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 120 - Analyze Risks
Risk Management Plan
Risk Descriptions and Impacts
Budget overrun, schedule delays, integration risks
due to concurrency, new technologies
Documented, updated and stored in a database
Mitigation Strategies
Pilot projects, engineering models, mockmock-ups
Analyses
Component and subsystem modeling
Training
Reviews with stakeholders
1998 INCOSE SYMPOSIUM
Slide 20
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 130 - Plan Increment Development
Systems Engineering Management Plan (SEMP)
Revision of alternative solutions
Definition of TPMs, requirement management approach, training plan,
plan,
CM,QA, technical and project reviews.
Description of the increment, e.g. reverse engineering
Look ahead of next increment, e.g. forward engineering
Problems, needs and constraints (SEP 210)
Function definition (SEP 220, 230)
Functional allocation (SEP 240)
Definition of system (SEP 250)
Development of the Organizational Breakdown Structure (OBS)
Development of the Work Breakdown Structure (WBS)
OnOn-going execution of risk aversion
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 21
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Step 140 - Track Increment Development
Formal reviews
Update the SEMP
Step 150 - Perform Increment Closure
OnOn-going capture of work products (e.g. developmental
configuration management)
Capture Lessons learned from the increment
Baseline work products
1998 INCOSE SYMPOSIUM
Slide 22
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
Step 200 - Technical Activities
Step 210 - Analyze Needs
Legacy system requirements were known
Comments, suggestions, deficiencies were captured
Potential customer’
customer’s requirements were captured
Compile, analyze, prioritize
Operational scenarios and environment rere-assessed
Review with stakeholders in parallel with Risk Management Plan
Steps 220 - Define Requirements, 230 - Define Functional Architecture,
240 - Synthesize Allocated Architecture and 250 -Evaluate Alternatives
Performed iteratively
Step 260 - Verify and Validate Work Products
Requirements and verification requirements, stored in a database
1998 INCOSE SYMPOSIUM
Slide 23
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
Oerlikon
Aerospace
A SEP INCREMENT (THE REAL LIFE)
SEP-100 Manage Development Effort
Understand
Context
Analyze
Risk
Plan Increment
Development
Track Increment Development
Develop System Plan
SEP-200 Define System Increment
Analyze Needs
Define Requirements
Define Functional Architecture
Synthetize Allocated Architecture
Evaluate Alternatives
Validate and Verify Solution
Control Technical Baseline
Not to Scale
1998 INCOSE SYMPOSIUM
Slide 24
Oerlikon
Aerospace
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
LESSONS LEARNED
Use Pilot Projects to Mitigate Risk
Members of Pilots projects have a Safety Net for ¨mistakes¨
–
–
Manageable length so to be able to assess progress.
Well identified deliverables: % of completion can be assessed.
Experienced Project Manager
Success of Pilots facilitates adoption of technologies
Size of Increments
Selection of participants that knew the system process
Other participants were coached
First time use of an incremental process
Series 100 steps were performed in sequence while series
200 steps were performed in multiple iterations
1998 INCOSE SYMPOSIUM
Oerlikon
Aerospace
Slide 25
Application of a Systems Engineering Process
to the ReRe-engineering of an Air Defense System
NEXT STEPS
Integrate SEP with Project Management Process and
Software Development Process (e.g. risk management)
Define Project Metrics and Process Tailoring Guidelines
Apply SEP to detailed design & development phase
Map SEP to CORE® Systems Engineering Tool
Conclusion
Process was found very useful in planning activities,
collecting and managing technical information
Pilot projects helped in better understanding the SEP
Experienced project managers are still required
The systems engineering process cannot be followed blindly
1998 INCOSE SYMPOSIUM
Slide 26