MS ORT spec Oct 2020.docx
DOCX document 66 KB Posted
- Attached to
- 7025- Software Capability Increase for MS-ORT trainer Federal contract opportunity
- Solicitation number
- N6134021R0017
About this file
This document outlines requirements for a trainer system to support Coast Guard aircraft missions. The system must include two image generators and two radar modules to provide high-fidelity sensor replication for visual, infrared, electro-optic, and night vision training. Integration support is required to interface the new equipment with an existing flight station simulator. The work will primarily relate to Navy and Marine Corps aircraft simulation programs and be performed at classified facilities. The solicitation seeks sole source negotiation for increased software capability on existing trainer hardware to support HC-144B aircraft and maintain compatibility with pilot station simulators. The opportunity aims to leverage existing Minotaur software and consolidate training in a compact footprint utilizing 4U of rack space.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| MS-ORT - HC-144B Add-On Final 072320.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TRAINER DESIGN REQUIREMENTS
NOTE: The PTT (Part-Task-Trainer) and TORT (Tactical Operational Readiness Trainer) will both be Unclassified training systems. All software and hardware components must meet USCG Information Security requirements in accordance with COMDTINST 5500.13 series.
Basic Configuration
Must consist of a minimum of two operator workstations and one instructor operating station.
PTT and reconfigurable TORT must be capable of creating three different platform configurations. To the maximum extent possible, ownship models and configuration files shall allow for configuration of HC-130J, HC-144B, and future HC-27J Minotaur platforms.
All assembled components must fit through a space 78” high x 33” wide.
Main Electrical power as required; prefer to utilize standard ACV 120/60Hz if possible. Backup power/Surge suppression devices should be easily accessible for battery inspection / replacement.
Acoustic considerations – equipment noise should be controlled to allow instructor/student interaction via normal verbal communication levels (acoustic cabinets and/or intercommunication systems)
Cooling considerations – should utilize ambient air within the climate controlled space with temperature setting of no less than 68 degrees. If alternative is required USCG POC should be consulted.
Image Generation System must accommodate all standard USCG Minotaur video output signals (EOIR and RADAR) simultaneously.
Controllable Tracks/Target Models – (reference JIATF-S vessel recognition guides for examples):
EO/IR Visual Models – Should focus on smaller surface vessels with various capabilities; from Shrimp Boats and Trawlers down to single person rafts. Aircraft models should include at a minimum MH-65, MH-60 and Cessna 182.
RADAR Model – Should include surface vessels of various size and capabilities; from Super tankers to marker buoys. Aircraft models should include at a minimum MH-65, MH-60 and Cessna 182. If possible, a radar data base that includes most of the real-world objects within the Gulf of Mexico and the Florida Straits.
Background Tracks (clutter) – should include autonomous surface vessels and airborne tracks.
Area coverage – At a minimum operating area should include shoreline out to 400 nautical miles around Alaska, Hawaii, entire CONUS and the entire Caribbean area. Inland coverage should extend 30 Nautical miles (plus 30 Nautical miles around USCG Air Station Sacramento).
PTT Capabilities Trainer design shall facilitate the following training objectives:
Simulation of all Radar Search Modes
| Up to 200NM / Altitudes of 500’ to 10,000’ |
| Sector setup and control capability |
Simulation of Inverse Synthetic Radar (ISAR) and Range Profile Modes
| HC-130J: 5NM (min) up to 80NM / Altitudes of 500’ to 10,000’ |
| HC-144B: 2NM (min) up to 66NM / Altitudes of 500’ to 10,000’ |
EO/IR control and viewing of all available EO/IR Channels &/or Camera’s within the FLIR-380HD.
Includes UHCU (Universal Hand-Controller Unit) and Minotaur control interfaces.
Excludes access to the UHCU MAIN MENU for 380HD configuration purposes (default parameters to be provided upon request).
EO/IR Sensors:
1. HD EO: 5x step zoom
2. HD IR: 5x step-zoom
3. HD LL (Low Light): Continuous zoom
4. SWIR (Short-Wave IR): 5x step-zoom
Ability to generate VMTI track indication – when operator maintains EOIR pointing angles at a known radar or AIS track for 20 seconds or more.
Simulation of DF-500 Selectable standard SAR signal type Attachable to any model Include Line of Bearing (LOB)
Injection/Display of following Track sources (Quantity):
1. Radar (200)
2. APY-11 Radar (HC-130J) or APS-143 Radar (HC-144B) (200)
3. AIS (300)
4. ADS-B Tracks (50)
TORT Capabilities All PTT capabilities plus:
Radar Strip Map, Spot SAR, Weather, SART/BCN and Air-to-Air Modes
EO/IR (FLIR 380HD) MAIN MENU access and functionality
Full DF-500 Mode Control Simulation:
Full representation and control/response to MSO workstation Power Control Panels
Full representation of Minotaur system status monitor to MSO workstation displays.
Full representation and control/response to MSO workstation Circuit Breaker Panels
Full representation and control/response to MSO workstation Lighting Controls
Full representation and control of MSO workstation KVM switches
Full representation of MSO workstation Laptop Display(s)
Full Communication Simulation:
| HC-130J, HC-144B, and HC-27J ICS Panel controls and selection |
| RT-5000 Radio(s) (VHF/UHF AES & DES) |
| ARC-210 Radio(s) (MILSATCOM & LOS) |
| HF Radios |
| KY-100 |
| DVP-200 |
| INMARSAT Control |
| STE |
| KG-175D |
Instructor Operating Station (IOS)
IOS should possess sufficient display area to allow the instructor to display/control various scenario aspects simultaneously. Additionally, display space should be available to adequately mirror selected operator workstation monitors to facilitate training.
Aircraft Control
Attitude Control for pitch and roll (zero to no less than 80 degrees) Speed (zero to no less than 300 Knots) Altitude (zero to no less than 25000 feet)
Navigation Control Autonomous via waypoint entry – allow instructor to designate waypoints by either data entry or select with cursor.
Autonomous Patterns – allow programming of orbits, search patterns or direct steering to select point (either designate waypoint or other point of interest) Manual – allow utilization of simplified instructor input from joystick type device and/or attribute entry fields Instructor should be able to deviate from planned flight path anywhere in route; maneuver freely and then continue to the next waypoint without having to restart from the beginning.
Simulation Environmental Controls Date and Time of Day should correspond to normal solar illumination schedule Lunar illumination should be set as a percentage (0 to 100% - default to 50% ) Visibility (zero to no less than 60 nautical miles) Wind Controls Direction (zero to 359) Speed (zero to no less than 80 Knots) should automatically determine Sea State based on Beaufort Scale Reference following link for scale and visual representation http://www.seakayak.ws/kayak/kayak.nsf/7fa3095d976a5b7c8525711d006d6667/e4e2c690916a3a24852570da0057e036!OpenDocument Wave action should occult EOIR and RADAR detection accordingly
Track/Target controls Key factor - US Coast Guard has no requirements for radar ELINT signature identification; our focus is on detection and classification of surface targets (radar ISAR and Range Profile functions)
Track entries should allow for dynamic input throughout scenario - designate with cursor, drag and drop from list, or any viable option that allows maximum training flexibility.
Directional Controls - Heading, Speed and Altitude (All default to zero)
Track Navigation should be selectable via designated TRACK waypoints or Heading/speed
Track Attributes should be adjustable – names, AIS ID numbers, and registration numbers (Flag/Country would be useful, but not required)
Scenario Generation/Initial Conditions
IOS should allow creation, modification and deletion of training scenarios and establish initial condition files. Initial Conditions should quickly set location/configuration of ownship, controllable models, background tracks, environmental conditions and Date/Time settings.
Workstations (MSO1 and MSO2)
Workstation framework should mirror basic layout of mission system pod design identified for the HC-27 and HC-144 aircraft. (Seating/chairs will not be part of trainer delivery)
Any cable connection required between the pods must allow the pods to be position laterally no less than 60 inches apart, facing the same direction and without stressing the connection points (measured between external pod surfaces).
Cables required between the IOS and the workstation must allow six-foot separation between the back of the IOS work surface and the front of the workstations with sufficient length to route the cables under a standard raised floor.
Minotaur Software - trainer must utilize the same software as the aircraft system; without modification of the code.
Main Displays – must have same viewable space as the aircraft (20” diagonal). Touch screen capability is not required unless eliminating the option causes integration errors with the mission system software.
Workstation Controls – should be modeled utilizing computer generated representation of power, communications and configuration panels as placeholders; these can be touch screen enabled as required for Minotaur configuration needs or for future growth. Placement of panels should approximate the actual physical location on the real asset within the confines of the framework described above.
Mission System Interface Controls – physically should match designs installed in HC-130J MSS Keyboard P/N: 537-0174 (backlighting optional, but utilize standard computer connection (PS2 or USB) Trackball P/N: 606-0020 (backlighting optional, but utilize standard computer connection (PS2 or USB) EOIR Universal Hand Controller (modeled – no backlighting required, control buttons should look and feel same as original manufacturer)
Mission System Specifications
The following items are for reference only. They provide a basic idea of the integration of Minotaur software, sensors, interface controls and aircraft workstations.
3.2.2 Mission System Functionality
The MS SHALL have a track capacity of at least 80,000 non-active maritime surface tracks. (MSS3.2.2.4)
Concern with achieving this performance. Previous Minotaur threshold was 10.000. Requires discussion.
Sunderland’s response: 80,000 non-active tracks, stored, accumulated over a period of time (72 hours via Minotaur spec). 10,000 active (live) contacts.
The MS SHALL initiate manual contacts independent of sensor data with a user selected time out. (MSS3.2.2.7)
The MS SHALL display radar track data. (MSS3.2.2.8)
The MS SHALL be able to add data, such as speed, course and name to a sensor or manual track. (MSS3.2.2.9)
The MS SHALL display Inverse Synthetic Aperture Radar (ISAR) stills. (MSS3.2.2.10)
The MS SHALL display ISAR video. (MSS3.2.2.11)
The MS SHALL display AIS tracks. (MSS3.2.2.12)
The MS SHALL display EO/IR imagery and video. (MSS3.2.2.13)
The MS SHALL be able to strip map video directly overlaid on the tactical map. (MSS3.2.2.14)
The Strip map SHALL be able to be turned on/off with a single button/click. (MSS3.2.2.15)
The MS SHALL display correlated radar-to-AIS tracks. (MSS3.2.2.17)
The MS SHALL display correlated radar-to- DNC points. (MSS3.2.2.18)
The MS SHALL display correlated AIS-to-DNC points. (MSS3.2.2.19)
The MS SHALL permit user-selected map overlays. (MSS3.2.2.20)
The MS SHALL display correlated tracks in a different color than non-correlated tracks. (MSS3.2.2.21)
The MS SHALL display user selected multiple track histories including AIS and radar information for correlated tracks and associated imagery. (MSS3.2.2.22)
The MS SHALL display tracks and generate visual alerts based on user-defined speed filters. (MSS3.2.2.23)
The MS SHOULD generate audible alerts based on user-defined speed filters. (MSS3.2.2.24)
The MS SHALL display tracks and generate visual alerts based on user-defined length filters. (MSS3.2.2.25)
The MS SHOULD generate audible alerts based on user-defined length filters. (MSS3.2.2.26) The MS SHALL display tracks and generate visual alerts based on user-defined heading filters. (MSS3.2.2.27)
The MS SHOULD generate audible alerts based on user-defined heading filters. (MSS3.2.2.28) The MS SHALL display tracks and generate visual alerts based on user-defined age filters. (MSS3.2.2.29)
The MS SHOULD generate audible alerts based on user-defined age filters. (MSS3.2.2.30)
The MS SHALL display tracks and generate visual alerts based on user-defined associated imagery filters. (MSS3.2.2.31)
The MS SHOULD generate audible alerts based on user-defined associated imagery filters. (MSS3.2.2.32)
The MS SHALL display tracks and generate visual alerts based on user-defined identity filters (e.g., Maritime Mobile Service Identity [MMSI]). (MSS3.2.2.33)
The MS SHOULD generate audible alerts based on user-defined identity filters (e.g., MMSI). (MSS3.2.2.34)
The MS SHALL display tracks and generate visual alerts based on user-defined annotation filters. (MSS3.2.2.35)
The MS SHOULD generate audible alerts based on user-defined annotation filters. (MSS3.2.2.36)
The MS SHALL display tracks and generate visual alerts based on user-defined source filters. (MSS3.2.2.37)
The MS SHOULD generate audible alerts based on user-defined source filters. (MSS3.2.2.38)
The MS SHALL display tracks and generate visual alerts based on user-defined geographic area filters. (MSS3.2.2.39)
The MS SHOULD generate audible alerts based on user-defined geographic area filters. (MSS3.2.2.40)
The MS SHALL differentiate tracks based on user-defined filters. (MSS3.2.2.41)
The MS SHALL provide automated and operator controlled alerts for communications events. (MSS3.2.2.42)
Each MSO station SHALL allow operators to modify their monitor views to include, but not be limited to selection of sensor to display, resize, rescale, and center on both the aircraft and the target. (MSS3.2.2.43)
The MS SHALL measure the length of objects in captured imagery. (MSS3.2.2.44)
The MS SHALL associate imagery with designated tracks. (MSS3.2.2.45)
The MS SHALL provide a visual display to the MSO when an AIS Search and Rescue Transponder (SART) distress message is received. (MSS3.2.2.46)
The MS SHALL visually differentiate AIS SART tracks from non-AIS SART tracks. (MSS3.2.2.47)
The MS SHOULD provide the MSO the ability to select which audio channels are recorded. (MSS3.2.2.48) As per Andy Strachan email on 5.31.16, current MSS requirements involving audio with Minotaur have to be changed to objectives (SHOULD statements) as the Minotaur processor does not have the ability to process sound.
The MS SHALL be capable of two-way Voice over Internet Protocol (VoIP) communication. (MSS3.2.2.49)
The MS SHALL receive data from the aircraft navigational system. (MSS3.2.2.50)
The MS SHALL provide the MSO the ability to create reports and analyze imagery and video while in-flight. (MSS3.2.2.51)
The MS SHALL switch easily to “native mode” radar hits from the maritime radar sensor. (MSS3.2.2.52)
The MS SHALL be able to inject an EO/IR video track on the tactical display. (MSS3.2.2.56)
The MS SHALL be able to select and regain an original target with a single action. (MSS3.2.2.57)
The MS SHALL operate using off-board data received from Minotaur-equipped ground-based servers and supporting air-, marine-, or shore-based assets and command center(s) (within in the data transfer rates and capabilities available). (MSS3.2.2.58)
Classified e-mail and chat capabilities (Secret Internet Protocol Router Network [SIPRNet]) SHALL be provided with a carry-on classified laptop and crypto device. (MSS3.2.2.62)
3.2.4 Mission Operators Station
The MSO Station SHALL include two functional operator consoles. The consoles SHALL be designed for installation in either location without modification. (MSS3.2.4.10)
The MSO station consoles SHALL use a standard configuration that includes a keyboard, trackball, (or sensor control) and high-definition (HD) capable monitor screen(s); or equivalent, achieved through capacitive touch screens. (MSS3.2.4.11)
Each MSO station console SHALL be equipped with, at minimum, dual-screen displays. (MSS3.2.4.12)
Each MSO station console SHALL contain sensor joysticks or hand controller with the commonly used functions useable with one hand. (MSS3.2.4.13)
3.3 SENSOR SYSTEMS
The MPA SHALL have organic sensor capability to automatically detect, classify, and identify: surface targets, TOI, and small targets during day and night operations from patrol altitudes, as listed in Table 2: Sensor System Performance.
The MPA SHALL have organic sensor capability to automatically detect, classify, and identify a single Person In the Water (PIW) during day and night operations from patrol altitudes referenced for the “Life Raft (with 1 person)” contact, as listed in Table 2: Sensor System Performance.
Individual targets of interest SHALL be automatically sorted from non-targets of interest prior to compromising the covert position (5,000 ft. Above Water Level [AWL] and 5 NM of MPA).
The composite sensor system SHALL meet the performance requirements in Table 2: Sensor System Performance.
The composite sensor system SHALL detect a 20' fiberglass or wooden boat as defined in Table 2: Sensor System Performance.
The composite sensor system SHALL automatically detect target movement and other mission triggers such as pollution, icebergs, marine sanctuary violations, and closed area incursions.
Sensor System Performance Sensor System Performance1
| Detect2 Target |
| Classify2 Target |
| Identify2 Target |
| Contact Characteristics |
| Day & Night Slant Range & Alt AWL (NM/feet) |
| Target Type |
Day & Night Slant Range & Alt AWL (NM/feet) Target Activity Day & Night Slant Range & Alt AWL (NM/feet) Day Slant Range & Alt AWL (NM/feet) Night Slant Range & Alt AWL (NM/feet)
| Vessels greater than 150 feet in length3 |
| 200/27,000 |
| 100/27,000 |
| 15/2,000 |
| 8/2,000 |
| 4/2,000 |
| Vessels greater than 50 but less than 150 feet in length3 |
| 75/10,000 |
| 50/10,000 |
| 8/2,000 |
| 4/2,000 |
| 4/2,000 |
| Vessels greater than 15 but less than 50 feet in length3 |
| 50/5,000 (KPP)7 |
| 25/5,000 |
| 4/2,000 |
| 2/2,000 |
| N/A |
| Life Raft (with 1 person)4 |
| 25/2,000 |
| N/A5 |
| 0.25/1,0006 |
| 0.25/1,000 |
| N/A |
1 All requirements are threshold except as noted.
2 Beaufort scale sea state 3, 90% probability of detection (on one single pass of MPA) required.
3 Vessel category representatives:
• 15-50' category – a 20' wooden or fiberglass boat.
• 50-150' category – a 100' steel hull, western rig fishing trawler.
• >150' category – a 200' steel hull, aft superstructure coastal freighter.
4 Six- to eight-person life raft with 1 person in raft.
5 Objective requirement of 5/2,000 (NM/feet) for this category.
6 Additional objective requirement of 2/2,000 (NM/feet) for this category.
7 20' wooden or fiberglass boat (KPP).
Notes: AWL = Above Water Level, KPP = Key Performance Parameter, N/A = Not applicable.
3.3.1 Multi-Mode Radar
The HC-27J SHALL be equipped with a Multi-Mode Radar (MMR).
The MS SHALL have control of all functions of the MMR.
The MS SHALL have control of all modes of the MMR.
The MMR SHALL be controllable by the MSO via alternate means when the MS is not functional.
The MMR SHALL pass track data to the MS.
The MMR SHALL have an Inverse ISAR mode.
Target resolution in the ISAR mode SHALL be no greater than 1.5 feet.
Target resolution in the ISAR mode SHOULD be no greater than one (1) foot.
The MMR SHALL have a Synthetic Aperture Radar (SAR) mode.
The MMR SHALL pass STRIP SAR/ISAR imagery to the MS.
The MMR SHALL be capable of automatic track initiation of all detected targets in SAR modes.
The MMR SHALL be capable of automatic track initiation of all detected targets in all search modes.
The MMR SHALL provide the means in the search modes for the operator to designate targets for tracking.
The MMR SHALL provide an air search mode.
The MMR SHALL detect a SART signal at no less than 10 NM slant range.
The MMR SHALL display relative bearing of detected SART signals.
The MMR SHALL be operated with full functionality from any MSO position.
Radar data (with the exception of weather radar) SHOULD be displayed in color in accordance with Radio Technical Commission for Aeronautics (RTCA) DO-173, where color significantly enhances presentation.
The MMR SHALL have an automatic track-while-scan capability of all detectable targets.
The MMR SHALL be configured to display all radar data at the pilots’ stations and at the MSO positions as selected by the individual crewmember.
The radar SHALL provide 360 degree (°) azimuth and 60° (+20°, -40°) elevation coverage, as limited only by aircraft installation or obstruction from aircraft structure.
3.3.2 Electro-Optical/Infrared
The MPA SHALL be equipped at all times with a minimum of 1 EO/IR system operationally interfaced with the radar.
The EO/IR system SHALL provide infrared spectrum images (Short Wavelength IR [SWIR] and Medium Wavelength IR [MWIR]).
The EO/IR system SHALL provide visible spectrum images.
The EO/IR exterior mounting location SHALL provide a 360 degree (°) field of view (FOV) that does not result in any additional airframe operating limitations on the MPA.
The EO/IR line of sight to targets SHALL be maintained with minimal obstructions from the aircraft in a 20 degree (°) angle of bank.
The EO/IR/Radar interface SHALL allow the EO/IR to be slewed to a radar-designated contact.
The EO/IR SHALL be capable of auto tracking on a fixed coordinate. This feature SHALL be selectable (on or off) by the operator.
The EO/IR SHALL be capable of auto tracking on a target (once acquired). This feature SHALL be selectable (on or off) by the operator.
The EO/IR system SHALL have multiple FOV to support the requirements noted in Table 2: Sensor System Performance.
The MS SHALL display the field of regard (azimuth and FOV of the EO/IR sensor based on elevation).
The EO/IR sensor SHOULD possess a day and a night digital video imaging capability with a National Imagery Interpretability Rating Scale (NIIRS) level 7 capabilities at 8 NM slant range (visual meteorological conditions). (KPP) Through AA analysis cannot meet NRIS 7.
The EO/IR sensor SHOULD possess a day and a night digital video imaging capability with a NIIRS level 8 capabilities at 8 NM slant range (visual meteorological conditions).
The EO/IR sensor SHALL discern 4 inch letters from the Latin alphabet or Arabic or Roman numerals prior to compromising the covert position (5,000 ft. AWL and 5 NM) of MPA.
The positional accuracy of the EO/IR targets displayed SHALL be within 328 ft. at 5 NM slant range with proportional accuracy to the maximum range of the system.
The EO/IR imagery output SHALL be compatible with DHS IT systems capable of receiving imagery.
The EO/IR imagery SHALL be annotated with date, time, and Global Positioning System (GPS) position of the MPA and TOI as overlays.
The operator SHALL have the ability to select/deselect imagery overlays.
The MS SHALL be configured to display EO/IR sensor video to the pilot and co-pilot, and at the MSO positions as selected by the individual crewmember.
In narrowest FOV, when the EO/IR is slewed to a radar contact, the TOI SHALL be visible within EO/IR display.
The EO/IR sensor SHALL embed metadata on captured images as required by current DHS policy.
The EO/IR imagery SHALL be annotated with MPA and TOI as metadata in accordance with current DHS policy.
The EO/IR SHALL provide still imagery to the MS by both the visible and infrared sensors with a minimum native resolution of 1280 x 1024 pixels.
The EO/IR SHOULD provide still imagery to the MS by both the visible and infrared sensors with a minimum native resolution of 1600 x 1200 pixels.
The EO/IR sensor SHALL be capable of high-definition video (minimum 1080P at 30fps).
The MPA SHALL be equipped with an IR laser illuminator, laser range finder, and laser pointer that can be remotely controlled by the MSOs.
The laser range finder SHALL be capable of measuring ranges to 8 NM with measurement accuracy better than ±5m for an extended target that is perpendicular to the LOS.
The laser range finder SHOULD be capable of measuring ranges to 10 NM with measurement accuracy better than ±5m for an extended target that is perpendicular to the LOS.
The laser pointer SHALL operate at an infrared wavelength that is invisible to the unaided human eye and is visible to Gen III & IV night-vision goggles.
The laser pointer SHALL have safety mechanisms to prevent eye damage.
The laser pointer SHALL have interlocks that prevent lasing while on the ground.
The laser pointer SHALL have interlocks that prevent own-aircraft lasing.
The laser pointer SHALL not be enabled when the laser range finder indicates the range to target would cause an energy density at the target greater than 0.002 watts per square centimeter (W/cm2).
Simultaneous images from each waveband video camera SHALL be aligned so the operator can compare object features in each waveband.
Alignment between the optical centerlines of each video waveband, the laser range finder, and the laser illuminator SHALL be less than 0.001° (0.016 milliradian [mrad]).
Alignment between different waveband images at the periphery of the FOV SHALL be less than 0.04 degrees (°) (0.64 mrad) when the FOV size is 10° or less.
Alignment between different waveband images at the periphery of the FOV SHALL be less than 0.005° (0.08 mrad) when the FOV size is 10° or less.
All components of the electro-optical sensor SHALL be mechanically aligned and stabilized to ensure range measurements and the projected laser designator illumination aligns with both video cameras.
The EO/IR sensor SHALL be physically stabilized so that residual optical centerline jitter to less than 0.002° (0.032 mrad).
Video images SHALL be free of visible jitter (may be through a combination of mechanical and electronic stabilization).
The EO/IR video image SHALL be stabilized (possibly a combination of physical and electronic stabilization) to less than 0.0006° (0.01 mrad).
3.3.3 Automatic Identification System (AIS)
The MPA SHALL transmit, receive, monitor, and display encrypted (e-AIS) and clear data transmitted from vessels equipped with and broadcasting AIS information.
The AIS transmit capability SHALL be selectable (on/off).
The AIS SHALL be interfaced with the MS.
The AIS data SHALL be displayed on the MS display.
AIS SART (distress message) tracks SHALL be displayed on the MS display in a color different than normal AIS tracks (non-distress message tracks).
The AIS transceiver SHALL be Sensitive but Unclassified Tactical Exchange Display System (STEDS) compliant.
3.3.4 Automatic Detection Surveillance – Broadcast (ADS-B)
The system SHALL provide an Automatic Dependent Surveillance-Broadcast (ADS-B) OUT system that will meet all Federal Aviation Administration (FAA) certification and compliance requirements.
The system SHOULD provide an ADS-B IN system that will meet all FAA certification and compliance requirements.
The MS SHALL have an interface for Automatic Dependent Surveillance-Broadcast (ADSB) IN received data.
The ADS-B SHALL operate in Class A airspace with equipment that meets the antenna and power output requirements of Class A1, A1S, A2, A3, B1S, or B1 equipment as defined in FAA Technical Service Order (TSO)–C166b: Extended Squitter ADS–B, Flight Information Services-Broadcast (FIS-B), and Traffic Information Services-Broadcast (TIS–B) Equipment.
The ADS-B system SHALL operate at 1090 Megahertz (MHz) and 978 MHz.
The system SHALL provide the MSO the ability to turn off ADS-B OUT and use ADS-B IN without ADS-B OUT.
The system SHOULD provide the MSO the ability to switch the Traffic Collision Avoidance System (TCAS) into a passive mode.
The MS SHALL display ADS-B IN data when selected (layer on/off) by a Mission System Operator (MSO).
3.3.5 Identification Friend or Foe
The MS SHOULD be equipped with an Identification Friend or Foe (IFF) interrogator of air and surface targets to include Modes 2, 3, 4, and 5.
The MS SHOULD be equipped to operate with modes A, C, 3/C, and S.
The IFF system SHOULD provide, at the minimum, range and azimuth coverage compatible with the radar type platform (Airborne Early Warning [AEW] or Laser Radar Technology [LRT]) that carries it.
The transceiver SHALL be capable of receiving and transmitting on a digital secure trunked network and a secure P-25 conventional channel, either networked or simplex, in the VHF-FM, UHF-FM (LO and HI) and 700/800 MHz bands.
3.3.6 Direction Finding
The MS SHALL receive, monitor, home in on, and display bearing information of Ultra High Frequency (UHF) signals in the frequency ranges listed in Table 4: Communication Capabilities Requirements, throughout a full 360-degree azimuth.
The MS SHALL receive, monitor, home in on, and display bearing information of Very High Frequency – Amplitude Modulation (VHF-AM) signals in the frequency ranges listed in Table 4: Communication Capabilities Requirements, throughout a full 360-degree azimuth.
The MS SHALL receive, monitor, home in on, and display bearing information of VHF frequency Modulation (FM) signals in the frequency ranges listed in Table 4: Communication Capabilities Requirements, throughout a full 360-degree azimuth.
The MS SHALL receive, monitor, home in on, and display bearing information of 406 MHz Emergency Position Indicating Radio Beacon (EPIRB) signals throughout a full 360-degree azimuth.
The MS SHALL select, scan, direction find, and home on international distress frequencies 121.5, 243.0, and 156.8, and on 406 MHz for EPIRB signals.
The MS SHALL display International 406 MHz Cospas/Search and Rescue Satellite Aided Tracking (SARSAT) EPIRB digital data including registration number, beacon identification, country code, and latitude/longitude (if available).
The MS SHALL monitor 406 MHz (EPIRB) independently of and simultaneously with selected transmit/receive frequencies.
The MS SHALL provide a means of presenting DF data to the pilots.
The DF signal source audible tone (if a tone exists) SHOULD be active during homing.
The MS SHALL display multiple LOBs from the same signal source over time.
The DF system SHALL determine LOB relative to the MPA position and heading with an accuracy of ≤ 10 degrees.
DF bearing information SHALL be displayed on the pilot and copilot Horizontal Situation Indicator (HSI) when selected.
All DF LOBs SHALL be displayed at the MSO position.
The MS SHALL enable the MSO to select (on/off) individual LOBs.
3.4 External Communications
3.4.1 General External Communications Requirements
The HC-27J MS SHALL be equipped with a multi-band communications package that enables the crew to operate voice and data on multiple bands (see Table 5: Communication Capabilities Requirements) and other common public safety, and military frequencies while providing appropriate encryption.
Each MS SHALL select, tune, transmit, and receive on the radio frequencies and modes listed below and in Table 5: Communication Capabilities Requirements.
The MS SHALL provide a text chat feature.
The text chat feature SHALL allow the operator to make non-verbal communication with other aircraft and ground operators, to include group and private (whisper) functions.
The system SHALL simultaneously monitor guard channel 121.50 MHz while operating on another VHF-AM frequency.
Each MS station SHALL electronically control and tune the radios by integrated means vice individual hardware radio control panels (e.g., Control Display Unit [CDU]-like device).
Each MS station SHALL provide visual indication of transmit/receive selection and frequency.
The communications system SHALL be configured such that a user may transmit/receive on any available radio in all phases of flight and ground operations without degradation or interference with any other aircraft or mission system avionics.
All Type 3 encryption equipment SHALL be NIST compliant.
1. Communications Capabilities Requirements
| Type |
| Frequency Range (MHz) |
| Non-Secure Voice |
| Secure Voice |
| Non-Secure Data |
| Secure Data |
| Protected Voice |
| Protected Data |
| Comments |
| HF |
| 2.000-29.999 |
| • |
| • |
| • |
| • |
| • |
| • |
| DHS compatible Advanced Encryption Standard (AES). USB/LSB/AM modes, Automatic Link Establishment (ALE), Selective Calling (SELCAL). |
| VHF-FM |
| 30.000-87.975 |
| • |
| • |
Single-Channel Ground and Air Radio System (SINCGARS)
| VHF-AM |
| 118.000-155.975 |
| • |
SHALL comply with 8.33 kHz channel spacing and SHOULD VHF digital Link (VDL) capability
| VHF-FM |
| 136.000-173.975 |
| • |
| • |
| • |
| DHS compatible AES with Digital Selective Calling (DSC). SHALL be APCO P25 compliant. SHALL be OTAR capable |
| UHF-AM |
| 225.000-380.000 |
| • |
| • |
DHS and/or DoD compatible encryption. SHALL have anti-jam (e.g. HAVEQUICK II) capability
| UHF-FM |
| 380.000-870.000 |
| • |
DHS compatible AES SHALL be APCO 25 complaint. SHALL be OTAR capable.
MILSATCOM
Demand Assigned Multiple Access (DAMA), Non-DAMA voice, Integrated Waveform (IW). SHALL have imagery handling and transfer.
| COMSATCOM |
| • |
| • |
| • |
| • |
| • |
| • |
DHS Data Network
| • |
| • |
SIPRNet
3.4.2 MILSATCOM & VHF/UHF
The MS SHALL provide non-secure and secure UHF-AM voice communications in the
225.000 MHz–380.000 MHz frequency band.
The UHF-AM system SHALL have anti-jam (for example: HAVEQUICK II) capability.
The UHF-AM system SHALL be capable of simultaneously monitoring guard channel 243.00 MHz while operating on another UHF frequency.
The MS SHALL provide both non-secure and secure VHF-FM voice communications capability in the frequency range of 30.0000 MHz–87.975 MHz (e.g., Single Channel Ground and Air Radio System [SINCGARS]).
The VHF-FM system SHALL simultaneously monitor guard channel 156.800 MHz while operating on another VHF-FM frequency.
The VHF-FM system SHALL have SINCGARS capability.
The system SHALL simultaneously monitor guard channel 121.50 MHz while operating on another VHF-AM frequency.
The MS SHALL access the MILSATCOM system to provide secure MILSATCOM voice and data communications using Demand Assigned Multiple Access (DAMA), non-DAMA, Integrated Waveform (IW), and Mobile User Objective Service (MUOS) protocols.
The MS SHALL transmit and receive still imagery and data through the MILSATCOM system with DoD Type 1 encryption.
3.4.3 HF Communications
The HF system SHALL provide 2.000 MHz–29.999 MHz frequency band coverage with dual Single Side Band (SSB), Upper Side Band (USB), Lower Side Band (LSB), AM, Automated Link Establishment (ALE) (most recent generation), and Selective Calling (SELCAL) voice capability.
The HF system SHALL transmit voice and data on either HF transceiver, selectable by the MSO.
The HF system SHALL support data transmission via Internet Protocol (IP) and Standardized Agreement (STANAG) 4538 and STANAG 5066 Protocol.
The HF system SHALL provide non-secure, secure, and protected voice and data communications with DHS and DoD HF systems.
The HF system SHOULD provide U.S. Scope Command E-mail send and receive connectivity up to the SECRET level.
The HF system SHALL transmit still imagery.
The HF system SHALL transmit data.
The HF system SHALL receive still imagery.
The HF system SHALL receive data.
The MS SHALL enable receiving two simultaneous HF radio transmissions.
3.4.4 Association of Public Safety Communications Officials (APCO) Project 25 Radios
The APCO transceiver system SHALL be capable of receiving and transmitting on a digital secure trunked network and a secure P-25 conventional channel, either networked or simplex, in the VHF-FM, UHF-FM (LO and HI) and 700/800 MHz bands.
The VHF-FM, UHF-FM (LO and HI) and 700/800 MHz bands SHALL have the ability to conduct OTAR (Over the Air Rekey) operations from a suitable Key Management Facility and SHALL have the encryption ability to load at least 64 Common Key Reference (CKR) or 16 Physical Identifier Reference (PID) keys, with at least 16 being selectable for transmit function.
The VHF-FM, UHF-FM (LO and HI) and 700/800 MHz bands SHALL be capable of operating with National Institute of Standards and Technology (NIST)-approved, Federal Information Processing Standard (FIPS ) 140-2 compliant, Type 3-certified Data Encryption Standard (DES-XL), DES Output Feedback (OFB), and Advanced Encryption Standard (AES) encryption on all Association of Public-Safety Communications Officials Project-25 (APCO-25) compliant channels, either conventional or trunked.
The APCO transceiver system SHALL be capable of operation on any analog FM channel.
The APCO transceiver system SHALL be capable of Network Identifier/Network Access Code (NID/NAC) on any digital FM channel.
The APCO transceiver system SHALL permit simultaneous transmission on separate channels from any/all bands that the radio is capable of through use of a single microphone/headset input (SIMULCAST mode).
The APCO transceiver system SHALL permit half-duplex, cross-band relay operation using any two bands with no restrictions on the operating channels (RELAY mode). This capability SHALL be bidirectional, meaning that either band is capable of transmitting upon reception on the other selected band.
When in RELAY mode, an onboard operator SHALL be provided a “break-in” capability to transmit on both transceivers being utilized in the RELAY operation, on their assigned channels, just as with SIMULCAST mode.
The APCO transceiver system SHALL monitor DSC Channel 70 independent of and simultaneously with selected transmit/receive frequencies.
The APCO transceiver system SHOULD permit a scanning mode across all channels within a given band, or a defined subset of channels.
The APCO transceiver system SHOULD be RTCA/DO-160G compliant.
The APCO transceiver system SHALL be APCO-25 compliant for both Phase-I and Phase-II.
The MS SHALL access the APCO transceiver system to provide non-secure and protected UHF-FM communications in the 380.0000 MHz–870.0000 MHz frequency band.
UHF-FM external communications SHALL be APCO-25 compliant.
UHF-FM external communications SHALL be capable of Over The Air Re-Keying (OTAR) to receive AES and Data Encryption Standard keys.
UHF-FM external communications SHALL be compatible with Type 3 encryption AES-256 and National Institute of Standards and Technology (NIST) compliant.
The MS SHALL access the APCO transceiver system to provide non-secure and protected VHF-FM voice and data communications capability in the frequency range of 136.000 MHz–
173.975 MHz.
VHF-FM external communications SHALL be compatible with Type 3 encryption AES-256 and NIST compliant.
VHF-FM external communications SHALL be APCO-25 compliant.
VHF-FM external communications SHALL be capable of OTAR to receive AES and Data Encryption Standard keys.
3.4.5 Line of Site Datalink
The MS SHALL include a LOS data link system for streaming video transmissions with a minimum transmission range of 50 NM.
The MS SHALL be equipped with a LOS system that is compatible with and meets or exceeds the specifications of the HC4 HELI-CODER 4 High Power Transmitter.
All MSO stations SHALL control the LOS system equipment.
The LOS unit SHALL transmit both MPEG 2 and MPEG 4 video to a compatible receiver.
The LOS system SHALL operate in the L band (1-2GHz) or S band (2-4GHz).
The LOS system SHALL provide protected communications.
The LOS system SHALL transmit/receive IP.
SBU-Laptop
| Swift Broadband EMS Page Emulation |
| Office Communicator Emulation |
| MS Outlook Emulation |
SIPR-Laptop
| MACO Chat (Client) Emulation |
| MS Outlook Emulation |
File details come from the government source that posted it. Updated .