The PBO allows the Program Manager (PM) to track program objectives using a formal baseline. This follow-up will draw the PM`s attention to potential problems and implement corrective measures to maintain a program within its objectives. For each increment and block of an MDAP program or a MAJOR ACQUISITION SYSTEM (MAIS) an APB is required. Deviations from the approved BPA should be recorded in a program deviation report (PDR). The program sponsor and MP ensure that content includes KPP/KSAs sustainability settings, measurement metrics, and all directions managed by the program that influence the planning and execution of lifecycle support strategies. The APBs for Acquisition Category (ACAT) I and IA programs are created in the Defense Acquisition Management Information Retrieval (DAMIR) system. The Baseline Acquisition Program (APB) is developed by the Manager Program (PM) prior to the launch of a program for all Acquisition Category (ACAT) programs and represents the current state of a program. The plan sets out the threshold and objective values for a program`s cost, schedule and performance requirements. Performance requirements are listed as key performance attributes (KPP) and key system attributes (KSA) and are linked to program objectives. These KPp and KSAs are developed by program sponsors (users) and are listed in the Capabilities Design Document (CDD) or Capabilities Production Document (CPD) and are also documented in the basic technical framework. The Milestone Decision Authority (MDA) is the responsible authority for receiving the BPA. For each increment of an MDAP or BUT program and each sub-program of an MDAP, a separate APB is required. Increments can be used to plan simultaneous or sequential efforts to provide capacity faster and in tune with the technological maturity of each increment.
(If an MDAP requires the delivery of two or more categories of final items, which differ considerably in terms of form and function, sub-programs may be implemented.)