PWS_Training_Simulator_Purchase_v.2_6-2-15.docx

PERFORMANCE WORK STATEMENT (PWS)

1. Background: MAWTS-1 provides standardized advanced tactical training and certification of unit instructor qualifications that support Marine Aviation Training and Readiness (T&R). MAWTS-1 accomplishes this by conducting the twice-annual Weapons and Tactics Instructors (WTI) Course and supplementary courses of instruction that include MAWTS-1 Commanders Course, Marine Division Tactics Course (MDTC), Aviation Ground Support (AGS) Course, and Air Command and Control Officers Course. MAWTS-1 also provides assistance in the development and employment of aviation weapons and tactics.

2. Objectives:

MAWTS-1 modeling and simulation supports (4) functional areas:

2.1. Training aviation unit instructors per MCO 3500.109 accomplished by conducting the twice-annual Weapons and Tactics Instructors (WTI) Course.

2.2. Integration of joint LVC agencies such as Air Force Airborne Warning and Control System (AWACS) Mission Training Center (MTC) simulators, 32nd Army Air Missile Defense Command (AAMDC) simulators and Navy Fleet Synthetic Trainers (FST) to train aviation battle staffs during WTI and fleet support.

2.3. ACE LVC training and integration in joint and MAGTF exercises such as LSE and ITX.

2.4. Test and evaluation of future equipment and Tactics, Techniques, and Procedures per MAWTS-1 charter.

3. Scope: The contractor shall provide all equipment, tools, and materials, support (installation, hardware, and software) other items, and non-personal services necessary to provide MAWTS-1 with a modeling and simulation capability as defined in this PWS for all Weapons and Tactics Instructor courses and supplementary courses annually in accordance with the tasks defined below. The simulation system will be used to support a total of 30 USMC/joint/coalition WTI students per the bi-annual WTI class who will learn to manage the simulation scenarios. This is the training audience. Upon completion, those students should know the simulation equipment requirements and have the required managerial skills to produce their own simulation scenario at home station. In addition, it is anticipated that there will be 5 USMC simulation system operators per class that will be response cells to the training audience. The response cells will enact commands given by the WTI students. When not in direct support of the WTI course, the simulation equipment will be used in support of supplementary courses and fleet support training offered by MAWTS-1. The equipment will be operated by MAWTS-1 staff and on-site modeling and simulation contractor (not provided by this PWS).

3.1. Period of Performance.

3.1.1. The contractor shall provide these services beginning on 15 July 2015 on-site at the MAWTS-1 training site aboard Marine Corps Air Station, Yuma, Arizona.

4. Applicable Documents. The following regulations apply and guide the requirements of the training:

MCO 3500.109 Marine Corps Aviation Weapons and Tactics Training Program; NAVMC 3500.14C Aviation Training and Readiness Program Manual; MCO 1553.3A Unit Training Management; NAVMC 3500.119 Tactical Air Operations Center Training and Readiness Manual; NAVMC 3500.95 Direct Air Support Center Training and Readiness Manual

3.

4.

5. Task 1. The contractor shall provide simulation system equipment and software, as outlined below, for the period outlined in paragraph 3.1 at MAWTS-1 training site aboard Marine Corps Air Station, Yuma, Arizona.

5.1. The contractor will provide all equipment and software required to operate a simulation system. The simulation system must be self-contained, meaning that it comes with all software and hardware required to operate and accomplish the below tasks. Simulation system must run Windows 7 and be IA compliant with Marine Corps IA protocols. MAWTS-1 will have hardware administration rights to the Simulation system in order to apply IA protocols. Simulation system must have the ability to integrate Marine Corps C2 systems with other Marine Corps and joint ground and aviation simulation systems over a federated and Distributed Interactive Simulation (DIS) compliant network.

5.2. The simulation system must replicate air, land, and sea C2 tactical radars. It must produce realistic entities or targets that an operator would see if utilizing real radar vice this simulation system. Not only must this simulation system generate realistic entities that move on pre-scripted paths, but a simulation system operator must be able to dynamically control (or maneuver) each individual entity in real-time.

5.3. The simulation system shall be interoperable, and interface directly with organic Marine Corps tactical air command and control equipment. Specifically, the simulation system shall simulate a radar input which is capable of injecting an air operations scenario directly into the Mobile Tactical Air Operations Module (MTAOM) and Common Aviation Command and Control System (CAC2S) via the same tactical radar ports used by the actual tactical radars (Multi-Radar Tracker (MRT) and/or Multi-Source Correlator Tracker (MSCT) respectively).

5.4. The simulation system, located in the white cell and utilizing a multicast User Datagram Protocol (UDP) signal, shall have the capability to convert multicast UDP into a unicast UDP signal for transmission and receipt over a tactical Secure Internet Protocol Router (SIPR) network and convert from unicast UDP back to multicast UDP at both the MTAOM and CAC2S field locations. The simulation systems shall have the capability for the UDP conversions to occur in reverse order from both field locations to the white cell.

5.5. The simulation system shall have an intuitive graphical user interface which enables the simulation system operators to easily create realistic and robust combat scenarios and reduce the total number of man-hours used to create the scenario.

5.6. The simulation system shall support the ability for operators, acting as pilots, to take dynamic control of aircraft entities within the scenario in real-time. The simulation system must (1) provide workstations that allow operators to manage the simulation scenario and (2) take control of pre-scripted entities on pre-scripted routing through airspace and dynamic maneuver them on alternative routing at alternative altitudes. The simulation system will include (5) simulation operator workstations to accomplish this task.

5.7. The simulation system shall be capable of emulating any friendly or threat aircraft, surface to weapons systems, or naval entities. The simulation system must have an extensive library of weapons employment specifications of friendly and threat aircraft, surface, and naval weapons systems that it can emulate.

5.8. The simulation system shall have the ability to import a Theater Battle Management Core System (TBMCS) generated Air Tasking Order (ATO) in United States Message Text Format (USMTF) and generate an air scenario based on that ATO. The ATO contains specific aircraft types, number of aircraft, aircraft routing, departures times and from which airport, weapons load outs, aerial refueling times and fuel amounts, and orbits. The Airspace Control Order (ACO) contains all of the airspace control measures, (flight paths, restricted operating zones, etc.) that the aircraft are scheduled to fly as identified on the ATO.

5.9. The simulation system shall, while running a scenario, must allow an operator to create an entity or entities “on-the-fly,” and inject those into the CAC2S without stopping the scenario. The operator must also be able to control each entity’s organic capability (e.g. simulated radar becomes degraded, so it tracks fewer or no targets or a fighter can actually launch its weapons against an enemy fighter or ground target). The operator must be able to control each entity's weapon, sensor, Identify Friend or Foe (IFF), and data link system to include: weapon and sensor systems that can be put in auto-fire mode; having the entity detect and engage opposing forces on its own; sending aircraft auto-Return To Base (RTB); and executing automated tactics and on routes in and out of target areas. Each entity must also have the ability to be put in an “auto-mode” so that it (1) engages other entities according to realistic weapons employment ranges and (2) will complete a mission and RTB on its own.

5.10. The simulation system shall include realistic damage assessment based on weapon type, warhead size/type, and target size/armor. Based on the employed weapon, the simulation system would produce a battle damage assessment that would be proportional to the size of the weapon used against the target type.

5.11. The simulation system shall have the ability to save and play back a scenario for debriefing and lessons learned in front of the training audience. Playback must have the ability to be run up to, but not limited to 10x speed (meaning 10 seconds playback for every 1 real-time second). Playback must also have the ability to display playback time to the training audience.

5.12. The simulation system shall have the ability to create, move and modify ground unit symbols using Mil-Standard 2525 and Marine Air Ground Task Force (MAGTF) OPS TERM and Graphics. This ability should be such that it indicates the locations and identities of friendly and enemy ground units.

5.13. The simulation system, having a local server, must have the ability to connect with two individual USMC C2 systems; both of which will be geographically displaced from the server, but within IP connectivity. Each of these units will be expected to generate a tactical air picture. The simulation system must be able to produce and transmit to the USMC C2 systems a simulated radar feed that is unique to each USMC C2 system per their geographic location.

5.14. The simulation system must be Distributed Interactive Simulation (DIS) compliant and have the ability to integrate both voice communication and entity management with joint C2 simulation platforms through the Distributed Mission Operations Network (DMON).

5.15. The simulation system must be able to support four (4) entity manipulation operator consoles and one (1) scenario editing console simultaneously. When connected to the DMON, the simulation system must be able to support Voice-Over-Internet-Protocol (VOIP) connections for up to three (3) different joint C2 simulation systems.

5.16. The simulation system must have the ability to transmit entities via Mil-Standard 3016, Joint Range Extension Application Protocol C (Secure Internet Protocol Router Network).

5.17. The contractor shall deliver and set up all equipment and software to the MAWTS-1, Bldg. #406, Marine Corps Air Station, Yuma, AZ 85369 no later than 30 days after receipt of award.

6. Task 2. The contractor shall provide personnel necessary for installation, integration, and testing of the Simulation System. Successful installation is defined as simulation system operational and able to perform all functions as outlined in paragraph 5 (Task 1).

7. Simulation System Warranty. The contractor shall provide software warranty on all software for a period of twelve months after delivery or industry standard. All hardware provided by the contractor shall carry the manufacturers’ warranty. The warranty shall provide MAWTS-1 with a helpdesk in which to report problems and to seek assistance for repair.

8. Additional Simulation System Maintenance Support. The contractor shall offer optional support services for a minimum of one year.