Defense Business Systems (DBS) Model
DBS Pathway (BCAC)
Capability Need ID Phase
Solution Analysis ATP
Solution Analysis Phase
Functional Requirements ATP
Functional Req and Acq Planning Phase
Acquisition, Testing, and Deployment Phase
Capability Support ATP
Capability Support Phase
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 Sect 4.2.c
At this decision point, the MDA:
Verifies the requirement is fully funded across the FYDP to support all the acquisition activities requested for approval.
Authorizes execution of the acquisition strategy and approves continued execution of the capability implementation plan.
- See Appendix 4B for information about the capability implementation plan.
- Section 2222 Title 10, U.S.C. information / CMO certification (CMO certification can occur during prior phases, but must occur before the Acquisition ATP is approved.)
- Solution approach (fulfills market research, analysis of alternatives and economic analysis)
- Cybersecurity strategy (for mission essential and mission critical IT)
Considerations for Decision Criteria:
- Alternatives leverage market research on existing or emerging COTS and GOTS products and services.
- Potential business systemInformation systems that are operated by, for, or on behalf of the DoD, including: financial, contracting, logistics, planning and budgeting, installations management, human resources management, and training and readiness. solutions reflect traceability to functional requirements and decomposition.
- Potential business system solutions include trade space to minimize customization.
- Potentially expensive or high risk functional requirements are identified with recommended alternative approaches.
- Potential business system solutions address technical and lifecycle support requirements.
- Solution evaluation criteria include: economic analysis; satisfaction of functional requirements and information assets; satisfaction of technical requirements and lifecycle support requirements; and overall risk.
- Solution evaluation criteria include (if needed): delivery schedule; evaluation of trade space for functional requirements; and enterprise impacts.
- Technical management strategy identifies lifecycle methodology for development and delivery of the business system, to include capability support.
- Consistency with DoD Information Enterprise policies and architecture.
- Cybersecurity strategy consistent with DoD policies, standards and architectures, including interoperability requirements.
- Auditability compliance is reviewed and confirmed, if necessary and appropriate
- Certification under Section 2222 Title 10, U.S.C.
Authority to Proceed (ATP) Decisions
Reference Source: Based on DAG CH 6-22.214.171.124 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.