| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2018-06-29 (8.2 years ago) |
| Status | Current |
| Proponent / OPR | SAF/CN |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This publication establishes policy and assigns roles and responsibilities for developing, maintaining, storing, and implementing sound integrated and interoperable architectures across the Air Force for Information Technology (IT) and National Security System (NSS) across the four DoD mission areas to support decision-making processes and ensure the alignment of Air Force’s IT and NSS environment with the critical mission needs of the Air Force. It redefines the Air Force Enterprise Architecture (AFEA) framework and removes architecture approval and certification guidance and removes the Terms of Reference for the Architecture Executive Committee and Architecture Development Working Group. Chapter 1 — ENTERPRISE ARCHITECTURE 4 Figure 1.1. Levels of Architecture. (Federal Enterprise Architecture Practice Guidance, Chapter 2 — ROLES AND RESPONSIBILITIES 8
This document has been substantially revised and needs to be completely reviewed. This instruction supersedes AFI 33-401, Air Force Architecting. This instruction incorporates interoperability guidance contained in expired Air Force Guidance Memorandum (AFGM) 2015 - 33-03. This publication establishes policy and assigns roles and responsibilities for developing, maintaining, storing, and implementing sound integrated and interoperable architectures across the Air Force for Information Technology (IT) and National Security System (NSS) across the four DoD mission areas to support decision-making processes and ensure the alignment of Air Force’s IT and NSS environment with the critical mission needs of the Air Force. It redefines the Air Force Enterprise Architecture (AFEA) framework and removes architecture approval and certification guidance and removes the Terms of Reference for the Architecture Executive Committee and Architecture Development Working Group
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 | 2 | DAFI 63-101 20-101, DAFPAM 63-128 |
2 publications in 1 other community depend on this one, which Cyberspace 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 17-140 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.
Records in this branch carrying the same series and number — interim changes, guidance memoranda, and unit supplements. A copy stamped with one of these is a different document from the base publication.