Attachment 7 TO-00-33A-1001.PDF

T.O. 00-33A-1001

TECHNICAL MANUAL

METHODS AND PROCEDURES

GENERAL CYBER DEFENSE OPERATIONS

ACTIVITIES MANAGEMENT PROCEDURES AND PRACTICE REQUIREMENTS

THIS PUBLICATION SUPERSEDES T.O. 00-33A-1001 DATED 15 Apr 2021.

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative or operational use, 23 April 2009. Refer other requests for this document to HAF A2/6FC 1D7XX Career Field Manager. Submit recommended changes to appropriate MAJCOM 1D7 functional manager who will then forward to the appropriate HAF A2/6FC 1D71XX Career Field Manager, using Air Force Technical Order (AFTO) Form 22, Technical Manual (TM) Change Recommendation and Reply, according to T.O. 00-5-1.

Published under authority of the Secretary of the Air Force

1 Nov 2021

Attachment 7

LIST OF EFFECTIVE PAGES

Dates of issue for original:

Original.................... 0 ............1 Nov 2021

(TOTAL NUMBER OF PAGES IN THIS MANUAL IS 148)

Changes:

Chapter 2: AEF Reporting Tool has been replaced by the Deliberate and Crisis Action Planning and Execution Segments (DCAPES) and Defense Readiness Reporting System (DRRS).

Chapter 4: Replaced NC3 Center with AFGSC

Chapter 5: Misc changes

Chapter 11: Misc changes

Throughout: 3DXXX Cyberspace Support career fields changed to 1D7XX Cyber Defense Operations career fields. Commanders

Policy Letter removed, see AFI 33-360.

Table of Contents

INTRODUCTION

CHAPTER 1 OVERVIEW

CHAPTER 2 QUALITY ASSURANCE PROGRAM

CHAPTER 3 CONTROL OF PRODUCTION

CHAPTER 4 NUCLEAR COMMAND, CONTROL AND COMMUNICATIONS EQUIPMENT (NC3E) MANAGEMENT

CHAPTER 5 EQUIPMENT/SYSTEM INSPECTION POLICY

CHAPTER 6 CORROSION PREVENTION AND CONTROL PROGRAM (CPCP)/ELECTROSTATIC DISCHARGE (ESD)

CHAPTER 7 HISTORICAL RECORD MANAGEMENT

CHAPTER 8 LIFE CYCLE MANAGEMENT

CHAPTER 9 MATERIAL MANAGEMENT

CHAPTER 10 PUBLICATIONS PROGRAMS

CHAPTER 11 CABLE AND ANTENNA MAINTENANCE

CHAPTER 12 TOOL & TMDE MANAGEMENT

CHAPTER 13 PERFORMANCE METRICS AND ALGORITHMS FOR COMMUNICATIONS/CYBER

CHAPTER 14 CENTRALIZED REPAIR ACTIVITIES (CRA)

CHAPTER 15 SYSTEM MANAGERS

CHAPTER 16 SPECIALIZED COMMUNICATIONS TEAMS (SCT)

CHAPTER 17 HOW TO

CHAPTER 18 PROJECTS AND REQUIREMENTS FUNCTION

CHAPTER 19 PLANS, PLANNING, AND AGREEMENTS

APPENDIX A GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

APPENDIX B NUCLEAR COMMAND, CONTROL AND COMMUNICATIONS EQUIPMENT (NC3E)

APPENDIX C SAMPLING PLAN

APPENDIX D COMMUNICATIONS PLAN

APPENDIX E ADDITIONAL TOOL MANAGEMENT INFORMATION

APPENDIX F PLANS AND IMPLEMENTATION PROGRAMS

LIST OF ILLUSTRATIONS

Number Title

17-1 General TCTO Routing

19.7.1 Project Initiation Flowchart

19.7.2 Downward Direct Program Flowchart

19.7.3 Project Planning Flowchart

19.7.4 Project Execution Flowchart

19.7.5 Project Acceptance Flowchart

20.6.1 Wing Directed Plans Flowchart

20.6.2 Support Agreement Flowchart

20.6.3 MOU/MOA Flowchart

20.6.4 Service Level Agreement Flowchart

LIST OF TABLES

Number Title

2-1 Personnel Evaluations Task Deficiency Codes

2-2 Personnel Evaluation Task Result Matrix

2-3 Equipment Evaluations Task Deficiency Codes

2-4 Equipment Evaluation Result Matrix

5-1 Inspection Deviations Allowances

C-1 Sample Sizes

INTRODUCTION

1. PURPOSE.

The purpose of this manual is to establish procedures for the management of communications, cyberspace, information technology and space (CCITS) equipment (see paragraph 1.3.2).

2. USE OF THIS MANUAL.

The table of contents indicates chapter, paragraph, title, and page number to facilitate location of information. Illustrations, tables, and diagrams, when applicable, are located throughout the publication to supplement the text material. A list of illustrations and a list of tables indicate the number, title, and location. Abbreviations, phrases, and words which need clarification are spelled out and explained the first time and again in the glossary of reference and supporting information.

3. DEFINITIONS.

The word SHALL is used to express a provision that is binding. The words SHOULD and MAY are used when it is necessary to express non-mandatory provisions. WILL may be used to express a mandatory declaration of purpose or when it is necessary to express a future event.

4. NOTES.

Notes which appear in this manual are defined as follows:

NOTE

An essential operating or maintenance procedure, condition, or statement which must be highlighted.

5. ABBREVIATIONS.

ACS Air Control Squadron

AFCFM Air Force Career Field Manager

AFCQCC Air Force Communications Quality Control Checklist

AFEMS Air Force Equipment Management System

AFETS Air Force Engineering Technical Service

AFI Air Force Instruction

AFIN Air Force Information Network

AFJQS Air Force Job Qualification Standard

AFMAN Air Force Manual

AFMC Air Force Materiel Command

AFNet SOP Air Force Network Standard Operating Procedure

AFNetOps Air Force Network Operations

AFPD Air Force Policy Directive

AFQTP Air Force Qualification Training Package

AFRC Air Force Reserve Command

AFRIMS AF Record Information Management System

AFSATCOM Air Force Satellite Communications

AFSC Air Force Specialty Code

AFTO Air Force Technical Order AHE Automated History Event

AIM Asset Inventory Management

AIS Automated Information System

ALC Air Logistics Center

ANG Air National Guard AOC Air Operations Center

AOCI Air Operations Certification Inspection

AOR Area of Responsibility

AS Allowance Standard

ATS Automated Test Sets

AWP Awaiting Parts

BCE Base Civil Engineering

CA/CRL Custodian Authorization/Custody Receipt Listing Design

CADD Computer-Aided Drawing and Design

CBCS Combat Communications Squadron

CCITS Communication/Cyberspace/Information Technology/Space

CCO Cyber Control Officer CDC Career Development Course

CDE Corrected During Evaluation

CD-ROM Compact Disk-Read Only Memory

C-E Communications-Electronics

CEE Core Equipment Evaluation CEG Cyberspace Engineering Group

CESR Communications-Electronics Schedule Review

CFETP Career Field Education and Training Plan

CFP Communications Focal Point

CIPS Cyberspace Infrastructure Planning System CITS Combat Information Transport System

CMDS Communications Mission Data Set

CN Control Number

COR Contracting Office Representative

COS Chief Of Supply

COTS Commercial-Off-The-Shelf

CPCP Corrosion Prevention and Control Program

CPSD Cryptologic Systems Division

CRA Centralized Repair Activity

CRB Configuration Review Board

CSI Cyber Systems Integrators

CSO Communications and Information Systems Officer

CTO Cyber Tasking Order

CUT Cross-Utilization Training

CVC Cyberspace Infrastructure Planning System Visualization Component

CWC Complies With Comments DBM Database Manager

DCAPES Deliberate and Crisis Action Planning and Execution Segments

DCGS Distributed Common Ground System

DIFM Due In From Maintenance DISA Defense Information System Agency

DISN Defense Information System Network

DLADS Defense Logistics Agency Disposition Services

DoD Department of Defense

DoDAF Department of Defense Architecture Framework

DPEM Depot Purchased Equipment Maintenance

DRRS Defense Readiness Reporting System

DRU Direct Reporting Unit DSN Defense Switched Network

ECO Equipment Control Officer

EDSC Engineering Data Service Center

EE Equipment Evaluation

EI Engineering Installation EIL Equipment Inventory Listing

EIP Equipment Inoperable for Parts

EIS Engineering Installation Squadron

ESD Electrostatic Discharge ESR Equipment Status Reporting

ETRO Estimated Time of Return to Operation

FAD Force Activity Designator FCO Field Change Order

FMC Fully Mission Capable

FOA Field Operating Agency

FOD Foreign Object Damage

FOUO For Official Use Only

GIO Geographic Integration Office GIS Geographic Information Systems

GOTS Government-Off-The-Shelf

GPS Global Positioning System

GSA General Service Administration HQ Headquarters

HQ CCC Headquarters Cyberspace Capabilities Center

ICAP Integrated Communications Access Package

IG Inspector General

IIR Interim Installation Record

IMDS Integrated Maintenance Data System

ITN Inter-Network Transfer Node

ITP Individual Training Plan

JCN Job Control Number

JDD Job Data Documentation

JDRS Joint Discrepancy Reporting System JP Joint Publication

LAN Local Area Network LC Lead Command

LCQCC Local Communications Quality Control Checklist

LCSP Life Cycle Sustainment Plan

LDL Low Density Level

LIMS-EV Logistics, Installation and Mission Support-Enterprise View LMR Land Mobile Radio

LOM List of Materials

LPS Local Page Supplement

LRS Logistics Readiness Squadron

LRU Line Replaceable Unit LSC Logistics Support Center

LWC Local Work Cards

MAJCOM Major Command

MDC Maintenance Data Collection

MDS Mission Design Series MDT Mean Downtime

MEO Most Efficient Organization

MFM MAJCOM Functional Manager

MICAP Mission Capable

MICT Management Internal Control Toolkit

MIL Master Inventory List

MOA Memorandum of Agreement MOU Memorandum of Understanding

MRSP Mobility Readiness Spares Package

MRT Mean Repair Time

MRT Mission Readiness Training

MSM MAJCOM System Manager

MTBCF Mean Time Between Critical Failure

MTBM Mean Time Between Maintenance

MTO Maintenance Tasking Order

NATO North Atlantic Treaty Organization

NC3 Nuclear Command, Control and Communications

NC3E Nuclear Command, Control and Communicatioins Equipment

NCOIC Non-Commissioned Officer-In-Charge

NCPE Nuclear Continuation Personnel Evaluation

NIC Not in Compliance

NIST National Institute of Standards and Technology

NMC Not Mission Capable

NMCMU Not Mission Capable Maintenance Event Unscheduled

NOSC Network Operations Support Center NOTAM Notice to Airmen

NRTS Not Repairable This Station

NSA National Security Agency

NSN National Stock Number

OCCR Organizational Cost Center Record OEE Other/Ancillary Equipment Evaluation

OIL Open Incident Listing

OJT On-The-Job-Training

OPLAN Operations Plan OPORD Operational Order

OPREP Operational Event/Incident Report

OR Operational Readiness

OSS Operations Support Squadron

OT&E Operational Test and Evaluation OWC Owning Work Center

P&I Planning & Implementation

PAD Program Action Directive

PDM Programmed Depot Maintenance PE Personnel Evaluation

PEP Performance Evaluation Program

PFMR Project Fund Management Record

PHS&T Package, Handling Storage and Transportation

PI Periodic Inspection PMC Partially Mission Capable

PMI Preventive Maintenance Inspection POC Point of Contact

PSA Project Support Agreement

PWC Production Work Center

PWS Performance-Based Work Statement

QA Quality Assurance

QAR Quality Assurance Representative

QDR Quality Deficiency Report

RDS Records Disposition Schedule

RM&A Reliability, Maintainability and Availability

RPA Remote Piloted Aircraft

RSP Readiness Spares Package

SACCS Strategic Command and Control System

SAF Secretary of the Air Force

SCT Specialized Communications Team

SEE Special Equipment Evaluation

SITREPS Situational Report SLA Service Level Agreement

SM System Manager

SME Subject Matter Expert

SMR Source, Maintenance, and Recoverability Code SOO Statement of Objective

SOR Source of Repair

SOW Statement of Work

SPE Special Personnel Evaluation SPECAT Special Category

SPO System Program Office

SRD Standard Reporting Designator

TAS Tool Accountability System

TBA Training Business Area TCI Time Change Item

TCNO Time Compliance Network Order

TCTO Time Compliance Technical Order

TDC Theater Deployable Communications

TM Technical Manual

TMS Telephone Management System

TO Technical Order

TODO Technical Order Distribution Office TRM Turn-Around Monitor

U&TW Utilization and Training Workshop

UDM Unit Deployment Manager

UHF Ultra High Frequency UMD Unit Manning Document

UND Urgency of Need Designator

UR Utilization Rate

UTC Unit Type Code

UTM Unit Training Manager WCE Work Center Event

WRM War Reserves Material

WS3 Weapons Storage and Security System

WUC Work Unit Code

6. LIST OF RELATED PUBLICATIONS.

These publications contain information in support of this technical manual and are required, if applicable, to accomplish the prescribed maintenance.

List of Related Publications

Publication Number Publication Title

AFCSM 21-556, Volume 2 Integrated Maintenance Data System (IMDS), Introduction to IMDS CDB

Software User Manual

AFCSM 21-560, Volume 2 Integrated Maintenance Data System (IMDS) C-E Equipment Status and Inventory Reporting Software User Manual

AFCSM 21-561, Volume 2 Integrated Maintenance Data System (IMDS), Maintenance Events, Software User Manual AFCSM 21-568, Volume 2 Integrated Maintenance Data System (IMDS), Time Compliance Technical Orders

(TCTO) Software User Manual

AFCSM 21-567, Volume 2 Integrated Maintenance Data Systems (IMDS) Equipment/Personnel Transfer

AFI 10-403 Deployment Planning and Execution AFI 10-601 Operational Capabilities Requirements Development

AFI 16-1404 Air Force Information Security Program

AFI 17-101 Risk Management Framework for Air Force Information Technology

AFI 17-130 Cybersecurity Program Management

AFI 17-220 Spectrum Management AFI 21-101 Aircraft and Equipment Maintenance Management

AFI 21-103 Equipment Inventory Status and Utilization Reporting

AFI 25-201 Intra-Service, Intra-Agency, and Inter-Agency Support Agreements Procedures

AFMAN 32-1065 Grounding Systems

AFI 32-9005 Real Property Accountability and Reporting

AFI 33-322 Records Management Program

AFI 33-360 Publications and Forms Management

AFI 63-101_20-101 Integrated Lifecycle Management AFI 64-102 Operational Contracting Program

AFI 65-501 Economic Analysis

AFI 90-201 The Air Force Inspection System

AFI 90-821 Hazard Communications (HAZCOM) AFI 99-103 Capabilities-Based Test and Evaluation

AFMAN 10-206 Operational Reporting

AFMAN 17-204 Air Force On-the-Job Training Products for Cyber Defense Operations Enlisted

Specialty Training

AFMAN 17-1203 Information Technology Asset Management

AFMAN 17-1301 Computer Security (COMPUSEC) DAFMAN 23-122 Materiel Management Procedures

AFMAN 91-203 Air Force Occupational Safety, Fire, and Health Standards

DAFPAM 63-128 Integrated Life Cycle Management DAFPD 10-9 Lead Command/Lead Agent Designation and Responsibilities for Weapon Systems, Non-Weapon Systems, and Activities

DISA Area Regulations 195-Series Defense Switched Network (DSN) Evaluation Program

DoDI 5000.2 Operation of the Defense Acquisition System

DoDM 5200.01 Vol 4 DoD Information Security Program: Controlled Unclassified Information (CUI)

DoD 5220.22-R Industrial Security Regulation

DoD 5400.7- R/AFMAN 33-302A Freedom of Information Act Program

JP 1-02 DoD Dictionary of Military and Associated Terms

00-5-1 AF Technical Order System 00-5-15 Air Force Time Compliance Technical Order Process

00-20-1 Aerospace Equipment Maintenance Inspection, Documentation, Policies, and Procedures

00-20-2 Maintenance Data Documentation

00-20-3 Maintenance Processing of Reparable Property and the Repair

Cycle Asset Control System

00-20-14 AF Metrology and Calibration Program

00-25-108 Communication- Electronics (C-E) Depot Support

00-25-195 Source, Maintenance, and Recoverability Coding of Air Force

Weapons, Systems, and Equipment

00-25-234 General Shop Practice Requirements for the Repair, Maintenance and

Test of Electrical Equipment

00-33A-1100 AFNet Operational Change Management Process

00-33A-1109 Air Force Information Network Vulnerability Management

00-33D-2002 Cyberspace Engineering Installation Activities Management 00-33D-3004 Managing Cable and Antenna with the Cyberspace Infrastructure Planning System

(CIPS) Visualization Component (CVC) 00-33D-3004-2 Maintaining Cyber and Transport Records with the Cyberspace Infrastructure Planning

System Volume 2

00-35D-2 Electronic Set Inventory Checklist for General Communication

Electronic (CE) Equipment

00-35D-54 USAF Deficiency Reporting, Investigation, and Resolution 1-1-700 Corrosion Prevention and Control Ground Communications - Electronic

Equipment (C-E)

31S5-4-ETOOL-1-WA-1 ETool Setup and Management

32-1-101 Use and Care of Hand Tools and Measuring Tools (TM 9-

243)

33-1-27 Logistics Support of Precision Measurement Tools

33-1-32 General Instructions Input Power Wiring of Elec/Elec

Support Equipment

33K-1-100-1 Technical Manual-TMDE Calibration Notes for Maintenance

Data Collection Codes and Calibration Measurement

Summaries

7. LIST OF APPLICABLE TIME COMPLIANCE TECHNICAL ORDERS (TCTO).

None.

8. IMPROVEMENT REPORTS.

Recommended changes to this manual shall be submitted through ETIMS or on an AFTO 22 in accordance with T.O. 00-5-1.

CHAPTER 1

OVERVIEW

1.1 PURPOSE.

The purpose of this manual is to establish procedures for the management of communications, cyberspace, information technology and space (CCITS) equipment (see paragraph 1.3.2).

1.2 SCOPE.

This technical order applies to all 1D7XX Cyber Defense Operations career fields in USAF units working on or supporting CCITS equipment unless exempted by the appropriate career field managers. It also applies to any other Air Force Specialty Code

(AFSC) working on or supporting CCITS equipment in USAF units unless exempted by the appropriate career field functional managers. It also applies to any organization with production responsibilities for CCITS equipment and/or processes in USAF units unless exempted by the appropriate AF-level functional manager. This includes all Air Force (AF) and Space Force (SF) military and civilian personnel, members of the Air Force Reserve Command (AFRC), Air National Guard (ANG), and AF contractors working in USAF units. The procedures and practices listed in this manual are established by Department of Defense

(DoD), Air Force Instructions (AFIs), technical order, and other guidance.

Units using AF contractors will follow guidance provided in paragraph 1.5, Contract Maintenance.

2MXXX personnel maintaining missile communications systems will follow guidance in the AFI 21-2XX series.

For all 1D7XX personnel or Contractor Military Equivalents (CME) aligned to other entities (i.e., National Security

Agency (NSA), Defense Information Systems Agency (DISA), Joint Communications Support Element (JCSE), etc.) need to identify any risks associated to not fully performing programs outlined within this document and adhering to the assigned entities directives/guidance. Use the AF Form 4437, Deliberate Risk Assessment

Worksheet, per AFI 90-802, Risk Management and AFPAM 90-803, Risk Management (RM) Guidelines and Tools.

Commanders use the results from the risk management (RM) process to establish and maintain their programs.

Commanders will document their program’s roles, responsibilities, structure, and local procedures in an operating instruction, standard operating procedure, or memo for record following guidance in AFI 33-360, Publication and

Forms Management. File completed AF Forms 4437 according to disposition instructions.

For items not covered by the AF Form 4437, route waiver requests according to paragraph 17.9.

The procedures and practices listed in this manual are available, but not directed, for Guardians and Airmen working in US Space Force (USSF) units. Direct applicability and use questions to the USSF Enlisted Cyber Functional

Manager.

1.3 DEFINITIONS.

1.3.1 Qualified Personnel. Refers to those individuals with the technical skills required to perform various functions relating to communication/cyber equipment/system corrective, inspection, production, and preventive maintenance activities. An individual is considered “qualified” if that individual has been trained to the level necessary to perform specific activities or functions under this technical order. Technical qualifications will vary by function being performed and technical competency required. For example, an individual qualified to troubleshoot a system will require more specialty/technical training than an individual qualified to remove and install a part. An individual qualified to remove and install a part will require more specialty/technical training than a custodian who conducts operational inspections and assessments.

1.3.2 (CCITS) Equipment CCITS systems and equipment are defined in AFI 21-103, Equipment Inventory, Status and Utilization

Reporting, and CCITS includes both fixed and deployable assets.

1.3.2.1 Mobility Equipment. Any item/asset that specifically supports deployable communications/cyber equipment/systems.

These items/assets include but are not limited to tents, poles, mobility boxes, tables, chairs, and other non-electronic items.

Generally, these items/assets are not tracked in an AF approved accounting system or contained within non-airborne Mobility

Readiness Spares Packages (MRSP) or considered War Reserve Material (WRM). These items will be tracked locally.

1.3.2.2 Non-airborne Readiness Spares Package (RSP). Items other than aircraft, such as communication electronics, vehicles, and bare base systems, that are a transportable set of spares and repair parts required to support planned wartime or contingency operations for a specified period of time pending resupply. RSP is also referred to as MRSP.

1.3.2.3 War Reserve Materiel (WRM). The pre-stocked portion of the total wartime requirement. WRM is materiel required, in addition to mobility equipment and peace time stock, to support wartime activities reflected in the WMP-1, USAF War and

Mobilization Plan. WRM represents that part of the war requirement needed in addition to RSP and peace time stock in order to sustain wartime operations until industrial production can meet total wartime needs.

1.3.3 Test Equipment. Any device used to maintain, evaluate, measure, calibrate, diagnose or otherwise examine materials, supplies, networks, equipment, and systems to identify or isolate actual or potential malfunction/discrepancies/deficiencies or decide if they meet operational specification established in technical publications. Some examples of test equipment are fiber testers, cable testers, spectrum analyzers, etc. See T.O. 00-20-14, AF Metrology and Calibration Program, for details.

1.4 RESPONSIBILITIES.

Responsibility for procedures outlined in this technical order will be assigned by the organization commander or equivalent.

Inspection, preventive maintenance, servicing, opening, repair or replacement of communications/cyber equipment/systems will be accomplished only by qualified personnel.

NOTE

If access to classified material by a contractor is required to perform tasks/functions for contract performance, then the service provisions of DoD 5220.22-R, Industrial Security Regulation, apply.

1.4.1 Applicability for Deployable Units. All units with a deployable communication/cyber mission and deployable Unit Type

Codes (UTCs), such as Combat Communications Squadrons (CBCS), Air Control Squadrons (ACS), Engineering Installation

Squadrons (EIS), etc., will apply and perform the management policies prescribed within this technical order unless otherwise specified. Regardless of the unit’s organizational structure, the principles of management will be followed to ensure efficient and effective activities in the deployed environment.

1.4.1.1 Units with deployable missions will designate a deployed UTC Chief prior to deployment and support management functions and activities. The appointed UTC Chief managing functions structured by UTC will ensure these functions adhere to the principles of a production work center.

1.4.1.2 Managers at all levels must leverage opportunities to compensate for the inefficiencies of contingency operations. In-garrison and predeployment planning are critical to ensuring equipment and personnel readiness and availability when tasked for contingency operations.

1.4.1.3 The deployed flight commander/chief is responsible for overall management, while equipment/UTC supervisors are responsible for ensuring their personnel comply with established guidance. Deployed maintenance management focuses on delivering the required operational capabilities while limiting operational interruptions.

1.4.2 Training Tracking and Documentation. All 1D7XX Cyber Defense Operations personnel training will be tracked in the

Training Business Area (TBA), except for ancillary training. Ancillary training will be tracked in my-Learning or Integrated

Maintenance Data System (IMDS) when my-Learning does not have the required course, unless it is required by a higher AF guidance to be tracked in some other training database. Cross-Utilization Training (CUT) will be used to facilitate training of individuals in one AFSC on tasks of another AFSC if not previously qualified. CUT training will be documented in the individuals’ training records in TBA.

NOTE

Cyber Defense Operations personnel will utilize the 1D7XX CFETP as comprehensive education and training documents that identifies life cycle education and training requirements, training support resources and minimum core task requirements for their specialty.

Non-Cyber Defense Operations AFSCs will use appropriate CFETP documentation and/or Automated Information

System (AIS).

AFRC and ANG are authorized to track ancillary training using ARCNet/ATMT.

1.4.3 Mission Readiness Training (MRT) MRT courses are owned, managed & funded by AETC. Units must be involved with the MRT process and ensure they document their training requirements. Non-MRT courses: Courses owned by organizations other than AETC and funded by the owning organization or by unit funds. See para 17.11 for more on MRT process and resources.

1.5 CONTRACT MAINTENANCE.

This section identifies the basic responsibilities for managing Most Efficient Organization (MEO) or contract maintenance.

1.5.1 Compliance. Laws, executive orders, regulation, instructions and technical orders will be executed by the government unless waived by appropriate authority. When the government solicits services via contract, some requirements may be excluded from the

Performance-Based Work Statement (PWS) or Statement of Work (SOW) due to cost/affordability. Requirements excluded from the PWS or SOW will be performed by the government.

1.5.1.1 When maintenance management responsibilities are required of a contractor, they must be specifically identified in the

PWS. Managers will base PWS requirements on existing maintenance policy. The intent and philosophy of organic maintenance processes must be carefully considered and included when appropriate. Contract maintenance is not automatically exempt from standard logistics processes. For example, the requirement to document maintenance in an AF-approved Automated Information

System (AIS) must be included in the PWS. As a minimum, PWSs shall have:

a. Contractor Maintenance Data Collection: Enter systems and component failure according to T.O. 00-20-2, Maintenance Data Documentation; Material Consumption according to T.O. 00-20-3, Maintenance Processing of Repairable Property and Repair Cycle Asset Control System; and Time Compliance Technical Order (TCTO) reporting requirements according to T.O. 00-5-15, Air Force Time Compliance Technical Order Process, in

PWSs. Cite appropriate data items and include collecting TCTO and reparable processing data in contracts.

Contract instructions call out the time and place to turn in data. Specify if the contractor provides complete source documents and forms or automated products.

b. System restoral priorities.

c. Procedures to maintain configuration control.

d. Procedures to document historical records if not using an AF automated information system.

1.5.2 Contract Surveillance Programs/Contracting Office Representative (COR). Accomplish contract maintenance surveillance program duties according to procurement guidelines and command directives. When requested by the procurement office, the commander/flight commander/chief provides a qualified Contracting Office Representative (COR) for surveillance purposes. Surveillance programs may vary depending on the scope of the contract and directions of the procurement office. Air

Force personnel shall not give any direction to contractors thus changing the contract.

1.5.3 Contract Rules and Assistance. Only contracting officers are authorized to enter into or change a contract, Performance-

Based Work Statement (PWS) or Statement of Work (SOW). Air Force personnel do not give any directions or instructions to contractors or take any other action that could form the basis for a contractual claim. Direct problems with contract performance, contract changes or interpretation to the responsible contracting officer, administrative contracting officer or COR for resolution.

Contractual assistance may be used to satisfy a wide variety of requirements ranging from minor one-time repairs to operation and maintenance of complete systems. For more information see AFI 64-102 and AFPD 64-1.

a. Contract maintenance data collection (MDC) for AFIN Units: Contracts must include MDC methods that accurately capture maintenance actions on AFIN systems/equipment to include; unscheduled maintenance, preventative maintenance, Time Compliance Technical Order (TCTO), Time Compliance Network Order

(TCNO), Maintenance Tasking Order (MTO), Cyber Control Order (CCO) and Cyber Tasking Order (CTO) implementation on AFIN systems/equipment. All preventive maintenance and TCTOs must be tracked in an AF approved AIS. All unscheduled maintenance, TCNO, MTO, CCO, and CTOs may be tracked in the AIS directed by the Program Office, such as AFNetOps Compliance Tracker for AFIN, EITSM (Remedy) or IMDS. Units are responsible for successfully demonstrating compliant MTO implementation on each end item.

b. Identify minimum historical documentation requirements for AFIN units.

Suggested minimum requirements:

• Facility “as is” physical configuration. To include location/nomenclature/IDs of racks, UPS, Power

Panels, Signal Panels, etc.

• Facility cabling diagrams and rack interconnections

• Location of facility grounds and diagram of grounding grid if applicable

• Major maintenance actions on any end item: Installation, removal, replacement, TCTO completion, etc.

1.5.4 Impact on Wartime Capabilities. Consider contract maintenance on a planned and selective basis; however, wartime capability may not be compromised by excessive use of this resource. Check with appropriate MAJCOM managers to ensure local contract efforts do not erode command wartime capabilities.

CHAPTER 2

QUALITY ASSURANCE PROGRAM

2.1 INTRODUCTION.

The Quality Assurance (QA) program ensures that a program, function, process, equipment, system, end item or service are of the type and quality to meet/or exceed mission requirements. The QA program enhances mission accomplishment within the confines of public law, DoD/AF policy and guidance or technical orders. QA empowers commanders to actively manage mission risk at the appropriate level.

NOTE

Some organizations follow other third-party evaluation programs. For example, this QA program is different than the Engineering Installation Quality Assurance Program directed in T.O. 00-33D-

2002, Cyberspace Engineering Installation Activities Management. Unit Commanders will review all published guidance and will document how they are meeting the intent of third-party evaluation programs and the core duties, functions, and program outlined within this chapter through the applicable MAJCOM/A6, or HAF A2/6FC 1D7 Career Field Manager. For ANG, contact 1D7

Career Functional Manager and AFRC contact 1D7 Functional Manager.

Personnel working with Remote Piloted Aircrafts (RPA) will follow AFI 21-101, Aircraft

Equipment Maintenance Management, and applicable supplements.

COMSEC operations, program, personnel, work center, and equipment are exempt from QA evaluation. The COMSEC program and operations are audited and semi-annual self-assessments conducted IAW AFMAN 17-1302-O Chapter 17, COMSEC Audits, using AFMAN 17-1302-O

Attachment 13, COMSEC Detailed Checklist. COMSEC Managers perform semi-annual self-assessments of the COMSEC program and operations following the schedule in MPTO 00-33B-

5001, Table 8-1. Based on the results from COMSEC audits and semi-annual assessments, Commanders direct QA to conduct special evaluations on any COMSEC areas.

2.1.1 Applicability and Authority. The QA program is applicable to any unit where 1D7XX personnel perform maintenance. This includes DoD civilians and contracted personnel performing 1D7XX maintenance as prescribed in their PWS or SOW per paragraph

1.5. Commanders will perform the QA functions prescribed within this technical order unless a risk assessment is performed on the function. The seven QA functions are:

• Personnel evaluations

• Equipment evaluations

• Technical order management

• Corrosion prevention and control program

• Electrostatic discharge program

• Statement of Work and Performance-Based Work Statement reviewer

• Local work card validator

2.1.1.1 Commanders will actively manage their unit(s) QA program. This includes performing a deliberate risk assessment across each of the seven QA functions. Commanders can identify any risks associated to not fully performing QA functions and eliminate/avoid/reduce/transfer risk on QA functions to an acceptable level. This is done by completing a documented risk assessment for each function. Commanders will document this process using the AF Form 4437, Deliberate Risk Assessment Worksheet, per AFI

90-802, Risk Management and AFPAM 90-803, Risk Management (RM) Guidelines and Tools. Commanders use the results from the risk management (RM) process to establish and maintain their QA programs. Commanders will document their program’s roles, responsibilities, structure, and local procedures in an operating instruction, standard operating procedure, or memo for record following guidance in AFI 33-360, Publication and Forms Management.

AFI 90-802 states, to effectively apply risk management, commanders, supervisors, and personnel must dedicate time and resources to integrate RM principles into planning, operational processes and day-to-day activities. It is a best practice that gaining commanders should accomplish AF Forms

4437s for each of the seven QA functions within 90-days of their assumption of command. If all seven QA functions are being performed in the unit, it is recommended the gaining CC should conduct a review of the QA program and any 4437s on file. No 4437s are required if the unit is already performing all seven QA functions.

The QA program will not be completely waived without a waiver from the AF 1D7 Career Field

Manager. See Chapter 10 for more information on processing waivers.

2.1.1.2 Primary responsibility and local policy for performing each QA function will be identified in an applicable unit operating instruction, standard operating procedure, or memo for record. For example, a Cyber Operations unit’s QA functions may be managed at the group level and administer by the subordinate the unit’s Quality Assurance Representative(s) (QAR). Additionally, based on risk assessment findings, leadership builds their QA program’s duty positions and lines of authority. These duty positions are identified in paragraph 2.3.1 and 2.3.2.

Examples of operating instructions, standard operating procedures, or memo for records can be found by searching the Cyberspace Arena or by posting a request to other QA personnel via the

Arena’s discussion board.

2.1.2 Purpose. QA personnel identify deficiencies, perform root cause analysis, develop short and long-term solutions, and analyze trends to determine if systemic deficiencies exist. The combined efforts of leadership, QA personnel, management, and technicians are necessary to ensure high quality production, services, and equipment reliability.

2.1.3 Scope of Program. Commanders actively manage their QA program. QA personnel perform key assessments of how the unit performs maintenance functions, trains maintenance personnel, and maintains compliance with instructions, technical data, safety directives, policies and other policy guidance. QA personnel performs these assessments by conducting personnel evaluations and equipment evaluations.

2.2 KEY TERMS.

2.2.1 Core Equipment/Systems. Core equipment/systems refers to equipment, systems, and infrastructure devices/items or processes that have grave effect(s) on the organization’s mission and day-to-day operations if not fully mission capable. Generally, these items are listed in the base restoral plan, mission essential listing, and/or are one-of-a-kind items. Examples would be central telephone switch, service delivery points, inter-network transfer nodes (ITN), etc. May also be referred to as mission critical equipment/systems.

2.2.2 Unit Type Code (UTC) Based Equpiment/Systems. Unit Type Code (UTC)-based organizations refers to units/flights/elements whose primary mission is to deploy. Examples of these units are combat communications squadrons, engineering installation squadrons, air control squadrons, and air support operation squadrons. Equipment/systems within UTC-based organizations are equipment/ systems that would prevent mission success (e.g., main satellite communications terminal, Promina, large voice) and/or prevent the UTC from meeting its mission capability.

2.2.3 Nuclear Command, Control and Communications Equipment (NC3E) Equipment/Systems. Refer to Chapter 4 for more details.

2.2.4 Other/Ancillary Equipment/Systems. Other/ancillary equipment/systems, if not fully mission capable, have negative effects on the organization’s mission and day-to-day operations; however, it is just degraded. Generally, these items have multiple redundant systems. These may include items like servers, end building node equipment, enterprise storage, receivers, transmitters, antennas, application monitoring, and client interfaces.

2.2.5 Trend Analysis. Trend analysis is used to collect, compile, analyze, and record data on the processes sampled by QA personnel. Trend analysis evaluates data collected and determines adverse or positive trends affecting quality. After a root cause determination is made, they will report their findings to management. Findings will include recommendations or options to improve identified non-conformities. Effective management processes will ensure prompt and standardized adjustments are made to the organization’s operations for continuous improvement of processes. See Chapter 17 for more information on conducting trend analysis.

2.2.6 Deficiency. A deficiency is any characteristic of equipment, processes or personnel that identifies a failure to conform to established directives or standards. Categorizing deficiencies aids evaluators in determining the overall result of the evaluation. All deficiencies for personnel and equipment evaluations are tracked for trend analysis using standardized codes. The decision to document a deficiency must be based on published standard communications practices and standardized procedures. Deficiencies fall under one of the following three categories, based on degree of seriousness:

2.2.6.1 Category I (Cat I)/Critical Deficiency. A category I/critical deficiency results in an unsatisfactory evaluation. It is also referred to as a Cat I deficiency and will require the evaluator to stop the evaluation and apply immediate corrective measures. See

Table 2-1 and Table 2-3 for more details. Cat I deficiencies have the potential to cause:

• Strong potential/actual loss of life or limb, litigation or a Ground Mishap Report (AF Form 164) is required

• Change mission to Non-Mission Capable (NMC) status

• Actual equipment degradation or life-span; to include end items, ancillary, support or test equipment

• Security incidents or violations that require further investigation or reporting; failure to meet instructions

2.2.6.2 Category II (Cat II)/Major Deficiency. A category II/major deficiency can result in an unsatisfactory evaluation. Cat II deficiencies can cause or have potential to cause:

● Slight risk/probability to cause minor bodily harm; e.g., faulty gloves, scratched goggles, dim flashlight, etc.

● Change mission to Partially Mission Capable (PMC) status

● Possible equipment degradation or life-span; to include end items, ancillary, support or test equipment

● Possible minor security issue that does not require further investigation or reporting

2.2.6.3 Category III (Cat III)/Minor Deficiency. A category III/minor deficiency can result in an unsatisfactory evaluation if it detracts from the overall job or equipment/system performance.

2.2.6.3.1 The equipment/system, product or service meets the overall requirements with the exception of minor deficiencies; and/or is any deficiency that does not degrade mission, system or equipment capability; and/or does not create an unsafe condition; and/or is not a potential security violation. However, it does not meet or comply with technical parameters, standards, and/or requirements.

2.2.6.3.2 The personnel performing the task on the equipment/system, and/or product or service meet the overall intention of the requirements, however, with exceptions. These exceptions/Cat III deficiencies do not result in mission degradation, equipment performance, damage to or a wasteful use of any resources, present a safety hazard, and/or create a security violation.

2.2.6.4 Corrected During Evaluation (CDE). Used on a report to show that the deficiency was corrected during the evaluation or on-the-spot. These deficiencies could still indicate a systemic issue and are factored in for trend analysis.

2.2.6.5 Deficiency Code. Deficiency codes are used by QA evaluators to assist with compiling similar data elements and ease the process of root cause analysis. They also help analyze trends across broad areas of the organization. Codes are assigned to each deficiency evaluation reports. All deficiencies are tracked for trend analysis using standardized codes referred to as deficiency codes.

The codes are listed within this chapter in tables 2-1 and 2-3.

2.2.6.6 Satisfactory. The rating given to indicate the overall results of evaluations. It indicates that the performance or operation meets mission requirements. Procedures and activities are carried out in an effective and competent manner. Resources and programs are efficiently managed. Minor deficiencies may exist but do not impede or limit mission accomplishment.

2.2.6.7 Unsatisfactory. The rating given to indicate performance or operation does not meet mission requirements. Procedures and activities are not carried out in an adequate manner. Resources and programs are not adequately managed.

2.2.7 Statement of Work (SOW). The SOW is the portion of a contract that establishes and defines all non-specification requirements for contractor's efforts either directly or with the use of specific cited documents. This document describes the actual work that is to be performed by the contractor and often uses references to such documents as specifications and documents incorporated into the SOW as compliance documents or reference documents. Some documents can be presented in full text while others may be incorporated by reference. The SOW specifies in clear, understandable terms the work to be done in developing or producing the supplies to be delivered or services to be performed by a contractor. Preparation of an effective SOW requires both an understanding of the supplies or services that are needed to satisfy a particular requirement and an ability to define what is required in specific, performance-based, quantitative, or qualitative terms. A SOW prepared in explicit terms enables offerors to clearly understand the government's requirements, including international acquisition documents (International Agreements, Foreign Military Sales Letters of Offer and Acceptance), as applicable.

This understanding facilitates the preparation of responsive proposals and delivery of the required supplies or services. A well-written

SOW also aids the government in selecting the source for contract award, and for contract management and contract administration after award. In short, a SOW can involve the “how” to successfully complete the contract.

2.2.7.1 Example. The contractor will build 2 server racks using 8 Dell 123 servers running Red Hat Enterprise Linux all configured as file servers in order to host documents for ACC.

2.2.8 Performance-Based Work Statement (PWS). The PWS is a statement of work for performance-based acquisition that describes the required results in clear, specific, and objective terms with measurable outcomes. These are often used in services, but can also be used in supply contracts when describing outcomes. The PWS states requirements in general terms of what is to be done (result), rather than how it is done (method). The PWS gives the contractor maximum flexibility to devise the best method to accomplish the required result. The PWS is written to ensure that offerors compete fairly based on their capabilities. The government can remove PWS requirements that unfairly restrict competition. However, the PWS is descriptive and specific enough to protect the interests of the government, including international acquisition documents (International Agreements and Foreign Military Sales Letters of Offer and

Acceptance, as applicable), and promote competition unless otherwise specified by the FMS customer nation. The clarity and explicitness of the requirements in the PWS invariably enhance the quality of the proposals submitted. A definitive PWS is likely to produce definitive proposals, thus reducing the time needed for proposal evaluation. In short, a PWS will specify what needs to be accomplished but not how to do it.

2.2.8.1 Example. The contractor will provide the USAF with file hosting capable of storing 500TB and providing 24/7 access to up to

25,000 users simultaneously with a guaranteed 99.5% uptime and automated redundancy.

2.3 PERSONNEL SELECTION AND TRAINING REQUIREMENTS.

QA personnel are assigned as QA evaluators and QA representatives positions, based on their level of experience and expertise in many areas.

2.3.1 QA Personnel. Individuals selected by the commander to staff QA positions will be the most qualified persons identified by skill and experience, motivation, and knowledge of evaluation, analysis, and support duties. Personnel will also need to possess the appropriate security clearance.

2.3.1.1 The unit commander staffs QA with a diversified and adequate number of personnel. Recommend at least two personnel assigned at all times.

2.3.1.2 QA personnel must be able to provide assistance with technical and management guidance so staff functions and work centers can detect and correct problems in the early stages.

2.3.1.3 When active duty personnel are assigned to QA, the minimum tour length should be 18 months with a maximum tour of 30 months. For Air National Guard (ANG) and Air Force Reserve Command (AFRC) units, the unit commander determines tour length.

Active duty personnel should not be utilized in a QA position for consecutive tours of duty. Allowing personnel to rotate back to an applicable work center will prevent stagnation. The assigned duty titles for QA personnel is NCOIC or Evaluator.

2.3.1.4 Due to the inherent need for experienced QA evaluators, the required minimum grade is SSgt, Civilian equivalent or

Contractor. When Contractors are utilized as QA personnel they may not perform Personnel Evaluations or Acceptance Inspections.

However, in cases of short-term (e.g. deployment related) or long-term unit manning shortfalls, a commander may appoint SrA with a 5-skill level who has completed Airman Leadership School. Document the grade and skill level waiver on a local memorandum signed by the unit commander.

2.3.1.5 Ensure assigned military personnel are qualified in Training Business Area (TBA) on tools, technical orders, significant history, approved AIS (i.e., IMDS, Remedy, etc. utilized by the PWC), and Test, Measurement and Diagnostic Equipment

(TMDE) along with at least one system or process the QA evaluator may be evaluating.

2.3.2 Quality Assurance Representative (QAR). A QAR is a member of the unit, not permanently assigned to a QA program.

QARs should be highly qualified persons identified by skill and experience, motivation, and knowledge of evaluation, analysis, and support duties. QARs are often used in small units or detachments where a full QA program does not exist, or when mission needs dictate a smaller permanent QA presence and still needs to complete inspections. When a military member is assigned as a QAR they must possess a minimum 5-skill level (PAFSC).

2.3.2.1 QARs assist QA personnel in performing personnel and equipment evaluations when requested by the QA evaluator.

2.3.2.2 If an organization is without QA support, QARs are utilized to perform all required evaluations. The unit commander has the authority to appoint one or more QAR(s) to accomplish duties as directed. The number of QARs must be restricted in order to maintain the integrity of QA evaluations.

2.3.2.3 As part of QAR training, an experienced QA evaluator will demonstrate an OJT EE and PE. Then an experienced QA evaluator will monitor the QARs first personnel and equipment evaluation administered subsequent to QAR qualification. If QARs conduct personnel evaluations, experienced QA evaluators shall conduct “over-the-shoulder” checks on QARs to validate the objectivity and accuracy of personnel evaluations. Each QAR must pass both “over-the-shoulder” checks prior to performing unsupervised equipment and personnel evaluations. QA will determine if additional “over-the-shoulder” checks are required. The

“over-the-shoulder” check should be documented on the AFCQCC 100-1; both the QAR and QA evaluator names should be listed in the “evaluators” block for the given evaluation.

2.3.2.4 Additionally, prior to performing unsupervised IDS/RTES or NC3E/WS3 evaluator duties, QAR personnel must:

a. Qualify on each of the following evaluation types: individual, equipment and special evaluations under the oversight of trained of trained QA personnel.

b. Be CFETP qualified on tools, technical orders, significant history, IMDS, and TMDE tasks.

c. Be interviewed by the OIC/NCOIC or QA.

2.3.3 Training Requirements. Training requirements should be specified within the unit’s QA operating instruction, standard operating procedure, or memo for record. QA and QARs will complete the following training requirements.

2.3.3.1 Personnel assigned to QA offices or appointed as QAR supporting a QA office will be trained by experienced QA personnel on evaluation procedures.

2.3.3.2 QA personnel will complete Air Force Job Qualification Standard (AFJQS) 1D7XX-201G, Quality Assurance, and use it as a guide for training QARs.