Defense Acquisition Portal - MDID

The MDID tool reflects content contained within the 5000.02T (Table 3, 6 and 7 only). Future updates will be made IAW with identified transition guidance.

Purpose of the Milestone Document Identification (MDID) tool

The Milestone Document Identification (MDID) assists acquisition personnel filter through statutory and regulatory document requirements as identified in Tables 2, Milestone and Phase Information Requirements; Table 5, Recurring Programs Reports; Table 6, Exceptions, Waivers, and Alternative Reporting Requirements; and Table 10, Information Requirements Unique to the Urgent Needs Rapid Acquisition Process of the DoDI 5000.02.

Table 2: Milestone and Phase Information Requirements

  1. Acquisition Program Information Requirements at Milestones and Other Decision Points
    1. Table 2 lists the Statutory and Regulatory requirements at each of the milestones and other decision points during the acquisition process. In consultation with the appropriate stakeholders, program managers may propose for MDA approval, tailoring of Regulatory program information. MDAs will document all information tailoring decisions.
    2. Each row identifies an information requirement and the source of the requirement. (Sources may refer to United States Code (U.S.C.), Public Law (P.L.), an Executive Order (E.O.), DoD Instructions (DoDIs), Directives (DoDDs), or other types of documentation. When available, the source will include paragraph (Para.), section (Sec.), or enclosure (Enc.) numbers and the reference (Ref.) identifier from the list of references in this instruction. Statutory items and sources appear in all caps; Regulatory items and sources appear in normal text. Requirements are in alphabetical order.
      • A dot (dot) in a cell indicates the specific applicability of the requirement to program type and life-cycle event, and represents the initial submission of information. Moving right across a row, a checkmark (checkmark) indicates the requirement for updated information, and another dot indicates submission of new information. For the purposes of the MDID tool the dot and checkmark have been replaced by a square to represent an action is required.
      • Notes accompany most rows to explain the requirement, limit or extend the requirement's applicability to program type and/or life-cycle event(s), or explain any special conditions.
    3. Labels for the "Life-Cycle Event" columns represent the following events:
      • "MDD" - Materiel Development Decision
      • "MS A" - Milestone A Decision Review
      • "CDD Val" - Capability Development Document Validation
      • "Dev RFP Rel" - The Development Request for Proposals (RFP) Release Decision Point conducted before Milestone B to authorize release of the RFP for the next phase
      • "MS B" - Milestone B Decision Review
      • "MS C" - Milestone C Decision Review
      • "FRP/FD Dec" - The Full Rate Production (FRP) Decision or the Full Deployment (FD) Decision
      • "Other" - An event other than the events listed above; the event will be identified in the notes associated with the row.
    4. Documentation for the identified events will be submitted at least 45 calendar days before the planned review.
    5. Information requirements that are finalized and approved by the responsible authority in support of the Development RFP Release Decision Point do not have to be re-submitted prior to Milestone B unless substantive changes have occurred.
    6. Final milestone documents for programs reviewed at the OSD level will be submitted to the Acquisition Information Repository within 5 business days of document approval.
    7. In Table 2, when applied to requirements associated the Develo9pmental RFP Release Decision Point, the modifier "draft" will mean a DoD Component- Program Manager-, Program Executive Officer-,CAE-approved draft subject to change based on results of the source selection process and pre-Milestone B Component and OSDE staff coordination.
    8. The Program Manager may submit a document prepared to satisfy the information requirements of multiple programs (instead of a program-specific document). Such substitution will require written permission from the approving authority.
    9. When there is a logical relationship between required documents, e.g., the Acquisition Strategy and the Life-Cycle Sustainment Plan, and consequent coordination can be streamlined; the MDA may approve combining requirements

Table 5: Recurring Programs Reports and Table 6: Exceptions, Waivers, and Alternative Reporting Requirements

  1. Reporting Requirements
    1. Tables 5 through 8 of this enclosure summarize Statutory and Regulatory reporting requirements, and specify when the reports are due.
      • Table 5 presents recurring reporting requirements.
      • Table 6 lists the reporting requirements established for exceptions, waivers, and alternative reporting.
      • Table 7 summarizes Cost and Software Data Reporting System requirements. This table is not included in the MDID
      • Table 8 summarizes Earned Value Management (EVM) reporting requirements. This table is not included in the MDID
    2. In Table 5 and Table 6 of this enclosure, each row identifies an information requirement and the source of the requirement. Statutory items and sources appear in all caps; Regulatory items and sources appear in normal text. A dot (dot) in a cell indicates the applicability of the requirement to the program type for that column. For the purposes of the MDID tool, the dot was changed to a square to represent an action is required.

Table 10: Information Requirements Unique to the Urgent Needs Rapid Acquisition Process

  1. Additional Information Requirements. Table 10 provides Information Requirements that replace or are in addition to selected statutory or regulatory requirements in Table 2 and 6 in Enclosure 1 that are applicable to ACAT II and ACAT III programs. For rapid acquisition, the documentation procedures described in DoDI 5000.02, Enclosure 13, paragraph 4a(3)(d) will be applied to all information requirements unless otherwise prescribed in statute.

Text taken from various sections of the DoDI 5000.02.