Presentation on theme: "Ref.: New Acquisition Policy by DAU, 20 May 2003, PMT-352"— Presentation transcript:
1 Ref.: New Acquisition Policy by DAU, 20 May 2003, PMT-352 Review of DoD’s New Acquisition Policy and its Impact on Programs and Systems Engineeringby Al Bruns INCOSE Gateway Chapter Wednesday, 30 July 2003Ref.: New Acquisition Policy by DAU, 20 May 2003, PMT-352
2 New Acquisition Policy Construct DoD DirectivePrinciples retained; innovation/flexibility emphasizedDoD InstructionFocused on required outcomes and statutory requirements and less on regulatory requirementsDoD Regulation RCancelled; becomes “guide” not a regulationProvides expectations (TEMP, C4ISP, etc..), best practices and lessons learned
3 The Defense Acquisition Management Framework DoDI , May 2003Technology Opportunities & User NeedsProcess entry at Milestones A, B, or CEntrance criteria met before entering phaseEvolutionary Acquisition or Single Step to Full Capability(ProgramInitiation)ABCIOCFOCConceptRefinementTechnologyDevelopmentSystem Development& DemonstrationProduction &DeploymentOperations &SupportNewDesignReadinessReviewFRPDecisionReviewConceptDecisionLRIP/IOT&EPre-Systems AcquisitionSystems AcquisitionSustainmentIncrement IIIncrement III
4 New Requirements Documents Common element is CAPABILITIESInitial Capabilities Document (ICD) replaces MNS at Milestone ADescribes desired capability. Evaluates multiple materiel approaches. Recommends a materiel approach.Capability Development Document (CDD) replaces ORD at Milestone BDescribes the SDD effort and provides KPPs for the increment. Describes program to get to complete solution.Capability Production Document (CPD) replaces ORD at Milestone CDescribes the SDD effort to produce materiel solution for the increment and provides KPPs for the production increment.Details will be implemented by CJCSI C & CJCSM
5 Technology Development Strategy Required ACAT I and IA programs. Based on AoA resultsContents:Rational for EA or single-step strategyFor EA, description of how program will be divided into technology spirals & development incrementsAppropriate limits on prototypes produced and deployed during the TD PhasePerformance Goals and Exit Criteria to be met prior to proceeding into SDD and producing additional prototypesOverall cost, schedule and performance goals for the total R&D effortSpecific cost, schedule and performance goals and exit criteria for the first technology spiral demonstration, and a test plan to ensure that they are met.
6 DoD Instruction 5000.2 New/Revised from previous 5000.2: Operation of the Defense Acquisition SystemNew/Revised from previous :“Concept Decision” - new decision point prior to Milestone AAnalysis of materiel approaches done prior to Concept Decision, and documented in Initial Capabilities Document (ICD). MNS is eliminated. New phase prior to Milestone A, “Concept Refinement”Analysis of Alternatives (AoA) due at Milestone A vice program initiation (Milestone B). Used to refine the initial concept and provide basis for the Technology Development Strategy.
7 Oversight & Review ACAT ID/IAM Programs* Defense AcquisitionExecutiveChief InformationOfficerDefense AcquisitionBoardIT AcquisitionBoardWeapon SystemsC3ISR SystemsMajor AISOverarchingIntegrated ProductTeams (OIPT)C3I OverarchingIntegrated ProductTeam (OIPT)Director, DefenseSystemsOUSD(AT&L)The acquisition responsibilities of USD(Intel) vs. ASD(NI2)/DoD CIO are a work in process.*Note: Space Programs have been delegated to the Air Force and most missile defense programs to the Missile Defense Agency
8 Transformation to the Joint Capabilities Integration and Development System RGSJCIDSIntegrated at DepartmentNational Military StrategyJoint VisionSystemsJoint Concept of OperationsRequirementsJoint Concepts Integrated ArchitecturesJoint CapabilitiesBottom Up, Often StovepipedTop Down, Born Joint
9 Evolutionary Acquisition Increment 2Increment 3Single Step toFull Capability ?ORKey ConsiderationsUrgency of RequirementMaturity of Key TechnologiesInteroperability, Supportability, and Affordability of Alternative Acquisition ApproachesCost/Benefit of Evolutionary vs. Single Step Approach
10 Operation of the Defense Acquisition System DoD InstructionOperation of the Defense Acquisition SystemEvolutionary AcquisitionTwo development processes to implement Evolutionary Acquisition StrategyIncremental Development: End-state requirement is known, and requirement will be met over time in several incrementsSpiral Development: Desired capability is identified, but end-state requirements are not known at Program Initiation. Requirements for future increments dependent upon technology maturation and user feedback from initial incrementsEvolutionary acquisition strategies shall be preferred approach to satisfying operational needs.Spiral development shall be the preferred process.
11 Evolutionary Acquisition – Incremental & Spiral Development Warfighter Capability=Known incrementKnown incrementKnown increment- IncrementalFirst Fielded CapabilityKnown increment- SpiralPartially known incrementTraditional = Big-Bang 100% solution that requires continuous development.P3I and Block occur subsequent to a development program and deliver an improved capability. Each P3I and Block effort is planned in detail before the effort begins—these “mini-bang” approaches do no provide for “use and learn” opportunities prior to fieldingSpiral Development, rather than the “Big Bang” approach of delivering 100% of the capability in a single development, incrementally delivers capabilities that grow to the 100% solution--deliver some core capability sooner that is better than today’s capability-- deliver fresher technology– “use and learn” with each capability to influence future spirals.Spiral development differs from P3I and Block Upgrades because the content of successive spirals is not clearly defined up-front – those subsequent spirals are shaped from 1-use and learn; 2-changing requirements; 3-funding availability; 4-technology discoveries. P3I is “pre-planned” and defined prior to start.Not known incrementTechnology DemosNot known incrementFeedback from warfighterTime
13 Evolutionary Approach CRTDSDDPDOSBCABCIncrement 2BCIncrement 3Key EnablersTime-Phased RequirementsA Modular Open Systems Approach to facilitate Technology InsertionEvolutionary Sustainment StrategiesT&E Consistent with Evolutionary ApproachFull Funding
14 Each Increment Must Have… BCIncrement 2BCIncrement 3Approved Operational RequirementsInteroperability Key Performance ParameterPerformance, Cost and Schedule Goals (Acquisition Program Baseline)Operational and Live Fire Testing (If Required)Compliance with Acquisition Oversight RequirementsAn Acquisition Strategy that reflects consideration of Logistics Planning; Manpower, Personnel and Training; Environmental and Security Factors; Protection of Critical Program Information; and Spectrum ManagementOther information tailored to the conditions of the programEach Increment is Managed as a Unique Acquisition
15 Acquisition Strategy Comparison Table Pre-planned Product Improvement (P3I)Single Step to Full CapabilityEvolutionary Acquisition *CriteriaIncremental DevelopmentSpiral Development **Full requirements defined at outsetYesYesYesNoUseful intermediate capabilitiesNoYesYesYesMultiple iterationsNoNoYesYesAll capabilities required in initial incrementYesNoNoNoUser feedback from earlier iterations used to define final requirementNoNoYesYesTraditional acquisition strategyAchieves increased capability from predictable maturing technologyOften used in hardware developmentPreferred process(Previously used mostly in Software development)Other characteristics* Preferred strategy ** Preferred process
16 DoD Instruction 5000.2 Operation of the Defense Acquisition System Statutory Information Requirements Changed/AddedWhenRequiredRequirementReferenceCommentSpectrum CertificationCompliance47 USC 305 &PLOMB A-11, Part 2DoDDMS B, orMS C if no BName changeFormerly –ApplicationFor FrequencyAllocationProgrammaticEnvironmentalSafety & HealthEvaluationMS B, orMS C if no BFromDoD R42 USC 4321Electronic Warfare T&E ReportSec. 220, PL & Sec. 214, PLannuallyFromDoD R
17 DoD Instruction 5000.2 Operation of the Defense Acquisition System Statutory Information Requirements Changed/AddedContinued…..WhenRequiredRequirementReferenceCommentCertification of Compliance with Financial Management Modernization Plan (FM acq programs only)NEWFrom CongressMS A, B, and CPLBenefits Analysis & Determination (applies to bundled acquisitions; part of acq strategy)NEWFrom Congress15 USC 644(e)MS B, orMS C if no BTechnology Development StrategyNEWFrom CongressSec. 803, PLMS A, B and C
18 DoD Instruction 5000.2 Operation of the Defense Acquisition System Regulatory Information Requirements Changed/AddedRegulatory InformationRequirements AddedWhenRequiredReferenceCommentNEW from Joint StaffReplaces MNSInitial Capabilities Document (ICD)CJCSIMS ACapability DevelopmentDocument (CDD)CJCSIMS BNEW from Joint StaffReplaces ORDCapability ProductionDocument (CPD)CJCSIMS CTechnology ReadinessAssessment (PM-level)Revised fromDoD R requirement for an Independent Technology Assessment for all programsDoDIMS B & CIndependent TechnologyReadiness Assessment (ACAT ID only – as required by DUSD(S&T))DoDIMS B & CEarned ValueManagement SystemsOMB Cir A-11, part 7See ANSI/ EIAFromDoD R
19 DoD Instruction 5000.2 Operation of the Defense Acquisition System Other Reports Changed/AddedReportReferenceWhen RequiredCommentDefense AcquisitionExecutive Summary(DAES) (MDAP & MAIS)QuarterlyPOM or BES submitUCR breachFromDoD RDoDIContractor Cost DataReport (CCDR)FromDoD RDoD M-1See the referenceSoftware ResourcesData Report(ACAT I/IA programs for all major contracts & sub – contracts for any software development elements with a projected software effort greater than $25M (FY02 constant dollars)-180 days prior to contract award-60 days after contract award-60 days after start of subsequent software releases-within 120 days after software release or final deliveryDoD M-2NEW from OSD Director, PA&E
20 Defense Acquisition Management Framework – Key PointsEvolutionary acquisition is the preferred strategy for rapid acquisition of mature technology; spiral development is the preferred processMDA may authorize entry at any point consistent with phase-specific entrance criteria and statutory requirementsNon-mandatory guidance on best practices, lessons learned and expectations are available in the Interim Guidebook (former DoD R)Validated and approved ORDs are still required until revised CJCSI is published
21 The Defense Acquisition Management Framework User Needs &Technology OpportunitiesProcess entry at Milestones A, B, or CEntrance criteria met before entering phasesEvolutionary Acquisition or Single Step to Full CapabilityBACIOCFOCSystemIntegrationSystemDemonstrationLRIPFull-Rate Prod & DeploymentSustainmentDisposalDesignReadinessReviewFRPDecisionReviewConceptDecisionConceptRefinementTechnologyDevelopmentSystem Development& DemonstrationOperations& SupportProduction & DeploymentPre-Systems AcquisitionSystems AcquisitionSustainmentValidated & approved byoperational validation authorityInitial CapabilitiesDocument (ICD)Capability DevelopmentDocument (CDD)Capability ProductionDocument (CPD)Relationship to Requirements Process