So How Do We Buy The Systems That You Operate And Maintain?

So How Do We Buy The Systems That You Operate And Maintain?
Defense Systems Management College Defense Acquisition University Fort Belvoir, Virginia Big “A” Acquisition

The Broad Policy Context Three Intersecting Processes = Big “A” Acquisition
Effective Interaction Essential for Success Planning, Programming, Budgeting and Execution (PPBE) DODD , May 03, Defense Acquisition Sys DODI , Jan15, Operation of Def Acq Sys DODI , Jan 16, Def Acq of Services Joint Capabilities Integration and Development System (JCIDS) Defense Acquisition System (DAS) JCIDS, Defense Acquisition, and PPBE must be synchronized to deliver capabilities to the warfighters. This is the Venn diagram introduced and discussed in Tab 1 as “Big A” acquisition. Each of the processes interacts with the others. Moreover, all three (JCIDS, Acquisition, and PPBE) processes must be synchronized to deliver timely, affordable capability to warfighters. This is a team effort between the Requirements Manager and Program Manager. The RM, the PM, PEO and Milestone Decision Authority (MDA) reside in the little triangle right in the center. They are responsible for integrating these three decision support systems in synch with warfighter’s needs.

Major DoD Decision Support Systems
JCIDS Requirements Management Defense Acquisition System PPBE Resource Management Program Management Contract Management Rules CJCSI series JCIDS Manual User/Service Chief VCJCS/JROC JROC Capability Need Threat/Capability DOD 5000 Series PEO/CAE/DAE Milestones Next Phase System Life Cycle R&D/Proc/O&S FAR DFARS PCO/HCA/SPE DCMA Business Clearance Contracts Contractor Performance DPG/POM/Budget DoD 7000 Series PEO/Service HQ/OSD OMB/Congress DMAG Funding/Resources Annual Funding & FYDP Players Reviews Decisions Focus This chart provides more insight into facets of the three decision support systems. Defense acquisition also includes not only project management but contract management as well, in most cases. Although the focus and key players of each process are specific to its purpose, the systems have parallels, as this table shows. Each process is governed by a set of unique policies (rules), conducts reviews, and makes decisions (output) that serve to frame how DOD will acquire capabilities that enable warfighters to meet national security objectives The key players at OSD are the Under Secretary of Defense (AT&L), the Under Secretary of Defense (Comptroller) and Director, Cost Assessment and Program Evaluation (DCAPE). Later in RQM 403 we’ll cover the PPBE process in greater depth. Chapter 1 of the Defense Acquisition Guidebook provides a summary of the three major decision support systems. The DAG has 14 Chapters and is a great resource especially if you are looking for info on a specific topic related to acquisition—you can do keyword searches quite easily. [It is being updated to reflect DODI , Jan 2015.] DCMA: Defense Contract Mgmt Agency DPG: Defense Planning Guidance FAR: Federal Acquisition Regulation FYDP: Future Years’ Defense Program HCA: Head of Contracting Activity JROC: Joint Requirements Oversight Council OMB: Office of Management & Budget CJCS: Chairman, Joint Chiefs of Staff CJCSI: Chairman, Joint Chiefs of Staff Instruction CAE: Component Acquisition Executive DAB: Defense Acquisition Board DMAG: Deputy’s Management Advisory Group DFARS: Defense FAR Supplement OSD: Office of the Secretary of Defense PCO: Procuring Contracting Officer PEO: Program Executive Officer POM: Program Objectives Memorandum SPE: Senior Procurement Executive VCJS: Vice Chairman, Joint Chiefs of Staff

DoD Requirements Overview
Defense Systems Management College Defense Acquisition University Fort Belvoir, Virginia This discussion of the Acq Policy and the Def Acq System (DAS) will highlight the key facets acquisition policy and then the Defense Acquisition. The discussion will include context on how that process interacts with the other two key decision processes for DoD – the JCIDS Process and the PPBE Process. After discussing the key facets of the DAS and the roles of key players in the governance of defense acquisition programs, we will explain in more detail the facets of each phase of the defense acquisition life cycle and how the requirements and acquisition interact. DoD Requirements Overview

DoD PPBE Overview Defense Systems Management College
Defense Acquisition University Fort Belvoir, Virginia This discussion of the Acq Policy and the Def Acq System (DAS) will highlight the key facets acquisition policy and then the Defense Acquisition. The discussion will include context on how that process interacts with the other two key decision processes for DoD – the JCIDS Process and the PPBE Process. After discussing the key facets of the DAS and the roles of key players in the governance of defense acquisition programs, we will explain in more detail the facets of each phase of the defense acquisition life cycle and how the requirements and acquisition interact. DoD PPBE Overview

DoD Acquisition Overview
Defense Systems Management College Defense Acquisition University Fort Belvoir, Virginia This discussion of the Acq Policy and the Def Acq System (DAS) will highlight the key facets acquisition policy and then the Defense Acquisition. The discussion will include context on how that process interacts with the other two key decision processes for DoD – the JCIDS Process and the PPBE Process. After discussing the key facets of the DAS and the roles of key players in the governance of defense acquisition programs, we will explain in more detail the facets of each phase of the defense acquisition life cycle and how the requirements and acquisition interact. DoD Acquisition Overview

Defense Acquisition System Overview
Governing policies and guidance Decision chain and oversight Defense Acquisition System (DAS): Materiel Development Decision through Operations & Support

DoDI 5000.02, 7 January 2015 Operation of the Defense Acquisition System
Emphasizes affordability, cost considerations-- integrates DAS with PPBE and JCIDS processes Defines acquisition categories (ACAT) and associated oversight levels Describes generic acquisition life cycle-- milestones and phases are to be tailored to program needs Statutory and regulatory compliance items covered in Enclosure 1 tables, by ACAT level and phase The latest DODI update was signed out 7 Jan 15. It had a few changes and replaced an interim update released in Nov 2013, which significantly updated the prior version from Main refocus was on the need to tailor the facets of the instruction to the particulars of a given user need. NOTE: The instruction clarifies where requirements apply only for Major Defense Acquisition Programs and Major Automated Information Systems. On 5 Jan 16, an entirely new DODI was released, DODI , Defense Acquisition of Services. These policies/instructions were previously covered in enclosure 9 within DODI , Dec 2008. DoDD Rapid Fulfillment of Combatant Commander Urgent Operational Needs

Where does the logistics community play?
Joint Capabilities Integration and Development System (JCIDS) / Defense Acquisition System (DAS) JCIDS DAS TRL-6 CDD Validation Development RFP Release Joint Concepts Joint Community Strategic Guidance Disposal Capabilities - Based Assessment Technology Maturation & Risk Reduction Engineering & Manufacturing Development Production & Deployment Operations & Support A MDD Draft CDD ICD AoA B C CPD Materiel Solution Analysis Sustainment FRP President SECDEF CJCS MDD is the initial formal interface between JCIDS and the DAS processes When an ICD recommends a materiel approach to resolve a warfighting capability gap, the JROC or Service ROC recommends the MDA convene a MDD Review Although a MDD is required for all programs to enter the acquisition process, at the MDD the Milestone Decision Authority (MDA) will authorize entry into the appropriate phase based on technology maturity and risk. The MDD does not establish a new acquisition program, that is done at Milestone B. Where does the logistics community play?

Defense Acquisition System – 2015 DoDI 5000.02, 7 Jan 2015
Materiel Solution Analysis (MSA) Technology Maturation & Risk Reduction (TMRR) Engineering & Manufacturing Development (EMD) Operations & Support (O&S) Production & Deployment (P&D) Materiel Development Decision (MDD) B C A CDD Validation RFP Release FRP Decision ICD draft CPD IOC FOC 5 Phases 3 Milestone Decisions – A, B, C 4 Other Decision Points: Materiel Development Decision (MDD), “Mandatory” Entry Capability Development Document (CDD) Validation Decision Development RFP Release Decision Full-Rate Production (FRP) Decision Acquisition programs use these models as a starting point in structuring a program to acquire a specific product. The structure of the program and the procedures used should be tailored as much as possible to the characteristics of the product being acquired, and to the totality of circumstances associated with the program including operational urgency and risk factors. Program Managers and Milestone Decision Authorities (MDAs) tailor program strategies and oversight, including program information, acquisition phase content, the timing and scope of decision reviews and decision levels, based on the specifics of the product being acquired, including complexity, risk factors, and required timelines to satisfy validated capability requirements. When there is a strong threat-based or operationally driven need to field a capability solution in the shortest time, MDAs are authorized to implement streamlined procedures designed to accelerate acquisition system responsiveness.

The Acquisition Chain of Authority
Acquisition Category (FY14 $) ACAT ID Makes ACAT ID and IAM Decisions Signs Acquisition Decision Memorandum (ADM) $480 M RDT&E or $2.79 B Procurement or MDA Special Interest Defense Acquisition Executive USD(AT&L) DAE ACAT IA Defense Acquisition Board $520 M Life Cycle Cost or $165 M Total Program Cost or $40 M Program Cost in any single year or MDA Special Interest Advice to DAE OIPT Issue resolution Overarching IPTs (OIPTs) ACAT IC/IAC Configuration Steering Boards Component Acquisition Executive (Asst Secretary) Makes ACAT IC, IAC & II decisions Signs ADM CAE ACAT II Working-Level IPTs (WIPTs) $185 M RDT&E or $835 M Procurement or MDA designation Component HQ Review Issue resolution ACAT III Program Executive Officer (Gen Officer/SES) PEO Makes ACAT III decisions Signs ADM No Fiscal Criteria [Does not meet criteria above.] Program Level IPTs The acquisition chain of command and key decision making roles are in yellow, in response to 1986 Goldwater-Nichols Act that requires no more than 3 levels between the program manager and the highest level decision maker in the Department. Oversight processes are at each level (at PEO level, Service/Agency level, or OSD level, if Milestone Decision Authority is at that level) Acquisition category (ACAT) drives level of review for key milestones; thus oversight is greatest for ACAT ID/IAM programs where the USD(AT&L) is the milestone decision authority. The AT&L staff plays an expanded role for ACATID and IAM programs. Note the role of the Configuration Steering Board: it is an interface with the requirements process to ensure currency and affordability of requirements over the program life cycle (as cost estimates get refined, and requirements learning occurs and/or technical challenges become clear). It also affords the PM the opportunity to request requirements modifications to improve affordability. Business systems used to have an IT Acquisition Board but they are now governed by the DAB since Mr Kendall is the MDA again for ACAT IAMs (he rescinded his delegation to the DCMO in Nov 2013.) Program Manager (Col/LtCol/Civilian Equiv) ACAT IV PM IPTs assist the MDA in oversight & review Used by Navy/USMC Note: Some PMs report directly to CAE Logistics is represented at every level

Materiel Solution Analysis (MSA) Phase
Purpose: Conduct the analysis and other activities needed to choose the concept to be acquired Begin translating validated capability gaps into system specific requirements including KPPs, KSAs, and APAs (where is logistics?) Conduct planning to support a decision on the acquisition strategy Major Events: Analysis of Alternatives reviews Guided by: ICD, MDD ADM, AoA Study Guidance, AoA Study Plan Key Performance Parameters (KPPs). Performance attributes of a system considered critical or essential to the development of an effective military capability. Failure of a system to meet a validated KPP threshold value triggers a review by the validation authority and evaluation of operational risk and/or military utility. Key System Attributes (KSAs). Performance attributes of a system considered important to achieving a balanced solution/approach to a system, but not critical enough to be designated a KPP. Additional Performance Attributes (APAs). Performance attributes of a system not important enough to be considered KPPs or KSAs, but still appropriate to include in the CDD or CPD are designated as APAs. Current KPP and KSAs: Page D-A-2 to D-A-4, JCIDS Manual Force Protection KPP (all manned systems) System Survivability KPP (all manned; may be applicable to unmanned ) Sustainment KPP (all ACAT I* ) Materiel Availability Operational Availability Supporting KSAs Materiel Reliability Operation & Support Costs Net Ready KPP (all IS & NSS) Training KPP (all ACAT I) Energy KPP (all where provisions of energy impact operational reach, or protection of energy infrastructure or energy resources is required) Note: The last two are mandatory where applicable Examples of what might be APAs: Navy is using a “cost” and a “schedule” parameter They are also using a SWaP-C parameter: “Space, Weight, Power and Cooling” to ensure programs have sufficient and clearly defined design margins at the outset

MSA Phase Major Activities
Component Acquisition Executive selects a Program Manager (PM) Conduct the Analyze alternative materiel solutions activities needed to choose the product concept PM develops the acquisition strategy to mature technology and reduce risk PM develops the functional strategies to support the capability development PM and Requirements Manager (RM) prepare a preliminary Reliability, Availability, Maintainability and Cost (RAM-C) rationale report RM develops draft CDD/ Problem Statement; including the CONOPs/OMS/MP/Use Cases ASR: alternative systems review. technical review to ensure that requirements agree with the customers’ needs and expectations and that the system under review can proceed into the Technology Maturation and Risk Reduction (TMRR) phase. The ASR should be completed prior to Milestone A. Note the activities, and importance of JCIDS document (ICD) to guide this phase. [Business systems used a Problem Statement, which matures over the course of this analysis phase.] Draft CDD/Problem Statement is needed to assist in determining the technical requirements for the TMRR Phase contract. The Draft CDD/updated Problem Statement reflects the emerging results of the AoA and evolves to reflect solution approved by the MDA at Milestone A. Validated CDD/Approved Problem Statement update supports the Development RFP Release decision and Milestone B.

Technology Maturation and Risk Reduction (TMRR) Phase
Purpose: Reduce technology, engineering, integration and life cycle cost risk Demonstrate critical technologies on Prototypes Develop an acquisition strategy to support the decision to proceed into development, production and sustainment Major Events: Design Reviews (only PDR is required) Early assessments (EOAs and ILAs) CDD Validation Development RFP Release Technology Readiness Assessment Guided by: Acq Strategy, MS A ADM, sponsor-approved draft CDD/Problem Statement and other program documents (PPP, SEP, LCSP, TEMP) SRR. Ensures all system and performance requirements derived from the ICD or draft CDD [or Problem Statement] are defined and consistent with cost, schedule, risk, and other system constraints. SFR. Assesses the system functional requirements as captured in system specifications (functional baseline), and ensures all required system performance is fully decomposed and defined in the functional baseline TRA. For MDAPs PM will conduct a Technology Readiness Assessment of critical technologies to ensure TRL 6 for MS B. TRA Report goes to ASD(R&E) for an independent assessment to support MS B certification. ”Technology demonstrated in a relevant environment” means achieve Technology Readiness Level (6). PDR prior to MS B is required for ACAT I programs. May be conducted before or after Pre-EMD review. It is important for the program strategy to include features that use the insight gained from the PDR (and the Post-PDR Review), even if it is after Milestone B. In other words, how does the contract accommodate the findings/results of PDR if PDR does not occur before EMD is awarded? EOA. Early Operational Assessment. An Operational Assessment (OA) conducted early in an acquisition program, often on subsystems and early prototype equipment, to forecast and evaluate the potential operational effectiveness and suitability of the system during development. EOA also assist in determining any system-unique test assets for future developmental and operational tests. ILA. Independent Logistics Assessment assess the adequacy of the product support strategy, and identify features likely to drive future operating and support costs, changes to system design that could reduce costs, and effective strategies for managing such costs. DODI now includes a Reqmts Decision Point (CDD Validation/Problem Statement approval). A valid requirement helps ensure realism in planning (affordability; feasibility) for preliminary design efforts in this TMRR phase. IT programs (for example) may use mature technology but the integration of various technologies (even COTS) can be a risk--so this phase can be more about risk reduction due to integration than about maturing technology. The DODI renamed this phase to TMRR Phase to add equal emphasis to risk reduction.

TMRR Phase Major Activities
At Milestone A the focus is on how to mature appropriate technology and reducing risks through demonstration PM reduces risk through competitive prototyping (req’d for MDAPs unless MDA approves waiver) PM conducts Preliminary Design Review(s) (PDR) to review the initial design PM assess technology readiness for EMD PM and RM conduct an annual Configuration Steering Board (CSB) RM supports CDD/ Problem Statement Validation decision; including the CONOPs/OMS/MP/Use Cases PM completes draft RFP review to support Development RFP Release decision Generic requirements to enter and leave (exit) each phase are in DoDI Note the activities, and importance of JCIDS document (ICD) to guide this phase. [Business systems used a Problem Statement, which matures over the course of this analysis phase.] Draft CDD/Problem Statement is needed to assist in determining the technical requirements for the TMRR Phase contract. The Draft CDD/updated Problem Statement reflects the emerging results of the AoA and evolves to reflect solution approved by the MDA at Milestone A. Validated CDD/Approved Problem Statement update supports the Development RFP Release decision and Milestone B.

TMRR Phase Program Documents
Acquisition Strategy Acquisition Program Baseline (APB) [KPPs from user requirements] Systems Engineering Plan (SEP) [RAM-C report attached] Test & Evaluation Master Plan (TEMP) [includes COIs] Life Cycle Sustainment Plan (LCSP) [addresses sustainment KPP and KSAs] Program Protection Plan (PPP) [identifies critical technologies & Defense Exportability Features (DEF)] DoDI , Enclosure 1, Table 2 provides more specific detail

Engineering and Manufacturing Development (EMD) Phase
Purpose: Develop, build and test a product to verify all operational and derived requirements are met Support production and deployment decisions Major Events: Design Reviews (only CDR is required; PDR also if PDR prior to Milestone B was waived) Developmental Test & Evaluation (DT&E) / Operational Assessments (OAs) Independent Logistics Assessments (ILAs) Capability Production Document (CPD) Validation Production and Deployment RFP release and source selection Guided by: Acquisition Strategy, MS B ADM and APB, validated CDD/Problem Statement, and other planning documents (PPP, SEP, LCSP, TEMP) Developmental Test and Evaluation (DT&E). Discussed more later. Independent Logistic Assessment (ILA). Discussed more later Operational Assessments (OAs). Discussed more later Critical Design Review (CDR). The CDR provides evidence that the system, down to the lowest system element level, has a reasonable expectation of satisfying the requirements of the system performance specification as derived from the CDD within current cost and schedule constraints. CDR is discussed in more detail later in this lesson. Test Readiness Review (TRR). conducted to determine if the system under review is ready to proceed into formal testing by deciding whether the test procedures are complete and verify their compliance with test plans and descriptions. Normally conducted before each major test configuration item including hardware and software and provides management with the assurance that a system has undergone a thorough test process and is ready for turnover to the next test phase. System Verification Review (SVR). a product/process assessment to ensure the system under review can proceed into LRIP and FRP within cost, schedule, risk, and other system constraints during the EMD Phase. It assesses the system functionality and determines if it meets the functional requirements in the CDD and draft CPD documented in the functional baseline. Establishes and verifies final product performance and provides inputs to the CPD. The SVR is often conducted concurrently with the PRR and FCA Production Readiness Review (PRR). Assesses a program to determine if the design is ready for production. It assesses if the prime contractor and major subcontractors have accomplished adequate production planning without incurring unacceptable risks that will breach thresholds of schedule, performance, cost, or other established criteria.

EMD Phase Major Activities
At Milestone B normally formal program initiation with approval of the Acquisition Program Baseline (APB) At Milestone B referred to as a “Program of Record (POR)” - commits required investment resources to the program PM completes hardware/software detailed design of an integrated system PM demonstrates design through appropriate development test & evaluation and assessments PM aligns technology, manufacturing and sustainment readiness to support production and deployment PM develops system product support attributes PM completes Critical Design Review(s) RM supports CPD/ Problem Statement Validation PM completes draft RFP review to support P&D PM conducts program tracking through acquisition reporting

EMD Phase Product Support Policy/Statute
Core: Logistics capability required to perform maintenance and support of mission-essential equipment (Title 10, Section 2464) 50/50: Restricts use of non-federal government workers performing depot level maintenance and repair to 50% of allocated funding* (Title 10, Section 2466) Competition: Mandates public/private competition or merit- based selection for existing depot level work valued at > $3M (Title 10, Section 2469) CITE: authorizes/encourages organic repair depots partnering with Centers of Industrial and Technical Excellence (CITE), enables depot activities to become formal subcontractors (Title 10, Section 2474) Public Law – Source of repair analysis 10 USC 2474 – Public-Private Partnerships Core - DoD must maintain core logistics capability to perform maintenance and support of mission-essential equipment (Title 10, Section 2464). 50/50 - Not more than 50 percent of the funds available to a military DoD agency in a fiscal year for depot-level maintenance and repair workload may be used to contract for performance of this workload by nonfederal government personnel (Title 10, Section 2466). Competition - Existing depot-level maintenance or repair workload valued at $3 million or more must be neither contracted out nor moved to another depot-level activity without using public and private competition procedures or merit-based selection procedures (Title 10, Section 2469). CITE - Center of Industrial and Technical Excellence (CITE) Service Secretaries designate each depot activity and arsenal as a Center of Industrial and Technical Excellence (CITE) in their core competencies Authorizes and encourages Public-Private Partnerships (PPP) with CITE. CITE-enabled public-private partnerships (PPP) allow Employees of Center, private industry, and others to perform work related to core competencies Private industry and others to use facilities or equipment of the Center that are not fully utilized Enables depot activities to serve as subcontractors to commercial Product Support Integrators (PSI) Work performed at a CITE by a contractor as part of a PPP is not counted towards the 10 U.S.C % limitation * Reported at the Service level, not program

Production and Deployment (P&D) Phase
Purpose: To produce and deliver requirements- compliant products to receiving military organizations Major Events Production and Test Readiness Reviews IOT&E/LFT&E FRP/FD decision Production RFP Release Guided by: Acquisition Strategy, MS C ADM, sponsor-approved CPD/Problem Statement and other planning documents (PPP, SEP, LCSP, TEMP) PCA. Physical Configuration Audit - examines the actual configuration of an item being produced and is conducted around the time of the Full-Rate Production Decision. It verifies that the related design documentation matches the Configuration Item (CI) as specified in the contract and confirms that the manufacturing processes, quality control system, measurement and test equipment, and training are adequately planned, tracked, and controlled. OTRR. Operational Test Readiness Review - assess if a system should proceed into Initial Operational Test and Evaluation (IOT&E). The review addresses and verifies system reliability, maintainability, and supportability performance and determines if the hazards and Environmental, Safety, Occupational and Health (ESOH) residual risks are manageable within the planned testing operations. PRR. Production Readiness Review - assesses a program to determine if the design is ready for production. It assesses if the prime contractor and major subcontractors have accomplished adequate production planning without incurring unacceptable risks that will breach thresholds of schedule, performance, cost, or other established criteria.

P&D Phase Major Activities
At Milestone C the program is reviewed for entrance into the Production and Deployment Phase (or Limited Deployment for software intensive systems) PM executes Low-rate Initial Production and Limited Deployment Complete Operational Test and Evaluation DOT&E completes Beyond LRIP Report* PM ensures Limited Deployment (LD) for software intensive systems PM establishes the Product Support Capability PM executes Full-rate Production and Full Deployment PM conducts product support draft RFP review Generic requirements to enter and leave (exit) each phase are in DoDI Note the activities, and importance of JCIDS document (CPD) to guide this phase. [Business systems used a Problem Statement, which matures over the course of this analysis phase.] CPD/Problem Statement is needed to assist in determining the technical requirements for the production and sustainment Phase contracts. * DoDI calls it “DOT&E Report on IOT&E”

Operations & Support (O&S) Phase
Purpose: To execute the product support strategy Satisfy materiel readiness and operational support performance requirements Sustain the system over its life cycle (to include disposal) Operations and Support ISR PIR Dev RFP Release Major Events: Begins when the first system is fielded Modifications and technology insertion MDA approved Life Cycle Sustainment Plan Guided by: Acquisition Strategy, MS C ADM and APB, sponsor-approved CPD/Problem Statement and other planning documents (PPP, SEP, LCSP, TEMP) ISR: In Service Review - an assessment of a system to determine if it’s operationally employed with well-understood and Managed Risks. It assesses the current status, operational health and corrective actions to satisfy user operational needs based on user feedback and performance metrics. The reviews should be conducted at defined intervals to identify needed revisions and corrections and to allow for timely improvements in the strategies to meet performance requirements. Should provide the following: An overall System Hazard Risk Assessment, An Operational Readiness Assessment in terms of system problems (hardware, software, and production discrepancies), and Status of current system problem (discrepancy) report inflow, resolution rate, trends, and updated metrics. The metrics may be used to prioritize budget requirements. PIR: Post-implementation Review - verifies the MOEs of the ICD or the benefits of a business plan. Normally the FRP/FD review and decision completes this action. A process that aggregates information needed to successfully evaluate the degree to which a capability has been achieved. A PIR answers the question, “Did the Service/Agency get what it needed, per the ICD / Business Plan, and if not, what should be done? A PIR is required for all acquisition program increments at the Full-Rate Decision Review (FRDR). The Sponsor is responsible for planning the PIR, gathering data, analyzing the data, and assessing the results. The PM is responsible for maintaining an integrated program schedule that includes the PIR on behalf of the Sponsor. The PM is also responsible for supporting the Sponsor with respect to execution and reporting of the PIR

O&S Phase Major Activities
PM continues with Full-rate Production and Deployment PM implements and adjusts the Product Support Strategy based on evolving operating, threat and budget environment PM collects feedback and evaluates operations and support activities PM implements modifications, including technology insertion activities PM evaluates program resources and ensures intellectual property deliverables and associated license rights, tools, equipment, and facilities are acquired PM fully establishes organic or industry depot maintenance capability in accordance with statute and the LCSP PM implements Disposal planning and execution Generic requirements to enter and leave (exit) each phase are in DoDI Note the activities, and importance of JCIDS document (CPD) to guide this phase. [Business systems used a Problem Statement, which matures over the course of this analysis phase.] Note: all actions must be in accordance with all legal and regulatory requirements relating to safety (including explosives safety, security, and the environment)

Materiel Acquisition Process Additional References
Great Help for locating just about anyone in DoD (formerly the “White Pages”) (CAC login required, choose version) Links to more common OSD sites: (connects you to all OSD sites) (actually takes you to the CAPE web site) Good general information site:

Materiel Acquisition Process Additional References
Defense Acquisition Portal Better Buying Power (BBP) Gateway ACQuipedia Acquisition Community Connection Program Managers e-Tool Kit 2014 Acquisition Process Chart or%20enhancements%2017%20Dec%20final%20(3).pdf DOD Acquisition Net

Questions?

DAB Membership 27

Technology Readiness Assessment (TRA)
Begins in MSA Phase: Technology risk is assessed against the ability to deliver the desired capability Documented in the AS and SEP By End of TMRR Phase, technology maturity is demonstrated sufficiently to verify development risk is at an acceptable Level During EMD Phase, maturity of technology is assessed to ensure it meets stated requirements and it can be manufactured Prior to a Production Decision, technology maturity risks must be acceptable, including any new technology insertion considerations TRA results support the Capability Production Document (CDD/CPD) Technology Readiness Levels (TRLs) serve as a common definition for evaluating technology maturity Technology Readiness Assessment (TRA) is a systematic, metrics-based process that assesses the maturity of, and the risk associated with, critical technologies to be used in MDAPs. It is conducted by the PM with the assistance of an independent team of subject matter experts (SMEs). Focuses on the program’s “critical” technologies (i.e., those that may pose major technological risk during development, particularly during the EMD phase of acquisition). Required prior to Milestone B to determine if critical technologies are at least TRL 6. Services may require TRAs at other points in the acquisition process. TRA results for ACAT I programs must be submitted to the office of the Assistant Secretary of Defense (Research and Engineering) (ASD R&E). Key players in the TRA process are as follows: The PM, the Component S&T Executive, and the CAE are the principal stakeholders for the Component conducting the TRA. The PM funds, schedules, and conducts the TRA. The PM identifies critical technologies for consideration during the TRA. The ASD (R&E) has responsibility for reviewing and evaluating the TRA for the OSD for ACAT I programs to support statutory MS B Certification. Component policy applies for ACAT II and below. TRAs are not required for MAIS programs, and are not required for MS A, C or FRPDR. However, CAEs are responsible to ensure the appropriate level of technology maturity for production. TRA Results are Included in the CDD/CPD

Manufacturing Readiness Assessment (MRA)
Begins in MSA Phase, manufacturing readiness and risk are assessed and documented in the SEP By End of TMRR Phase, manufacturing processes is demonstrated to the extent needed to verify risk is at an acceptable Level During EMD Phase, maturity of critical manufacturing processes will be assessed to ensure they are affordable and executable Prior to a Production Decision, manufacturing risks must be acceptable, supplier qualifications completed, and manufacturing processes are or will be under statistical process control MRA results support the Capability Production Document (CDD/CPD) Manufacturing Readiness Levels (MRLs) serve as a common definition for evaluating manufacturing maturity Manufacturing Readiness is the ability to harness the manufacturing, production, Quality Assurance, and industrial functions to achieve an operational capability that satisfies mission needs; in the quantity and quality needed by the military to carry out its missions.

Independent Logistics Assessment (ILA)
Begins in MSA Phase, sustainment readiness and risk are assessed, supportability objectives and KPP/KSA requirements defined By End of TMRR Phase, maintenance concepts and sustainment strategy complete; LSCP approved During EMD Phase, support features embedded in design, support capabilities demonstrated, and SCM approach validated During P&D Phase, product support package demonstrated in operational environment, performance measures in place ILA results support the Capability Production Document (CDD/CPD) Sustainment Maturity Levels (SMLs) serve as a common definition for evaluating sustainment maturity (new concept) SRLs (Sustainment Readiness Levels) where introduced in the 2016 PSM Guide. TRLs and MRLs have been around for 20 to 30 years Sustainment Readiness Levels, PSM Guidebook, April 2016

Model 1: Hardware Intensive Program
Capability Development Document (CDD) Validation Development Request for Proposals (RFP) Release Decision Full-Rate Production (FRP) Decision Initial Operational Capability (IOC) Full Operational Capability (FOC) Materiel Development Decision A B C Low-Rate Initial Production (LRIP) OT&E Sustainment Disposal Materiel Solution Analysis Technology Maturation & Risk Reduction Engineering & Manufacturing Development Production & Deployment Operations & Support The “classic” approach: requirements drive one final capability, complex, usually defense unique, hardware program that will be fully deployed Examples: Trucks Note: Program deploys with full capability described in the CDD

Model 2: Defense Unique Software Intensive Program
B A C Build 1.1 Build 1.2 Build 1.3 Build 1.4 Integration Build 0.1 Risk Reduction Build 2.1* Materiel Solution Analysis Technology Maturation & Risk Reduction Production & Deployment Engineering & Manufacturing Development Sustainment Disposal Materiel Development Decision Development RFP Release Decision CDD Validation IOC Full Deployment (FD) Full Deployment Decision (FDD) Build 1.5 Operations & Support Limited OT&E Complex, usually defense unique, software program that will not be fully deployed until several software builds have been completed Examples: command and control systems and significant upgrades to the combat systems found on major weapons systems such as surface combatants and tactical aircraft Note: Several software builds are typically necessary to achieve a deployable capability

Model 3: Incrementally Fielded Software Intensive Program
B A Materiel Development Decision Development RFP Release CDD Validation IOC Limited Deployment Decisions Materiel Solution Analysis Risk Reduction Development & Deployment Sustainment Build 0 Build OT&E Build 1.1 Build 1.2 . . . Full Deployment Decision (FDD) Full (FD) Operations & Support Build 1.n Operations & Support Increment 2 Development RFP Release Decision Limited Deployment Decisions IOC FD Development & Deployment Sustainment B FDD OT&E Build 2.1 Build 2.2 Build 2.n . . . Risk Reduction Full capability occurs in multiple increments as new capability is developed and delivered Examples: Business systems, upgrades to command and control systems or weapon systems Note: Caution can be structured so the program is overwhelmed with frequent milestones/ deployment decision points Increment N Development RFP Release Decision Limited Deployment Decisions FD Development & Deployment B OT&E Build n.1 Build n.2 IOC Operations & Support Build n.n . . . Sustainment Disposal Risk Reduction FDD Sometimes people try to equate to “Agile software development” which is: Evolving vision, Evolving requirements, Multiple “Sprints” and “Releases,” Feedback loop is essential Less about “increments” or “builds” and more about “sprints” of work which create a product (packets of software). Helps teams respond to unpredictability through incremental, iterative work cadences, known as sprints. Agile methodologies are an alternative to waterfall, or traditional sequential development. What is Scrum? The most popular way of introducing Agility due to its simplicity and flexibility. Because of this popularity, many organizations claim to be “doing Scrum” but aren’t doing anything close to Scrum’s actual definition. Scrum emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations. Agile development methodology provides opportunities to assess the direction of a project throughout the development lifecycle. Achieved through regular cadences of work, known as sprints or iterations, at the end of which teams must present a potentially shippable product increment. Focusing on the repetition of abbreviated work cycles as well as the functional product they yield, agile methodology is described as “iterative” and “incremental.” In waterfall, development teams only have one chance to get each aspect of a project right. In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited throughout the lifecycle. When a team stops and re-evaluates the direction of a project every two weeks, there’s always time to steer it in another direction.

Model 4: Accelerated Acquisition Program
A/B C Materiel Solution Analysis Sustainment Disposal Materiel Development Decision Preliminary Design Review IOC FOC Concurrent Technology Maturation, Risk Reduction, and Development Concurrent Production and Deployment OT&E Operations & Support Applies when schedule considerations dominate over cost and technical risk considerations. Compresses or eliminates phases of the process and accepts potential inefficiencies Examples: Quick reaction programs, MRAP or bunker buster bomb Note: Used when technological surprise by a potential adversary necessitates a higher risk acquisition program. Mature technology supports rapid acquisition considerations DoDI , Rapid Fulfillment of Combatant Commander Urgent Operational Needs Establishes the Warfighter Senior Integration Group (SIG) as a standing DoD-wide forum and establishes policy, assigns responsibilities, and provides direction to facilitate the rapid delivery of capabilities in response to UONs, consistent with all applicable laws and governing regulations. Reference: DoDI , Enclosure 13, DoDD , and DoDI (IT systems)

Model 5: Hybrid Program A (Hardware Dominant)
C Build 1.1 Build 1.2 Build 1.3 Build 1.4 Integration Build 0.1 Risk Reduction Build 2.1 Materiel Solution Analysis Technology Maturation & Risk Reduction Production & Deployment Engineering & Manufacturing Development Sustainment Disposal Materiel Development Decision Development RFP Release CDD Validation IOC FOC FRP Build 1.5 Operations & Support LRIP OT&E Build 3.1 Build 3.2* Combines hardware development as the basic structure with software intensive development occurring simultaneously Examples: F-22 Note: Design, fabrication, and testing of physical prototypes may determine overall schedule, decision points, and milestones, but software development will often dictate the organization, pace of test and program execution

Model 6: Hybrid Program B (Software Dominant)
Development RFP Release CDD Validation B A C Build 1.1.1 Build 1.1.2 Build 1.0.1 Integration Build 1.1.3 Build 1.2 Materiel Solution Analysis Technology Maturation & Risk Reduction Production and Deployment Engineering & Manufacturing Development Sustainment Materiel Development Decision IOC FD FDD Build 1.3.1 Build 1.3.2* Limited Deployment LD) Operations & Support OT&E Operations & Support Increment 2 Development RFP Release Decision FDD IOC FD B OT&E Build 2.1.1 Build 2.1.2 Build 2.3.1 Sustainment Disposal C LD Build 2.3.2 Technology Maturation & Risk Reduction Engineering & Manufacturing Development Production and Deployment Build 2.1.3 Build 2.2 Integration Includes a mix of incrementally fielded software products or releases that include intermediate software builds Examples: GPS Control Segment Note: Configuration control and recurring training may drive effectiveness

Milestone A Information Requirements All programs except where noted (see Table 2, DoDI 5000.02)
2266a Determinations (MDAP only) Acquisition Decision Memorandum (ADM) Acquisition Strategy (see text of DoDI for additional requirements) Benefit Analysis & Determination Consideration of Technology Issues (MDAP & MAIS only) Cooperative Opportunities Industrial Base Capabilities Considerations Intellectual Property Strategy Market Research Small Business Innovation Research/Small Business Technology Transfer Program Technologies Termination Liability Estimate (MDAP only) Affordability Analysis Analysis of Alternatives (AoA) Report Capability Development Document (CDD) - Draft Clinger-Cohen Act (CCA) Compliance Concept of Operations/Operational Mode Summary/ Mission Profile (CONOPS/OMS/MP) Core Logistics Determination Cost Analysis Requirements Description (CARD) (MDAP & MAIS only) Cybersecurity Strategy DoD Component Cost Estimate (CCE) (MDAP & MAIS only) DoD Component Cost Position (CCP) (MDAP & MAIS only) Economic Analysis (MAIS only) may combine w/AoA Exit Criteria Frequency Allocation Application Full Funding Certification Memorandum (MDAP & MAIS only) Independent Cost Estimate (MDAP & MAIS only) Item Unique Identification Implementation Plan Life-Cycle Mission Data Plan Life-Cycle Sustainment Plan Program Certification to the Defense Business Systems Management Committee (DBS only) Program Protection Plan (PPP) Replaced System Sustainment Plan (MDAP only) Request for Proposal (RFP) Should Cost Target Spectrum Supportability Risk Assessment System Threat Assessment Report (STAR) Systems Engineering Plan (SEP) Technology Targeting Risk Assessment Test & Evaluation Master Plan (TEMP) MAIS: Major Automated Information System MDAP: Major Defense Acquisition Program Statutory Requirements in blue italics DBS: Defense Business Systems

Development RFP Release Information Requirements All programs except where noted (see Table 2, DoDI ) Acquisition Decision Memorandum (ADM) Acquisition Program Baseline (APB) Acquisition Strategy (see text of DoDI for additional requirements) Benefit Analysis & Determination Consideration of Technology Issues (MDAP & MAIS only) Contract Type Determination (MDAP only) Industrial Base Capabilities Considerations Intellectual Property Strategy Market Research Small Business Innovation Research/Small Business Technology Transfer Program Technologies Termination Liability Estimate (MDAP only) Affordability Analysis  Analysis of Alternatives (AoA) Report  Bandwidth Requirements Review Capability Development Document (CDD) - Validated Concept of Operations/Operational Mode Summary/ Mission Profile (CONOPS/OMS/MP)  Core Logistics Determination/Core Logistics Sustaining Workloads Estimate (MDAP only) Cost Analysis Requirements Description (CARD) (MDAP & MAIS)  Cybersecurity Strategy  Development RFP Release Cost Assessment Economic Analysis (MAIS only) may combine w/AoA Exit Criteria Information Support Plan Item Unique Identification Implementation Plan  Life-Cycle Mission Data Plan  Life-Cycle Sustainment Plan  Low Rate Initial Production (LRIP) Quantity Problem Statement (DBS only) Program Protection Plan (PPP)  Request for Proposal (RFP) Should Cost Target System Threat Assessment Report (STAR)  Systems Engineering Plan (SEP)  Technology Readiness Assessment (MDAP only) Test & Evaluation Master Plan (TEMP)  MAIS: Major Automated Information System MDAP: Major Defense Acquisition Program Statutory Requirements in blue italics DBS: Defense Business Systems Updated Information

Milestone B Information Requirements All programs except where noted (see Table 2, DoDI 5000.02)
2366b Certification Memorandum (MDAP only) Acquisition Decision Memorandum (ADM) Acquisition Program Baseline Affordability Analysis  Bandwidth Requirements Review  Capability Development Document (CDD) Clinger-Cohen Act (CCA) Compliance Contract Type Determination (MDAP only) Core Logistics Determination/Core Logistics Sustaining Workloads Estimate (MDAP only)  Cost Analysis Requirements Description (CARD) (MDAP & MAIS only) Cybersecurity Strategy  DoD Component Cost Estimate (CCE) (MDAP & MAIS only) DoD Component Cost Position (CCP) (MDAP & MAIS only) Economic Analysis (MAIS only)  Exit Criteria Frequency Allocation Application Full Funding Certification Memorandum (MDAP & MAIS only) Independent Cost Estimate (MDAP & MAIS only) Independent Logistics Assessment (ILA) (MDAP only) Item Unique Identification Implementation Plan Life-Cycle Mission Data Plan  Life-Cycle Sustainment Plan (LCSP)  LRIP Quantities (MDAP, ACAT II & III only) Program Certification to the Defense Business Systems (DBS) Management Committee (DBS only) Program Protection Plan (PPP)  Programmatic Environmental Safety & Occupational Health Evaluation (PESHE) and NEPA/E.O Compliance  Replaced System Sustainment Plan (MDAP only) Should-Cost Target Spectrum Supportability Risk Assessment Systems Engineering Plan (SEP)  Technology Readiness Assessment (TRA) (MDAP only)  Test & Evaluation Master Plan (TEMP)  Waveform Assessment Application Updated and re-submitted only if changes have occurred since approved at the Development RFP Release Decision. Statutory Requirements in blue italics DBS: Defense Business Systems MAIS: Major Automated Information System MDAP: Major Defense Acquisition Program

Milestone C Information Requirements All programs except where noted (see Table 2, DoDI 5000.02)
2366b Certification Memorandum (MDAP only) (only if Milestone C is program initiation) Acquisition Decision Memorandum (ADM) Acquisition Program Baseline  Acquisition Strategy (see text of DoDI for additional requirements)  Benefit Analysis & Determination (only if no MS B) Contract Type Determination (MDAP only) General Equipment Valuation Industrial Base Capabilities Considerations Intellectual Property Strategy Small Business Innovation Research/Small Business Technology Transfer Program Technologies Termination Liability Estimate (MDAP only) Affordability Analysis  Analysis of Alternatives (updated only if required)  Bandwidth Requirements Review  Capability Production Document (CPD) - validated Clinger-Cohen Act (CCA) Compliance CONOPS/Operational Mode Summary/Mission Profile (CONOPS/OMS/MP)  Core Logistics Determination/Core Logistics Sustaining Workloads Estimate (MDAP only)  Cost Analysis Requirements Description (CARD) (MDAP & MAIS only)  Cybersecurity Strategy  DoD Component Cost Estimate (CCE) DoD Component Cost Position (CCP) (MDAP & MAIS only) Exit Criteria Frequency Allocation Application Full Funding Certification Memorandum (MDAP & MAIS only) Independent Logistics Assessment (ILA) (MDAP only) Independent Cost Estimate (MDAP & MAIS only) Information Support Plan (ISP)  Item Unique Identification Implementation Plan  Life-Cycle Mission Data Plan  Life-Cycle Sustainment Plan (LCSP)  Preservation and Storage of Unique Tooling Plan (MDAP only) Problem Statement (DBS only)  Program Protection Plan (PPP)  Programmatic Environmental Safety & Occupational Health Evaluation and NEPA/E.O Compliance  Request for Proposal (RFP) Should-Cost Target Spectrum Supportability Risk Assessment System Threat Assessment Report (STAR)  Systems Engineering Plan (SEP)  Technology Readiness Assessment (MDAP only) (only if Milestone C is program initiation) Test & Evaluation Master Plan (TEMP)  Waveform Assessment Application  MAIS: Major Automated Information System MDAP: Major Defense Acquisition Program Statutory Requirements in blue italics DBS: Defense Business Systems Updated Information

Full-Rate Production/Full Deployment Information Requirements All programs except where noted (see Table 2, DoDI ) Acquisition Decision Memorandum (ADM) Acquisition Program Baseline  Acquisition Strategy (see text of DoDI for additional requirements) Benefit Analysis & Determination (only if no MS B)  Contract Type Determination (MDAP only) General Equipment Valuation  Industrial Base Capabilities Considerations  Intellectual Property Strategy  Small Business Innovation Research/Small Business Technology Transfer Program Technologies  Termination Liability Estimate (MDAP only) Affordability Analysis  Clinger-Cohen Act (CCA) Compliance Cost Analysis Requirements Description (CARD) (MDAP & MAIS only)  DoD Component Cost Estimate (CCE) Cybersecurity Strategy  DoD Component Cost Position (CCP) (MDAP & MAIS only) DOT&E Report on Initial Operational Test & Evaluation (IOT&E) (DOT&E Oversight List programs only) DoD Component Live Fire Test & Evaluation Report (DOT&E Oversight List programs only) Economic Analysis (MAIS only) Full Funding Certification Memorandum (MDAP & MAIS only) Independent Cost Estimate (MDAP & MAIS only) Independent Logistics Assessment (ILA) (MDAP only) Information Technology (IT) and National Security System (NSS) Interoperability Certification Life-Cycle Mission Data Plan  Life-Cycle Sustainment Plan (LCSP)  Live-Fire Test & Evaluation Report (DOT&E Oversight programs only) Operational Test Agency Report of OT&E Results Program Certification to the Defense Business Systems (DBS) Management Committee (DBS only) Problem Statement (DBS only)  Program Protection Plan (PPP)  Programmatic Environmental Safety & Occupational Health Evaluation and NEPA/E.O Compliance  Request for Proposal (RFP) Should-Cost Target System Threat Assessment Report (STAR)  Test & Evaluation Master Plan (TEMP)  MAIS: Major Automated Information System MDAP: Major Defense Acquisition Program Statutory Requirements in blue italics DBS: Defense Business Systems Updated Information

So How Do We Buy The Systems That You Operate And Maintain?

Similar presentations

Presentation on theme: "So How Do We Buy The Systems That You Operate And Maintain?"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

So How Do We Buy The Systems That You Operate And Maintain?

Similar presentations

Presentation on theme: "So How Do We Buy The Systems That You Operate And Maintain?"— Presentation transcript:

Similar presentations

About project

Feedback