| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2018-10-29 (7.8 years ago) |
| Status | Current |
| Proponent / OPR | SAF/FM |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This document has been substantially revised and needs to be completely reviewed. Major changes include: Air Force Instructions (AFIs) 65-501 and 65-509 have been combined to form one Instruction; a clarification was added that economic analysis is both an analytical approach to decision-making and one of many products resulting from the analytical approach; a clarification was added that all comparative analysis products (e.g., Cost Benefit Analysis, Analysis of Alternatives, Business Case Analysis, etc.) fit under the umbrella of the economic analysis approach and are subject to this Instruction (consistent with Department of Defense Instruction (DoDI) 7041.03). As a result, this Instruction now uses one term, comparative analysis, to refer to all types of analysis that result from using the economic analysis approach and uses the term comparative analysis product for the document resulting from a comparative analysis
Publications state their own changes on page 1 — behind a PDF the official host will not serve to a search engine. This is that section, verbatim. It describes the edition above, not every historical change.
| Functional community | Publications | Which ones |
|---|---|---|
| Materiel Management | 3 | DAFMAN 23-300 ACC Sup, AFI 23-101 AFMC Sup, AFMAN 23-122 AFMC Sup |
| Acquisition | 2 | DAFI 63-101 20-101, DAFPAM 63-128 |
5 publications in 2 other communities depend on this one, which Financial Management owns. Each community inspects its own publications; a dependency that crosses communities is owned by nobody, which is why this list normally does not exist anywhere. Built from the publications' own citations, so it reflects what we have read.
If AFI 65-501 changes, these are the documents that point at it. Extracted from the publications' own text, so it reflects what we have read, not a complete dependency map. Every publishing office validates its own document; nobody validates the seams between them.