This instruction supersedes DAFI 61-201, which is currently listed in the MPM. It provides mandatory guidance for managing Air Force Scientific and Technical Information (STINFO): creation, marking, protection, dissemination, archiving, and destruction throughout its lifecycle. Intended for all DAF personnel and organizations involved in RDT&E, technical publishing, or handling of STINFO. Reference: 1.1.5.9 Manage Scientific and Technology Information
AFMAN 63-143 Centralized Asset Management Procedures (19 August 2025)
Establishes procedures for the Air Force Centralized Asset Management program, detailing roles, funding execution, and oversight processes. Provides standardized guidance for program managers, financial managers, and acquisition personnel. Reference: 1.2.2 Conduct Programming and 1.2.2.8 Conduct Logistics Requirements Determination Process
Adaptive Acquisition Framework Document Identification Tool (AAFDID) (12 August 2021)
The AAF Document Identification Tool (AAFDID) enables acquisition professionals to systematically identify applicable statutory and regulatory documentation requirements aligned to each Adaptive Acquisition Framework pathway. Reference 1.5 Conduct “Program” Management Tasks
DAFMAN 23-300 Materiel Management Procedures (22 July 2025)
This document supersedes DAFI 23-101. Initial review indicates it impacts current processes in sections 1.4.3.4.1 through 1.4.3.4.3.
DAFI 62-601Airworthiness (30 June 2025)
Purpose / Scope -Defines Department of the Air Force (DAF) airworthiness policy—covering design, production, operations, and maintenance—for all DAF‑owned, leased, modified, or operated air systems Lifecycle Phases -Design: Independent design assessments against airworthiness criteria; requires approvals via the Technical Airworthiness Authority (TAA) -Production: Oversight of manufacturing processes (DCMA, program manager) to ensure each system conforms to approved design -Operations: Systems operated per approved technical data and relevant DAF instructions -Maintenance: Maintenance aligned with approved technical orders and program maintenance concepts Reference 1.5.1.2.6 Conduct Other Technical Processes
