Product_Specifications.docx

Purchase Specification for F-16 Image Generator PURCHASE SPECIFICATION for

F-16 IMAGE GENERATOR COMPUTER SYSTEM

UNITED STATES AIR FORCE

OGDEN AIR LOGISTICS CENTER (OO-ALC)

SOFTWARE MAINTENANCE DIRECTORATE (519 SMXG/MXDPC)

July 11, 2017

1.0 Background

1.1 The Human Engineering Development System (HEDS) is part of the Software Engineering Division (MAS) located at the Ogden Air Logistics Center (OO-ALC), Hill Air Force Base, Utah. Among other responsibilities, MAS supports all Operational Flight Program (OFP) modifications to the F-16 C/D Block 30 and Block 40/50 OFP aircraft. HEDS is responsible for prototyping the OFP changes and then showing these prototypes in a flight simulator to pilots and others that make decisions about the OFP upgrades.

1.2 Prototyping, simulating, and evaluating an OFP modification is most effective when experienced in an environment simulating actual flight conditions. Current OFP upgrades include the use of a Helmet Mounted Display (HMD) device which will make available to the pilot flight and target information similar to what he sees in the current Heads Up Display (HUD). A big part of immersive flight simulation is the visual scene the pilot sees. 3D graphics computers, known as Image Generators (IG), draw the images for the pilot. These images include the out-the-window (OTW) scene representing the real world, radar and other sensor images simulating real sensor video, and symbology for the HUD, HMD, and Multi-Function Display (MFD) cockpit displays.

1.3 The OTW images will be projected onto the outside (rear projected) of a 16.5 foot diameter spherical dome such that a field-of-view (FOV) approximately +90o to -35o vertical and nearly ±180o horizontal will be achieved. This provides the pilot, located at the center of the dome, with a very wide FOV both horizontally and vertically within which he can evaluate the various aspects of the HMD. The images presented must appear as close to being real world scenes as is possible. Anomalies and artifacts must be reduced to a minimum.

1.4 Simulated real world radar, Charge-Coupled Device TV (CCD) and Forward Looking Infrared (FLIR) images are displayed on the cockpit MFD. This adds to the realism by helping the cockpit look and feel as close to real as possible. The primary motivation is to provide an environment for the evaluation of proposed HMD OFP changes.

1.5 Another part of the system which is valuable to the pilot review team is distributing video from the dome simulator to a video wall where other pilots and system designers can view what is going on in the dome. These views include a channel that is independent of the 30 OTW channels in the dome. This channel is commanded from the host via Common Image Generator Interface (CIGI) View Control to update its 40 degree field of view with the motion of the head tracker on the helmet. This view must also support the symbology Dynamically Linked Library (DLL) so that the Helmet symbology can be drawn in the center of this view at all times. This view is referred to by HMD+OTW below. Other views that are distributed to the video wall are the two MFD displays a Center Display Unit (CDU) and the HUD.

2.0 Objective

2.1 The primary objective is to provide an environment that creates images as close to being real world scenes with minimal anomalies and artifacts. The primary purpose to achieving this objective is to enhance the evaluator’s ability to evaluate a proposed Helmet Mounted Display OFP change(s). A secondary objective is the dome is used as a marketing tool. Almost all dignitaries that visit Hill AFB tour building 1515 and are shown the dome simulator. Therefore, the databases need to be high quality, with high density of 3D buildings and features, and have large areas of 1 meter or better resolution imagery on the terrain.

2.2 The required IG computer system is described by this specification. Other parts / systems mentioned herein will be provided by other vendors. The IG system shall be compatible with and integrate with all the other components of the F16 simulation system. This purchase is to replace an existing Windows XP Image Generator with a Windows 10 Image Generator.

2.3 While the OTW must be as real world as possible, it is also important for the Sensor visuals also be convincing as a true representation of the actual sensor device whether it is Radar, CCD or FLIR which are viewed on the MFD screens and CDU. It is also important that the IG vendor provide an easy to use Plug-in capability to the real time rendering software to allow the HEDS team to run a DLL which draws the symbology over the sensor video on the MFD screens and the CDU.

3.0 Scope

3.1 The scope of the IG computer systems involves:

1. A pre-award site visit to finalize the vendor installation requirements and the IG system requirements (make sure vendor and HEDS group have a complete understanding of what is expected and will be delivered).

2. This purchase is to replace an existing Windows XP Image Generator with a Windows 10 Image Generator with all the same functionality and integration requirements.

3. Setup of the Image Generator computer systems which would include onsite installation, an initial alignment and calibration of the OTW viewports, and integration.

4. Integration with the auto alignment system which is provided by Scalable Display Technologies.

5. Integration with other systems: Video signals will be provided by the IG computer system that will drive projectors provided independently of the IG computer system and not covered under this specification. The spherical projection screen will also be provided independent of the IG computer system and is not addressed in this specification. It is anticipated that the providers of the IG, display screen, auto alignment and the projection system will be required to coordinate implementation of the completed system as their respective components are incorporated in the final assembly. This coordination will be effected by the delivery of required documentation and technical support. Similar documentation and technical support will be provided by the vendors of the projection system, auto alignment and display screen providers and will be available to the IG computer system provider.

6. Acceptance testing, training, and system documentation.

7. Technical support for maintenance and integration (initially in person, followed by phone and a means to enter problem reports to be handled by technical support of vendor)

8. Provision of a standard commercial minimum one year warranty which covers parts and labor.

3.2 System characteristics

3.2.1 The IG will draw the following types of channels: 30 OTW, Radar, FLIR, CCD, HMD+OTW.

3.2.2 The IG system will drive video projectors illuminating a spherical dome display screen. The dome is a partial sphere with a diameter of 16.5 feet. It covers nearly 360o horizontally, 90o up vertically, and 35o down vertically. This covers the majority of the FOV the pilot can see in an actual F-16. The view must appear as if looking out from inside of a cockpit to the real world. (For example, while flying over flat terrain, the horizon line will appear as a flat, straight line across the entire screen, through all associated channels. This horizon line will continue to appear flat and straight as the scene moves and rotates, as would occur while the pilot performs roll, pitch and yaw maneuvers.)

3.2.3 The evaluation of OFP change candidates involves a number of people. To assist in the evaluation, selected video images are presented in a theater environment. This video will include a repeat of the MFD displays, CDU and an OTW view showing some of what the pilot is seeing (in the cockpit), and a HUD window. The OTW view will track with the pilot’s head to show what he is seeing in a 40 degree field of view. This view requires an additional IG channel and does not correspond to any one channel within the dome. It will also show the HMD symbology on top of the OTW view (referred to as HMD+OTW below). The HMD symbology is the helmet symbology which is similar to a HUD with situational awareness and weapon targeting information.

3.2.4 Sensor imagery will be provided for display on the cockpit MFD displays. Radar, FLIR, and CCD video will all be selectable on these displays. The display can be zoomed in and out. These sensor images need to be as real-world as possible. HEDS symbology will be displayed on the MFDs as well. There is a new Center Display Unit which is similar to an MFD but has higher resolution. The Center Display Unit has 768 X 1024 pixels resolution. At this point the design is to have only the FLIR/CCD and Radar video displayed on the CDU. The Sensor video is 768 X 768 pixels resolution; the HEDS DLL symbology needs to be able to draw to the entire 768 X 1024 pixel display size. We will need a video switch that is capable of three outputs and 3 inputs. Or a second video switch that just handles the higher resolutions CCD/FLIR and Radar and one output to the Center Display Unit.

3.2.5 The visual and sensor database(s) will be provided for a worldwide database with high resolution insets. It is required that all of the United States be 1 meter or better resolution imagery and terrain be generated from DTED Level 3 for detailed areas. All of the databases Sensor and Visual must correlate. The database will be detailed enough to provide realism and not distract from the evaluation of OFP changes. The vendor shall provide detailed information on the coverage area of databases and details about areas of interest. We require high detailed insets in many areas of the world, such as, then entire United States, the Middle East, Afghanistan, Korea, and Japan.

3.2.6 Acceptance testing will be performed onsite to validate system capability. Training on the use, maintenance, and troubleshooting of the system will be supplied by the vendor. Applicable documentation will also be supplied in common electronic format (i.e. PDF, MS Word, etc.) along with technical assistance as needed with software and hardware questions for maintenance and integration of HEDS software. The government will be permitted to share any documentation and information acquired by training or technical assistance with auto-alignment, projection system and screen vendors as required to integrate associated components of the full simulation system. Similar information will be available to the IG provider from the auto-alignment, projection system and display screen providers.

4.0 Specific Tasks

The contractor shall be directly responsible for ensuring the accuracy, timeliness and completion of all tasks assigned under this contract. Specifically, the contractor will perform all tasks described in this section.

4.1 PREAWARD SITE VISIT (IF NEEDED) this will only be needed if not awarded to current IG Vendor, as this is a replacement Image Generator.

4.1.1 Vendor Installation Requirements. Visit to ensure all the requirements to have a successful installation of the vendors IG will be met.

4.1.2 Onsite IG System Requirements. To make sure vendor and HEDS group have a complete understanding of what is expected and will be delivered. Especially covering all integration issues with the system.

4.2 BUILD OR CAUSE TO BE BUILT AND THEN DELIVER all of the items listed in section 5.1 that is part of the Image Generator to 6137 Wardleigh Rd., Hill AFB, UT 84056. There are items listed in this section that will be provided by other vendors.

4.3 SET UP OF THE COMMERCIAL OFF-THE-SHELF (COTS) IG COMPUTER SYSTEMS

4.3.1 Onsite Installation. The IG computer system hardware and software will be installed at 6137 Wardleigh Rd., Hill AFB, UT 84056. All cabling within the IG. All other installation processes which are necessary to affect a functioning IG.

4.3.2 View Alignment. The viewports of each of the 30 OTW channels will be aligned and adjusted as necessary to achieve a seamless display between channels. The projectors will have been mounted and aligned previously. The IG vendor will integrate with the auto alignment system.

4.3.3 Integration. The IG Vendor will supply integration support to HEDS engineers and auto alignment vendor to make sure Host integration, channels requiring symbology DLL, and projector alignment tasks are all completed to satisfaction of customer. (The symbology DLL may take longer to get running, as long as vendor supports this effort over the phone and via emails this will suffice)

4.4 ACCEPTANCE

4.4.1 Acceptance Testing. Acceptance testing will be performed onsite to validate system capability.

4.4.2 Operation Instruction / Training. Instruction on the use, maintenance, and troubleshooting of the system will be provided at time of acceptance testing.

4.4.3 Documentation. Applicable documentation for the use and maintenance of the system shall be provided on a common electronic medium in a common electronic format (i.e. PDF, MS Word, etc.)

4.5 WARRANTY The IG shall have a standard commercial warranty of a minimum of 1 year against defects and workmanship to cover parts and labor.

Extended warranties shall be quoted as an option.

4.6 Technical assistance and support as needed with software and hardware questions for maintenance and integration of HEDS software.

5.0 Deliverables/Delivery Schedule

DELIVERABLES - All of the following deliverables shall be delivered on or before 18 calendar weeks after contract award. The characteristics and functional requirements are described in section 6.0. The simulation system will be comprised of the following deliverables. The IG Vendor shall provide a turnkey solution that satisfies all the requirements of this specification.

The components in this specification that are outside the IG are listed here for reference only. The IG vendor must deliver a fully functioning system and demonstrate that all software running on the delivered hardware meets the requirements of this document.

The following items shall be delivered.

5.1 Deliverables.

5.1.1 Semi-Sphere Dome Display Surface. (Not part of this spec. – ref only)

5.1.2 Digital Projection System. (Not part of this specification – ref only)

5.1.3 Auto Alignment/Blending Hardware & Software (Not part of this specification – ref only) However, IG vendor must integrate with the Auto Alignment/Blending system which is provided by Scalable Display Technologies. HEDS will only accept auto alignment that executes on the graphics boards NOT on external video processing cards.

5.1.4 IG computer system hardware This includes all PCs, this must be a Windows 10 or newer OS based IG, rack, video switcher, disk drives and cabling inside the rack as necessary.

5.1.5 Image Generator Computer System Software. This is the real-time software controlling the simulation graphics, load management, database paging, etc. This software will be loaded onto the deliverable IG systems.

5.1.6 Sensor System Software. This is system real-time software used to generate the Radar, CCD and FLIR sensor video and handles load management, database paging, etc. This software will be loaded onto the IG system. This includes a copy of the software that HEDS can re-load on the system if necessary.

5.1.7 Image Generator Visual Database. This is the OTW visual database(s).

5.1.8 Sensor Databases. This is the FLIR, CCD and Radar database(s).

5.1.9 Grid Post elevation Data. Matching Grid Post data is required in our Host software for mission functions.

5.1.10 Video Switch(es). Controls switching sensor video feeds to MFDs and CDU. May require more than one switch.

5.1.11 Head Tracker. This is for Helmet Mounting Cueing system. (Not part of this specification – for reference only)

5.2 DELIVERY SCHEDULE

· Vendor installation Requirements

· Onsite IG System Requirements 4.1

4.1.1

4.1.2

YES

TO ARRANGE

THE MEETING

Within 2 weeks prior to award.

4.2

· Onsite installation

· View Alignment

· Integration

4.3

4.3.1

4.3.2

4.3.3

· Acceptance Testing

· Operation Instruction/ Training

· Technical support

· Documentation 4.4

4.4.1

4.4.2 4.4.3 4.4.4

6.0 FUNCTIONAL AND PERFORMANCE SPECIFICATIONS

The simulation systems are for engineering purposes. There is no current plan to support flight training of pilots with this IG, although this may change. As an engineering system, the requirements will change over time. The specifications detailed below represent the requirements at this time. Continued development and support of the IG after the systems are installed and operational is anticipated via new contractual agreements. The components in this specification that are outside the IG are listed here for reference only.

6.1 Display System (not part of this specification – for reference only)

6.1.1 Spherical Dome (Rear Projected) 16.5 foot diameter

Dome has nearly 360 degree field of view horizontal, and + 90 degree up and 35 degree down vertical. Specification of dome is available if desired.

6.1.2 Projectors

Commercial projectors with 1080p or 1920 x 1200 resolutions will be used. We are currently using projectors that have no undesirable latency time within the projectors. The auto alignment/blending is done by Scalable Display Technologies. Specification for the projectors, projector mountings, and display are available if desired.

6.2 Image Generator Computer System

6.2.1 General Requirements

6.2.1.1 The system shall be PC based Windows 10 Operating System or newer and use diskless technology (no disks drives in the channel render computers). Only one set of disk drives to swap out for classified swap out.

6.2.1.2 The IG shall have a 20 Terabyte or larger database server configured in a Raid5 or similar configuration.

6.2.1.3 The IG operating system shall be MS Windows 10 or newer.

6.2.1.4 IG vendor must integrate with the Auto Alignment system provided by Scalable Display Technologies. HEDS will only accept auto alignment that executes on the graphics boards of the IG, NOT on external video processing cards.

6.2.1.5 The system must be scalable such that additional channels can be added in the future.

6.2.1.6 No decrease in frame rate is acceptable due to overloading. Load management techniques will be employed in order to maintain constant frame rate in visually complex areas. Overload management strategy selection should be provided (e.g. complexity versus frame rate).

6.2.1.7 In case of an overload, the system should provide information on which channel is responsible for overloading the system.

6.2.1.8 No noticeable terrain, model, or texture LOD popping is allowed.

6.2.1.9 No more than one frame drop or skip is allowed within a 15 minute period.

6.2.1.10 A minimum of 60 nautical miles visual range shall be supported when no atmospheric effects are present.

6.2.1.11 The number of polygons per second performance shall be sufficient to render high fidelity terrain and models with texture, anti-aliasing, fog, and other possible effects. Yet the terrain and model polygon counts shall not be so high as to cause overloading.

6.2.1.12 The IG shall generate a stable image while maintaining compliance with these requirements for own-ship speeds from 0 to 800 knots for normal operation with no artifacts or objectionable effects.

6.2.1.13 Paging of geometry and texture shall handle low or high level flight for the speeds already specified.

6.2.1.14 The compute performance of the various channel types (OTW, FLIR, CCD, Radar, etc.) shall be sufficient such that no channel lags behind another in its rendering. All channels must operate at 60 Hz.

6.2.1.15 IG shall be able to instantiate (create) moving models at any time during the simulation under host control. This is for such capabilities as launching a missile or bomb and being able to observe it travel to its target.

6.2.1.16 The system shall provide the ability to have access to all renderers through a KVM switch or other means at the console and for outputting each renderer video to a monitor for debugging.

6.2.1.17 The ability to send data from the Host to the IG via a gigabit network is required and this data needs to be delivered to the sensor and HMD+OTW channels. The data is state data for the HEDS symbology DLL. This must be an additional network connection independent of the CIGI Host to IG connection.

6.2.1.18 Mission Functions. Provide for sending of limited data from IG to Host (e.g. messages, acknowledgements, height above terrain (HAT), line of sight (LOS), etc.).

6.2.1.19 The tools and software libraries (SDKs) required for integrating HEDS symbology software shall be provided.

6.2.2 OTW Channels

6.2.2.1 For the 30 OTW channels, a 60 Hz frame rate is required and shall be gen-locked or it must be demonstrated at acceptance test that software frame locking is capable of looking as good as gen-locked hardware (no tearing across channels at any time during flight).

6.2.2.2 The placement of the 30 OTW channel projectors on the dome surface has been arranged such that they can be paired using the dual outputs of the video graphics cards. All projectors are laid out one above the other, creating a 1920 x 2160 (2 x 1080) arrangement.

6.2.3 MFD & CDU Channels

6.2.3.1 Three IG sensor channels FLIR, CCD and Radar will be used to drive two MFD displays.

6.2.3.2 The resolution for the MFD video channels shall be 480 x 480 pixels and a 480X640 @ 60HZ video format can be used for this. An MFD display can be shipped to vendor for testing.

6.2.3.3 A 768 x 768 pixel resolution CCD/FLIR and Radar video to be displayed on the Center Display Unit. The CDU display resolution is 768 pixels high and 1024 pixels wide. HEDS symbology needs to draw to the entire CDU screen, primarily when video is blanked.

6.2.3.4 The way we chose to handle the difference in MFD and CDU resolutions, is to have two CCD/FLIR channels. We do not need a scan convert as stated here in this image.

6.2.3.5 A frame rate of 60 Hz is the minimum acceptable for the Sensor channels.

6.2.3.6 One MFD channel will render the radar imagery.

6.2.3.7 Two channels will render the other sensor imagery, FLIR or CCD. Each channel could be either FLIR or CCD, configured at system start up. Thus, there could be two FLIR channels, one FLIR and one CCD, or two CCD channels. (Two FLIR channels is possible, one from a targeting pod the other from a Maverick.)

6.2.3.8 The CCD video will be monochrome views of the visual database. Supporting Color video CCD is a possible future requirement please note if the system can support this.

6.2.3.9 As stated earlier 768 X 768 pixels video will also be needed for the Center Display Unit which may require switching an additional channel of CCD/ FLIR to this display. If this can be done in another way please describe in the proposal.

6.2.3.10 The sensor channels shall support standard minimum pixel configurations of 32 bit RGBA, double buffering, and 24 bit depth.

6.2.3.11 The video output from the two sensor channels will be selected with a video switcher to drive the two MFD display devices such that any MFD channel can display IR/CCD or Radar any MFD display device. This can be accomplished with one switcher that has two video outputs.

6.2.3.12 As stated above there is a need to have higher resolution FLIR/CCD and Radar video switched to a single 768 X 1024 pixel display in much the same way as above.

6.2.3.13 The IGs that will be rendering FLIR, CCD and Radar MFD images must have texture memory sufficient for their own needs as well as for HEDS symbology code. HEDS symbology includes a moving map capability only displayed when video is blanked. The moving map texture will have a lower resolution than the geo-specific texture will and will not cover the entire database.

6.2.3.14 It is important to note that we need the HEDS symbology DLL to run on the Sensor channels. We do not want to rework how we do symbology to work with a command driven symbology system like GL Studio. We need the IG to support a plug-in DLL which will draw our symbology using OpenGL. This is because we want one code base for both this DLL and our desktop simulation symbology.

6.2.3.15 The FLIR, CCD and Radar channels shall have the ability to blank the sensor video per command from the host, while continuing to render symbology. (Not all symbology displayed on the MFD is associated with sensor video.) This is also the case for the Center Display Unit. There are pages on both the MFDs and the CDU that display symbology with no video.

6.2.3.16 The radar channel video done by the IG is for air-to-ground radar only. HEDS will do the air-to-air radar in the HEDS plug-in. This means vendor only needs to supply video of simulated ground radar sweep of terrain and any 3D geometry on the ground, also note new requirement in 6.2.3.20 for Synthetic Aperture Radar.

6.2.3.17 The radar channel must support receiving commands from the host to modify the ground sweep. For example, half angle of sweep can be changed from 60 to 30 to 10 degrees and must be positioned based on an azimuth location. We need to be able to command the radar to meet the APG 68 radar model.

See section 6.3.2.7 for more details on these requirements.

6.2.3.18 HEDS must be able to display symbology overlaid on any sensor channel on the MFD or CDU and the OTW+HMD channel. Overlaid means that the symbology obscures / occludes any / all sensor video behind it. The real-time software will need to load a DLL plug-in containing HEDS code to draw the symbology.

6.2.3.19 HEDS has a new requirement to do AESA Synthetic Aperture Radar so this will be an additional requirement over the existing system that we are replacing.

6.2.4 OTW+HMD Channel

6.2.4.1 The OTW+HMD channel listed above is a channel with HMD (Helmet) symbology overlaid on an OTW view with a 40 degree FOV that will be displayed to an audience on a video wall and not to the pilot. The OTW part of this will be a view that tracks with the pilot’s head and shows what the pilot is seeing in the OTW channels within the dome. (The HMD symbology will remain static within this display.) The HMD is the Helmet symbology done as an overlay over the OTW. The view will be controlled from the host via CIGI view definition and view control packets.

6.2.5 OTW Software

6.2.5.1 The vendor shall provide a plug-in architecture for inserting HEDS code into the IG runtime software for the purpose of rendering symbology. Other means of producing symbology (e.g. VAPS, GL Studio, others) will not be used. The HEDS DLL utilizes OpenGL to render the symbology. It is vital for it to do this on ALL sensor channels and the OTW+HMD channel. If the vendor’s IG supports plug-in for symbology on all channels please note it in proposal.

6.2.5.2 Latency, defined as the interval of time from when new host data is available to the input of the IG until the corresponding video image is completely displayed, shall not exceed 64 milliseconds.

6.2.5.3 The database and IG rendering process shall use at least 64-bits of positional and 32 bits of angular data for terrain, features, and moving models displayed in the scene and for Host and IG communication. The least significant bit (LSB) of the positional data shall not be greater than 0.01 feet, and the LSB of the angular data shall not be greater than 0.001 arc seconds.

6.2.5.4 Host -IG communications shall be “over the wire” utilizing a mature interface (e.g. CIGI). The protocol ICD, software development tools and libraries utilized by the vendor shall be provided. Technical assistance shall also be provided.

6.2.5.5 The IG software will be able to render and provide for the control of a minimum of 100 moving models. These models will consist of aircraft of various types, ground vehicles, watercraft, missiles, and bombs. Special effects shall also be provided for some of these, including but not limited to missile trails, explosions, dust clouds, and wakes.

6.2.5.6 Shall be able to instantiate moving models at any time during the simulation. This is for such capabilities as launching a missile or bomb and being able to observe it travel to its target.

6.2.5.7 The system shall contain software to perform self-diagnostics. This is meant to act as a daily operational readiness check, as well as a means to identify problems during troubleshooting.

6.2.5.8 The system will employ a predictive paging algorithm to ensure that terrain and texture within visible range is rendered and no popping of terrain is noticeable.

6.2.5.9 The IG rendering software shall be built upon the OpenGL graphics API for compatibility with HEDS software or show that the system can render OpenGL symbology including texture maps.

6.2.5.10 A round earth model shall be used to render the OTW.

6.2.5.11 The IG shall be capable of environmental effects including: fog and fog layers, volumetric clouds, missile trails, tracers, explosions, and time of day control (Day / dusk / night).

6.2.5.12 Faithful star fields are not required.

6.2.5.13 The IG shall be capable of airport lighting systems including REIL, VASI, PAPI, MALSR, strobe, rabbit and beacon support for raster displays.

6.2.5.14 Shall be capable of searchlight, landing and hover lobe rendering.

6.2.5.15 Shall be capable of cultural and area lighting.

6.2.5.16 Shall support WGS-84 Geo-centric Round Earth terrain models.

6.2.5.17 The ability to scale moving models in the OTW view for recognition shall be provided.

6.2.6 Sensor Software

6.2.6.1 FLIR will emulate the F-16 LITENING AT TGP, SNIPER TGP, and Maverick missile sensors.

6.2.6.2 The following table lists the effective range, wave bands, and FOV parameters for the LITENING AT and SNIPER TGP and Maverick FLIR sensors. The effective range is the max distance at which detail is discernable. The sensor can sense out much farther but with reduced detail. Max visibility shall be 80 miles. The Max visibility range shall be adjustable.

0.125o 0.5ox0.5o

6.2.6.3 The FOV will be selectable and controlled from the host.

6.2.6.4 For LITENING AT, the continuous FOV range is from 4.0ox4.0o down to 0.25ox0.25o for FLIR and from 3.5ox3.5o to 0.25ox0.25o for CCD, inclusive of all modes and zoom ranges. It also has a 24.0ox24.0o FOV SWIDE mode for FLIR.

6.2.6.5 For SNIPER, the continuous FOV range is 3.6ox3.6o down to 0.25ox0.25o for FLIR and from 0.5ox0.5o to 0.125ox0.125o for CCD, inclusive of all modes and zoom ranges.

6.2.6.6 Sensor special effects include gain, noise, polarity, plumes atmospherics, and per Texel radiance.

6.2.6.7 The FLIR, CCD and Radar sensor software shall have the ability to stop rendering (blank) the sensor imagery by command from the host while continuing to render symbology generated by the HEDS DLL.

6.2.6.8 The rendering to the MFD channels will run HEDS software that will load grid post elevation data and texture images. This rendering is only done when the Sensor Video is blanked. HEDS initialization code must have the ability to do this and control the paging of this data. (If paging information can be supplied by the vendor software, it may enable HEDS to be consistent with the vendor terrain paging.)

6.2.6.9 The rendering time of symbology with HEDS code shall be included in the IG load management calculations. (HEDS does not at this time have a meaningful estimate on the rendering time for symbology, either Helmet or MFD. We have been successful running this symbology code on all channels of an Aechelon PC Nova IG. Symbology will typically be 2D lines only.) It is suggested the vendor be able to distinguish between this and HEDS symbology code rendering time and report problems as appropriate.

6.2.6.10 FLIR sensor images can come from two sources and it is therefore possible to have an FLIR image on both MFD displays. However, these sensor images will not be the same. The IG system shall produce two FLIR sensor images with different eye points. This same requirement applies to the CCD video. (E.g. the targeting pod can slew / gimbal its camera to any forward position or the view from a Maverick missile will change as the missile is in flight.) This is not typical but the system needs to be able to do this and demonstrated in acceptance test.

6.2.6.11 All necessary software and configuration files shall be delivered and integrated to generate radar APG-68 images, and support AESA Synthetic Aperture Radar.

6.2.6.12 Physics based calculations include advanced heat transfer algorithms based on real-time environmental conditions (time-of-day, day of year, latitude, longitude, humidity, rate of precipitation, etc.)

6.2.6.13 Calculate real-time atmospherics based on a fully validated model, and is easily controlled from IG system control.

6.2.6.14 Calculate the integration of these affects across the prescribed wavelengths for the sensor being simulated.

6.2.6.15 If radar related symbology is displayed by the vendor, the source code must be available and modifiable by HEDS. Otherwise the vendor will not display symbology and HEDS will assume full responsibility for displaying radar symbology.

6.2.6.16 HEDS has a new requirement to do AESA Synthetic Aperture Radar so this will be an additional requirement over the existing system that we are replacing.

6.2.7 IG Test Patterns

6.2.7.1 IG Vendor shall deliver all test patterns or similar to those identified in Appendix A of this specification by integration time defined in 5.2 delivery schedule Item # 3.

6.2.8 Hardware

6.2.8.1 All PCs in the system will be controlled via one centralized interface. System operators will not need to boot each PC independently.

6.2.8.2 “Diskless”, i.e. all PCs boot from a common disk. All render channel PCs do not have disk drives.

6.2.8.3 Removable hard disk drives shall be supplied.

6.2.8.4 The contract will have an option for a complete set of spare hard drives please quote separate cost for these if option exercised all spare hard drives shall be supplied.

6.2.8.5 The best industry COTS PC graphics card available at the time of purchase shall be utilized in the delivered final product for all IG channels.

6.2.8.6 The OTW channels shall support standard minimum pixel configurations of 32 bit RGBA, double buffering, and 24 bit depth or better.

6.2.8.7 The OTW channels shall be capable of up to 16 sub-pixel samples (SPS) programmable FSAA, or better. This is variable depending upon the display resolution, i.e. the higher the pixel count the lower the SPS can be. We will most likely run at 8 sub-pixel samples.

6.2.8.8 Transport delay / latency through the IG shall be 60 msec. or less.

6.2.8.9 Each IG channel will have sufficient main memory to load the database structure and models necessary to render the OTW, FLIR sensor, or Radar views from the eye point out to the minimum 60 mile visual range; the FLIR sensor, or radar views from the eye point out to 120 mile range.

6.2.8.10 Sufficient disk storage space shall be provided to store all terrain, model, texture, and configuration data provided with the system on shared storage hard drives. There needs to be the ability to expand the hard drives in the removable bays, unless vendor is supplying significantly more than 20 T-byte minimum.

6.2.8.11 The IG system shall have high availability. There shall be one of each type of major component of the IG provided as a spare to reduce down time. For example, a main control computer, a sensor renderer, and an OTW renderer.

6.2.8.12 1 Gbit Ethernet connection for host to IG communications.

6.2.8.13 HEDS will also require a second 1 Gbit Ethernet connection for sending information to the plug-in DLL. See sect. 6.2.9 for details.

6.2.8.14 The IG will be network ready.

6.2.8.15 Video Switch (See also section 6.2.3.12) accomplished with one video switch with two outputs for MFDs and one output for CDU.

6.2.8.15.1 There could be one complex or two complex switches each controlled by the host computer.

6.2.8.15.2 MFD switch has two video inputs: Radar, FLIR/CCD. And two outputs to the left and right MFDs.

6.2.8.15.3 CDU switch has two video inputs (hi res) FLIR/CCD and Radar. And one output the CDU.

6.2.8.15.4 Both or single switche(s) mounted in the IG rack.

6.2.9 HEDS Data Transfer. HEDS will transfer data to the embedded DLL via a UDP socket connection distinct from the connection used for CIGI protocol. Average transferred per frame are 2K bytes, peak are 4k bytes.

6.3 Databases

6.3.1 Out-The-Window (visual)

6.3.1.1 The IG vendor is encouraged to offer OTW and Sensor databases that have been developed for other government contracts. The databases proposed must have representation of all types of terrain i.e. mountains, plains, lake/sea shore, forest, fields, suburbs and city.

6.3.1.2 Vendor to provide total area of coverage, coverage area (sq. miles) of high detailed AOIs, coverage of high detailed imagery (1 meter or better), areas containing 3D features (building, trees etc). The database(s) is going to be very important in this award. Vendor shall provide details about the databases included in the proposal.

6.3.1.3 The visual database(s) must have large areas of high detail (1 meter or better) imagery for at least 250 miles by 250 miles square in at least one high detail area of interest.

6.3.1.4 There must be at least one significant area of mountainous terrain where the DTED used to produce the terrain is at least DTED Level 3 or higher. This area must also have 1 meter imagery or better and it should be obvious looking at this area how well the imagery matches all the high and low points and ridges of the of the higher resolution terrain.

6.3.1.5 The following areas are of interest high detailed. The databases must include the following areas.

6.3.1.5.1 Hill Air Force Base, UT, centered in a 250 miles by 250 miles to include the UTTR ranges.

6.3.1.5.2 Nellis Air Force Base, NV and target ranges.

6.3.1.5.3 Iraq and Afghanistan.

6.3.1.5.4 The entire United States with 1 Meter imagery.

6.3.1.5.5 Japan and Korea.

6.3.1.6 Example of expected high detail insets. Cover 16 geo-cells in a 4X4 grid of data. The outer boundary of geo-cells will be a minimum of 5 meter imagery and level 1 DTED elevation data. The inner 4 geo-cells 2X2 grid will have the airfield or point of interest fairly close to center in it. And these geo-cells will have a minimum of 1 meter imagery and the airfield and approach areas using about 0.25 meter imagery. These areas will also have 3D buildings, trees, towers and other features.

6.3.1.7 This minimal database size must be part of a larger lower resolution database for the entire world.

6.3.1.8 If possible source DTED data for the databases should be delivered.

6.3.1.9 Taking off and landing on a runway is not a priority. The database should include appropriate runway lights, etc. for runway exercises.

6.3.1.10 Multiple resolution texture shall be used (MIP). The highest resolution shall include better than 1 meter resolution for high detail areas such as runways and cities.

6.3.1.11 General minimum terrain resolution is better than 10 meter grid posts.

6.3.1.12 DB shall include 3D static models of buildings at runways and other municipal areas in high detail areas.

6.3.1.13 Lights for runways and populated areas (although, there is no requirement to land/takeoff) this would include cultural lighting for cities in high resolution areas.

6.3.1.14 The database shall have sufficient data to report HAT info for ground collision information.

6.3.1.15 The database shall employ a sufficiently large number of polygons such that high fidelity to the real world is achieved. However, the numbers shall not be so high as to lead to overload conditions for the IG hardware and software.

6.3.1.16 A minimum of 100 independent moving models controlled by and dynamically created by the host via CIGI is required.

6.3.1.17 Animated human models are not required, but if included at no additional charge there may be future needs for this.

6.3.2 Sensor Database

6.3.2.1 Must correlate with the visual database.

6.3.2.2 The radar and FLIR database(s) shall be derived from the same database as the OTW database to assure correlation. The FLIR can be derived from true multi-spectral data; this would give the most accurate FLIR simulation.

6.3.2.3 The required sensor modes include: Radar, FLIR and CCD.

6.3.2.4 The database shall be materially classified to support the above listed sensor modes.

6.3.2.5 The sensor database shall contain sufficient information for physics based calculations. Each texture Texel will have classification codes describing the material for FLIR and radar as necessary.

6.3.2.6 The radar graphics shall present an APG-68 radar simulation. Therefore the database will contain the necessary and applicable attributes to provide the APG-68 radar model.

6.3.2.7 APG-68 Radar shall include the following Air to Ground capability.

6.3.2.7.1 Air to Ground Modes

1) Ground Map (GM) 2) Doppler Beam Sharpening (DBS)

3) Expand 1 & 2 Beacon Mode (BCN)

4) Air to Ground Ranging (AGR) 5) Standby & Off

6.1.2.8.2 Display Modes

1) Normal (GM) 2) Expand (DBS) 3) Freeze (GM/SEA/BCN)

6.1.2.8.3 Description of these capabilities.

1) Ground Map (GM) Mode – Normal Normal sectored PPI display.

Drift stabilized scan pattern.

Display centered about the cursor.

Range scales: changed from host (5, 10, 20, 40 nautical miles) Range Control: options Auto or Manual.

Scan Widths: changed from host (10, 30, 60 degrees)

2) DBS Expand Two modes DBS 1 and DBS 2 (these are expand “zoom” modes) Cursor centered in the Expand patch.

Expand patch size function of range scale.

Scan pattern and the map stabilization are referenced to a point on the ground map.

3) Beacon Mode (BCN) Detects ground based and airborne beacons. PPI display.

Freeze can be selected in BCN.

4) Air to Ground Ranging Mode (AGR) Provides accurate range to ground information.

5) Standby Mode (STBY) Non-radiating mode.

6.3.2.8 HEDS has a new requirement to do AESA Synthetic Aperture Radar so this will be an additional requirement over the existing system that we are replacing.

6.3.3 Grid Post Elevation Data

6.3.3.1 Grid post elevation data for the database shall be supplied in DTED format.

6.3.3.2 Elevation data shall correspond to the visual database at its highest LOD as triangulated. That is, if the grid post does not correspond to a terrain polygon vertex, the elevation is calculated from the polygon elevation at that point. (This applies more specifically to TIN terrain rather than regularly triangulated terrain.)

6.3.3.3 The spacing of the grid posts shall be the same as for the raw DTED used in building the terrain.

6.3.4 Required Moving and Static Models.

Some of the models shall include damaged states, as indicated. Both OTW and sensor attributes of the models are needed.

A library of models containing a variety of military aircraft, vehicles, animations and special effects that are optimized for the IG to support fixed wing simulations and that can be included by the user into the visual and sensor scene. A tool capable of converting open flight models to a format usable by the IG shall be provided. A variety of buildings for ground targets shall be provided that can be placed onto the terrain.

AIR Targets

6.3.4.10 MIG-25

6.3.4.11 MIG-23

6.3.4.12 MIG-29

6.3.4.13 SU-27 Flanker Russian Fighter

6.3.4.14 SU-37 Flanker Russian Fighter

6.3.4.15 E3A - AWACS

Ground Targets

6.3.4.16 M1 - Tank

6.3.4.17 M60 - Tank

6.3.4.18 T72 – Ground Vehicle.

6.3.4.19 Bradley – Tank

MISSILES

6.3.4.20 SAM site - multiple surface to air missiles

6.3.4.21 AIM 9

6.3.4.22 AIM 7

6.3.4.23 A120

6.3.4.24 HARM

6.3.4.25 Maverick

6.3.4.26 Additional Air Target Models

6.3.4.27 Additional Ground targets buildings etc. that have damage states that can be placed in the scene.

6.3.4.28 Special Effects such as Air and Ground explosions, missile trails, gun tracers etc. available to use in the Simulation.

6.4 Physical Facilities

6.4.1 Room width and length is approximately 60 by 48 feet and ceiling height is approx. 19 feet.

6.4.2 The Image Generators will be housed in a server room left of the top of the stairs in this drawings lower right corner.

6.4.3 Each dome system should use approximately 25% of this space, because a total of four systems will occupy this space, 3 of which are domes.

6.4.4 There is a support column at the center of the room.

6.4.5 There is a hydraulic lift in the center of the north wall (the room floor is below the hallway floor).

6.4.6 Stairways at the west wall extending into the room and at the south-east corner extending north along the east wall further restrict the space.

6.4.7 There is no direct exterior access to this room.

6.4.8 Largest access to this room is a 6 by 7 foot doorway (middle of north wall).

6.4.9 Center post is approximately 17.5 ft from north wall and centered east to west (i.e. 30 ft from west wall).

6.4.10 Refer to the following diagram for more information (dome placements are for illustration only). North is at the top of the diagram.

6.4.11 A more detailed drawing with all measurements is available if desired.

6.5 Warranty

6.5.1 The IG shall have a standard commercial warranty of a minimum of 1 year against defects and workmanship to cover parts and labor. Extended warranties shall be quoted as an option.

6.6 Documentation

6.6.1 Applicable documentation for the use and maintenance of the IG system will also be provided on electronic medium.

Acceptance Test Plan Operation and Maintenance Manual Interface Control Document Software Manuals and Licenses for all components of the system A list of all third party licenses or other material that will be needed to perform any and all tasks specified in this specification.

· Visual and Sensory databases

7.0 Acronyms

DTED Digital Terrain Elevation Data

HMCS Helmet Mounted Cueing System

TIN Triangulated Irregular Network is a type of terrain model. Most terrain models are regular grid of polygons that fit the elevation grid.

Appendix A – Test Patterns

The test patterns described below are examples from our current IG. Test patterns like these must be available from the Image Generator for routine maintenance and calibration of the display system. It must be easy to bring up test patterns from a GUI and select the different types from a simple drop down list. Test patterns similar to or equivalent to these that can be used for the purposes listed in the Uses section of each pattern below.

The composition and application of each test pattern is described in this section.

1. Spherically Mapped Dot Pattern Description: This is an array of white light points spherically mapped on a black background as lines of elevation and azimuth on a unit sphere, centered on and fixed with respect to the theoretical eye point. The critical features of the pattern are:

1. A line along each channel boundary

2. A line on the major horizontal and vertical axis of each channel

3. Some means of highlighting the center major horizontal axis and the major vertical axis of each channel. The separation of light points between major intersections should be typically 1degree. For optimum alignment at channel boundaries, the light points should be anti-aliased.

The separation between lines of elevation and azimuth should be 5 degrees. The Light point size should be clearly seen in the cockpit environment.

Uses: This pattern is used in conjunction with a Navigator system to calibrate the basic geometry, green convergence, edge matching and edge blending of the display system; it can also be used to calibrate projector focus.

2. Linear Crosshatch Description: This is a conventional crosshatch test pattern comprising of 8 equally spaced horizontal and vertical rectangles defined by white lines on a black background mapped onto a flat plane.

Uses: This pattern is used to calibrate color convergence and to set the electrical and optical focus adjustments.

3. Grayscale Description: This pattern comprises ten equally spaced bars varying in intensity from black to peak white. This pattern should be spherically mapped.

Uses: The pattern is used to assess video linearity to achieve correct color balance, grayscale tracking, and edge blending.

4. Uniform Field Description: This pattern is a full raster at a uniform video drive level.

Uses: The pattern is used to check and calibrate brightness uniformity and beam current limits.

5. Black Field Description: This pattern is a full raster at uniform zero drive level.

Uses: This pattern is used to calibrate the black level and CRT cut-off controls.

6. Nine White Squares Description: This pattern consists of an array of nine white squares at 70% drive level on a black background. The squares should be positioned at the channel centre and at eight points around the boundary. The squares should be typically 10º square.

Uses: This pattern is used to compare the center luminance with the eight positions around the channel boundary.

7. White Square Test Pattern Description: This pattern consists of a white rectangle at peak drive level, with a square in the middle, which has an intensity of one level below absolute white.

Uses: This pattern is used to set the peak white level.

8. Edge blend Geometry Description: This is a spherically mapped…