BY ORDER OF THE AIR FORCE INSTRUCTION 16-501
SECRETARY OF THE AIR FORCE 14 JUNE 1994
Operations Support
CONTROL AND DOCUMENTATION OF AIR FORCE PROGRAMS
This instruction implements AFPD 51-1, The Judge Advocate Generals Department; Department of Defense DoD) Directive 5160.64, Federal Legal Information Through Electronics FLITE) and the Defense Emergency Authorities Retrieval and Analysis System DEARAS), July 9, 1991, with Change 1. This instruction assigns legal automation responsibilities to the Legal Information Services Directorate of the Air Force Legal Services Agency AFLSA/JAS) and Air Force legal offices. It provides procedural guidance for complying with operational and security requirements concerning procurement, maintenance, operation, transfer, and disposal of computer systems for use in Air Force legal offices. It also provides guidance and procedures concerning the operation of Air Force law libraries. It describes the Worldwide Automated Law Library System WALLS) and explains the concept of the core law library system. The term major command MAJCOM), as used in this instruction, includes field operating agencies. Attachment 1 lists the references, abbreviations, acronyms, and terms used in this instruction.SUMMARY OF CHANGES
____________________________________________________________________________________________________
LEGAL AUTOMATION
This instruction implements AFPD 16-5, Planning, Programming, and Budgeting System (PPBS). It establishes procedures for documenting and controlling Air Force Planning, Programming, and Budgeting System (PPBS) activities and states programming responsibilities of Headquarters US Air Force (HQ USAF) and Programming Agencies (i.e., major commands [MAJCOM], field operating agencies [FOA], direct reporting units [DRU], US Air Force Reserve [AFRES], and the Air National Guard [ANG]). Use this instruction along with Department of Defense [DoD] guidance, DoD Instruction 7045.7, Implementation of the Planning, Programming and Budgeting System (PPBS), May 23, 1984, with Change 1, Air Force Supplement 1 to DoD Instruction 5000.2, Acquisition Management Policies and Procedures, February 23, 1991, with Change 1; Air Force 10-, 16-, and 172-series publications, and PPBS Primer to ensure a full understanding of the PPBS. A glossary of abbreviations, acronyms, and terms is at attachment 1.
SUMMARY OF CHANGES
This is the initial publication of this instruction. It incorporates the new Air Force resource allocations process, and creates Resource Allocation Teams. It also updates, clarifies, and streamlines previous guidance on the Air Force PPBS.
1. DoD PPBS--Program Controls:
1.1. Basic Controls. Air Force flexibility, within PPBS, is primarily limited to changes within and among program elements (PE). Other controls such as Commander in Chief (CINC) priorities, country manpower authorizations, mutual security commitments, Troop Strength ceilings, congressional limitations for the current year, and the Office of the
Secretary of Defense (OSD) considerations for the budget years further limit flexibility. The Secretary of Defense (SECDEF) will approve major force structure changes and the associated procurement or research and development increases within the total Air Force manpower or dollar levels. The methods to get approval for OSD program changes,
when required, vary with the item; however, the principal method of changing the overall program is the Program Objective Memorandum (POM). The POM represents balanced, total Air Force program recommendations within the OSD specified fiscal guidance limitations and directions contained within Defense Planning Guidance (DPG).
1.2. Air Force Controls. HQ USAF limits the authority of Programming Agency commanders to deviate from the Air Force programs--without advance approval of HQ USAF. Programming agencies must promptly request program adjustments if they expect not to meet program objectives with their available resources or if their allocated resources exceed their needs. Forward requests either through the PPBS or through a Program Change Request (PCR) (see paragraph 6.1 and DoD Instruction 7045.7 [Enclosure 6]). HQ USAF must notify implementing commanders of program changes resulting from OSD decisions, resource limitations, and other program adjustments.
2. Air Force PPBS Process. The goal of this process is to achieve the defense objectives established by the President and the SECDEF in the DPG.
2.1. Resource Allocation (RA) Teams. The Air Force reviews and screens resource and programming issues using seven Resource Allocation Teams, chaired from the following Deputy Chiefs of Staff (DCS) (or Secretariat equivalent):
- TEAM CHAIRMAN/CO-CHAIRMAN
- Power Projection HQ USAF/XO
- Global Mobility HQ USAF/XO
- Space, Nuclear Deterrence, & C4I HQ USAF/XO
- Materiel Support SAF/AQ & HQ USAF/LG*
- Personnel & Support HQ USAF/DP
- Special Access Required (SAR) Programs SAF/AQ
- National Foreign Intelligence Program (NFIP) HQ USAF/IN
- Team chaired by SAF/AQ for acquisition programs and HQ USAF/LG for logistics programs.
2.1.1. The DCSs appoint the RA team chiefs and, in turn, the chiefs solicit membership to their teams from other DCSs. They must obtain their DCS's (or the Secretariat equivalent functional manager's) approval before submitting program options to the Directorate of Programs and Evaluation (HQ USAF/PE), which integrates them into the overall Air Force program briefing to the Air Force Council (AFC), the Secretary of the Air Force (SECAF), and the Chief of Staff (CSAF).
2.2. Program Elements. PEs are primary data elements in the Future Years Defense Program (FYDP). They are organized into 11 major force programs (MFP), 6 combat force oriented programs, and 5 support programs. SECAF assigns PEs to the RA teams which most closely reflect their force structure or support function. Since some PEs affect more than one RA team and cut across functional lines, each assigned RA team must coordinate with each of the other teams on actions which may affect their PEs. The functional DCS, or the Secretariat equivalent functional manager, will coordinate assignment changes to existing PEs for approval by the SECAF.
2.3. Process Timing--Calendar Year Schedule. (Refer to Air Force POM Preparation Instruction (PPI) and DoD Instruction 7045.7 for calendar of events.)
3. Responsibilities:
3.1. HQ USAF:
- Implements OSD program and budget directives and guidance.
- Issues appropriate amendments to program guidance and directives and provides to Programming Agencies.
- Implements the OSD approved program reflected in the FYDP.
- Reviews requests for program changes initiated within HQ USAF or submitted by the Programming Agencies. Forwards the request to OSD as required by DoD Instruction 7045.7.
- Makes necessary changes within the range of HQ USAF approval authority, funding, and manpower.
- Develops and submits the Air Force input to OSD for the DPG, the Air Force POM, the Air Force Budget Estimate Submission (BES), and the Air Force input to the President's Budget (PB); and finally, distributes program documents to the Programming Agencies.
- SAF/AQ will inform SECAF on programs in the POM and BES that reflect a significant change to any program subject to review by the Defense Acquisition Board (DAB) since SECAF is required by DoD Directive 5134.1, Under Secretary of Defense for Acquisition, September 30, 1992, to consult with the Under Secretary of Defense for Acquisition (USD[A]) on these programs before submitting them to OSD.
3.2. Programming Agencies:
- Comply with program guidance and direction issued by HQ USAF.
- Provide program guidance and direction to subordinate commanders.
- Submit POM data and briefings according to HQ USAF schedule and direction.
- Submit, as necessary, a cover letter to address specific Air Force-wide requirements, Joint Chiefs of Staff (JCS) commitments, known fiscal constraints, mission area differences, or enhancements which the sponsor desires to emphasize in the POM.
- Coordinate with Component Commanders to translate CINCs' requirements into programmatic terms, to include program elements and required funding.
- Integrate CINCs' requirements into POM submissions to HQ USAF.
- Provide sections in POM submissions highlighting the CINCs' requirements and priorities in POM submissions. Include funding for each CINC requirement by program element. Include rationale for any changes from funding needed to support CINCs' requirements.
- Implement the approved Air Force program as directed.
3.3. Component Commanders:
3.3.1. The following MAJCOMs, as Component Commanders, are responsible for reporting programming requirements for:
- Air Combat Command (ACC)--US Central Command, US Atlantic Command, North American Aerospace Command, and US Southern Command.
- Air Force Space Command--US Space Command.
- United States Air Forces in Europe--European Command.
- Pacific Air Forces--US Pacific Command.
- Air Mobility Command (AMC)--US Transportation Command.
- Air Force Special Operations Command (AFSOC)--the non-MFP-11 portion of the US Special Operations Command.
3.3.2. Component Commanders' Primary Responsi-bilities:
- Highlight CINC requirements and priorities in POM submissions to HQ USAF.
- Coordinate with MAJCOMs to translate requirements into programmatic terms, to include program elements and required funding.
- Coordinate with other Air Force MAJCOMs concerning requirements outside their programming responsibility but within their areas of responsibility as components of Unified Commands.
- Track CINCs' concerns throughout the POM process.
- Provide direct feedback to CINCs on POM funding status of requirements.
- Involve CINCs in identifying tradeoffs between programs as required.
- Relay changing CINC concerns to the Air Staff and other affected Air Force MAJCOMs.
4. Documentation:
4.1. USAF Force and Financial Plan (F&FP). The USAF F&FP and Program Documents reflect the Air Force Program. These documents are consistent with the DoD FYDP (see DoD Instruction 7045.7). The F&FP provides considerable expansion of details over the FYDP for Air Force programs. When submitting a request to OSD to modify the Air Force Program, ensure the request relates to the F&FP and its resources data. Changes in the F&FP are implemented only with specific direction from HQ USAF.
4.2. Air Force Program Documents. The Air Force disseminates its Program in various documents called Program Documents. Responsible HQ USAF organizations will publish the principal program documents twice during a cycle:
- After Air Force POM submission to OSD.
- After PB resolution.
As a rule, publish supplementary documents along with the program documents. (Responsible HQ USAF organization may publish these documents after a significant amended budget submission or anytime OSD directs an additional update.)
4.2.1. The principal program documents and the supplementary program documents that show particular resource commodity of the overall program are listed at attachment 3.
4.2.2. The OPR will categorize these program documents, where appropriate, by the PE, consistent with the USAF F&FP.
4.2.3. Implement program documents only with specific and separate authority from HQ USAF (except for flying hours in the PA document).
5. Distributing DoD and USAF Program Documents:
5.1. DoD Distribution Controls. Do not disclose PPBS documents and supporting data bases outside the DoD or other governmental agencies not directly involved in the defense planning and resource allocation process (e.g., OMB). The OSD office responsible for the PPBS phase to which the document or data base pertains (e.g., the Under Secretary of Defense [Policy] for the Planning phase, the Director [Program Analysis and Evaluation] for Programming, and the DoD Comptroller for Budgeting [see DoD Instruction 7045.7]) will consider requests for exceptions on a case-by-case basis. The responsible OSD office coordinates requests with the General Counsel.
5.2. Air Force Distribution Controls. The Air Force occasionally, but not routinely, distributes to OSD and headquarters elements of the Departments of the Army and the Navy. Sub-elements of those departments that require information on Air Force programs should get it from their respective departmental headquarters. The Air Force distributes program documents internally on a strict "need-to-know" basis (see DoD 5200.1-R, Information Security Program Regulation, June 1986, and AFPD 31-4, Information Security [formerly AFR 205-1]).
5.3. Requests for Distribution. HQ USAF usually distributes program documents to directorates at the Programming Agencies. With specific, fully justified requests from the Programming Agencies, HQ USAF may distribute documents directly to the subordinate commands immediately below MAJCOM level.
5.3.1. HQ USAF/PE controls the distribution for the principal program documents; the OPRs control supplementary documents (see attachment 3).
5.3.2. Send all requests for program documents through the Programming Agencies to the HQ USAF OPR. Do not use normal publications channels. Requests for new or increased distribution must:
- Be signed at the command directorate level.
- Identify the using agency.
- Justify the reason for the request.
- Identify the total number now being received in the command headquarters.
- Identify the Programming Agencies focal point responsible for program document control.
5.3.3. In determining total requirements, Programming Agencies should:
- Use focal points or classified libraries that can make copies available to several offices in order to minimize the number of copies needed.
- Using DoD 5200.1-R and AFI 31-401, Information Security Program Management (formerly AFR 205-1), try to reproduce parts of documents when an individual office or subordinate command does not need the whole document.
5.4. Limitations for Educational Purposes. Limit access to program documents for educational purposes to:
- General Student Use. The Air Force does not make program documents available for general student use until at least 2 years have elapsed from the date on the cover of the documents, and then only if the instructional subject matter warrants their use.
- Instructor Use. Air University may make current documents (i.e., those less than 1-year old) available to their instructors for research purposes and for curriculum planning, provided the curriculum objective warrants such use. Air University authorities may also make current documents available on a "need-to-know" basis to a very limited number of students to work on assigned special studies or research projects.
- Library Use. Libraries must ensure their facilities and controls meet security classification standards. Personnel having access to documents must have proper security clearances.
5.5. Limitations on Distribution to Contractors. Limit access to industrial firms under contract to the Air Force on a strict "need-to-know" basis as provided in DoD 5200.1-R/AFI 31-401 and DoD 5220.22-R, Industrial Security Regulation, December 1985 and AFI 31-601, Industrial Security Program Management (formerly AFR 205-4). Do not release entire documents. The commander responsible for procuring material, supplies, or services from a contractor or bidder may release or disclose only the classified information required to perform the specific contract or to prepare a specific bid or quotation.
6. Program Change Request (PCR). See DoD Instruction 7045.7 for general guidance on requesting a change to the FYDP program structure.
6.1. General Guidelines for Air Force PCRs:
- Use PCR actions to make small corrections to programs, not major program restructures.
- Final approval authority is SECAF and CSAF.
- For creation of or changes to program elements, send requests, by letter or message, to HQ USAF/PE using the guidelines of DoD Instruction 7045.7 (Enclosure 6).
- If operational or fiscal requirements necessitate changes to the Air Force program outside the normal PPBS cycle, commanders should submit PCRs by message (after coordinating within Programming Agencies) to the appropriate PCR Programming Agency, and provide informational copies to the other Programming Agencies and HQ USAF/PE.
- Other Programming Agencies wishing to comment on a proposed PCR will provide comments directly to the submitting command and to their counterparts on the Air Staff, National Guard Bureau, or Air Force Reserve.
- Commands submitting PCRs will coordinate them through Air Force Materiel Command (AFMC) prior to sending them to HQ USAF. AFMC provides impacts, then the Air Staff optimizes the beddown plan.
- All commands possessing similar assets must coordinate on PCRs before sending them to HQ USAF.
- Each Programming Agency will establish procedures for numbering and tracking their PCRs.
6.1.1. The PCR programming agencies are generally aligned with the RA Teams. The PCR processing programming agencies and their RA Teams are:
- HQ USAF/XOFP--Power Projection; Global Mobility; and Space, Nuclear Deterrence, and C4I Teams.
- SAF/AQXR or HQ USAF/LGS--Materiel Support Team.
- HQ USAF/DPPR--Personnel and Support Team.
- HQ USAF/INR--NFIP Team.
- HQ USAF/PEF--SAR Team.
6.1.2. Submit PCRs only when you must change the Air Force Program during the execution and budget years. Do not submit PCRs for changes to the Air Force Program which begin beyond the execution or budget years. Submit those requests as part of Program Agency initiatives or disconnects during the next programming exercise.
6.1.3. Include in each PCR a detailed explanation of the costs involved, for all appropriations. For Procurement Accounts, in addition to the PE, include the Budget Program (BP). Also include outyear costs and BP for PCR actions affecting out years.
6.1.4. Identify in each PCR the source of the cost estimates in each appropriation. Specify offsets within each appropriation for the execution and budget year (for each fiscal year in which the requested change impacts the Air Force Program). Each offset will contain funding information to the program element and cost element detail. For Procurement Accounts, in addition to the PE, include the BP. Each PCR should be a stand-alone action. HQ USAF will normally reject using offsets from prior or subsequent PCRs.
6.1.5. To identify PCRs, include the initiating organization name (Air Combat Command, National Guard Bureau, etc.), execution year designation, and a sequential two digit number (e.g., AMC 94-01 is the first PCR AMC submits in Fiscal Year 94). HQ USAF-generated PCRs will use the three-letter office symbol of the responsible Directorate followed by execution year designation and sequential two digit number.
6.1.6. Each PCR will state that the requester has initiated the Environmental Impact Analysis Process (EIAP), as directed by AFI 32-7061, Environmental Impact Analysis Process (formerly AFR 19-2) and identify which Program Agencies have coordinated on the PCR.
6.2. PCR Request Message. Programming Agencies will submit PCRs in message format (see attachment 2). As a minimum, the message will contain the following elements:
- Addressed to the appropriate HQ USAF PCR Programming Agency. Information copies to all interested MAJCOMs, the other PCR Programming Agencies, HQ USAF/PE and SAF/FMBP, Air Staff Directorates, the National Guard Bureau, and the Air Force Reserve. HQ AFMC/LGI must be an addressee on all messages that affect force structure and flying hours.
- The Programming Agency PCR number and title.
- Brief summary of proposed changes.
- Force structure or manpower displays of current program and a display of proposed changes by quarter of each fiscal year to include out years.
- Cost summary of the proposed program to include program element, appropriation, cost element detail, and BP (for Procurement Accounts) including out years. As a minimum, identify Base Operating Support (BOS) Operations and Maintenance (O&M), Environmental Compliance, Real Property Maintenance (RPM), Communications and Military Construction (MILCON) costs as well as mission PE costs. If no impact, so state.
- Summary of proposed offsets to include program element, appropriation and cost element detail including out years. Also identify cost savings, over and above proposed offsets, resulting from proposed program.
- Discussion of the proposed plan, including the pros and cons of such areas as operational effects, combat enhancements, supportability issues, manpower issues, and congressional concerns.
- A statement that EIAP actions have been initiated and a properly completed AF Form 813, Request for Environmental Impact Analysis, is being forwarded under separate cover.
- Last statement should include the action officer's name, office symbol, and telephone number.
6.3. Programming Agency Actions. When SECAF/CSAF has decided on each PCR, the Programming Agency will notify HQ USAF/PE, SAF/FMB, and appropriate Programming Agency of approval or disapproval status and ensure that the appropriate data base and Programming documents are updated during the next available budget exercise.
6.4. Approval or Disapproval Message. Addressed to the submitting MAJCOM. Information copies to all interested MAJCOMs, the Secretariat and Air Staff Directorates, the National Guard Bureau, and the Air Force Reserve (if required). HQ AFMC/LGI must be an addressee on all messages that affect force structure and flying hours so they can ensure the changes are incorporated into the buy, repair, and distribution decisions. An approval message will contain the following elements:
- Present Program. Force structure or manpower displays of current program by quarter of each fiscal year to include out years.
- Approved Program. Force structure or manpower displays of the approved program by quarter of each year to include out years.
- Costs of Approved Program. Cost summary of the approved program to include program element, appropriation, cost element detail, and BP (for Procurement Accounts) including out years. As a minimum, identify BOS O&M, RPM, Communication and MILCON cost as well as mission PE costs.
- Approved Offsets. Include program element, appropriation, cost element detail, and BP (for Procurement Accounts) including out years. As a minimum, identify BOS O&M, RPM, Communication and MILCON cost as well as mission PE costs.
- Verification of the receipt of Program Agency approved AF Form 813.
- Approval comments.
- Changes to mobility and war authorizations if approved. If not applicable, so state.
- Action officer's name, office, and DSN number.
6.5. Headquarters Air Force Actions:
6.5.1 Each PCR Programming Agency will:
- Act as the executive agent for their PCRs.
- Coordinate with affected Air Staff directorates (including HQ USAF/PE and SAF/FMB) to ensure the program requested in the PCR is executable, correctly costed, and contains appropriate offsets.
- Coordinate the PCR for possible base impacts, public announcement, and congressional notification procedures (OCR: HQ USAF/XOO).
- Maintain a master control log of all generated PCRs.
- Coordinate and verify, through the Office of the Civil Engineer (HQ USAF/CE), Directorate of Environmental Quality (HQ USAF/CEV) (and NGB/CEV or HQ USAF/REXR when appropriate) that required EIAP actions are complete.
- Complete required follow-up actions after PCR approval or disapproval (see paragraph 6.4).
6.5.2. HQ USAF/CE (and NGB/CEV or HQ USAF/REXR when appropriate) will coordinate MILCON, family housing and real property maintenance requirements, EIAP, and all issues relating to facilities support.
6.5.3. SAF/AQ will ensure details relating to major system acquisition and aircraft supportability are correct.
6.5.4. HQ USAF/LG will ensure that execution and budget year procurement of logistic support items are adjusted to reflect all approved PCRs.
6.5.5. HQ USAF/XO will:
- Ensure PCRs correctly identify operational readiness and training issues.
- Ensure PCRs correctly identify factors relating to war readiness, including changes to the War Reserve Materiel munitions, Readiness Spares Packages (RSP), regional issues, etc.
- Ensure initiation of proper public announcement and congressional notification procedures.
- Review PCRs for base impacts and ensure that facility requirements driven by new missions at a base are properly identified and coordinated with HQ USAF/CEP (and NGB/CEP or HQ USAF/REXR when appropriate).
6.5.6. SAF/FM will:
- Ensure all appropriation managers review PCR.
- Ensure a correctly costed PCR to include but not limited to manpower and flying hours actions.
- Ensure the proposed offsets are appropriately costed.
- Review PCR for financial limitations imposed by OSD, OMB, or the Congress.
- Help identify funding issues that may arise before the Operating Budget Review Committee.
- Ensure inclusion of command transfers during the budget year and out years (to include BOS tails) for model and non-model costs which result from PCRs processed under this instruction.
- Ensure sufficient funding is available and programmed to carry out proposed personnel actions (permanent change of station, separation incentives, etc.).
- SAF/FMB will task MAJCOM/FMA to provide
- D-22 exhibits for non-model command transfers.
- 6.5.7. HQ USAF/PE will:
- Verify manpower impacts, issues, and costs.
- Review the PCR to ensure it can be integrated into the Air Force Program.
- Track all approved and pending PCR actions.
- In conjunction with SAF/FM, validate the completed resources action as outlined in the approved PCR.
- Maintain Change Control Number (CCN) integrity of model and non-model resources.
- Enter approved PCR action into the Options database and pass as Programming Guidance to SAF/FMB.
- Ensure approved PCRs are included in the next update of programming documents.
6.5.8. SAF/LL will coordinate on all PCRs and accomplish appropriate congressional notification.
6.5.9. HQ USAF/DP will:
- Verify military and civilian personnel impacts, issues, and costs/savings with SAF/FMBOP.
- Assess impacts of proposed actions in training and availability of trained personnel resources.
- In conjunction with SAF/FM, insure sufficient funding is available and programmed to carry out proposed personnel actions (permanent change of station, separation incentives, etc.).
- Recommend the most cost effective forms of unit moves.
6.5.10. Air Reserve Components will:
- Coordinate all issues and requirements listed in paragraphs 6.5.2 through 6.2.9 within Air National Guard and Reserve channels, verifying impacts, issues and costs for Air Reserve Component specific PCRs.
- CHARLES R. HEFLEBOWER, Brig General, USAF
- Director of Programs and Evaluation
3 Attachments
1. Glossary of Abbreviations, Acronyms, and Terms
2. Sample Program Change Request (PCR) Message
3. Program Documents and Supplementary Program Documents Listing
GLOSSARY OF ABBREVIATIONS, ACRONYMS, AND TERMS
AFC (Air Force Council)--Advises and makes recommendations to the Chief of Staff on major matters, including the responsiveness of Air Force plans and programs to national, Office of the Secretary of Defense, Joint Chiefs of Staff, and Air Force objectives. AFC is the only review body for programmatic issues whose recommendations go to the Chief of Staff and the Secretary of the Air Force. This process balances programs among mission areas, between force structure and support, and between readiness and modernization. The Vice Chief of Staff chairs the AFC. Membership is at the Deputy Chief of Staff (three-star) level, corresponding Secretariat level, and selected Directorate (two-star) level. The Special Access Required (SAR) Programs Oversight Committee (SPOC) is a subset of the AFC. The SPOC will review programmatic issues for SAR Programs.
Budget Year--The first fiscal year of a 2-year budget awaiting approval by the Congress.
C4I-- Command, Control, Communications, Computers, and Intelligence.
Disconnect--An approved program or portion of an approved program which has become unexecutable because of a mismatch between its resources and the content validated by Headquarters Air Force. Specific Air Force or Office of the Secretary of Defense decisions to change the program content or pace in the Planning, Programming, and Budgeting System cycle are not candidates for disconnects in the following year's cycle. These represent intentional adjustments to programs and must compete as new content in the initiative phase of the next cycle if restoration of content is desired. The using command and the applicable Headquarters United States Air Force Resource Allocation Agency must validate all disconnects.
D-22--Office of the Assistant Secretary of the Air Force, Financial Management and Comptroller, Directorate of Budget Operations (SAF/FMBO) Financial Plan exhibit used as a vehicle to transfer Air Force Operations and Maintenance funds between commands to include approved Program Change Request actions for the budget year but not included in the President's Budget submission.
EIAP--Environmental Impact Analysis Process.
Execution Year--The current fiscal year.
Fiscal Year (FY)--The 12-month period which begins 1 October of 1 year and ends 30 September of the next.
FYDP--Future Years Defense Program. The official document and data base which summarizes Secretary of Defense approved plans and programs for the Department of Defense.
Headquarters PCR--Generated by Headquarters Air Force to direct an out-of-cycle program change.
MAJCOM Initiative--A proposal for additional funds to add to an approved ongoing program's content or to initiate a new program (new start).
MAJCOM PCR--Generated by the major command to request an out-of-cycle program change.
Offsets. Identified resources that are offered to "pay" for a Program Change Request action, disconnect, or initiative.
Out Years--The years of the Air Force Program not included in the execution or budget years.
PCR--A Program Change Request to change programmed resource allocations outside the normal program exercise process (out-of-cycle).
Prior Year (PY)--The fiscal year immediately preceding the current year (last completed fiscal year). Also referred to as Past Year.
USAF F&FP--USAF Force and Financial Plan--the data base which describes the Future Years Defense Program.
SAMPLE PROGRAM CHANGE REQUEST (PCR) MESSAGE
UNCLASSIFIED
01 03 FEB 94 RR RR UUUU
NGB WASHINGTON DC//XO//
HQ USAF WASHINGTON DC/(appropriate Programming Agency)//
INFO:
HQ USAF WASHINGTON DC//(other Programming Agencies)/PE//
HQ ACC LANGLEY AFB VA//XP/XPP/DO/LG/FM//
HQ AFMC WRIGHT PATTERSON AFB OH/DO/XP/XPP/XRA/XRB/XRI/XRJ/FM//
HQ AFMPC RANDOLPH AFB TX//CC//
HQ AFRES ROBINS AFB GA//XP/FM//
HQ AFSOC HURLBURT FLD FL//XP/XPP/FM//
HQ AFSPC PETERSON AFB CO//XP/XPP/FM//
HQ AMC SCOTT AFB IL//XP/FM//
HQ AETC RANDOLPH AFB TX//XP/XPPB/FM//
HQ PACAF HICKAM AFB HI//XP/XPPC/FM//
HQ USAFE RAMSTEIN AB GE//XP/XPPF/FM//
HQ USAF WASHINGTON DC//CE/CEVP/DP/DPPR/IN/INRP/LG/LGSW//
RE/REXP/REC//XO/XOFP//
NGB WASHINGTON DC//CF/LG/CE/DP/FM//
SAF WASHINGTON DC//AQ/AQXR/FM/FMBP/GC/MI/MII//
UNCLASS
SUBJECT: ADD 3 PAA TO 106 RS (ANG PCR 94-01)
1. THIS NGB PCR ADDS 3 PAA (RF-4C) TO THE 106 RS AT BIRMINGHAM BEGINNING IN FY 94/3, AND DRAWS DOWN 6 F-16AS FROM 127 FW, SELFRIDGE BEGINNING IN FY 95/3.
2. PRESENT PROGRAM: FY 94 FY 95
1 2 3 4 1 2 3 4
106 RS (RF-4C) 18 18 18 18 18 18 18 18
127 FW (F-16A) 24 24 24 24 24 24 24 24
3. PROPOSED CHANGE: FY 94 FY 95
1 2 3 4 1 2 3 4
106 RS (RF-4C) 18 18 21 21 21 21 21 21
127 FW (F-16A) 24 24 24 24 24 24 18 18
4. WE ESTIMATE THE FOLLOWING COSTS FOR FY 94 AND FY 95:
FY 94 FY 95
3010 (PE XXXXX) +.880 +1.088
3080 +.05 +0.050
3300 0 0
3400 +4.31 +4.38
3500 +1.68 +1.70
TOTAL +6.92 +7.218
5. THE FOLLOWING MANPOWER POSITIONS WILL BE REQUIRED:
DRILL OFFICER +23 +23
DRILL ENLISTED +137 +137
CIVILIAN +44 +44
6. THE FOLLOWING OFFSETS ARE PROPOSED:
FY 94 FY 95
3010 (PE XXXXX) -.80 -.837
3080 -.698 -.720
3300 0 0
3400 -4.13 -4.38
3500 -2.33 -2.36
TOTAL -7.958 -8.187
7. THE FOLLOWING MANPOWER POSITIONS WILL BE GIVEN UP:
DRILL OFFICER -26 -26
DRILL ENLISTED -193 -193
CIVILIAN -53 -53
8. THE ADDITIONAL RF-4C AIRCRAFT ARE AVAILABLE FROM RECONSTITUTION RESERVE (NOTE: RECONSTITUTION RESERVE EQUALS ATTRITION RESERVE MINUS PROGRAMMED ATTRITION LOSSES). AFMC AND SYSTEM PROGRAM MANAGER ASSURE US THAT SUFFICIENT SPARES AND SUPPORT EQUIPMENT ARE AVAILABLE FOR THE ADDITIVE FLYING HOURS. THE 6 F-16AS WILL BE PROGRAMMED INTO RECONSTITUTION RESERVE. WE HAVE INITIATED THE ENVIRONMENTAL IMPACT ANALYSIS PROCESS, AND THE AF FORM 813 IS BEING FORWARDED. THIS PCR HAS BEEN COORDINATED WITH HQ ACC, HQ PACAF, HQ USAFE, AND HQ AFMC.
9. THE NGB POC IS MAJOR CLARK, NGB/XOOC, DSN 225-0226.RELEASER'S SIGNATURE BLOCK
UNCLASSIFIED
PROGRAM DOCUMENTS AND SUPPLEMENTARY PROGRAM DOCUMENTS LISTING
PROGRAM DOCUMENTS
HQ
Short USAF Biennial
Title Title OPR Pubs
Aerospace Vehicles and Flying Hours PA
- Vol I, Aircraft and Flying PE 2
Hours by Mission Design Series
- Vol II, Aircraft and Flying PE 2
Hours by Command
- Vol III, Strategic Missiles, PE 2
Cruise Missiles, Remotely
Piloted Vehicles, and
Target Drones
- Vol IV, Space Systems XOF 2
Installations, Units, and Priorities PD XOO 2
SUPPLEMENTARY PROGRAM DOCUMENTS
HQ
Short USAF Biennial
Title Title OPR Pubs
Flying Training Program FTP XOO 3
Manpower and Organization PM PE 2
- Vol I, Regular Forces
- Vol II, Reserve Forces
Operational Test and Evaluation Program PO TE 2
Tactical Air Missile Program PT XOF 1
Technical Training Program PTT DPP 3
Air Force