Defense Business Systems (DBS) Model

AAF  >  DBS  >   Solution Analysis ATP

Solution Analysis 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.a.(2)

 

At this decision point

  • The appropriate CMO decision authority, with input from the functional sponsor, validates the capability requirements, approves the work planned for the next phase and
  • Verifies the capability is aligned with the Business Enterprise Architecture (BEA)A blueprint to guide development of integrated DoD business processes including viewpoints of: capabilities, activities, processes, data, info exchanges, business rules, system functions, services, system data exchanges, tech standards, terms, and linkages to laws, regulations and policies. as well as organizational or OSD functional strategy and IT portfolio management goals.

 

Information Requirements

Machine searchable capability requirements must be provided for the Solution Analysis ATP. Capability requirements must include:

  • A description of the business problem or opportunity and its impact on cost and mission performance.
  • Prioritized business capabilities and their attributes, such as testable, quantifiable, and achievable capability performance measures with associated current and future values, including threshold and objective values for future capability performance.
  • Pertinent law, regulations and policies that will either require modification or constrain solutions.

Statutory Requirements

  • None

 

Reference Source: DoDI 5000.75, Table 5

 

Considerations for Decision Criteria include:

  • Concise business problem and desired end state, with cost and performance improvements.
  • Documented laws, regulations and policies.
  • Alignment with and submission to the BEA.
  • Validated capabilities and capability performance measures.
  • Affordable capability with compelling business case for committing organizational resources for work planned up to next decision point.

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.