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.

SUMMARY OF CHANGES

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.

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:

2.1. Air Staff:
2.1.1. HQ USAF/XO. The Deputy Chief of Staff for Plans and Operations:
2.1.1.1. Manages EWIR activity.
2.1.1.2. Prepares and implements EWIR-related program management directives (PMD).
2.1.1.3. Resolves EWIR conflicts at the major command (MAJCOM) level.
2.1.1.4. Chairs the EWIR Oversight Committee.
2.1.1.5. Ensures that commanders effectively communicate their EWIR intelligence production requirements to the intelligence community and HQ USAF/IN.
2.1.1.6. Ensures that MAJCOMs practice and evaluate the effectiveness of EWIR by conducting at the least an annual worldwide SERENE BYTE exercise.
2.1.1.7. Oversees the analysis of EW equipment based on potential threats or enemy threat change validations.
2.1.1.8. Develops procedures and coordinates other services for jointly developing and using EWIR resources.
2.1.1.9. 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.
2.1.1.10. Oversees the FMS Electronic Combat International Security Assistance Program (ECISAP) as described in chapter 5.
2.1.1.11. 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:
2.1.2.1. 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.
2.1.2.2. Works with the DIA and JCS to set up procedures for rapidly validating and reporting threat changes.
2.1.2.3. Ensures that commanders document their operational EWIR intelligence requirements and send them to the DIA for action.
2.1.2.4. Provides complete intelligence information to the theater or MAJCOM commander concerning EW system reprogramming for training, exercises, and combat operations.
2.1.2.5. Works with the DIA to ensure that other services and intelligence agencies receive EWIR intelligence support.
2.1.2.6. Chairs the EWIR Intelligence Subcommittee and informs HQ USAF/XO of the committee's progress.
2.1.2.7. Works within the intelligence community to get EWIR products for the RCs to support allied and friendly nations.
2.1.2.8. Coordinates the EWIR efforts of the DIA, JICs, JAC, and S&TI centers in accordance with JCS SM 90-85.
2.1.2.9. Orchestrate intelligence participation in annual SERENE BYTE exercises.
2.1.2.10. 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:
2.1.3.1. Develops an integrated logistics support plan to facilitate multiple, simultaneous EW reprogramming actions.
2.1.3.2. Sets up procedures and agreements to coordinate all phases of EWIR logistics support.
2.1.3.3. Oversees EWIR logistics support (including support equipment and reprogramming tools) to maintain standardization and flexibility.
2.1.3.4. 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:
2.1.4.1. 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:

Intelligence databases.

Mission data.

Operational flight programs.

Support documentation.

2.1.4.2. Acts as office of primary responsibility (OPR) for a comprehensive EWIR communications plan outlining current and future connectivity and data transfer needs.
2.1.4.3. Coordinates with HQ USAF/IN C4 on communications issues unique to EWIR data that Defense Special
Security Communications Systems (DSSCS) process.
2.1.4.4. Provides data to the US Non-Communications Database through JS/J-6 and the Electromagnetic Compatibility Analysis Center (ECAC).
2.1.4.5. 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:
2.1.5.1. Acts as the focal point for foreign military sales of US Air Force EW and EWIR systems to foreign governments.
2.1.5.2. 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.
2.1.5.3. Acts as the OPR for transferring military information to allied and friendly nations.
2.1.5.4. Co-chairs the FMS ECWG to manage policies and procedures for transfer of US Air Force EC capabilities to allied and friendly nations.
2.1.5.5. 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:

Encourage effective exchange of information.

Eliminate duplication of effort.

Achieve mutual joint service support in accordance with Joint Pub 3-51.

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

Reprogramming support tools.

Data transfer equipment.

Support equipment (field and depot-level).

All aspects of software reprogramming and support facilities.

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.
2.3.5.1. Sets up and manages facilities and personnel to
analyze, develop, and test changes to:

Ensures that SERENE BYTE participants identify, collect, and report the elapsed times between critical EWIR elements.

Confirms findings.

Suggests improvements.

2.4.1.2. Designs, manages, and budgets EW equipment flagging and analysis models by coordinating with other agencies.
2.4.1.3. 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.
2.4.1.4. Chairs the SERENE BYTE Exercise Subcommittee and informs HQ USAF/XO of the committee's progress.
2.4.1.5. Trains personnel to provide EWIR support for wartime, contingency, and training operations.
2.4.1.6. Analyzes EWIR actions during wartime, contingency, and training operations as HQ USAF directs.
2.4.1.7. Updates parametric information on US-produced or rest-of-world(ROW) systems for the EWIRDB.
2.4.1.8. Participates in advisory and other groups, as appropriate, to further develop and standardize EWIRDB and EWIR.
2.4.2. National Air Intelligence Center (NAIC):
2.4.2.1. Acts as the DoD executive agent for the EWIRDB as the DIA requires.
2.4.2.2. 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.
2.4.2.3. Accesses the EWIRDB on-line (using DISN or other secure networks) when external organizations request.
2.4.2.4. Distributes the EWIRDB in accordance with DIA rules.
2.4.2.5. Performs accuracy checks on the EWIRDB.
2.4.2.6. Quickly provides outside consumers with S&TI data for reprogramming during exercises and wartime and contingency operations.
2.4.2.7. Predicts the total capabilities of threat systems, including WARM capabilities, when requested, and reports its predictions via the EWIRDB.
2.4.2.8. Participates in advisory and other groups, as appropriate, to further develop and standardize the EWIRDB and EWIR.
2.4.2.9. Coordinates with AFMC and SAF/AQ to provide equipment and support for ground and airborne testing against foreign assets.
2.4.2.10. 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.
2.5.2.1. 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.
2.6.5.1. 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.
2.8.3.1. 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.
2.8.4.1 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):
2.9.3.1. Review operational intelligence requirements to support EWIR.
2.9.3.2. Assess technical and operational ELINT for emergency validation and reporting (using available intelligence products) to the S&TI centers, RCs, AFIWC, and MAJCOM/IN.
2.9.3.3. Appoint intelligence production points of contact and coordinate production efforts among them.
2.9.3.4. Identify and work on improvements to intel-ligence collection and production methods to provide near real-time assessments of technical and operational ELINT.
2.9.3.5. Identify unsatisfied operational intelligence requirements to support EWIR and report them to:

HQ USAF/IN.

Appropriate national intelligence production centers.

2.9.3.6. 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:

NAIC.

Missile and Space Intelligence Center (MSIC).

Foreign Science and Technology Center (FSTC).

Office of Naval Intelligence (ONI).

AFIWC.

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:

HQ USAF/IN.

Appropriate national intelligence production centers.

2.9.7. Provides intelligence support to the RCs during SERENE BYTE and PACER WARE actions.
2.9.7.1. 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:

S&TI production requirements.

General military intelligence require-ments.

All technical and operational intelligence for developing, modifying, or reprogram-ming EW systems.

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.
2.11.18.1. TIMs describe:

The specific effects that these changes might have on the performance of the EW equipment.

Tactical or employment actions to counter the threat.

Specific actions that the RCs are taking to reprogram the EW equipment.

Monitoring exercises and providing re-commendations and comments to head-quarters and other appropriate agencies.

Compiling and sending exercise results and recommendations to the MAJCOMs.

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:
2.13.2.1. 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.
2.13.2.2. Helps implement:

Software.

Equipment settings.

Aircrew tactics changes.

2.13.2.3. Ensures that aircrews receive the appropriate TIMs and RIMs.
2.13.2.4. Ensures appropriate plans, instructions, and responsibilities for EW reprogramming are disseminated at the appropriate levels.
2.13.2.5. Monitors theater operations and intelligence data to identify and assess changes in the EW environment.
2.13.2.6. Integrates EW reprogramming into appro-priate exercise scenarios.
2.13.2.7. 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.6.3. Prepares collection requests with the CID ELINT analyst and sends them to the Collection Management Branch (CMB) when insufficient data exists for assessment.
2.14.6.4. Determines, if possible, the impact of threat parametric and changes in capability on combat EW systems.
2.14.6.5. Notifies the CID Chief, Combat Operations and Combat Plans Divisions, of the impact of threat changes.
2.14.6.6. Requests technical help from the appropriate
MAJCOMs, RCs, and support agencies.
2.14.6.7. Prepares OCRs for newly defined threat changes.
2.14.6.8. Takes any of these actions (but is not limited to them) to minimize the impact of threat changes:

2.14.6.11. Implements alternate distribution procedures (for example, airlift) when it can't transmit reprogramming data.
2.14.6.12. 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:
2.14.7.1. Assesses the threat using theater resources, including:

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.
2.15.3.1. 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.
2.15.5.1. Report SERENE BYTE exercise results in accordance with paragraph 3.4.
2.15.6. The Wing or Group IN:
2.15.6.1. 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.
2.15.6.2. Reviews aircrew debriefings and mission reports for unusual EW equipment that indicates threat changes.
2.15.6.3. Helps the wing or group DSO, EWO, or ECO prepare OCRs.
2.15.6.4. Reports unusual findings in MISREPs.
2.15.7. The Wing or Group DSO, EWO, or ECO:
2.15.7.1. Sets up and directs an EWIR action team consisting of operations, maintenance, intelligence, and communications personnel to:

2.15.7.2. Reviews aircrew and intelligence inputs, including OPREPs and MISREPs, to identify possible EW system deficiencies and prepares an OCR when it finds discrepancies.
2.15.7.3. Keeps aircrews informed on current EW equipment.
2.15.7.4. Briefs affected aircrews on at least RIMs and TIMs prior to their next flight.
2.15.7.5. Briefs aircrews on new EW capability resulting from reprogramming.
2.15.7.6. Briefs aircrews by using all available sources, including:

Test plans.

Test results.

Messages.

System handbooks.

EC mission guides.

2.15.7.7. Works with the operations group (OG) (or equivalent) to prioritize changes for aircraft and maintenance squadrons.
2.15.7.8. Notifies aircraft and maintenance squadrons when it receives implementation messages (IMP).
2.15.7.9. Sends all required EWIR reports and messages to higher headquarters and subordinate organizations as appropriate.

2.15.7.10. 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.
2.15.7.11. Notifies MAJCOM DO and LG representatives (or equivalent) and RCs of unit connectivity status. The notification includes:

AUTODIN plain language address.

The routing indicator for data.

Limitations on communications (such as no floppy disk capability).

EW support equipment.

Telephone and STU-III numbers for both operations and maintenance.

2.15.8. Aircraft and Maintenance Squadrons:
2.15.8.1. 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.
2.15.8.2. Notify wing or group DSO, EWO, or ECO when they receive MD changes.
2.15.8.3. Implement changes only after wing or group DSO, EWO, or ECO approval.
2.15.8.4. Keep the wing or group DSO, EWO, or ECO informed of changes and provide timing data as required.
2.15.8.5. Help staff the EWIR action team.
2.15.9. The Base or Wing/SC:
2.15.9.1. Ensures that telecommunications centers (TCC) comply with information processing instructions and develops OIs to provide instructions for handling EW messages and data.
2.15.9.2. Helps staff the EWIR action team.
2.15.9.3. 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.

NOTE: This subcommittee includes the RCs, their parent MAJCOM, and AFIWC. A complete membership list is provided at attachment 2.
2.16.2.5. HQ USAF/LGM co-chairs (with ASC/RWX) the Acquisition and Logistics Support Subcommittee, which:

Plans, develops, and integrates new and existing EWIR systems.

Ensures that new support technology complies with EWIR objectives.

NOTE: This subcommittee includes the RCs and their parent MAJCOM.
2.16.2.6. 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.
2.16.2.7. HQ USAF/IN chairs the Intelligence Sub-committee, which develops and integrates intelligence production, including parametric data for the EWIRDB.
NOTES:
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.
2.16.2.8. 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.

The EWIRDB, which the Defense Intelligence Agency (DIA) manages and the National Air Intelligence Center (NAIC), Air Intelligence Agency (AIA), distributes.

The order of battles (air, land, sea, radar, and so forth), which are databases of observed weapon systems and their configuration that help define the threat for modern jamming systems. The DIA creates and maintains this product in its Military Integrated Intelligence Data Systems/In-tegrated Data Base (MIIDS/IDB) under the

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:

MD.

OFP.

Support software.

3.1.3.1. For software deficiencies, the RCs:

Reprogram MD and help their MAJCOMs report the changes to AFMC.

Review non-MD changes that AFMC has developed and send them to the MAJCOMs.

Certify all EW software and hardware for operational use.

Use RIMs to guide units when mission data or software changes affect system operation or response.

3.1.3.2. AFMC:

Oversees each weapon system, EW system, and associated support equipment.

May authorize software changes for the reprogramming of each EW system.

Obtains and modifies hardware.

3.1.3.3. The RCs guide units in operating new or
modified EW systems.
3.1.3.4. AFSOC/DO develops and implements EW tactics for special missions.
3.1.3.5. USAFAWC develops and implements EW tactics for the CAF.

3.1.5. Implementation. The RCs and AFMC support agencies send reprogramming changes to operational units.
3.1.5.1. The MAJCOM/DO or JFACC/CFACC/AOC reviews the RC and AFMC changes and prepares an IMP upon approval.
3.1.5.2. The units make the reprogramming change after receiving the IMP.
3.1.5.3. The units support EWIR changes with trained personnel and the appropriate equipment.

3.2.1. OCR Logistics:
3.2.1.1. CAF units may start a change by sending an OCR directly to the RC.
3.2.1.2. The RC prioritizes and evaluates the OCR and suggests methods for implementing it.

3.2.1.3. HQ ACC/DO (with USAFE and PACAF) or HQ AFSOC/DO decides the final OCR priority for CAF EW systems.
3.2.1.4. 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.
3.2.1.5. The RC may send more than one request on a specific system but must identify each request.
3.2.1.6. 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:

When a condition exists preventing an adequate response to threat-associated radar, and the situation is normal but warrants immediate action.

To change operational characteristics that might result in injury or equipment damage.

3.2.2.4. 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.
3.2.2.5. Originators submit routine OCRs (Priority R) with a ROUTINE message when:

The system has a high probability of correctly responding to a threat or can compensate for threat and friendly emitter changes but minor deficiencies exist that may show an error.

The situation is normal and does not warrant immediate action.

The deficiencies or errors are not a hazard to personnel or equipment.

Changes in training MD are desired.

3.2.2.6. 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:

3.2.3.3. 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:

AUTODIN.

Secure digital transmission.

Military airlift.

Surface transportation.

Courier.

US mail.

A TCTO.

A simple message.

3.2.4.1. Each change package includes:

The actual change.

Supporting documentation (such as a RIM, MIM, and so forth).

Reporting procedures.

3.2.4.2. 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.
3.2.4.3. To receive EWIR data on time, deployed units must:

Immediately notify their MAJCOM/DOs (or equivalent) and RCs of their:

Deployed location.

Plain language address and routing indicator (for data).

Operations and maintenance POCs.

DSNs.

Register STU-IIIs with the RCs for BBS connectivity.

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.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:

Summarizes what the RC has done.

Lists the current versions of all EW systems that the RC manages.

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:

A synopsis of reprogramming changes, including start and stop times for:

Receipt of reprogramming data.

Installation of reprogramming changes into the affected EW system, including average loading time per aircraft.

Any problems that a unit encountered.

Recommendations for improving reprogramming procedures.

Any delays in reprogramming, including the reasons and estimated time to comply with the change.

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).

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:

Well-trained personnel fully support (including US Government [USG] technical support) and maintain.

Undergoes testing and documenting according to US Air Force standards.

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.
5.4.2.1. 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:

Deliverable software.

Technical orders.

Operating manuals.

Tactics.

Training.

Technology.

Threat data base.

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.

5.4.7.1. 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:
5.5.1.1. The Deputy Assistant Secretary of the Air Force for Acquisition Programs (SAF/AQ) coordinates system acquisition for the US Air Force and foreign nations.
5.5.1.2. Within SAF/AQ, the Electronic Combat Division
(SAF/AQPE) oversees EC systems acquisition.
5.5.1.3. The International Programs Division (SAF/AQXI) negotiates non-FMS agreements such as cooperative development, data exchange, and so forth.
5.5.1.4. The Deputy Under Secretary of the Air Force for International Programs (SAF/IA) oversees security assistance policy and program execution.
5.5.1.5. 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:

5.5.4.11. 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):
5.5.5.1. The National Air Intelligence Center (NAIC):

Generates EWIRDB products when AF/INJ requests it.

Delivers these products to agencies such as USAFAWC and WR-ALC, which use them to program and reprogram EC systems.

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.
5.6.1.1. HQ USAF/XOFE co-chairs the FMS ECWG with SAF/IASW.
5.6.1.2. Additional members come from:

SAF.

HQ USAF.

The MAJCOMs (which manage the export of US Air Force EC systems).

5.6.1.3. Nonvoting members that provide technical support to the FMS ECWG are:

AFIWC.

USAFAWC.

WR-ALC.

Other MAJCOM support agencies involved in the export of US Air Force EC systems, support equipment, and systems support.

5.6.1.4. After staffing and approval, FMS ECWG actions become HQ USAF/CC Memorandums of Policy for EC systems.
5.6.1.5. The FMS ECWG may act in an advisory or subcommittee role for the EWIR oversight committee.
5.6.1.6. 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.
5.6.2.1. ECISAP acts in accordance with:

HQ USAF/CC Memorandums of Policy for EC systems.

US Air Force foreign disclosure policies.

FMS ECWG direction.

The terms of each FMS program.

5.6.2.2. 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.
5.6.2.3. ECISAP may both use EWIR and support EWIR.
5.6.2.4. WR-ALC/LNI, International Logistics Division, normally chairs ECISAP meetings on behalf of the individual EC system managers.
5.6.2.5. The key ECISAP administering agencies are:

AF/XOFE.

SAF/IASW.

ACC/DOTS.

AFSAC.

Air Force Security Assistance Training (AFSAT).

5.6.2.6. The ECISAP implementing agencies are:

AF/INJ.

WR-ALC/LNI.

USAFAWC.

5.6.3. Additional EWIR-Supported Programs:
5.6.3.1. SERENE BYTE and PROUD BYTE exercises may include allied and friendly nations to demonstrate US Air Force support and provide training.
5.6.3.2. 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.
5.6.3.3. 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.2.1. 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.
5.7.2.2. When USAFAWC MD generation is not available, WR-ALC generates and distributes the MD after coordinating it with USAFAWC, as in paragraph 5.7.2.1.
5.7.3. Non-US Air Force Inventory Systems:
5.7.3.1. WR-ALC generates and distributes MD to those nations that keep EC systems no longer in the active US Air Force inventory.
5.7.3.2. WR-ALC works with USAFAWC to use MD expertise that might still exist for these systems.

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:

System intelligence data.

Mission data.

Software.

Operational guidance.

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).

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.

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).

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.

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.

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.