| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2020-04-29 (6.3 years ago) |
| Status | Current |
| Proponent / OPR | SAF/SA |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This instruction applies to all Air Force (owned or managed) models and simulations that qualify as federation elements, common-use, general-use, or joint modeling & Simulation as defined in the DoD online Modeling & Simulation Glossary.
This instruction is revised to meet current SecAF guidance for publications. Section A —General 3 1. Applicability.......................................................................................................... 3 2. Background............................................................................................................ 3 Section B —Roles and Responsibilities for V&V Management 4 3. HQ USAF Responsibilities.................................................................................... 4 4. MAJCOM Commander Responsibilities................................................................. 6 Section C —VV&A Framework, Functional Roles, and Processes 6 5. VV&A Framework................................................................................................ 6 Figure 1. M&S Options and VV&A Steps.............................................................................. 7 6. Functional Roles within the Air Force VV&A Process........................................... 8 Table 1. VV&A Roles & Documentation Responsibilities................................................... 9 7. VV&A Process........................................................................................................ 13 8. VV&A Documentati on.......................................................................................... 17 9. VV&A Repository................................................................................................. 18 10. Multi-Model or Federated Architectures................................................................. 19
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 |
|---|---|---|
| Acquisition | 1 | DAFI 63-101 20-101 |
1 publication in 1 other community depend on this one, which Operations Support 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 16-1001 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.