Defense Business Systems (DBS) Model

AAF  >  DBS  >  Deployment ATPs

Deployment ATPs

How to use this site

Each page in this pathway presents a wealth of curated knowledge from acquisition policies, guides, templates, training, reports, websites, case studies, and other resources. It also provides a framework for functional experts and practitioners across DoD to contribute to the collective knowledge base. This site aggregates official DoD policies, guides, references, and more.

DoD and Service policy is indicated by a BLUE vertical line.

Directly quoted material is preceeded with a link to the Reference Source.

Reference Source: DoDI 5000.75 Section 4.2.d

Limited Deployment ATP(s)

At this decision point

  • The MDA, in conjunction with the functional sponsor, considers the results of testing, and approves deployment of the release to limited portions of the end user community. Multiple limited deployments may be authorized at the same decision point or delegated to a lower decision authority.

Reference Source: DoDI 5000.75 Table 4

Statutory Requirements

  • Full CCA compliance at first ATP; confirmation of compliance at additional ATPs (Full CCA compliance can occur during prior ATP decision points, but must occur no later than the first Limited Deployment ATP.  Separate documentation should not be needed to confirm CCA compliance.)

Considerations for Decision Criteria 

  • Maturity of developed or configured software through pre-production assessment of functional requirement coverage and defects impacting users.
  • Execution of change management, training and deployment plans.
  • Consistency with DoD Information Enterprise policies and architecture.
  • Test results (including cybersecurity tests) indicating adequate performance and cybersecurity.
  • Program progress against baselined cost, schedule and performance.
  • Ensure CCA compliance
  • Actions necessary for capability support.

 

Full Deployment ATP

At this decision point

  • The MDA, with the support of the functional sponsor and appropriate CMO decision authority, considers the results of limited deployment(s) and operational testing and approves deployment to the entire user community.

 

Reference Source: DoDI 5000.75 Table 4

Statutory Requirements

  • Confirmation of CCA compliance
  • Initial Operational Test and Evaluation Report (for business systems on the DOT&E oversight list)

Considerations for Decision Criteria

  • Measured performance of operational software in support of future business processes and technical and lifecycle requirements.
  • Organizational readiness for continued deployment.
  • Consistency with DoD Information Enterprise policies and architecture.
  • Test results (including cybersecurity tests) indicating adequate performance and cybersecurity.
  • Program progress against baselined cost, schedule and performance.
  • Ensure CCA compliance.
  • Actions necessary for capability support.

Reference Source: DoDI 5000.75 Table 3

 

The MDA is the decision authority for all Deployment ATPs

Authority to Proceed (ATP) Decisions

Reference Source: Based on DAG CH 6-5.3.2.2 content, Jan 2020

An ATP is a “milestone-like” event. It is possible to map some of the BCAC ATPs to traditional acquisition milestones, but the intent was not to make them equivalent. Table 4 of DoDI 5000.75 identifies the statutory requirements that are aligned to ATPs. In addition, the entrance criteria in Table 5 of DoDI 5000.75 —which can be further tailored—help point to what may need to be accomplished for an ATP.

Some key points about ATPs include:

  • ATP meetings or decision reviews should include participation/input from all relevant stakeholders and decisions should be based on timely and relevant capability or program information.
  • Chief Management Officer and MDA roles both exercise decision authority at:
    • Functional Requirements ATP, during which it is determined if there is a valid requirement and/or if a business system is needed
    • Acquisition ATP, during which it is determined whether or not to acquire a particular system and where the CMO initially certifies funds
  • The leading community recommendation is to capture both investment and acquisition decisions in a single memo with two signatures; discussion will continue on the Business Systems Community of Practice (DoD CAC Required) regarding ATP procedures and documentation.
  • Although separate reviews for Clinger-Cohen Act Compliance are no longer required under BCAC, some organizations may choose to include a CIO signature on ATP documentation beginning with the Acquisition ATP.