DoD Instruction 5000.02 8 December 2008 Operation of the Defense Acquisition System Statutory and Regulatory Changes

1. DoD Instruction 5000.028 December 2008Operation of the Defense Acquisition System Statutory and Regulatory Changes 

2. This presentation is in two parts: -Part one covers the first five bullets. -Part two covers the last bullet, and can be used as a separate presentation. For this reason, there is some duplication in material between parts one and two. To prepare for this presentation: Read and be completely familiar with the 2 Dec 2008 DoDI 5000.02 Read Defense Acquisition Guidebook chapters: 2, Acquisition Strategy 4, Systems Engineering, Part 4.3, Systems Engineering Activities in the System Life Cycle 5, Life Cycle Logistics, Part 5.1.2.2, Life Cycle Sustainment Plan .This presentation is in two parts: -Part one covers the first five bullets. -Part two covers the last bullet, and can be used as a separate presentation. For this reason, there is some duplication in material between parts one and two. To prepare for this presentation: Read and be completely familiar with the 2 Dec 2008 DoDI 5000.02 Read Defense Acquisition Guidebook chapters: 2, Acquisition Strategy 4, Systems Engineering, Part 4.3, Systems Engineering Activities in the System Life Cycle 5, Life Cycle Logistics, Part 5.1.2.2, Life Cycle Sustainment Plan .

3. -Content of 5000.02 has grown from 37 to 79 pages. About 113%. -Although there are new policies that originated at OSD, the majority are a result of a very active Congress from 2004 thru 2008. -This includes six National Defense Authorization Acts (NDAA) for FY�s 2004 through 2009.-Content of 5000.02 has grown from 37 to 79 pages. About 113%. -Although there are new policies that originated at OSD, the majority are a result of a very active Congress from 2004 thru 2008. -This includes six National Defense Authorization Acts (NDAA) for FY�s 2004 through 2009.

7. The major differences between the 2003 and 2008 versions of the DoDI 5000.02 are: -The Materiel Development Decision (MDD) replaces the Concept Decision (CD). A MDD is required regardless of where the program intends to enter the acquisition process. NOTE: The arrows from User Needs/Technology Opportunities now point to the MDD at the extreme left: THIS DOES NOT MEAN THAT EVERY PROGRAM MUST ENTER AT THE MATERIEL SOLUTION ANALYSIS PHASE. This is illustrated better on chart 5. -The Materiel Solution Analysis Phase (MSA) replaces the Concept Refinement (CR) Phase. MSA is not �refinement� of the preferred solution(s) identified in the ICD. The JCIDS process no longer includes an Analysis of Materiel and Non-Materiel Alternatives. Non-materiel solutions will be handled IAW JCIDS; however, all analysis of alternative materiel solutions will be accomplished by the AoA during MSA. The MDA will approve the materiel solution at Milestone A. -Technology Development: This phase now includes a mandatory requirement for competitive prototyping of the system or key-system elements. A Preliminary Design Review (PDR) may be conducted for the candidate designs, and a PDR report will be provided to the MDA with recommended requirements trades. (The final CDD should contain trade-offs determined during the TD phase). -Engineering & Manufacturing Development (EMD) replaces System Development and Demonstration (SDD). There is more emphasis on systems engineering and technical reviews. The two major efforts have been renamed. The PM must provide a PDR report, and must provide a Critical Design Review (CDR) report to the MDA (more on this later). A Post-CDR Assessment replaces the Design Readiness Review. The MDA will determine if the results of the CDR warrant continuing EMD to Milestone C. SE is much more robust throughout all phases, with mandatory technical reviews. The major differences between the 2003 and 2008 versions of the DoDI 5000.02 are: -The Materiel Development Decision (MDD) replaces the Concept Decision (CD). A MDD is required regardless of where the program intends to enter the acquisition process. NOTE: The arrows from User Needs/Technology Opportunities now point to the MDD at the extreme left: THIS DOES NOT MEAN THAT EVERY PROGRAM MUST ENTER AT THE MATERIEL SOLUTION ANALYSIS PHASE. This is illustrated better on chart 5. -The Materiel Solution Analysis Phase (MSA) replaces the Concept Refinement (CR) Phase. MSA is not �refinement� of the preferred solution(s) identified in the ICD. The JCIDS process no longer includes an Analysis of Materiel and Non-Materiel Alternatives. Non-materiel solutions will be handled IAW JCIDS; however, all analysis of alternative materiel solutions will be accomplished by the AoA during MSA. The MDA will approve the materiel solution at Milestone A. -Technology Development: This phase now includes a mandatory requirement for competitive prototyping of the system or key-system elements. A Preliminary Design Review (PDR) may be conducted for the candidate designs, and a PDR report will be provided to the MDA with recommended requirements trades. (The final CDD should contain trade-offs determined during the TD phase). -Engineering & Manufacturing Development (EMD) replaces System Development and Demonstration (SDD). There is more emphasis on systems engineering and technical reviews. The two major efforts have been renamed. The PM must provide a PDR report, and must provide a Critical Design Review (CDR) report to the MDA (more on this later). A Post-CDR Assessment replaces the Design Readiness Review. The MDA will determine if the results of the CDR warrant continuing EMD to Milestone C. SE is much more robust throughout all phases, with mandatory technical reviews.

8. This is Figure 2., DoDI 5000.02. Key Point: While EA should get systems to the field faster, there are some complex areas that need attention: -The user needs to specify timing of requirements leading to full capability over a selected number of increments/period of time. The PM must be involved in the development of the requirements documents (CDD/CPD). -Sustainment must consider how feedback from fielded systems will be captured to determine impact on sustainment, not just on warfighting capability. The sustainment strategy must also consider PBL, and must consider any need to upgrade fielded systems or to manage various configurations. Note: The �gap analysis� is short-hand for the JCIDS Capabilities-Based Assessment (CBA) process. As previously pointed out: CBA is under revision, and will not longer include a detailed analysis of materiel alternatives. The ICD is being modified to eliminate the priority listing of materiel alternatives. The assessment of materiel alternatives is being shifted to the AoA process. Milestone A. Major systems that have technology development phase must have a MS A to authorize entry. This applies to ACAT I and II programs and is likely to be extended to other ACATs by the CAEs. Also applies to subsequent increments of an EA program that need a TD phase to mature technology (not all will). This is Figure 2., DoDI 5000.02. Key Point: While EA should get systems to the field faster, there are some complex areas that need attention: -The user needs to specify timing of requirements leading to full capability over a selected number of increments/period of time. The PM must be involved in the development of the requirements documents (CDD/CPD). -Sustainment must consider how feedback from fielded systems will be captured to determine impact on sustainment, not just on warfighting capability. The sustainment strategy must also consider PBL, and must consider any need to upgrade fielded systems or to manage various configurations. Note: The �gap analysis� is short-hand for the JCIDS Capabilities-Based Assessment (CBA) process. As previously pointed out: CBA is under revision, and will not longer include a detailed analysis of materiel alternatives. The ICD is being modified to eliminate the priority listing of materiel alternatives. The assessment of materiel alternatives is being shifted to the AoA process. Milestone A. Major systems that have technology development phase must have a MS A to authorize entry. This applies to ACAT I and II programs and is likely to be extended to other ACATs by the CAEs. Also applies to subsequent increments of an EA program that need a TD phase to mature technology (not all will).

9. -EA now just one process as shown. No �spirals�. Term spiral development no longer used as an EA strategy term. �Spirals� are out. �Spiral Development� is an engineering term that will continue to be used for software development. However, using it as a �strategy� term caused problems �Increments� are in. -Each increment is a militarily-useful and supportable operational capability that can be developed, produced, deployed, and sustained. -Each increment will have its own set of threshold and objective values set by the user. -Block upgrades, pre-planned product improvement, and similar efforts that provide a significant increase in operational capability and meet an acquisition category threshold specified in this document shall be managed as separate increments. . -EA now just one process as shown. No �spirals�. Term spiral development no longer used as an EA strategy term. �Spirals� are out. �Spiral Development� is an engineering term that will continue to be used for software development. However, using it as a �strategy� term caused problems �Increments� are in. -Each increment is a militarily-useful and supportable operational capability that can be developed, produced, deployed, and sustained. -Each increment will have its own set of threshold and objective values set by the user. -Block upgrades, pre-planned product improvement, and similar efforts that provide a significant increase in operational capability and meet an acquisition category threshold specified in this document shall be managed as separate increments. .

10. For some, this chart better illustrates that programs may enter the process at points further to the right than the MSA phase. The change from 2003 is that now an MDD is required to determine what the appropriate entry point will be. This chart also shows the JCIDS process at the front end. The policy for JCIDS is under revision, with a revised CJCSI 3170.01G due out soon. CJCSM 3170.01C will be cancelled and replaced with a �manual� posted on the J8 website on the SIPRNET. Non-SIPRNET access is not known at this time.For some, this chart better illustrates that programs may enter the process at points further to the right than the MSA phase. The change from 2003 is that now an MDD is required to determine what the appropriate entry point will be. This chart also shows the JCIDS process at the front end. The policy for JCIDS is under revision, with a revised CJCSI 3170.01G due out soon. CJCSM 3170.01C will be cancelled and replaced with a �manual� posted on the J8 website on the SIPRNET. Non-SIPRNET access is not known at this time.

11. MDD: the formal entry into the acquisition process; mandatory for all programs. -At the MDD, the Joint Staff presents JROC recommendations; the Component presents the ICD with a preliminary CONOPS, description of capability needed, operational risks, and basis for why a non-materiel solution(s) will not fill the need (or completely fill the need). --The MDA approves the guidance for conduct of the AoA (for ACAT I programs, OSD/PA&E provides); determines the phase of entry into the process; and designates the lead Component. --The lead Component prepares the AoA study plan after approval of the study guidance at the MDD. Post PDR Assessment: Required only if PDR comes after Milestone B. More on PDRs later. Post CDR Assessment: -MDA conducts based on a post-CDR report from the PM. -Post CDR Report provides assessment of design maturity, a summary of the issues and actions PM intends to take to resolve the issues, assessment of risk of meeting exit criteria for EMDD phase, potential issues that could result in an APB breach. -MDA reviews the PM�s report and decides if program is ready/not ready to proceed in EMD and issue an ADM.MDD: the formal entry into the acquisition process; mandatory for all programs. -At the MDD, the Joint Staff presents JROC recommendations; the Component presents the ICD with a preliminary CONOPS, description of capability needed, operational risks, and basis for why a non-materiel solution(s) will not fill the need (or completely fill the need). --The MDA approves the guidance for conduct of the AoA (for ACAT I programs, OSD/PA&E provides); determines the phase of entry into the process; and designates the lead Component. --The lead Component prepares the AoA study plan after approval of the study guidance at the MDD. Post PDR Assessment: Required only if PDR comes after Milestone B. More on PDRs later. Post CDR Assessment: -MDA conducts based on a post-CDR report from the PM. -Post CDR Report provides assessment of design maturity, a summary of the issues and actions PM intends to take to resolve the issues, assessment of risk of meeting exit criteria for EMDD phase, potential issues that could result in an APB breach. -MDA reviews the PM�s report and decides if program is ready/not ready to proceed in EMD and issue an ADM.

12. Materiel Solution Analysis (MSA). Major change: AoA no longer �refines� materiel solution(s) identified in the ICD. ICD will no longer contain prioritized materiel solutions. Technology Development. Major change: The TDS and associated funding must provide for two or more competing teams producing prototypes of the system and/or key system elements prior to, or through, Milestone B. PDR conducted for candidate designs and PDR report provided to MDA at Milestone B. Guided by the ICD, draft CDD, the TDS and systems engineering planning. (Note, 5000.02 does not mention draft CDD; however, revised 3170 will make this clear). Engineering & Manufacturing Development. Major changes: Establishment of the product baseline for all configuration items prior to P-CDR Assessment. Requires that selected production-representative article be demonstrated in their intended environment and that manufacturing processes have been effectively demonstrated prior to MS C. Names and some activities of two major efforts changed: covered later.Materiel Solution Analysis (MSA). Major change: AoA no longer �refines� materiel solution(s) identified in the ICD. ICD will no longer contain prioritized materiel solutions. Technology Development. Major change: The TDS and associated funding must provide for two or more competing teams producing prototypes of the system and/or key system elements prior to, or through, Milestone B. PDR conducted for candidate designs and PDR report provided to MDA at Milestone B. Guided by the ICD, draft CDD, the TDS and systems engineering planning. (Note, 5000.02 does not mention draft CDD; however, revised 3170 will make this clear). Engineering & Manufacturing Development. Major changes: Establishment of the product baseline for all configuration items prior to P-CDR Assessment. Requires that selected production-representative article be demonstrated in their intended environment and that manufacturing processes have been effectively demonstrated prior to MS C. Names and some activities of two major efforts changed: covered later.

13. PDR Before MS B: �When consistent with technology development phase objectives, associated prototyping activity, and the MDA approved TDS, the PM shall plan a Preliminary Design Review (PDR) before Milestone B.� PDR planning is reflected in the TDS and conducted for the candidate design(s) to establish the allocated baseline (hardware, software, human/support systems) and underlying architectures and to define a high-confidence design. All system elements (hardware and software) must be at a level of maturity commensurate with the PDR entrance and exit criteria. A successful PDR informs requirements trades; improves cost estimation; and identifies remaining design, integration, and manufacturing risks. The PDR is conducted at the system level and includes user representatives and associated certification authorities (not defined). The PDR Report is provided to the MDA at Milestone B and includes recommended requirements trades based upon an assessment of cost, schedule, and performance risk. PDR After MS B: �If a PDR has not been conducted prior to Milestone B, the PM shall plan for a PDR as soon as feasible after program initiation.� PDR planning is reflected in the Acquisition Strategy and conducted consistent with the policies for the TD phase PDR (above). Following PDR, the PM submits a PDR report and the MDA conducts a formal Post-PDR Assessment. The PDR report reflects any requirements trades based upon the PM�s assessment of cost, schedule, and performance risk. The MDA will consider the results of the PDR and the PM�s assessment, and determine whether remedial action is necessary to achieve APB objectives. The results of the MDA's Post-PDR Assessment are documented in an ADM. PDR Before MS B: �When consistent with technology development phase objectives, associated prototyping activity, and the MDA approved TDS, the PM shall plan a Preliminary Design Review (PDR) before Milestone B.� PDR planning is reflected in the TDS and conducted for the candidate design(s) to establish the allocated baseline (hardware, software, human/support systems) and underlying architectures and to define a high-confidence design. All system elements (hardware and software) must be at a level of maturity commensurate with the PDR entrance and exit criteria. A successful PDR informs requirements trades; improves cost estimation; and identifies remaining design, integration, and manufacturing risks. The PDR is conducted at the system level and includes user representatives and associated certification authorities (not defined). The PDR Report is provided to the MDA at Milestone B and includes recommended requirements trades based upon an assessment of cost, schedule, and performance risk. PDR After MS B: �If a PDR has not been conducted prior to Milestone B, the PM shall plan for a PDR as soon as feasible after program initiation.� PDR planning is reflected in the Acquisition Strategy and conducted consistent with the policies for the TD phase PDR (above). Following PDR, the PM submits a PDR report and the MDA conducts a formal Post-PDR Assessment. The PDR report reflects any requirements trades based upon the PM�s assessment of cost, schedule, and performance risk. The MDA will consider the results of the PDR and the PM�s assessment, and determine whether remedial action is necessary to achieve APB objectives. The results of the MDA's Post-PDR Assessment are documented in an ADM.

14. Integrated System Design. This effort is intended to define system and system-of-systems functionality and interfaces, complete hardware and software detailed design, and reduce system-level risk. Integrated System Design includes the establishment of the product baseline for all configuration items. System Capability and Manufacturing Process Demonstration. This effort is intended to demonstrate the ability of the system to operate in a useful way consistent with the approved KPPs and that system production can be supported by demonstrated manufacturing processes. Program enters SCMPD upon completion of the Post-CDR Assessment and establishment of an initial product baseline. Effort ends when the system meets approved requirements and is demonstrated in its intended environment using the selected production-representative article; manufacturing processes have been effectively demonstrated; industrial capabilities are reasonably available; and the system meets or exceeds exit criteria and Milestone C entrance requirements. Successful developmental test and evaluation (DT&E) to assess technical progress against critical technical parameters, early operational assessments, and, where proven capabilities exist, the use of modeling and simulation to demonstrate system/system-of-systems integration are critical during this effort. Test and evaluation (T&E) assesses improvements to mission capability and operational support based on user needs and shall be reported in terms of operational significance to the user. Integrated System Design. This effort is intended to define system and system-of-systems functionality and interfaces, complete hardware and software detailed design, and reduce system-level risk. Integrated System Design includes the establishment of the product baseline for all configuration items. System Capability and Manufacturing Process Demonstration. This effort is intended to demonstrate the ability of the system to operate in a useful way consistent with the approved KPPs and that system production can be supported by demonstrated manufacturing processes. Program enters SCMPD upon completion of the Post-CDR Assessment and establishment of an initial product baseline. Effort ends when the system meets approved requirements and is demonstrated in its intended environment using the selected production-representative article; manufacturing processes have been effectively demonstrated; industrial capabilities are reasonably available; and the system meets or exceeds exit criteria and Milestone C entrance requirements. Successful developmental test and evaluation (DT&E) to assess technical progress against critical technical parameters, early operational assessments, and, where proven capabilities exist, the use of modeling and simulation to demonstrate system/system-of-systems integration are critical during this effort. Test and evaluation (T&E) assesses improvements to mission capability and operational support based on user needs and shall be reported in terms of operational significance to the user.

15. Preliminary Design Review (PDR)

16. EMD Phase

17. Post-CDR Assessment

18. Prototyping and Competition

19. 19 Configuration Steering Boards

20. 20 Test and Evaluation Integrated DT&E / OT&E activities Evaluations include comparison with current capability Evaluations conducted in the expected �mission context�

21. Acquisition Process: includes pre-systems acquisition, systems acquisition and sustainment. The term �pre-systems acquisition� is used to designate activities that take place prior to program initiation (normally Milestone B) User Need: This is the JCIDS process. The CBA and development of the ICD take place prior to the MDD �outside� of the acquisition process; however, CDD and CPD development take place during the acquisition process. Technology Opportunities: Placement of the text just below the TD phase can mislead some who see this chart. It is not intended to reflect that technology opportunities are only considered during TD phase. Technology opportunities may be considered during the CBA (albeit not as rigorously as before current revisions to 3170 series), most importantly during the AoA, and at any point during the acquisition process. Sources include government labs and centers, academia, and the commercial sector. Technology Projects: Encl. 3, DoDI 5000.02 has an extensive list of technology projects. Some, like JCTDs and prototype projects intended for direct transition to the field that are highlighted in the new JCIDS Manual (replaces CJCSI 3170.01C), may not require an ICD to transition to the acquisition process.Acquisition Process: includes pre-systems acquisition, systems acquisition and sustainment. The term �pre-systems acquisition� is used to designate activities that take place prior to program initiation (normally Milestone B) User Need: This is the JCIDS process. The CBA and development of the ICD take place prior to the MDD �outside� of the acquisition process; however, CDD and CPD development take place during the acquisition process. Technology Opportunities: Placement of the text just below the TD phase can mislead some who see this chart. It is not intended to reflect that technology opportunities are only considered during TD phase. Technology opportunities may be considered during the CBA (albeit not as rigorously as before current revisions to 3170 series), most importantly during the AoA, and at any point during the acquisition process. Sources include government labs and centers, academia, and the commercial sector. Technology Projects: Encl. 3, DoDI 5000.02 has an extensive list of technology projects. Some, like JCTDs and prototype projects intended for direct transition to the field that are highlighted in the new JCIDS Manual (replaces CJCSI 3170.01C), may not require an ICD to transition to the acquisition process.

22. -Not every program requires own ICD � an ICD may support many programs -MDD will take place for all programs, regardless of entry point -Lead DoD component � could be for joint acquisition program, or not. -Note that a more detailed AoA plan due after MDD. Not sure what �immediately� really means. -Study guidance for an ACAT I program comes from OSD, Dir, PA&E. AoA Plan comes from organization that will do the AoA. -Not every program requires own ICD � an ICD may support many programs -MDD will take place for all programs, regardless of entry point -Lead DoD component � could be for joint acquisition program, or not. -Note that a more detailed AoA plan due after MDD. Not sure what �immediately� really means. -Study guidance for an ACAT I program comes from OSD, Dir, PA&E. AoA Plan comes from organization that will do the AoA.

23. Point out requirements to enter and leave (exit) each phase -Note the activities, and importance of JCIDS documents (ICD) to guide each phase. -The enter and exit bullets on these charts are �generic� to all programs. Read about program specific �exit criteria� in the DAG. Materiel Solution Analysis: The purpose of this phase is different from Concept Refinement (CR). The AoA during CR was conducted to �refine� the materiel solutions prioritized in the ICD. The ICD no longer does this, so the AoA is now focused on alternative solutions provided from a number of sources: �a diversified range of large and small businesses�. Revisions to JCIDS: Because portions of the 5000.02, like the MSA phase, take into account upcoming changes to JCIDS, these changes should be pointed out. -The Functional Solutions Analysis (FSA) part of the Capabilities-Based Assessment (CBA) has been eliminated. -ICD will no longer contain a prioritized list of potential materiel alternatives. The ICD will define non-materiel options, DOTMLPF and policy changes that may lead to a Joint DCR. If non-materiel approaches are not sufficient to mitigate the warfighting capability gap, and a materiel solution is required, the ICD will make a recommendation on the type of materiel solution preferred: IT system, evolution of existing systems with significant capability improvement, or a transformational approach for �breakout� systems that differ significantly in form, function, operation and capabilities from existing systems and offer significant improvement over current capabilities or transform how the mission is accomplished. -These materiel options will be investigated during the MSA phase during the AoA. Concurrent with the AoA, a draft CDD (see draft CJCSI 3170.01G) will be prepared to guide the TD phase activities.Point out requirements to enter and leave (exit) each phase -Note the activities, and importance of JCIDS documents (ICD) to guide each phase. -The enter and exit bullets on these charts are �generic� to all programs. Read about program specific �exit criteria� in the DAG. Materiel Solution Analysis: The purpose of this phase is different from Concept Refinement (CR). The AoA during CR was conducted to �refine� the materiel solutions prioritized in the ICD. The ICD no longer does this, so the AoA is now focused on alternative solutions provided from a number of sources: �a diversified range of large and small businesses�. Revisions to JCIDS: Because portions of the 5000.02, like the MSA phase, take into account upcoming changes to JCIDS, these changes should be pointed out. -The Functional Solutions Analysis (FSA) part of the Capabilities-Based Assessment (CBA) has been eliminated. -ICD will no longer contain a prioritized list of potential materiel alternatives. The ICD will define non-materiel options, DOTMLPF and policy changes that may lead to a Joint DCR. If non-materiel approaches are not sufficient to mitigate the warfighting capability gap, and a materiel solution is required, the ICD will make a recommendation on the type of materiel solution preferred: IT system, evolution of existing systems with significant capability improvement, or a transformational approach for �breakout� systems that differ significantly in form, function, operation and capabilities from existing systems and offer significant improvement over current capabilities or transform how the mission is accomplished. -These materiel options will be investigated during the MSA phase during the AoA. Concurrent with the AoA, a draft CDD (see draft CJCSI 3170.01G) will be prepared to guide the TD phase activities.

24. -Materiel Solution: Previously, the term �preferred solution� was used to describe what the MDA approved at MS A. �Approved materiel solution� makes a clearer statement. -Technology Development Strategy must be approved before release of final RFP for TD phase. -Milestone A Certification, (MDA Program Certification) at Milestone A, is a statutory requirement (see backup slide). It is a signed MFR from the MDA; cannot be delegated. -Component Cost Estimate (CCE): a new name for Component Cost Analysis (CCA) -Item Unique Identification (IUID) Implementation Plan. DoDI 8320.04, requires unique IUID identifiers be established to enable items to be tracked and traced throughout their lifecycle -Life Cycle Signature Support Plan. Signature. A distinctive basic characteristic or set of characteristics that consistently re-occurs and uniquely identifies a piece of equipment, activity, individual, or event. Life-Cycle Signature Support Plans. A management plan that is applied throughout the life of a signature-dependent acquisition that bases all programmatic decisions on the anticipated mission-related and economic benefits derived over the life of a signature-dependent acquisition. See DoDD 5250.01. -Systems Engineering Plan. PM prepares a SEP for each milestone review, beginning with MS A. At MS A, the SEP supports the TDS; at MS B or later, the SEP supports the Acquisition Strategy. The SEP describes the program�s overall technical approach, including key technical risks, processes, resources, metrics, and applicable performance incentives. It also details the timing, conduct, and success criteria for technical reviews.-Materiel Solution: Previously, the term �preferred solution� was used to describe what the MDA approved at MS A. �Approved materiel solution� makes a clearer statement. -Technology Development Strategy must be approved before release of final RFP for TD phase. -Milestone A Certification, (MDA Program Certification) at Milestone A, is a statutory requirement (see backup slide). It is a signed MFR from the MDA; cannot be delegated. -Component Cost Estimate (CCE): a new name for Component Cost Analysis (CCA) -Item Unique Identification (IUID) Implementation Plan. DoDI 8320.04, requires unique IUID identifiers be established to enable items to be tracked and traced throughout their lifecycle -Life Cycle Signature Support Plan. Signature. A distinctive basic characteristic or set of characteristics that consistently re-occurs and uniquely identifies a piece of equipment, activity, individual, or event. Life-Cycle Signature Support Plans. A management plan that is applied throughout the life of a signature-dependent acquisition that bases all programmatic decisions on the anticipated mission-related and economic benefits derived over the life of a signature-dependent acquisition. See DoDD 5250.01. -Systems Engineering Plan. PM prepares a SEP for each milestone review, beginning with MS A. At MS A, the SEP supports the TDS; at MS B or later, the SEP supports the Acquisition Strategy. The SEP describes the program�s overall technical approach, including key technical risks, processes, resources, metrics, and applicable performance incentives. It also details the timing, conduct, and success criteria for technical reviews.

25. Milestone A Certification (10 USC 2366a) A major defense acquisition program may not receive Milestone A approval, or Key Decision Point A approval in the case of a space program, until the MDA certifies, after consultation with the JROC on matters related to program requirements and military needs� (1) That the system fulfills an approved initial capabilities document; (2) That the system is being executed by an entity with a relevant core competency as identified by the Secretary of Defense under section 118b of Title 10, U.S. Code; (3) If the system duplicates a capability already provided by an existing system, the duplication provided by such system is necessary and appropriate; and (4) That a cost estimate for the system has been submitted and that the level of resources required to develop and procure the system is consistent with the priority level assigned by the JROC

26. The blue bold items in italics highlight the emphasis on systems engineering in technology development. Competitive Prototyping: Two or more competing teams producing prototypes of the system and/or key system elements. RAM Strategy: Reliability, Availability, and Maintainability strategy that includes a reliability growth program is documented in the SEP, in the LCSP, and assessed during tech reviews, T&E and Program Support Reviews. Preliminary Design Review (PDR). -A PDR will be conducted for the candidate design(s) to establish the allocated baseline (hardware, software, human/support systems) and underlying architectures and to define a high-confidence design. -A successful PDR informs requirements trades; improves cost estimates; and identifies remaining design, integration, and manufacturing risks. -The PDR will be conducted at the system level and include user representatives and associated certification authorities. -A PDR Report is provided to the MDA at Milestone B and includes recommended requirements trades based upon an assessment of cost, schedule, and performance risk. -Note: The CDD KPPs and other performance attributes should reflect the trades from the PDR report; however, the CDD must be approved before MS B. The requirements trades recommended at MS B could be the �derived� technical requirements, not sure.The blue bold items in italics highlight the emphasis on systems engineering in technology development. Competitive Prototyping: Two or more competing teams producing prototypes of the system and/or key system elements. RAM Strategy: Reliability, Availability, and Maintainability strategy that includes a reliability growth program is documented in the SEP, in the LCSP, and assessed during tech reviews, T&E and Program Support Reviews. Preliminary Design Review (PDR). -A PDR will be conducted for the candidate design(s) to establish the allocated baseline (hardware, software, human/support systems) and underlying architectures and to define a high-confidence design. -A successful PDR informs requirements trades; improves cost estimates; and identifies remaining design, integration, and manufacturing risks. -The PDR will be conducted at the system level and include user representatives and associated certification authorities. -A PDR Report is provided to the MDA at Milestone B and includes recommended requirements trades based upon an assessment of cost, schedule, and performance risk. -Note: The CDD KPPs and other performance attributes should reflect the trades from the PDR report; however, the CDD must be approved before MS B. The requirements trades recommended at MS B could be the �derived� technical requirements, not sure.

27. Program Initiation (not �new start�). Effort was a new start in PPBE when funding for MSA and TD phases were sought) -Important: at MS B PM must demonstrate �full funding� in FYDP � i.e., at least 6 years of funding. -PM was probably assigned prior to MS A � need someone in charge to get ready for MS A and B. -Content of acq strategy is in DAG, Chapt. 2. -Acq Strategy must be approved before release of final RFP for EMD. -APB reflects KPPs, and other data for schedule and cost � all related to the CDD and to key programmatic activities (such as T&E) -Certification required by Congress (see backup). Nothing in required certification not already required by 5000.02. -Exit criteria is program specific (e.g., attain first flight prior to MS C). -Type of contract: If MDAP and cost-type is chosen, needs written determination by MDA. DAG will have to address this. Waiting for MS B to get decision is no-go. Need contractor proposals in hand prior to MS B for obvious reasons. Program Initiation (not �new start�). Effort was a new start in PPBE when funding for MSA and TD phases were sought) -Important: at MS B PM must demonstrate �full funding� in FYDP � i.e., at least 6 years of funding. -PM was probably assigned prior to MS A � need someone in charge to get ready for MS A and B. -Content of acq strategy is in DAG, Chapt. 2. -Acq Strategy must be approved before release of final RFP for EMD. -APB reflects KPPs, and other data for schedule and cost � all related to the CDD and to key programmatic activities (such as T&E) -Certification required by Congress (see backup). Nothing in required certification not already required by 5000.02. -Exit criteria is program specific (e.g., attain first flight prior to MS C). -Type of contract: If MDAP and cost-type is chosen, needs written determination by MDA. DAG will have to address this. Waiting for MS B to get decision is no-go. Need contractor proposals in hand prior to MS B for obvious reasons.

28. Point out new requirements in bold face type.Point out new requirements in bold face type.

30. PDR conducted if not conducted prior to MS B. Applies to programs that enter at MS B, or if design changes occur during TD that require PDR after EMD contract award. PDR report provided by PM to MDA. Post-PDR Assessment required if PDR conducted after MS B. Same rules as for pre-MS B PDR (see Technology Development chart), to include ADM. Post CDR Assessment: -System-Level CDR Conducted as soon as practicable after Program Initiation -PM Provides a Post-CDR Report -MDA Reviews the Post-CDR Report and the PM�s Plans to Resolve or Mitigate Issues/Risks -Results of the Post-CDR Assessment are Documented in an ADM Note use of Production-Representative articles. Previous 5000.2 said, �prototypes or EDMs�. Even though DAU defines EDMs as production representative, there is no DoD-level standard use of the term. The use of production-representative articles is particularly important for those programs that do not have LRIP and MS C is the production decision. PDR conducted if not conducted prior to MS B. Applies to programs that enter at MS B, or if design changes occur during TD that require PDR after EMD contract award. PDR report provided by PM to MDA. Post-PDR Assessment required if PDR conducted after MS B. Same rules as for pre-MS B PDR (see Technology Development chart), to include ADM. Post CDR Assessment: -System-Level CDR Conducted as soon as practicable after Program Initiation -PM Provides a Post-CDR Report -MDA Reviews the Post-CDR Report and the PM�s Plans to Resolve or Mitigate Issues/Risks -Results of the Post-CDR Assessment are Documented in an ADM Note use of Production-Representative articles. Previous 5000.2 said, �prototypes or EDMs�. Even though DAU defines EDMs as production representative, there is no DoD-level standard use of the term. The use of production-representative articles is particularly important for those programs that do not have LRIP and MS C is the production decision.

31. No change from 2003 DoDI 5000.02.No change from 2003 DoDI 5000.02.

32. Point out new requirements in bold face type.Point out new requirements in bold face type.

33. Essentially same as the 2003 DoDI 5000.02. Guided By: DoDI 5000.02 indicates what documents �guide� the phase activities for MSA, TD and EMD; however, it does not state what documents guide Production and Deployment. So, shown here some obvious documents that guide the activities. Essentially same as the 2003 DoDI 5000.02. Guided By: DoDI 5000.02 indicates what documents �guide� the phase activities for MSA, TD and EMD; however, it does not state what documents guide Production and Deployment. So, shown here some obvious documents that guide the activities.

34. No change from 2003 version of DoDI 5000.02.No change from 2003 version of DoDI 5000.02.

35. Point out new requirements in bold face type.Point out new requirements in bold face type.

36. Performance-Based Life-Cycle Product Support (PBL), has the same meaning as Performance-Based Logistics (PBL) and uses the same acronym. Guided By: DoDI 5000.02 indicates what documents �guide� the phase activities for MSA, TD and EMD; however, it does not state what documents guide Operations and Support. So, shown here are some obvious documents that guide the activities. Performance-Based Life-Cycle Product Support (PBL), has the same meaning as Performance-Based Logistics (PBL) and uses the same acronym. Guided By: DoDI 5000.02 indicates what documents �guide� the phase activities for MSA, TD and EMD; however, it does not state what documents guide Operations and Support. So, shown here are some obvious documents that guide the activities.

37. Military Equipment Valuation (accounting for military equipment) MDA Certification at Milestones A & B Cost type contract for EMD Phase requires written determination by MDA Lead Systems Integrator Restrictions Replaced System Sustainment Plan Configuration Steering Boards (CSBs) -Military Equipment Valuation (accounting for military equipment): Acq strategy at MS C must provide that all equipment requiring capitalization is serially identified and valued at full cost. Full cost must be entered in the Item Unique Identification (IUID) registry. All systems are tracked throughout life cycle via IUID. -MDA certification at MS A & B. MDAPs only. MFR signed by MDA. --MS A cert: fulfills an approved ICD; executed by entity with relevant core competency; cost est. submitted; and if duplicating other capability the duplication is necessary. --MS B cert: affordable, reasonable cost and schedule est. submitted, funding avail, market research conducted, AoA done, JROC on board, technology mature, high likelihood of msn accomplishment, and complies with all statutory and regulatory requirements. MS B cert memo must be provided to the congressional defense committees. -Contracting for EMD: MDAPs only: type contract based on risk; if cost type MDA must sign written determination that risk does not permit fixed price contract. -Lead Sys Integrator (major systems): if used, MDA must ensure contractor does not/will not have a direct financial interest in the system. -Replaced System Sustainment Plan (sustainment plan for the existing system): MDAPs only: Required if existing sys remains necessary during fielding of replacement system; includes budget for sustainment of existing system; includes analysis of ability of existing system to meet mission requirements against threat. -Configuration Steering Boards: CAEs must establish to review all requirements and significant technical configuration changes that have potential to impact cost and schd of ACAT I and IA. Generally, changes will be rejected and deferred to future increments. Required by DoDI 5000.02 for ACAT I and IA; required by public law (FY09 NDAA, section 814) for MDAPs) -Military Equipment Valuation (accounting for military equipment): Acq strategy at MS C must provide that all equipment requiring capitalization is serially identified and valued at full cost. Full cost must be entered in the Item Unique Identification (IUID) registry. All systems are tracked throughout life cycle via IUID. -MDA certification at MS A & B. MDAPs only. MFR signed by MDA. --MS A cert: fulfills an approved ICD; executed by entity with relevant core competency; cost est. submitted; and if duplicating other capability the duplication is necessary. --MS B cert: affordable, reasonable cost and schedule est. submitted, funding avail, market research conducted, AoA done, JROC on board, technology mature, high likelihood of msn accomplishment, and complies with all statutory and regulatory requirements. MS B cert memo must be provided to the congressional defense committees. -Contracting for EMD: MDAPs only: type contract based on risk; if cost type MDA must sign written determination that risk does not permit fixed price contract. -Lead Sys Integrator (major systems): if used, MDA must ensure contractor does not/will not have a direct financial interest in the system. -Replaced System Sustainment Plan (sustainment plan for the existing system): MDAPs only: Required if existing sys remains necessary during fielding of replacement system; includes budget for sustainment of existing system; includes analysis of ability of existing system to meet mission requirements against threat. -Configuration Steering Boards: CAEs must establish to review all requirements and significant technical configuration changes that have potential to impact cost and schd of ACAT I and IA. Generally, changes will be rejected and deferred to future increments. Required by DoDI 5000.02 for ACAT I and IA; required by public law (FY09 NDAA, section 814) for MDAPs)

38. New MAIS Reporting Requirements �Time-Certain� IT Business Systems Development Defense Business Systems Oversight MDA assessment of compliance with chemical, biological, radiological, and nuclear survivability (CBRN) requirements at Milestones B and C -MAIS Reporting: Statutory requirements for reporting to Congress, of: 1. Cancellation or significant (not defined) reduction in scope. 2. Significant program change (schedule slip of more than 6 mos but less than 1 yr); increase in estimated development or life cycle cost of at least 15% but less than 25%; significant adverse change (not defined) in expected performance. 3. Critical program changes (failure to meet IOC w/in 5-years after funds were first obligated for the program (probably defined as MS A/TD phase); delay of 1 year or more in any program schedule; 25% increase in estimated development or life cycle cost; change in performance that undermines ability to perform functions anticipated. 4. Report to Congress of cost, sch, and performance information (annually w/in 45 days of Presidents Budget). 5. PMs report of variances in cost, sch, or KPPs (any variance from the first report to Congress) -Time Certain IT Business System Development: MDA cannot approve MS A unless system can achieve IOC within 5 years. -Defense Business Systems Oversight: new encl 11 provides the Investment Review Board certification and Defense Business Sys Mgmt Committee approval process. (covered in more detail later) -MDA assessment of compliance with CBRN requirements: See DoDI 3150.09, 17 Sep 2008. Applies to �mission-critical� CBRN systems regardless of ACAT. Mission-critical is determined by the sponsor developing the JCIDS documents (ICD/CDD/CPD). Encl 5 to DoDI 3150.09 has a tool that can be used by the sponsor to decide if CBRN mission-critical designation is required. Also requires nuclear survivability KPP for CBRN mission-critical systems covered by DoDD S-5210.81. -MAIS Reporting: Statutory requirements for reporting to Congress, of: 1. Cancellation or significant (not defined) reduction in scope. 2. Significant program change (schedule slip of more than 6 mos but less than 1 yr); increase in estimated development or life cycle cost of at least 15% but less than 25%; significant adverse change (not defined) in expected performance. 3. Critical program changes (failure to meet IOC w/in 5-years after funds were first obligated for the program (probably defined as MS A/TD phase); delay of 1 year or more in any program schedule; 25% increase in estimated development or life cycle cost; change in performance that undermines ability to perform functions anticipated. 4. Report to Congress of cost, sch, and performance information (annually w/in 45 days of Presidents Budget). 5. PMs report of variances in cost, sch, or KPPs (any variance from the first report to Congress) -Time Certain IT Business System Development: MDA cannot approve MS A unless system can achieve IOC within 5 years. -Defense Business Systems Oversight: new encl 11 provides the Investment Review Board certification and Defense Business Sys Mgmt Committee approval process. (covered in more detail later) -MDA assessment of compliance with CBRN requirements: See DoDI 3150.09, 17 Sep 2008. Applies to �mission-critical� CBRN systems regardless of ACAT. Mission-critical is determined by the sponsor developing the JCIDS documents (ICD/CDD/CPD). Encl 5 to DoDI 3150.09 has a tool that can be used by the sponsor to decide if CBRN mission-critical designation is required. Also requires nuclear survivability KPP for CBRN mission-critical systems covered by DoDD S-5210.81.

39. Detailed Acquisition of Services Policy Independent management reviews (Peer Reviews) for supplies and services contracts Interim Beyond LRIP Report DOT&E�s Role in Testing Force Protection Equipment / Non-Lethal Weapons Nunn-McCurdy breach / APB Revision Procedure -Acquisition of Services: expanded policy includes dollar threshold for oversight and review of services. IT of more than $500M, all services of more than $1B, and others as designated by USD(AT&L)/ASD(NII) must go to USD(AT&L)/ASD(NII) for review and approval (could be a briefing or a written notification) prior to proceeding with the solicitation. Peer Reviews. Director, DPAP, will organize review teams for pre-award and post-award Peer Reviews for service contracts with estimated value of $1 billion or more. Teams include senior contracting leaders from across DoD and members of the Office of General Counsel who are civilian employees or military personnel from outside of department or agency whose procurement is the subject of the Peer Review. Component Decision Authorities establish procedures for Peer Reviews for contracts valued at less than $1 billion. -Interim Beyond LRIP Report: DOT&E submits to congress if decision is made to proceed to operational use or procurement funds are made available before FRP decision. Final report still due prior to formal FRP decision. -Force protection equipment (to include non-lethal weapons) must be separate category on OSD T&E Oversight List, and DOT&E must expedite the testing process. -New Table 6 describes revised statutory requirements for the APB �original� or first APB, and �current� or a revision of original APB. Provides detailed guidance for APB revision and Nunn-McCurdy significant and critical cost threshold breaches as they relate to the original and current APBs. After a critical breach (PAUC or APUC increase of 25% over current APB; 50% PAUC or APUC increase over original APB) and certification to Congress a new original APB is formed. Only the current APB may be revised based on significant breach (15% over current APB; 30% over original APB)-Acquisition of Services: expanded policy includes dollar threshold for oversight and review of services. IT of more than $500M, all services of more than $1B, and others as designated by USD(AT&L)/ASD(NII) must go to USD(AT&L)/ASD(NII) for review and approval (could be a briefing or a written notification) prior to proceeding with the solicitation. Peer Reviews. Director, DPAP, will organize review teams for pre-award and post-award Peer Reviews for service contracts with estimated value of $1 billion or more. Teams include senior contracting leaders from across DoD and members of the Office of General Counsel who are civilian employees or military personnel from outside of department or agency whose procurement is the subject of the Peer Review. Component Decision Authorities establish procedures for Peer Reviews for contracts valued at less than $1 billion. -Interim Beyond LRIP Report: DOT&E submits to congress if decision is made to proceed to operational use or procurement funds are made available before FRP decision. Final report still due prior to formal FRP decision. -Force protection equipment (to include non-lethal weapons) must be separate category on OSD T&E Oversight List, and DOT&E must expedite the testing process. -New Table 6 describes revised statutory requirements for the APB �original� or first APB, and �current� or a revision of original APB. Provides detailed guidance for APB revision and Nunn-McCurdy significant and critical cost threshold breaches as they relate to the original and current APBs. After a critical breach (PAUC or APUC increase of 25% over current APB; 50% PAUC or APUC increase over original APB) and certification to Congress a new original APB is formed. Only the current APB may be revised based on significant breach (15% over current APB; 30% over original APB)

40. -SE policy: New encl 12 institutionalizes SE policy memos over last 3 years or so: requires SEP; lead SE on PEO staff; event driven tech reviews; config mgmt, etc.. -Program Support Reviews: Cross functional review to inform MDA and PM on cost, sch, perf risks and recommendations for mitigation. For ACAT ID and IAM planned by OSD/AT&L Dir SE and Software Engineering to support OIPT reviews. -Integrated T&E: Close coordination of DT and OT and integration of test activities with requirements definition and systems design and development. Must maintain IOT&E independence per statutory requirements. -Performance requirements that do not support KPPs �shall be limited and considered a part of the engineering trade space during development.� OT&E must clearly distinguish between performance values that do not meet threshold values in the CDD/CPD and those that should be improved to provide enhanced capability in future upgrades. -Comparison with current mission capabilities: OT&E includes this evaluation to determine �measurable improvements� have been made. PM can recommend alternative eval approach if this is too costly. Further, evaluations �shall make a clear distinction� between deficiencies related to approved requirements and those that are recommendations for improvement not related to approved requirements. -AOTR: Office of DUSD(A&T) will conduct independent assessment of readiness for OT of all ACAT ID and special interest programs. -Life Cycle Sustainment Plan: Describes how the sustainment strategy is being implemented. See DAG Chapt. 5 for content. -Cost of Energy: --Resource estimates: Fully burdened cost of delivered energy must be used in trade-off analysis for all tactical systems with end items that create a demand for energy --AoA: must assess alternative ways to improve the energy efficiency of DoD tactical systems consistent with mission and cost effectiveness. -SE policy: New encl 12 institutionalizes SE policy memos over last 3 years or so: requires SEP; lead SE on PEO staff; event driven tech reviews; config mgmt, etc.. -Program Support Reviews: Cross functional review to inform MDA and PM on cost, sch, perf risks and recommendations for mitigation. For ACAT ID and IAM planned by OSD/AT&L Dir SE and Software Engineering to support OIPT reviews. -Integrated T&E: Close coordination of DT and OT and integration of test activities with requirements definition and systems design and development. Must maintain IOT&E independence per statutory requirements. -Performance requirements that do not support KPPs �shall be limited and considered a part of the engineering trade space during development.� OT&E must clearly distinguish between performance values that do not meet threshold values in the CDD/CPD and those that should be improved to provide enhanced capability in future upgrades. -Comparison with current mission capabilities: OT&E includes this evaluation to determine �measurable improvements� have been made. PM can recommend alternative eval approach if this is too costly. Further, evaluations �shall make a clear distinction� between deficiencies related to approved requirements and those that are recommendations for improvement not related to approved requirements. -AOTR: Office of DUSD(A&T) will conduct independent assessment of readiness for OT of all ACAT ID and special interest programs. -Life Cycle Sustainment Plan: Describes how the sustainment strategy is being implemented. See DAG Chapt. 5 for content. -Cost of Energy: --Resource estimates: Fully burdened cost of delivered energy must be used in trade-off analysis for all tactical systems with end items that create a demand for energy --AoA: must assess alternative ways to improve the energy efficiency of DoD tactical systems consistent with mission and cost effectiveness.

41. Contract Incentives Strategy. Acquisition Strategy must describe how PM plans to employ contract incentives to achieve cost, schedule, and performance outcomes. During TD and subsequent phases PM must give small business maximum opportunities and where feasible employ Ability One program (formerly Javits-Wagner-O�Day) Contracting for Operational Support Services. PMs must coordinate with the Component manpower authority in advance of contracting for operational support services to ensure that tasks and duties that are designated as inherently governmental or exempt are not contracted. Determination of the workforce mix in accordance with DoD Instruction 1100.22, Reference (bl). Approval of TDS prior to release of final RFP for TD phase. PM cannot commit to any particular contracting strategy until TDS is approved. Approval of Acq Strategy prior to release of final RFP for EMD or any succeeding phase. Due to need for information obtained from contractor(s) proposals for EMD prior to MS B review, probably need to get acquisition strategy approval lead time from MS B to allow for release of draft and final RFPs and proposal evaluation. RAM strategy that includes a reliability growth program is required and must be documented in SEP and LCSP. Assessed during tech reviews, during T&E, and during PSRs. Data Management Strategy: acquisition strategy element; assessment of data required to design, manufacture, and sustain system, and addresses merits of priced contract option for future delivery of technical data and intellectual property rights not acquired on initial contract. Evolutionary Acquisition description revised (next chart).Contract Incentives Strategy. Acquisition Strategy must describe how PM plans to employ contract incentives to achieve cost, schedule, and performance outcomes. During TD and subsequent phases PM must give small business maximum opportunities and where feasible employ Ability One program (formerly Javits-Wagner-O�Day) Contracting for Operational Support Services. PMs must coordinate with the Component manpower authority in advance of contracting for operational support services to ensure that tasks and duties that are designated as inherently governmental or exempt are not contracted. Determination of the workforce mix in accordance with DoD Instruction 1100.22, Reference (bl). Approval of TDS prior to release of final RFP for TD phase. PM cannot commit to any particular contracting strategy until TDS is approved. Approval of Acq Strategy prior to release of final RFP for EMD or any succeeding phase. Due to need for information obtained from contractor(s) proposals for EMD prior to MS B review, probably need to get acquisition strategy approval lead time from MS B to allow for release of draft and final RFPs and proposal evaluation. RAM strategy that includes a reliability growth program is required and must be documented in SEP and LCSP. Assessed during tech reviews, during T&E, and during PSRs. Data Management Strategy: acquisition strategy element; assessment of data required to design, manufacture, and sustain system, and addresses merits of priced contract option for future delivery of technical data and intellectual property rights not acquired on initial contract. Evolutionary Acquisition description revised (next chart).

42. Enclosures to DoDI 5000.02 1 References 2 Procedures 3 ACAT and MDA 4 Statutory and Regulatory Information and Milestone Requirements Table 5. EVM Implementation Policy Table 6. APB Policy Table 7. Unique Decision Forums 5 IT Considerations 6 Integrated T&E 7 Resource Estimation 8 Human Systems Integration 9 Acquisition of Services 10 Program Management 11 Management of Defense Business Systems 12 Systems Engineering -New Enclosure 2, Procedures, contains 95% of material that was in PART 3 of the previous document (formatting change directed by Dir, Management). -New Table 5, EVM Implementation Policy, provides requirements for compliance with earned value management guidelines depending on type/value of contract. -New Table 6, APB Policy is focused on the descriptions of the �original� baseline (first baseline approved at MS B), and �current� baseline (reflects current program as revised from original). --Defines �significant� and �critical� Nunn-McCurdy breaches: Applies only to MDAPs Program Acquisition Unit Cost (PAUC) or Average Procurement Unit Cost (APUC). Nunn-McCurdy breaches are based on both original and current baseline data. --APB RDT&E cost, Performance, and Schedule requirements and deviation criteria are not discussed in 5000.02; see DAG chapter 2. -New Table 7, Unique Decision Forums: --Defense Space Acquisition Board (DSAB). USD(AT&L) chairs the DSAB unless delegated to Under SECAF by USD(AT&L). see National Security Space Acquisition Policy 03-01 (available in AKSS) --Joint Intelligence Acquisition Board (JIAB). USD(AT&L) co-chairs JIAB for National Intel Programs (NIP) funded programs executed within DoD. See Intel Community Dir. (ICD) 105, 15 August 06, and Intel Community Policy Guidance (ICPG) 105.1, 12 Jul 07. Both are available at http://www.dni.gov/electronic_reading_room.htm --Missile Defense Executive Board (MDEB). USD(AT&L Chairs the MDEB. See USD(AT&L) memo, �Ballistic Missile Defense Program Implementation Guidance� http://www.mda.mil/mdalink/pdf/progimp.pdf -Revisions to enclosures and new enclosures are discussed on the next series of charts. -New Enclosure 2, Procedures, contains 95% of material that was in PART 3 of the previous document (formatting change directed by Dir, Management). -New Table 5, EVM Implementation Policy, provides requirements for compliance with earned value management guidelines depending on type/value of contract. -New Table 6, APB Policy is focused on the descriptions of the �original� baseline (first baseline approved at MS B), and �current� baseline (reflects current program as revised from original). --Defines �significant� and �critical� Nunn-McCurdy breaches: Applies only to MDAPs Program Acquisition Unit Cost (PAUC) or Average Procurement Unit Cost (APUC). Nunn-McCurdy breaches are based on both original and current baseline data. --APB RDT&E cost, Performance, and Schedule requirements and deviation criteria are not discussed in 5000.02; see DAG chapter 2. -New Table 7, Unique Decision Forums: --Defense Space Acquisition Board (DSAB). USD(AT&L) chairs the DSAB unless delegated to Under SECAF by USD(AT&L). see National Security Space Acquisition Policy 03-01 (available in AKSS) --Joint Intelligence Acquisition Board (JIAB). USD(AT&L) co-chairs JIAB for National Intel Programs (NIP) funded programs executed within DoD. See Intel Community Dir. (ICD) 105, 15 August 06, and Intel Community Policy Guidance (ICPG) 105.1, 12 Jul 07. Both are available at http://www.dni.gov/electronic_reading_room.htm --Missile Defense Executive Board (MDEB). USD(AT&L Chairs the MDEB. See USD(AT&L) memo, �Ballistic Missile Defense Program Implementation Guidance� http://www.mda.mil/mdalink/pdf/progimp.pdf -Revisions to enclosures and new enclosures are discussed on the next series of charts.

43. The Acquisition Warrior The AT&L workforce is faced with a daunting array of mandatory policy, directives, instructions, milestone documentation, best practices, local practices and oversight directions, The AT&L Knowledge Sharing System (AKSS) is specifically designed to help the workforce work efficiently within the three principle DoD management systems, (JCIDS, AT&L, and PPBE) by centrally providing the policy, processes, best practices, tools and expertise needed at the point of need. In support of AT&L�s objectives DAU has moved away from its historical �intermittent� classroom based training model, to a model where we support the workforce before, during and after formal training events.The AT&L workforce is faced with a daunting array of mandatory policy, directives, instructions, milestone documentation, best practices, local practices and oversight directions, The AT&L Knowledge Sharing System (AKSS) is specifically designed to help the workforce work efficiently within the three principle DoD management systems, (JCIDS, AT&L, and PPBE) by centrally providing the policy, processes, best practices, tools and expertise needed at the point of need. In support of AT&L�s objectives DAU has moved away from its historical �intermittent� classroom based training model, to a model where we support the workforce before, during and after formal training events.

44. BACK-UP SLIDES

45. -Investment Review Board (IRB). Replaces OIPTs for business systems that are MAIS and MDAP. Also, supports DBSMC for certification of all business systems valued at $1 million or more (see new incl. 11) -Time Certain acquisition of IT business systems, also see Table 2-1, Statutory Requirements for MAIS Acquisition Programs, Note 4, and chart 11 of this presentation. For all MAIS, a critical program change that must be reported to Congress is �system failed to achieve IOC within 5 years after funds were first obligated for the program�. This is defined as for technology development (Milestone A) or EMD (MS B) if there is no MS A/TD phase. So, evidently the 5-year from �MS A� requirement for IOC applies to both IT Business Systems and to MAIS. -DBSMC process covered in more detail in new Encl. 11. -Revision to include BEA: The BEA replaces both the DoD Financial Management Enterprise Architecture and the DoD Financial Management Enterprise Architecture Transition Plan. -Investment Review Board (IRB). Replaces OIPTs for business systems that are MAIS and MDAP. Also, supports DBSMC for certification of all business systems valued at $1 million or more (see new incl. 11) -Time Certain acquisition of IT business systems, also see Table 2-1, Statutory Requirements for MAIS Acquisition Programs, Note 4, and chart 11 of this presentation. For all MAIS, a critical program change that must be reported to Congress is �system failed to achieve IOC within 5 years after funds were first obligated for the program�. This is defined as for technology development (Milestone A) or EMD (MS B) if there is no MS A/TD phase. So, evidently the 5-year from �MS A� requirement for IOC applies to both IT Business Systems and to MAIS. -DBSMC process covered in more detail in new Encl. 11. -Revision to include BEA: The BEA replaces both the DoD Financial Management Enterprise Architecture and the DoD Financial Management Enterprise Architecture Transition Plan.

46. This chart requires no further explanation.This chart requires no further explanation.

47. AOTR does not replace Operational Test Readiness Review (OTRR) conducted at Service level. The SAE must consider results of AOTR when making decision on readiness for operational testing.AOTR does not replace Operational Test Readiness Review (OTRR) conducted at Service level. The SAE must consider results of AOTR when making decision on readiness for operational testing.

48. -Both the Contractor Cost Data Report (CCDR) and the Software Resources Data Report (SRDR) were required by Table E3.T3, May 2003 ver. Of DoDI 5000.2. Change here is the highlighting of both in Encl. 7, instead of just the CCDR. -CARD: makes sense that CARD should reflect results of PDR; also remember, the final CDD at MS B should also reflect trades conducted during TD phase, and the cost estimate at MS B should be in sync with the CDD.-Both the Contractor Cost Data Report (CCDR) and the Software Resources Data Report (SRDR) were required by Table E3.T3, May 2003 ver. Of DoDI 5000.2. Change here is the highlighting of both in Encl. 7, instead of just the CCDR. -CARD: makes sense that CARD should reflect results of PDR; also remember, the final CDD at MS B should also reflect trades conducted during TD phase, and the cost estimate at MS B should be in sync with the CDD.

49. -DoDI 5000.02, requires use of DoDI 1100.22 to determine workforce mix. -DoDI 5000.02, requires use of DoDI 1100.22 to determine workforce mix.

50. This chart needs no further explanation.This chart needs no further explanation.

51. Peer Reviews: Service contracts valued at $1B or more. -Organized by Dir, DPAP. -Teams comprised of senior contracting officials from across DoD. Pre-award of all contracts and post-award reviews for service contracts will be conducted. -Senior officials and Component decision authorities will establish procedures for peer reviews for contracts valued at less than $1B.Peer Reviews: Service contracts valued at $1B or more. -Organized by Dir, DPAP. -Teams comprised of senior contracting officials from across DoD. Pre-award of all contracts and post-award reviews for service contracts will be conducted. -Senior officials and Component decision authorities will establish procedures for peer reviews for contracts valued at less than $1B.

52. This chart needs no further explanation. This chart needs no further explanation.

53. -Previously the 4-year requirement for PMs and Deputy PMs to be assigned until at least a major milestone closest to 4 years in the position also applied to PMs of ACAT II programs; changed to 3 years for those programs. -PMAs: Required for ACAT I & II programs. Described as an �achievable and measurable annual plans that are fully resourced�. Signed by the PM, CAE, requirements and resource authority. PMA�s must establish PM�s clear authority to object to addition of new requirements that would be inconsistent with parameters established at MS B and reflected in the PMA unless approved by the CSB. -PEO command responsibilities/waivers: --The Air Force has dual-hatted the commanders of their Product Centers as PEOs. --The Army had obtained a number of waivers to dual hat some PEO�s; however, lessons learned may have reversed the process in the Army. For example, the Commander, Communications & Electronics Command (CECOM) is no longer dual-hatted as PEO C3T. Commander, Joint Munitions and Lethality Life Cycle Management Command is still dual-hatted as Commanding General, Picatinny Arsenal and PEO Ammunition. --Navy PEOs have no other command responsibilities.-Previously the 4-year requirement for PMs and Deputy PMs to be assigned until at least a major milestone closest to 4 years in the position also applied to PMs of ACAT II programs; changed to 3 years for those programs. -PMAs: Required for ACAT I & II programs. Described as an �achievable and measurable annual plans that are fully resourced�. Signed by the PM, CAE, requirements and resource authority. PMA�s must establish PM�s clear authority to object to addition of new requirements that would be inconsistent with parameters established at MS B and reflected in the PMA unless approved by the CSB. -PEO command responsibilities/waivers: --The Air Force has dual-hatted the commanders of their Product Centers as PEOs. --The Army had obtained a number of waivers to dual hat some PEO�s; however, lessons learned may have reversed the process in the Army. For example, the Commander, Communications & Electronics Command (CECOM) is no longer dual-hatted as PEO C3T. Commander, Joint Munitions and Lethality Life Cycle Management Command is still dual-hatted as Commanding General, Picatinny Arsenal and PEO Ammunition. --Navy PEOs have no other command responsibilities.

54. Applies to �defense business systems� modernizations with total modernization or development funding exceeding $1 million. Defines Defense Business System as an information system, other than a national security system, operated by, for, or on behalf of DoD, including financial management systems, mixed systems, financial data feeder systems, and IT and information assurance infrastructure. Defense Business Systems support activities such as acquisition, financial management, logistics, strategic planning and budgeting, installations and environment, and human resource management. This chart needs no further explanation. This chart needs no further explanation.

55. Funds cannot be expended until the Defense Business System Management Committee (DBSMC) approves Investment Review Board Certification (IRB) that the system: Is in compliance with the enterprise architecture; or Is necessary to achieve a critical national security capability or address a critical requirement in an area such as safety or security; or Is necessary to prevent a significant adverse impact on a project that is needed to achieve an essential capability The IRB functions as an �OIPT� for business systems. The IRB functions as an �OIPT� for business systems.

56. -Components appoint PCA who reviews and validates certification requests and sends to responsible IRB -IRB reviews request, Chair signs Certification Authority Memorandum, and requests DBSMC approval � before first milestone review. The IRB Chair determines each request: (a) is in compliance with the enterprise architecture; or (b) is necessary to achieve a critical national security capability or address a critical requirement in an area such as safety or security; or (c) is necessary to prevent a significant adverse effect on a project that is needed to achieve an essential capability, taking into consideration the alternative solutions for preventing such adverse effect. -IRB conducts annual review and may request de-certification if system fails to comply with certification conditions or risks are not acceptable -Certification Authorities (CA) --USD(AT&L): business system of which the primary purpose is to support acquisition, logistics, or installations and environment activities --USD(C): business system of which the primary purpose is to support financial management, or strategic planning and budgeting activities --USD(P&R): business system of which the primary purpose is to support human resource management activities --ASD(NII): business system of which the primary purpose is to support information technology infrastructure or information assurance activities --Deputy Secretary of Defense: business system of which the primary purpose is to support any DoD activity not covered above -DBSMC Chair: DEPSECDEF; Vice Chair: USD(AT&L Note: The Deputy Chief Mgmt Officer of DoD is to be the Vice Chair of the DBSMC. This is a new political position that will be nominated and filled by the next administration.-Components appoint PCA who reviews and validates certification requests and sends to responsible IRB -IRB reviews request, Chair signs Certification Authority Memorandum, and requests DBSMC approval � before first milestone review. The IRB Chair determines each request: (a) is in compliance with the enterprise architecture; or (b) is necessary to achieve a critical national security capability or address a critical requirement in an area such as safety or security; or (c) is necessary to prevent a significant adverse effect on a project that is needed to achieve an essential capability, taking into consideration the alternative solutions for preventing such adverse effect. -IRB conducts annual review and may request de-certification if system fails to comply with certification conditions or risks are not acceptable -Certification Authorities (CA) --USD(AT&L): business system of which the primary purpose is to support acquisition, logistics, or installations and environment activities --USD(C): business system of which the primary purpose is to support financial management, or strategic planning and budgeting activities --USD(P&R): business system of which the primary purpose is to support human resource management activities --ASD(NII): business system of which the primary purpose is to support information technology infrastructure or information assurance activities --Deputy Secretary of Defense: business system of which the primary purpose is to support any DoD activity not covered above -DBSMC Chair: DEPSECDEF; Vice Chair: USD(AT&L Note: The Deputy Chief Mgmt Officer of DoD is to be the Vice Chair of the DBSMC. This is a new political position that will be nominated and filled by the next administration.

57. Systems Engineering Plan (SEP) required at each milestone MDA is approval authority for the SEP For programs where USD(AT&L) is MDA, and programs on the DT-only portion of OSD T&E Oversight List, SEPs must be submitted to Director, Systems and Software Engineering 30 days prior to DAB/ITAB review PEOs must have lead systems engineer � oversees SE across PEOs portfolio; reviews SEPs; assesses performance of subordinate systems engineers with PEO and PM Event-driven technical reviews required � with SMEs independent of program, unless waived by MDA Requires configuration management to establish and control product attributes and the technical baseline Encl 12 includes SE policy previously directed by AT&L memos.Encl 12 includes SE policy previously directed by AT&L memos.

58. ESOH risk management required to be integrated with overall SE process; Programmatic ESOH Evaluation (PESHE) required of all programs regardless of ACAT NEPA and EO 12114 (Environmental Effects Abroad of Major Federal Actions) analysis required of PM, approved by CAE Addresses PM support of Mishap Accident Investigations Requires Corrosion Prevention Control Plan for ACAT I programs at MS B and C Requires PMs to employ modular open systems approach to design Data Management Strategy (DMS) required to assess long-term technical data needs of the system � included in Acquisition Strategy Encl 12 includes SE policy previously directed by AT&L memos. Encl 12 includes SE policy previously directed by AT&L memos.