Baltimore Chapter

Systems Engineering (SE)

&
Project Management
Nick Clemens, PMP
Engineering Management & Integration Inc. (EMI)
585 Grove Street, Herndon, VA 20170 703-742-0585
www.em-i.com
 Legal Notice
Baltimore Chapter

Images of PMI material such as the PMBok and the use of related logos and trademarked terms such as
OPM3 ™ or PMP ™ are the property of The Program Management Institute. All rights are reserved
by The Program Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299,
USA, ‘www.pmi.org, 610-356-4600.
INCOSE material when used is noted in the brief and remains the property of the International Council on
Systems Engineering, 2150 N. 107th St., Suite 205, Seattle, Washington, 98133-9009,
‘www.incose.org, 800-366-1164
Other material is sourced as noted and the originating author(s) maintain full rights where appropriate.
 The Talk
Baltimore Chapter

• PMI Standards and Documentation

– OPM3 (PMI’s Project Management Maturity
Model)
• Role of the Project Manager and Systems
Engineer
– Impact of Evolutionary Acquisition
• Questions and Discussion
 Heritage of SE Standards
Baltimore Chapter 1998
EIA/IS 731 CMMI
Systems SE Capab Model

Engineering 1994 1998 2000 2004 2005

EIA/IS ANSI/EIA INCOSE SE
1969 1974 1994 632 632 Handbook V2 V2A V3
Mil-Std- Mil-Std- Mil-Std- (Interim)
499 499A 499B 2002
1994 1998 ISO/IEC
IEEE IEEE 15288
1220 1220
(Trial Use) 2003
NAVAIR
SE Guide

1999
DSMC/DMU
SE Fundamentals
Others ...
1995 1996
Software 1988 ISO/IEC
12207
IEEE/EIA
12207
Engineering Dod-Std-
2167A
1987 1994 1995 1995
Dod-Std- Mil-Std- IEEE 1498 EIA/IEEE
1703 498 /EIA 640 J-Std-016
1988 (Draft) (Interim)
Based On
Dod-Std-
7935A Referenced In

Source: INCOSE Handbook

 The SE Body of Knowledge
Baltimore Chapter (SEBok)
• A comprehensive resource for understanding the extent of the
practice of Systems Engineering for a spectrum of users
– Accomplished systems engineers may seek more in-depth information in a
particular area of the discipline
– Program managers may seek support for just-in-time performance
– Other engineering disciplines may be asked to perform systems engineering tasks
– An interested neophyte or potential consumer of systems engineering services
may wish to learn more about the discipline
• The supporting body of work referenced in the guide is
referred to as the "systems engineering body of knowledge”
– The guide does not create extensive new work; it provides organization and
context for the information
– The processes, lessons learned, products and standards have been developed
since the 1930s
– The guide is helpful in understanding systems engineering, and the roles that
INCOSE and its members play in promoting the discipline of systems engineering
– Potential basis for future SE certification
 PMBok Evolution
Baltimore Chapter

1987 2000

1983 1996 2005

 PMI Documents
Baltimore Chapter

Organizations

Projects People
 PMBoK
Baltimore Chapter

• Published December
2000
• Adopted By The
American National
Standard Institute
(ANSI) as ANSI/PMI
99-001-2000
• Next Update Due NLT
2005
 PM Competency
Baltimore Chapter Framework

• Published September
2002
• Focus is on the
Individual
Professional
• Not for Personnel
Assessments
• Some Unresolved
Issues
 Government Extensions
Baltimore Chapter

• Published 2002
• Applies to National
State/Provincial and
Local Governments
• Internationally Based
• US DoD Extension
Also
 Other Extensions
Baltimore Chapter

• Construction Extension
• Automotive Extension
• Earned Value
Management Standard
• Configuration
Management Standard
• Scheduling Standard
• WBS Standard
• Portfolio Management
Standard
• Combined Standard
Glossary
 OPM3
Baltimore Chapter

• Published December
2003
• Global Standard
• Looks at the
Organization
• Specific Levels Not
Defined (Continuum)
 OPM3 Standard Elements
Baltimore Chapter

The essence for OPM3 is the blending of knowledge,

assessment, and improvement.
 OPM3 Standard Elements
Baltimore Chapter •A Best Practice is an
optimal way to achieve an
objective
•A set of Capabilities
supports the achievement of
a Best Patrice

•An Outcome is a result of

applying a Capability
•A Key Performance
Indicator (KPI) represents
the means to measure an
outcome via a metric
 How it Stacks Up
Baltimore Chapter
BP Name: Use Team Work
BP Description: Cross functional teams carry out the
Organization’s activities

Capability Descriptions:
•Develop Integrated Program and Project teams

•Develop Cross Functional Teams

•Organize project work by functional area

 Categorizing Best
Baltimore Chapter Practices & Capabilities
• The Capabilities are categorized by the Process Groups -
Initiating, Planning, Executing, Controlling and Closing
Processes (IPECC)

• Best Practices are categorized according to the

Organizational Project Management Domains - Project,
Program, Portfolio (PPP)

• Best Practices are also categorized by the Stages of

Process Improvement - Standardize, Measure, Control,
continuously Improve (SMCI)
 OPM3 Construct
Baltimore Chapter
 Assessment Diagrams
Baltimore Chapter
 OPM3 Continuum
Baltimore Chapter
 Roles of the PM and SE
Baltimore Chapter
 Program Manager
Baltimore Chapter Responsibilities

Source: Defense Acquisition University (DAU)

 Systems Engineering
Baltimore Chapter Focus (Traditional)
 System Definition
Baltimore Chapter

• Definition: A system is a construct or collection of different

elements that together produce results not obtainable by the
elements alone
– The elements, or parts, can include people, hardware, software, facilities,
policies, and documents; that is, all things required to produce systems-
level results
– The results include system level qualities, properties, characteristics,
functions, behavior and performance
– The value added by the system as a whole, beyond that contributed
independently by the parts, is primarily created by the relationship
among the parts; that is, how they are interconnected (Rechtin, 2000)

A Consensus of the INCOSE Fellows

 Systems Engineering
Baltimore Chapter Definition

• Definition: Systems Engineering is an engineering discipline

whose responsibility is creating and executing an
interdisciplinary process to ensure that the customer’s and
stake-holder's needs are satisfied throughout a system's entire
life cycle.
– High quality
– Trustworthy
– Cost efficient and
– Schedule compliant

A Consensus of the INCOSE Fellows

 A Systems Engineering
Baltimore Chapter Process
The systems engineering process typically comprises seven tasks
• State the problem
• Investigate alternatives
• Model the system
• Integrate
• Launch the system
• Assess performance, and
• Re-evaluate

From A. T. Bahill and B. Gissing, “Re-evaluating systems engineering concepts using

systems thinking,” IEEE Transaction on Systems, Man and Cybernetics, Part C:
Applications and Reviews, 28 (4), 516-527, 1998
 Traditional SE Process
Baltimore Chapter
Linier Acquisition Process
Project Start Project End

A B
Development Production Deployment
 Evolution of MIL STD
Baltimore Chapter
499B to ANSI/EIA 632

Source: Defense Acquisition University (DAU)

 Linier Acquisition Phases
Baltimore Chapter

User Needs & z Process entry at Milestones A, B, or C

Technology Opportunities z Entrance criteria met before entering phase
z Evolutionary Acquisition or Single Step to Full
Capability

(Program
A B Initiation) C IOC FOC

Concept Technology System Development Production & Operations &

Refinement Development & Demonstration Deployment Support
Concept Design FRP
Decision Readiness LRIP/IOT&E Decision
Review Review

Pre-Systems Acquisition Systems Acquisition Sustainment

Source: DOD 5000.2

 DoD Acquisition Process
Baltimore Chapter (Simplified)
MS B

MS C
MS A

AoA
Concept Technology JROC DAB
Refinement Development

DAB Demo Incre ment 1

MS B MS C
Demo Incre ment 2

DoDI 5000.2 MS B MS C
Demo Incre ment 3

Source: DoDI 5000.2

 Systems Engineering
Baltimore Chapter Focus
 Traditional Optimal Zone
Baltimore Chapter For Design Changes
Detail Available
Conceptual Breadth

Optimal Zone for

“Cost” to Resolve C4I Support Issues
Issue Identification

time

MS- A MS - B MS - C

Source: Clemens, CCRTS 2004

 Evolutional Acquisition
Baltimore Chapter Change Zones
Detail Available

Shape the JTRS Program

Conceptual Breadth

Cluster x
Manage the Program
Optimal Zone for
Issue Identification
“Cost” to Resolve C4I Support Issues
Support JV 2020
Cluster 2
time
MS 0 Detail Available
MS I MS II MS III
Conceptual Breadth MNS ORD Engineering/ Production/
Manufacturing Fielding

Optimal Zone for

“Cost” to Resolve C4I Support Issues
Issue Identification

time
MS 0 MS IDetail Available
MS II MS III Cross Cluster Optimal Zones for-
Conceptual Breadth MNS ORD Engineering/ Production/
Manufacturing Fielding Issue Identification
Technology Insertion
System Enhancements
Optimal Zone for
Issue Identification
“Cost” to Resolve C4I Support Issues
Role of the JPO
Manage across clusters and over time to smoothly
MS 0
Cluster 1
MS I MS II MS III
time
enhance system capabilities in support of near, mid and
MNS ORD Engineering/ Production/
Manufacturing Fielding
long term program objectives and requirements

Source: Clemens, CCRTS 2004

 New DoD SE Policy 20
Baltimore Chapter February 2004
• “All programs…shall apply a robust SE approach that
balances total system performance and total ownership
costs…”
• “System Engineering Plan (SEP) required for MDA
approval in conjunction with each MS review”
• Interim Guidance Provided in a March 30th Memorandum
– SE is to be integrated into a program’s IPT Structure
– SE process will be tailored in each phase of a program
– The system’s technical baseline will be managed and metrics
developed to show progress
– Technical Reviews will assess maturity risk and support program
decisions.

Source: DoD USD AT&L

 Possible JTRS JPO SE
Baltimore Chapter Organization
SE Division
Chief

NETWORK

Arch Services Management IA Configuration

Branch Branch Branch Branch Branch

LOG Waveform
Branch Branch
 The Role of the Systems
Baltimore Chapter Engineer
• Every systems engineering project should have one
• Provide the “glue” to pull all the sometimes diverse system elements together
• Assist the Program/project manager in the managing the technical effort
• Handles myriad of daily activities of coordination between system elements
• Maintain good overall perspective of the system
• Define, clarify, and document requirements
• Perform the necessary parametric analysis and tradeoffs
• Recognize when interface impacts might occur and take early action to avoid
problems
• Act as technical interface between subsystem teams and project management
• Role in development phase considered most important
– Approximately 80% - 90% of development cost of a large system is predetermined
by the time only 5% - 10% of the development effort has been completed
Source: INCOSE Systems Engineering Handbook
 The Project Manager
Baltimore Chapter

• Provides the “glue” that holds the Project

Together
• Responsible to Stake Holders and Project
Advocate
– Cost
– Schedule
– Performance (Capabilities)
– Scope
• Responsible to the Customer for Delivery
 Questions
Baltimore Chapter

Nick Clemens, PMP

President, Baltimore Chapter
www.pmibaltimore.org
‘nick@pmibaltimore.org
‘nick.clemens@em-i.com
703-588-1427 / 703-742-0585