5000
Ser PEO C4I/
From: Program Executive Officer, Command, Control,
Communications, Computers and Intelligence and Space
Subj: INCLUSION OF NEW SHIP CONSTRUCTION (SCN) PARAMETERS IN ACQUISITION PROGRAM BASELINE (APB) AGREEMENTS
Ref: (a) Title 10 U.S.C. 2435
(b) DODI 5000.2 of 12 May 03
(c) SECNAVINST 5000.2B of 6 Dec 96
(d) Interim Defense Acquisition Guidebook of 30 Oct 02
(e) Consolidated Acquisition Reporting System (CARS)
(f) SPAWAR Acquisition Program Structure Guide (V 2.0)
1. The Acquisition Program Baseline (APB) is a management document that records an agreement between the acquisition management chain (i.e., Program Manager (PM), Program Executive Officer (PEO), Component Acquisition Executive (CAE), and Milestone Decision Authority (MDA)), and is endorsed by appropriate representatives from the user and financial communities. It is established to enhance program stability and provide a critical reference point for measuring and reporting the status of program execution. The statutory requirement to baseline programs is contained in Reference (a). The procedures and format for reporting baselines is contained in References (b) through (f).
2. The PEO is responsible for executing Ship Construction Navy (SCN) appropriated dollars when they become available, however, SCN dollars are budgeted under new ship construction and are a portion of the shipbuilding cost reflected in that ship’s APB. If included in the C4I program APB, these dollars can artificially result in a cost breach. Inclusion of SCN parameters in the APB is not specifically addressed in any federal law or regulation.
3. In order to give the PEO visibility and allow for SCN projections to change without effecting program execution, all APBs for programs under the PEO (C4I & Space) will incorporate SCN values into APBs without affecting Program Objective and Threshold values.
(a) For those programs mandated to use the Consolidated Acquisition Reporting System (CARS) software, enter SCN parameters in section 6.7 of the Defense Acquisition Executive Summary (DAES) instruction template. Do not enter any SCN information in section 5.3 of the template. This will not affect the program’s threshold and objective parameters when the APB is generated.
(b) For programs not mandated to use CARS software, ensure APBs are developed in the format of the CARS generated APB. Do not include any SCN appropriated fund values, schedule or performance data in the mandated, existing APB data lines. Add one extra line (after the last line in the cost section) and report any known SCN appropriated funding estimates without any deviation criteria. Include a footnote in the cost section to indicate that the added SCN appropriations line represents the projected appropriated funding for the quantity of anticipated SCN systems currently projected.
(c) Existing APBs should not be updated/changed as a result of this policy, or as a result of a change in projected SCN. Only update SCN values when an APB change/update occurs. As specified in references (d) through (f),an APB change would occur as a result of an APB breach condition and an APB update prior to a major program review.
3. Please direct inquiries on this subject to Lois Harper at (619) 524-7144.
DENNIS M. BAUMAN
Distribution:
PMW 101/159
PMW 150
PMW 151
PMW 156
PMW 157
PMW 161
PMW 165
PMW 166
PMW 173
PMW 176
PMW 179
PMW 189
Share with your friends: |