Attch8-11.pdf

1239914680C Typewritten Text Attachment 08

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE INSTRUCTION 32-1024

14 JULY 2011

Incorporating Change 1, 19 December 2014

Civil Engineering

STANDARD FACILITY REQUIREMENTS

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 and ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: AFCEE/TDB

Supersedes: AFI32-1024, 31 May 1994

Certified by: AF/A7CP

(Lt Col John J. Allen, Jr.)

Pages: 8

This Instruction implements AFPD 32-10, Installations and Facilities, and Department of

Defense Instruction (DoDI) 4165.3, Department of Defense Facility Classes and Construction

Categories. This Instruction is applicable to all Air Force active duty, civilian, Reserve (AFR) and Air National Guard (ANG) personnel and unit facilities. Air National Guard facility requirements are defined in ANGH 32-1084, ANG Standard Facility Requirements. Civil Air

Patrol may adopt this guidance at the discretion of the applicable installation commander, per

AFI 10-2701. It provides general guidance for developing standard facility requirements. It describes the facility requirements system, assigns responsibilities, and explains how to initiate and process new and revised standards for publication in AFMAN 32-1084, Facility

Requirements. Civil engineers should use the facility space allowances listed by category code in

AFMAN 32-1084 to assign occupancy and to program new facilities. Refer recommended changes and questions about this publication to the Office of Primary Responsibility (OPR) using the AF Form 847, Recommendation for Change of Publication; route AF Forms 847 from the field through appropriate functional chain of command. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with

AFMAN 33-363, Management of Records, and disposed of in accordance with the Air Force

Records Disposition Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm. 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.

http://www.e-publishing.af.mil/ https://www.my.af.mil/afrims/afrims/afrims/rims.cfm 1239914680C

Attachment 09

2 AFI32-1024 14 JULY 2011

SUMMARY OF CHANGES

The authorities to waive wing/unit level requirements in this publication are identified with a

Tier (“T-0, T-1, T-2, T-3”) number following the compliance statement. See AFI 33-360, Publications and Forms Management, 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 Publication OPR for non-tiered compliance items. An asterisk (*) indicates newly revised material. Due to Air Force restructuring effective

1 October 2012, Air Force Center for Engineering and the Environment (AFCEE) and Air Force

Civil Engineer Support Agency (AFCESA) were changed to Air Force Civil Engineer Center

(AFCEC) throughout the document. Any name change resulting from creation of the Air Force

Installation and Mission Support Center (Provisional) on 1 October, 2014 will be incorporated into the next revision.

1. Facility Requirements System:

1.1. The Facility Requirements System develops and approves standards that define the type, number, and size of facilities. The system promotes economy and efficiency in using and developing facilities and helps realize the following goals:

1.1.1. Design standards for new and revised functional requirements.

1.1.2. Maximum use of existing facilities.

1.1.3. Standards of use to justify new facilities and occupy existing facilities.

1.1.4. Comprehensive programming for the construction, operation, and maintenance of needed facilities.

1.2. The organization of the Facility Requirements System is based on the DoD Real

Property Classification System (RPCS). RPCS is a hierarchical scheme of real property types and functions that forms the framework for identifying, categorizing, and analyzing

DoD’s inventory of land and facilities. The scheme is a tiered structure represented by numerical codes, with one-digit codes being the most general and five- or six-digit codes representing the most specific types of facilities.

1.2.1. Each Military Service has established its own set of numerical codes, commonly known as facility Category Codes, to represent each type of facility in its inventory. The

Air Force uses a six-digit hierarchy.

1.2.2. Category Codes (CATCODE) are generally similar but not identical between

Military Services. However, DoD established a higher-level facility classification that groups facilities with similar functions and units of measure from the Military Services into common Facility Analysis Categories (FAC) at the four-digit level. These FACs allow consistent macro-level analysis and planning across DoD. Successively smaller groupings of facility types are represented by three-, two-, and one-digit numerical classifications. The RPCS structure is numerically consistent between the one-digit and four-digit levels, but it is not always consistent across the Military Services at the five-and six-digit level. Further information on the DoD Real Property Classification System can be viewed on the Office of the Deputy Under Secretary of Defense, Installations and

Environment Web site:

http://www.acq.osd.mil/ie/fim/programanalysis_budget/tool_metrics/RPCS/rpcs.shtml.

http://www.acq.osd.mil/ie/fim/programanalysis_budget/tool_metrics/RPCS/rpcs.shtml 1024710587C Highlight

AFI32-1024 14 JULY 2011 3

1.3. The Facility Requirements System is further defined in AFMAN 32-1084, Facility

Requirements, which provides guidance and standards for the type, number, and size of facilities the Air Force can use, occupy, or build to support its mission. Air National Guard facility requirements are defined in ANGH 32-1084, ANG Standard Facility Requirements.

A listing in the handbook does not provide automatic justification for programming a facility or for including it in the base comprehensive plan. All available space must be considered when establishing a space deficiency and when justifying programming action. Approved standards published in AFMAN 32-1084 contribute to:

1.3.1. Timely acquisition of facilities.

1.3.2. Expedited construction program reviews and approvals.

1.3.3. Expedited project design.

1.3.4. Equitable space allocation in existing facilities; the published standards help divide limited assets among competing functions.

1.3.5. Standardization of facility design; the Air Force realizes benefits not only in design and construction but also in program management and functional operations.

2. Responsibilities:

2.1. The Deputy Assistant Secretary of the Air Force for Environment, Safety and

Infrastructure (SAF/IEE) establishes Air Force facility requirements policy consistent with

DoD policy and standards for facility requirements.

2.2. The Director of Civil Engineer (AF/A4C):

2.2.1. Implements policies and establishes procedures for the Facility Requirements

System.

2.2.2. Monitors Air Force-wide programs leading to new or revised facility standards to ensure all functional requirements are satisfied.

2.2.3. Consults on architectural, engineering, and other design aspects of proposed facility requirements.

2.2.4. Approves standard facility requirements.

2.2.5. Prepares AFMAN 32-1084 and ensures it is current.

2.3. AFMAN32-1084, Table A2.2, lists the facility OPRs for each Facility Category Code;

these OPRs are the primary action offices for developing facility requirements. Facility OPRs must ensure facility requirements supporting new and changing functions are identified early and timely action is taken to develop new standards for approval and publishing.

2.4. Major commands (MAJCOM), field operating agencies (FOA), and the Air National

Guard establish active programs to:

2.4.1. Keep abreast of new missions, programs, or concepts that may generate new facility requirements and initiate basing action, as appropriate, for new or modified missions in accordance with AFI 10-503, Base Unit Beddown Program.

2.4.2. Develop or refine functional standards for the type, number, and size of facilities needed for mission support.

4 AFI32-1024 14 JULY 2011

2.4.3. Investigate current facility operations to determine if existing standards are adequate.

2.4.4. Obtain approval of new or revised standard facility requirements for publication in

AFMAN 32-1084 using the procedure outlined in paragraph 4 of this Instruction.

2.4.5. Initiate the Environmental Impact Analysis Process (EIAP) in accordance with 32

CFR §989

2.4.5.1. The Air Force’s EIAP (32 CFR §989) shall be accomplished consistent with the National Environmental Policy Act (NEPA) (Pub. L. 91-190, 42 U.S.C. 4321-

4347) and the Presidents’ Council on Environmental Quality (CEQ) Regulations for

Implementing the Procedural Provisions of NEPA (40 CFR §§1500-1508) prior to implementing any irrevocable actions and/or committing irretrievable resources.

2.4.5.2. The proponent of the action (32 CFR §989.3(d)) is the person or organization that is responsible for initiating action and is responsible for complying with the

EIAP and ensuring integration of the EIAP during the initial planning stages of proposed actions so that planning and decisions reflect environmental values, delays are avoided later in the process, and potential conflicts are precluded.

2.4.5.3. The Environmental Planning Function (EPF) (32 CFR §989.3(e)) supports the proponent. The proponent is responsible for notifying the EPF of its pending action and completing Section I of AF Form 813, Request for Environmental Impact

Analysis.

2.5. Other echelons develop and submit proposals to facility OPRs to improve facility requirements standards and use facilities more efficiently.

2.6. Installation commanders shall determine the requirements for a specific facility based on standards published in AFMAN32-1084 according to AFI32-1021, Planning and

Programming Military Construction (MILCON) Projects. (T-1)

2.7. New systems or major modifications to existing systems often generate facility requirements. Program managers for these systems submit requirements to OPRs listed in

AFMAN32-1084. OPRs submit approved requirements via AF Form 847 to AF/A4CF for publication in AFMAN32-1084.

3. Developing Standard Facility Requirements. Facility OPRs will coordinate with command headquarters for facilities in which they have a primary interest to:

3.1. Acquire a good understanding of the function.

3.2. Explore combining or integrating the proposed facility requirement with other requirements.

3.3. Help civil engineers turn functional requirements into design and planning standards by investigating:

3.3.1. The number of personnel and types of organizations using the facility.

3.3.2. Time and scheduling of assigned workload.

3.3.3. Environmental control.

1024710587C Highlight

AFI32-1024 14 JULY 2011 5

3.3.4. Major equipment or material used in the facility.

3.3.5. Site location or base comprehensive plan.

3.3.6. Safety considerations.

3.3.7. Cost considerations to achieve functional requirements.

3.3.8. Standards used by other government organizations for comparable facilities.

3.3.9. Environmental protection requirements.

3.3.10. Energy and sustainability features.

3.4. Establish the most accurate means of measuring and expressing the requirements to support the function; for example, square feet per person, per vehicle, per aircraft; one each per organizational unit; square yard per total factors.

3.5. Obtain AFCEC’s help with facility requirements, layout, and functional relationships.

4. Procedures for Submitting Proposed New Standards or Changes to Existing Standards:

4.1. The Office of the Secretary of Defense (OSD) has established maximum space allowances for certain facilities (primarily administrative, community, and personnel support) which by new construction or changed use may not be exceeded without advance approval. AFMAN32-1084 indicates which category code facility standards are OSD controlled. OSD also approves or implements standards developed through interagency action to standardize certain facilities (such as NAVAIDs). Facility requirements OPRs listed in AFMAN32-1084 and facility requirements OPRs in the ANG and the Air Force Reserve are responsible for obtaining desired changes to standards under OSD control. Facility OPRs will:

4.1.1. Coordinate proposals with AF/A4CF before submitting them to OSD or other

Services. ANG and AFR OPRs will also cross-coordinate proposals of mutual interest before coordinating them with AF/A4CF. Send proposals using the AF Form 847, Recommendation for Change of Publication, to AF/A4CF for processing through

AF/A4C to OSD.

4.1.2. Keep detailed records on the development and approval of the revised standards.

4.1.3. Notify AF/A4CF when OSD approves revised standards.

4.2. For standards that are not established by OSD, MAJCOM headquarters OPRs submit proposed standards and changes to standards to the appropriate Air Staff OPR listed in

AFMAN32-1084. The Air Staff facility OPR then evaluates the proposed standards for implementation, and preparation for publication. The Air Staff OPR submission must include a draft text, in the same format as those contained in AFMAN32-1084, and supporting documentation.

4.2.1. The draft handbook text of the proposed standards must include the preferred facility nomenclature, proposed space allowances or other quantitative facility requirement, and explain:

4.2.1.1. Why the facility is required to support Air Force missions, programs, responsibilities, or activities. (Reference basic publications.)

6 AFI32-1024 14 JULY 2011

4.2.1.2. The principal activities or tasks supported by the facility. (Identify the type of organization performing the work.)

4.2.1.3. The facility's major physical components and special features influencing space, cost, or other quantitative requirements.

4.2.1.4. Other important features.

4.2.2. The supporting documentation must explain in detail the descriptions and standards expressed in condensed form in the handbook text and how facility space requirements, or other quantitative limits, were derived.

5. Space Allowances. Except for those facilities covered by paragraph 4.1, the sizes and scopes in AFMAN32-1084 are guidance and may be increased or decreased. When the projects or actions require construction or change in use and require AF/A4CF approval under 32-series policy directives, the writer of the project documents must explain and justify the need to exceed published allowances. When the projects or actions do not require AF/A4CF approval, increases beyond the scopes shown may be made when approved by the MAJCOMs and Air National

Guard. AFI32-1021, Planning and Programming Military Construction (MILCON) Projects, and

AFI32-9002, Use of Real Property Facilities, provide guidance to the MAJCOMs and Air

National Guard. See also DODI 5305.5, Space Management Procedures, National Capital

Region, and AFI32-9010, Management and Reporting of Air Force Space and Building Services in OSD Assigned Facilities and in the Washington DC Area.

LOREN M. RENO, Lt Gen, USAF

DCS/Logistics, Installations & Mission Support

AFI32-1024 14 JULY 2011 7

Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

AFI 10-503, Base Unit Beddown Program, May 29, 2003

AFI 10-2701, Organization and Function of the Civil Air Patrol, July 29, 2005

AFI 32-10, Installations and Facilities, March 4, 2010

AFI 32-1021, Planning and Programming Military Construction (MILCON) Projects, January 24, 2003

AFI 32-9002, Use of Real Property Facilities, November 22, 1993

AFI 32-9010, Management and Reporting of Air Force Space and Building Services in OSD

Assigned Facilities and in the Washington DC Area, January 27, 2011

AFMAN 32-1084, Facility Requirements, (New Date TBD)

AFMAN 33-363, Management of Records, March 1, 2008

32 CFR § 989, Environmental Impact Analysis Process, March 19, 2009

40 CFR §§1500-1508, Council on Environmental Quality, 42 USC §§ 4321-4347, National Environmental Policy Act

DoDI 5305.5, Space Management Procedures, National Capital Region, June 14, 1999

Prescribed Forms

No forms are prescribed by this publication.

Adopted Forms

AF Form 813, Request for Environmental Impact Analysis

AF Form 847, Recommendation for Change of Publication

Abbreviations and Acronyms

AFCEC—Air Force Civil Engineer Center

AFCEE—Air Force Center for Engineering and the Environment

AFCESA—Air Force Civil Engineer Support Agency

AFI—Air Force Instruction

AFMAN—Air Force Manual

ANG—Air National Guard

CATCODE—Category Code

CFR—Code of Federal Regulations

DoD—Department of Defense

8 AFI32-1024 14 JULY 2011

DRU—Direct Reporting Unit

EA—Environmental Assessment

EIAP—Environmental Impact Analysis Process

EPF—Environmental Planning Function

FOA—Field Operating Agency

MAJCOM—Major Command

MILCON—Military Construction

NEPA—National Environmental Policy Act

OPR—Office of Primary Responsibility

OCR—Office of Concurrent Responsibility

OSD—Office of the Secretary of Defense

RPCS—Real Property Classification System

UFC—Unified Facilities Criteria

USAF—United States Air Force

USAFR—United States Air Force Reserve

AIR FORCE INSTRUCTION 32-10141

5 FEBRUARY 2015

Civil Engineering

PLANNING AND PROGRAMMING FIRE

SAFETY DEFICIENCY CORRECTION

PROJECTS

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

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

OPR: AF/A4CS

Supersedes: AFI32-10141, 3 March 2011

Certified by: AF/A4CS

(Col Valerie L. Hasberry)

Pages: 23

This publication implements Air Force policy directive (AFPD) 32-10, Installations and

Facilities; Department of Labor, Occupational Safety and Health Administration (OSHA) standards; the Code of Federal Regulations (CFR); applicable Unified Facilities Criteria (UFC);

National Fire Protection Association (NFPA) regulations; and other national consensus standards cited herein. It establishes a program to identify, manage, and correct fire safety deficiencies

(FSD) as defined within this instruction. It provides objective criteria for determining proper classification of FSDs and the process for correcting, deferring, and reporting FSDs. It supports processes implemented by AFPD 32-20, Fire Emergency Services, and Department of Defense

Instruction (DODI) 6055.6, DoD Fire and Emergency Services (F&ES) Program, for delivery of fire prevention services. This instruction applies to US Air Force (USAF) active and reserve component installations and activities in the United States. It also applies to USAF enduring locations outside the United States. It does not apply to contingency locations. This instruction applies to all USAF, Air Force Reserve (USAFR), and Air National Guard of the United States

(ANGUS) military and civilian personnel. This publication may be supplemented at any level, but all direct supplements must be routed to the office of primary responsibility (OPR) of this publication for coordination prior to certification and approval. The authorities to waive wing/unit level requirement in this publication are identified with a Tier (“T-0, T-1, T-2, T-3”) number following the compliance statement. See AFI 33-360, Publications and Forms

Management, 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 publication OPR for non-tiered compliance items. Refer recommended changes and questions about this publication to the OPR using AF Form 847, http://www.e-publishing.af.mil./ 1239914680C

Attachment 10

2 AFI32-10141 5 FEBRUARY 2015

Recommendation for Change of Publication; route AF Forms 847 from the field through the appropriate functional chain of command. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN)

33-363, Management of Records, and disposed of in accordance with the Air Force Records

Information Management System (AFRIMS) Records Disposition Schedule (RDS). 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.

SUMMARY OF CHANGES

This revision clarifies the intent of the fire safety deficiency program to mirror other requirement prioritization processes. This revision prevents small, high-priority fire safety deficiencies from exercising a disproportionate impact on the requirements prioritization process, and reduces the base-level management burden when installation resources have been allocated to correct a deficiency. Civil engineering program management terminology is updated to reflect the evolving asset management processes.

1. Overview

2. Roles and Responsibilities

3. Fire Safety Deficiency (FSD)

4. Processing and Managing FSDs

5. Authority Having Jurisdiction (AHJ)

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 12

Attachment 2—FIRE SAFETY DEFICIENCY CODE DECISION MATRIX 18

Attachment 3—FIRE PROTECTION ENGINEERING ANALYSIS/REVIEW MATRIX 20

1. Overview.

1.1. Purpose. This instruction defines roles and responsibilities and is designed to help effectively identify, plan, program, and advocate for the resources required to fix existing fire safety deficiencies (FSD) and avoid them during new construction.

1.2. Scope. This instruction implements the fire protection engineering policies established for the Air Force in Unified Facilities Criteria (UFC) 3-600-01, Fire Protection Engineering for Facilities. (T-1)

1.3. Background. The procedures in this instruction are designed to effectively identify, plan, program, and advocate for the resources required to correct existing FSDs and avoid them in new construction. This policy guidance supersedes Fire Protection Policy Guidance, Determining Fire Safety Deficiency (FSD) Codes, dated 17 March 2006. This guidance addresses the findings and the recommendations made by the Air Force Inspector General’s

FSD Eagle Look Inspection Report published in August 2006. These new objective

AFI32-10141 5 FEBRUARY 2015 3

procedures are a complete departure from the FSD procedures previously included in AFI

91-301, Air Force Occupational and Environmental Safety, Fire Protection, and Health

(AFOSH) Program, to address the findings and incorporate the recommendations made by the FSD Eagle Look Inspection Report. This guidance supersedes the procedures in AFI 91-

301, Instructions for Deriving RACs for Fire Safety Deficiencies.

2. Roles and Responsibilities.

2.1. Deputy Assistant Secretary of the Air Force for Environment, Safety, and

Infrastructure (SAF/IEE). SAF/IEE establishes and provides oversight of policies relating to real property, real property systems and components, and engineering services, and grants waivers to those policies in appropriate circumstances. SAF/IEE is the approval authority for facility projects exceeding a certain cost or of a certain type.

2.2. Director of Civil Engineers (HQ USAF/A4C). HQ USAF/A4C provides programming guidance, oversight, and policy as required. HQ USAF/A4C reviews, validates, and approves operation and maintenance (O&M) funded projects classified as repair, unspecified minor military construction, or for operational requirements exceeding the

Active Air Force MAJCOM commander's delegated approval authority. HQ USAF/A4C, through the Installation Support Panel, makes recommendations to the Assistant Secretary of the Air Force for Financial Management and Comptroller (SAF/FM), and the Air Force

Group, Board, and Council on requirements for, and appropriate allocation of, resources.

2.3. Reserve Component (RC) Headquarters and MAJCOMs. RC headquarters and

MAJCOMs provide oversight to ensure compliance with the law and Department of Defense and Air Force policies. MAJCOMs are responsible for establishing quality standards;

providing MAJCOM-unique guidance to supplement Air Force policies, procedures, and instructions; validating requirements identified by their installations; developing and advocating for sustainment, restoration and modernization (S/R&M) projects; promoting timely obligation of funds; project approval within delegated approval authorities; and execution of projects. The ANG Civil Engineer and AFRC Civil Engineer perform these

MAJCOM functions for their installations. The ANG Civil Engineer and AFRC Civil

Engineer will process packages for SAF/IEE approval for O&M-funded (repair or unspecified minor military construction) projects exceeding approval authority of their

MAJCOMs. For ANG or AFRC installations the responsibilities described within this instruction must be prescribed by the ANG Civil Engineer and AFRC Civil Engineer if the organizational structure at the installation does include the following roles. (T-1)

2.4. Installation Commander. The installation commander’s responsibilities include the following:

2.4.1. Provide workplaces for all Air Force employees that are free from fire safety deficiencies to the extent possible and require unit commanders, tenant commanders, functional managers, and supervisors to enforce AFOSH program requirements within their areas of responsibility. If fire safety deficiencies exist, eliminate or control them through engineering, substitution, isolation, administrative controls, revised procedures, special training, or personal protective clothing and equipment (PPE). (T-1)

2.4.2. Ensure qualified personnel evaluate and assign FSDs.

2.4.3. Review FSD-abatement projects and establish priorities.

4 AFI32-10141 5 FEBRUARY 2015

2.5. Base Leadership.

2.5.1. Facility Board (FB). Reference AFI 32-10142, Facilities Board. (T-1)

2.5.2. Functional Manager. The organizational commander responsible for the care, custody, and protection of assigned real property will initiate the process to correct existing FSDs and assist in preventing the creation of new FSDs. (T-1) Responsibilities include the following:

2.5.2.1. Ensure compliance with fire prevention requirements in their areas of responsibility. (T-1)

2.5.2.2. Provide workplaces that are free from fire safety deficiencies and conduct self-inspections for fire safety hazards and deficiencies (T-1)

2.5.2.3. Establish and implement hazard reporting and abatement programs. (T-1)

2.5.2.4. Establish procedures for employees to follow in situations of imminent danger. (T-1)

2.5.2.5. Enforce compliance with OSHA guidelines. (T-1)

2.5.3. Facility Manager (Building Manager). The facility/building manager works for the functional manager and is ultimately responsible for, submitting the work request, or calling in the work order to correct an FSD. The installation fire prevention office is available to assist the facility manager in completing the work request by identifying necessary corrective actions and the applicable design standard. (T-2)

2.6. Civil Engineering.

2.6.1. Base Civil Engineer (BCE) / Installation Fire Marshal.

2.6.1.1. The BCE approves FSD Code assignments that impact priority facilities mission continuity or generate a loss potential in excess of $5 million. (T-2)

2.6.1.2. The BCE semi-annually briefs the Environment, Safety and Occupational

Health Council (ESOHC) on any FSDs I and II remaining open or completed since the last briefing and annually briefs the ESOHC on the total number of FSD IIIs corrected during the past year. (T-3)

2.6.2. CE Engineering Flight (CEN). The chief of the engineering flight is responsible for ensuring that projects meet the requirements in UFC 3-600-01. (T-0) The engineering flight chief also ensures that the fire protection engineering analysis using operational risk assessment processes is performed in accordance with paragraph 4.6 of this instruction. (T-3) Programmers are responsible for developing the documentation for the project (e.g., DD Form 1391, FY__ Military Construction Project Data) in accordance with AFI 32-1032, Planning and Programming Appropriated Funded Maintenance, Repair, and Construction Projects. (T-1) Programmers ensure the complete solution set to an FSD is addressed as well as ensure the FSD is correctly annotated in the Civil

Engineering Project Management database. Engineers/designers need to ensure new

FSDs are not created (T-2)

2.7. Fire Emergency Services Flight. The fire emergency services flight is normally responsible for identifying FSDs. Once identified, the fire emergency services flight shall be

AFI32-10141 5 FEBRUARY 2015 5

involved in the work order review boards, facility working group meetings, and/or design review meetings. The fire emergency services flight will also attend pre-construction meetings and final facility inspections to ensure that fire safety policies and practices are being followed and that the FSD is properly corrected. Responsibilities include the following:

2.7.1. Conduct fire protection inspections and assessments. (T-1)

2.7.2. Evaluate fire hazard reports and coordinate actions with installation ground safety personnel as required. (T-1)

2.7.3. Assign risk assessment codes (RAC) to fire-related hazards IAW AFI 91-202 and/or FSD rating to FSDs IAW this instruction and coordinate them with safety officials as required. (T-2)

2.7.4. Maintain copies of OSHA standards, AFOSH related instructions/guidance and other fire prevention guidelines. (T-2)

2.7.5. Maintain a file of approved permanent exemptions or alternative/equivalency exemptions related to fire protection standards and requirements.(T-1)

2.7.6. Maintain a file of approved mitigation/corrective action plans developed under this guidance to fire-related standards. (T-2)

3. Fire Safety Deficiency (FSD).

3.1. Existing Facilities. Existing facilities on which no work is planned or underway are assumed to have been correctly constructed in accordance with the codes and standards in effect at the time of design/construction. Those standards in effect at the time the original construction project reached the 35 percent design complete stage are normally considered to be the design basis for the fire protection features of the facility. (T-1)

3.1.1. An FSD exists when it can be clearly demonstrated that some feature within the facility specifically did not meet the minimum construction standards in effect at the time of design or construction. (T-1)

3.1.2. An FSD exists when it can be shown the facility was modified or renovated and it can be clearly demonstrated that the modified or renovated feature specifically did not meet the minimum construction standards in effect at the time of design, modification, or construction. (T-1)

3.1.3. An FSD exists when it can be shown the facility occupancy (classification) changed and the building features did not meet the minimum construction standards in effect at the time of the occupancy change. (T-1)

3.1.4. An FSD exists when there is a current code or standard that specifically requires a retroactive level of installed fire protection or life safety features which are not met in an existing facility. FSDs are not created simply because current or future criteria require additional or different fire protection features than those currently installed in an existing facility unless there is a specific retroactive requirement. (T-1) Generally, NFPA 101, Life Safety Code®, establishes the specific minimum fire protection feature requirements for existing buildings; however, there are a few other standards which address specific occupancies and these could also cause an FSD. To apply to all buildings immediately, a

6 AFI32-10141 5 FEBRUARY 2015

new requirement must have specific guidance that the technical requirement is mandatory in all current existing buildings (much like NFPA 101 has specific chapters establishing the standards for existing occupancies). Failure to comply with Life Safety Code may, in fact, be a hazard and therefore qualify for a RAC. Consult with the safety office for this determination.

3.1.5. An FSD exists when the current installed fire protection features (e.g., construction elements, separation elements, fire detection/alarm systems, fire suppression systems) are not adequate for the current conditions (e.g., assets, materials, mission) in the facility. (T-2) These conditions may result from changes in commodity configurations and/or materials, changes in function operations (such as open storage to rack storage), change in process from a manual operation to an automatic or electronic operation, change from routine administrative operations to 24/7 command and control, and change from a test platform to an operational mission platform.

3.1.6. An FSD exists when it can be shown the facility operations or mission changed and the building features did not meet the minimum construction standards in effect at the time of the change. FSDs are not created simply because current or future criteria require additional or different fire protection features than those currently installed in an existing facility; an FSD only exists if there is a protection deficiency, unless there is a specific change in risk exposure.

3.1.7. An FSD identified during a fire inspection that is not corrected during the inspection visit will require the fire inspector to prepare an AF Form 1487, Fire

Prevention Visit Report. This in turn may require the fire inspector to assist the facility manager with filling out and turning in a job order (minor work) or work request to correct the deficiency. (T-2)

3.2. New Facilities. New facilities shall include all the fire protection features required by applicable codes and standards. Any failure to meet any fire protection feature will create an

FSD. (T-1) The fire chief or his/her designated representative provides consultation and design recommendations regarding firefighting operational requirements. The fire chief is not responsible for fire protection or life safety system designs. The fire chief coordinates on design drawings to signify for the fire department that firefighting operational recommendations have been incorporated. This coordination does not indicate acceptance or approval of the fire protection engineering design. (T-2)

3.3. Conflicting Criteria. If conflicts exist among criteria, UFC 3-600-01 takes precedence.

(T-0) (Note: “Use the most stringent requirement” does not apply). In cases where conflicts among criteria are not resolved by the technical guidance in UFC 3-600-01, request clarification from AFCEC/COS through the MAJCOM. (T-1) For overseas installations, where UFC and host nation fire protection engineering criteria conflict, the UFC criteria will apply unless an applicable international agreement requires use of host nation criteria.

Conflicts in the technical features standards and approvals used to comply with the protection requirements will apply the host nation equipment standards and approvals. Request specific clarification from AFCEC/COS for unique correlation of US and Host Nation codes and criteria. (T-1)

AFI32-10141 5 FEBRUARY 2015 7

3.4. Fire Safety Deficiency (FSD) Codes.

3.4.1. FSD I. FSD I includes missing fire protection systems or missing NFPA 101 features in any building or process. Any facility FSD which results from a failure to comply with the following is considered an FSD I: (T-1)

3.4.1.1. New Facilities. New facilities must meet the requirements specified in UFC

3-600-01, paragraph 1-3.2.1. (T-0) Such facilities shall not be considered as a complete and usable facility until such time as the deficiency is corrected. (T-2)

3.4.1.2. Modernized, Renovated, Repaired, Restored, Upgraded and Change-of-

Occupancy Facilities. These facilities must meet the requirements of UFC 3-600-01, paragraphs 1-3.2.2 thru 1-3.2.4. (T-0)

3.4.1.3. Existing Facilities. Existing facilities must meet the minimum requirements of NFPA 101 for existing occupancies (UFC 3-600-01, paragraph 1-3.1). (T-0)

3.4.1.4. Impairments. Impairments of fire safety features required for existing occupancies in accordance with NFPA 101 which are not corrected within 72 hours.

(T-1)

3.4.1.5. Other Deficiencies. Deficiencies in mission-priority facilities which impact mission continuity or generate a loss potential in excess of $5 million and have been evaluated and approved by the installation fire marshal. (T-2)

3.4.2. FSD II. FSD II includes deficiencies in existing fire protection systems or features in any building or process not covered by paragraph 3.4.1 of this instruction.

Any existing fire protection system/feature identified in UFC 3-600-02, O&M:

Inspection, Testing, and Maintenance of Fire Protection Systems, which is out of service or impaired so as to prevent automatic or manual (manual is applicable only if the system/feature is operated by manual activation) response to a fire event for more than 72 hours shall be considered an FSD II. (T-2)

3.4.3. FSD III. All other FSDs not covered by paragraphs 3.4.1 and 3.4.2 of this instuction are classified FSD IIIs. (T-2)

3.4.4. FSD Code Decision Matrix. Attachment 2 is a decision matrix to correctly classify FSDs for various situations.

4. Processing and Managing FSDs. These processes are not an alternative to the risk management (RM) analysis; rather, ORM is an integral part of the risk quantification necessary to processing and managing FSDs. ORM documentation should be part of the supporting information with any mitigation/corrective action plan or alternative/equivalency/exemption approval request. (T-2)

4.1. FSD I. FSD I indicates a deficiency with the greatest risk to life and mission continuity.

Facilities with an identified FSD I not being corrected through paragraph 4.4, “In-House

Work,” should not be occupied except in accordance with an approved corrective action plan which includes interim control measures. (T-2)

4.1.1. Corrective Action Plan. For an existing facility, a mitigation/corrective action plan shall be prepared by the facility user with the support of the fire emergency service flight, the engineering flight, the operations flight (as appropriate), and wing safety. (T-2)

8 AFI32-10141 5 FEBRUARY 2015

The plan shall specifically identify the level of occupancy and operations permitted pending the correction of the FSD I. (T-2) The wing commander shall approve the plan before forwarding it to the MAJCOM/A7 for informational purposes. (T-2)

4.1.2. Alternatives/Equivalencies. Requests for approval of alternative or equivalent methods to meet the intent of a criteria requirement must be submitted through the

MAJCOM to AFCEC/COS (see UFC 3-600-01) by the appropriate commander. (T-1)

Alternative equivalency requests should be submitted following the staff study process and format in Air Force Handbook (AFH) 33-337, Tongue and Quill. (T-2) Emphasis should be placed on explaining how the selected technical solution/process achieves the intent of the criteria requirement. (T-2)

4.1.3. Exemptions. Requests for permanent exemption to criteria must be submitted through the MAJCOM to AFCEC/COS (see UFC 3-600-01) by the appropriate commander. (T-1) Exemptions should be submitted following the staff study process and format in AFH 33-337. Emphasis should be placed on explaining how the increased mission continuity risk can be tolerated/assumed by the Air Force.

4.2. FSD II. FSD II indicates a significant risk to mission continuity and/or existing property capability. Facilities with an identified FSD II not being corrected through paragraph 4.4, “In-House Work,” should not be occupied unless interim control measures are in place. (T-2)

4.2.1. Corrective Action Plan. For an existing facility, a mitigation/corrective action plan shall be prepared by the facility user with the support of the fire emergency service flight, the engineering flight, the operations flight (as appropriate), and wing safety. (T-2)

The plan shall specifically identify the level of occupancy and operations permitted pending the correction of the FSD II. (T-2) The wing commander (or other appropriate commander) shall approve the plan before forwarding it to the MAJCOM/A7 for information. (T-2)

4.2.2. Repair or Correction of Fire Protection System Impairments/Feature

Performance.

4.2.2.1. Impairments affecting the performance of installed fire protection features shall be corrected immediately after identification using the highest priority in the appropriate repair work identification and management system. (T-1)

4.2.2.2. When the impairment will exist for more than 72 hours, an FSD II is established and the installation authorities for fire system/feature maintenance and fire emergency services shall collaborate with the facility/area user to jointly develop written control/mitigation measures. (T-2) These measures, to the maximum degree possible, shall ensure personnel safety as well as mission continuity (and, as appropriate, high-value asset protection) until the impairment is corrected. The jointly developed package must also identify the remaining mission risk exposure. In the absence of interim control measures, the facility shall be evacuated or operations stopped. Implementation of interim control measures are not considered a permanent fix and shall not reduce the priority required to correct the impairment. (T-2)

AFI32-10141 5 FEBRUARY 2015 9

4.2.2.3. The maintenance activity must inform the installation and/or operational commanders of new impairments not corrected within 72 hours, the jointly developed interim control measures being recommended, and the remaining mission risk exposure. (T-2)

4.2.2.4. The maintenance activity must regularly inform the installation and/or operational commanders, not less than annually, on the status of system impairments, in-place compensatory measures, projected corrective actions, and corrective actions completed since the last report. (T-2)

4.2.3. Alternatives/Equivalences. Requests for approval of alternative or equivalent methods to meet the intent of a criteria requirement must be submitted through the

MAJCOM to HQ AFCEC/COS by the appropriate commander. (T-1)

Alternative/equivalency requests should be submitted following the staff study process and format in AFH 33-337. (T-2) Emphasis should be placed on explaining how the selected technical solution/process achieves the intent of the criteria requirement. (T-2)

4.2.4. Exemptions. Requests for permanent exemption to criteria must be submitted through the MAJCOM to HQ AFCEC/COS by the appropriate commander. (T-1)

Exemptions should be submitted following the staff study process and format in AFH 33-

337. (T-2) Emphasis should be placed on explaining how the increased mission continuity risk can be tolerated/assumed by the Air Force. (T-2)

4.3. FSD III. FSD III indicates a deficiency with the least risk to life, mission continuity and/or existing property capability. Facilities with an identified FSD III may be routinely occupied. FSD IIIs are typically identified, tracked, and corrected during scheduled facility renovation or remodeling projects. (T-2)

4.4. In-House Work. Deficiencies identified during the fire prevention inspection process

(AFI 322001) or the reoccurring maintenance and repair process (UFC 3-601-02) are initially considered for correction through the in-service work program. (T-1) If CEO approves the work to be accomplished in-house, then the CE shops will accomplish the work and fill out the appropriate Civil Engineering Operations database automated records.

4.4.1. Corrective Action Plans for In-Service Work. The approved/funded job order/work order represents the installation’s commitment of resources to the corrective action and will be considered the corrective action plan required under paragraph 4.1.1 or

4.2.1 of this instruction. (T-1) No additional approval is required outside the in-service work plan process. (T-1)

4.4.2. Rating FSD and Other Work Requirements Combined in a Single Work

Package. Deficiency corrective actions are often combined with other maintenance and repair tasks in a single in-service work package. (T-2) Such combined work packages will be coded as an FSD correction package only if more than 50 percent of the combined package cost is directly related to the FSD correction work. (T-2)

4.5. New Project. Regardless of funding source, when a new project, is required to correct an identified FSD, the information will be transferred to the Engineering Flight and the documentation that was entered into the Civil Engineering Operations database must be reentered into the Civil Engineering Project Management database. (T-2) Note: For accurate tracking and FSD management, the FSD fields must also be reentered into the Civil

10 AFI32-10141 5 FEBRUARY 2015

Engineering Project Management database. From this point forward, the project is managed like any other design project.

4.5.1. Rating FSD and Other Work Requirements Combined in a Single

Project. Projects that include a scope of work greater than required for correction of identified FSDs will not classify the entire project as an FSD correction project unless at least 50 percent of the programmed funding is specifically intended to address correction of the FSDs. (T-2) For example, a building renovation project programmed for $100K that includes one FSD correction requirement for $2K would not include an overall FSD code rating in the project scoring process.

4.5.2. Rating Multiple FSD Requirements in a Single Project. Projects that include correction of multiple FSDs representing at least 50 percent of the programmed funding will reflect the least severe code found in those multiple FSDs.(T-2) For example, a project that combines one FSD I (10 percent of the programmed funding), four FSD IIs

(30 percent), two FSD IIIs (15 percent), and some non-FSD work (45 percent) would be rated as an overall FSD III project in the project scoring process. If any single FSD code accounts for at least 50% of the total programmed costs the project will reflect the code regardless of the severity of other requirements.(T-2) For example, a project that combines one FSD I (10 percent of the programmed funding), four FSD IIs (60 percent), two FSD IIIs (15 percent), and some non-FSD work (15 percent) would be rated as an overall FSD II project in the project scoring process.

4.6. Fire Protection Engineering Analysis. UFC 3-600-01, paragraph 1-4, requires every design to receive a fire protection design analysis; paragraph 1-5 requires this analysis be conducted by a qualified fire protection engineer for major projects. (T-0) In some cases the results of the analysis is ―no analysis is required. Attachment 3 provides a matrix describing when an analysis is required and what type of analysis is required.

4.6.1. Phased projects will be considered cumulatively when determining whether or not the project requires an analysis in accordance with UFC 3-600-01, paragraph 1-4 or 1-5.

(T-1)

4.6.2. Phased projects will be considered cumulatively when determining the percentage of the facility involved and the cost of the work versus the replacement cost of the facility. (T-1)

4.6.3. The initial analysis of phased projects will evaluate all phases together and a comprehensive documentation package will be developed and follow all phases through the design, construction, maintenance, or repair process. (T-1)

5. Authority Having Jurisdiction (AHJ). The office responsible to approve exemptions and plans and interpret technical criteria issues varies depending on the issue and its technical complexity. (T-1)

5.1. Military Child Care Facilities. United States Code (USC) Title 10, Section 1794, Child Abuse Prevention and Safety at Facilities, requires immediate correction of life threatening fire safety deficiencies at each child development and youth program facility.

Correct life threatening fire safety deficiencies at each child development and youth program facility immediately. Correct non-life threatening fire safety violations at a child development or youth program facility within 90-days or close the facility until the violation

AFI32-10141 5 FEBRUARY 2015 11

is corrected. An exemption to correct a non-life threatening deficiency may be available to authorize the facility to remain open in a case in which the violation cannot reasonably be remedied within that 90-day period or in which major facility reconstruction is required.

Note: Exemptions as used in Title 10 include both permanent and expiring. (T-0)

JUDITH A. FEDDER, Lieutenant General, USAF

DCS/Installations, Logistics & Mission Support

12 AFI32-10141 5 FEBRUARY 2015

Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

10 USC Sec. 1794, Child Abuse Prevention and Safety at Facilities, 15 October 2014

AFH 33-337, Tongue and Quill, 1 August 2004

AFI 32-1032, Planning and Programming Appropriated Funded Maintenance, Repair, and

Construction Projects, 17 October 2014

AFI 32-2001, Fire Emergency Services Program (FES), 27 February 2014

AFI 91-202, The U.S. Air Force Mishap Prevention Program, 5 Aug 2011

AFI 91-301, Air Force Occupational and Environmental Safety, Fire Protection and Health

(AFOSH) Program, 1 June 1996 (Rescinded)

AFMAN 33-363, Management of Records, 1 March 2008

AFPD 32-10, Installations and Facilities, 4 March 2010

AFPD 32-20, Fire Emergency Services, 21 Jun 2012

ETL 00-07, Fire Protection Engineering Criteria – Correlation of US and Host Nation Codes and Criteria, 10 May 2000

UFC 3-600-01, Fire Protection Engineering for Facilities, Change 3, 1 March 2013

UFC 3-601-02, O&M, Inspection, Testing, and Maintenance of Fire Protection Systems, 8 Sept

DODI 6055.06, DoD Fire and Emergency Services (F&ES) Program, 21 December 2006

OPM General Schedule Qualification Standards, Fire Protection Engineering Series, 0804

AWWA Manual 14, Recommended Practice for Backflow Prevention and Cross-Connection

Control, 2004

AWWA Manual 31, Distribution System Requirements for Fire Protection, Fourth Edition, 2008

NFPA 101: Life Safety Code®, 2012

Adopted Forms

AF IMT 332, Base Civil Engineer Work Request

AF…