3d. AFI 32-1020, Planning and Programming Built Infrastructure Projects.pdf

DEPARTMENT OF THE AIR FORCE

HEADQUARTERS UNITED STATES AIR FORCE

WASHINGTON DC

DAFI32-1020_DAFGM2023-01

20 July 2023

MEMORANDUM FOR DISTRIBUTION C

MAJCOMs/FLDCOMs/FOAs/DRUs

FROM: AF/A4

1030 Air Force Pentagon, Suite 4E154 Washington DC 20330-1030

SUBJECT: Department of the Air Force Guidance Memorandum to Department of the Air Force

Instruction 32-1020, Planning and Programming Built Infrastructure Projects

By order of the Secretary of the Air Force (SecAF), this Department of the Air Force (DAF) Guidance Memorandum (DAFGM) immediately implements changes to Department of Air Force Instruction (DAFI) 32-1020, Planning and Programming Built Infrastructure Projects. Compliance with this memorandum and its attachments is mandatory. To the extent its direction is inconsistent with other Department of the Air Force publications, the information herein prevails in accordance with Department of the Air Force Instruction (DAFI) 90-160, Publications and Forms Management and Department of the Air Force Manual (DAFMAN) 90-161, Publishing Processes and Procedures.

This memorandum has been updated to reflect how the civil engineer governance structure applies to special Military Construction programs and funding authorized by Congress outside the established authorities outlined in DAFI 32-1020. It establishes AF/A4 Deputy Chief of Staff for Logistics, Engineering & Force Protection as the office authorized to determine and decide program management questions, including project sequencing, scheduling, and prioritization, for special Military Construction programs that would normally be decided by the Air Force corporate structure.

It also makes updates to the economic analysis requirement within a project’s lifecycle, deletes the requirement to accomplish a DD1354 in the programming stage, establishes requests for equitable adjustment as a funded cost, and updates guidance on reporting for relocatable facilities.

Furthermore, it provides updates the table in Attachment 2 for Networked Facilities and clarifies existing guidance in various sections.

The use of an asterisk (*) identifies a substantive change over the previous guidance. It becomes void after one year has elapsed from the date of this memorandum, upon publication of an interim change to, or rewrite of DAFI 32-1020, whichever is earlier.

TOM D. MILLER

Lieutenant General, USAF DCS/Logistics, Engineering & Force Protection

Attachment:

DAFI32-1020_DAFGM2022-02, Planning and Programming Built Infrastructure Projects Current guidance in DAFI 32-1020, Planning and Programming Built Infrastructure Projects, remains in effect with the following changes:

*Added. This publication applies to all civilian employees and uniformed members of the Regular Air Force, the Air Force Reserve, the Air National Guard, the United States Space Force, the Civil Air Patrol when conducting missions as the official Air Force Auxiliary, all DAF civilian employees, and those with a contractual obligation to abide by the terms of DAF issuances.

*Added. Note: All references to United States Air Force (USAF) terminology, units, grades, and positions will also apply to the equivalent in the USSF, as appropriate. For example, references to Airmen will also apply to Guardians. References to MAJCOMs or NAFs will also apply to field commands. References to wings will also apply to deltas. Air Staff roles and responsibilities (e.g., AF/A1, etc.) may also apply to the equivalent Office of the Chief of Space Operations (Space Staff) position or office (e.g., SF/S1, etc.), as deemed appropriate.”

*Changed. Throughout the DAFI change “AFCEC Director” to “AFCEC Commander” and change “AFCEC/CL” to “AFCEC/CC.”

*1.2.3 Changed. Director of Civil Engineers (AF/A4C). Provides policy-implementing guidance and oversight for built infrastructure programs and facilities investment. Advocates for Civil Engineer portfolio resources through the Air Force Corporate Structure, Office of the Secretary of Defense (OSD), Office of Management and Budget (OMB), and Congress. A4C will define 35% design maturity to ensure Air Force budget requests comply with OSD standards. When delegated from AF/A4 Deputy Chief of Staff, Logistics, Engineering & Force Protection, act as the Air Force Corporate Structure element to decide program management and funding questions for special Military Construction programs and funding authorized by Congress outside normal Military Construction authorities.

*2.1.1. Changed. Certificate of Compliance for Critical Planning Actions (CoC). For projects approved higher than installation-level, the Planning Action Process on the Comprehensive Planning Platform (CPP) is the primary vehicle to validate requirements and determine the appropriate course of action. For projects, which go through the Planning Action Process, a completed Certificate of Compliance is not required. Instead, the BCE or designated Flight Chief (may not be delegated lower) may sign the CoC and check the box stating the project was approved via the Planning Action Process. For projects requiring HAF or higher-level approval which did not go through the Planning Action Process, a completed CoC is still required.

Alternatively, programmers may choose to put these requirements through the Planning Action Process to eliminate the Certificate of Compliance requirement. When a completed CoC is required for projects requiring HAF or higher-level approval it must include BCE signature and the first cross-functional commander above the Civil Engineer or Group. If the first cross-functional commander is above the group level, signature may be delegated to that commander’s vice or deputy, but no lower. (T-1) Approval request packages for projects requiring AFCEC, AFRC/A4, or NGB/A4 approval require a CoC signed by the BCE (or equivalent) ensuring the elements of the CoC were used to inform planning actions and requirements development of the project, though completion of the CoC items do not need to be documented or coordinated on the CoC. (T-1) BCE signature on the CoC for projects to be approved by AFCEC, AFRC/A4, or NGB/A4 may be delegated no lower than a flight chief/commander. (T-1) For projects with costs requiring approval at the installation level, a CoC is not required, but planners and programmers are encouraged to consider the elements of a CoC for all projects. The planning results documented by the CoC should be approved by the installation Facilities Board.

*2.4.8.1.2. Changed. Though cost comparison and value analysis should be completed for all work, in accordance with AFI 65-501, Economic Analysis, project justification based on an economic analysis is required when either: 1) the construction cost is greater than $2M or 2) the repair cost is greater than $2M and is greater than 75% of estimated cost of a construction project to replace the facility. (T-1) See Paragraph 2.5.1 for work classification guidance.

*2.4.8.1.3. Changed. When accomplishing an EA, programmers must demonstrate use of an acceptable cost estimating method for determining the estimated facility replacement cost:

Parametric Cost Estimating System (PACES) cost estimate, Micro Computer Aided Cost Estimating System 2nd Generation (MII), or other method specified by the Life Cycle Cost Engineering Subject Matter Expert (LCCE SME) in AFCEC/COS. (T-1)

*2.6.4. DELETED

*2.6.6. Changed. Project Management Information Technology (IT) Databases. Project management data will be maintained in an Air Force-approved project management database.

(T-1) NexGen IT is the DAF authoritative IT system for maintenance and reporting of real property data as prescribed in DAFI 32-9005.

*2.7.9. Changed. Sensitive Compartmented Information Facilities (SCIF). When a project will include a SCIF subject to Intelligence Community Directive (ICD) Number 705, Sensitive Compartmented Information Facilities, the installation must obtain project security requirements from the Site Security Manager or Accrediting Official. (T-0) Applicable construction standards and any escorts, construction surveillance technicians (CST), or cleared American guards, if allowed by 10 USC § 2465, Prohibition on contracts for performance of firefighting or security-guard functions, shall be identified and estimated costs included as separate lines on the DD Form 1391. (T-0) The installation will include the estimated cost of escorts or cleared American Guards on the DD Form 1391 as an unfunded cost from other appropriations; these costs will be provided or funded by the user. (T-1) The SCIF security cost shall be calculated during the planning phase and certified by the design agent and/or design and construction project managers (DM/CM). (T-1) If the installation is to provide any project support, only that portion of installation overhead or support costs that can be identified as additional costs that would not have been incurred were it not for the SCIF portion of the project should be included ((DoD 7000.14-R, Volume 3, Financial Management Regulation, Budget Execution – Availability and Use of Budgetary Resources, Chapter 17, Accounting Requirements for Military Construction Projects, paragraph 1704). Any requirements exceeding a standard, even when based on risk, requires a waiver be processed and approved in accordance with ICD 705. (T-0) For standards, see IC Tech Spec – for ICD/ICS 705, Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities, current edition, located at https://www.dni.gov/files/Governance/IC-Tech-Specs-for-Const-and-Mgmt-of-SCIFs-v15.pdf. Per Paragraph 2.7.9.1, the term “Sensitive Compartmentalized Information Facility” or the acronym “SCIF” cannot be used in any project title or anywhere in a DD Form 1391;

however, SCIF requirements, including escorts and CSTs, must be identified on the DD Form 1391 to be considered in scope. (T-1)

2.7.9.1. Changed. Do not use the term “Sensitive Compartmentalized Information Facility” or the acronym “SCIF” in any project title or anywhere in a DD Form 1391. (T-0) The facility’s location and identity as a SCIF shall be protected at a minimum of “Controlled Unclassified Information” (CUI), formerly FOR OFFICIAL USE ONLY (FOUO), in accordance with Department of Defense Manual (DODM) 5105.21-V2 CE-01, Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Physical Security, Visitor Control, and Technical Security. (T-0)

2.7.9.2. Changed. SCIFs should be referred to as a controlled space so as not to designate it as a SCIF on releasable documents (e.g., bid requests, permit requests, sub-contractor plans). Ensure SCIF spaces are properly captured on the DD Form 1354 and labeled as Controlled Space (similar to DD Form 1391) for proper accountability.

*2.7.9.3 Added. The following paragraph applies to repair and construction (unspecified and specified) work of SCIFs as outline in Paragraph 2.7.9 and associated sub-paragraphs. This change for project funded costs takes effect and applies to all contracts awarded on or after 1 October 2024 (FY25). Construction surveillance technicians/personnel required to comply with ICD 705, as directed within the Accrediting Official (AO) approved Construction Security Plan, are authorized as a project funded cost. If the project did not require ICD 705 compliance, this work and associate personnel would not be required. This does not include site security, which is either provided by the user, requestor, or site owner or funded by said parties. Construction surveillance can only be project funded if the construction surveillance is not accomplished by a government employee (military, civilian, or government hired contractor). This line-item cost should be titled “Construction Security Surveillance” and should be placed in the funded section after the SUBTOTAL and before the SIOH. This nomenclature will be distinguished from unfunded “Site Security Surveillance” cost, which includes escorts and cleared American guards.

*2.7.12.1. Changed. Planners and programmers shall follow the process outlined in AFMAN 32- 7003, Environmental Conservation, Section 3D. (T-1) The goal should first be to avoid the construction of facilities in or partially within a floodplain. The EIAP process shall be completed for all repair or construction projects within or partially within the 100-year floodplain. (T-0)

*2.9. Changed. Cost Estimates. All cost estimates for projects covered by this Instruction and exceeding $1,000,000 (considering funded project costs only) must be prepared by an authorized cost estimator, defined as an AFIT WENG 400 graduate. (T-1) Cost estimates may be prepared by an Architectural-Engineering (A-E) firm as part of the planning charrette or design process.

Projects with funded costs exceeding installation approval level must be reviewed by an

AFCEC/COS dedicated reviewer/approver. (T-1) A-E personnel are not required to be WENG 400 graduates. However, a WENG 400 graduate at the installation level must take ownership of the A-E estimate and submit the estimate, and other required documentation to AFCEC/COS as required for review. (T-1) Similarly, projects at locations not under the jurisdiction of a primary installation commander and/or locations not on DoD real property records with costs exceeding approval levels delegated to the respective senior Civil Engineers (for example, HQUSAFE-

AFAFRICA/A4C, HQ PACAF/A4C, HQ AFCENT/A7, HQ AFSOUTH/A4, HQ ACC

AMIC/PCE) must be reviewed by an AFCEC/COS dedicated reviewer/approver. (T-1) AFRC/A4 or NGB/A4 projects requiring DAF-level approval must be reviewed by an AFCEC/COS dedicated reviewer and approver. (T-1) For AFRC/A4 or NGB/A4 projects approved below DAF-level, the respective staffs can choose whether to secure AFCEC/COS review and approval. AFCEC/CV has authority to determine which project cost estimates with costs exceeding installation approval level may be exempted from review by AFCEC/COS. All estimates should be prepared, reviewed, and approved in accordance with guidelines in the Civil Engineering Cost Estimating Improvement Program.

NOTE: MILCON and UMMC projects in which the Air Force is the Design and Construction Agent (DCA) must be reviewed by an AFCEC/COS dedicated reviewer/approver. MILCON and UMMC projects in which USACE or NAVFAC is the DCA will not go through the CEIP reviewer process but will use USACE’s or NAVFAC’s internal review process.

*2.9.1. Changed. All estimates must be prepared using parametric estimating tools, at a minimum. (T-1) PACES is the only DoD-approved software to develop parametric cost estimates. The basis for parametric project cost estimates is completed planning documents, such as a charrette report. Cost estimates must be developed using PACES, MII, or other method, as approved by the LCCE SME in AFCEC/COS. (T-1) For example, a paving project being executed by an Indefinite Delivery / Indefinite Quantity (IDIQ) contract should be estimated using the predefined contract cost line items in the same format as the IDIQ contract and not in PACES or MII. Other methods are also permitted for A-E projects already in solicitation as of the date of this guidance memorandum. A-E projects not yet in solicitation require a provision in the statement of work requiring estimates be developed using PACES, MII, or other method as approved by the LCCE SME in AFCEC/COS prior to award. (T-1) The estimator must develop and maintain a Basis of Estimate (BOE) that supports a well-documented and auditable estimate (T-1) The BOE, which may use the RP 34R-05 as a guide as taught in AFIT’s cost estimating training (WENG 400), provides cost estimating traceability. Additional detailed requirements for use of PACES, AFIT training, and other guidance for cost estimating are found on the LCCE SME Cost Estimating guidance in CE DASH SharePoint ® site. The site can currently be found at https://usaf.dps.mil/teams/CEDASH/SitePages/Service%20Page.aspx?Service=Cost%2 0Engineering and the guidance is under “Resources.”

*2.11.2. Changed. Ensure an equivalent cost-to-replacement comparison. Programmers cannot expand the facility used in the replacement cost estimate (cost of a replacement MILCON) to accommodate new or additional requirements beyond the existing facility (mission, function, size, etc.) unless that same additional scope is also included in the repair project. The replacement scope (MILCON) should be the same as the total facility of the project in the numerator (existing facility), to include any additions. For example, if the repair project in the numerator includes an addition, the replacement MILCON project in the denominator should also include this same addition or square footage. Note: the replacement facility can be brought up to code. (T-1)

*3.5.2. Changed. After approving repair projects estimated to exceed $7,500,000, SAF/IEE will report the approval to the appropriate congressional committees. (T-0) Failure to obtain SAF/IEE approval of such projects prior to the obligation of funds may be a statutory violation. Such projects may not proceed until completion of a 7-day period beginning on the day of SAF notification to committees and ending after AF/A4CF, AFRC/A4, or NGB/A4 notification to the installation that the waiting period is complete. (T-1) See the AF/A4CF FSRM DD Form 1391 preparation business rules for details on the contents of a project approval request package.

AF/RE and NGB/A4 will establish procedures within their respective chains to obtain necessary SAF/IEE approvals and notifications for repair projects. (T-1)

*3.5.4. Changed. Project Re-Approval. The authorities provided for project approval cover both scope and cost as provided in the approval document (DD Form 1391). Projects with work, which differs from or has been changed (increased or decreased) from the scope of what was approved (see Paragraph 3.5.4.3) or with costs exceeding the threshold cost-differences described in this paragraph require re-approval. The cost threshold requiring re-approval of a repair project is different in the project’s pre-award and post-award life cycle. Prior to award, a repair project with costs exceeding 45% difference from the approved amount requires re-approval by the appropriate approval authority (based on the newly expected cost if the cost went up and based on the original approval if the cost went down). After award, the baseline is reset at the award amount plus other funded costs (e.g., SIOH), and a repair project with costs (including all funded costs) exceeding 25% difference from the award amount requires re-approval by the appropriate approval authority (based on the newly expected cost). Once a project has been re-approved, the new threshold for the project is based on the re-approved amount.

*3.5.4.2.1. Added. Per Paragraph A5.1.13., requests for equitable adjustment (REAs) are funded costs to the project. REAs do count against statutory thresholds—they are part of the total project cost. If an REA contributes to the funded cost of a project exceeding a statutory threshold or cost limit (e.g., the 10 USC §2811 repair approval and notification threshold of $7,500,000 or the 10 USC §2805(c) cost limit for unspecified minor construction projects funded with appropriations available for operation and maintenance), re-approval and applicable notification are required.

*3.5.4.2.2. Added. Though requests for equitable adjustment (REAs) are funded costs to a project, if an REA only causes a project’s cost to exceed the 125% cost increase threshold or the threshold for higher level approval (e.g., AFCEC approval instead of installation-level approval), the project does not require re-approval.

*3.5.7.1. Changed. See the AF/A4CF FSRM DD Form 1391-preparation business rules for details on the contents of a project approval request package.

*5.2.1.5. Added. Special Military Construction Programs. Congress may choose to authorize military construction projects outside of the authorities and funding listed in the paragraphs above. Emergent and urgent projects that cannot be deferred to proceed through the established military construction planning and programming process describes programs that might be authorized through special authorities. As these projects have not been planned and competed through the normal prioritization and programming process, authority to manage these programs, including decisions on prioritization, sequencing, and scheduling is retained by AF/A4 Deputy Chief of Staff, Logistics, Engineering & Force protection and as delegated to AF/A4C.

*5.2.2.5. Changed. Foreign Military Sales Construction (FMS). 22 USC § 2751 et seq., Arms Export Control, establishes legal controls on the import and export of defense articles and defense services and codifies the Arms Export Control Act. 22 USC § 2769 authorizes construction services sales to eligible foreign countries. Air Force installations must ensure that proposed FMS construction facilities, built on their installations, are solely for foreign government use. (T-0) Facilities required for Air Force use, which may also be available for FMS, must be constructed with appropriated funds. (T-0) FMS construction facilities built on Air Force installations are not Air Force real property assets unless the foreign government transfers title to the Air Force an appropriate statutory authority. Unless title is thus conveyed to the Air Force, installations must ensure that the land on which the facility is built is leased to the foreign government. (T-0) Installations must consult the Office of the Air Force Deputy General Counsel (Installations, Energy and Environment) through AFCEC regarding such leases. (T-1) FMS-funded construction on Air Force installations is subject to the EIAP. EIAP results for MILCON-scope and UMMC-scope construction must be approved by SAF/IEE. (T-1)

7.2.4 Changed. Project Justification and Submittal. Installations will submit project justifications as specified in the published storm damage business rules, which are located at https://usaf.dps.mil/teams/10041/Dashboards/Pages/Storm%20Tracker%20Dashboard.aspx (T-2) Commanders will ensure that the submittal includes a DD Form 1391, a DD Form 1391c, and any additional information requested. (T-2) The submittal should explain the urgency and indicate, for each facility, the cause of damage or destruction. The Base Civil Engineer shall certify the following: (i) the project is for restoration or replacement of facilities damaged or destroyed; (ii) any scope increase is a result of economy of design or compliance with new criteria; (iii) deferral of the replacement project for inclusion in the next regular MILCON program would be inconsistent with the national security or the protection of health, safety or environmental quality; and (iv) in the case of damage to a facility rather than destruction, a replacement project is more cost-effective than repairing the facility. (T-2)

*8.5. Changed Management and Approval. All RLFs require approval before being acquired and placed in service, except those in support of a named continuing military operation (see Paragraph 8.4.6). RLF management and approval guidance outlined below includes leased swing space as appropriate. In accordance with OSD policy, approval to use RLFs may not be delegated below a general officer or senior executive service civilian equivalent located at a centralized headquarters organization. For the Regular Air Force (RegAF), AFCEC manages the relocatable facility program and holds approval responsibility for use of RLFs to include extending use beyond the initial approved duration (see Paragraph 8.5.2 for use duration and https://usaf.dps.mil/teams/10041/Dashboards/Pages/Storm%20Tracker%20Dashboard.aspx approval thresholds). AFRC/A4 and NGB/A4 similarly hold approval and extension responsibility for their respective units. If necessary, AFCEC, AFRC/A4, and NGB/A4 may establish approval criteria beyond what is provided below.

*8.3.8.8. Added. CONEX boxes less than 500 square feet (including when connected) and not being used for living or working. These CONEX boxes are equipment items and are not subject to policy in this chapter. CONEX boxes are essentially shipping containers being used for storage. Purpose-built structures (e.g., for living or working) should not loosely be categorized as CONEX boxes. Validate categorization with AFCEC/CI or AF/A4CA. Placing CONEX boxes requires siting approval through the installation’s facility board before being placed. (T-2)

*8.5.2.1. Changed. The RLF is supporting a continuing military contingency operation. RLFs supporting a named contingency operation are exempt from the limitations on time of use regardless of location of the RLF. See Paragraph 8.4.

*8.5.9.3. Added. The following relocatable facilities will not require reporting:

*8.5.9.3.1. Changed. Facilities placed in service at contingency locations.

*8.5.9.3.2. Changed. Facilities used to meet international agreements in lieu of permanent solutions.

*8.5.9.3.3. DELETED

*A5.1.13. Added. Request for Equitable Adjustment (REA). Unlike claims, which are considered unfunded costs to the project, REAs are considered funded costs to the project. See Paragraph 3.5.4.2.1. and Paragraph 3.5.4.2.2. for guidance on repair project re-approval driven by REAs.

Attachment 1 Abbreviations and Acronyms

*Changed. LCCE – Life Cycle Cost Engineering

Terms

* Changed. Parametric Estimate - An estimate using pre-developed algorithms and cost models using the AFCEC approved software. Currently, PACES is the only approved software for parametric estimates. Parametric estimates should not include guidance unit costs.

Attachment 2 Networked Facility Determination

*Table A2.1. Changed. Networked Facility Determination.

Networked Facility Networked Facility Components (Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category

Airfield Pavements:

Interconnected assets within the 2-digit DoD Category Group “11”.

- Airfield Runways (3-digit DoD Basic Category - 111) -- Associated Lighting, Runway (6-digit Category Code -

136664) -- Associated Utility Vaults (4-digit DoD FAC - 8927) -- Associated Aircraft Pavement Shoulder (4-digit DoD FAC

- 1165) -- Exclude Runway, Unsurfaced (4-digit DoD FAC - 1114)

- Airfield Taxiways (3-digit DoD Basic Category - 112) -- Associated Taxiway Lighting (6-digit Category Code -

136667) -- Associated Utility Vaults (4-digit DoD FAC - 8927) -- Associated Aircraft Pavement Shoulder (4-digit DoD FAC

- 1165)

- Airfield Aprons (3-digit DoD Basic Category - 113) -- Associated Airfield Pavement Lighting (4-digit DoD FAC

- 1361) -- Associated Utility Vaults (4-digit DoD FAC - 8927) -- Associated Aircraft Pavement Shoulder (4-digit DoD FAC

- 1165)

- Compass Calibration Pad, Surfaced (4-digit DoD FAC -

1161) -- Associated Airfield Pavement Lighting (4-digit DoD FAC

- 1361) -- Associated Utility Vaults (4-digit DoD FAC - 8927) -- Associated Aircraft Pavement Shoulder (4-digit DoD FAC

- 1165)

- Aircraft Washing Pad, Surfaced (4-digit DoD FAC - 1163) -- Associated Airfield Pavement Lighting (4-digit DoD FAC

- 1361) -- Associated Utility Vaults (4-digit DoD FAC - 8927) -- Associated Aircraft Pavement Shoulder (4-digit DoD FAC

- 1165)

- Miscellaneous Airfield Pavement, Surfaced (4-digit DoD

FAC - 1164)

- Aircraft Arresting System (6-digit Category Code - 116922)

Networked Facility Networked Facility Components (Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category

Aircraft Fuel Dispensing Facilities: Interconnected assets within the 3-digit DoD Basic Category “121”, to include associated components as listed to the right.

- Aircraft Fueling Facility (4-digit DoD FAC - 1211)

- Aircraft Defueling Facility (4-digit DoD FAC - 1212)

- Aircraft Operating Fuel Storage (4-digit DoD FAC - 1241)

- Other Operating Fuel Storage (4-digit DoD FAC - 1244)

- POL Pipeline (4-digit DoD FAC - 1251)

- POL Piping (4-digit DoD FAC - 1252)

- Liquid Fuel Loading/Unloading Facility (4-digit DoD FAC -

1261)

- POL Pump Station (4-digit DoD FAC - 1262)

- Bulk Liquid Fuel Storage (4-digit DoD FAC - 4111)

- Large Bulk Liquid Fuel Storage (4-digit DoD FAC - 4112)

- Cut-and-Cover Bulk Liquid Fuel Storage (4-digit DoD FAC

- 4113)

- Small Bulk Storage (4-digit DoD FAC - 4114)

- Miscellaneous Storage Tank and Basin (4-digit DoD FAC -

8951)

Marine Fuel Dispensing Facilities: Interconnected assets within the 3-digit DoD Basic Category “122”, to include associated components as listed to the right.

- Marine Fueling Facility (4-digit DoD FAC - 1221)

- Marine Operating Fuel Storage (4-digit DoD FAC - 1242)

- Other Operating Fuel Storage (4-digit DoD FAC - 1244)

- POL Pipeline (4-digit DoD FAC – 1251)

- POL Piping (4-digit DoD FAC - 1252)

- Liquid Fuel Loading/Unloading Facility (4-digit DoD FAC -

1261)

- POL Pump Station (4-digit DoD FAC - 1262)

- Bulk Liquid Fuel Storage (4-digit DoD FAC - 4111)

- Large Bulk Liquid Fuel Storage (4-digit DoD FAC - 4112)

- Cut-and-Cover Bulk Liquid Fuel Storage (4-digit DoD FAC

- 4113)

- Small Bulk Storage (4-digit DoD FAC - 4114)

- Miscellaneous Storage Tank and Basin (4-digit DoD FAC -

8951)

Land Vehicle Fuel Dispensing Facilities: Interconnected assets within the 3-digit DoD Basic Category “123”, to

- Vehicle Fueling Facility (4-digit DoD FAC - 1231)

- Vehicle Operating Fuel Storage (4-digit DoD FAC - 1243)

- Other Operating Fuel Storage (4-digit DoD FAC - 1244)

- POL Pipeline (4-digit DoD FAC - 1251)

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category include associated components as listed to the right.

- POL Piping (4-digit DoD FAC - 1252)

- Liquid Fuel Loading/Unloading Facility (4-digit DoD FAC -

1261)

- POL Pump Station (4-digit DoD FAC - 1262)

- Bulk Liquid Fuel Storage (4-digit DoD FAC - 4111)

- Large Bulk Liquid Fuel Storage (4-digit DoD FAC - 4112)

- Cut-and-Cover Bulk Liquid Fuel Storage (4-digit DoD FAC

- 4113)

- Small Bulk Storage (4-digit DoD FAC - 4114)

- Miscellaneous Pump Station (4-digit DoD FAC - 8924)

- Miscellaneous Storage Tank and Basin (4-digit DoD FAC -

8951)

Communication Lines:

Interconnected assets within the 3-digit DoD Basic Category “135”, to include associated components as listed to the right.

- Communication Lines (4-digit DoD FAC - 1351)

- Associated Utility Vaults (4-digit DoD FAC - 8927)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

Electrical Power:

Interconnected assets within the 2-digit DoD Category Group “81”, to include associated components as listed to the right.

- Electrical Power Distribution Line, Overhead (4-digit DoD

FAC - 8121)

- Exterior Lighting, Pole (4-digit DoD FAC - 8122)

- Electrical Power Distribution Line, Underground (4-digit

DoD FAC - 8123)

- Electric Power Substation (4-digit DoD FAC - 8131)

- Electric Power Switching Station (4-digit DoD FAC - 8132)

- Electric Power Transformers (4-digit DoD FAC - 8133)

- Associated Utility Vaults (4-digit DoD FAC - 8927)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Exclude all Electric Power Source assets (3-digit DoD Basic

Category - 811)

Heat Transmission and Distribution Lines:

Interconnected assets within the 3-digit DoD Basic Category “822”, to include

- Heat Distribution Line (4-digit DoD FAC - 8221)

- Miscellaneous Pump Station (4-digit DoD FAC - 8924)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Associated Utility Channels (4-digit DoD FAC - 8932)

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category associated components as listed to the right.

Heat Gas Transmission:

Interconnected assets within the 3-digit DoD Basic Category “824”, to include associated components as listed to the right.

- Heat Gas Storage (4-digit DoD FAC - 8232)

- Heat Gas Distribution Line (4-digit DoD FAC - 8241)

Chilled Water (Air Conditioning) Transmission and Distribution Lines:

Interconnected assets within the 3-digit DoD Basic Category - 827”, to include associated components as listed to the right.

- Chilled Water and Refrigerant Distribution Line (4-digit DoD FAC - 8271)

- Miscellaneous Pump Station (4-digit DoD FAC - 8924)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Associated Utility Channels (4-digit DoD FAC - 8932)

Sewage and Industrial Waste Treatment and Disposal:

Interconnected assets within the 3-digit DoD Basic Category “831”, to include associated components as listed to the right.

- Water Separation Facility (4-digit DoD FAC - 8313)

- Septic Tank and Drain Field (4-digit DoD FAC - 8314)

- Septic Lagoon and Settlement Ponds (4-digit DoD FAC -

8315)

- Sewage Lift Stations (4-digit DoD FAC - 8316)

- Sewer and Industrial Waste Line (4-digit DoD FAC - 8321)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Associated Utility Channels (4-digit DoD FAC - 8932)

- Exclude all Sewage Treatment assets (4-digit DoD FAC -

8311)

- Exclude all Industrial Waste Treatment assets (4-digit DoD

FAC - 8312)

- Exclude all Water Separation Facility assets (4-digit DoD

FAC - 8313)

- Exclude all Storm Drainage Disposal (6-digit Category

Code - 871183)

Potable Water Distribution System: Interconnected assets within the 3-digit DoD Basic Category “842”, to

- Water Storage, Potable (4-digit DoD FAC - 8413)

- Water Distribution Line, Potable (4-digit DoD FAC - 8421)

- Water Pump Facility, Potable (4-digit DoD FAC - 8422)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category include associated components as listed to the right.

- Associated Utility Channels (4-digit DoD FAC - 8932)

Fire Protection Water Facilities: Interconnected assets within the 3-digit DoD Basic Category “843”, to include associated components as listed to the right.

- Water Distribution Line, Fire Protection (4-digit DoD FAC - 8432)

- Water Impoundment, Fire Protection (4-digit DoD FAC - 8433)

- Water Pump Facility, Fire Protection (4-digit DoD FAC - 8434)

- Water Tank, Fire Protection (4-digit DoD FAC - 8435)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Associated Utility Channels (4-digit DoD FAC - 8932)

- Exclude all Water Source, Fire Protection assets (4-digit

DoD FAC - 8431)

Non-potable Water Distribution System:

Interconnected assets within the 3-digit DoD Basic Category “845”, to include associated components as listed to the right.

- Water Storage, Non-potable (4-digit DoD FAC - 8442)

- Water Distribution Line, Non-potable (4-digit DoD FAC -

8451)

- Water Pump Facility, Non-potable (4-digit DoD FAC -

8452)

- Associated Utility Tunnels (4-digit DoD FAC - 8931)

- Associated Utility Channels (4-digit DoD FAC - 8932)

Roads, Bridges, and Tunnels:

Interconnected assets within the 3-digit DoD Basic Category “851”, to include associated components as listed to the right.

- Road, Surfaced (4-digit DoD FAC - 8511)

- Vehicle Bridge (4-digit DoD FAC - 8513)

- Vehicular Tunnel (4-digit DoD FAC - 8514)

- Traffic Control Signals (4-digit DoD FAC - 8541)

- Vehicle Parking, Surfaced assets (4-digit DoD FAC - 8521)

[Exclude those serving a single building]

- Vehicle Parking and Staging Area, Unsurfaced assets (4-digit DoD FAC - 8522) [Exclude those serving a single building]

- Vehicle Staging Area, Surfaced assets (4-digit DoD FAC - 8523) [Exclude those serving a single building]

- Miscellaneous Paved Area assets (4-digit DoD FAC - 8526) [Exclude those serving a single building]

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category

- Exclude all Driveway assets (6-digit Category Code -

851145)

- Exclude all Road, Unsurfaced assets (4-digit DoD FAC -

8512)

Sidewalks and Other Pavements: Interconnected assets within the 3-digit DoD Basic Category “852”, to include associated components as listed to the right.

- Sidewalk and Walkway (4-digit DoD FAC - 8524)

- Pedestrian Bridge (4-digit DoD FAC - 8525)

- Exclude all Vehicle Parking, Surfaced assets (4-digit DoD

FAC - 8521)

- Exclude all Vehicle Parking and Staging Area, Unsurfaced assets (4-digit DoD FAC - 8522)

- Exclude all Vehicle Staging Area, Surfaced assets (4-digit

DoD FAC - 8523)

- Exclude all Miscellaneous Paved Area assets (4-digit DoD

FAC - 8526)

Railroad Tracks:

Interconnected assets within the 3-digit DoD Basic Category “860”, to include associated components as listed to the right.

- Railroad Track (4-digit DoD FAC - 8601)

- Railroad Bridge (4-digit DoD FAC - 8611)

Grounds Drainage:

Interconnected assets within the 3-digit DoD Basic Category “871”, to include associated components as listed to the right.

- Storm Drainage (4-digit DoD FAC - 8711)

- Retaining Structure assets (4-digit DoD FAC - 8712) [Note:

only those contributing to grounds drainage]

- Grounds Drainage Dams (4-digit DoD FAC - 8713)

- Levees and Dikes for Ground Drainage (4-digit DoD FAC -

8714)

- Storm Water Ponds (4-digit DoD FAC - 8715)

- Sewer and Industrial Waste Line (4-digit DoD FAC – 8715)

- Storm Drainage Disposal (6-digit Category Code - 871183)

- Sewer and Industrial Waste Line (4-digit DoD FAC – 8715)

[Note: only those contributing to grounds drainage]

- Miscellaneous Pump Station (4-digit DoD FAC - 8924)

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category

Grounds Fencing, Gates, and Guard Towers:

Interconnected assets within the 3-digit DoD Basic Category “872”, to include associated components as listed to the right.

- Boundary Fence and Wall (4-digit DoD FAC - 8721)

- Security Fence (4-digit DoD FAC - 8722)

- Security Guard Tower (6-digit Category Code - 872845)

[Note: These towers must be integrated into the perimeter fence or directly/solely employed at the installation perimeter.]

- Security Police Entry Control Building (6-digit Category Code - 730837)

- Access Control Facility (6-digit Category Code - 730839)

- Visitor Control Center (6-digit Category Code – 730832)

- Overhead Protection (6-digit Category Code - 145921)

[Note: This only pertains to self-supporting structures providing overhead to Airmen and Guardians directly supporting entry control points.]

Additionally, the following are also included in the Grounds Fencing, Gates, and Guard Towers Networked Facility for the area directly supporting the respective controlled areas entry control points. Reference Figure A2.1 below and the US Army Military Surface Deployment and Distribution Command Transportation Engineering Agency Pamphlet 55- 15, Traffic and Safety Engineering for Better Entry Control Facilities.

- Road, Surfaced (4-digit DoD FAC - 8511)

- Traffic Control Signals (4-digit DoD FAC - 8541)

- Vehicle Parking, Surfaced assets (4-digit DoD FAC - 8521)

- Vehicle Parking and Staging Area, Unsurfaced assets (4-digit DoD FAC - 8522)

- Vehicle Staging Area, Surfaced assets (4-digit DoD FAC -

8523)

- Miscellaneous Paved Area assets (4-digit DoD FAC - 8526)

- Exclude all Driveway assets (6-digit Category Code -

851145)

- Exclude all Road, Unsurfaced assets (4-digit DoD FAC -

8512)

(Those which are interconnected within the networked facility) Note: FAC = Facility Analysis Category

Note: An installation may have more than one Grounds

Fencing, Gates, and Guard Towers Networked Facility. For example: The main Networked Facility is the exterior perimeter fence and entry gates. This network should also include the interior airfield fence and gates that ARE connected to the perimeter fence. The second Networked Facility maybe the Grounds Fencing, Gates, and Guard Towers network around a specific facility or compound inside the installation (i.e., Korea Air Operations Center, CENTCOM Headquarters, etc.) This network value shall not be combined with the exterior perimeter fence Networked Facility.

Installation Gas Distribution Line: Interconnected assets within the 4-digit DoD Facility Analysis Category “8930”, to include associated components as listed to the right.

- Installation Gas Distribution Line (4-digit DoD FAC - 8930)

*Figure A2.1 Added. Entry Control Facilities Limits for Grounds Fencing, Gates, and Guard Towers Networked Facilities

Added. Facility component contained in the Approach Zone, Access Control Zone or Response Zone are considered part of the Networked Facilities based on category codes defined in Table A2.1. This figure is from the US Army Military Surface Deployment and Distribution Command Transportation Engineering Agency Pamphlet 55-15, Traffic and Safety Engineering for Better Entry Control Facilities.

Attachment 5 Funded And Unfunded Costs

*A5.1.7.5. Changed. SIOH is generally used to pay for U.S. Army Corps of Engineers (USACE) or the Naval Facilities Engineering Command (NAVFAC) execution for design and construction services. Air Force execution (design and construction) and contracting, and some OCONUS contracting (e.g., Republic of Korea lead contracting agency for non-MILCON is the Contracting Support Brigade) do not qualify for SIOH. For SIOH performed by USACE or NAVFAC refer to the applicable agent’s district office for current rates and note the reference in Block 11 of the DD Form 1391. Ensure costs included as SIOH are among those listed in Paragraph 2.9 See AF/A4C DD Form 1391 preparation business rules for guidance about stating the SIOH cost in the DD Form 1391.

A5.1.7.6. Changed. Title II services costs are typically included in SIOH. When additional service is required above normal SIOH, it must be added as a separate line item in Block 9. (T-1) Do not title these services as "Title II Services". Programmers must specify what the services are. Provide justification for additional services in Block 11, ADDITIONAL. (T-1)

BY ORDER OF THE SECRETARY

OF THE AIR FORCE

DEPARTMENT AIR FORCE

INSTRUCTION 32-1020

18 DECEMBER 2019

Incorporating Change 1, 19 JANUARY 2022

Civil Engineering

PLANNING AND PROGRAMMING

BUILT INFRASTRUCTURE PROJECTS

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at www.e-Publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication

OPR: AF/A4CF Certified by: AF/A4C

(Brig Gen Kale) Supersedes: AFI32-1020, 18 December 2019

AFI32-1032, 24 September 2015 AFI32-1021, 25 February 2016 AFI32-1022, 30 December 2015

Pages: 116

This instruction implements Air Force Policy Directive (AFPD) 32-10, Installations and Facilities, and AFPD 34-1, Air Force Services, and establishes an asset management framework to deliver common levels of service for civil engineering activities. It provides guidance and instruction for planning and programming and obtaining approval for appropriated fund and nonappropriated fund maintenance, repair, and construction projects. This instruction applies to all Department of the Air Force civilian employees and uniformed members including the Air Force Reserve and Air National Guard. To ensure a full understanding of the process of providing maintenance, repair, and construction support to real property, users of this instruction should be familiar with other Air Force 32-(Civil Engineer) and 65-(Budget) series publications. Department of the Air Force Manual (DAFMAN) 65-605, Volume 1, Budget Guidance and Technical Procedures, is particularly important for determining funded and unfunded costs for all projects.

Ensure all records generated as a result of processes prescribed in this publication adhere to Air Force Instruction 33-322, Records Management and Information Governance Program, and are disposed in accordance with the Air Force Records Disposition Schedule, which is located in the Air Force Records Information Management System. Refer recommended changes and questions about this publication to the Office of Primary Responsibility using AF Form 847, Recommendation for Change of Publication; route AF Forms 847 from the field through Major Command (MAJCOM) publications or forms managers. MAJCOMs may supplement this http://www.e-publishing.af.mil/

2 *DAFI32-1020 18 DECEMBER 2019

instruction to include command-unique requirements. Waiver authorities are identified with a Tier (“T-0, T-1, T-2, and T-3”) number following the compliance statement. See Department of Air Force Instruction (DAFI) 33-360, Publications and Forms Management, Table 1.1 for a description of the authorities associated with the Tier numbers. Submit requests for waivers through the chain of command to the appropriate Tier waiver approval authority, or alternately, to the requestor’s commander for non-tiered compliance items. The use of the name or mark of any specific manufacturer, commercial product, commodity, or service in this publication does not imply endorsement by the Air Force. Compliance with Attachments 1, 2, 4, and 5 in this publication is mandatory. Attachment 3 is the Certificate of Compliance for Critical Planning Actions template. This template is going to be dynamic, so this publication does not mandate this exact template. AF/A4C will post the recommended and updated form for use by the field and will communicate updates.

SUMMARY OF CHANGES

This interim change revises AFI32-1020, Planning and Programming Built Infrastructure Projects, dated 18 December 2019. This IC (1) updates the following requirements: Certificate of Compliance, maintaining a project management database, applicability of antiterrorism measures under Unified Facilities Criteria (UFC) 4-010-01, DoD Minimum Antiterrorism Standards for Buildings, guidance for programming Sensitive Compartmented Information Facilities, programming guidance for aircraft sunshades, programming of pump houses as a component of an associated building, requirement to use Air Force standard facility designs, guidance for programming contingency on Facility Sustainment, Restoration, and Modernization (FSRM) projects, the distinction of sustainment vs. restoration and modernization, 14-day notification requirement for certain repair projects, re-approval requirements for Unspecified Minor Military Construction projects, the definition of Air Force project management database, guidance for funding for cleanup of environmental contamination, projects to improve already-improved surfaces, system owner involvement in alteration of privatized systems; (2) defines allowable use of Working Capital Funds for certain minor construction, responsibility for planning actions, requirements for cost estimator and reviewer qualifications, data standards and business rules for facilities projects, definition of failed facilities, programming guidance for Energy Resilience and Conservation Investment Program, Certificate of Compliance requirements for Wing Safety coordination, facility conversion, and basing action, mission growth and personnel increases and networked facilities; (3) adds guidance for Cybersecurity of Civil Engineer Control systems; (4) explaining capitalization, incorporates demolition guidance; (5) updates guidance for programming communications cabling; (6) adds relocatable facility guidance; (7) adds Planning Charrette Report guidance. A margin bar (|) and asterisk (*) indicates newly revised material.

Chapter 1—INTRODUCTION 5

1.1. Overview

1.2. Roles and Responsibilities

1.3. Legal Framework

*DAFI32-1020 18 DECEMBER 2019 3

Chapter 2—PROJECT PLANNING AND PROGRAMMING 12

2.1. Overview

2.2. Responsibilities

2.3. Requirements Identification and Definition

2.4. Development and Evaluation of Alternative Solutions

2.5. Work Classification, Demolition, and Capitalization

2.6. Programming Actions

Table 2.1. Suggested Source Documentation

2.7. Planning and Programming Factors

Table 2.2. UFC 3-600-01, Fire Protection Engineering for Facilities, Compliance Metrics.

(T-0)

2.8. DELETE

2.9. Cost Estimates

2.10. Funded and Unfunded Costs

2.11. Estimated Facility Replacement Cost for Repair Projects

2.12. AFCAMP Floor

Chapter 3—MAINTENANCE AND REPAIR PROJECTS 40

3.1. This chapter provides general procedures for programming Air Force real property projects with the work classified as maintenance or repair

3.2. Maintenance

3.3. Repair Authority

3.4. Funding Categories

3.5. Delegation and Approval Levels

Chapter 4—UNSPECIFIED MINOR CONSTRUCTION 48

4.1. Unspecified Minor Construction

4.2. Unspecified Minor Construction approval

4.3. Project Justification

4.4. Re-Approval

Chapter 5—PROGRAMMING MILITARY CONSTRUCTION (MILCON) 50

5.1. Military Construction (MILCON) Definition

5.2. MILCON Programming

5.3. Project Identification and Validation

4 *DAFI32-1020 18 DECEMBER 2019

Chapter 6—NONAPPROPRIATED FUND PROJECTS 56

6.1. Nonappropriated Fund Projects

6.2. Fund Sources for NAF Projects

6.3. Project Approvals

Chapter 7—OTHER CONSTRUCTION AUTHORITIES 65

7.1. Contingency Construction Authority and Limitations

7.2. Restoration or Replacement of Damaged or Destroyed Facilities (10 USC § 2854)

Chapter 8—*RELOCATABLE FACILITIES 70

8.1. Relocatable facilities (RLFs)

8.2. Definition

8.3. Scope

8.4. When Relocatable Facilities May Be Used

8.5. Management and Approval

8.6. Programming and Funding Relocatable Facilities

8.7. NAF Relocatable Facility Requirements (see Paragraph 6.2.13)

8.8. Maintenance of Relocatable Facilities

8.9. Inventory, Reuse, and Disposition of Relocatable Facilities

Table 8.1. Funding Guide for Relocatable Facilities and Their Allied Support

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 81

Attachment 2—NETWORKED FACILITY DETERMINATION 93

Attachment 3—CERTIFICATE OF COMPLIANCE 100

Attachment 4—EXAMPLES OF WORK CLASSIFICATION 107

Attachment 5—FUNDED AND UNFUNDED COSTS 113

*DAFI32-1020 18 DECEMBER 2019 5

Chapter 1

INTRODUCTION

1.1. Overview. This instruction establishes guidance and provides guidance on planning and programming cost-effective appropriated fund and nonappropriated fund (NAF) maintenance, repair, and construction projects for real property facilities, collectively referred to as “built infrastructure projects,” in compliance with referenced and applicable law, and Department of Defense (DoD) and Air Force guidance.