Clima

acquisition and requirements process for DBS, and assigns responsibilities and provides procedures for the successful development, testing, fielding, and sustainment of DBSs. This model is a guideline and is not intended to preclude tailoring, consistent with statute and sound business practice.

7.17.1. DBS Requirements. Activities performed and documentation required in the Business Capability Definition (BCD) Phase of the BCL guidance shall be used in lieu of JCIDS. The Problem Statement replaces the JCIDS documentation. The BCD phase is led by the functional sponsor. Refer to AFI 10-601 for DBS requirements process and documentation.

7.17.1.1. The Functional Sponsor shall present the approved requirements document with the AoA Study Guidance and Plan to the MDA for MDD. Results of the MDD are documented in an ADM by the MDA.

7.17.2. DBS Acquisition. Major Automated Information Systems (MAIS) Defense Business System programs will follow BCL guidance. If a DBS below the MAIS threshold is

designated as special interest by either the USD(AT&L) or the Deputy Chief Management Officer (DCMO), it shall be subject to OSD oversight. Programs below MAIS thresholds shall follow BCL guidance and guidance in this document. The SAE shall designate the MDA for DBS that do not meet the MAIS threshold.

7.17.2.1. The MDA shall be responsible for making DBS life cycle management decisions including all acquisition and sustainment execution decisions. The MDA shall not approve program changes unless the program increment is fully funded and schedule impacts mitigated. The MDA is responsible for approving the Business Case. The Business Case replaces the Acquisition Strategy in the BCL policy. The MDA shall tailor the regulatory information requirements and life cycle processes and procedures in the BCL model to achieve cost, schedule, and performance goals, as appropriate.

7.17.2.1.1. All DBS programs under MAIS thresholds and over $10 Million in total modernization cost shall be managed under the appropriate Air Force PEO unless otherwise directed. The PEO shall act as MDA authority for DBS over $10 Million and below MAIS thresholds. Functional Sponsor shall contact the appropriate PEO for assistance. IRB/SWG shall advise the MDA as appropriate.

7.17.2.1.2. All DBS programs under $10 Million in total modernization cost may be managed by a HAF and HAF DRU CIOs or IT Functional Portfolio Managers acting as the MDA authority. HAF and HAF DRU CIOs or IT Functional Portfolio Managers shall inform SAF/AQ of the programs for which they are assuming MDA responsibility. Programs under $10 Million in total modernization are required to follow the BCL model and follow all applicable laws, regulations, and policy. Programs using investment funding are required to be on the AML and report in SMART.

7.17.2.1.2.1. HAF and HAF DRU CIOs or IT Functional Portfolio Managers acting as the MDA and PM authority over DBS are highly encouraged to meet the acquisition workforce requirements in this document. MDA and PM credentials are required to be listed in SMART.

7.17.2.1.2.2. DBS programs managed by HAF and HAF DRU CIOs or IT Functional Portfolio Managers are subject to the reporting and review guidelines in this document. The SAE shall review and adjust the program based upon program execution.

7.17.2.1.2.3. Directions for HAF and HAF DRU CIOs or IT Functional Portfolio Managers informing SAF/AQ of MDA and PM responsibility is included in AFPAM 63-128.

7.17.2.2. MAIS programs are required to conduct an Enterprise Risk Assessment Methodology (ERAM) per BCL guidance. MAIS programs below the threshold are not required to conduct an ERAM assessment, but are required to conduct a Component Level Equivalent as appropriate. MAIS programs below the threshold programs shall follow the risk management guidance in this document. The MDA will determine the extent of the risk management assessment based upon program conditions.

7.17.3. DoD Defense Business Council (DBC) Certification. DBC certification is required for any defense business system investment costing in excess of $1 million in total DoD

funds over the FYDP, regardless of type of funding or whether any development or modernization is planned. Obligating DoD funds for a defense business system modernization over $1M that has not been approved by the DBC is a violation of 31 U.S.C. § 1341(a)(l) (the Anti-Deficiency Act). Any modernization to a National Security System does not require certification. For additional information refer to DTM 08-020, Investment Review Board (IRB) Roles and Responsibilities, DoD IT Defense Business Systems Investment Review Process Guidance, or AFI 33-141, Air Force Information Technology Portfolio Management and IT Investment Review.

7.17.3.1. To obtain DBC certification systems must be:

7.17.3.1.1. In compliance with the DoD Business Enterprise Architecture (BEA) and BPR efforts must have been sufficiently undertaken to ensure that;

7.17.3.1.1.1. The business process supported by the Defense business system is (or will be) as streamlined and efficient as practicable; and

7.17.3.1.1.2. The need to tailor commercial-off-the-shelf systems to meet unique requirements or incorporate unique interfaces has been eliminated or reduced to the maximum extent practicable;

7.17.3.1.2. Necessary to achieve a critical national security capability or address a critical requirement in an area such as safety or security; or

7.17.3.1.3. Necessary to prevent a significant adverse effect on a project that is needed to achieve an essential capability, taking into consideration the alternative solutions for preventing that adverse effect.

7.17.3.2. The DBC chair is the final approval authority for all defense business system certification requests. The Chair shall document decisions in an Investment Decision Memorandum to affected PMs through the DoD Component Pre-Certification Authorities. DBC Chair approval shall occur before the first milestone review of an acquisition program. The PM shall include a copy of the DBC approved Investment Decision Memorandum with the documentation provided to the MDA. A DBC certification approval does not constitute authority to execute an acquisition program 7.17.4. DBS Acquisition Reporting. All DBS efforts using investment funds are subject to acquisition reporting that is detailed in Chapter 10 of this AFI.

7.17.4.1. DBS efforts using investment funds, regardless of amount, will be listed on the AML.

7.17.4.2. DBS efforts on the AML shall initiate and maintain program data within the SMART acquisition management system. DBS efforts that are managed within AFMC and SMC are also required to use Comprehensive Cost and Requirement (CCaR). Additionally, DBS efforts with more than $30M in RDT&E (3600) or $50M in procurement over the life of the effort are required to submit a Monthly Acquisition Report (MAR) via the SMART system.

7.17.5. DBS Sustainment Reporting. DBS efforts that have reached Full Deployment Decision (or equivalent milestone) are not required to submit a MAR. If DBS sustainment efforts use investment funding that exceeds the MAR reporting thresholds then the efforts will adhere to the reporting requirements in Chapter 10 of this AFI.

Chapter 8

ACQUISITION OF SERVICES

8.1. Purpose. This chapter defines the framework and expectations for acquiring and ensuring delivery of promised performance of contracted services. As used herein, “Services Designated Officials” has the same meaning as “Decision Authority” in DoDI 5000.02 Enclosure 9, dated December 8, 2008, referred to hereafter as USD (AT&L) Acquisition of Services Policy. Related references include Title 10 United States Code §2330, §2330a, and §2463; FAR Part 37,

Service Contracting; DFARS Part 237, Service Contracting; DoDI 1100.22, Policy and Procedures for Determining Workforce Mix; AFFARS Part 5337, Service Contracting; AFI 38- 203, Commercial Activities Program; and SECAF memorandum of 9 March 2006, Contractor Support Approval Policy Memo 06A-002. AFI 63-138 (when published) must be used in conjunction with this document for implementation guidance on Air Force Acquisition of Services.

8.2. Acquisition of Services Objectives. Acquisitions of services shall support and enhance the