| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2013-03-14 (13.5 years ago) |
| Status | Current |
| Proponent / OPR | SAF/AQ |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This instruction establishes guidance and procedures for planning, governance, and execution of the Air ForceS&T Program. The Air ForceS&T Program consists of Basic Research, Applied Research, and Advanced Technology Development (research, development, test and evaluation [RDT&E] budget activity categories 6.1, 6.2, and 6.3, respectively). The S&T Program must be responsive to Air Force capability needs while guarding against technological surprise. It includes in-house laboratory and contracted activities to produce both evolutionary and revolutionary technology-enabled opportunities.
This publication is updated to document roles and responsibilities for Air ForceS&T planning, governance, Capability Collaboration Teams (CCT), Flagship Capability Concepts (FCC), Joint Capability Technology Demonstrations (JCTD), and S&T-related Memorandums of Agreement (MOA) or Memorandums of Understanding (MOU) that were not addressed in the previous AFI. It also reflects changes in guidance and procedures dealing with Applied Technology Councils (ATC) and Advanced Technology Demonstra tions (ATD). This is a major revision to AFI 61 - 101 and must be reviewed in its entirety. 2 AFI61-101 14 MARCH 2013
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. 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 61-101 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.