Request For Information (RFI) for future devices MH-60 MISSION REHEARSAL TRAINER
|Agency:||DEPT OF DEFENSE|
|Level of Government:||Federal|
|Posted Date:||Aug 19, 2020|
|Due Date:||Oct 8, 2020|
- Contract Opportunity Type: Special Notice (Updated)
- All Dates/Times are: (UTC-04:00) EASTERN STANDARD TIME, NEW YORK, USA
- Updated Published Date: Aug 19, 2020 01:33 pm EDT
- Original Published Date: Aug 19, 2020 01:01 pm EDT
- Updated Response Date: Oct 08, 2020 05:00 pm EDT
- Original Response Date: Oct 08, 2020 05:00 pm EDT
- Inactive Policy: 15 days after response date
- Updated Inactive Date: Oct 23, 2020
- Original Inactive Date: Oct 23, 2020
- Original Set Aside:
- Product Service Code: 6910 - TRAINING AIDS
- NAICS Code: 333318 - Other Commercial and Service Industry Machinery Manufacturing
Place of Performance:
Fallon , NVUSA
REQUEST FOR INFORMATION (RFI)
MH-60 MISSION REHEARSAL TRAINER
INTEGRATED TRAINING FACILITY, FALLON, NEVADA
1.1 The Naval Air Warfare Center Training Systems Division (NAWCTSD) is conducting market
research in support of a Mission Rehearsal Trainer (MRT) for the MH-60 aircraft, to be located at the
Integrated Training Facility (ITF) in Fallon, NV. The MH-60 Training Systems (TS) Program
encompasses a full spectrum of training systems used to develop the knowledge, skills, and abilities of
sailors to operate and maintain the MH-60R and MH-60S helicopters.
The ITF at Fallon may require a rotary wing trainer to support the Carrier Air Wing (CVW) mission sets.
The MRT will be used for tactics development in the CVW environment, and must contain highly
accurate MH-60R/S mission system capabilities, with the ability for experimentation and upgrades. This
device must be Special Access Program (SAP)-capable as it will be operating in a full-time common
security environment at the TS-SCI level. The MRT must operate under the same standards as the other
CVW platforms currently planned for inclusion in the ITF in order to ensure a seamless integration into
the ITF training missions. Additionally, the MRT must have the ability to expand to Navy Continuous
Training Environment (NCTE) in the future. The MRT will be used to ensure the Government’s approach
to ensuring aircraft concurrency, readiness, relevance to training systems, support of integrated warfare
requirements, managing baseline software configurations, and cyber compliance of operational systems.
The proposed action is to solicit those listed under the TSC IV MAC only.
2.1 The burgeoning contract actions described herein are new, and are aimed at supporting CVW
missions. Specifically, the MH-60 MRT would support:
2.1.1 Physical Characteristics
22.214.171.124 Two simulation devices capable of switching between MH-60R and MH-60S configurations
126.96.36.199 Crew stations for Aircraft Tactical Officer (ATO), Sensor Operator, Pilot (or control station
capable of positioning aircraft in simulation environment)
188.8.131.52 Crew input devices that physically match those in the aircraft (i.e. keypad, trackball, mission
display bezel keys, etc.).
184.108.40.206 Mission Display presentation that matches the size and appearance of the aircraft.
220.127.116.11 Ability to maneuver the aircraft through the simulation environment. High-fidelity flight
characteristics similar to an Operational Flight Trainer (OFT) are not sough – control functions
should be sufficient to correctly position the aircraft in the simulation environment for tactical
execution and sensor performance. For example, this might include a generic cyclic and
collective that might be used in a desktop flight simulator.
18.104.22.168 Small footprint device to accommodate limited space in the ITF. The MH-60 MRT will likely be
physically placed in a 24 ft x 11ft room. This room will plan to include up to two MRT’s and two
simulators from a different platform (similar in size to the MH-60), for a total of four simulators
in the room. A separate server room will house all computing devices for each simulator, so only
crew stations, crew input devices, and MRT control station will need to be co-located in the same
22.214.171.124 MRT computers shall be in a rack-mounted form factor for placement in the server room, as
mentioned in requirement 126.96.36.199.
188.8.131.52 OFT-like visual systems are not sought. One or multiple computer monitors are sufficient for
out-the-window visuals. Emphasis for the MRT is mission execution through the crew input
devices, as detailed in requirement 184.108.40.206.
2.1.2 Sensor Characteristics
220.127.116.11 The device must represent all onboard sensors and data links employed by the MH-60 in
Electronic Warfare and Surface Warfare missions.
18.104.22.168 Simulation of surface surveillance sensors and related information, to include radar (all modes of
APS-147 and APS-153), electronic warfare (ALQ-210), APR-39, Multi-Spectral Targeting
System (MTS), Automatic Information System (AIS) and Identification Friend or Foe (IFF).
22.214.171.124 Accurate, physics-based modeling of included sensors, except for MTS. For example, radar
performance modeling should include all available environmental effects, target radar crosssection
true to aspect, and true-to-life Inverse Synthetic Aperture Radar (ISAR) imaging. ALQ-
210 detections should display representative variability in detection ranges and parameter
measurement. It is important that the sensors be modelled as accurately as possible to properly
integrate the MH-60 MRT into ITF integrated mission scenarios. Conversely, MTS modelling
similar to current OFT devices, which relies just on image generators, is sufficient.
126.96.36.199 All internal and external communication systems and data links, to include Internal
Communication System (ICS), HAWKLINK, Link 16 and Satellite Communication (SATCOM)
should be modelled and operate with true-to-life performance. All communication systems that
are currently supported by the ITF, that are also a capability of the MH-60 platform, shall be
implemented. All other communication systems capabilities in the MH-60 platform not currently
supported by the ITF should be architected so as to allow room for expansion in the future.
188.8.131.52 Simulation devices should be integrated into the overall simulation environment and be
interoperable with all other simulation devices in the ITF using the Distributive Interactive
Simulation (DIS) standard.
184.108.40.206 The simulation device in this environment must integrate with simulation devices from other
220.127.116.11 Mission playback and other post mission analysis tools and capabilities should include accurate
sensor information to permit detailed performance assessment and feedback.
18.104.22.168 Device must operate in an open building with a common security classification system, currently
planned for the Top Secret, Sensitive Compartmented Information and Special Access Program
22.214.171.124 Device must have ability to expand into Navy Continuous Training Environment (NCTE) in the
126.96.36.199 Current with deployed System Configuration Set (SCS).
188.8.131.52 The simulation devices must have the ability to load mission planning data on the same
removable drives as the actual aircraft and developed on the same mission planning system.
184.108.40.206 SCS and other software should be upgradable and changeable in advance of fleet introduction to
enable to analysis of software performance and Tactics, Techniques, and Procedures (TTP)
220.127.116.11 Cyber compliance.
18.104.22.168 Ability to adapt to evolving Cyber standards through the device’s entire life cycle.
3.1 Interested parties are requested to respond to this RFI with a white paper.
3.2 White papers in Microsoft Word for Office 2010 compatible format are due no later than October 8th
2020 by 1700 EST. Responses shall be limited to three (3) pages and submitted via e-mail only to
email@example.com. Please be advised that all submissions become Government property and will
not be returned.
3.3 The white paper shall provide administrative information, and shall include the following as a
3.3.1 Name, mailing address, phone number, fax number, and e-mail of designated point of
3.3.2 Recommendation on how to meet all or part of requirements listed in section 2.1.
THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information
and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP
in the future. This request for information does not commit the Government to contract for any supply or
service whatsoever. Further, the Navy is not currently seeking proposals and will not accept unsolicited
proposals. Responders are advised that the U.S. Government will not pay for any information or
administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will
be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in
any future RFP, if any is issued. If a solicitation is released, it will be synopsized on the appropriate
Government-wide Point of Entry (GPE) in accordance with FAR Subpart 5.2. It is the responsibility of
the potential offerors to monitor these sites for additional information pertaining to this requirement.
Questions regarding this announcement shall be submitted in writing by e-mail to the Contract
Specialist, Shaan A. Charran, at firstname.lastname@example.org. Verbal questions will NOT be
accepted. Questions will be answered via an email response. The Government does not guarantee
that questions received after (October 8th 2020 by 1700 EST) will be answered.
- 12211 SCIENCE DRIVE
- ORLANDO , FL 32826-3224
- Shaan Charran
- Phone Number 4073808125
- Howard Rodriguez
- Phone Number 4073804409
- Aug 19, 2020 01:33 pm EDTSpecial Notice (Updated)
- Aug 19, 2020 01:18 pm EDT Special Notice (Updated)
- Aug 19, 2020 01:01 pm EDT Special Notice (Original)
TRY FOR FREE
Not a USAOPPS Member Yet?
Get unlimited access to thousands of active local, state and federal government bids and awards in All 50 States.