Air Force
Intelligence and Security Doctrine





This instruction implements AFPD 10-7, Command and Control Warfare, by providing the requirements for reprogramming electronic warfare (EW) systems to respond to changing threats. Because electronic warfare integrated reprogramming (EWIR) requires multiple agencies to work together, each agency must ensure that its reprogramming is timely, accurate, and effective. These instructions implement portions of the Chairman of the Joint Chiefs of Staff (CJCS) Memorandum of Policy (MOP) 6, Electronic Warfare, January 19, 1990; CJCS MOP 25, Wartime Reserve Modes (WARM), July 13, 1990; Joint Chiefs of Staff Memorandum (JCSM) 173-87, WARM Implementation Plan, October 10, 1987; JCSM 227-86, Plan for Joint Coordination of Electronic Warfare Reprogramming, October 27, 1986; Joint Chiefs of Staff Secretary Joint Staff Memorandum (JCS SM) 90-85, Plan for Integrated Intelligence Support to EW and C3CM, February 11, 1985; and Joint Pub 3-51, EW in Joint Military Operations, June 30, 1991. See attachment 1 for a list of abbreviations, acronyms, and terms used in this instruction.


This is the initial publication of AFI 10-703, substantially revising AFR 55-24. This instruction provides improved descriptions of responsibilities and organization interfaces. The focus of these improvements is to inform participants of specific processes and to facilitate the timely and accurate completion of EWIR.


Chapter 1--EWIR Purpose, Scope, and Objectives
Purpose 1.1
Scope 1.2
Objectives 1.3

Chapter 2--Functional Responsibilities
Air Staff 2.1
MAJCOMs and Agencies 2.2
Air Force Materiel Command (AFMC) 2.3
Air Intelligence Agency (AIA) 2.4
MAJCOM Headquarters Operations Directorate (DO) or Equivalent 2.5
MAJCOM Headquarters Requirements and Acquisition Directorate (DR)
or Equivalent 2.6
MAJCOM Headquarters Logistics Directorate (LG) 2.7
MAJCOM Headquarters Command, Control, Communications, and Computers
Directorate (SC) 2.8
MAJCOM Headquarters Intelligence Directorate (IN) 2.9
Air Force Reserve (AFRES) and National Guard Bureau (NGB) 2.10
US Air Force Air Warfare Center (USAFAWC) and Detachment 1 Special
Operations Command Operations Staff (DET 1 SOCOS) (Operational
Reprogramming Centers [RC]) 2.11


Supersedes AFR 55-24, February 1991. Certified by: HQ USAF/XO (Lt Gen Buster C. Glosson)
OPR: HQ ACC/DOTE (Lt Col Daniel W. Lange) Pages: 28/Distribution: F


Air Force Operational Testing and Evaluation Center (AFOTEC) 2.12
Numbered Air Forces (NAF) 2.13
Air Force Air Operations Center (AOC) 2.14
Operational Units 2.15
EWIR Committee and Subcommittee Interoperability 2.16

Chapter 3--Operational Procedures
Critical EWIR Operations 3.1
EWIR Deficiency Reporting 3.2
Implementing Changes 3.3
Reporting 3.4

Chapter 4--Exercises and Evaluation Programs
General 4.1
Annual Exercises 4.2
Quarterly Exercises 4.3
Local Exercises 4.4

Chapter 5--International Agreements and Security Assistance
Purpose 5.1
Scope 5.2
Objectives 5.3
Special Factors 5.4
Functional Responsibilities 5.5
US Air Force Management 5.6
Mission Data Responsibilities 5.7
Operational Procedures 5.8
Intelligence 5.9
Communications 5.10
Support 5.11


1. List of Abbreviations, Acronyms, and Terms 19
2. EWIR Subcommittee Membership Matrix 23
3. Sample Operational Change Request (OCR) Format 24
4. Sample Implementation Message (IMP) Format 25
5. Sample Unit Loading Message (ULM) Format 26
6. EWIR Message Designation Standards 27


Chapter 1


1.1. Purpose. EWIR is a critical, systematic, decision-making tool that gives operational commanders a timely and accurate means to respond to unexpected emissions and unique mission requirements. It reduces aircraft attrition.

1.2. Scope. EWIR consists of systems and procedures to
make changes to EW equipment. Effective EWIR requires that:

1.2.1. Reprogramming includes changes in:
1.3. Objectives. The Air Force's overall objective for EWIR is to maintain the ability to detect, classify, and effectively counter enemy threats. To support this principal objective, the Air Force:
1.3.1. Sets up an effective intelligence capability to rapidly collect, identify, compare, analyze, and distribute tactical and technical electronic intelligence (ELINT) information during peacetime, contingency, and wartime operations.
1.3.2. Maintains an accurate, timely, and worldwide EWIR database (EWIRDB) to provide intelligence and operations personnel with parametric data for EW systems reprogramming. This data base also supports:
1.3.3. Maintains order of battle (OB) databases for
regions with "electronic fit" (radar-system-to-weapon-system-platform correlation) of threats to generate regional mission data (MD) for MOP 6.
1.3.4. Maintains an effective and responsive wartime reserve and threat analysis capability.
1.3.5. Develops and implements EWIR support structures and processes.
1.3.6. Implements a timely, secure, and survivable means to transmit reprogramming change information worldwide.
1.3.7. Sets up and maintains facilities to create, test, and distribute EW software changes for operational com-manders.
1.3.8. Completes EW systems reprogramming to lessen the negative effects of a commander's use of assets for sorties and missions.
1.3.9. Develops an EWIR process that includes:
1.3.10. Operates an effective EWIR training program at all command levels.
1.3.11. Applies research, development, test, and evaluation (RDT&E) resources to obtaining rapidly reprogrammable EW systems and related support equipment that remain effective in a changing electro-magnetic environment.
1.3.12. Promotes joint applications and interoperability.


Chapter 2


2.1. Air Staff:
2.1.1. HQ USAF/XO. The Deputy Chief of Staff for Plans and Operations: Manages EWIR activity. Prepares and implements EWIR-related program management directives (PMD). Resolves EWIR conflicts at the major command (MAJCOM) level. Chairs the EWIR Oversight Committee. Ensures that commanders effectively communicate their EWIR intelligence production requirements to the intelligence community and HQ USAF/IN. Ensures that MAJCOMs practice and evaluate the effectiveness of EWIR by conducting at the least an annual worldwide SERENE BYTE exercise. Oversees the analysis of EW equipment based on potential threats or enemy threat change validations. Develops procedures and coordinates other services for jointly developing and using EWIR resources. Co-chairs the Foreign Military Sales (FMS) Electronic Combat Working Group (ECWG), which manages policies and procedures for transferring US Air Force EC capabilities to allied and friendly nations. Oversees the FMS Electronic Combat International Security Assistance Program (ECISAP) as described in chapter 5. Sets up requirements for joint intelligence centers (JIC), the joint analysis center (JAC), and scientific and technical intelligence (S&TI) centers.
2.1.2. HQ USAF/IN. The Assistant Chief of Staff for Intelligence: Ensures that NAIC, by using the Defense Intelligence Agency (DIA) and the other S&TI centers, continues to predict Wartime Reserve Modes (WARM)
capabilities effectively. Works with the DIA and JCS to set up procedures for rapidly validating and reporting threat changes. Ensures that commanders document their operational EWIR intelligence requirements and send them to the DIA for action. Provides complete intelligence information to the theater or MAJCOM commander concerning EW system reprogramming for training, exercises, and combat operations. Works with the DIA to ensure that other services and intelligence agencies receive EWIR intelligence support. Chairs the EWIR Intelligence Subcommittee and informs HQ USAF/XO of the committee's progress. Works within the intelligence community to get EWIR products for the RCs to support allied and friendly nations. Coordinates the EWIR efforts of the DIA, JICs, JAC, and S&TI centers in accordance with JCS SM 90-85. Orchestrate intelligence participation in annual SERENE BYTE exercises. Supports intelligence production requirements unique to the EWIR process as the EWIR Intelligence Subcommittee develops them.
2.1.3. HQ USAF/LG. The Deputy Chief of Staff for Logistics: Develops an integrated logistics support plan to facilitate multiple, simultaneous EW reprogramming actions. Sets up procedures and agreements to coordinate all phases of EWIR logistics support. Oversees EWIR logistics support (including support equipment and reprogramming tools) to maintain standardization and flexibility. Chairs the EWIR Logistics Subcommittee and informs HQ USAF/XO of the committee's progress.
2.1.4. HQ USAF/SC. The Deputy Chief of Staff, Command, Control, Communications and Computers: Provides secure, reliable, and survivable communications and computer capability for the worldwide transmission and processing of essential EWIR information to and from fixed and mobile locations. This information includes: Acts as office of primary responsibility (OPR) for a comprehensive EWIR communications plan outlining current and future connectivity and data transfer needs. Coordinates with HQ USAF/IN C4 on communications issues unique to EWIR data that Defense Special
Security Communications Systems (DSSCS) process. Provides data to the US Non-Communications Database through JS/J-6 and the Electromagnetic Compatibility Analysis Center (ECAC). Chairs the EWIR Communications Subcommittee and informs HQ USAF/XO/IN of the committee's progress.
2.1.5. SAF/IA. The Deputy Under Secretary for International Affairs: Acts as the focal point for foreign military sales of US Air Force EW and EWIR systems to foreign governments. Informs the JCS and unified and specified commanders of proposed and actual sales of EW systems (to include hardware and software configurations) to foreign governments. Acts as the OPR for transferring military information to allied and friendly nations. Co-chairs the FMS ECWG to manage policies and procedures for transfer of US Air Force EC capabilities to allied and friendly nations. Provides oversight to the FMS Electronic Combat International Security Assistance Program (ECISAP) as described in chapter 5.

2.2. MAJCOMs and Agencies. Air Combat Command (ACC), Air Force Special Operations Command (AFSOC), Air Mobility Command (AMC), Air Force Materiel Command (AFMC), Air Intelligence Agency (AIA), US Air Forces Europe (USAFE), and Pacific Air Forces (PACAF):
2.2.1. Provide staffing, resources, and funding to fulfill peacetime, wartime, and contingency EWIR requirements.
2.2.2. Advise the Chief of Staff, Headquarters US Air Force (HQ USAF), when EWIR capabilities do not meet Air Force objectives.
2.2.3. Develop comprehensive EWIR training programs that include EWIR decision-making and intelligence support.
2.2.4. Ensure that OPLANs, CONPLANs, and strategic war plans discuss EWIR in order to:

2.2.5. Ensure that EWIR exercises take place annually under simulated wartime conditions. Attend SERENE BYTE exercise planning conferences and annual EWIR conferences, as required. Conduct quarterly SERENE BYTE data trans-mission reprogramming exercises for operational, maintenance, and communications personnel. Participate in annual SERENE BYTE exercises. Include the appropriate AFRES and ANG units in SERENE BYTE exercises (ACC and AFSOC only). Compile SERENE BYTE exercise results and send them with recommendations to the appropriate agencies. Identify the EW systems and units requiring SERENE BYTE exercises and coordinate this information with the Air Force Information Warfare Center (AFIWC) and the RCs.
2.2.6. Develop EWIR hardware and software require-ments and coordinate them with other MAJCOMs and HQ USAF. These requirements include:
2.2.7. Attend the EWIR oversight committee or subcommittee working groups, as required.
2.2.8. Advise the joint frequency management office (JFMO) of frequency changes to active EW equipment.
2.2.9. Provide applicable RCs with quarterly updates of the EW assets and locations list.
2.2.10. Ensure that commanders' EWIR requirements for S&TI production of threat systems, including WARM, are current, complete, and properly documented.

2.3. Air Force Materiel Command (AFMC). AFMC:
2.3.1. Reprograms EW systems and ensures that: Users receive fully developed and tested EW systems and EWIR improvements with the operational capabilities that they have specified. Each EW system relying on the parametric characteristics of electromagnetic energy propagation and processing is rapidly reprogrammable. The appropriate communication devices can transmit software reprogramming changes to field units, regardless of location. An EW system's reprogrammability and methods of distributing EWIR changes receive the proper RDT&E. Each EW system includes these fully tested items both at the reprogramming centers and in the field at delivery of the first asset:

2.3.2. Plans, integrates, and acquires new EWIR systems.
2.3.3. Identifies opportunities for acquiring joint systems.
2.3.4. Uses the EWIR Database (EWIRDB) and other sources of intelligence information to develop and reprogram EW systems.
2.3.5. Helps acquire and provide the logistics and engineering support for both the hardware and software elements of EW systems and their associated support, training, and range simulators equipment. Sets up and manages facilities and personnel to
analyze, develop, and test changes to: Maintains facilities for complete EW system ground testing. Maintains equipment to transmit EW software changes to operational units worldwide. Responds to approved OCRs. Helps operational commands develop OFPs and MD support when the operational MAJCOMs request. Helps identify, obtain, develop, and maintain EW systems software reprogramming tools. Helps AFIWC develop and maintain flagging models. Develops and maintains a Computer Resources Life Cycle Management Plan (CRLCMP) for each EW system. Updates software block cycles for the using commands according to each EW system's CRLCMP. Chairs the Configuration Management Subcommittee (WR-ALC/LNE) and informs HQ USAF/XO of the committee's progress. Provides EC engineering and logistics support to allied and friendly nations through the ECISAP, as detailed in chapter 5. Gives AFIWC complete EWIRDB information on systems that AFMC manages or develops. Notifies the appropriate theater MAJCOM DOs of FMS sales of EW equipment (including software updates) that AFMC manages or develops. Ensures that the RCs and MAJCOMs can track EWIR actions (such as threat change validation messages [TCVM], threat impact messages [TIM], OCRs, reprogramming, and so forth).

2.4. Air Intelligence Agency (AIA):
2.4.1. The Air Force Information Warfare Center (AFIWC): Plans, implements, and manages the annual, worldwide SERENE BYTE exercise to assess EWIR effectiveness. As part of this effort, AFIWC: Designs, manages, and budgets EW equipment flagging and analysis models by coordinating with other agencies. Provides CONUS and in-theater flagging analysis of ELINT data to the RCs, the Joint Forces Air Component Command (JFACC), and the Combined Forces Air Component Command (CFACC)/AOC as required to support peacetime, exercise, contingency, and
wartime operations. Chairs the SERENE BYTE Exercise Subcommittee and informs HQ USAF/XO of the committee's progress. Trains personnel to provide EWIR support for wartime, contingency, and training operations. Analyzes EWIR actions during wartime, contingency, and training operations as HQ USAF directs. Updates parametric information on US-produced or rest-of-world(ROW) systems for the EWIRDB. Participates in advisory and other groups, as appropriate, to further develop and standardize EWIRDB and EWIR.
2.4.2. National Air Intelligence Center (NAIC): Acts as the DoD executive agent for the EWIRDB as the DIA requires. Merges data, when required, from NAIC EW analysis activities, other S&TI centers, National Security Agency (NSA) Kilting ELINT data, and AFIWC (for US systems and some friendly foreign systems data) to form the EWIRDB. Accesses the EWIRDB on-line (using DISN or other secure networks) when external organizations request. Distributes the EWIRDB in accordance with DIA rules. Performs accuracy checks on the EWIRDB. Quickly provides outside consumers with S&TI data for reprogramming during exercises and wartime and contingency operations. Predicts the total capabilities of threat systems, including WARM capabilities, when requested, and reports its predictions via the EWIRDB. Participates in advisory and other groups, as appropriate, to further develop and standardize the EWIRDB and EWIR. Coordinates with AFMC and SAF/AQ to provide equipment and support for ground and airborne testing against foreign assets. Allows RCs to conduct Foreign Material Exploitation (FME).

2.5. MAJCOM Headquarters Operations Directorate (DO) or Equivalent:
2.5.1. Oversees EW reprogramming.
2.5.2. Approves software changes for all systems in the field. The MAJCOM/DO considers recommendations from the RCs and the EW Software Configuration Control Sub-Board (SCCSB) as part of its review.
2.5.3. Sends implementation messages (IMP) to applicable subordinate units.
2.5.4. Coordinates RCs in developing EW training settings.
2.5.5. Attends the Computer Resource Working Group
(CRWG) and Interface Control Working Groups (ICWG), as required.
2.5.6. Upgrades EW software flight-testing priorities during wartime and contingency operations (ACC and AFSOC only).
2.5.7. Discusses employment concepts and the operations concept for theater assets with the RCs.
2.5.8. Supports the ECISAP, as requested.

2.6. MAJCOM Headquarters Requirements and Acquisition Directorate (DR) or Equivalent:
2.6.1. Works with the RCs to identify the initial requirements of reprogramming facilities, equipment, and staffing for EW systems under development.
2.6.2. Works with the RCs to ensure that changes to EW systems in the field, support equipment, and new systems are compatible with EWIR requirements and associated communications support systems.
2.6.3. Identifies and coordinates Operational Test and Evaluation (OT&E) requirements for all EW systems.
2.6.4. Coordinates EW system requirements with MAJCOM/DO/IN/LG/SC and the EC Product Group Manager (PGM).
2.6.5. Ensures that all applicable program specifications include validated operational requirements. Represents program management concerns during the demonstration and validation, engineering and manufacturing development, and production and deploy-ment phases of acquisition.
2.6.6. Coordinates EWIR actions with the MAJCOM/DO.

2.7. MAJCOM Headquarters Logistics Directorate (LG):
2.7.1. Oversees EWIR logistics.
2.7.2. Reports logistics deficiencies in EW system software in the field according to Technical Order (TO) 00-35D-54, USAF Deficiency Reporting and Investigating System and TO 00-5-1, The Air Force Technical Order System.
2.7.3. Monitors EW equipment and support equipment to ensure that units are meeting EWIR logistics support requirements.
2.7.4. Ensures that all field units receive adequate EW support equipment.
2.7.5. Notifies the MAJCOM/DO of logistics problems in reprogramming.
2.7.6. Ensures that maintenance personnel receive training in reprogramming EW systems.
2.7.7. Sets up requirements for working with the RCs to transport reprogramming data to Combat Air Forces (CAF) units.
2.7.8. Coordinates EWIR actions with the MAJCOM/DO.

2.8. MAJCOM Headquarters Command, Control, Communications, and Computers Directorate (SC):
2.8.1. Provides inputs to CRLCMPs for all EW systems and support equipment software.
2.8.2. Coordinates between EWIR OPRs and telecom-munications centers (TCC) (fixed and mobile).
2.8.3. Ensure that RCs have the correct routing indicators for EWIR text and data messages that are based on the plain language addresses. Each wing or unit must provide the correct unit and office symbol to their TCCs (fixed and mobile) to ensure that RCs are using the correct routing indicator.
2.8.4. Ensures that TCCs (fixed and mobile) have a floppy-disk capability that is compatible with EWIR systems and TCC terminals. Reports deficiencies or changes to the MAJCOM/DO/LG.
2.8.5. Ensures that TCC personnel receive training in operating TCC communication equipment during repro-gramming.
2.8.6. Sets up procedures for transmitting and receiving EW reprogramming data.
2.8.7. Ensures that TCC operating instructions (OI) are developed to provide installation handling instructions for PACER WARE and SERENE BYTE text and data messages.
2.8.8. Works with others, as necessary, to resolve problems with fixed and mobile communications support.
2.8.9. Coordinates EWIR actions with the MAJCOM/DO.

2.9. MAJCOM Headquarters Intelligence Directorate (IN):
2.9.1. Develops a guide describing the role of collectors in EW reprogramming analysis.
2.9.2. Trains both operators and collectors (including crew briefings and debriefings) in intelligence matters.
2.9.3. Works with HQ USAF/IN to ensure that supporting intermediate processing centers (IPC): Review operational intelligence requirements to support EWIR. Assess technical and operational ELINT for emergency validation and reporting (using available intelligence products) to the S&TI centers, RCs, AFIWC, and MAJCOM/IN. Appoint intelligence production points of contact and coordinate production efforts among them. Identify and work on improvements to intel-ligence collection and production methods to provide near real-time assessments of technical and operational ELINT. Identify unsatisfied operational intelligence requirements to support EWIR and report them to: Give theater-collected ELINT intercept and other intelligence data to the AFIWC and AFIWC Flagging
Analysis Team (AFAT) (when deployed) for EW flagging.
2.9.4. Maintains points of contact in these S&TI centers:
2.9.5. Contacts the S&TI centers for help with WARM validation and for quick threat system technical assign-ments.
2.9.6. Identifies unsatisfied S&TI requirements to support EWIR and reports them to:
2.9.7. Provides intelligence support to the RCs during SERENE BYTE and PACER WARE actions. This support includes reviewing operations and exercise plans to ensure that the RCs properly evaluate intelligence production and reporting methods.
2.9.8. Coordinates EWIR actions with the MAJCOM/DO.

2.10. Air Force Reserve (AFRES) and National Guard Bureau (NGB):
2.10.1. Ensure that units reprogram their EW equipment as soon as practical, depending on staffing and duty hours.
2.10.2. Ensure that AFRES and Air Guard units can reprogram EW equipment before they move to overseas locations.
2.10.3. Give WR-ALC/LNE quarterly updates of EW assets, addresses, and locations.

2.11. US Air Force Air Warfare Center (USAFAWC) and Detachment 1 Special Operations Command Operations Staff (DET 1 SOCOS) (Operational Reprogramming Centers [RC]):
2.11.1. Develop, produce, and test EW MD (such as conducting EWIR).
2.11.2. Provide technical expertise to all combat EW systems under their command.
2.11.3. Provide guidance and technical help with developing intelligence, logistics, and communications systems in support of EWIR.
2.11.4. Identify computer resource requirements to higher headquarters.
2.11.5. Participate in development and design reviews.
2.11.6. Staff the CRWG, ICWG, and other working groups that help obtain new EW and EW systems.
2.11.7. Help decide on software support concepts.
2.11.8. Help prepare CRLCMPs.
2.11.9. Maintain competent managers and technical personnel for EW computer concerns.
2.11.10. Maintain software support facilities in
accordance with the CRLCMP software support concept.
2.11.11. Support MAJCOM software users and keep track of the software they are using.
2.11.12. Evaluate EW MD and support documentation to ensure adequacy.
2.11.13. Conduct, manage, and support FOT&E of EW software changes.
2.11.14. Create training parameters for EW systems, as necessary.
2.11.15. Identify and send to MAJCOM/IN formal intelligence requirements, including:

2.11.16. Set up procedures for maintaining a Bulletin Board System (BBS) as a backup means of distributing reprogramming data.
2.11.17. Conduct operational analysis and testing to find specific EW system deficiencies.
2.11.18. Prepare Threat Impact Messages (TIMs) when changes in the threat environment might affect EW systems in the theater. TIMs describe:
2.11.19. Submit final OCRs to AFMC.
2.11.20. Produce all MD changes and reprogramming impact messages (RIMs) for assigned reprogrammable EW systems.
2.11.21. Evaluate and resolve field Operational Change Requests (OCRs).
2.11.22. Contribute information to test plans concerning the nature of required tests and independent verification and validation (IV&V).
2.11.23. Authorize reprogramming changes.
2.11.24. Develop system handbooks or EC mission guides for each EW system. USAFAWC and DET 1 SOCOS update and distribute the handbooks and mission guides when required or with each MD update.
2.11.25. Participate in SERENE BYTE reprogramming exercises by:
2.11.26. Give current versions of operational MD to AFIWC for the desired level of MAJCOM and RC flagging support.
2.11.27. Provide engineering support and tactical expertise to ECISAP as defined in chapter 5.

2.12. Air Force Operational Testing and Evaluation Center (AFOTEC). AFOTEC performs end-to-end testing of EW system reprogramming during new EW system operational testing.

2.13. Numbered Air Forces (NAF):
2.13.1. Set up procedures to regularly review the threat systems in their theater, as necessary.
2.13.2. The DO/IN in these organizations: Reviews aircrew and electronic support inputs on threat parameter changes and new threats and sends them to MAJCOM/DO/IN, the RCs, and AFIWC for further review and analysis. Helps implement: Ensures that aircrews receive the appropriate TIMs and RIMs. Ensures appropriate plans, instructions, and responsibilities for EW reprogramming are disseminated at the appropriate levels. Monitors theater operations and intelligence data to identify and assess changes in the EW environment. Integrates EW reprogramming into appro-priate exercise scenarios. Participates in and supports SERENE BYTE exercises as directed by the MAJCOM.

2.14. Air Force Air Operations Center (AOC). (These procedures apply to the US Air Force component of the Joint Forces Air Component Command [JFACC] and Combined Forces Air Component Command [CFACC].) The AOC is the operations center of the CAF Commander. Within the AOC, threat evaluation and identification of changing target/mission requirements are continuous and time-critical functions. The CAF forms the Air Force component of a joint force, a combined force, or as an independent force for the purpose of conducting combat air operations. When deployed for combat operations, US Air Force assets will be under the operational control of the JFACC acting as the principal air advisor to the unified, joint, or combined forces commander who is responsible for management of all resources within the area of operation. The JFACC is responsible for the planning, allocating, directing,
executing, and controlling of combat air operations and air intelligence resources required to support combat operations. The AOC:
2.14.1. Monitors the EW threat environment during emergency situations.
2.14.2. Performs preliminary operational deficiency analysis, generates, and sends field OCRs to MAJCOMs and RCs.
2.14.3. Issues threat system warnings to aircrews to increase aircraft survivability.
2.14.4. Distributes reprogramming change information to joint and combined organizations to:

2.14.5. The AOC Combat Intelligence Division (CID) Air Defense Analysts and Electronic Analysts: Reviews source data to find: Reports friendly force source data findings that lead to false identifications or inappropriate responses and requests that supporting IPCs validate these changes. Notifies the electronic combat duty officer and the EW officers in Combat Plans and Combat Operations Divisions of all source data findings, helps notify units, and prepares OCRs. Reviews TIMs and reports additional data to reprogramming centers.
2.14.6. The AOC Electronic Combat Staff: Monitors: Analyzes these reports and messages to find: Prepares collection requests with the CID ELINT analyst and sends them to the Collection Management Branch (CMB) when insufficient data exists for assessment. Determines, if possible, the impact of threat parametric and changes in capability on combat EW systems. Notifies the CID Chief, Combat Operations and Combat Plans Divisions, of the impact of threat changes. Requests technical help from the appropriate
MAJCOMs, RCs, and support agencies. Prepares OCRs for newly defined threat changes. Takes any of these actions (but is not limited to them) to minimize the impact of threat changes: Receives reprogramming data and distributes it quickly to the proper units. Instructs subordinate units to install repro-gramming data depending on: Implements alternate distribution procedures (for example, airlift) when it can't transmit reprogramming data. Determines the impact on planning of an installation's reprogramming changes and changes the air tasking order accordingly.
2.14.7. When communications with RCs (or other support agencies) are disrupted or degraded, the AOC: Assesses the threat using theater resources, including: Determines the potential impact on current EW capability. Identifies operational deficiencies in EW systems and tactics. Advises operational units. Makes every effort to set up alternate com-munications with the RCs. Limits reprogramming changes to aircrew reprogrammable actions and tactics changes.

2.15. Operational Units:
2.15.1. Provide the NAF DO/IN and the AOC (when activated) with aircrew inputs on observed threat parameter and symbology changes.
2.15.2. Assign a single EW POC (Wing or Group Defensive Systems Officer [DSO], an EW Officer [EWO], or an Electronic Combat Officer [ECO]) to coordinate wing or group EWIR activities.
2.15.3. Receive software changes for EW equipment operation, employment, and tactics via the RIMs and TIMs that the RCs provide. Immediately report any errors in
reprogramming procedures to the MAJCOM/DO/LG and the RC representatives.
2.15.4. Prepare OCRs according to paragraph 3.2.
2.15.5. Participate in SERENE BYTE exercises as HQ USAF, the MAJCOM, or host MAJCOM/JFACC/CFACC set them up. Report SERENE BYTE exercise results in accordance with paragraph 3.4.
2.15.6. The Wing or Group IN: Provides the wing or group DSO, EWO, or ECO with threat changes that impact EW systems and includes this information, along with RIMs and TIMs, in mission and aircrew briefings. Reviews aircrew debriefings and mission reports for unusual EW equipment that indicates threat changes. Helps the wing or group DSO, EWO, or ECO prepare OCRs. Reports unusual findings in MISREPs.
2.15.7. The Wing or Group DSO, EWO, or ECO: Sets up and directs an EWIR action team consisting of operations, maintenance, intelligence, and communications personnel to: Reviews aircrew and intelligence inputs, including OPREPs and MISREPs, to identify possible EW system deficiencies and prepares an OCR when it finds discrepancies. Keeps aircrews informed on current EW equipment. Briefs affected aircrews on at least RIMs and TIMs prior to their next flight. Briefs aircrews on new EW capability resulting from reprogramming. Briefs aircrews by using all available sources, including: Works with the operations group (OG) (or equivalent) to prioritize changes for aircraft and maintenance squadrons. Notifies aircraft and maintenance squadrons when it receives implementation messages (IMP). Sends all required EWIR reports and messages to higher headquarters and subordinate organizations as appropriate. Maintains a current listing of operational and training software and mission data for EW systems. This list includes pertinent RIMs, TIMs, IMPs, and so forth, as required. Notifies MAJCOM DO and LG representatives (or equivalent) and RCs of unit connectivity status. The notification includes:

2.15.8. Aircraft and Maintenance Squadrons: Ensure that required EWIR equipment is available and operational (such as STU-III, Digital Computer System [DCS], Memory Loader Verifier [MLV], Program Loader Verifier [PLV], current and correct software, and so forth) to support reprogramming at home and deployed locations. If not, notify the wing or group DSO, EWO, or ECO and MAJCOM/LG. Notify wing or group DSO, EWO, or ECO when they receive MD changes. Implement changes only after wing or group DSO, EWO, or ECO approval. Keep the wing or group DSO, EWO, or ECO informed of changes and provide timing data as required. Help staff the EWIR action team.
2.15.9. The Base or Wing/SC: Ensures that telecommunications centers (TCC) comply with information processing instructions and develops OIs to provide instructions for handling EW messages and data. Helps staff the EWIR action team. Quickly identifies communications deficiencies affecting EWIR capability to the wing or group DSO, EWO, or ECO.
2.15.10. Independently deployed flying squadrons per-form the duties outlined in paragraph 2.15.

2.16. EWIR Committee and Subcommittee Inter-operability:
2.16.1. Oversight Committee. HQ USAF/XOFE chairs the Oversight Committee and performs these duties: Notifies applicable DoD agencies of EWIR requirements. Groups all EWIR acquisition programs and funding under a single Electronic Warfare Avionics Integration Support Program (EWAISP), program management directive (PMD), and program officer. Acts as the EWAISP Officer by writing and updating PMD 5092 in accordance with applicable directives. Approves and manages EWAISP funding. Conducts an Oversight Committee meeting at least annually or when required by the chairman. (See attachment 1, section B, for members of the EWIR Oversight Committee.)
2.16.2. EWIR Subcommittees. EWIR subcommittees help to maintain and improve effective worldwide EWIR and perform these duties: Comply with the directives in EWIR-related PMDs, including the EWAISP PMD 5092. Subcommittee memberships are provided at attachment 2. Hold meetings at least twice a year and when the Oversight Committee chairperson directs. Write and distribute subcommittee charters and meeting minutes.
NOTE: The EWIR Oversight Committee Chairman approves subcommittee charters. AFMC WR-ALC/LNE chairs the Configuration Management Subcommittee, which:

NOTE: This subcommittee includes the RCs, their parent MAJCOM, and AFIWC. A complete membership list is provided at attachment 2. HQ USAF/LGM co-chairs (with ASC/RWX) the Acquisition and Logistics Support Subcommittee, which:
NOTE: This subcommittee includes the RCs and their parent MAJCOM. HQ USAF/SCMB chairs the Communications Subcommittee, which develops and integrates communications connectivity between RCs, AFIWC, intelligence support agencies, MAJCOMs, and the operational units. NOTE: This subcommittee includes the RCs, their parent MAJCOM, and AFIWC. HQ USAF/IN chairs the Intelligence Sub-committee, which develops and integrates intelligence production, including parametric data for the EWIRDB.
1. This subcommittee includes the RCs, NAIC, and AFIWC. A complete membership list is provided at attachment 2.
2. DIA, NSA, and the Joint Electronic Warfare Center (JEWC) may attend all EWIR-related meetings as observers. AFIWC/DOOS chairs the SERENE BYTE Exercise Subcommittee, which helps plan, manage, and implement the SERENE BYTE exercise program. NOTE: This subcommittee includes the RCs and AFIWC. A complete membership list is provided at attachment 2.


Chapter 3


3.1. Critical EWIR Operations. These elements are critical to the success of EWIR:
3.1.1. Intelligence. The intelligence community provides: Effective EWIR depends on promptly notifying and validating changes in threat technical capabilities. The S&TI centers authorize threat change validations under normal circumstances. IPCs authorize threat change validations in time-critical situations. They:
NOTE: Request validations via a Threat Change Validation Request (TCVR). AFIWC flagging uses near real-time intelligence to determine how enemy threat changes are affecting friendly EW systems and rapidly transfers this information to the CAF, RCs, and IPCs. The key organizations are the:
3.1.2. Operational Support: ACC and AFSOC oversee the development and maintenance of rapid reprogramming for combat EW systems. USAFAWC and DET 1 SOCOS oversee their respective combat EW systems and missions. They:
3.1.3. Reprogramming. The RCs correct deficiencies or improve the Air Force's response to new threats or threat changes by managing software, hardware, and tactics changes to EW systems. NOTE: The three major types of software that require reprogramming are: For software deficiencies, the RCs: AFMC: The RCs guide units in operating new or
modified EW systems. AFSOC/DO develops and implements EW tactics for special missions. USAFAWC develops and implements EW tactics for the CAF.
3.1.4. Communications. The TCCs let intelligence, the RCs, and units rapidly exchange:
  • Reprogramming data.
  • Mission data.
  • Software.
  • Operational guidance.
  • Text and binary data. Units usually transmit reprogramming data and messages via AUTODIN. The RCs ensure that the TCCs receive AUTODIN-compatible data. Units may use backup methods such as: Agencies and units must:
3.1.5. Implementation. The RCs and AFMC support agencies send reprogramming changes to operational units. The MAJCOM/DO or JFACC/CFACC/AOC reviews the RC and AFMC changes and prepares an IMP upon approval. The units make the reprogramming change after receiving the IMP. The units support EWIR changes with trained personnel and the appropriate equipment.

3.2. EWIR Deficiency Reporting. Organizations and individuals performing EWIR must identify EW deficiencies via the operational change request (OCR) (see attachment 3). EW deficiencies may come from:

3.2.1. OCR Logistics: CAF units may start a change by sending an OCR directly to the RC. The RC prioritizes and evaluates the OCR and suggests methods for implementing it. HQ ACC/DO (with USAFE and PACAF) or HQ AFSOC/DO decides the final OCR priority for CAF EW systems. The RC sends the OCR to USAFAWC/EC or DET 1 SOCOS (with an informational copy to MAJCOM/DO/IN/LG or equivalent) through the wing or group DSO, EWO, or ECO. The RC may send more than one request on a specific system but must identify each request. The RC sends final approved OCR to AFMC when the OCR affects the OFP, system hardware, and so forth.
3.2.2. Prioritizing OCRs. The OCR originator prioritizes OCRs using these designators: Originators submit emergency OCRs (Priority E) with an IMMEDIATE message: Emergency changes are worked by the RCs on a 24-hour basis until complete. Originators submit urgent OCRs (Priority U) with an IMMEDIATE or PRIORITY message: Urgent changes will be worked by the RCs full-time during normal duty hours, with a completion goal of 10 days, and take precedence over any other activity. EXCEPTION: Emergency changes. Originators submit routine OCRs (Priority R) with a ROUTINE message when: Routine OCRs are scheduled and included in block cycle updates for the affected EW equipment.
3.2.3. OCR Change Types. The RCs designate a change in one of three ways: The operational command may authorize Type U changes, although outside agencies may serve in an advisory capacity. Type U changes include: AFMC implements Type L changes. These changes: AFMC implements Type S changes when it acquires a new system. NOTE: AFMC works closely with operational commands to help meet their require-ments.
3.2.4. Distributing Reprogramming Changes. Depending on the type, priority, and scope of the change and the degree of unit connectivity, RCs and AFMC distribute changes via: Each change package includes: A deployed operational unit, or a unit moving from its deployed position, must contact (in writing) the applicable Mobile COMM Center responsible for providing connectivity to the unit during deployment. To receive EWIR data on time, deployed units must:
3.3. Implementing Changes. When the MAJCOM or the JFACC/CFACC/AOC directs, operational units implement software reprogramming changes (and report delays) rapidly to ensure mission success and to protect aircrews and aircraft. Units use these messages to give commands and aircrews information on EWIR changes:
3.3.1. Threat Impact Message (TIM). The appropriate RC sends the TIM to the MAJCOM or air command and operational units. This message:
3.3.2. Reprogramming Impact Message (RIM). The appropriate RC sends the RIM to operational units. This message:
3.3.3. Maintenance Instruction Message (MIM). The RC sends the MIM, which provides maintenance uploading instructions, to operational units with the EWIR changes for an EW system.
3.3.4. Implementation Message (IMP). (See attachment 4.) The MAJCOM or JFACC/CFACC/AOC prepares the IMP, which notifies operational units to implement a specific EW software change.
3.3.5. Time Compliance Technical Order (TCTO). The appropriate air logistics center (in most cases, WR-ALC) sends the TCTO to unit maintenance personnel.
This message includes detailed maintenance instructions for:
3.3.6. Unit Loading Message (ULM). (See attachment 5.) Units send the ULM to the MAJCOM, appropriate RCs, JFACC/CFACC/AOC (when activated), and AFIWC after the units have finished implementing a command. This message reports the upload status.
3.3.7. Summary Message (SUM). The RCs send the SUM to the MAJCOM or the air commander when the MAJCOM requests. This message:
3.4. Reporting. Within 72 hours after SERENE BYTE exercises or when PACER WARE activity requires, operational units report this information to the MAJCOM, RCs, JFACC/CFACC/AOC, AFIWC, and other appropriate addressees:
3.4.1. These reporting requirements are exempt from Report Control Symbol (RCS) licensing in accordance with AFI 37-124, Management and Control of Information Reports Requirements (formerly AFR 4-38).


Chapter 4


4.1. General. The Air Force must assess its EW reprogramming and conduct reprogramming exercises periodically to:
4.1.1. MAJCOM Inspector General Operational Readiness Inspections. These inspections give units a chance to evaluate EW reprogramming.
4.1.2. Security Precautions. Units must:
4.1.3. SERENE BYTE Exercises. Units hold SERENE BYTE exercises with other exercises to stress communication and cooperation.
4.1.4. Exercise Categories. Reprogramming exercises fall into these three categories:
4.2. Annual Exercises. SERENE BYTE annual exercises:
all major components of reprogramming, including:
  • Collecting and distributing intelligence information.
  • Evaluating signals.
  • Distributing changes.
  • Implementing changes.
  • Validating equipment changes in combat units.

4.3. Quarterly Exercises. These exercises:
4.3.1. Frequency of Exercises. Units conduct these EW reprogramming exercises as directed. EXCEPTION: Within one month of the annual exercise. (The annual exercise serves as a quarterly exercise.)

4.4. Local Exercises. Units may:


Chapter 5


5.1. Purpose. EWIR supports EC programs with allied and friendly air forces through various agreements and security assistance programs. The purpose is to foster a greater combined war capability.

5.2. Scope. The two basic areas of EWIR support are international agreements and security assistance programs.
5.2.1. International Agreements. These agreements may:

5.2.2. Security Assistance Programs. These agreements: The Electronic Combat International Security Assistance Program (ECISAP) manages the electronic combat aspects of FMS agreements.

5.3. Objectives. EWIR support of allied and friendly nations follows the US Air Force EWIR process. Procedures, actions, and organizational responsibilities outlined in chapters 2, 3, 4, and this chapter form the basis for EWIR support of international agreements and security assistance programs. Allied and friendly nations receive EC system hardware and software that:

5.4. Special Factors. Transferring US Air Force military
capability to foreign nations and managing EC programs with them involve these special factors:
5.4.1. Contractual Relations. International agreements and security assistance programs are Generally contractual in nature. Program changes that require alter-ing supporting documents (such as the memorandum of understanding, FMS case, bilateral or multilateral agreement, and so forth) may require the foreign nation to agree to the change.
5.4.2. Funding. Foreign nations must fund FMS programs at no cost to the US Government. Both the United States and the foreign nation normally fund programs based on international agree-ments.
5.4.3. Disclosure. The transfer of US military information to a foreign nation must take place in accordance with National Disclosure Policy. EC military information includes:
5.4.4. Time Factor. The time required to implement or change a program may depend on the need to gain the nation's agreement or proper funding.
5.4.5. Currently Established Programs. Some currently established EC programs may require a transition period to adapt to this instruction. Manage this transition in accordance with the CRLCMP or the corresponding document for each program or EC system.
5.4.6. Projected Programs. Programs involving future US Air Force EC systems must set themselves up according to chapter 2 and this chapter.
5.4.7. Foreign and Non-US Air Force EC Systems. ECISAP generally does not support:
  • EC systems that the US Air Force does not currently use.
  • Foreign-sourced and US commercial systems not in the US Air Force inventory. ECISAP supports retired US Air Force EC systems to the maximum extent possible, although the foreign nation entirely funds this support.

5.5. Functional Responsibilities. Responsibilities follow chapter 2 of this instruction. These additional specific responsibilities cover EWIR support of allied and friendly air force programs.
5.5.1. Secretary of the Air Force: The Deputy Assistant Secretary of the Air Force for Acquisition Programs (SAF/AQ) coordinates system acquisition for the US Air Force and foreign nations. Within SAF/AQ, the Electronic Combat Division
(SAF/AQPE) oversees EC systems acquisition. The International Programs Division (SAF/AQXI) negotiates non-FMS agreements such as cooperative development, data exchange, and so forth. The Deputy Under Secretary of the Air Force for International Programs (SAF/IA) oversees security assistance policy and program execution. The Policy Division (SAF/IAD) sets up and implements the US Air Force disclosure of military information to foreign nations. This implementation takes place according to: The Systems Division (SAF/IAS) co-chairs the FMS ECWG and provides:
5.5.2. HQ USAF: The Deputy Chief of Staff for Operations (HQ USAF/XO) oversees EC operations. Within HQ USAF/XO, the Electronic Combat Division (HQ USAF/XOFE) oversees ECISAP EC operations and co-chairs the FMS ECWG. The ECWG: The Assistant Chief of Staff for Intelligence, Director of Special Matters (HQ USAF/INJ):
5.5.3. Air Combat Command: The Director of Operations (ACC/DO) oversees combined operations and security assistance programs. The Training and Tactics Division (ACC/DOT): The Operational Readiness Division (ACC/DOX)
plans and executes training exercises. The Electronic Security Division (ACC/DOI) helps other USG agencies with an interest in EWIR. The US Air Force Air Warfare Center (USAFAWC) is the Air Force Reprogramming Center (RC) for Operational Mission Data (MD). USAFAWC:
5.5.4. Air Force Materiel Command: The Air Force Security Assistance Center (AFSAC) manages a broad array of security assistance programs, including: The Aeronautical Systems Center (ASC) provides: The EC System Program Office (SPO) (ASC/RW) plans, develops, acquires, produces, and integrates ECs. Warner Robins Air Logistics Center (WR-ALC) provides system management and logistics support for most US Air Force EC systems. The Directorate of EC systems (WR-ALC/LN) modifies, maintains, and provides logistics support for EC systems. The International Logistics Division (WR-ALC/LNI) helps allied and friendly nations by: Ogden Air Logistics Center (OO-ALC) programs aircrew training simulators. Sacramento Air Logistics Center (SM-ALC) programs training range simulators. Oklahoma City Air Logistics Center (OC-ALC) programs the E-3's Electronic Support Measures (ESM) system. Air Force Developmental Test Center (AFDTC) operates the EC range at Eglin AFB and provides development testing to allied and foreign nations. AFMC/INF manages AFMC's disclosure of military information to foreign nations. NOTE: Each ALC also has an office that helps with that ALC's programs.
5.5.5. Air Intelligence Agency (AIA): The National Air Intelligence Center (NAIC):

5.6. US Air Force Management:
5.6.1. FMS EC Working Group (ECWG). The FMS ECWG, when HQ USAF/CC directs, develops, recom-mends, and oversees the export of US Air Force EC systems and system support. HQ USAF/XOFE co-chairs the FMS ECWG with SAF/IASW. Additional members come from: Nonvoting members that provide technical support to the FMS ECWG are: After staffing and approval, FMS ECWG actions become HQ USAF/CC Memorandums of Policy for EC systems. The FMS ECWG may act in an advisory or subcommittee role for the EWIR oversight committee. The FMS ECWG oversees the US Air Force's ECISAP.
5.6.2. Electronic Combat International Security Assistance Program (ECISAP). ECISAP provides acquisition, logistics, technical engineering, and training services to ensure the effectiveness of EC systems that the US Air Force sells to allied and friendly nations. This support provides the standardization and dependability that participating ECISAP member nations need to field effective EC systems. ECISAP acts in accordance with: Because it mimics similar US Air Force EC systems, ECISAP does not require the involvement of all
US Air Force agencies when it manages FMS programs. ECISAP may both use EWIR and support EWIR. WR-ALC/LNI, International Logistics Division, normally chairs ECISAP meetings on behalf of the individual EC system managers. The key ECISAP administering agencies are: The ECISAP implementing agencies are:
5.6.3. Additional EWIR-Supported Programs: SERENE BYTE and PROUD BYTE exercises may include allied and friendly nations to demonstrate US Air Force support and provide training. Training exercises with allied and friendly nations may include EWIR support. NOTE: Repro-gramming EC systems can enhance the quality of combined training in such exercises as Red Flag or Bright Star. The US Air Force participates in a number of combined and joint programs. Many of these programs (such as NATO E-3 ESM, data exchange agreements, material evaluations, and so forth) might depend on EWIR.
5.6.4. Security of International Transmissions. Set up secure transmission channels for the physical transfer of documents and software or the electronic transfer of data. NOTE: Electronic transmission is the desired method.

5.7. Mission Data Responsibilities:
5.7.1. General. The ECISAP encourages US Air Force agencies to interact and cooperate so that allied and friendly nations receive effective and supportable EC systems. (Paragraph 5.4 outlines basic considerations in supporting foreign nations.) The value of the resulting combined war capability depends on WR-ALC and USAFAWC coordinating MD reprogramming effectively. USAFAWC serves as the source of MD expertise. Both WR-ALC and USAFAWC maintain RC and communication capabilities. USAFAWC provides all ECM jamming techniques and matrices.
5.7.2. US Air Force Inventory Systems: USAFAWC generates the MD and coordinates it with WR-ALC/LNI before delivering it to each nation. EXCEPTION: Under emergency reprogramming conditions, USAFAWC delivers the MD to the nation and coordinates the delivery at the same time with WR-ALC/LNI. When USAFAWC MD generation is not available, WR-ALC generates and distributes the MD after coordinating it with USAFAWC, as in paragraph
5.7.3. Non-US Air Force Inventory Systems: WR-ALC generates and distributes MD to those nations that keep EC systems no longer in the active US Air Force inventory. WR-ALC works with USAFAWC to use MD expertise that might still exist for these systems.

5.8. Operational Procedures. Each nation's CRLCMP contains operational procedures that detail such actions as block cycle responsibilities.

5.9. Intelligence. The intelligence community provides necessary intelligence information for producing and maintaining EC software and tactics. Its primary product is the country-specific EWIRDB, which NAIC produces with input from the AFIWC and NSA.

5.10. Communications. Communications is key to rapidly distributing:

5.10.1. US Air Force EWIR communication procedures form the basis for deliveries to foreign nations.
5.10.2. The ECISAP RCs manage the primary communication link, which is the STU-III/DCS to STU-III/DCS (or STU-IIIA/DCS to STU-IIB/DCS). (See the Country and System CRLCMP for details.) This link provides the necessary connectivity for transmitting text and binary data between the RCs and foreign nations (see paragraphs 5.7.2 and 5.7.3).

5.11. Support. ECISAP operational, technical, and logistics support comes primarily from WR-ALC and USAFAWC.
5.11.1. USAFAWC provides tactics and operational considerations for using US Air Force EC equipment.
5.11.2. WR-ALC/LNI helps with contracting, technical assistance, logistics support, and hardware and software configuration control.

DCS/Plans and Operations

Section A--Abbreviations and Acronyms

and Acronyms Definitions

ACC Air Combat Command
AECAT AFIWC Electronic Combat Analysis Team
AFAT AFIWC Flagging Analysis Team
AFDTC Air Force Developmental Test Center
AFIWC Air Force Information Warfare Center
AFMC Air Force Materiel Command
AFRES Air Force Reserve
AFSAC Air Force Security Assistance Center
AFSAT Air Force Security Assistance Training
ARAT Army Reprogramming Analysis Team
ASC Aeronautical Systems Center
AUTODIN Automatic Digital Network
BBS Bulletin Board System
CACC Combat Air Control Center
CAEWIS Computer Aided Electronic Warfare Information System
CAF Combat Air Forces
CFACC Combined Forces Air Component Command
CID Combat Intelligence Division
COE Center of Excellence
COMSEC Communications Security
CPIN Computer Program Identification Number
CRISP Computer Resource Integrated Support Plan
CRLCMP Computer Resources Life Cycle Management Plan
CRWG Computer Resource Working Group
DCS Digital Computer System
DDN Defense Data Network
DIA Defense Intelligence Agency
DISN Defense Information Systems Network
DISUM Defense Intelligence Summary
DSO Defensive Systems Officer
DSSCS Defense Special Security Communications Systems
EC Electronic Combat
ECAC Electromagnetic Compatibility Analysis Center
ECISAP Electronic Combat International Security Assistance Program
ECO Electronic Combat Officer
EC PGM Electronic Combat Product Group Manager
ECWG Electronic Combat Working Group
EID Emitter Identification Data
ELINT Electronics Intelligence
ERC Emergency Reprogramming Center
ESM Electronic Support Measures
EW Electronic Warfare
EWAISP Electronic Warfare Avionics Integration Support Program
EWIR Electronic Warfare Integrated Reprogramming
EWO Electronic Warfare Officer
FLTREP Flight Report
FMS Foreign Military Sales

and Acronyms Definitions

FSTC Foreign Science and Technology Center
ICWG Interface Control Working Group
IDB Integrated Data Base
IMP Implementation Message
IPC Intermediate Processing Center (AIC, IPAC, JACEUR, 20 AIS)
IV&V Independent Verification and Validation
JAC Joint Analysis Center
JCS Joint Chiefs of Staff
JEWC Joint Electronic Warfare Center
JFACC Joint Forces Air Component Command
JFMO Joint Frequency Management Office
JIC Joint Intelligence Center
MAXI Modular Architecture for the Exchange of Intelligence
MD Mission Data
MDCCB Mission Data Configuration Control Board
MIID Military Integrated Intelligence Data Systems
MIM Maintenance Instruction Message
MISREP Mission Report
MLV Memory Loader Verifier
MNS Mission Needs Statement
MOP Memorandum of Policy
MSIC Missile and Space Intelligence Center
NAIC National Air Intelligence Center
NGB National Guard Bureau
OC-ALC Oklahoma City Air Logistics Center
OCR Operational Change Request
OFP Operational Flight Program
OI Operating Instruction
ONI Office of Naval Intelligence
OO-ALC Ogden Air Logistics Center
OPR Office of Primary Responsibility
OPREP Operational Report
OPSEC Operations Security
ORD Operational Requirement Document
OT&E Operational Test and Evaluation
PFM Pre-Flight Message (Obsolete terminology - use Mission Data)
PLV Program Loader Verifier
POC Point of Contact
RC Reprogramming Center (USAFAWC, DET 1 SOCOS, and WR-ALC)
RCS Report Control Symbol
RIM Reprogramming Impact Message
SARAH Standard Automated Remote to AUTODIN Host
S&TI Scientific and Technical Intelligence
SCCSB Software Configuration Control Subboard
SEAD Suppression of Enemy Air Defenses
SIFT Selectively Improved Flagging Technique
SM-ALC Sacramento Air Logistics Center
SPO System Program Office
STRATCOM Strategic Command
TCC Telecommunications Centers
TCTO Time Compliance Technical Order
TCVM Threat Change Validation Message

and Acronyms Definitions

TCVR Threat Change Validation Request
TIM Threat Impact Message
TO Technical Order
ULM Unit Loading Message
USG US Government
WARM Wartime Reserve Modes
WR-ALC Warner Robins Air Logistics Center

Section B--Terms

AUTODIN--The Automatic Digital Network (AUTODIN) system is the primary means to distribute changes to all operational field units with a floppy disk capability. It can transmit text changes to previous guidance/procedures and direct implementation of new ones. It can also transmit specially prepared digital data to update electronic warfare software at the field units. The reprogramming centers are responsible for ensuring an AUTODIN-compatible product is delivered to the telecommunications center (TCC). The TCC is responsible for the actual transmission and distribution of the product to the user.

Block Cycle--The controlled and recurring process of improving software through regularly scheduled updates. These routine changes are generally made annually for Operational Flight Programs and Mission Data.

BRAVE BYTE--The nickname for exercising Army electronic warfare system changes.

Bulletin Board System (BBS)--Currently, the electronic BBS is a secondary means of transmitting digital data to operational locations. The BBS uses the STU-III/DCSs to transmit digital data, via commercial or Defense Switch Network (DSN) voice lines, from reprogramming centers directly to operational locations which possess STU-III/DCSs and appropriate communications software. Since the BBS is a "pull" system, units must be notified by message or telephone that new mission data software has been loaded on the BBS. With the implementation of the Defense Message System, the BBS may become the secondary source for the transmission of reprogramming data.

Certification--The process by which reprogramming centers test that a given software change or update is operationally suitable for implementation.

Electronic Warfare Integrated Reprogramming (EWIR)--The process that fully integrates operations, intelligence, communications, logistics, and other support functions to provide changes to reprogrammable electronic warfare equipment (EW) hardware and software, tactics, and equipment settings. EWIR gives the Air Force a clear and comprehensive picture of tasks, data, staffing, and the interrelationships between the agencies that reprogram EW equipment. This process forms the basis for developing Air Force procedures, organizations, facilities, and expertise to ensure responsive EW reprogramming during peacetime, wartime, and contingencies.

EWIRDB--The database managed by the that contains parametric data describing radar and ECM systems. Scientific and Technical Intelligence Centers, Air Force Information Warfare Center, Army, Navy, and National Security Agency provide the data, and National Air Intelligence Center compiles it. This is the primary data source for mission data.

EWIR Oversight Committee--An officer committee, chaired by HQ USAF/XOFE, that oversees Air Force Electronic Warfare Integrated Reprogramming. Permanent committee members include representatives from Air Combat Command, Air Force Materiel Command, Air Force Special Operations Command, San Antonio Air Logistics Center, Warner Robins Air Logistics Center, US Air Force Air Warfare Center, Air Force Information Warfare Center, National Air Intelligence Center, Aeronautical Systems Center, Defense Intelligence Agency, National Security Agency, US Air Forces Europe, Pacific Air Forces, Air Mobility Command, HQ USAF/LGM/INX/SCM, and SAF/AQP. The chairperson may call for additional members. The committee meets annually or as the chairperson requests. The committee reviews subcommittee reports, discusses and resolves program deficiencies, and monitors corrective actions.

Firmware--The combination of hardware device and computer software that resides as read-only memory on the hardware device. The software cannot be readily modified under program control.

Flagging--Comparing observed threat data to the data programmed in an electronic warfare system to determine if the system will be correctly identified. Air Force Information Warfare Center maintains automated flagging models.

Implementation--Major command or Joint Forces Air Component Command, Combined Forces Air Component Command, or Air Operations Center approval to load a change that the reprogramming centers have given to electronic warfare systems.

Mission Data (MD)--Elements or files that a computer uses to perform signal discrimination or elicit jammer responses, which are selectable, adjustable, or changeable by the using command. MD is also called Emitter Identification Data (EID) or Pre-Flight Message (PFM).

Neptune Byte--The nickname for exercising Navy electronic warfare system changes.

Operational Change Request (OCR)--A formal request to the appropriate major command and support command facilities that identifies the inability of an electronic warfare system to meet operational requirements. In emergencies, an OCR identifies the inability to discriminate or respond to a threat and then requests mission data or operational flight program (OFP) changes to correct the problem.

Operational Flight Program (OFP)--The executable program resident in computer-controlled electronic warfare systems that contains the algorithms that receive, identify, process, and do jamming tasks. This program does not contain any threat-specific data, and operational commands cannot change the program. The reprogramming centers send an operational change request to Air Force Materiel Command to get an OFP modified.

PACER WARE--The nickname for actual electronic warfare system changes, either routine, urgent, or emergency.

PROUD BYTE--The nickname for the joint exercising of electronic warfare systems.

SERENE BYTE--The nickname for Air Force exercise and training reprogramming changes.

Validation--The integration, testing, and evaluation performed at the system or subsystem level to ensure that the final program satisfies the system specifications and user or supporting command requirements.

Verification--The evaluation to determine whether the product of one step of the development process fulfills all the requirements levied by the previous step.

















NOTE: HQ PACAF and HQ USAFE attend subcommittee meetings as they wish and when HQ USAF/XOFE directs.

Key: C = Chairman; X = Member; O = Observer

Figure A2.1. EWIR Subcommittee Membership Matrix.


SUBJ/PACER WARE OCR ALR-56C PW 91 AWF001// (See attachment 6 for message designation standards.)

REF/A/MSG/68 ECG CC/123456ZJAN91// (Reference all previous, pertinent messages.)

AMPN/REF A IS TIM ALR56C PW 91 AWF001 (List the previous message applicable to this OCR. For example: If a TIM preceded this message it will be listed; if a TVM generated this message it is listed.)





C. {?} (Describe signal parameters causing change and the approach to reprogramming.) ELNOT, THREAT NAME, AND PARAMETER AFFECTING REPROGRAMMING APPROACH

D. {?} (Describe the specific mission data changes requested.)


4. {U} (List TIMs included/unresolved/canceled.)

5. {U} (Contact instructions.)



A3.1. This message attempts to follow the US Message Text Format (USMTF) General Administrative (GENADMIN) message format. Originators will ensure the complete message complies with USMTF.

A3.2. Each message identification number (e.g., OCR ALR-56C PW 91 AWF001) MUST be complete on a single line. Do not break the string (OCR ... AWF001) to continue it on another line.

A3.3. Multiple message identification numbers must be separated by a comma (,).

A3.4. For current address listings, refer to the Air Force Plain Language Address Directory.

A3.5. For exercise messages use SERENE BYTE in place of PACER WARE. Do not use both.


SUBJ/PACER WARE IMP ALR-56C PW 91 ACC001// (See attachment 6 for message designation standards.)

REF/A/MSG/68 ECG CC/123456ZJAN91// (Reference all previous, pertinent messages.)

AMPN/REF A IS RIM ALR-56C PW 91 AWF001// (Reference could be a RIM, TCT or MIM.)


2. {?} (MAJCOM authorization to install referenced software change.)


4. {U} (Contact instructions.)



A4.1. This message attempts to follow the US Message Text Format (USMTF) General Administrative (GENADMIN) message format. Originators will ensure the complete message complies with USMTF.

A4.2. Each message identification number (e.g., IMP ALR-56C PW 91 ACC001) MUST be complete on a single line. Do not break the string (IMP...ACC001) to continue it on another line.

A4.3. Multiple message identification numbers must be separated by a comma (,).

A4.4. For current address listings, refer to the Air Force Plain Language Address Directory.

A4.5. For exercise messages use SERENE BYTE in place of PACER WARE. Do not use both.


SUBJ/PACER WARE ULM ALR-56C PW 91 FFA001// (See attachment 6 for message designation standards.)

REF/A/MSG/68 ECG CC/123456ZJAN91// (Reference all previous, pertinent messages.)



2. {?} THE ______(unit name, i.e., 1FW) HAS COMPLETED LOADING OF REF CHANGE. LOADING COMPLETE: (DTG in ZULU) i.e., 123456Z JAN 91. (Units should ensure any pertinent information is included in this message, to include delays in loading, problems encountered, etc.)

3. {U} (Contact instructions.)



A5.1. This message attempts to follow the US Message Text Format (USMTF) General Administrative (GENADMIN) message format. Originators will ensure complete message complies with USMTF.

A5.2. Each message identification number (e.g., ULM ALR-56C PW 91 FFA001) MUST be complete on a single line. Do not break the string (ULM...FFA001) to continue it on another line.

A5.3. Multiple message identification numbers must be separated by a comma (,).

A5.4. For current address listings, refer to the Air Force Plain Language Address Directory.

A5.5. For exercise messages use SERENE BYTE in place of PACER WARE. Do not use both.


(1) (2) (3) (4) (5, 6)

(1) Type of Message:

TVR: Threat Change Validation Request
TVM: Threat Change Validation Message
OCR: Operational Change Request
TIM: Threat Impact Message
EDD: Estimated Distribution Date Message
RIM: Reprogramming Impact Message
MIM: Maintenance Instruction Message
TCT: Time Compliance Technical Order
DAT: Data Message
IMP: Implementation Message
ULM: Unit Loading Message
STM: Status Message
RTM: Request for Transmission Message (Foreign Military Sales Only)
RRM: Request for Release Message (Foreign Military Sales Only)
RAM: Release Authorization Message (Foreign Military Sales Only)

(2) Equipment Designation:

Do not use slashes (/) (for example, ALR-56C, ALR-69, and so forth).
Include software and mission data version identifier if required (for example, ALQ-172(V)1-50X).
Include three-letter command or nation identifier for multicommand and multinational systems (for example, ALR-69(KOR), ALQ-172(V)2-50X(SOC)).

(3) Situation Code:

Two letter designation for:

Actual changes (PW - PACER WARE).
Quarterly exercises (Q1 through Q4).
Annual exercise (SB - SERENE BYTE).
Tests (T1, T2, T3...).
Other specified two letter code.

(4) Calendar-Year Designation:

Two number designation for the current calendar year (for example, 91 for 1991, 92 for 1992, and so forth).

(5) Originator's Designation:

ACC Air Combat Command
AWB Air Warfare Center, 513 Engineering and Test Squadron (ETS)
WLA Wright Labs
RLN Warner Robins Air Logistics Center
AMC Air Mobility Command
ANG Air National Guard
AFR Air Force Reserve

Unit Codes: Codes for individual units are based on their distinctive unit aircraft identification markings (tail codes). Provisional units and units without tail codes generate an originator identifier with their MAJCOM.

(6) Three-Digit Sequence Number Designation:

Number each message sequentially by system and message type (for example, 001 for the first ALR-69 OCR, 002 for the next ALR-69 OCR, and so on). NOTE: The first RIM for an ALQ-184 reprogramming action will also be 001. Do not attempt to follow other originators' numbering sequences.