Sign In
  • Question

    Are there specific documents and process requirements required for Accelerated Advancement Programs (AAPs)?


    Answer

    With regard to documentation required for Accelerated Acquisition Programs (AAPs), I found similar info regarding your below query that was posted to our Ask-A-Professor (AAP) website a few years ago.  The subject matter is heavily tailored to a US Navy program and should be appropriate to your situation.
     
    In addition, the following link https://dap.dau.mil/aphome/das/pages/mdid.aspx, will take you to our Defense Acquisition Portal that contains a listing of all documents required at specific phases of a weapons systems life cycle.  You can use it as a cross walk to ensure that the documents cited in the previous AAP response is still valid. 
     
    In case you also do not already have access to templates for initiating program related documents, the following link could contain some useful examples that could be of assistance with your endeavor https://dap.dau.mil/aphome/das/pages/mdid.aspx.
     
    SECNAV 5000.2 applicability to AAPs:
     
    Applicability and Precedence
     
    a. The provisions of this instruction apply to all DON organizations, to all acquisition category (ACAT) acquisition programs including Naval Intelligence and Naval Cryptologic ACAT programs, abbreviated acquisition programs (AAPs), non-acquisition programs, and Rapid Deployment Capability programs.  The designation ACAT I, when used in this instruction, signifies both ACAT ID and IC programs.  Similarly, the designation ACAT IA, when used in this instruction, signifies both ACAT IAM and IAC programs.
     
    2.1.1.2 Navy Program and Resource Sponsor Responsibilities
     
    Program sponsors are responsible for identifying Navy program requirements. They shall provide the key interface between the JCIDS, the NCDP, the EFDS, the PPBES, and the Defense Acquisition System.  A requirements officer shall be assigned for each platform, system, or initiative for which funding is programmed or planned.  Prior to program initiation, a Capability Development Document (CDD), Capability Production Document (CPD) (for acquisition category (ACAT) programs), or program/resource sponsor memorandum (for abbreviated acquisition programs (AAPs) or non-acquisition programs) shall define the program requirements for each platform, system, or initiative for which funding is programmed or planned.  The resource sponsors are responsible for managing specific appropriation categories.
     
    2.4.6 Abbreviated Acquisition Programs (AAPs)
     
    Small DON acquisitions and modifications may be designated an AAP if they do not require OT&E and they meet dollar threshold and other criteria in Table E2T1.  The OTA must concur in writing that OT&E is not required.
     
    The office of ASN(RD&A) (APA) shall be notified of all AAP designations for entry into the ASN(RD&A) Acquisition Program listing.
     
    4.1 Clinger-Cohen Act (CCA) (40 U.S.C., Subtitle III) Compliance
     
    The CCA applies to all information technology (IT) systems, including National Security Systems (NSS).  Acquisition category (ACAT) IAM and IAC programs require a CCA compliance certification while all other ACAT programs containing Mission-Critical (MC) or Mission-Essential (ME) IT systems, including NSS, require CCA compliance confirmation.  See reference (a), enclosure (4), for minimum requirements to demonstrate compliance with the CCA for ACAT programs containing MC or ME IT systems, including NSS.  The website www.doncio.navy.mil provides additional guidance, the CCA compliance table, and a sample signature page confirming CCA compliance for ACAT ID, IC, II, III, and IV programs, abbreviated acquisition programs (AAPs), and contracts that acquire MC or ME IT systems, including NSS; and a sample signature page for CCA certification for ACAT IAM.
     
    SECNAVINST 5000.2C is available on-line at http://acquisition.navy.mil/policy_and_guidance
     
    Also applicable to AAPs: Defense Business System Management Committee (DBSMC) Certification and Approval, per Title 10 United States Code (U.S.C.) Section 2222, prohibits obligation of any funds for any defense business system modernization that will have a total development/modernization cost of greater than $1 million until the proposed modernization is reviewed by the appropriate OSD Investment Review Board (IRB), certified by the designated OSD approval authority, and approved by the DBSMC.  The law specifically provides that obligation of any funds for a defense business system modernization costing more than the $1 million threshold without DBSMC approval is a violation of the Anti-deficiency Act (31 U.S.C. Section 1341(a)(1)).
     
    The website http://www.doncio.navy.mil/  provides links to the full text of 10 U.S.C. Section 2222, the detailed OSD certification and approval process guidance, and the detailed DON Business Information Technology System Pre-Certification Workflow Guidance, which includes additional clarification and guidance for DON defense business system modernizations.
     
    Additional excerpt from: SECNAVISNT 5000.2C:
     
    2.4.6 Abbreviated Acquisition Programs (AAPs) Small DON acquisitions and modifications may be designated an AAP if they do not require OT&E and they meet dollar threshold and other criteria in Table E2T1 below.  The OTA must concur in writing that OT&E is not required.
     
    2.4.6.1 Weapon System and IT System AAP Procedures
     
    Potential ACAT programs shall not be artificially divided into separate entities for the purpose of having the entities qualify as separate AAPs. PEOs, SYSCOM Commanders, DRPMs, and flag officers or SES designees are assigned program decision authority (PDA) for AAPs and shall designate AAP weapon system and IT system programs unless ASN (RD&A) elects to retain or otherwise delegate this authority.  PDA may be delegated to the PM.  Prior to final approval of an AAP designation, the OTA (COMOPTEVFOR or Director, MCOTEA) shall concur in writing that OT&E is not required.  The CNO (N091) will arbitrate disputes concerning the need for OT&E per the TECG process.  In addition, ASN(RD&A) or designated MDA may elect to treat any program meeting the AAP criteria listed in Table E2T1 as an ACAT program if circumstances warrant, such as joint service involvement or high risk, or if greater visibility is justified.
     
    Designated PEOs, SYSCOM Commanders, and DRPMs shall be responsible for developing AAP policies and procedures for assignment of PDAs, conducting program reviews, and reporting and tracking program status. The PDA shall document all major program decisions.  Only ASN (RD&A) shall assign PDA to organizations other than SYSCOM Commanders, PEOs, and DRPMs.
     
    AAPs shall not be initiated without funding and a written requirement.  As a minimum, requirements or capabilities shall be documented by a sponsor and approved at the appropriate level (e.g., CNO (program sponsor)/CMC (DC,CD)).
     
    The PM for AAPs shall:  conduct a tailored manpower, personnel, and training (MPT) analysis (per Military Standard 464 (MIL-STD-464)); conduct a tailored analysis of the system's ability to operate in the intended electromagnetic environment; establish a system safety program tailored (per MIL-STD-882) to identify environmental, safety, and occupational health hazards; complete Clinger-Cohen Act (CCA) compliance and information assurance strategy for IT systems, including NSS; complete IT registration for mission-critical and mission-essential IT systems, including NSS; and provide any other statutory or program information required by the PDA.  The PM shall comply with the DOD PPBES and configuration management requirements and reporting procedures.
     


    Open full Question Details