Presentation on theme: "In order of Appearance: Bob Scheurer Bill Jennings Shawn Simmons"— Presentation transcript:
1 In order of Appearance: Bob Scheurer Bill Jennings Shawn Simmons How to Start a Successful Program A Panel Discussion for Midwest Gateway INCOSE Chapter May 25, 2011In order of Appearance:Bob ScheurerBill JenningsShawn Simmons
2 “Successful Programs Begin with Good Planning” …But what is good planning???
3 Good Planning:Combines the management approach with the technical solution definition/derivationEncompasses the holistic view of planning and engineering for the complete system lifecycleContinuous across pre-contract, post-award planning, and program execution
4 Good Planning Drives Execution Successful Program Execution is dependent onClarity of program objectives and requirementsClarity of activities, schedules, deliverables, resourcesEarly identification of needsViewing requirements in terms of the entire system life cycleIntegration of top-down needs and bottom-up solutionsFlexibility in response to changing conditions - updatesAll of these depend on good planning!
5 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).
6 Could something else be missing, too?: Integration Localized Technical Planning is Not EnoughToo Many Disconnected Program VisionsInefficiencies from Plan Redundancies and InconsistenciesGaps in Planning DetailsIntegrated Technical Planning is the Gateway to Program SuccessOrganized and DisciplinedAligned Planning ProcessesInstituted at the Very Beginning of an InitiativeDescribes Transformation from Problem (Requirements) to DesignOn-Going Updates and Coordination
7 Integrated Planning Over the Acquisition Lifecycle Defense Acquisition Management System, May 22, 2009 extrapolatedThe Materiel Development Decision precedes entry into any phase of the acquisition management systemEntrance criteria met before entering phaseEvolutionary Acquisition or Single Step to Full CapabilityUser NeedsTechnology Opportunities & ResourcesATechnology DevelopmentBCIOCFOC(Program Initiation)Technological Maturity and Integration Risk AssessmentMateriel Solution AnalysisEngineering and Manufacturing DevelopmentProduction and DeploymentOperations and SupportFRP DecisionReviewCompetitivePrototypingPDRCDRLRIP/IOT&EPre-Systems AcquisitionSystems AcquisitionSustainmentMateriel Development DecisionPost-PDR AssessmentPost-CDR Assessment= Decision Point= Milestone Review= Decision Point
8 Outcome of Int. Tech. Planning Outcome is an Integrated Technical View 1.0WBS2.03.02.12.22.3WBS / PBSSOWContractSRR SDR PDR.…Lifecycle PhasesWork Product 1 Final Update UpdateWork Product 2 Prelim Final UpdateWork Product N - - -WorkProductsIMP/IMSEventsSignificant AccomplishmentsAccomplishment Criteria - -CDRLsSEITPMIPTFltEESWOrganizationRAMSEMPPEPTEPRMPgm PlansPlansSOOSRR SFR PDR.Lifecycle Phases / EventsStandardDeckDeck +MetricsSig Accom (SA) - Acc Crit (AC)Sig Accom (SA)- Acc Crit (AC)AirframeWingSW Integration LabSystem Integration LabProgram Customized Plan(Basis for Proposal Estimate & Schedule)Detailed / Refined Technical PlanDetailed Functional Work FlowsGate CGate DATPIBRPlanMaturationSRRPDRCDRTRRWork ProductRepositorySFR
9 Elements of the Integrated Planning Integrated & TraceableStatement 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 eventsReviews and AuditsSystems Engineering Management Plan (SEMP) (what the supplier has planned) and Systems Engineering Plan (SEP) (what the acquirer/customer has planned)Technical Performance MeasuresSubordinate Plans (risk mgt, reqts mgt, trade studies, etc.)Test and Evaluation Master Plan (TEMP)Integrated Logistics Plan (for Operations and Support)Use of SuppliersResource 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 SystemIntegrated Master Schedule (IMS) with Activity Networks (when)Cost Estimates (resource management)
10 Engineering and Manufacturing Development Production and Deployment And the Planning Needs to Continue: Plan the Work / Work the Plan … for Each PhaseACCBABICDTechnologyDevelopmentEngineering and Manufacturing DevelopmentProduction and DeploymentMaterielSolutionAnalysisMDDCPDCDDO&SFRP DRPDRCDRPlanningExecuting
11 Overview Summary of Integrated Technical Planning Performed Regularly Across the Total System LifecycleEncompasses a Diverse Set of Views to Form the Complete Planning PictureReceives Guidance for Constructing the Various Plans from:Customer DocumentsSystems Engineering ProcessProduct Architecture (Product Components via Modeling)IMP/IMS
12 Getting Started – Identifying the Planning Elements RFP/BAA/ECPCLINs/CDRLs/SDRLsCustomer SEPSOO/SOWCustomer DocumentsTechnical Plan DocumentsContract SOWPlanning PackagesPEP/TEPs/Organizational Breakdown StructureSEMP &Supporting Technical PlansIMP & IMSContract WBSMethods & ToolsQuestions FrameworksProcess GuidesProcess NetworksPlanningChecklistsDAGBAA – 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 PlanRFP – Request for ProposalSDRL – Supplier Data Requirements ListSEMP – Systems Engineering Management PlanSEP – System Engineering PlanSOO – Statement of ObjectivesSOW – Statement of WorkTEP – Team Execution PlanWBS – Work Breakdown StructureCDRL:Contract Data Requirements ListContract Deliverable Requirements ListContract Document Requirements ListContractor Data Requirements ListCustomer Data Requirements List
13 Program Specific Risks Technical Plan Documents – The Logical Connectivity Flow and Interfaces Between Planning ElementsTechnical Plan DocumentsContract SOWPlanning PackagesPEP/TEPs/Organizational Breakdown StructureSEMP &Supporting Technical PlansIMP & IMSContract WBSCustomer/AcquirerSOOWBSSOWContractorCSOWCWBSQuestionsProgram PlansOBS RAMChecklistsIMPProcessesSEMPIterate to align & add detailIndustry GuidanceSA’s and AC’sProgram Specific RisksIMSPlanning Packages
14 Summary of Program Planning Building Blocks 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 StructureWork PackagesWork PackagesBuild-up of DetailsFinancialsFinancialsOperating PlanOperating PlanBudgetBudgetEVMEVMLabor/ SkillsLabor/ SkillsEstimatesEstimatesContractsContractsFacilitiesFacilitiesPlanning PackagesPlanning PackagesIntegrated Master Schedule Tiers 3 and BelowIntegrated Master Schedule Tiers 3 and BelowOther SupportingOther SupportingPEPPEPSEMPSEMPManufManuf, Support, Test Plans, Support, Test PlansIterate thesePlansPlansto add detailCSOWCSOWCWBSCWBSOrganizationOrganizationProcessesProcessesIntegrated Master Schedule Tiers 1 & 2Integrated Master Schedule Tiers 1 & 2Foundation/InputsIntegrated Master PlanIntegrated Master PlanPlanning GuidancePlanning GuidanceMajorMajorRFP/ BAA/ SOO/RFP/ BAA/ SOO/SOW/SOW/WBS/WBS/SuccessSuccessDAG/ Questions/ChecklistsQuestionsQuestionsPBSPBSCLINs/ Referenced DocumentsCLINs/ Referenced DocumentsCriteriaCriteriaCommand MediaCommand Media& Products& Products14-Customer-P. Mgmt/ Finance-P. Mgmt & Engr-Engineering14
15 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 SystemMaterial Solution Analysis, Technology Development, Engineering & Manufacturing Development, etc. phases
16 Focus On Technical Baselines The Defense Acquisition Guidebook Focuses on the Technical Baselines and Maturing the Technologies/DesignsPurposeABCMateriel Solution AnalysisMateriel Development DecisionPost-PDR AssessmentEngineering and ManufacturingDevelopmentTechnology DevelopmentOperations and SupportProduction and DeploymentPrototypingSystem DesignIBROTRRAOTRTRAProgram Reviewswith a technical basisTechnicalReviewsPost-CDR AssessmentFRP Decision ReviewSustainmentDisposalITRBaselineASRPreferred System ConceptSRRPrototypeSystemDesign SpecificationSFRFunctional BaselinePDR may occur after MS B for less than MDAPAllocated BaselinePDRCDRInitialProduct BaselineTRRSVR/FCA/PRRISRPCAPhasesFocus On Technical BaselinesTechnology Readiness AssessmentTechnical ReviewsProgram ReviewsDecision PointMilestone ReviewsDecision Point if PDR is not conducted before MS BAOTR - Assessment of Operational Test ReadinessASR - Alternative Systems ReviewCDR - Critical Design ReviewFCA - Functional Configuration AuditFRP – Full Rate ProductionIBR - Integrated Baseline ReviewISR - In-Service ReviewITR - Initial Technical ReviewOTRR - Operational Test Readiness ReviewPCA - Physical Configuration AuditPDR - Preliminary Design ReviewPRR - Production Readiness ReviewSFR - System Functional ReviewSRR - System Requirements ReviewSVR - System Verification ReviewTRA - Technology Readiness AssessmentTRR - Test Readiness Review
17 Questions Framework Formal Guidance Question-based Framework By Stage Question-Based Construct By StageProgram ReviewsJCIDS & DoDIQuestionsSub-questionsLower Level Tasks & I/OJFCOMQ #QuestionsSub-QuestionsWHENEntry,Early,DuringandSub-question inTask Format(Use Casenames)InputsLower Level TasksOutputs2Does the program have documentedcapability needs at the system level(Capability Description Document orequivalent)?1. Documented resolution ofconflicts, uncertainties, andambiguities within theprogram and with thecustomer2. Updated capability needs2.1Does the program havedocumented capability needsat the system level?EntryCollect thedocumentedcapability needs1. Possible sources --ORD/O&O, CDD,SRD, SPS, SOW,RFP (Sections L&Mand SOW)1. Identify the inputsthat may have2. Search the inputsfor capability needsConsolidated list of2.2Have these capability needsbeenreviewed forunderstandingby theprogram?EarlyReview thefor understandingby the program1. Review the needs2. Identify conflicts3. Identifyambiguities4. IdentifyDescription of conflicts,ambiguities anduncertainties2.3Have areas of potentialmisunderstanding or lack ofclarity been identified andresolved forconsensuswithinthe program and with thecustomer?Resolve theconflicts,uncertainties withthe customer1. Consolidated list of2. Description ofconflicts, ambiguitiesand uncertainties1. Hold discussionswith the stakeholdersto resolve the2. Update theDoDQuestionsIMP Significant Accomplishments & Accomplishment CriteriaIMS Tasks by IPTProgram Reviews/ EventsProgram Reviews/ EventsCritical Tasks and Work ProductsSignificant AccomplishmentsAccomplishment Criteria110050TPMs Process and Measures UpdatedBeyer / ShannonStrand / MAJ Byers1SoS/FoS TPMs updated & approved toreflect current program managementneedsSoS/FoS TPMs updated and approved to reflect currentprogram managementmonitoringas of SoSFR.Review and concurrence, subject to required changes,of theapproved TPMs by appropriate Tier 2 & 3One TeamManagement.Required changes implemented in a timelymanner.SAACEventLSI Owner(s) /LSI ManagerPMUA /TRADOCClosure CriteriaIMSIMP1717
18 Planning information availability by phase Available InformationAvailable InformationConcepts of OperationInitial system-level capabilitiesOperations analysis studiesTechnology readiness informationLifecycle cost estimatesFinalized system-level capabilitiesRequirementsFunctional architecture viewsPhysical architecture viewsPreliminary designKey supplier dataSubstantiated lifecycle cost estimatesMaterielSolutionAnalysisEngineering &Manufacturing DevelopmentViable set of system-level capabilities & requirementsConceptual architecture views & design conceptsTrade studies supporting draft capabilities & requirementsKey supplier dataDetailed lifecycle cost estimatesCompleted designComplete product assembled and testedManufacturing and assembly process in placeFully mature lifecycle cost estimatesTechnologyDevelopmentProduction &Deployment181818
19 Purpose of the Integrated Master Plan Serves as a contractual agreement with the customer on what will be doneDocuments program events (PEs)Identifies significant accomplishments (SAs) for each eventSpecify accomplishment criteria (ACs) for each Significant AccomplishmentProvides traceability to WBS, SOW, deliverables, risks, and opportunitiesProvides a framework for planning integration across the programRepresents the integrated product development encompassing all functional disciplinesProvides a common framework for developing the IMS and detailed team schedulesEvent-basedIMP1919
20 IMS Calendar based Purpose of the IMS Documented schedule of program eventsSpecify tasks to satisfy accomplishment criteria for each significant accomplishmentTask traceability to WBS, SOW, deliverables, & program milestonesTime-phased tasks and show predecessor and successor relationshipsTime-phased integrated product development encompassing all program teamsCommon framework for developing detailed team schedulesCalendar basedFramework for planning packages and ultimately work packagesFacilitate resource needs estimating and use planningTrack progress and completion statusBasis for determining progress against planned efforts including start/finish/durationKey supplier events2020
21 Translating IMP into IMS content Lesson 3 – Develop an IMS using PMATranslating IMP into IMS contentIMPIMSSequential Flow on Vertical AxisSequential Flow on Horizontal AxisTier 1 – Events and tasksTier 2 – Events and tasksTier 3 – Events and tasksTier 4 – Events and tasksProgram Events (PEs)SAs and ACsLower level tasks2121
23 Systems Engineering Management Plan (SEMP) Program Overview & ObjectivesDocument ScopeApplicable and Reference DocumentsSE Organizational Integration and Technical AuthoritySystems Engineering Technical ProcessesSE Management ProcessesIntegration with Program Management EffortsTransitioning Critical TechnologiesIntegrated Environment for Systems EngineeringAdditional and Specialty SE ActivitiesSupporting PlansSystems 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.2323
24 The structure of Integrated Technical Planning Program EventsDefine the availability of a Capability at a point in time.AccomplishmentsRepresent requirements that enable Capabilities.CriteriaRepresent Work packages that fulfill Requirements.Narration:Integrated Technical Planning describes the increasing maturing of a product or service through Events or Milestones, Accomplishments, Criteria, and Work Packages.Each Event or Milestone represents the availability of one or more capabilities.The presence of these capabilities is measured by the Accomplishments and their Criteria.Accomplishments are the pre-conditions for the maturity assessments of the product or service at each Event or Milestone.This hierarchy decomposes the System Capabilities into Requirements, Work Packages, and the activities the produce the deliverables. This hierarchy also describes increasing program maturity resulting from the activities contained in the Work Packages.Performance of the work activities, Work Packages, Criteria, Accomplishments, and Events or Milestones is measured in units of “physical percent complete” by connecting Earned Value with Technical Performance Measures.We will learn more about the lower level planning details and plans in course 5.Work PackageWork PackageWork PackageWork PackageWork PackageWork PackageWork PackageWork Package24
26 Assessing Completeness Integrated Program PlanningAchieve program technical objectiveDiscover and demonstrate related findings of the assessmentApply the Questions Framework to get from the incomplete state to the complete stateCorrect deficienciesSOWCDRLsRequirementsProcessesRisks=ExecutableQuestionsIMP/IMSWBSExitEVMCriteriaFile name.ppt|1Assess adequacy of integration of technical plans to ensure completenessIdentifying conflicts between plan elementsIdentifying intermediate work products late or out of sequenceIdentifying incompatible levels of detailIdentifying conflicts in the IMP/IMS
27 Steps 1 & 2: Determine the intended program state PurposeStep 1: Collect customer provided descriptions of their needs and conceptsRFP/ BAA/ RFA etc.JCIDS Functional Needs Analysis (FNA)JCIDS Functional Solutions Analysis (FSA)Initial Capabilities Document (ICD)Analysis of Alternatives (AoA)Capabilities Development Document (CDD)Step 2: determine where your program is in the acquisition life cycleIdentify the Program Events (PEs), e.g. ITR, ASR, SRR, etc.Identify technical objectives associated with events2727
28 Questions & Product Flow Technical guidance is available for major program stages“Questions focus”Questions & Product FlowUse Product Flow but add Questions philosophy if trying new methods & technologiesA top-Down, question-based construct drives Integrated Planning by establishing a framework for robust, successful program execution & RFP responses
29 Good Planning is Valuable From Blanchard and Fabrycky, “Systems Engineering and Analysis”, 4th Edition2929
30 Engineering and Manufacturing Development Production and Deployment Integrated Planning Uses the Development Planning, Systems Engineering, and Developmental Test & Evaluation FrameworkACCBABICDTechnologyDevelopmentEngineering and Manufacturing DevelopmentProduction and DeploymentMaterielSolutionAnalysisMDDCPDCDDO&SFRP DRPDRCDRDevelopmentDevelopment PlanningSEDP (Early SE)LCSDT&EDP: Development PlanningDT&E: Developmental Test and EvaluationLCS: Life Cycle SustainmentSE: System EngineeringCBA: Capabilities Based AssessmentCDD: Capability Development DocumentCPD: Capability Production DocumentICD: Initial Capabilities DocumentMDD: Materiel Development Decision3030
31 The DoD Customer is Trying to Help… Weapon SystemAcquisition Reform Law (2009)Defense Acquisition ManagementSystemSystems Engineering Plan Preparation Guide…With Law, Policy, and Guidance!!!3131
Your consent to our cookies if you continue to use this website.