Presentation is loading. Please wait.

Presentation is loading. Please wait.

How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011 In order of Appearance: Bob Scheurer Bill Jennings.

Similar presentations

Presentation on theme: "How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011 In order of Appearance: Bob Scheurer Bill Jennings."— Presentation transcript:

1 How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011 In order of Appearance: Bob Scheurer Bill Jennings Shawn Simmons 1

2 Integrated Technical Planning Successful Programs Begin with Good Planning …But what is good planning???

3 Integrated Technical 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

4 Integrated Technical Planning 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!

5 Integrated Technical 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, 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

6 Integrated Technical Planning 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

7 Integrated Technical Planning Integrated Planning Over the Acquisition Lifecycle 7 ABC Materiel Solution Analysis Materiel Development Decision PDRCDR Post-CDR Assessment Post-PDR Assessment Engineering and Manufacturing Development (Program Initiation) Technology Development Operations and Support FRP Decision Review Production and Deployment Defense Acquisition Management System, May 22, 2009 extrapolated Competitive Prototyping 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 IOCFOC Pre-Systems Acquisition Systems Acquisition Sustainment = Decision Point= Milestone Review= Decision Point LRIP/IOT&E

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

9 Integrated Technical Planning 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 & Opportunities Inputs to Earned Value Management System Integrated Master Schedule (IMS) with Activity Networks (when) Cost Estimates (resource management) 9 Integrated & Traceable

10 Integrated Technical Planning 10 And the Planning Needs to Continue: Plan the Work / Work the Plan … for Each Phase Planning AC CBA B ICD Technology Development Engineering and Manufacturing Development Production and Deployment Materiel Solution Analysis MDD CPDCDD O&S FRP DR PDRCDR Executing

11 Integrated Technical Planning 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

12 Integrated Technical Planning Getting Started – Identifying the Planning Elements 12 RFP/BAA/ECP CLINs/ CDRLs/SDRLs Customer SEP SOO/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 Planning Checklists Process Guides Methods & Tools Process Networks DAG RFP – Request for Proposal SDRL – Supplier Data Requirements List SEMP – Systems Engineering Management Plan SEP – System Engineering Plan SOO – Statement of Objectives SOW – Statement of Work TEP – Team Execution Plan WBS – 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 Announcement BPI – Business Process Instruction BPG – Business Process Guide CLINs – Contract Line Item Numbers DAG – Defense Acquisition Guidebook ECP – Engineering Change Proposal IMP – Integrated Master Plan IMS – Integrated Master Schedule PEP – Program Execution Plan

13 Integrated Technical Planning Technical Plan Documents – The Logical Connectivity Flow and Interfaces Between Planning Elements 13 Questions SOWWBS Processes SOO CSOW CWBS Planning Packages SEMP Checklists Program Specific Risks IMP IMS Iterate to align & add detail Program Plans Technical Plan Documents Contract SOW Planning Packages PEP/TEPs/ O B S Organizational Breakdown Structure SEMP SEMP & Supporting Technical Plans IMPIMS IMP & IMS Contract WBS Customer/Acquirer Industry Guidance Contractor SAs and ACs OBS RAM

14 Integrated Technical Planning Summary of Program Planning Building Blocks 14 Build-up of Details Foundation/ Inputs BAA – Broad Agency Announcement CLINs – Contract Line Item (Numbers) CSOW – Contract Statement of Work CWBS – Contract Work Breakdown Structure DAG – Defense Acquisition Guidance EVM – Earned Value Management PBS – Product Breakdown Structure PEP – Program Execution Plan RFP – Request for Proposal SEMP – Systems Engineering Management Plan SEPMQC – SE Proposal Maturity Quality Checklist SOO – Statement of Objectives SOW – Statement of Work WBS – Work Breakdown Structure Integrated Master Schedule Tiers 3 and Below Estimates Contracts Facilities Operating Plan Financials Budget EVM Labor/ Skills CWBS Processes Organization Integrated Master Plan CSOW RFP/ BAA/ SOO/ SOW/ WBS/ CLINs/ Referenced Documents PEP SEMP Manuf, Support, Test Plans Planning Guidance DAG/ Questions/Checklists Command Media PBS Work Packages Planning Packages -Customer-P. Mgmt/ Finance -P. Mgmt & Engr -Engineering Integrated Master Schedule Tiers 1 & 2 Iterate these to add detail Success Criteria Other Supporting Plans Major Questions & Products

15 Integrated Technical Planning 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 Operation of the Defense Acquisition System Defense Acquisition Management System Material Solution Analysis, Technology Development, Engineering & Manufacturing Development, etc. phases 15

16 Integrated Technical Planning Purpose 16 The Defense Acquisition Guidebook Focuses on the Technical Baselines and Maturing the Technologies/Designs Focus On Technical Baselines A BC Materiel Solution Analysis Materiel Development Decision Post-PDR Assessment Engineering and Manufacturing Development Technology Development Operations and Support Production and Deployment Prototyping System Design IBR OTRR AOTR TRA Program Reviews with a technical basis Technical Reviews Post-CDR Assessment FRP Decision Review Sustainment Disposal ITR Technical Baseline ASR Preferred System Concept SRR Prototype Technical Reviews System Design Specification SFR System Functional Baseline PDR may occur after MS B for less than MDAP Allocated Baseline PDR CDR Initial Product Baseline TRR SVR /FCA /PRR ISR PCA 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 Review OTRR - Operational Test Readiness Review PCA - Physical Configuration Audit PDR - Preliminary Design Review PRR - Production Readiness Review SFR - System Functional Review SRR - System Requirements Review SVR - System Verification Review TRA - Technology Readiness Assessment TRR - Test Readiness Review

17 Integrated Technical Planning 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 Critical Tasks and Work Products Program Reviews/ Events Program Reviews TPMs Process and Measures UpdatedBeyer / ShannonStrand / MAJ Byers SoS/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 & 3One Team Management. Required changes implemented in a timely manner. SAAC Event LSI Owner(s) / LSI Manager PMUA / TRADOC Closure Criteria Questions IMP IMS JFCOM DoD

18 Integrated Technical Planning Planning information availability by phase 18 Materiel Solution Analysis Technology Development 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 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

19 Integrated Technical Planning 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 19 Event-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

20 Integrated Technical Planning 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 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

21 Integrated Technical Planning Translating IMP into IMS content 21 Program Events (PEs) SAs and ACs Tier 1 – Events and tasks Tier 2 – Events and tasks Tier 3 – Events and tasks Tier 4 – Events and tasks IMS IMP Lower level tasks Sequential Flow on Vertical Axis Sequential Flow on Horizontal Axis Lesson 3 – Develop an IMS using PMA

22 Integrated Technical Planning Example: CWBS Dictionary 22 Lesson 3: Relationships between Planning Elements

23 Integrated Technical Planning 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 & Objectives 2.Document Scope 3.Applicable and Reference Documents 4.SE Organizational Integration and Technical Authority 5.Systems Engineering Technical Processes 6.SE Management Processes 7.Integration with Program Management Efforts 8.Transitioning Critical Technologies 9.Integrated Environment for Systems Engineering 10. Additional and Specialty SE Activities 11.Supporting Plans SEMP

24 Integrated Technical Planning Accomplishments Represent requirements that enable Capabilities.Accomplishments Program Events Define the availability of a Capability at a point in time. Program Events Define the availability of a Capability at a point in time. Work Package Criteria Represent Work packages that fulfill Requirements.Criteria The structure of Integrated Technical Planning

25 Integrated Technical Planning Backups

26 Integrated Technical Planning 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 Integrated Program Planning Executable IMP/IMS = Risks Exit Criteria CDRLs Requirements WBS EVM SOW Processes Questions

27 Integrated Technical Planning Purpose 27 Steps 1 & 2: Determine the intended program state Step 1: Collect customer provided descriptions of their needs and concepts a)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 cycle a)Identify the Program Events (PEs), e.g. ITR, ASR, SRR, etc. b)Identify technical objectives associated with events

28 Integrated Technical Planning 28 Questions focus Technical guidance is available for major program stages A top-Down, question-based construct drives 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

29 Integrated Technical Planning Good Planning is Valuable 29 From Blanchard and Fabrycky, Systems Engineering and Analysis, 4 th Edition

30 Integrated Technical Planning Integrated Planning Uses the Development Planning, Systems Engineering, and Developmental Test & Evaluation Framework 30 Development Development Planning DP (Early SE) SE DT&E LCS DP: Development Planning DT&E: Developmental Test and Evaluation LCS: Life Cycle Sustainment SE: System Engineering CBA: Capabilities Based Assessment CDD: Capability Development Document CPD: Capability Production Document ICD: Initial Capabilities Document MDD: Materiel Development Decision A C CBA B ICD Technology Development Engineering and Manufacturing Development Production and Deployment Materiel Solution Analysis MDD CPDCDD O&S FRP DR PDRCDR

31 Integrated Technical Planning 31 Weapon System Acquisition Reform Law (2009) Defense Acquisition Management System Systems Engineering Plan Preparation Guide …With Law, Policy, and Guidance!!! The DoD Customer is Trying to Help…

Download ppt "How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011 In order of Appearance: Bob Scheurer Bill Jennings."

Similar presentations

Ads by Google