Presentation on theme: "Systems Engineering in DoD"— Presentation transcript:
1 Systems Engineering in DoD Mr. Gordon Kranz Director, Major Program SupportOffice of the Director, Defense Research & Engineering/Systems Engineering
2 Bottom-line UpfrontDoD changes emphasize early stages of pre-systems acquisition - prior to Milestone B (MS B)Reduce risk before making business commitmentImprove likelihood of being able to meet commitmentsThe Weapon Systems Acquisition Reform Act of 2009 furthers this emphasis withadditional certification requirements at MS A and B,mandatory competitive prototyping, andsystem-level Preliminary Design Review [PDR] before MS B for all MDAPsKnowledge-based Acquisition – Starting Programs Right!
3 DoD Instruction 5000.02 Mandatory Materiel Development Decision Mandatory Milestone A for all “major weapon systems” requiring technology developmentMandatory system-level PDR and CDR with reports to and assessments by the Milestone Decision Authority (MDA)Strengthened MDA certifications at Milestones A and B3
4 Acquisition Reform - SE Thumbnail New legislation, Public Law , recognizes the importance of SE to weapon systems acquisitionHeavy focus on starting MDAPs right:Development and tracking of measurable performance criteria as part of SEPs and TESs / TEMPsRequiring completion of competitive prototypes for all Major Defense Acquisition ProgramsRequiring completion and MDA assessment of a system-level Preliminary Design Review before MS BCodifying a role for systems engineering in development planning, lifecycle management and sustainabilityYearly OSD assessment to Congress of Component capabilities for SE, development planning, and DT&E and of SE in MDAPs
5 Summary of Legislation The Weapon Systems Acquisition Reform Act of contains provisions that will:Address problems with unreasonable performance requirements by requiring DoD to reestablish systems engineering organizations and developmental testing capabilities; make trade-offs between cost, schedule and performance early in the program cycle; and conduct preliminary design reviews before giving approval to new acquisition programs;Address problems with unreasonable cost and schedule estimates by establishing a new, independent director of cost assessment to ensure that unbiased data is available for senior DoD managers;Address problems with the use of immature technologies by requiring the Director of Defense Research and Engineering to periodically review and assess the maturity of critical technologies and by directing the Department to make greater use of prototypes, including competitive prototypes, to prove that new technologies work before trying to produce them; andAddress problems with costly changes in the middle of a program by tightening the so-called “Nunn-McCurdy” requirements for underperforming programs.Excerpts from Bill Signing Ceremony Press Release – May 22, 20095
6 Impact of Acquisition Reform Legislation on Early Acquisition Policy Establishes Director, Systems Engineering (D, SE) and Director, Developmental Test and Evaluation (D, DT&E) as principal advisors to the Secretary of Defense and the USD(AT&L) on systems engineering and development planning and on developmental T&E, respectivelyMandates documented assessment of technological maturity and integration risk of critical technologies for MDAPs during the Technology Development (TD) phaseEstablishes D, DT&E and D, SE joint tracking and Congressional reporting on MDAP achievement of measurable performance criteriaMandates competitive prototyping and MDA completion of a formal Post-Preliminary Design Review Assessment for all MDAPs before MS B; additional MDA certification to both at MS BStrengthens technical analysis of cost and schedule breaches during the Technology Development (pre-MS B) and the Engineering and Manufacturing Development (post-MS B) phases
7 Acquisition Lifecycle Comparisons Defense Acquisition Management System, May 12, 2003ABC(Program Initiation)System Development and DemonstrationConcept RefinementTechnology DevelopmentProduction and DeploymentOperations and SupportDesignReadiness ReviewFull-RateProduction DecisionReviewConcept DecisionDefense Acquisition Management System, December 8, 2008ABC(Program Initiation)Materiel Solution AnalysisEngineering and Manufacturing DevelopmentProduction and DeploymentTechnology DevelopmentOperations and SupportFRP DecisionReviewPDRPDRCDRMateriel Development DecisionPDR after B w/ Post-PDR AssessmentPost-CDR AssessmentOrDefense Acquisition Management System, May 22, 2009ATechnology DevelopmentBC(Program Initiation)Technological Maturity and Integration Risk AssessmentMateriel Solution AnalysisEngineering and Manufacturing DevelopmentProduction and DeploymentOperations and SupportFRP DecisionReviewCompetitivePrototypingPDRCDRMateriel Development DecisionPost-PDR AssessmentPost-CDR Assessment7
8 DoD 5000.02 and PL 111-23 Change the Early Acquisition Landscape New 2366a & 2366b CertificationsLCSPPDRCDRMateriel Development Decision (MDD)Renewed emphasis on manufacturing across the lifecyclePDR, PDR Report to the MDA, and Post-PDR-AssessmentSystem-level CDR with an initial product baseline and a Post-CDR Report to the MDACompetitivePrototypesPost-CDR Assessment by the MDA between EMD sub- phasesWhat are the implications of these changes for programs and SEs?How can systems engineering enable the program during this early phase?
9 What This Means for Systems Engineers Systems engineering is now recognized in law as inherently necessary in requirements definition, development planning, and early acquisitionNeed for and focus of all engineering in the “pre-acquisition” phases (Materiel Decision Analysis and Technology Development) is dramatically altered:Earlier engineering involvement (well before Milestone A)More government expertise to plan for and oversee requirements definition, technology maturation, and competitive prototyping leading to fully expressed system design (the allocated baseline) at the system-level Preliminary Design Review
10 New Challenges for Programs Need for Program Office formation and PM skill-sets after MDD and prior to MS AIncreased importance of the Technology Development Strategy (TDS) (as a surrogate Acquisition Strategy) at MS ASchedule and funding shifts – EMD into TDEarlier engagement with industry and different contracting strategies for technology maturation, competitive prototyping, data rights, PDR before MS B, etc.Explicit need for earlier, formal SE process application (e.g., data, configuration, and risk management)
11 DDR&E Organization Director, Defense Research and Engineering (DDR&E) Honorable Zachary J. LemniosDirector, ResearchDr. David HoneyPrincipal Deputy Dr. André van TilborgDirector,Systems EngineeringMr. Stephen WelbyPrincipal Deputy Mr. Terry JaggersRapid FieldingMr. Earl WyattPrincipal Deputy Mr. Ben RileyDirector, Developmental Test & Evaluation (DT&E)Mr. Chris DiPetto (Acting)Principal Deputy Mr. Chris DiPettoDefense Advanced Research Projects Agency (DARPA)Dr. Regina DuganDefense Technical Information Center (DTIC)Mr. Paul RyanPrincipal DeputyMr. Alan R. Shaffer
12 New Emphasis on Development Planning and Early SE CCBABICDTechnologyDevelopmentEngineering and Manufacturing DevelopmentProduction and DeploymentMaterielSolutionAnalysisMDDCPDCDDO&SFRP DRPDRCDRDevelopment PlanningDevelopmentSEDP (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 Decision
13 Development Planning and Early SE Critical Activities MDDABCBAICDMateriel Solution AnalysisCDDTechnology DevelopmentSE Input to MDDEngagement in AoAEngineering AnalysisCONOPSAwareness of Strategic ContextEngagement with S&TEngagement with JCIDSGuidancePlanAnalysis ActivityReportConsideration of SOS/Interdependency, Interoperability ContextSEP for Milestone AInput to TDS (CTE, CPI), TES, CCESE in TD Contract RequirementsTech Reviews (ASR, Early SE Requirements)Prototyping & Risk ReductionPrototyping (Technology and Design)CTE TRL MaturationTrade StudiesSE Support for Technology Risk ReductionOversight of Competitive DesignsRisk AssessmentInput to Acquisition/ Planning, CARD, Budget & OtherSE in Contract RequirementsSE into the PDR Report to MDA, Acquisition Strategy, TEMP, CARD, and ICEEvidence of Strong SE ActivityPDR and PDR Report and AssessmentTechnical Reviews up to and including PDRSystems Engineering PlanStrong Reliability, Availability and Maintainability (RAM)Inputs to RequirementsSystem Requirements DefinitionRAM and SustainabilityRequirements Traceability MatricesTranslation of Requirements to ContractCapability Development Document (CDD)*Reference DAG Sections and
14 The Milestone A Planning Challenge Documents / activities / data requiring technical input from the Systems Engineer before Milestone A:Analysis of AlternativesTechnology Development StrategyCritical Program InformationTechnology maturation plansCompetitive Prototyping plansNet-Centric Data StrategyMarket ResearchData Management StrategyComponent Cost EstimateSystems Engineering PlanTest and Evaluation StrategyThe PM’s Dilemma: Where to find the data!?
15 Why Is This Hard?Program offices (both government and contractor) have very little experience with pre-MS B systems engineering activitiesThe DAG guidance is voluminous – online resource with over 750 printed pages in recent revisionProgram offices have limited understanding about interdependencies within the DAG guidanceNew implementing policy and DAG guidance in response to PL will not be available immediately
16 New Challenges for SEPs Explicit technical planning for the Technology Development phase at Milestone A (and subsequent Milestones) including:Technology maturationCompetitive prototypingManufacturing readiness as assessed in Tech ReviewsCritical Program Information in designItem Unique Identification (IUID) planningIntegration of RAM and HSI with SERole of Component Configuration Steering Board relative to requirements and configuration management processesMandatory system-level PDR before MS B for MDAPs and rationale for its placement before or after Milestone B for non-MDAPsPDR Report to the MDA either side of MS BPost-PDR Assessment by the MDA for MDAPs or if PDR after MS BMandatory system-level CDRPost-CDR Report to and Assessment by the MDA followed by an ADMIUID Implementation Plan as SEP Annex at Milestones B and C
17 SE Policy & Guidance Some Activities [Re] Adopted ISO/IEC Standards into ASSIST15288 [SE], [SWE, in progress], [Risk], [Measurement], [IEEE 1220]Reviewed ISO drafts[[in JTC1/SC7 for Systems & Software Engineering]24748 [guide for Life cycle management, [guide to 15288[,29148 [Requirements engineering]Reviewed GEIA/EIA draftsEIA-649 STD and HDBKGEIA-Std-927Under development in SESS [DDRE/SE approves]MIL-STD-189A Reliability Growth ManagementMil-Std Engineering drawingsOtherUpdated earlier cancellation of Mil-Std-973 to note that EIA-649 is a good alternativeAdopted ANSI/GEIA-STD-0009 [Reliability]led update of SEMP DID; ready to be posted in ASSISTIn process guide updates: SEP Prep, SE in Contracting, IMP/IMS, Risk Mgt, DAG/SE
18 SE Policy and Guidance Structure DoDData Flow:Acquisition PolicyDefense Acq GuidebookChapter 4SEChapter 8SecurityPolicy-specific guidance linked to . . .M&S GuidanceRisk Mgmt Guide“Wall Chart”PPPDoDI. . . all other relevant guidanceDoD M&S Mgt DoDDSE Slide RuleSEP Prep GuideSystems AssuranceGuideSafety/ESOH GuidesDoD M&S VV&ADoDIDM GuideDTMSupply Chain RiskManagementEW and C2W CountermeasuresDoDDSafety MIL-STD-882DFunctionalArchitectureDevelopmentGuideRAM GuideRAM-CRationale ReportManualContracting forSE GuidePPP Prep GuideDoD IADoDD ETech Review GuideCPI Security Classification GuideSOS SE GuideInteroperability &Supportability of IT &NSS DoDDCM Mil Hbk 61AIMP/IMS GuidePlannedCPI Identification ToolWBS Mil Hbk 881ExtentMOSA GuideAcq Security-RelatedPolicies & IssuancesToolOther Standards &Mil HandbooksPP Contract Language CompendiumOther DesignConsideration Guides
19 <Gordon.Kranz@osd.mil> If any who review this presentation have questions, feel free to contact Gordon Kranz at: