Defense Business Systems (DBS) Model

AAF  >  DBS  >  Capability Support ATP

Capability Support ATP

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.(4)

 

At this decision point

  • The functional sponsor accepts full deployment of the system and approves transition to capability support.

 

Reference Source: DoDI 5000.75 Table 4

Statutory Requirements

  • None

 

Reference Source: DoDI 5000.75 Table 5

Considerations for Decision Criteria:

  • Measured performance of implemented future business processes.
  • Continued cybersecurity readiness.
  • Organizational readiness for capability support.

 

Reference Source: DoDI 5000.75 Table 3

The Functional Sponsor is the Decision Authority

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.