F-16 MISSION TRAINING CENTER

TERMS OF REFERENCE

I. SYSTEM DESCRIPTION

The Indonesian Air Force (TNI-AU) F-16 Mission Training Center (MTC) is the integrated set of
hardware and software that implement the requirements described herein. The main function of
the F-16 MTC System is to support basic and advanced pilot mission training,
emergency/abnormal procedures, TNI-AU tactics validation, and mission rehearsal in Local Area
Network (LAN) environments, for the TNI-AU F-16 aircraft employment capabilities.

II. SYSTEM PERFORMANCE REQUIREMENTS

II. 1. System Elements

The MTC shall include a two (2) Full Mission Trainers (FMTs), four (4) Weapons and Tactics Trainers
(WTTs), 4 (four) Brief-Debrief Systems (BDSs), and one (1) Scenario Generation System (SGS). The
FMT and WTT shall provide the ability to train the F-16 Block 15 Enhanced MLU configuration and
the F-16 Block 25 IAU configuration. The FMT cockpit configuration shall be based upon TNI-AU F-
16 Block 15 Enhanced MLU aircraft configuration (Limitations for the Block 25 IAU configuration
will exist based upon differences between the Block 15 and Block 25 cockpits).

There shall be two FMTs, four WTTs, and four Brief-Debrief Systems (BDSs) (section 3.3.4) located
at one base in a single facility, secured facility. Accordingly, each FMT shall include one Ownship,
one Instructor-Operator Station (IOS), and one Tactical Environment Simulation (TES). Each WTT
shall include one Ownship, one limited Instructor-Operator Station (IOS), and one Tactical
Environment Simulation (TES).

II. 2. Integrated System Performance

II. 2. 1. Ranges of Training and Mission Operations

The MTC shall support the TNI-AU F-16 aircraft training as defined in Annex 1 - Training Task
List (TTL) from initial qualification, emergency procedures, advanced skills training, upgrade
training (flight lead, instructor, and mission commander), to mission qualification on all
avionics, weapons systems, and flight profiles, as well as TNI-AU tactics validation and mission
rehearsal. The MTC shall support execution of all TNI-AU F-16 employment skills as defined in
Annex 1 - Training Task List (TTL) including: transition, operation of aircraft sensors/systems,
air-to-air, air-to-surface, communications, data links, electronic system interface, and other
TNI-AU F-16 weapons system interactions. The MTC shall support effective accomplishment
of all tasks and procedures identified in the Contractor-developed Training Task List (TTL).

The MTC shall support the following combat missions and operations:

• Fundamental Missions:
- Instrument (INST)
 - Day and night Visual Flight Rules (VFR) and Instrument Flight Rules (IFR) approach
procedures
- Advance Handling (AH)
- Local Area Procedures and Orientation (LAO)
- Tactical Intercepts (TI)
- Offensive Basic Fighter Maneuvers (OBFM)
- Defensive Basic Fighter Maneuvers (DBFM)
- High Aspect Basic Fighter Maneuvers (HABFM)
- Air Combat Maneuvers (ACM)
- Functional Check Flight (FCF)
- Basic Surface Attack (BSA)
- Surface Attack Tactics (SAT)

• Combat Air-to-Air Missions:

- Offensive Counter Air-Air-Escort (OCA-A/Escort)
- Offensive Counter Air-Air-Sweep (OCA-A/Sweep)
- Defensive Counter Air (DCA) – including Beyond Visual Range (BVR) employment

• Combat Air-to-Surface Missions:

- Air Interdiction
- Low-level Strike
- Close Air Support (CAS)
- Forward Air Controller (FAC)
- Offensive Counter Air – Surface (OCA-S)

• Standard Operations:
- EmergencyProcedures
- Out of Control Recovery
- Electronic Warfare and Electronic Countermeasure (ECM) training - Mission
qualification training
- Air refueling training (FMT only)
- Organic tactics validation
- Weapons Procedures and Employment
- Mission rehearsal
- Data link training using Improved Data Modem (IDM)
- Sniper Advanced Targeting Pod (ATP)
- Medium Altitude Operations and Tactics
- Day/Night All-Weather Operations (to include approach procedures
- Alert Conditions and Procedures
- Night Vision Goggle (NVG) operations

II. 2. 2. Networking

All components within the MTC shall be capable of being locally networked together for
performing multi-ship mission training. The Distributed Interactive Simulation (DIS) Network
traffic shall conform to Institute of Electrical and Electronics Engineers (IEEE) 1278.1a-1998
(Version 6). The latency or the delay shall not affect training when operating MTC Ownships
in a LAN. Individual MTC Ownship’s latency shall be no greater than 150 milliseconds.
II. 2. 3. Real-time Operation – Control Input Response

The simulations implemented within each Ownship shall be designed for real-time operation.
Real-time operation requires dataflow latencies and temporal inconsistencies to be minimized
as prerequisite to realistic and accurate simulations of critical combat interactions. For the
MTC, the cumulative (end-to-end) data flow and computational latencies associated with
simulations of real-world systems shall not exceed the latencies in the actual real-world
systems by more than 100 milliseconds, as measured from cockpit stick movement to horizon
movement per Federal Aviation Administration (FAA) latency definition (i.e., excess time from
aircraft response time).

II. 2. 4. Reliability, Availability, and Maintainability (RAM)

The set of FMT, IOS/TES, WTT, SGS, and BDS elements and associated systems used for
training and mission operations are designated as Mission Event Elements. The RAM design
shall presume the worst case that all Mission Event Elements must be operational together as
an integrated system for local missions, while achieving the 90% steady state availability rate.
Where the availability (A) is defined as:

(Actual Training Time)

A = 100 X -------------------------------------- %
(Scheduled Training Time)

Where:
Actual Training Time = (Total Scheduled Hours ) – (Chargeable + Non-Chargeable Lost Hours)
Scheduled Training Time = (Total Scheduled Hours) – (Non-Chargeable Lost Hours)

For purposes of its RAM design, the sustained utilization rate of the Mission Event Elements
is assumed to be 8 hours per day, 5 days per week. The RAM design of the Mission Event
Elements shall not preclude use for surge operations exceeding the sustained utilization rates,
with extended mission hours up to 24 hours per day, for two consecutive days. A failure of the
Mission Event Elements is defined as a loss of any FMT, WTT, IOS/TES, SGS, or BDS element
function or capability (hardware or software) that results in an inability to accomplish the
required training tasks and mission functions.

Failures include, for example:

a. An unplanned interruption in, or delay of, a scheduled training or mission event;
b. An aborted training or mission event;
c. The withdrawal of any Mission Event Element from a local single- or multi-ship
training;
d. Ineffective training or an inability to accomplish training objectives for a scheduled
training event;
e. Inability to accomplish pre-mission briefing or post-mission execution debriefing
activities.
f. The reliability and maintainability of the MTC shall be predicted during design, and
assured in operation. During design, availability shall be predicted based on allocated
reliability (MTBF), maintainability (MTTR), and spares/maintenance strategies.
II. 2. 5. Design and Construction

The MTC will be designed with a flexible and expandable hardware and software architecture
to support evolutionary changes due to capability enhancements and concurrency
requirement updates. These updates will be implemented through an Engineering Change
Proposal (ECP). The TS design will maximize the use of open architecture and commercial-off-
the-shelf (COTS) equipment and software where life cycle cost savings can be realized and
where performance, fidelity, and Environmental Safety and Occupational Health
requirements are not compromised.

II. 2. 5. 1. Electromagnetic Interference

Best commercial practices shall be used to ensure that MTC components do not interfere with
each other or with collocated standard office equipment. The MTC performance shall not be
degraded by collocated standard office equipment, while installed per the Facility
Requirements in the specified operating environment. The MTC shall comply with all
applicable Federal Communications Commission (FCC) requirements for Electromagnetic
Interference (EMI).

II. 2. 5. 2. Facilities Interface and Operating Environment

The MTC shall be designed for compatibility with, to interface to, and to operate within a TNI-
AU- provided facility. Heating, ventilation, and air conditioning (HVAC), electrical power,
telephone service, water and sewer utilities, and office furniture will be provided by the TNI-
AU. A facility fire suppression sprinkler system will be present, and the MTC design shall allow
appropriate clearances to be maintained.

II. 2. 5. 3. Power Conditioning

Electrical Power will be provided at the MTC Facility. The Contractor shall provide a minimum
of one Uninterruptible Power Supply (UPS) system to allow for manual shutdown of the MTC
equipment in the event of loss of facility power. The UPS will be sized to sustain power to the
MTC for 5 minutes following a power interruption and or complete loss of power to allow the
shutdown process to be successfully completed. The MTC shall include compatible interfaces
with the facility power.

II. 2. 5. 4. Cooling

HVAC facility cooling capability will be provided at the MTC Facility. The Contractor shall
propose cooling requirements for the MTC and evaluate the HVAC capabilities during the site-
surveys and provide recommended modifications.

II. 2. 5. 5. Environmental Safety and Occupational Health

The MTC design shall comply with ESOH laws, regulations, and AFOSH standards applicable at
the MTC site to minimize threats to the environment or safety and health hazards to all
personnel operating, using or maintaining the equipment for the life cycle of the system. The
following specific requirements apply:

a. Emergency power off (EPO) switches shall be provided at multiple, easily reached
locations within the cockpits, computer room, IOS, WTT, and BDS to bring the entire
TS to an immediate safe and stopped condition without damage to the MTC or its site
operating environment. The EPO switches shall also be designed, or located, to
prevent someone from accidentally tripping the switch by inadvertently bumping into
or brushing it.
b. The MTC design shall comply with the requirements of AFOSH 91-118, Training
Systems Fire Protection, to minimize safety and health hazards to all personnel using
or maintaining the equipment, whether the MTC equipment is in an operative or non-
operative state. The MTC EPO system shall include interfaces with the facility fire
detection and suppression system, such that all power is removed from MTC
equipment in the event of a facility fire, and to trigger the facility fire suppression
system when a fire is detected.
c. The MTC design should eliminate or minimize the use of hazardous materials during
testing, operation, support and disposal. Hazardous materials which cannot be
eliminated shall be integrated using sound Systems Engineering management. The
MTC design shall minimize and control hazards associated with the inclusion or use of
hazardous or toxic materials and the generation of toxic or noxious gases. In addition,
materials used in the construction of the MTC equipment will not support the
propagation of flame. The MTC shall not generate or use Class I or Class II Ozone
Depleting Substances during operation or disposal. For the purposes of this
requirement, the following are the Class I ODCs and controlled substances that shall
not be used in any MTC system, component or process:
- Halons: 1011, 1202, 1211, 1301, and 2402
- Chlorofluorocarbons (CFC): CFC-11, CFC-12, CFC-13, CFC-111, CFC-112, CFC-
113, CFC-114, CFC-115, CFC-211, CFC-212, CFC-213, CFC-214, CFC-215, CFC-
216, and CFC-217, and the blends R-500, R-501, R-502, and R-503
- Other controlled substances: carbon tetrachloride, methyl chloroform, and
methyl bromide.
d. The following chemicals shall not be used as ODC replacements in situations (e.g., fire
suppression) where inhalation by humans is possible: Tetrafluoroethane (HFC-134a)
and 1,1,1,2,3,3,3 - Heptafluoropropane (HFC-227ea).
e. To the maximum extent possible, the TS shall be designed to avoid the following
materials: Polycyclic Aromatic Hydrocarbons, Cadmium, and Mercury.
f. The MTC shall not contain asbestos, Polychlorinated biphenyls (PCBs), or
Polychlorinated terphenyls (PCTs).
g. The MTC shall be designed to minimize the following materials: Benzene, Chromium,
Dichloromethane, Phenol, Phthalates, Copper, Lead, Nickel, Radon,
Tetrachloralethene, Zinc, Fluorides, Beryllium, Radio-active elements (including
Uranium-238, Thorium, and Tritium), Crystalline Silica, Antimony, Arsenic,
Molybdenum, Thallium, and Vanadium.
h. Materials used in the construction of the equipment shall not support the propagation
of flame.
i. The design shall minimize and control hazards associated with the generation of toxic
or noxious gases.
j. The ambient noise levels generated by the MTC System equipment (excluding
simulation noises during the training operations) shall meet applicable state and local
laws and regulations.
II. 3. Element Performance Requirements

While supporting all integrated system requirements identified in section II.2, the MTC elements
shall conform to the requirements established in this section. The MTC shall consist of all aspects
of hardware and software that present a complete and integrated pilot vehicle interface,
consistent with the behavior, characteristics and performance of the TNI-AU F-16 Block 15
Enhanced MLU and Block 25 IAU fielded aircraft to provide a seamless training experience and
achieve the training tasks in Annex 1 - Training Task List (TTL).

II. 3. 1. Full Mission Trainer (FMT)

The FMTs shall include a high-fidelity, fully-functional NVIS compatible cockpit, a high-fidelity
360-degree out-the-window (OTW) Visual System. Each FMT shall include a realistic
representation of a TNI-AU F-16 fielded aircraft with an immersive, high-fidelity, visual, aural,
and tactile simulation of aircraft functional and operational capabilities. Aircraft performance
characteristics shall be simulated for normal and abnormal flight operations, normal and
abnormal ground operations, weather effects, and emergencies. Each FMT shall be capable
of operating in single-ship and local multi-ship training and mission operations modes. At
initial startup, the FMT shall initialize to a default operational aircraft configuration that is
instructor settable by the IOS. The immersive simulation shall also realistically model
interactions with the external environment, including correlated, visual (OTW and imaging
sensor), tactile, and aural perceptions and electronic combat and sensor capabilities. The FMT
shall provide capability for a stimulated NVG solution using actual TNI-AU-provided goggles.

II. 3. 1. 1. Full Mission Trainer (FMT) Cockpit

The FMT cockpit hardware configuration shall match the physical cockpit configuration of the
TNI-AU F-16A Block 15 Enhanced MLU aircraft as defined by Annex 1 - Training Task List (TTL)
and the TNI-AU F-16 Block 15 Enhanced MLU Cockpit Fidelity Matrix. In accordance with the
TNI-AU F-16 Block 15 Enhanced MLU Cockpit Fidelity Matrix , all cockpit controls, displays,
instruments, and any systems that interface with the aircraft or with pilot personal
equipment, shall include a training level appropriate-fidelity physical (3-dimensional size,
shape, appearance, feel, sound, articulations, movement, location) and functional (displays
and display logic, aerodynamics, handling, engines, avionics, weapons/stores, sensors)
representation of actual aircraft components and subsystems. A physically representative
Data Transfer Unit panel for acceptance of a dummy Data Transfer Cartridge (DTC) shall be
provided. The capability shall emulate the process of loading mission data as in the aircraft to
include reading the contents of the DTC files to determine the necessary mission parameters
for the simulation. An accurate projected simulation of the Head-Up Display (HUD) shall be
included, with physical representation of the HUD structural components (Note: no combining
glass or glass support brackets will be present). Ejection seat hardware shall be physically and
electro- mechanically representative of the aircraft and shall support “strapping in” by pilots
wearing F-16 life support gear (to include connection of the Oxygen hose) and shall support
all seat adjustments available in the aircraft, with the exception that actual ejection
components shall be inert. Cockpit lighting shall be simulated to support all modes of
employment including day and night operations. Cockpit lighting and instruments backlight
and panel lighting shall be NVG compatible with functional lights control.
II. 3. 1. 2. Out-the-Window (OTW) Visual Simulation

Each FMT shall include an OTW visual simulation correlated with all Ownship systems (e.g.,
radar, sensors) and TES simulations. The FMTs shall include a full OTW visual display system.
Visual cues presented to the pilot shall simulate those in the TNI-AU F-16 aircraft and shall not
present false, erroneous, or inappropriate perceptions that would adversely impact pilot
training. The OTW visual simulation shall permit realistic air target distance and closure rate
visual estimation training to achieve the training tasks in Annex 1 - Training Task List (TTL).

II. 3. 1. 2. 1. Out-the-Window (OTW) Visual Display System

The FMTs shall include a full OTW visual display system. Unless otherwise specified, values are
measured from the pilot’s eyepoint and assume processing through all components of the
visual simulation system (Image Generator (IG), image display systems, optics, projection
screen). For integration with the HUD, a pilot viewing volume of +/- 6 inches horizontal and
+/- 3 inches vertical shall be assumed.

II. 3. 1. 2. 1. 1. Field of View (FOV)

The OTW visual display system shall display the full 360 degree horizontal field of view (HFOV)
and a minimum of 130 degree vertical field of view (VFOV) experienced by the pilot in the
aircraft, with the exception of areas occluded by any visual restrictions caused by the aircraft
body or associated external stores.

II. 3. 1. 2. 1. 2. Resolution and Modulation Transfer Function

The horizontal and vertical OTW visual simulation resolution at a minimum of 10% modulation
shall be consistent with the following specification:
a. There shall not be any perceptible degradation in the image acuity, target resolution,
or Modulation Transfer Function (MTF) across projector edge boundaries.
b. The visual display system shall be capable of supporting a mean resolution of less than
or equal to 4.0 arc-minutes per optical line pair with an average deviation from the
mean of less than or equal to 1.0 arc-minutes per optical line pair for any sampled
points that exceed the mean.

II. 3. 1. 2. 1. 3. Luminance

The OTW visual display system shall provide an average luminance for each display channel
that exceeds 7 foot-lamberts. Luminance variation shall not exceed:
a. 20% over a single display channel,
b. 40% over the entire FOV, and
c. 20% across channel boundaries.
II. 3. 1. 2. 1. 4. Contrast

The OTW visual simulation shall achieve a contrast ratio of at least 18:1 as measured with a
full FOV, 50% duty cycle, black and white checkerboard test pattern with each square no larger
than 10 degrees and no smaller than 5 degrees with a white square in the center of each
channel.

II. 3. 1. 2. 1. 5. Channel Matching

Color, contrast, and luminance shall be balanced over the entire OTW visual display with no
perceptible channel- or edge-matching artifacts. Luminance variation shall not exceed 20%
across channel or edge boundaries. Over the entire FOV, the ratio of the lowest measured full-
on luminance to the highest measured full-on luminance shall exceed 70%.

II. 3. 1. 2. 1. 6. Sharpness

The OTW visual simulation shall include anisotropic texturing, adjustable gamma correction,
imperceptible moiré, and imperceptible Mach banding. The quality of polygon and texture
lines and edges shall remain noticeably sharp regardless of raster orientation or perspective
obliqueness. There shall be no smearing or multiple image artifacts in imagery moving
anywhere within the FOV that distract the pilot from accomplishing the required training
tasks.

II. 3. 1. 2. 1. 7. Vergence

The eyepoint-to-image focal plane (eye relief) distances shall exceed 30 inches, with zero dip-
vergence, and no negative vergence. Allowing for normal pilot head movement, the eyepoint-
to- image display distance variation and vergence disparity between the OTW image and any
other image on HUD should be minimized to preclude any noticeable parallax, eyestrain, focus
distractions (e.g. defocus), disorientation, or nausea.

II. 3. 1. 2. 1. 8. Setup and Maintenance

The visual display system shall not require more than 5 minutes recurring time per trainee for
pre-mission adjustment, calibration, or setup to account for pilot-unique physical attributes.
The design shall incorporate maintainability features that provide for the following
adjustments: (a) automatic edge blend geometry correction; (b) color, luminance, contrast,
and convergence calibration; and (c) channel-to-channel blend correction of the visual display.

II. 3. 1. 2. 2. Out-the-Window (OTW) Visual Image Generation System

The OTW visual simulation geometric distortion shall not exceed 1.0 degree, with no pilot-
distracting visual artifacts (including speckle) and no spatial or temporal discontinuities. This
requirement presumes no unrealistic insetting; no dynamic loss of resolution (which can be
caused by interlacing or pixel depth complexity overloads); and no image lag.
The visual simulation shall support visual maneuvering in relation to multiple prioritized
stationary and moving air and ground models (such as: aircraft, missiles, Anti-Aircraft Artillery
(AAA) and ground target sets) represented in the synthetic environment to achieve the
training tasks in Annex 1 - Training Task List (TTL). The visual system shall have the ability to
simultaneously present, at least 250 actively moving and static entities distributed across the
scenario consistent with training objectives. The entities shall be rendered at the highest
detailed version of each entity model appropriate for the viewing distance, including up to:
30% as aircraft; 30% as weapons in flight; 40% as land- or sea-based moving models. To
achieve the training tasks in Annex 1 - Training Task List (TTL), all fixed and moving models
shall be properly obscured by intervening cultural and terrain features as seen from all
sensors, weapons, and OTW simulations, at varying ranges and elevations. The visual
simulation shall display representations of hostile and friendly weapons effects and visual cues
such as: surface-to air and air-to-air missiles (SAM/AAM) in flight with contrails; SAM launch
blast; AAA and gun tracers; bomb detonations; smoke and smoke columns; multi-state
damage models (undamaged, damaged, and destroyed states); countermeasures;
illumination flares; afterburner; and landing gear and speedbrake articulation. Environmental
effects including but not limited to variable sun and moon positions, illumination and shading
effects, cast shadows based on sun/moon position from moving and static entity models,
day/night, dawn, dusk, weather effects, haze, storm clouds and cloud decks, fog, rain, snow,
blowing snow and sand, and seasonal effects shall be provided. Illumination effects of
ownship lighting on the ground, atmospheric particulates, and other formation aircraft under
night conditions shall be simulated.

Sky and terrain backgrounds and surrounds, with natural insetting in terms of color, contrast,
and camouflage shall be included for all terrain features, targets, threats, and moving models.
Visible ownship control surfaces shall be simulated with articulation and observable motion
for all flight regimes and attitudes, including normal flight and malfunctions.

II. 3. 1. 3. Instructor Operator Station (IOS)

The FMT shall include one (1) IOS to create, modify, setup, initiate, execute, manage, monitor,
evaluate all modes of TS operation, including single-ship and local multi-ship training and
mission operations. The IOS shall support and control training and mission operations for all
or any subset of the Ownships and the other mission event MTC elements (i.e., TES) on the
local network at the MTC site that are allocated for the event. The capability to use multiple
IOSs together to control a multi-ship mission event shall be included. The IOS shall be
assignable to support simultaneous single-ship mission events. The IOS shall be used for
scenario generation when not being used to support training and mission operations. In
addition to the above, the following capabilities shall be supported:
a. 2D/3D display of exercise area
b. Map and photo-specific terrain displays
c. View of all entities in exercise
d. Weather-editing mode and control of the natural environment weather simulation
e. Airport view with glide slope approach corridor
f. Selection of Ownship and entities
g. Malfunction insertion and control
h. Weapon loading and modification
i. Cockpit switches/instrument monitoring
j. Consumables and expendables control
k. Weapon-scoring displays
 l. Reset and reposition
m. “Role playing” for instructional purposes
n. Ground control intercept operator
o. Aerial refueling
p. Tactical entity control
q. IDM datalink
r. Air Traffic Control (ATC) role player (using the IOS communication capabilities and the
IOS support for approach vector and glideslope displays for selected airfields)
s. Laser designator role player display

II. 3. 1. 3. 1. Scenario Generation Capability

Each IOS shall include a scenario generation capability to generate and/or modify scenarios
for training and mission operations. The scenario generation capability shall include the
capability to load mission scenarios containing mission planning data and initialization data to
support TNI-AU F-16 operations. The generated mission scenario files shall be usable and
sharable among all operational Ownships. The scenario generation capability shall incorporate
a graphical interface. The scenario generation capability shall be capable of generating
scenarios to support all required MTC training and mission operations requirements.

The scenario generation capability shall include capabilities to:

a. Geographically place and set initial conditions and behavioral parameters for the TES
entities to be active in the scenario.
b. Select rules to affect the behaviors of the TES entity state machines via the TES editing
capability. The TES rules shall be programmed/edited via a TES editing capability (not
in ScenGen).
c. Store copies of all scenario files for selectable retrieval, use, and reuse in TS training
and mission operations.
d. Load mission planning data produced on and transferred from mission planning
systems.
e. Define and select the malfunctions set to be used during a mission.

II. 3. 1. 3. 2. Scenario Setup and Management

The IOS shall include the capability to access, select, load, initialize, and initiate the execution
of scenarios and mission planning data stored by the IOS scenario generation capability. Each
IOS shall include the capability to initialize all or any subset of the event-allocated Ownship
elements to on-ground or in-flight conditions at any geospatial location in the selected
scenario. The IOS shall include mission control functions to support reset, mission monitoring,
and performance evaluation. The IOS shall have the capability to raise and lower arrestment
systems on applicable airfields. The IOS shall include the capability for each event-allocated
Ownship to bypass simulated aircraft system delays, including inertial navigation system
alignment, Built-In- Test checks, and subsystem/weapon warm-up times. The IOS shall include
the capability to reset to the beginning of the mission or to markpoints. The IOS shall include
the capability for instructors and operators to change and modify scenarios during the
mission. In addition, the following IOS scenario generation capabilities shall be supported:
a. Define scenarios (time, date, and location)
b. Save scenarios
c. Edit scenarios
 d. Set ownship initialization conditions
e. Set entity initial conditions
f. Define and set routes for entities
g. Define entity flight plans, behavior and formations
h. Set scenario weather
i. Set communication, identification and navigational information
j. Define malfunction sets
k. Select malfunction set to be used during mission.

II. 3. 1. 3. 3. Entity Management

The IOS shall include a full range of TES control capabilities for the instructor to reposition
entities, add and activate selectable entities, remove entities, define entity profiles via
scenario generation, and modify entity state and behavior in real-time. Threat control features
shall include the selection of pre-defined threat profiles during a simulation or engagement.
The IOS shall include the capability, in real-time without a freeze, to assume control of any
local TES- generated airborne or ground moving entity in the scenario. The capability to
release control of one entity and assume control of another at the operator’s discretion shall
be included with no disruption to real-time simulation. The IOS shall include a selectable entity
out-the-window display view and situational awareness displays to facilitate operator
perceptions of entity positions and affiliations. The IOS shall include aircraft-like stick and
throttle controls to facilitate instructor control of threats. The IOS mouse shall also function
to graphically select and slew the geographic position of entities within the synthetic
environment. The IOS shall include the capability to freeze the position (lat/long/altitude) of
any ownship and of all constructive entities. The IOS shall also include the capability to reset
weapons and expendable stores station counts. The IOS shall include the capability to adjust
weapons hit/miss criteria by overriding ownship crash and kill results (e.g., “shields up”), and
shall be able to reset the states of inactive and killed entities to an active status. The IOS shall
include the capability for the instructor to serve as a surrogate for (i.e., role-play) airborne and
ground-based command and control entities. The IOS shall include capabilities that allow the
instructor to accomplish basic Weapons Director or Air Operations Center (AOC) “desk”
functions to the scenario (broadcast and tactical control) in all modes of operation and to
input other tactical information through data link commands. The IOS shall support instructor
role-play of air traffic control functions utilizing the IOS communications capabilities and
approach vector and glideslope displays for instructor-selected airfields.

II. 3. 1. 3. 4. Scenario Monitoring and Evaluation

The IOS shall support instructor scenario monitoring with 2D/3D scenario visualization, Gods
Eye View, cockpit instruments views, switch activations, and data logging, which provide the
capability to assess performance (tasks and tactics) and facilitate real-time instruction for any
single or selected set of local event-allocated Ownship elements. The content of any IOS
display, excluding cockpit repeaters, shall be selected according to instructor preferences,
with instructor-settable default configurations. The selectable content on each display shall
include: simulator control functions and menus; any combination of the Ownship instrument
indications; a forward-looking OTW visual view, and a real-time battlespace visualization
display view as described below.
The IOS shall provide cockpit graphics repeater displays for two cockpits for use in local multi-
ship operations. Cockpit repeater displays shall include: Right and Left Color Multi-functional
Displays (CMFDs); RWR; and Forward looking OTW with HUD.

The IOS shall include the capability to monitor any combination of all simulated aircraft radio
(voice and data) communications, observe all system sensor outputs, and monitor on-board
stores status for each event-allocated Ownship. The IOS shall support collection of mission
data for transfer to, presentation and analysis at the BDS during debrief. The data to be
collected shall include weapons launch/shot data to include target range/aspect, kill/damage
results, and countermeasures.

a. Real-time Battlespace Visualization Display View. The IOS shall include a 3D real-
time visualization display view of the synthetic battlespace, from any entity
perspective (Ownship cockpits, any selected friendly, neutral, or hostile entity in the
scenario), a “stealth” (repositionable/slewable) perspective, and entity offset (i.e.,
“attached to”) perspective, with an overhead “bird’s eye” perspective as default. This
display view shall portray entities with readily discernable symbology appropriate for
the entity type, entity orientation, and selectable (on/off by entity) numerically
represented geospatial position (speed/heading/alt). The view shall be configurable
to show the three-dimensional motion of entities in the scenario with variable-length
history “trails” (from 0 seconds [i.e., no trail] to one hour [or until the view eyepoint
is changed]). The view shall include the capability to zoom in and out, to three-
dimensionally rotate the view aspect and offset distances (when applicable), and to
turn on/off entity trails. The view shall include the capability to selectively visualize
the real-time radar scan volumes for any entity or set of entities within the scenario.

b. Malfunction Controls. The IOS shall include the capability to insert malfunctions
during generation, setup, or execution of scenarios (preprogram or manually input)
for all event-allocated Ownship elements. The IOS shall have the capability to select
individual or multiple malfunctions (per simulated aircraft system or multiple
systems) and to delete/clear malfunctions individually or all at once. A reset mode to
clear all malfunctions and reset the simulation to the configuration prior to the
malfunction(s) shall be included. The IOS shall support the capability for the instructor
to induce variations into Ownship cockpit instrumentation (e.g., oil pressure, Fan
Turbine Inlet Temperature (FTIT)) without affecting aircraft system performance, with
the intent of verifying that the pilot is cross-checking cockpit indications.

c. IOS Voice Communications. In addition to simulated radio communications

/monitoring capabilities, the FMT shall include a secure, private, local voice
communication capability, initiated from any event-allocated IOS or Ownship element
to or among any other event-allocated IOS or Ownship elements. This intercom
capability shall be designed to remain fully operable during all TS element states.

d. Mark Points. The IOS shall include the capability for the instructor to designate
multiple specific points during the mission scenario timeline, known commonly as
mark points, for reference during the mission and brief/debrief activities. (SNIPER pod
waypoint picture/data PVI will not be available for recall. This is not the simulator
Markpoint functionality but is also referred to as a Markpoint capability within the
Sniper ATP). Mark points shall be discretely selectable by the instructor at any time
(e.g., to designate a scenario event such as weapons release or RWR spike),
automatically at instructor settable regular time intervals, or both. For each mark
 point, the entity positional state of each event-allocated Ownship element and TES
entity shall be captured and stored, to support a subsequent reset of all event-
allocated Ownship elements and TES entities to that point in the scenario. Weapons
in flight will not be saved/restored. Data storage supporting data capture for a
minimum of 20 mark points per scenario shall be included.

e. Freeze and Reset. The IOS shall have the capability to freeze any or all local Ownship
and TES elements in the scenario; and to subsequently reset and restart each or all at:
(1) the point of freeze, (2) the start of the scenario, or (3) at any instructor-selected
mark point in the mission. TES elements shall be frozen by placing the scenario into
the freeze condition.

f. Mission Recording. The capability shall be included, to record data for entire missions,
encapsulating mission activities for post-mission playback and debriefing at the BDS.
To allow mission reconstruction, visualization, and replay during debriefing, the
information recorded shall include:
1) Intercom and radio communications;
2) State data on all scenario entities; and
3) For each local Ownship element participating in the scenario:
(a) Cockpit control and switch positions,
(b) Cockpit displays (including: HUD, CMFD, and RWR), and
(c) Correlated visual OTW display

The IOS shall include on-line accessible storage capacity to store recorded data for at least
20 hours of mission time (e.g., ten 2-hour missions).

II. 3. 2. Ownship Simulation

The Ownship simulation shall ensure temporal and spatial correlation and consistency among
subsystem simulations to preclude visual or functional anomalies, such as designation or
tracking errors, geo-position and altitude disparities, weapons impact and collision detection,
or occulting/intervisibility anomalies.

II. 3. 2. 1. Aircraft Aerodynamics and Propulsion Simulations

Each Ownship shall include high-fidelity simulations of TNI-AU F-16 aircraft aerodynamics,
flight controls, handling characteristics, and propulsion performance for all ground and flight
regimes, and aircraft configurations (weapons/stores/pods) in accordance with Annex 1 -
Training Task List (TTL). The Block 25 aircraft aerodynamics and propulsion performance shall
match the Block 15 aircraft aerodynamics and propulsion performance. Tail-hook deployment
and simulation of landings on airfields with arrestment systems shall be included.

II. 3. 2. 2. Avionics, Sensors, Weapons and Stores Simulations

Each Ownship shall include high-fidelity simulations of all internally and externally mounted
TNI-AU F-16 Block 15 Enhanced MLU and Block 25 IAU avionics, sensors, weapons, and stores
used in the operational employment of the TNI-AU F-16 weapon system as defined in the
Annex 2 - TNI-AU F-16 Block 15 Enhanced MLU (eMLU) and Block 25 Indonesia Avionics
Upgrade (IAU) Aircraft Configurations. The following specific simulation requirements also
apply:

a. Navigation and Communication. Each Ownship shall include high-fidelity simulations

of all aircraft and weapon system navigation and communication systems available in
the TNI-AU F-16 aircraft, supporting all aircraft employment modes, techniques, and
channels for local multi-ship operations. Voice and data are included in this
requirement. Independent of simulated inter-entity communications, each Ownship
shall also include a simulator-unique capability to securely and privately communicate
among the other local Ownship cockpits and the Instructor/Operator Stations
allocated to the mission. The communication system shall be compatible with pilot
personal gear. The radios shall simulate curvature of the earth occulting and
atmospheric attenuations. The navigation systems shall be comprised of simulations
of the Embedded GPS-INS LN-260 (EGI) system.

b. Combat Identification (CID). Each Ownship shall include a high-fidelity simulation of

the CID system employed by the TNI-AU F-16 Block 15 Enhanced MLU and Block 25
IAU configuration, supporting ownship interrogations and responses to interrogations
from other entities operating in the synthetic environment. The simulation shall
model the capabilities and limitations of the systems including range, resolution,
accuracy, response times, modes, and codes, with degradation in an electronic
combat environment with active ownship, friendly, and threat countermeasures.

c. Electronic Warfare Management System (EWMS)/Countermeasures. Each Ownship

shall include high-fidelity simulations of the TNI-AU F-16 Block 15 Enhanced MLU and
Block 25 IAU Electronic Warfare (EW) and countermeasures systems, including the
Radar Warning Receiver (RWR) and Countermeasures Dispenser (CMD). The
simulations shall model the threat-specific, all-weather capabilities and limitations of
these systems for all threats in the electronic combat environment. The electronic
warfare suite shall provide a high fidelity simulation of the TNI-AU F-16 ALQ-213
EWMS including the ALR69 and ALE47.

d. Sensors. Each Ownship shall include high-fidelity simulations of the TNI-AU F-16
qualified and operational sensors, with simulation of modes of operation, mission
employment, spatial coverage, detection range, target resolution, target
identification, target tracking, and data display. The sensor simulations shall respond
to atmospheric, lighting, and weather effects and threat countermeasures with the
fidelity required to achieve the tasks in Annex 1 - Training Task List (TTL). The sensor
simulations shall perceptually correlate with all other ownship simulations. Sensor
simulations shall include the APG-68v9 Fire Control Radar (FCR) (Block 15 eMLU), APG-
68v0 Fire Control Radar (FCR) (Block 25 IAU), ALR-69 RWR, APX- 126 Advanced
Identification Friend or Foe (AIFF) (Block 15 eMLU), APX- 101 Identification Friend or
Foe (IFF) (Block 25 IAU), and Sniper Advanced Targeting pod. The Sniper Advanced
Targeting pod shall exclude the following capabilities: recording DDR functionality,
Video Down Link (only PVI functionality), Compact Multi-Band Data Link (CMDL) (only
PVI functionality); two way data Link (TWDL) functionality. The imaging modes of the
TNI-AU F-16 sensors are also subject to the requirements established in paragraph
II.3.2.5.

e. Weapons, Munitions and Stores. Each Ownship shall simulate the employment of TNI-
AU F-16 weapons, munitions, and stores as defined in the TNI-AU F-16 Weapons,
 Munitions, and Stores List. All weapon simulations, both air-to-surface and air-to-air,
shall incorporate models with a realistic: Probability of Kill (PK); Launch Acceptability
Region (LAR) expectations/presentation; flyout timeline; engagement timeline; and
weapon lethality. Capabilities/limitations of the weapons in the high, medium, and
low altitude; all weather; day/night; and electronic combat environment employed
against maneuvering/non-maneuvering air targets, and moving/stationary ground
targets shall be modeled (including all appropriate visual and sensor perceptions)
based on authoritative open source data to achieve the training tasks in Annex 1 -
Training Task List (TTL). The Ownship shall simulate weapons, munitions, and stores
management/status, on-rail malfunctions, pre-launch procedures, launch,
missile/bomb/bullet flyout, target tracking, impact detection and detonation (when
applicable), and battle damage (i.e., damage models, fire, smoke) to other entities in
the synthetic environment. Weapon flyout performance for all required weapons
shall be verified by defining 3-5 launch profiles (test cases defined by Subject Matter
Experts [SMEs]), then verifying launches against Operational Flight Program (OFP)
provided launch cues, and time on target countdowns. Weapon flyouts shall be based
on white world data and are unclassified. The effects of countermeasures shall be
simulated, to include chaff and flares on active ordnance. The capability to set discrete
weapon fuzes or laser codes and to buddy lase shall be included.

II. 3. 2. 3. Simulated Malfunctions

The Ownship shall implement IOS-selectable, simulated malfunctions of TNI-AU F-16 Block 15
Enhanced MLU and Block 25 IAU systems and components for training of emergency
procedures and employment techniques for degraded system performance. Malfunctions
shall include failure of or damage to avionics, weapons, communications, sensors, engines,
hydraulics, as well as cascading effects of malfunctions through related systems. The
implemented malfunctions shall be consistent with TNI-AU F-16 Pilot TTL, and emergency
procedures as described in TNI-AU F-16 flight manuals. Each malfunction shall be presented
such that pilot corrective actions and emergency procedures can be performed as in the actual
aircraft. Malfunctions shall be modeled to represent degraded or failed system performance
perceived by the pilot in the actual aircraft under the same conditions, to include internal
aspects (e.g., cockpit indicators and/or displays) and external aspects (e.g. hydraulic or fuel
leaks, hung stores, landing gear, flap, speedbrake, and tail hook configuration). Upon
deactivation of the malfunction at the IOS or resolution by the pilot, the simulation shall return
to a normal operation.

II. 3. 2. 4. Synthetic Environment

Each Ownship shall include a Synthetic Environment Simulation that supports the full range
of day/night, low altitude, and all-weather mission training and operations for employment of
the full range of weapons and sensors. The Synthetic Environment Simulation shall be
correlated with all visual (OTW and imaging sensor), audio, radar, datalink, electronic combat,
navigation, weapons, and TES to support all training and mission events. The Synthetic
Environment Simulation shall support Ownship participation in single and multi-ship training
and mission operations.
II. 3. 2. 4. 1. Natural Environment

The Synthetic Environment Simulation shall include a natural environment with simulation of
terrain, bodies of water, atmosphere and atmospheric phenomena including weather, time of
day, celestial bodies, sun, star and moon along with their positions, directional illumination
and shading. Spectrum specific effects of the natural environment on the performance of TNI-
AU F-16 sensors and emitters shall be simulated. The natural environment shall interact with
the aircraft, weapons, sensor and emitter (including electronic combat systems) simulations
in such a way to establish realistic performance for the natural environmental conditions as
encountered by the aircraft.

II. 3. 2. 4. 2. Electro-Optical/Infrared Environment

The Synthetic Environment Simulation shall represent the electro-optical (EO) and infrared
(IR) environments and artifacts for use with EO/IR sensors and weapon systems. The EO/IR
environment shall correlate with visual, radar, and other displays/sensors. As a minimum, the
EO/IR environment simulation shall incorporate the following environmental effects:
a. Minimum resolvable temperature difference of at least 1.07oC
b. Temperature range encompassing the range from -25oC to +25oC
c. Radiant exitance computed at the texture element (texel) level of precision, and
unique radiance computed per pixel, to support normal and magnified sensor fields
of view
d. Black body emissivity and surface reflectance based on material properties

II. 3. 2. 5. Imaging Sensor Simulations

Each Ownship shall include imaging sensor simulations to replicate NVG, Sniper Advanced
Targeting pod, and radar operations in all illumination levels. Dynamic shadows shall only be
casted for moving models and terrain shading corresponding to lunar position and phase. To
achieve the training tasks defined in Annex 1 - Training Task List (TTL), the simulations shall
replicate directional illumination effects of natural and artificial light sources including moon,
starlight, fire, runway lights, airfield lights, strobes, cultural lighting, aircraft lighting,
afterburners, dynamic flares, illuminations flares, smoke, and horizon glow. To achieve the
training tasks defined in Annex 1 - Training Task List (TTL), the appropriate effects of
directional, spotlight, and indirect lighting shall be included, along with moon-cast terrain
shadows. To achieve the training tasks defined in Annex 1 - Training Task List (TTL), glare
effects of ownship aircraft lighting shall be simulated. The sensor simulations shall properly
occult objects out to the maximum range without restriction on the relative placement of
fixed or moving objects or restrictions on viewing position. All sensor simulations shall be
correlated with the visual OTW simulation to support cross-checking and situational
awareness. To achieve the training tasks defined in Annex 1 - Training Task List (TTL), the
simulation shall present the effects of multiple, temporally overlapping, combat related
actions such as air and ground weapons launch (including ownship weapons), AAA fire, tracer
rounds, flak bursts, missile/rocket/jet plumes and smoke trails (including ownship-launched
weapons), fires, detonations, countermeasures (flares, chaff), contrails.
II. 3. 2. 5. 1. NVG-Specific Effects

NVG-specific irradiance sensitivity, acuity/resolution, FOV, contrast, halos, scintillation, veiling

glare, and noise effects shall be simulated. NVG flight hazards and illusions shall be simulated,
cultural light reflection on cloud decks, and cloud deck and haze obscuration of the horizon.
To achieve the training tasks defined in Annex 1 - Training Task List (TTL), the MTC design shall
support accurate training of NVG operations and malfunctions including employment
techniques, situational awareness, visual cross-check, glare effects of light sources from
within the cockpit, weather and lightning effects, and effects from aerosol/particulate
obscurants. The MTC design shall support NVG look-under and look-aside capability, with a
simultaneously viewable OTW visual night scene.

II. 3. 2. 5. 2. Sensor-Specific Effects

The imaging sensor simulation shall support variable, magnified, and slew-able FOV, pixel
target tracking, manual and automatic level and gain control, and accurate reticle and
symbology representations.

II. 3. 2. 5. 3. Radar-Specific Effects

Radar effects shall be simulated and shall include those effects associated with the radar
sensor and signal processor, the atmospheric environment, and with radar signal interaction
with the target/earth’s surface. Earth curvature and refraction shall be simulated at all
altitudes. The range to the radar horizon shall be a function of earth radius, height of the
antenna, and refraction of the atmosphere. Dynamic shadows shall be casted for moving
models but not articulated parts of moving models. The displayed shadows shall vary in length
and direction based on light source position and orientation. There shall be no shadows for
objects that do not cause shadows in the real world. The radar simulation shall include the
effects of material (codes) associated with terrain and feature data bases and the appropriate
effects due to weather and free space attenuation associated with the relative position of the
radar and radar targets. The air-to-air modes shall detect and track targets at all altitudes,
with and without ground clutter. Environmental inputs such as weather cells, targets, threats,
chaff, jammers, shall be accepted as inputs to the FCR simulation, which shall in turn present
an output to the aircraft displays. The FCR simulation performance shall properly respond to
the simulated aircraft flight parameters and radar set controls to achieve the training tasks
defined in Annex 1 - Training Task List (TTL). Antenna movement and gain shall be simulated.

II. 3. 2. 6. Visual and Sensor Databases

The TS database shall provide visual cues, image quality, feature density, mission area and
geo- positional accuracy to accomplish the training activities defined in the TTL. The database
shall represent the geospecific area within the borders of the Republic of Indonesia as defined
by the U.S. State Department at the time of contract award. The entire database shall be
blanketed with a minimum of 15 meter imagery. The database shall include high resolution
areas for two airfields. The high resolution areas shall utilize up to 1 meter imagery. Details of
the high resolution areas will be refined and defined at database working group meetings. The
mission area databases shall be derived from real world data and imagery and supplying the
visual, sensor, and weapons simulations with sufficient accuracy, feature density, and
geographic coverage to support all established training and mission operations requirements.
All local airfield databases shall include high-density insets with appropriate incorporation of
geo- specific, and photo-specific content. The databases shall represent current terrain
elevation, terrain texturing, geospecific natural and cultural features. All visual texture shall
be full color, and all sensor texture shall be material coded and display spectrum-specific
physical properties. Local airfield and mission area databases shall contain geo-typical feature
scatter. The theme of geo-typical feature scatter shall be consistent with the general
environment where it is located (e.g., urban vs rural, desert versus mountainous). All 3D
features shall include appropriately aligned photo-texture on horizontal surfaces. The
visual/sensor simulation design shall support the display of moving models within the
database areas, in any combination of ground and air targets. Geo-positioned and geo-specific
features shall include appropriately aligned geo- specific or geo-positioned photo-texture on
all surfaces. Foliage shall include a range of tree types and sizes. Simulations of targets and
target areas, navigation references, and low-level navigation areas generating realistic pilot-
perceptible geo-specific cues shall be included.

Specific requirements for levels of database are as follows:

II. 3. 2. 6. 1. Mission Area Databases and Local Airfields

When source imagery is available, these databases shall include geo-specific photo-texture
with a minimum resolution of 15 meters. When source imagery is unavailable, geo-typical
photo- texture with equivalent resolution may be used. Terrain elevation shall be represented
with 100m post spacing, or better. Feature content of the local airfield and mission area
database shall be equivalent to or better than that provided with NGA VMap1 datasets.

II. 3. 2. 6. 2. High Resolution/Density Insets

High resolution and density database areas shall be inset and feathered into the local airfield
and mission area databases. These insets shall include two airfields. When source imagery is
available, insets shall incorporate geo-specific photo-texture with 1-meter resolution or
better. When source imagery is unavailable, photo-derived, geo-positioned texture with
equivalent resolution may be used. Terrain elevation for the runway surface shall be
represented with minimum 30m post spacing with the highest resolution elevation available,
or with increased accuracy for Precision Guided Munition-targetable features and airfields.
The visual/sensor simulation design shall support the display of moving models within the
database areas, in any combination of ground and air targets. High resolution/density insets
shall provide feature content with the highest feature content available. Geo-positioned and
geo-specific features shall include appropriately aligned geo-specific or geo-positioned photo-
texture on all surfaces. A maximum of 15 feature models shall be provided per airfield and
range. Foliage shall include a range of tree types and sizes. Airfields shall be represented
consistent with NGA Digital Aeronautical Flight Information File (DAFIF) descriptors, with
extents covering a 5 NM buffer area surrounding the airfield boundaries. As present in real
world airfields, arrestment systems shall be realistically modeled with appropriate IOS control
interfaces. For raised/lowered cable type systems, the database shall support both raised and
lowered models.
II. 3. 3. Tactical Environment Simulation (TES)

The TES shall include one (1) interactive, real-time, constructive TES environment per FMT and
WTT. The TES elements shall generate multiple hostile, neutral, and friendly entity instances
within the local training mission event that interact with each other and each Ownship in the
scenario. The TES shall provide the following capabilities: high fidelity aerodynamics, six
degree of freedom fixed wing and rotary wing aircraft, five degree of freedom (roll stabilized)
missiles. The system shall contain a customizable, full-featured electronic warfare with
occulting and atmospheric propagation effects. The TES shall include selectable entity state
machines and modifiable rules to effect the behaviors of the state machines. The TES shall
include user programmable data for maintainability to include the capability for user to add,
modify, and delete entities with TNI-AU data. The TES shall include interaction with the natural
environment simulation to include: weather simulation using global weather database,
surface winds, cruise winds, gusts, ambient light conditions based on solar position, and the
capability to realistically perceive and engage a full range of potential threats and targets
represented by fixed and moving ground, surface, and air forces models. The TES shall be
based on a physical model database with the following capabilities: entity editing capability
allowing users to select assets for inclusion on an entity, assets include weapon systems,
radars and sensors, physical chassis information and tactical role players based on behavioral
elements; asset editing capability allowing users to modify the characteristics of particular
assets (e.g. thrust characteristics of aircraft engine, gimbals of a radar, or the set of rules used
by a tactical role player); data manager managing the large data elements associated with
electronic warfare, detection ability and probability of survivability model behavior database,
rules-based behavior modeling for entities, human-readable and user-editable rules can be
modified by users, rules can be used to create maneuvers and add simple and complex tactics.

II. 3. 3. 1. TES Capacities and Throughput

The TES shall be designed with sufficient computational processing throughput and storage
capacity reserves to support the entities required in this document. The TES design shall
support the conduct of multiple simultaneous local (single- and multi-ship) operations. Each
TES shall support the generation of up to 250 total dynamic entities with a full range of entity
behaviors and controls and any combination of entity types (airborne or surface), and with up
to 250 in motion simultaneously.

II. 3. 3. 2. TES Simulation Models

The TES shall include 200 predefined models of synthetic forces and entities as proposed by
the Contractor in Annex 3– Tactical Environment Simulation (TES) Predefined Models List. The
TES entity performance characteristics shall be based on authoritative open source data (e.g.,
from Jane’s). These entity types shall include a full range of threats, command and control
elements, and other tactical entities that could be encountered in combat theaters to achieve
the training tasks defined in Annex 1 - Training Task List (TTL) such as: fixed-wing aircraft,
helicopters, surface ships, missiles, bombs, missile sites, AAA sites and cultural feature sites
(i.e., buildings and bridges). These entities shall be editable and expandable by the operator.
All TES entities shall have selectable, artificial intelligence characteristics such as skill,
aggressiveness, command and control and teamwork relationships with other friendly
entities, rules of engagement doctrine They shall react appropriately to offensive/defensive
system countermeasures, tactics employment from other Ownship entities, weapons, and
sensor systems, while operating within a simulated synthetic environment to include natural
environment/EW/EO/IR, time of day, and terrain and cultural features. In addition, entity
models shall be included with user-programmable performance parametric that enable the
instructor or mission planner to generate threat entities with hypothetical or enhanced
performance. TES entities shall be assignable to an allegiance group to include: friendly (blue)
forces, hostile (red) forces, and non-combatant (neutral) forces. When appropriate, TES
entities shall be able to operate autonomously or tactically as a group commensurate with the
selected skill level with the fidelity required to achieve the tasks in Annex 1 - Training Task List
(TTL). TES entities shall also have a deterministic behavior (pre-programmed) mode in which
they will follow predefined routes with no reaction to tactics employment or maneuvering by
other entities. TES entity models shall generate radar, jamming, and CID emissions consistent
with real-world entity capabilities and allegiance assignments with the fidelity required to
achieve the tasks in Annex 1 - Training Task List (TTL). The TES entities shall interoperate with
the F-16 Ownship entities and all avionics emissions, sensor perceptions, and weapons
interfaces with the fidelity required to achieve the tasks in Annex 1 - Training Task List (TTL).
The TES shall support ground targeting and battle damage assessment by air forces entities.
TES threat models shall be designed to operate in the following selectable modes: (1) as an
autonomous entity; (2) under the control of an instructor-operator via control interfaces with
the IOS. The TES Command, Control, and Communications (C3) simulation shall consist of a
role player by the IOS instructor and shall realistically simulate communications signals and
C3 activity messages that are pre-emptive to the actions of the specific threat systems under
the control of the C3. TES ground entity models shall realistically “clamp” to the terrain surface
and dynamic airborne entity models shall “crash” upon contact with terrain exceeding
programmed crash velocity thresholds.

II. 3. 3. 3. Electronic Combat Simulation

The TES shall model hostile and friendly electronic combat entities and integrate the effects
of countermeasures to include chaff, chaff corridors, flares, jamming, anti-radar maneuvers,
and frequency hopping. The TES shall simulate the electronic combat interactions among
ground and airborne entities, to include simulations of radar, radar warning receiver
perceptions, jamming, data link, CID, air and surface emissions, Electronic Countermeasures
(ECM)/Electronic Counter-Countermeasures (ECCM) via degraded jammer effectiveness, IR
countermeasures via flares, electronic support measures, IR emissions, and other common
emissions observed by TNI-AU F-16 aircraft. The TES electronic combat environment shall
support hostile, friendly, and non-combatant entity interactions with TNI-AU F-16 sensor and
countermeasure systems simulations with the fidelity required to achieve the tasks in Annex
1 - Training Task List (TTL). The TES electronic combat environment simulations shall be
programmable to allow doctrinal changes in the behavior of threat models to include combat
flight tactics and combat operation of sensors, jammers, AAA, and missile systems. Emissions
from the Ownship shall be occulted and/or attenuated by terrain, cultural features, weather,
atmosphere and ECM/ECCM. Degradation of electromagnetic emissions with respect to
jamming, range, weather effects, and terrain/culture occulting shall be simulated. The TES
shall include interfaces with the visual system to ensure that moving ground entities remain
clamped to the terrain surface throughout their course of travel.
II. 3. 4. Brief-Debrief Station (BDS)

The BDS shall include visualization capability with at least 3900 square inches of total viewable
display space on no less than two COTS displays. The content of the majority of displays shall
be selectable and scalable/-sizable according to instructor preferences, (excluding cockpit
display repeaters) with instructor-settable default configurations. The simultaneously
selectable content on the displays shall include: BDS control functions and menus; recorded
Ownship cockpit displays (Right CMFD, Left CMFD, RWR); a forward-looking recorded HUD
correlated with OTW visual view for each cockpit, and a simultaneous battlespace
visualization display view. The BDS shall support the two (2) FMT and two (2) WTT devices.
The BDS shall also include functionally equivalent capabilities to the IOS scenario generation
capability to allow for its use as an additional scenario generation/modification resource. BDS
design shall maximize use of COTS multimedia equipment for playback of recorded mission
data. The BDS shall include Microsoft Office necessary to support the briefing presentation by
F-16 instructors and flight leads for accessing and presenting squadron briefings. Controls, and
display menus/data shall be included for flexible selection of all required BDS functionality.

II. 3. 4. 1. Briefing Capability

The BDS shall support pre-mission planning and briefing activities to prepare TNI-AU F-16
pilots for a subsequent planned mission scenario execution. The BDS shall include a 3D
battlespace visualization display view of the scenario data, with functionality consistent with
the IOS real-time battlespace visualization display view capability.

II. 3. 4. 2. Debriefing Capability

The BDS shall support pilot debriefing for any recorded mission scenario for both the FMT and
WTT devices. The BDS shall include hardware and software to access recorded mission data
from on-line storage per the IOS mission recording functionality (section II.3.1.3.4). The BDS
shall include 3D battlespace visualization display capability for recorded segments of any
mission scenario from any eyepoint and perspective within the scenario battlespace
consistent with the IOS real-time visualization display capability, while simultaneously
displaying correlated cockpit control, switch, and display information for all local Ownship
elements in the scenario. The BDS shall include appropriate controls to select a different
visualization eyepoint at any time during playback without freezing or stopping the playback.
The BDS shall include controls to start, freeze, rewind, fast forward, and restart the playback
from or to any time reference in the mission timeline, along with the capability snap to any
mark point.
 II. 3. 5. Weapons and Tactics Trainer (WTT)

The WTT shall be a “glass cockpit” environment simulator for combat tactics training within
an F-16 shell cockpit. All touch panels shall be displayed in similar relative positions as in the
real cockpit. Due to physical size constraints of COTS display technology, priority should be
placed upon ensuring the display of virtual cockpit panels is similar in size to aircraft panels.
Therefore, a pilot-accessible user interface may be included to allow the panel(s)-of-interest
to be displayed while adjacent panels are hidden. Control of the aircraft shall be provided with
high fidelity Hands-On-Throttle-And-Stick and medium-fidelity rudder pedals. Utilizing
common software with the FMT, the WTT shall provide high-fidelity software simulation. The
WTT shall be capable of operating in a basic, single-ship, non-tactical mode for fundamental
F-16 familiarization (switchology, contact flying, and instrument flying) and emergency
procedures training. Emergency procedure training shall be limited by not having actual
switches, knobs, or buttons (these items will exist and be functional in the WTT, but the pilot
will have a different action/feel than the FMT). The WTT shall also be capable of operating in
a networked multi- ship training and mission operations mode in support of tactical training
with the FMTs.

II. 3. 5. 1. Weapons and Tactics Trainer Visual System

The visual system for the WTT shall consist of three (3) COTS monitors that measure
(diagonally) between 40 inches to 50 inches. The visual system for the WTT shall utilize a
common visual database and Out-the-Window Image Generators with the FMT to display the
same visual models and effects as the FMT.

II. 3. 5. 2. Weapons and Tactics Trainer Limited Instructor Operator Station

The WTT shall provide the ability to control the IOS from the cockpit to enable the student to
self-instruct (single-ship, non-tactical mode). The limited IOS shall consist of one IOS monitor
without any cockpit repeater displays. The one IOS monitor shall provide the same IOS
capability as described in section 3.3.1.3 without any IOS voice communication capability.

II. 3. 6. System Status Requirement

The MTC shall include a daily readiness test to assess readiness of the major system
components. The TS shall include all diagnostics that are provided with COTS components.
COTS equipment with software diagnostics shall use the COTS User Interfaces.

III. Verification and Validation

The Contractor shall execute and document a comprehensive Test and Evaluation (T&E)
program IAW the Contract-Statement of Work (CSOW). Each requirement in section II
shall be verified through appropriate tests, demonstrations, and/or analyses. Verification
requirements for specific section 3 performance requirements are also established below
in Section III.2.
III. 1. Verification of System Elements

The hardware requirements of section 3.1 shall be verified by inspection.

III. 2. Integrated System Performance Verification

III. 2. 1. Verification of Ranges of Training and Mission Operations

Training/mission scenarios shall be created and executed to demonstrate capability as

defined in section 3.2.1. The scenarios shall be developed based on analysis of training
requirements and subject matter expert discussions during the design process, and
should resemble scenarios that might be developed for actual training purposes.
These test scenarios shall be maintained in and accessible from the scenario file
storage capability for use by the Contractor and TNI-AU to support future verification
and validation activities.

III. 2. 2. Verification of Real-Time Operation

To verify real-time operation requirements specified in sections II.2.2 and II.2.3,

objective tests will be designed and conducted using the data logger and event log
capturing real time operational data to manually quantitatively measure cumulative
(end-to-end) dataflow and computational latencies and latency variations for selected
critical combat simulation interactions in and among the MTC element simulations. In
addition to the measured latencies, analysis shall also be used to verify these
requirements.

III. 2. 3. Design and Construction Requirements Verification

Compliance with section II.2.5 design and construction requirements (and

subparagraphs) will be verified throughout the course of system development, test,
and evaluation through inspections of design disclosure documentation and
supporting analyses (when necessary). Verification documentation summarizing how
each requirement is verified will be created as the disclosure documentation and
supporting analyses are reviewed, and shall be maintained as part of the test record.

III. 3. Element Verification and Validation

Section II.3 MTC System Element requirements will be verified with appropriately
designed and documented tests, demonstrations, inspections, and analyses. As each
element is designed, a verification strategy for each performance requirement
(including Contractor-derived requirements allocated in system/subsystem
specifications) will be developed and then executed to ensure complete traceability
from system level requirements to detailed system design compliance.
IV. MTC Facility Requirements

TNI-AU F-16 project facilities will be used to accomplish new pilot training, pilot conversion training,
upgrade, and advanced skills training. The facilities will house simulation equipment; associated
student station, computers and power distribution panels; IOS, BDS; WTT and peripheral equipment.
All equipment will be located within one local building.

The facility should also include areas for administrative personnel who will perform functions
necessary for day-to-day operations of the TNI-AU F-16 project with provisions for services such as
toilet and janitorial. These administrative personnel include instructors to oversee ground training of
students; maintenance personnel to maintain the simulation systems; and training administration
personnel to maintain training material, records, and schedules.

Base support will typically provide facility fire protection; maintenance of the real property and
utilities; maintenance of the grounds around the building; maintenance of access roads; maintenance
of the facility main circuit, Heating, Ventilation, and Air Conditioning (HVAC) system, including
humidity control; trash removal service; communications; physical security; and law enforcement.
Base support will also provide water and sewage; handle disposal/recycling of hazardous materials (if
required); and install emergency lighting in the facility in the case of power outages, including exit
lights with battery backup, if necessary.

IV. 1. Access Roads

All-weather-type roadways and service drives are required to access the facility entrance
designated to receive the system.

The facility requires an area capable of withstanding the load of a parked 80,000-pound
(36,287 kilograms) vehicle. All access roads and parking areas surrounding the facility will be
able to support a load of a parked 80,000-pound (36,287 kilograms) vehicle. The equipment
offload area near the equipment staging and preparation area must be near the access to the
simulation facility and have paved access from the vehicle to building ingress for forklifts and
other material handling equipment. The receiving area must be large enough to allow lift
trucks to unload. Access doors must be flat and free of obstructions such as curbs or steps.
IV. 2. Physical Arrangement and Orientation
IV. 2. 1. FMT High Bays

The facility shall provide a light-tight capability in this cockpit/out-the-window (OTW) Display
System room to accommodate training exercises, especially night operation exercises. This
shall also include any other lighting within the cockpit/OTW Display System room such as
emergency lighting (e.g., exit lights, emergency lighting in ceiling or on walls). The emergency
lighting shall have the capability of temporarily covered during training exercises. The room
and floor must minimize the use of reflective surfaces. All walls and ceilings should be coated
with a dark non-reflective paint with a flat black finish and then coated with matte concrete
sealer to maintain a light-tight area during training. The floor should also be covered with a
non- reflective coating.
These simulator bays shall be free of structural columns.\

All high bay entrance/exit doors shall have seals on door edges and thresholds to minimize
dust contamination from entering the high bay when doors are closed.
The FMT high bay dome equipment requires a minimum of 20 feet (6.096 meters) in height
clearance from the floor. All A/C ducts, pipes, electrical conduit, lighting, etc. shall be above
the 20 foot (6.096 meters) clearance.

The trenches that lead into the FMT high bay should have light seals as extra precaution.

IV. 2. 2. FMT Floor Level Requirements

The base floor in the FMT rooms shall be flat and level to within ± 1/4 inch (0.56 cm) per 25
feet (7.62 meters) to allow easy movement of the cockpit and lifting frame. All vertical
projections should be ground down to level and all cracks and holes filled with suitable filler.

IV. 2. 3. Acoustical

The major source of noise is the aural simulation system emulating the engine sounds of an F-
16 aircraft. The noise level, 70 +/- 10 dB, at varying frequencies, produced by this system is
required to provide the fidelity of the simulation and is only present at the student station
and is adjustable from the IOS by the operator. Acoustic insulation should be provided in the
walls of the IOS, BDS and WTT rooms to minimize sound between rooms. The IOS, BDS, SGS,
and WTT systems should be located in separate rooms.
The other major sources of noise are the air handlers for the Environmental Control System
(ECS). If possible, the air handlers should be located in a separate mechanical room.

IV. 2. 4. Windows

Simulator bays, computer rooms, and maintenance rooms are to be void of any exterior
windows. Simulator bays should be void of any interior widows. Windows may be used for
climate control and aesthetics in rooms such as break rooms or offices where only unclassified
equipment will be installed.

IV. 2. 5. Equipment Staging/Preparation/Spares Storage/Maintenance Area

An equipment staging and preparation area be provided as shown in the proposed layout.
Due to the volume of the system, coupled with the environmental conditions, this will provide
a safe and secure area to uncrate the system.

This area, 1,600 square feet (148.65 square meters) could later be used for contractor logistics
support (CLS) activities to include spares storage as well as a maintenance area and would be
located in proximity to the simulation system. The estimated storage space for spare parts,
supplies, tools, and consumables is 625 square feet (58.0 square meters). This storage space
should include a number of shelving units (estimate 5 or 6) each estimated to be 6 feet (1.8
meters) tall by 4 feet (1.2 meters) wide with four (4) levels; two (2) levels with adjustable
shelves; and each shelf rated for a load of 100 pounds (45.4 kilograms). The maintenance area
should be approximately 150 square feet (14.0 square meters) with an electrostatic discharge
(ESD) protected workbench to be used while handling (performing fault isolation procedures)
or repairing ESD-sensitive items (such as computers or other electronic devices).

In addition office areas are required within the facility for program personnel to perform their
daily status and tracking, correspondence and support activities. The current estimate is no
less than 70 square feet (6.50 square meters) per person. Office furniture is the responsibility
of the TNI-AU. It is also the responsibility of the TNI-AU to provide telephones, copiers,
printers, personal computers and internet access for the permanent site personnel in their
offices and/or maintenance rooms, in accordance with security considerations.

The remaining area could be used for facility electrical/mechanical equipment (power panels,
etc.). And with the Equipment Staging/Preparation/Spares Storage/Maintenance Area being
used for storage and personnel space, the area should be environmentally controlled.

IV. 2. 6. Door Requirements

The main exterior installation doors shall be of the roll-up type and 14 feet (4.27 meters) wide
by 16 feet (4.88 meters) high to the maintenance/storage area. The FMT bays shall have a
temporary access opening of 14 feet (4.27 meters) wide by 16 feet (4.88 meters) high. The
doors for the WTT room from their specific FMT bay shall be 6 feet wide by 7 feet high and
used for the spares storage area. All other doors in the trainer areas shall be 3 feet (0.91
 meters) wide by 7 feet (2.13 meters) high. All facility entrance/exit doors shall have seals for
dust control into the building.

IV. 2. 7. Floor Requirements

The IOS, BDS, and WTT rooms will require computer-type flooring, which is described in
Section 4.0. The concrete floor beneath the raised flooring should be sealed to control dust
and free of any construction debris, dirt, and dust.

IV. 2. 8. Ceiling Requirements

The ceiling heights noted in should be clear of hanging lights, etc. It is recommended that the
ceiling in the computer rooms be of the acoustical removable type.

IV. 3. Structural

IV. 3. 1. Floor Loads

The maximum loads imposed on the concrete floor shall be as follows for the simulation
equipment rooms/bays; computer rooms; maintenance and storage rooms, the Brief/Debrief
room, the WTT room, and the IOS room:

250 pounds/square feet (1220.61 kilograms/square meter) Uniform Live Load

1000 pounds/square feet (4882.43 kilograms/square meter) Rolling Load
2000 pounds/square feet (9764.86 kilograms/square meter) Concentrated Load.

IV. 3. 2. Computer Room Type Floors

A computer room-type, full-access floor system, provided as part of the facility, is required in
the computer room. The height of this floor above the building concrete subfloor should be
12 inches (30.48 centimeters). The concrete subfloor should be sealed to be dust free.

A computer room type of floor is required to provide a common mounting surface for
equipment; to place operating and maintenance personnel at the same elevation; and to
provide an under-the-cabinet means for concealing electrical conduit, signal cabling between
cabinets, and grounding cabling.

The floor system that is installed should be the full-access type consisting of 2-foot (60.96
centimeters) square modular tiled panels positioned on all sides by a grid understructure. This
grid understructure should use rigidly bolted stringers and be supported by pedestal
assemblies. The stringers should be rigidly bolted with a threaded fastener passing through
the stringer and mating with an integral nut welded to the pedestal cap to provide a secure
mechanical union and a long-term, low-resistance joint. Clip or metal screw-type fasteners
should not be used.

All panels should be easily removable by one person with a suction cup lifting device and be
interchangeable except where cut for special conditions. The floor panels that are
recommended should be metal clad, wood core with plastic edge trim, and a high-pressure
laminate covering. The floor panel shall be capable of supporting a uniform live load of 250
pounds per square foot (1220.61 kilograms/square meter). Permanent set shall not exceed
0.010 inch (0.254 millimeters) under this loading. The floor panel shall be capable of
supporting a concentrated load of 1,000 pounds applied on an area of 1 square inch (70.31
kilograms applied on an area of 1 square centimeter) at any location on the panel, with a
maximum beam deflection of 0.080 inch (2.032 millimeters) and a maximum permanent set
of 0.010 inch (0.254 millimeters). Design stresses shall provide a safety factor of 3, based on
the yield strength of the material being used. Panel bearing shall have a conductive grounding
and sound deadening pad that shall also act as a plenum seal. Pedestal adjustment for floor
leveling shall use a threaded rod with a 2-inch (5.08 centimeters) range using locking nuts to
secure the level attained. The complete floor system shall consist of compatible and corrosion-
resistant materials and shall be sturdy, rigid, and free of rocking, rattles, squeaks, and other
noises. The overall floor shall be level within +0.062 inch (+ 1.574 millimeters) in 10 feet, 10
inches (3.048 meters, 25.4 centimeters). The floor system shall be sealed against room walls,
power distribution cable raceway, etc.

Penetrations are required in the facility-provided computer room type of floor panels. These
penetrations in the floor are all required in the panels immediately under the equipment. The
penetrations will service the system as accesses for signal, grounding, and electrical cables.
Unrestricted access for passage of cables between any and all of the indicated cutouts shall
be provided.

It will be necessary to run wires and cables between the various pieces of equipment, which
may be located in different rooms and different parts of the facility. Because each facility is
unique, it will be critical to identify the methods and locations for routing these wires and
cables prior to completing building design. Installation of wire-ways between rooms housing
this equipment will be required. These wire-ways may be sleeves through walls or cable
troughs in ceilings. Distances, routing, and security requirements must be considered when
choosing wire-ways. Trenches shall be a minimum 12 inches by 12 inches (200 mm by 200
mm) in depth and width, and have steel cover plates that can bear the load of the adjacent
floor.

In addition, the trench metal covers shall have cutouts for each rack for cables. The cutouts
shall be 4 inches by 6 inches in size and no sharp edges.
IV. 4. Mechanical

IV. 4. 1. Environmental Conditions

Proper conditioning and control of the building environment by the facility is essential. Both
equipment reliability and operational efficiency depend on proper control of temperature and
humidity. For design purposes, the optimum conditions that should be achieved for the
operating environment of the system equipment are given in the following subparagraphs.
The environmental equipment is required to provide these controlled conditions in the system
area 24 hours per day.

The system is designed to operate or be stored (non-operating) in a controlled environment

with the conditions shown below:

IV. 4. 2. Filtration Requirements

The conditioned air shall be filtered prior to delivery to the system equipment and general
areas. The degree of filtration is to be equivalent to that achieved by a replaceable extended
surface pleated filter of 25- to 30-percent average efficiency in accordance with American
Society of Heating, Refrigeration, and Air-Conditioning Engineers (ASHRAE) Standard 52-76.

IV. 4 3. A/C Distribution for Computer Rooms

The trainer equipment racks will use room ambient air for heating/cooling. The HVAC
conditioned air is drawn into the racks by internal fans. This air is directed and passed over
heat- dissipating components and is free exhausted from the units to the room.

All HVAC systems for the computer rooms shall be split units with compressor units outside
of facility and air handlers inside the facility.

The HVAC pressure and return in the simulator bays should contain high-efficiency filters
having the capability of filtering down to a 5 micron particle size (ISO 14644-1 classification
level 8) that will help control contaminants such as dust from contaminating the dome
projection equipment.

The facility shall provide a dedicated HVAC unit per FMT to cool the OTW display structure
(i.e., inside the domes) and cockpit. The FMT OTW display is cooled and then exhausted into
the facility FMT room. The facility shall provide two (2) seven (7) inch (17.78 centimeter)
diameter flexible ducts to top of the visual display structure. The duct shall supply 55°F
(12.77 °C) ±5°F (±15°C) filtered heating/cooling air a minimum of TBD cubic feet per minute
(CFM) (TBD cubic meters per minute) at 1.17 inches (2.97 centimeters) minimum Water Gauge
(WG) static pressure, and shall contain high-efficiency filters having the capability of filtering
 down to a 5 micron particle size (ISO 14644-1 classification level 8) that will help control
contaminants such as dust from contaminating the dome internally.

All HVAC systems for the FMT rooms (simulator bays) shall be split units with compressor units
outside of facility and air handlers inside the facility.

IV. 4. 4. Fire Protection

The facility shall provide a fire protection system (FPS) in accordance with Air Force
Occupational Safety and Health (AFOSH) and National Fire Protection Association (NFPA)
standards including ETL 01-18, 24 Oct 2001, or European standard, to safeguard against loss
of life and property by fire. In rooms with raised computer floors, fire detection and
suppression systems shall be installed beneath the computer floors as determined by building
code requirements. The installations of the FPS shall be such that it does not interfere with
the simulator equipment installation. Base personnel and Lockheed Martin shall accomplish
this through coordination of the specific equipment layouts. The facility FPS shall be
responsible for shutdown of HVAC and facility power panels that supply electrical power to
the affected facility areas and equipment.

The facility shall supply and maintain the facility fire protection system and fire protection
IAW AFI 91-203, AFI 91-56 and NFPA 12A and 72E, or European standards. The facility is also
responsible for supplying the fire extinguishers required for the facility itself. The facility FPS
shall meet all AFI 91-203 requirements, or European standards, (to include ultra-sensitive
smoke detection systems) and standards without depending on the supplied simulation
system FPS.

The facility shall provide a closed circuit wall RJ11 receptacle from the facility fire control panel
to the simulation Tactical Trainer (TT) room. The closed circuit wall receptacle shall be located
near the Network Rack. See Figure 6.2-1, Electrical Plan View, for details. The facility interface
shall be connected to a closed set of relay contacts (from the fire control panel) that will open
in the event the fire panel intends to shut down the facility.

This interface will be connected to the simulation devices Emergency-Power-Off (EPO) system
to shut down the UPS device(s).

IV. 5. Electrical

IV. 5. 1. Power Requirements and Characteristics

The trainer equipment delivered must be designed to operate from an isolated secondary
electrical power source of the following basic characteristics:

• Voltage: 400 VAC ±10 percent

• Frequency: 50 Hz ±1 percent
• Phases: 3-Phase, wye connected
• Wires: 4-Wire (fifth wire for safety ground)
IV. 5. 2. Power Distribution Requirements Electrical Power Analysis and Estimated Heat Load

Table IV.2-1 lists the connected loads and associated heat dissipation. Figure IV.2-1 presents
the required electrical interfaces. The facility shall provide the trainer power distribution
panels and power cables. All power cables shall be constructed using flexible conduit
terminated to a metal electrical box with power connector. Table IV.2-2 lists the power cable
requirements.

Each Full Mission Trainer (FMT) Visual Display System (VDS) shall have a dedicated power drop
for their emergency lights. The VDS emergency light is required to have a connection to facility
power for maintaining battery charge in the event the FMT equipment power is removed at
end of training day or other reasons. Also, if the facility should ever lose power when someone
is inside the light tight VDS dome the emergency light is required to operate.

All facility rooms shall have EU standard wall receptacles to support maintenance equipment
and additional power distribution.

Table IV.2-1. Estimated Electrical Power Analysis and Heat Load

Table 6.2-2. Estimated Electrical Power Cable Requirements
IV. 5. 2. 1. Trainer Equipment Power Requirements

UPS devices internal to the equipment racks for the FMT and associated equipment will be
provided. These devices will provide clean system power to protect critical equipment from
abnormal power conditions. Integral to the power system is a battery-backup capability to
allow the operators sufficient time, to take the steps necessary to shut down the systems
safely to protect the hardware and prevent data contamination in case of a power outage.

IV. 5. 2. 2. Transient Voltage Surge Suppressor (TVSS)

A transient voltage surge suppressor (TVSS) shall be provided and installed by the building
contractor for transient voltage protection of the source power to the trainer. Electrical power
line transients shall be limited and not exceed two times the nominal line voltage.

IV. 5. 2. 3. Electronic Equipment Transformer

An isolation transformer with delta wound primary and a wye wound secondary shall be
provided for the trainer facility. This isolation transformer shall be dedicated to both FMTs,
the TT, BDS and associated equipment and shall not provide power to any other facility
systems. The transformer will provide isolation from the external power source for safety and
help to suppress electrical noise. The wye secondary neutral shall be connected to facility
(earth) ground.

IV. 5. 3. Grounding

A ground bus bar is required in each room with the simulator equipment and in the
maintenance room for ESD purposes. It shall accommodate a minimum wire size of #6
American Wire Gauge (AWG) or (16.0 mm2) connected to facility ground grid. The ground bus
bar shall be less than 1 Ohm from the ground bus bar to the facility ground rod. The ground
bus bar shall be provided for connecting multiple ground wires, such as a ground rod inside
the facility that is bonded to the facility ground grid outside. The ground bus bar shall be all
copper and secured to the concrete floor under raised flooring or wall in computer rooms.
Each ground bus bar shall be approximately 10 inches (254mm) wide 2 inches (51mm) in depth
with a 0.25 inch (6.4mm) copper plate having at least sixteen (16) holes, 0.28 in diameter, to
accommodate attaching hardware of 1/4-20 size for mounting of trainer ground cables. The
raised floor shall be electrically bonded to the facility ground grid.
IV. 5. 4. Electrostatic Discharge Ground

A ground connection point in the maintenance room shall provide protection per DOD-STD-
1686, as a guide, for parts and equipment during handling and storage. Persons handling ESD-
sensitive items will require training in ESD precautionary procedures.

IV. 5. 5. Lighting

IV. 5. 5. 1. General

Lighting intensities shall be in accordance with MIL-STD-1472C, or European standard

equivalent, as a guide. The lighting shall be fitted with suitable baffles or diffusers to prevent
a glare source. The lighting in the IOS rooms shall be complemented with incandescent lighting
with dimmer switch to provide continuous intensity from full off to maximum brightness. The
light source in the simulator bay shall not interfere with movements of the simulators, or
installation equipment. The lights are adequate for the simulator bays. It is recommended that
the lighting fixtures in the simulator bay be wired in four gangs to accomplish some amount
of lighting selection that will allow selection of Off (No power), 25%, 50%, 75%, and 100% of
maximum illumination.

IV. 5. 5. 2. Emergency Lighting

It is recommended that emergency lighting capability be provided by the facility in the areas
occupied by the trainer equipment. Though not a requirement of the system or essential to
the operation of the system, it is an important safeguard.
In the event of a facility power outage, this built-in emergency lighting capability would
provide strategically placed illumination to allow personnel to shut down any in-place high
investment equipment and to exit the facility safely.
ANNEX 1 – Training Task List
ANNEX 2 – TNI-AU F-16 Configuration
ANNEX 3 – F-16 MTC Training Devices
ANNEX 4 – F-16 Cockpit Configurations
ANNEX 4 – Visual Display System