ACAT II programs are defined as acquisition programs that do not meet the criteria of an ACAT I program, but the criteria of a major system. Contract report that provides Senior Managers with the following: Stage B is typically the formal launch of an acquisition program with MDA approval of the Acquisition Program Baseline (PDB). The PDB is the agreement between the MDA and the Program Manager and its acquisition chain, which is used for monitoring and reporting during the life of the program or program increment. The PDB will include affordability caps for production and maintenance costs. Affordability limits are defined as fixed cost requirements that correspond to PPPs. Cost, schedule and performance reference levels in SPB should be at a higher level of high program level to allow for the flexibility to move applications within and between versions. The Milestone B decision approves the entry of the programme into the EMD phase and the award of contracts for EMD activities. Based on the precedents of an agile approach to document acquisition set out in previous milestone decisions, there are expected to be few additional requirements for this review of decisions. Agile-minded program managers should continually socialize program changes with key stakeholders during the transition period between decision points.
More frequent ongoing reviews and ongoing coordination with stakeholders create the conditions for effective review of decisions. The MDA should focus on assessing the known risks and mitigation measures needed to carry out the iterative design, development, integration, testing, and deployment activities that are unique to agile EMD activities. Since the deployment of incremental functionality begins at this point, the risk mitigation solution is also prioritized gradually. That is, while all known risks must be adequately mitigated for the next iteration, the allocation of resources to mitigate the risks associated with subsequent iterations of functions may be less prioritized or deferred until the results of previous development activities are available. These include technology, engineering, integration, manufacturing, sustainability and cost risks. Similarly, capacity requirements continue to be refined with the highest resolution for short-term iterations. A separate PDB is required for each increment of an MDAP or MAIS program and each sub-program of an MDAP. Increments can be used to plan simultaneous or sequential efforts to deliver capabilities faster and based on the technology readiness of each increment. (If an MDAP requires the delivery of two or more categories of end products that differ significantly in form and function, subroutines can be configured.) defines the part of the program that is created by a specific contractor and forms the basis for collecting data on costs and deadlines for the contract. Like the custom list for Stage A, the PMO, in collaboration with the MDA, should significantly adapt the documents required to comply with legal and regulatory requirements.
A proposed custom list of the information required for Milestone B will be provided in a future AiDA update. For a complete list of required information, see Table 2 of DoDI 5000.02. For the MDAP at Milestone B, the MDA must confirm in writing to Congress that the program is affordable and that the Director of Costing and Program Evaluation (BCAH) agrees to reasonable estimates of the costs and timelines for the execution of the program`s development and production plans. The PDB allows the Program Manager (PM) to track program objectives against a formal baseline. This follow-up notifies the PM of any potential problems that may arise and takes corrective action to keep a program within its objectives. An APB is required for each increment and block for a Major Defense Acquisition Program (MDAP) or Major Acquisition Information System (MAIS). .