Defense Business Systems (DBS) Model

AAF  >  DBS  >  Functional Requirements ATP

Functional Requirements 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.b.(2)

 

At this decision point:

  • The appropriate CMO decision authority validates that sufficient business process reengineering has been conducted to determine whether a business system is required.
  • The MDA approves execution of the activities outlined in the capability implementation plan defined in Appendix 4B.

Information Requirements

  • Business Processes. High-level business processes must be structured to focus on the work to be conducted and on the information used, not supporting IT.
  • Capability Implementation Plan. See Appendix 4B for information on the capability implementation plan. 

Statutory Requirements

  • None

 

Reference Source: DoDI 5000.75, Table 5

 

Considerations for Decision Criteria include:

  • High-level business processes include performance measures and supporting activities and tasks with inputs and outputs.
  • Business processes focus on work and not supporting systems or IT.
  • Clear understanding of the process and functional changes needed to achieve future business processes.
  • Key processes identified for improvement documented with changes in process models.
  • Business processes reflect knowledge of industry state of the art.
  • Business process actions identified, prioritized and included in the capability implementation plan.
  • ROM cost estimate for all business changes to achieve future business processes.
  • Affordability targets for business system with compelling business case for committing organizational resources for work planned up to next decision point.
  • Acquisition strategy outlines planned decision points and decision authorities.
  • Consistency with DoD Information Enterprise policies and architecture
  • High-level understanding of capability support requirements.
  • Initial cybersecurity strategy consistent with DoD policies, standards, and architectures.

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.