How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011...

How to Start a Successful ProgramA Panel Discussion for

Midwest Gateway INCOSE Chapter

May 25, 2011

In order of Appearance:

Bob Scheurer

Bill Jennings

Shawn Simmons1

Integrated Technical Planning

“Successful Programs Begin with Good Planning”

…But what is good planning???


Good Planning:

• Combines the management approach with the technical solution definition/derivation

• Encompasses the holistic view of planning and engineering for the complete system lifecycle

• Continuous across pre-contract, post-award planning, and program execution

3


Good Planning Drives Execution

Successful Program Execution is dependent on• Clarity of program objectives and requirements• Clarity of activities, schedules, deliverables, resources• Early identification of needs• Viewing requirements in terms of the entire system life

cycle• Integration of top-down needs and bottom-up solutions• Flexibility in response to changing conditions - updates

4

All of these depend on good planning!


But Good Planning has Been Missing…

“A root cause of failures on acquisition programs includes …lack of technical planning and oversight ….” • Mark Schaeffer, OUSD AT&L. “The Value of Systems Engineering to

Program Management.” INCOSE. DoD-directed Studies/Reviews, 2005.

“Reason for Weapon Systems Cost Growth is a poor foundations at Milestone B go ahead, including …. artificially low cost estimates and optimistic schedules and assumptions ….” • Memo from John J. Young (DoD USD AT&L) to DoD Secretary

Gates, “Reasons for Cost Change for Selected Major Defense Acquisition Programs” (Feb 2009).

5


Could something else be missing, too?: Integration

Localized Technical Planning is Not Enough• Too Many Disconnected Program Visions• Inefficiencies from Plan Redundancies and Inconsistencies• Gaps in Planning Details

Integrated Technical Planning is the Gateway to Program Success• Organized and Disciplined• Aligned Planning Processes• Instituted at the Very Beginning of an Initiative• Describes Transformation from Problem (Requirements) to

Design• On-Going Updates and Coordination

6


Integrated Planning Over the Acquisition Lifecycle

7

A B C

Materiel Solution Analysis

Materiel Development

Decision

PDR CDR

Post-CDR Assessment

Post-PDRAssessment

Engineering and Manufacturing Development

(Program Initiation)Technology

Development

Operations and Support

FRP DecisionReview

Production and Deployment

Defense Acquisition Management System, May 22, 2009 extrapolated Defense Acquisition Management System, May 22, 2009 extrapolated

CompetitivePrototyping

Technological Maturity and Integration Risk

Assessment

User Needs

Technology Opportunities & Resources

• The Materiel Development Decision precedes entry into any phase of the acquisition management system

• Entrance criteria met before entering phase

• Evolutionary Acquisition or Single Step to Full Capability

IOC FOC

Pre-Systems Acquisition Systems Acquisition Sustainment

= Decision Point = Milestone Review = Decision Point

LRIP/IOT&E


Outcome of Int. Tech. Planning Outcome is an Integrated Technical View

8

1.0

WBS

2.0 3.0

2.1 2.2 2.3

WBS / PBS

SOW

Contract

SRR SDR PDR. …Lifecycle Phases

•Work Product 1 Final Update Update•Work Product 2 Prelim Final Update •Work Product N - - -

Work Products

IMP/IMS• Events

•SignificantAccomplishments

•AccomplishmentCriteria--

CDRLs

SEIT

PM

IPT IPT

Flt EE SW

Organization

RAM

SEMP

PEP

TEP RM

TEP TEP TEP

Pgm Plans

Plans

…

1.0

WBS

2.0 3.0

2.1 2.2 2.3

WBS / PBS

SOWSOO

Contract

SRR SFR PDR. …Lifecycle Phases / Events

•Work Product 1 Final Update Update•Work Product 2 Prelim Final Update •Work Product N - - -

Work Products

IMP/IMS• Events

CDRLs

SEIT

PM

IPT IPT

Flt EE SW

Organization

SEMP

PEP

TEP RM

TEP TEP TEP

Pgm Plans

Plans

StandardDeck

StandardDeck

StandardDeck +Metrics

…

• Sig Accom (SA) - Acc Crit (AC)• Sig Accom (SA) - Acc Crit (AC)

Airframe

Wing

SW Integration Lab System Integration Lab

Program Customized Plan(Basis for Proposal Estimate & Schedule)

Detailed / Refined Technical Plan

Detailed Functional Work Flows

Ga

te C

Ga

te D

AT

P

IBR

PlanMaturation

SRR PDR CDR TRR

Work ProductRepository

SFR


Elements of the Integrated Planning

Statement of Objectives (SOO) / Statement of Work (SOW) (what to do)• Deliverables (evidence of work done)• Work Breakdown Structure (WBS) (how work is organized)

Program Technical Specification (technical requirements)• Specification / Document Tree (decomposition)

Program Plans (how work will be done)• Integrated Master Plan (IMP) – major events

− Reviews and Audits• Systems Engineering Management Plan (SEMP) (what the supplier has

planned) and Systems Engineering Plan (SEP) (what the acquirer/customer has planned)

− Technical Performance Measures− Subordinate Plans (risk mgt, reqts mgt, trade studies, etc.)

• Test and Evaluation Master Plan (TEMP)• Integrated Logistics Plan (for Operations and Support)• Use of Suppliers• Resource Requirements and Staffing Organization (how people are

organized)• Metrics for Technical Progress, Technical Maturity, and Quality/Productivity

(measurement and feedback mechanism)Risks & OpportunitiesInputs to Earned Value Management System

• Integrated Master Schedule (IMS) with Activity Networks (when)• Cost Estimates (resource management)

9

Inte

gra

ted

& T

race

able


10

And the Planning Needs to Continue:Plan the Work / Work the Plan … for Each Phase

Planning

A C

CBA

B

ICD TechnologyDevelopment

Engineering and Manufacturing

Development


Materiel Solution Analysis

MDD

CPDCDDO&S

FRPDRPDR CDR

Executing


Overview Summary of Integrated Technical Planning

Performed Regularly Across the Total System Lifecycle

Encompasses a Diverse Set of Views to Form the Complete Planning Picture

Receives Guidance for Constructing the Various Plans from:• Customer Documents• Systems Engineering Process• Product Architecture (Product Components via Modeling)• IMP/IMS

11


Getting Started – Identifying the Planning Elements

12

RFP/BAA/ECPCLINs/

CDRLs/SDRLs

Customer SEPSOO/SOW

Customer Documents

Technical Plan Documents

Contract SOW

Planning Packages

PEP/TEPs/Organizational

Breakdown Structure

SEMP &Supporting

Technical Plans

IMP & IMS

Contract WBS

Questions Frameworks

PlanningChecklists

Process Guides

Methods & Tools

Process Networks

DAG

RFP – Request for ProposalSDRL – Supplier Data Requirements ListSEMP – Systems Engineering Management PlanSEP – System Engineering Plan SOO – Statement of ObjectivesSOW – Statement of WorkTEP – Team Execution PlanWBS – Work Breakdown Structure

CDRL:Contract Data Requirements List Contract Deliverable Requirements List Contract Document Requirements List Contractor Data Requirements List Customer Data Requirements List

BAA – Broad Agency AnnouncementBPI – Business Process InstructionBPG – Business Process GuideCLINs – Contract Line Item NumbersDAG – Defense Acquisition GuidebookECP – Engineering Change ProposalIMP – Integrated Master PlanIMS – Integrated Master SchedulePEP – Program Execution Plan


Technical Plan Documents –The Logical Connectivity Flow and Interfaces Between Planning Elements

13

Questions

SOWWBS

Processes

SOOSOO

CSOW CWBS

Planning Packages

SEMPSEMP

Checklists

Program Specific Risks

IMPIMP

IMSIMS

Iterate to align & add detail

Program Plans

Technical Plan DocumentsTechnical Plan Documents

Contract SOW

Planning Packages

PEP/TEPs/OOrganizational

BBreakdown SStructure

SEMPSEMP &Supporting

Technical Plans

IMPIMP & IMSIMS

Contract WBSCustomer/Acquirer

Industry Guidance

ContractorS

A’s

an

d A

C’s

OBS RAMOBS RAM


Summary of Program Planning Building Blocks

14

Build

-up o

f D

eta

ils

Foundation/ Inputs

BAA – Broad Agency AnnouncementCLINs – Contract Line Item (Numbers)CSOW – Contract Statement of WorkCWBS – Contract Work Breakdown StructureDAG – Defense Acquisition GuidanceEVM – Earned Value ManagementPBS – Product Breakdown StructurePEP – Program Execution PlanRFP – Request for ProposalSEMP – Systems Engineering Management PlanSEPMQC – SE Proposal Maturity Quality ChecklistSOO – Statement of ObjectivesSOW – Statement of WorkWBS – Work Breakdown Structure

Integrated Master Schedule Tiers 3 and BelowIntegrated Master Schedule Tiers 3 and Below

EstimatesEstimates ContractsContracts FacilitiesFacilities

Operating PlanOperating Plan

FinancialsFinancials

BudgetBudget EVMEVM Labor/ SkillsLabor/ Skills

CWBSCWBS ProcessesProcessesOrganizationOrganization

Integrated Master PlanIntegrated Master Plan

CSOWCSOW

RFP/ BAA/ SOO/ RFP/ BAA/ SOO/ SOW/SOW/ WBS/WBS/CLINs/ Referenced DocumentsCLINs/ Referenced Documents

PEPPEP SEMPSEMP ManufManuf, Support, Test Plans, Support, Test Plans

Planning GuidancePlanning GuidanceDAG/ Questions/Checklists

Command MediaCommand MediaPBSPBS

Work PackagesWork Packages

Planning PackagesPlanning Packages

- Customer - P. Mgmt/ Finance - P. Mgmt & Engr - Engineering

Integrated Master Schedule Tiers 1 & 2Integrated Master Schedule Tiers 1 & 2

Iterate these to add detail

Success Success CriteriaCriteria

Other Supporting Other Supporting PlansPlans

Major Major Questions Questions & Products& Products


Program Definition Documents

To identify Customer documents that indicate the program requirements for each program phase, examine the related Program Definition Documents.Example: DoD Instruction 5000.02 ‘Operation of the Defense Acquisition System’

• http://www.dtic.mil/whs/directives/• Defense Acquisition Management System − Material Solution Analysis, Technology Development, Engineering & Manufacturing

Development, etc. phases

15


Purpose

16

The Defense Acquisition Guidebook Focuses on the Technical Baselines and Maturing the Technologies/Designs

Focus On Technical Baselines

A B CMateriel Solution AnalysisMateriel Materiel Development Development DecisionDecision

Post-PDR Assessment


Technology Development Operations and Support


Prototyping System DesignSystem Design

IBR IBR IBR OTRRAOTR

TRA TRAProgram Reviewswith a technical basis

TechnicalReviews

Post-CDR AssessmentFRP Decision Review

SustainmentSustainment

DisposalDisposal

ITR

TechnicalBaseline

ASR

Preferred System Concept

SRRPrototypeTechnical Reviews

SystemDesign

Specification

SFR

SystemFunctional Baseline

PDR may occur after MS B for

less than MDAP

Allocated Baseline

PDR

CDR

InitialProduct Baseline

TRR SVR/FCA/PRR

ISRPCA

Product Baseline

Phases

Technology Readiness Assessment

Technical Reviews

Program Reviews

Decision Point

Milestone Reviews

Decision Point if PDR is not conducted before MS B

AOTR - Assessment of Operational Test Readiness ASR - Alternative Systems Review CDR - Critical Design Review FCA - Functional Configuration Audit FRP – Full Rate Production

IBR - Integrated Baseline Review ISR - In-Service Review ITR - Initial Technical ReviewOTRR - Operational Test Readiness Review PCA - Physical Configuration AuditPDR - Preliminary Design Review

PRR - Production Readiness Review SFR - System Functional ReviewSRR - System Requirements ReviewSVR - System Verification ReviewTRA - Technology Readiness AssessmentTRR - Test Readiness Review


17

Questions Framework

Formal Guidance

Question-Based Construct By Stage

Question-based Framework By Stage

IMS Tasks by IPT IMP Significant Accomplishments & Accomplishment Criteria

•Questions•Sub-questions

•Lower Level Tasks & I/O

•Program Reviews/ Events•Significant Accomplishments

•Accomplishment Criteria

• JCIDS & DoDI 5000.02

•Critical Tasks and Work Products

•Program Reviews/ Events

•Program Reviews

Q # Questions Sub-Questions WHENEntry, Early, During

and

Sub-question in Task Format(Use Case

names)

Inputs Lower Level Tasks Outputs

2 Does the program have documented capability needs at the system level (Capability Description Document or equivalent)?

1. Documented resolution of conflicts, uncertainties, and ambiguities within the program and with the customer2. Updated capability needs

2.1 Does the program have documented capability needs at the system level?

Entry Collect the documented capability needs

1. Possible sources -- ORD/O&O, CDD, SRD, SPS, SOW, RFP (Sections L&M and SOW)

1. Identify the inputs that may have capability needs2. Search the inputs for capability needs

Consolidated list of capability needs

2.2 Have these capability needs been reviewed for understanding by the program?

Early Review the capability needs for understanding by the program

Consolidated list of capability needs

1. Review the needs2. Identify conflicts3. Identify ambiguities4. Identify

Description of conflicts, ambiguities and uncertainties

2.3 Have areas of potential misunderstanding or lack of clarity been identified and resolved for consensus within the program and with the customer?

Early Resolve the conflicts, ambiguities and uncertainties with the customer

1. Consolidated list of capability needs2. Description of conflicts, ambiguities and uncertainties

1. Hold discussions with the stakeholders to resolve the conflicts, ambiguities and uncertainties2. Update the capability needs

1. Documented resolution of conflicts, uncertainties, and ambiguities within the program and with the customer2. Updated capability needs

110 050 TPMs Process and Measures Updated Beyer / Shannon Strand / MAJ Byers

110 050 1SoS/FoS TPMs updated & approved to reflect current program management

needs

SoS/FoS TPMs updated and approved to reflect current program management monitoring needs as of SoSFR. Review and concurrence, subject to required changes, of the approved TPMs by appropriate Tier 2 & 3 One Team Management. Required changes implemented in a timely manner.

SA AC EventLSI Owner(s) /LSI Manager

PMUA /TRADOC Closure Criteria

Questions

IMPIMS

Joint Forces Command JCIDs Process Defense Acquisition Management SystemBOEING PROPRIETARY

BOEING PROPRIETARY

Requirements/Acquisition Process Depiction

Conc ept Re fin ement Tech no lo gy Develop mentSystem Develop me nta nd Demon stratio n

Pr od uction an dDeploymen t

RequirementsAcquisitionIntegrated Decision Meeting

Incr ement 3

M S B M S C

M S B

Overarc hing Pol icy

Joint Visio n

Jo in t Cap ston e P ol icy

D

O

T

M

L

P

F

F unction al Are a

Analysis

M ateriel P ro cess

An alysis of M ateriel

Ap pro aches

DOT LPF Ch ang es

F unc tion al Area F un ctio nal Co nce pt

Integr ated Archi tectur e

T echn olog y Dev elo pmen t

AoA

Conc ept

Refin ementCD

M S A

DABJR OCDemo

Demo

Demo

MS B

DABJR OC

M S C

DABJROC

M S C

Incr ement 1

In crement 2

Feed bac k

Oversight

Taken from the U.S. Army Deputy Chief of Staff for Development bTaken from the U.S. Army Deputy Chief of Staf f for Development briefrieftitled, titled, ““The Army in the JCIDSThe Army in the JCIDS”” given at the 2003 CD leadership Conf.given at the 2003 CD leadership Conf.

ICD

CDD

CPD

ICD Initial Capabilities Document

CDD Capabilities Development Document

CPD Capabilities Production DocumentAoA Analysis of Alternatives

DAB Defense Acquisition Board

MS Milestone

BOEING PROPRIETARY

BOEING PROPRIETARY

Requirements/Acquisition Process Depiction

Conc ept Re fin ement Tech no lo gy Develop mentSystem Develop me nta nd Demon stratio n

Pr od uction an dDeploymen t

RequirementsAcquisitionIntegrated Decision Meeting

Incr ement 3

M S B M S C

M S B

Overarc hing Pol icy

Joint Visio n

Jo in t Cap ston e P ol icy

D

O

T

M

L

P

F

F unction al Are a

Analysis

M ateriel P ro cess

An alysis of M ateriel

Ap pro aches

DOT LPF Ch ang es

F unc tion al Area F un ctio nal Co nce pt

Integr ated Archi tectur e

T echn olog y Dev elo pmen t

AoA

Conc ept

Refin ementCD

M S A

DABJR OCDemo

Demo

Demo

MS B

DABJR OC

M S C

DABJROC

M S C

Incr ement 1

In crement 2

Feed bac k

Oversight

Taken from the U.S. Army Deputy Chief of Staff for Development bTaken from the U.S. Army Deputy Chief of Staf f for Development briefrieftitled, titled, ““The Army in the JCIDSThe Army in the JCIDS”” given at the 2003 CD leadership Conf.given at the 2003 CD leadership Conf.

ICD

CDD

CPD

ICD Initial Capabilities Document

CDD Capabilities Development Document

CPD Capabilities Production DocumentAoA Analysis of Alternatives

DAB Defense Acquisition Board

MS Milestone

JFCOM DoD


Planning information availability by phase

1818

MaterielSolutionAnalysis

TechnologyDevelopment

Engineering &Manufacturing Development

Production & Deployment

• Concepts of Operation• Initial system-level capabilities• Operations analysis studies• Technology readiness

information• Lifecycle cost estimates

• Finalized system-level capabilities• Requirements• Functional architecture views• Physical architecture views• Preliminary design • Key supplier data• Substantiated lifecycle cost estimates

• Completed design• Complete product

assembled and tested• Manufacturing and

assembly process in place• Fully mature lifecycle cost

estimates

Available Information Available Information

• Viable set of system-level capabilities & requirements

• Conceptual architecture views & design concepts

• Trade studies supporting draft capabilities & requirements

• Key supplier data• Detailed lifecycle cost estimates


Purpose of the Integrated Master Plan

• Serves as a contractual agreement with the customer on what will be done• Documents program events (PEs)• Identifies significant accomplishments (SAs) for each event• Specify accomplishment criteria (ACs) for each Significant Accomplishment• Provides traceability to WBS, SOW, deliverables, risks, and opportunities

19Event-based

IMP• Provides a framework for planning

integration across the program• Represents the integrated product

development encompassing all functional disciplines

• Provides a common framework for developing the IMS and detailed team schedules


Purpose of the IMS

• Documented schedule of program events

• Specify tasks to satisfy accomplishment criteria for each significant accomplishment

• Task traceability to WBS, SOW, deliverables, & program milestones

• Time-phased tasks and show predecessor and successor relationships

• Time-phased integrated product development encompassing all program teams

• Common framework for developing detailed team schedules

20

IMS

A/C PgmName Mod Kit & Install Updates Design Comp (A1.2)

Name S/W Del (A2.6)

Prime Resp: Name

Bus Ops Resp: Name

Contract No: FXXXXX-XX-D-XXXX Schedule No: 1.0

Status as of: MM-DD-YYTier 1 Program Master Schedule

Contractual

* CustomerTier I

Anticipated Early Completion

Slide

SymbologyLegend

Air Vehicle(WBS 110000)

Aircrafts Pre-Mod, I&CO, & DD250(WBS 130000)

Logistics(WBS 400000)

Major Milestones

(Name) Software(WBS 122000)

Page 1 of 1File Name:SampleFile Name Tier1.ppt

31 Mar14 May17 Apr

Undefinitized C/A

J F M A M JJ A S O N D

Calendar YearJ F M A M JJ A S O N D J F M A M JJ A S O N D J F M A M JJ A S O N D

2007 2008 2009 2010

Contract Definitization

Program SupportComplete (E13, E16)

(Program Name) Program


2006

Test & Evaluation(WBS 300000)

Sys Engr/Prog Mgmt(WBS 200000/220000)

17 Apr

17 Jan

Final Design Review (FDR) (A1.1)

17 Apr

14 Oct

A/C 2 Accept Test Comp (A9.10)

31 Jul 18 Dec

Tech Pubs Comp

(E3,A3.4)

31 Oct

16 Jun

Sys Engr Comp (A1.1)

PgmNameS/W Design & Dev Comp (E2, A2.6)

9 Feb 1 Jun

S/W Des & Code Comp (A2.2)

8 Feb

10 MarA/C 1 I&CO Comp (A6.9)

16 AprA/C 1 Accept Test Comp (AC6.13.2)

9 May

16 JunIn-Kingdom Demo Comp (A8.1)

15 Oct

A/C 2 DD250 (A9.11)

16 Mar

A/C 3 DD250 (A10.9)

3 Aug

A/C 4 DD250 (A11.9)

21 Dec

A/C 5 DD250 (A12.9)1 Oct


13 MarA/C 3 Accept Test Comp (A10.8)


A/C 5 I&CO Comp (A12.6)

15 Jul


31 Mar

Final Data Del (A13.1)

26 Nov

21 Dec

PgmName Engr Design Comp (E1)

21 Dec

A/C 5 Del (E12)

9 May

CONUS Demo Comp (E7)

16 JunIn-Kingdom Demo Comp (E8)

17 AprA/C 1 Del

(E6)

15 OctA/C 2 Del (E9)

3 Aug

A/C 4 Del (E11)

16 MarA/C 3 Del

(E10)

17 JanFDR

Contract Award (A9.8)

13 Apr

A/C 4 Pre-Mod & I&CO

Start (AC11.6.1)

31 Aug

A/C 5 Pre-Mod & I&CO Start

(AC12.6.1)

4 Dec

System Test Plan Comp (AC6.5.1)

14 Aug

E28 Cab Dwg Rel Start (AC1.2.2)

18 May

PMR #1 Comp(AC13.2.1)

11 Dec


31 Mar

Program SupportComplete (E13)

7 Mar

1 Aug

TRR Comp (AC6.11.1,AC13.2.6)

14 Apr

Trng Course Matl Dev/Prep Comp (A4.2)

Training Conduct

Comp (A4.3)


S/W Req Comp (A2.1)

Engr Test&Eval Comp (A6.12)

1 AprCONUS Demo Comp (AC7.1.3)

S/W Qual Test Comp (A2.4)

A/C 1 Pre-Mod & I&CO Start (A6.3)

S/W Unit/Integr Test Start

(A2.3)

I&CO I&CO

I&CO

17 Apr

17 Apr

17 Apr

31 Jul

17 Apr

17 Apr

Start

Start

Start

Start

Start

A/T

A/T

A/T A/T

A/T

Start

30 Apr

Final DwgsComp (D&A /

Install) (AC1.2.2,1.2.3)

PgmName Flight Test Proc Comp

(AC6.12.5)

Ground Accept Test Proc Comp (AC6.13.1)

30 Apr

Master TrainingPlan Comp (A4.1)

Revisions/Approvals

Pre-Mod

Pre-Mod

A/C 1 DD250 (A6.14)


12 NovA/C 3 Pre-

Mod & I&CO Start

(AC10.6.1)

Pre-Mod

Pre-ModI&CO

7 Dec

30 May

Mission Systems/Mod Kits Delivery(WBS 120000/117000)

PgmName Miss Sys Design Comp (A1.2)

31 Oct

A/C 1 Mod Kit DD250 (AC6.3.3)

31 Mar



30 Jun


31 Jul


17 Apr28 Nov

Pre-Mod

Baseline 27 Sep 06

I&CO Readiness Review Comp

25 Oct

I&CO Readiness

Review Comp (A6.1)

10 Jul

22 Nov

21 Dec

PgmNameEngr Design Comp (E1)

6 Dec

11 Jan

11 Jan

System & MS&ISS Specs Comp

(AC1.1.1, AC13.1.2) 16 Nov

4 Sep

28 Sep

7 Feb

A/C 2 Pre-Mod &

I&CO Start

(AC9.8.1)1 Jul

Start

SCR 1317 2 Apr 07

SCR 1327 17 Apr 07

27 Apr

18 Apr

30 Aug

SCR 1329 30 May 07

24May

17 Aug

SCR 1342 27 Jul 07

SCR 1347 27 Jul 07

SCR 1343 9-Aug 07

25 Oct

31 Mar S/W Complete (CLIN 3400AD)

31 OctPgmNameEngr & Design Comp (CLIN 3400AA)

1 Feb

Spares Complete(CLIN 3400AF)

30 Nov

A/C 1 Interim Contractor Support Comp (CLIN 4400)

21 Dec

Extended Interim Contractor Support

Complete (IMP AC14.1.2)

SCR 1358 17-Aug 07

30 Jun

I&CO

31 Aug

4 Dec

A/C 2-5 I&CO Option (CLINs3403AB, 3404AB)

31 Dec

SCR 1370 7 Sep 07

SCR 1375 24 Sep 07

19 Sep


Name S/W Del (A2.6)

Prime Resp: Name

Bus Ops Resp: Name



Contractual

* CustomerTier I


Slide

SymbologyLegend




Major Milestones



31 Mar14 May17 Apr

Undefinitized C/A



2007 2008 2009 2010





2006



17 Apr

17 Jan


17 Apr

14 Oct


31 Jul 18 Dec

Tech Pubs Comp

(E3,A3.4)

31 Oct

16 Jun



9 Feb 1 Jun


8 Feb



9 May


15 Oct

A/C 2 DD250 (A9.11)

16 Mar

A/C 3 DD250 (A10.9)

3 Aug

A/C 4 DD250 (A11.9)

21 Dec

A/C 5 DD250 (A12.9)1 Oct





15 Jul


31 Mar


26 Nov

21 Dec


21 Dec

A/C 5 Del (E12)

9 May



17 AprA/C 1 Del

(E6)


3 Aug

A/C 4 Del (E11)

16 MarA/C 3 Del

(E10)

17 JanFDR


13 Apr


Start (AC11.6.1)

31 Aug

A/C 5 Pre-Mod & I&CO Start

(AC12.6.1)

4 Dec


14 Aug


18 May


11 Dec


31 Mar


7 Mar

1 Aug

TRR Comp (AC6.11.1,AC13.2.6)

14 Apr


Training Conduct

Comp (A4.3)


S/W Req Comp (A2.1)






(A2.3)

I&CO I&CO

I&CO

17 Apr

17 Apr

17 Apr

31 Jul

17 Apr

17 Apr

Start

Start

Start

Start

Start

A/T

A/T

A/T A/T

A/T

Start

30 Apr


Install) (AC1.2.2,1.2.3)


(AC6.12.5)


30 Apr


Revisions/Approvals

Pre-Mod

Pre-Mod

A/C 1 DD250 (A6.14)


12 NovA/C 3 Pre-

Mod & I&CO Start

(AC10.6.1)

Pre-Mod

Pre-ModI&CO

7 Dec

30 May



31 Oct


31 Mar



30 Jun


31 Jul


17 Apr28 Nov

Pre-Mod

Baseline 27 Sep 06


25 Oct

I&CO Readiness

Review Comp (A6.1)

10 Jul

22 Nov

21 Dec


6 Dec

11 Jan

11 Jan


(AC1.1.1, AC13.1.2) 16 Nov

4 Sep

28 Sep

7 Feb

A/C 2 Pre-Mod &

I&CO Start

(AC9.8.1)1 Jul

Start

SCR 1317 2 Apr 07

SCR 1327 17 Apr 07

27 Apr

18 Apr

30 Aug

SCR 1329 30 May 07

24May

17 Aug

SCR 1342 27 Jul 07

SCR 1347 27 Jul 07

SCR 1343 9-Aug 07

25 Oct



1 Feb


30 Nov


21 Dec



SCR 1358 17-Aug 07

30 Jun

I&CO

31 Aug

4 Dec


31 Dec

SCR 1370 7 Sep 07

SCR 1375 24 Sep 07

19 Sep

Calendar based• Framework for planning packages and ultimately work packages• Facilitate resource needs estimating and use planning• Track progress and completion status• Basis for determining progress against planned efforts including

start/finish/duration• Key supplier events


Translating IMP into IMS content

21

• Program Events (PEs)• SAs and ACs

Tier 1 – Events and tasksTier 2 – Events and tasksTier 3 – Events and tasksTier 4 – Events and tasks

IMSIMSIMPIMP


Name S/W Del (A2.6)

Prime Resp: Name

Bus Ops Resp: Name



Contractual

* CustomerTier I


Slide

SymbologyLegend




Major Milestones



31 Mar14 May17 Apr

Undefinitized C/A



2007 2008 2009 2010





2006



17 Apr

17 Jan


17 Apr

14 Oct


31 Jul 18 Dec

Tech Pubs Comp

(E3,A3.4)

31 Oct

16 Jun



9 Feb 1 Jun


8 Feb



9 May


15 Oct

A/C 2 DD250 (A9.11)

16 Mar

A/C 3 DD250 (A10.9)

3 Aug

A/C 4 DD250 (A11.9)

21 Dec

A/C 5 DD250 (A12.9)1 Oct





15 Jul


31 Mar


26 Nov

21 Dec


21 Dec

A/C 5 Del (E12)

9 May



17 AprA/C 1 Del

(E6)


3 Aug

A/C 4 Del (E11)

16 MarA/C 3 Del

(E10)

17 JanFDR


13 Apr


Start (AC11.6.1)

31 Aug

A/C 5 Pre-Mod & I&CO Start (AC12.6.1)

4 Dec


14 Aug


18 May


11 Dec


31 Mar


7 Mar

1 Aug

TRR Comp (AC6.11.1,AC13.2.6)

14 Apr


Training Conduct

Comp (A4.3)


S/W Req Comp (A2.1)






(A2.3)

I&CO I&CO

I&CO

17 Apr

17 Apr

17 Apr

31 Jul

17 Apr

17 Apr

Start

Start

Start

Start

Start

A/T

A/T

A/T A/T

A/T

Start

30 Apr


Install) (AC1.2.2,1.2.3)


(AC6.12.5)


30 Apr


Revisions/Approvals

Pre-Mod

Pre-Mod

A/C 1 DD250 (A6.14)


12 NovA/C 3 Pre-

Mod & I&CO Start

(AC10.6.1)

Pre-Mod

Pre-ModI&CO

7 Dec

30 May



31 Oct


31 Mar



30 Jun


31 Jul


17 Apr28 Nov

Pre-Mod

Baseline 27 Sep 06


25 Oct

I&CO Readiness

Review Comp (A6.1)

10 Jul

22 Nov

21 Dec


6 Dec

11 Jan

11 Jan


(AC1.1.1, AC13.1.2) 16 Nov

4 Sep

28 Sep

7 Feb

A/C 2 Pre-Mod &

I&CO Start

(AC9.8.1)1 Jul

Start

SCR 1317 2 Apr 07

SCR 1327 17 Apr 07

27 Apr

18 Apr

30 Aug

SCR 1329 30 May 07

24May

17 Aug

SCR 1342 27 Jul 07

SCR 1347 27 Jul 07

SCR 1343 9-Aug 07

25 Oct



1 Feb


30 Nov


21 Dec



SCR 1358 17-Aug 07

30 Jun

I&CO

31 Aug

4 Dec


31 Dec

SCR 1370 7 Sep 07

SCR 1375 24 Sep 07

19 Sep


Name S/W Del (A2.6)

Prime Resp: Name

Bus Ops Resp: Name



Contractual

* CustomerTier I


Slide

SymbologyLegend




Major Milestones



31 Mar14 May17 Apr

Undefinitized C/A



2007 2008 2009 2010





2006



17 Apr

17 Jan


17 Apr

14 Oct


31 Jul 18 Dec

Tech Pubs Comp

(E3,A3.4)

31 Oct

16 Jun



9 Feb 1 Jun


8 Feb



9 May


15 Oct

A/C 2 DD250 (A9.11)

16 Mar

A/C 3 DD250 (A10.9)

3 Aug

A/C 4 DD250 (A11.9)

21 Dec

A/C 5 DD250 (A12.9)1 Oct





15 Jul


31 Mar


26 Nov

21 Dec


21 Dec

A/C 5 Del (E12)

9 May



17 AprA/C 1 Del

(E6)


3 Aug

A/C 4 Del (E11)

16 MarA/C 3 Del

(E10)

17 JanFDR


13 Apr


Start (AC11.6.1)

31 Aug

A/C 5 Pre-Mod & I&CO Start (AC12.6.1)

4 Dec


14 Aug


18 May


11 Dec


31 Mar


7 Mar

1 Aug

TRR Comp (AC6.11.1,AC13.2.6)

14 Apr


Training Conduct

Comp (A4.3)


S/W Req Comp (A2.1)






(A2.3)

I&CO I&CO

I&CO

17 Apr

17 Apr

17 Apr

31 Jul

17 Apr

17 Apr

Start

Start

Start

Start

Start

A/T

A/T

A/T A/T

A/T

Start

30 Apr


Install) (AC1.2.2,1.2.3)


(AC6.12.5)


30 Apr


Revisions/Approvals

Pre-Mod

Pre-Mod

A/C 1 DD250 (A6.14)


12 NovA/C 3 Pre-

Mod & I&CO Start

(AC10.6.1)

Pre-Mod

Pre-ModI&CO

7 Dec

30 May



31 Oct


31 Mar



30 Jun


31 Jul


17 Apr28 Nov

Pre-Mod

Baseline 27 Sep 06


25 Oct

I&CO Readiness

Review Comp (A6.1)

10 Jul

22 Nov

21 Dec


6 Dec

11 Jan

11 Jan


(AC1.1.1, AC13.1.2) 16 Nov

4 Sep

28 Sep

7 Feb

A/C 2 Pre-Mod &

I&CO Start

(AC9.8.1)1 Jul

Start

SCR 1317 2 Apr 07

SCR 1327 17 Apr 07

27 Apr

18 Apr

30 Aug

SCR 1329 30 May 07

24May

17 Aug

SCR 1342 27 Jul 07

SCR 1347 27 Jul 07

SCR 1343 9-Aug 07

25 Oct



1 Feb


30 Nov


21 Dec



SCR 1358 17-Aug 07

30 Jun

I&CO

31 Aug

4 Dec


31 Dec

SCR 1370 7 Sep 07

SCR 1375 24 Sep 07

19 Sep

Lower level tasks

Sequential Flow on Vertical AxisSequential Flow on Horizontal Axis

Lesson 3 – Develop an IMS using PMA


Example: CWBS Dictionary

22

Element Task Description

Technical Content:The Air Vehicle element task description refers to the effortrequired to develop, fabricate, integrate and test theairframe segment, portions of the Navigation/Guidanceelement, and Airborne Development Test Equipment andAirborne Operational Test Equipment and to the integrationassembly and check-out of these complete elements,together with the Engine Segment, to produce the completeAir Vehicle. The lower-level elements included and summarized in the Air Vehicle element are:

Airframe Segment (A11100), Navigation GuidanceSegment (A32100), Airborne Development TestEquipment (A61100), and Airborne Operational TestEquipment (A61200)

Cost Description

Cost Content–System ContractorThe cost to be accumulated against this element includesa summarization of all costs required to plan, develop,fabricate, assemble, integrate and perform developmenttesting, analysis and reporting for the air vehicle. It alsoincludes all costs associated with the required efforts in integrating, assembling and checking our GFP required to create this element.

Applicable SOW Paragraph3.6.2

MPC/PMCA10100

Work Order/Work AuthSee lower levelWBS Elements

Specification No.689ED78780028

Specification Title:Prime Item DevelopmentSpecification for AGM 86A Air Vehicle/Airframe

Date Revision No. Revision Auth Approved Chg

WBS ElementA10100

WBS TitleAir Vehicle

ContractLine Item:

0001, 0001AA, 0001AB, 0001AC, 0001AD0001AE, 0001AF, 0001AG, 0001AH

Index Item No. 2 WBS Level 2Contract NumberF33657-72-C-0923

Lesson 3: Relationships between Planning Elements


Systems Engineering Management Plan (SEMP)

23

Systems Engineering Management Plan (SEMP) describes the contractor's technical approach and proposed plan for the conduct, management, and control of the integrated

systems engineering effort.

1. Program Overview & Objectives2. Document Scope3. Applicable and Reference Documents4. SE Organizational Integration and Technical

Authority5. Systems Engineering Technical Processes6. SE Management Processes7. Integration with Program Management Efforts8. Transitioning Critical Technologies9. Integrated Environment for Systems

Engineering10. Additional and Specialty SE Activities11.Supporting Plans

SEMP


AccomplishmentsAccomplishmentsRepresent requirementsthat enable Capabilities.

AccomplishmentsAccomplishmentsRepresent requirementsthat enable Capabilities.

Program EventsProgram EventsDefine the availabilityof a Capability at a point in time.

Program EventsProgram EventsDefine the availabilityof a Capability at a point in time.

Work Work PackagePackageWork Work

PackagePackage


PackagePackage


PackagePackage


PackagePackage


PackagePackage


PackagePackage


PackagePackageWork Work

PackagePackageWork Work

PackagePackage

CriteriaCriteriaRepresent Work packages that fulfill Requirements.

CriteriaCriteriaRepresent Work packages that fulfill Requirements.

The structure of Integrated Technical Planning


Backups


Assessing Completeness

Achieve program technical objective• Discover and demonstrate related

findings of the assessment• Apply the Questions Framework to get

from the incomplete state to the complete state

• Correct deficiencies

26

Assess adequacy of integration of technical plans to ensure completeness• Identifying conflicts between plan elements• Identifying intermediate work products late or out of sequence• Identifying incompatible levels of detail• Identifying conflicts in the IMP/IMS

File name.ppt | 1

BOEING PROPRIETARY

Integrated Program Planning

Executable ??IMP/IMS

=Risks

ExitCriteria

WBS EVM

SOW

Processes

CDRLs Requirements

File name.ppt | 1

Integrated Program Planning

ExecutableIMP/IMS=

Risks

ExitCriteria

CDRLs Requirements

WBS EVM

SOW

Processes

Questions


Purpose

27

Steps 1 & 2: Determine the intended program state

Step 1: Collect customer provided descriptions of their needs and conceptsa) RFP/ BAA/ RFA etc.b) JCIDS Functional Needs Analysis (FNA)c) JCIDS Functional Solutions Analysis (FSA)d) Initial Capabilities Document (ICD)e) Analysis of Alternatives (AoA)f) Capabilities Development Document (CDD)

Step 2: determine where your program is in the acquisition life cyclea) Identify the Program Events (PEs), e.g. ITR, ASR, SRR, etc.b) Identify technical objectives associated with events


28

“Questions focus”

Technical guidance is available for major program stages

A top-Down, question-based constructdrives Integrated Planning by establishing a framework

for robust, successful program execution & RFP responses

Questions & Product Flow Use Product Flow but add Questions philosophy if trying new methods & technologies

A B CMateriel Solution AnalysisMateriel Materiel Development Development DecisionDecision

Post-PDR Assessment







TechnicalReviews

Post-CDR Assessment

FRP Decision Review


DisposalDisposal

ITR

TechnicalBaseline

ASR



SystemDesign

Specification

SFR



less than MDAP

Allocated Baseline

PDR

CDR


TRR SVR/FCA/PRR

ISRPCA

Product Baseline

PhasesA B C

Materiel Solution AnalysisMateriel Materiel Development Development DecisionDecision

Post-PDR Assessment







TechnicalReviews

Post-CDR Assessment

FRP Decision Review


DisposalDisposal

ITR

TechnicalBaseline

ASR



SystemDesign

Specification

SFR



less than MDAP

Allocated Baseline

PDR

CDR


TRR SVR/FCA/PRR

ISRPCA

Product Baseline

Phases

How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011...

Documents

Transcript of How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011...