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

Attachments
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

____________________________________________________________________________________________________

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

• Air Force agencies communicate fully in coordinating peacetime, contingency, and wartime operations.
• Theater commanders stay aware of force employment options and inform essential EWIR organizations (such as reprogramming centers [RC] and flagging assets).
  

• Tactics.
• Employment guidance.
• Support operations and equipment.
• EW equipment software and hardware.
• Aircrew training devices.
• Threat simulators and emitters.
• Other support systems.

• EW systems acquisition.
• Testing.
• Tactics development.
• Employment guidance.
• Training.
• Automated mission planning.
• Weapons allocation and targeting.
  

• Tactics.
• Employment guidance.
• Doctrine.
• Training.
• An effective operational response to enemy actions.
  

____________________________________________________________________________________________________

• Intelligence databases.
• Mission data.
• Operational flight programs.
• Support documentation.
  

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.
  

• Data automation.
• Test capabilities.
• Communication connectivity.
• Support equipment.
  

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.
  

• Operational Flight Programs (OFP).
• EW system support tools.
• Support equipment software.
  

2.4. Air Intelligence Agency (AIA):
2.4.1. The Air Force Information Warfare Center (AFIWC):
2.4.1.1. Plans, implements, and manages the annual, worldwide SERENE BYTE exercise to assess EWIR effectiveness. As part of this effort, AFIWC:

• Ensures that SERENE BYTE participants identify, collect, and report the elapsed times between critical EWIR elements.
• Confirms findings.
• Suggests improvements.
  

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.
  

• NAIC.
• Missile and Space Intelligence Center (MSIC).
• Foreign Science and Technology Center (FSTC).
• Office of Naval Intelligence (ONI).
• AFIWC.
  

• HQ USAF/IN.
• Appropriate national intelligence production centers.
  

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.
  

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

• Assigning focal points for SERENE BYTE reprogramming exercises.
• 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.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.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:

• Ensure interoperability.
• Avoid EW frequency conflicts.
  

• Radar parametric changes.
• New threat systems.
• Known systems showing new or unusual electronic emissions and capabilities.
• Changes to reserve and wartime parameters and to modes of operation.
• Unusual EW equipment.
  

• Operational reports (OPREP).
• Mission reports (MISREP).
• RC messages (RIM, TIM, MIM, and so forth).
• Flight reports (FLTREP).
  

• Unusual EW equipment.
• Changes in engagement tactics.
• Changes in successful engagement rates.
  

• Notifies aircrews of loss and degradation of EW capability.
• Uses new tactics.
• Avoids certain threat areas (if feasible).
• Diverts attack forces to other targets.
• Uses Suppression of Enemy Air Defenses (SEAD) assets.
• Reviews TIM recommendations.
  

• Its assessment of the change.
• Planned force movement.
• Critical timing.
  

• EW flagging output from the AFAT.
• EW analysis from the AFIWC EC analysis team (AECAT).
  

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:

• Develop plans and instructions.
• Assign EW reprogramming tasks.
• Develop procedures for receiving and distributing EWIR (PACER WARE/SER-ENE BYTE) messages.
• File letters at the TCC for receiving EWIR messages.
  

• Test plans.
• Test results.
• Messages.
• System handbooks.
• EC mission guides.
  

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.16. EWIR Committee and Subcommittee Inter-operability:
2.16.1. Oversight Committee. HQ USAF/XOFE chairs the Oversight Committee and performs these duties:
2.16.1.1. Notifies applicable DoD agencies of EWIR requirements.
2.16.1.2. Groups all EWIR acquisition programs and funding under a single Electronic Warfare Avionics Integration Support Program (EWAISP), program management directive (PMD), and program officer.
2.16.1.3. Acts as the EWAISP Officer by writing and updating PMD 5092 in accordance with applicable directives.
2.16.1.4. Approves and manages EWAISP funding.
2.16.1.5. 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:
2.16.2.1. Comply with the directives in EWIR-related PMDs, including the EWAISP PMD 5092.
2.16.2.1.1. Subcommittee memberships are provided at attachment 2.
2.16.2.2. Hold meetings at least twice a year and when the Oversight Committee chairperson directs.
2.16.2.3. Write and distribute subcommittee charters and meeting minutes.
NOTE: The EWIR Oversight Committee Chairman approves subcommittee charters.
2.16.2.4. AFMC WR-ALC/LNE chairs the Configuration Management Subcommittee, which:

• Develops and integrates common support software and hardware.
• Reviews EWAISP funding and recommends priorities to HQ USAF/XOFE.
  

• Plans, develops, and integrates new and existing EWIR systems.
• Ensures that new support technology complies with EWIR objectives.
  

____________________________________________________________________________________________________

• Technical, tactical, and organizational information for producing and maintaining EW equipment.
• 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
  

Distributed Production Program.


• Aircrew feedback.
• Air Force Electronic Warfare Center (AFIWC) EW flagging reports.
• Scientific and Technical Intelligence (S&TI) center expertise.
• Other national intelligence sources.
  

• Monitor theater electromagnetic activity for parametric changes.
• Rapidly analyze and distribute validated threat changes to ensure that reprogramming doesn't delay troop assignments.
• Sends a threat change validation message
  

(TCVM) to the RCs and other concerned agencies.

• AFIWC, which serves as the Air Force POC for flagging development and operation.
• AFAT, which provides theater support to the wartime Air Component Commander.
  

• Review intelligence information, OPLANs, test reports, flagging messages, and operational deficiencies that the field, ALC, and RC personnel identify to find all deficiencies in CAF EW systems.
• Correct deficiencies by:
• Reprogramming or modifying exist-ing EW systems.
• Getting new EW systems.
• Developing new tactics and employ-ment procedures.
  

• MD.
• OFP.
• Support software.
  

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

• 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.4. Communications. The TCCs let intelligence, the RCs, and units rapidly exchange:

• Reprogramming data.
• Mission data.
• Software.
• Operational guidance.
• Text and binary data.
  

• STU-III/DCS to STU-III/DCS.
• Bulletin Board Systems (BBS) at the RCs or performed point-to-point.
• Commercial telephone or Defense Switch Network (DSN) lines.
• Courier, US mail, or airlift for distributing reprogramming data.
  

• Send communications identifying threat changes or implementing reprogramming by the fastest means available.
• Confirm transmittals (with appropriate precedence and classification) via electrical message.
  

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:

• New threats.
• Changed parameters of existing threats.
• Aircrew interest in improving system operation.
  

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:

• E (Emergency).
• U (Urgent).
• R (Routine).
  

• To change operational characteristics that might seriously threaten national security.
• When a condition exists preventing an adequate response to a threat, and the situation warrants immediate action.
• To change operational characteristics that might result in fatal or serious injury or extensive equipment damage or destruction.
  

• To change operational characteristics that might seriously threaten mission effective-ness.
• 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.
  

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

• Type U (User).
• Type L (Logistics).
• Type S (System).
  

• Tactics.
• Equipment settings.
• Operational employment procedures.
• Mission data.
  

• Usually fall under the Air Force Modification Program.
• Include hardware and software improve-ments.
  

• AUTODIN.
• Secure digital transmission.
• Military airlift.
• Surface transportation.
• Courier.
• US mail.
• A TCTO.
• A simple message.
  

• The actual change.
• Supporting documentation (such as a RIM, MIM, and so forth).
• Reporting procedures.
  

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

• Describes the impact of threat changes on an EW system.
• Discusses system deficiencies.
• Recommends interim corrections (for example, interim tactics, recommended employment options, and so forth).
  

• Describes in detail how an EWIR change will improve an EW system.
• States the adverse effects of implementing or not implementing the change.
• Helps aircrews and commands decide when or whether to implement a change.
  

• An operational flight program.
• Mission.
• Combination change to a specific EW system.
  

• Summarizes what the RC has done.
• Lists the current versions of all EW systems that the RC manages.

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

____________________________________________________________________________________________________

• Identify problem areas.
• Gain confidence.
• Ensure a smooth flow of information during a crisis.
• Ensure readiness in response to threat parameter changes.
• Train operations, intelligence, communica-tions, and maintenance personnel.
  

• Follow operations security (OPSEC) and communications security (COMSEC) at all times.
• Use secure communications to the greatest extent possible.
  

• Annual.
• Quarterly.
• Local.

• Normally cover the entire EWIR process.
• Require the participation of at least:
  
  • HQ USA.
  • ACC.
  • AIA.
  • S&TI centers.
  • The IPCs.
  • WR-ALC.
  • AMC.
  • AFSOC.
  • DET 1 SOCOS.
  • USAFAWC.
  • AFIWC.
    
• May include allied and friendly nations.
• Document the capabilities and limitations of
  

all major components of reprogramming, including:

• Collecting and distributing intelligence information.
• Evaluating signals.
• Distributing changes.
• Implementing changes.
• Validating equipment changes in combat units.

• Focus on MAJCOM-selected aspects of reprogramming.
• Usually validate the procedures for distributing emergency reprogramming data to operational units.
• Identify shortcomings in communications and support equipment.
  

4.4. Local Exercises. Units may:

• Set up exercises to give personnel a chance to practice reprogramming. NOTE: Higher headquarters may also set up such exercises.
• Decide to conduct limited, periodic repro-gramming exercises after reviewing exercise results.

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:

• Take several forms (for example, cooperative research or data exchange agreements, joint development programs, joint exercises, and so forth).
• Require EWIR support to enhance their effectiveness.
  

• Take the form of foreign military sales (FMS) agreements.
• Represent the majority of EWIR supported programs with allied and friendly nations.
  

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.
  

• Deliverable software.
• Technical orders.
• Operating manuals.
• Tactics.
• Training.
• Technology.
• Threat data base.
  

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.

• AFRs and AFIs covering disclosure.
• A program's Delegation of Disclosure Authorization Letters (DDL).
  

• Security assistance policy.
• Management.
• Operations..
• Weapon system expertise.
• Oversight management for ECISAP.
  

• Reviews the operational impact and sensitivity of EC programs, information, and technology being transferred to allies and friendly nations.
• Sends its findings to the Air Staff for HQ USAF/CC to sign as Memorandums of Policy for EC Equipment.
  

• Reviews requests for US-owned threat emitter data.
• Sends the requests to the appropriate USG agency.
• Sends the resulting database to the organization that needs it to support system design and programming.
  

• Manages security assistance programs.
• Provides detailed ACC EC program management.
• Acts as the ACC foreign disclosure policy office.
• Participates in ECWG and ECISAP meetings.
  

• Acts as the source of MD expertise.
• Programs selected MD (see paragraph 5.7).
• Resolves MD problems.
• Develops operational tactics,.
• Conducts operational flight tests for the ECISAP.
  

• EC system acquisition.
• Logistics support.
  

• EC system planning.
• Acquisition.
• Weapon system expertise.
  

• Maintaining:
• OFP.
• Selected MD (see paragraph 5.7).
• Reprogramming tools.
• Test software.
• Providing configuration control.
• Setting up communication links.
• Changing schedules.
• Distributing EC products.
  

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.

• SAF.
• HQ USAF.
• The MAJCOMs (which manage the export of US Air Force EC systems).
  

• AFIWC.
• USAFAWC.
• WR-ALC.
• Other MAJCOM support agencies involved in the export of US Air Force EC systems, support equipment, and systems support.
  

• HQ USAF/CC Memorandums of Policy for EC systems.
• US Air Force foreign disclosure policies.
• FMS ECWG direction.
• The terms of each FMS program.
  

• AF/XOFE.
• SAF/IASW.
• ACC/DOTS.
• AFSAC.
• Air Force Security Assistance Training (AFSAT).
  

• AF/INJ.
• WR-ALC/LNI.
• USAFAWC.
  

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.
5.7.1.1. USAFAWC serves as the source of MD expertise.
5.7.1.2. Both WR-ALC and USAFAWC maintain RC and communication capabilities.
5.7.1.3. USAFAWC provides all ECM jamming techniques and matrices.
5.7.2. US Air Force Inventory Systems:

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

• System intelligence data.
• Mission data.
• Software.
• Operational guidance.
  

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.

BUSTER C. GLOSSON, Lt General, USAF

DCS/Plans and Operations

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
EWIRDB EWIR Data Base
EWO Electronic Warfare Officer
FLTREP Flight Report
FMS Foreign Military Sales

Abbreviations
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

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

HQ USAF/XOFE X X X X X X
LGMY C X
INJ C X X
SCMB C X

HQ ACC/DOT X
DRW X X X
LGM X SCM X

20 AIS/EEF X

USAFAWC
68 TSS/ESO X X X X
513 ETS/EEP X X X X

HQ AFSOC/DOX X X X
IN X
LGM X
SCT X

HQ AMC/XRS X
LGF X

DET 1 SOCOS X X X

WR-ALC/LNE C X X X
LNR X

SA-ALC/LDA X

AFIWC/OSX X C X
OSR X
DBP X

NAIC/TAE X X

AFMC EC PGM C
ASC/RWX X X X

DIA/DIW-1C X
DTI-4A X

NSA/W27 O O

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.

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

RMKS/1. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.

2. {?} MISSION DATA CHANGE FOR OUT OF PARAMETER SIGNAL(S)

A. {?} PRIORITY: (EMERGENCY, URGENT, or ROUTINE)

B. {?} SYSTEM: (ALR-56C PFM 005041) SYSTEM AND SOFTWARE VERSION

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

3. {U} REQUEST MAJCOM APPROVAL OF THE REQUESTED CHANGE AND DIRECTION TO THE APPROPRIATE REPROGRAMMING CENTER TO BEGIN WORK IMMEDIATELY AND CONTINUE UNLESS DISAPPROVED.

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

5. {U} (Contact instructions.)

6. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.//

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.

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

RMKS/1. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.

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

3. {U} UNITS NOTIFY (MAJCOM) UPON COMPLETION OF INSTALLATION AND IF ANY PROBLEMS ARE ENCOUNTERED.

4. {U} (Contact instructions.)

5. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.//

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.

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

AMPN/REF A IS IMP ALR-56C PW 91 ACC001//

RMKS/1. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.

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

4. {U} THIS IS AN AIR FORCE PACER WARE MESSAGE.//

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.

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

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.

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)
EWC AFIWC
USA HQ USAF
AWI USAFAWC 36 ETS/EEB (FMS Programs)
AWF USAFAWC 68 ECG (USAF Programs)
CEN CENTAF
PCF PACAF
SO1 SOCOS, DET 1 (AFSOC)
SUF SOUTHAF
SOC AFSOC
AFE USAFE
WLA Wright Labs
RLI WR-ALC/LNI
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.