Sources Sought 526 IS CGF.SAF Software (Current).pdf

SUBJECT: Sources Sought for Computer Generated Forces/Semi-Autonomous Forces (CGF/SAF) Software

1. Purpose:

This is NOT a solicitation. This memorandum serves as a Sources Sought notice to identify potential suppliers capable of providing a CGF/SAF software for the 526th Intelligence Squadron, Nellis Air Force Base. The purpose is to further advance the Squadron's testing, training, and tactics development mission to support the Combat Intelligence Training Audience worldwide.

2. Background:

The 526th IS currently employs Battlespace Simulation Inc's Modern Air Combat Environment (MACE)/Augmented Reality Mission Observation and Rehearsal (ARMOR) 3D software to aid its mission and are seeking information on suppliers whom can supply similar or near-identical products. Estimated qty: 9x softwares with associated maintenance.

3. Requirement Description:

The CGF/SAF software must:

• Software must be a physics-based, many-on-many simulation and threat environment with a large order of battle, including ground, air, sea, and space-based entities, weapons, and electronic warfare.

• Software must be suited for both stand-alone mission rehearsal and distributed mission simulation.

• Software must quickly and easily extend the distributed simulation framework to include software-generated semi-autonomous forces (SAF).

• Software must allow the end user to add or edit their own threat data, even down to the pulse level for generating emitter data.

• Software must have a Plug-in API for writing code to extend the software to meet customer needs (in C#, for Visual Studio).

• Software must support the Distributed Interactive Simulation (DIS) architecture, including simulation management, entity state, fire, detonate, and emissions Protocol Data Units (PDUs).

• Software must simulate an entire Integrated Air Defense System (IADS) including Early Warning, Acquisition, and Target Tracking RADAR systems (down to the pulse level), as well as both constructive and man-in-the-loop/virtual blue and red forces.

• Software must have a logical, consistent, easy-to-understand user interface and fast learning curve.

• Software must work seamlessly with existing DoD Joint mission planning systems. Users must be able to import routes and orders of battle into the software or create them from scratch within the software. Software missions should not be scripted; actions can be pre-planned or dynamically injected into the scenario in real-time.

• Software must use energy-based aerodynamic models for aircraft flight; physics-based flyable flight models for fast moving fighter-type and slower moving attack-type aircraft.

Software must construct a flight model that is “sufficiently realistic” for simulating aircraft response to person-in-the-loop flight control inputs.

• Software must use physics-based aerodynamic models and limited guidance models for missile fly-outs, derived from weapon thrust, drag, and weight.

• Software must use a physics-based aerodynamic model for ballistic fly-outs, determined from drag and weight, including the weapon’s drag reference area, coefficient of drag (subsonic and supersonic), speed, and atmospheric conditions at the flight altitude.

• Software must contain sufficient high-fidelity radar parametrics to process the Radar Range Equation and calculate radar burn-through ranges using the same equations as the Improved Many on Many (IMOM) Planner.

• Software must support a variety of elevation data sources, including Digital Terrain Elevation Data (DTED), Shuttle Radar Topography Mission (SRTM) data, MetaVR’s Virtual Reality Scene Generator (VRSG) elevation data (MDS), and GeoTiff heightmaps (used with Common Database – CDB elevation).

• Software must generate K-Series and J-Series messages that are broadcast over the network via Distributed Interactive Simulation (DIS) Signal PDUs. The software entities will automatically send accompanying DIS Transmitter PDUs for the appropriate Tactical Data Link network.

• The software must show the amount of damage a weapon causes is based on the target’s radius, target’s armor, weapon’s blast radius, weapon’s blast effect, and the distance from the weapon to the target at detonation. Depending on the weapon and target, it’s possible to not cause any damage or a single weapon can cause damage to may targets at once.

That amount of damage then reduces the target’s health, if applicable.

• Software must provide the ability to add or modify a variety of radio equipment and their associated parametric data to platforms; the presence of certain radios can impart specific behaviors on those platforms and will influence typical behaviors within a mission.

• Software must provide the ability to model networks and their corresponding signal propagation between network sites. The network must allow an operator to determine how platforms are connected to one another and to understand the connection signal strength (measured as a percentage) between the networked platforms.

• Software must provide access to and interact with Electronic Warfare (EW) devices advanced entity properties such as radios, radar systems, receivers, and infrared signatures.

• Software must support user-defined entity aggregation, using Mil-Std 2525D Joint Military Symbology. Software must also allow the operator to manage multiple aggregates and aggregates of aggregates.

• Software must operate within Windows-based Operating Systems and have a current Certificate To Field (CTF) for the Secret Internet Protocol Router Network (SIPRNet) and Joint Worldwide Intelligence Communications System (JWICS).

4. Anticipated Procurement Approach:

The procurement approach for the CGF/SAF Software is anticipated to be a competitive set-aside for small businesses, focusing on technical capability and price reasonableness.

5. Response Requested:

Interested suppliers are requested to provide the following information:

• Company Name

• Point of Contact Information (Name, Title, Phone, Email)

• Business Size (Small Business, Large Business, Other)

• Description of the proposed Mobile Expended Ordnance Deformer, including technical specifications and capabilities related to demilitarization and mobility.

• Pricing information, including initial cost, installation, and any recurring costs

• Relevant past performance or experience with similar demilitarization projects

6. Submission Instructions:

Responses to this notice should be submitted via email to AnnMarie Shields, candes.shields@us.af.mil and Margaret Young, margaret.young.6@us.af.mil no later than 4:00 PM EST, 7 June 2024

7. Point of Contact:

For ques�ons or further informa�on regarding this no�ce, please contact AnnMarie Shields at candes.shields@us.af.mil and Margaret Young at margaret.young.6@us.af.mil. Kindly request including both individuals on the "To" line.

8. Conclusion:

This Sources Sought no�ce is for market research purposes only and does not cons�tute a solicita�on. The informa�on obtained will be used to inform the acquisi�on strategy.

AnnMarie Shields Senior Contract Specialist, 633rd Contrac�ng Squadron 757-764-2926 mailto:candes.shields@us.af.mil mailto:margaret.young.6@us.af.mil mailto:candes.shields@us.af.mil mailto:margaret.young.6@us.af.mil