Attachment 4_Technical Compliance Crosswalk_RC2PL2529_Amend 0001.xlsx
XLSX spreadsheet 28 KB Posted
- Attached to
- Global Navigation Satellite Systems (GNSS) Federal contract opportunity
- Solicitation number
- 70Z04425RC2PL2529
About this file
The file is a Technical Compliance Crosswalk for a Global Navigation Satellite Systems (GNSS) solicitation issued by the US Coast Guard, detailing comprehensive technical requirements for GNSS receivers and antennas. The solicitation requires new commercial GNSS equipment with specific technical specifications, including thresholds and objectives across multiple performance categories such as size, weight, power, environmental durability, electromagnetic compatibility, positioning accuracy, security features, and data interface capabilities.
Key details include a total procurement of 402 GNSS receivers and 804 GNSS antennas over a 5-year period, with delivery timelines ranging from 45-90 calendar days after award. The technical requirements mandate compliance with international standards (IEC, NMEA), support for multiple satellite constellations (GPS, Galileo, GLONASS, BeiDou), and advanced features like interference suppression, satellite compass heading, and configurable network interfaces. The solicitation requires a minimum one-year commercial warranty, ongoing software/firmware updates, and specific reliability standards with a Mean Time Between Failure (MTBF) of at least 16,000 hours.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SF-30_0002_RFP-70Z04425RC2PL2529.pdf | ||
| Combined Synopsis_Solicitation_RC2PL2529_Amend 0002.pdf | ||
| Combined Synopsis_Solicitation_RC2PL2529_Amend 0001.pdf | ||
| Attachment 1 - GNSS Technical Specification _RC2PL2529_Amend 0001.pdf | ||
| CTR Questions_TORFP_70Z04425RC2PL2529_Amend 0001.pdf | ||
| CDRL A001_Manuals_RC2PL2529.pdf | ||
| Attachment 4_Technical Compliance Crosswalk_RC2PL2529.xlsx | XLSX spreadsheet | |
| Attachment 3 - MarkingPackagingDeliveryAcceptance_Instructions_RC2PL2529.pdf | ||
| Attachment 2_Price Schedule_RC2PL2529.xlsx | XLSX spreadsheet | |
| Combined Synopsis_Solicitation_RC2PL2529.pdf | ||
| Attachment 1 - GNSS Technical Specification _RC2PL2529.pdf |
Show all 11
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
Attachment 4
| Solicitation 70Z04425RC2PL2529_Amendment 0001 |
| Attachment 4 - Technical Compliance Crosswalk_Amend 0001 |
| Please complete the blocks highlighted in yellow in this column. | Please provide the requested documentation as part of your proposal submission. | |
| Contractor's Name: | ||
| SAM Unique Entity Identifier (UEI): |
| Trade Agreements: Are the end products U.S.-made or designated country end products? What country? |
| Manufacturer Name, Model/Part Number, etc. of the Product: |
| Requirements for the Global Navigation Satellite System (GNSS) : | |
| The specifications below identified as “Thresholds” are the minimum/required requirements. The specifications below identified as “Objectives” are preferred system capabilities, but not threshold/minimum requirements. | Specify in the below blocks if your proposed solution meets or does not meet each requirement/specification in the left hand column. Please also provide additional information regarding your proposed solution in regarding to each requirement/specification in the blocks below as applicable. Please provide technical datasheets, if they are available, to supplement this form. |
For Proposed Delivery Schedule, see the instructions in the left hand column below.
| GNSS-2.1 General | |||
| GNSS-2.1a. THRESHOLD: The GNSS must comply with IEC 60945. | Threshold: | ||
| GNSS-2.1b. THRESHOLD: The GNSS must comply with IEC 61108-1. | |||
| Threshold: | Provide compliance/certification documentation. | ||
| GNSS-2.2 Size, Weight, and Power (SWAP) | |||
| GNSS-2.2a: Size | |||
| (1) THRESHOLD: The GNSS must be a maximum of 300 cubic inches. | Threshold: | ||
| GNSS-2.2b: Operating Voltage |
(1) THRESHOLD: The GNSS must meet an Operating Voltage of 12-28 VDC.
(2) OBJECTIVE: The GNSS must meet an Operating Voltage of 10-30 VDC.
(3) OBJECTIVE: The GNSS must be dual input voltage source capable VDC OR 120V AC.
(4) OBJECTIVE: The GNSS must have an internal battery backup source.
Threshold:
Objective: Objective:
Objective:
| GNSS-2.3 Environment |
| GNSS-2.3a: Shock |
(1) THRESHOLD: The GNSS must be able to withstand a shock of 75g (non-operating).
(2) THRESHOLD: The GNSS must be able to withstand a shock of 40g (operating). Threshold:
Threshold:
GNSS-2.3b: Drop
(1) THRESHOLD: The GNSS must survive a one (1) Meter drop on a hard surface.
(2) OBJECTIVE: The GNSS must survive a drop greater than one (1) Meter on hard surface.
Threshold:
Objective:
| GNSS-2.3c: Temperature (Operating and Storage) | |
| (1) THRESHOLD: The GNSS must operate between -40 degrees Fahrenheit to +140 degrees Fahrenheit. | Threshold: |
| Provide test results/supporting documentation. | |
| GNSS-2.3d: Waterproof rating |
(1) THRESHOLD: All GNSS components must have a minimum IP rating of 67.
(2) OBJECTIVE: All GNSS components must have an IP rating of 68 or greater.
Threshold: Objective:
| GNSS-2.4 Electromagnetic Interference (EMI) and Electromagnetic Compatibility (EMC) |
| GNSS-2.4a. |
(1) THRESHOLD: The GNSS must comply to IEC 60945 standards.
(2) OBJECTIVE: The GNSS must comply to RTCM 13700.0 standards.
Threshold:
Objective:
| GNSS-2.5 Determination of Position | |
| GNSS-2.5a: Accuracy | |
| (1) THRESHOLD: The GNSS must have a horizontal position variation less than 2m via WAAS. | Threshold: |
| GNSS-2.6 Security |
| GNSS-2.6 Wi-Fi and/or Bluetooth capabilities are not required however, if equipped with Wi-Fi and/or Bluetooth, the system must meet security requirements (a and b) below: |
a. If system is equipped with Wi-Fi:
(1) THRESHOLD: Wi-Fi must be configurable (enabled/disabled).
(2) OBJECTIVE: Wi-Fi capabilities must support user configurable password protection.
b. If system is equipped with Bluetooth capability:
(1) THRESHOLD: Bluetooth must be configurable (enabled/disabled).
(2) OBJECTIVE: Bluetooth capabilities must allow user configurable password protected.
Threshold:
Objective:
| GNSS-2.7 Interference Suppression (Anti-Jam) |
| GNSS-2.7a Jamming |
(1) OBJECTIVE: The system must have the ability to detect jamming incident(s).
(2) OBJECTIVE: The must notify user when a jamming incident is detected.
(3) OBJECTIVE: The system must be Anti-Jam capable. Objective:
Objective:
Objective:
GNSS-2.7b Spoofing
(1) OBJECTIVE: The system must have the ability to detect spoofing incident(s).
(2) OBJECTIVE: The system must notify the user when a spoofing incident is detected.
(3) OBJECTIVE: The system must be Anti-Spoof capable.
Objective:
Objective:
Objective:
| GNSS-2.8 Operation | |
| GNSS-2.8a | |
| THRESHOLD: The system must have automatic selection of satellite-transmitted signals for position determination. | Threshold: |
| GNSS-2.8b | |
| THRESHOLD: The GNSS receiver must acquire signal for first fix within two (2) minutes from cold start. | Threshold: |
| GNSS-2.8c | |
| THRESHOLD: The GNSS receiver must reacquire signal for first fix within thirty (30) seconds from hot start. | Threshold: |
| GNSS-2.8d | |
| THRESHOLD: The GNSS receiver must generate and output to a display and digital interface a new position no less than once per second. | Threshold: |
| GNSS 2.8d | |
| Receiver must provide real-time position data including latitude, longitude, and altitude on the On-Screen Display (OSD) in WGS-84 format, with updates no less than once per second. | Threshold: |
| GNSS 2.8e | |
| Receiver shall output the same position data via a digital interface as defined in Requirement 2.11 of this document. | Threshold: |
| GNSS-2.8f | |
| OBJECTIVE: The GNSS receiver must provide alerts when jamming or spoofing is detected. | Objective: |
| GNSS-2.9 Antenna Specifications | |
| GNSS-2.9a | |
| OBJECTIVE: The GNSS Antenna must be mountable on a standard one-inch fourteen (14) NPT antenna mount. | Objective: |
| GNSS-2.9b | |
| OBJECTIVE: The GNSS Antenna must be Controlled Reception Pattern Antenna (CRPA) capable. | Objective: |
| GNSS-2.10 Features |
| GNSS-2.10a: The system must provide Satellite Compass Heading (A satellite compass, also known as Global Navigation Satellite System (GNSS) compass, determines heading using satellite signals, typically from dual or multiple antennas. Unlike traditional magnetic compasses, satellite compasses are not affected by magnetic interference and can maintain accurate heading even when stationary or during GNSS outages): |
(1) THRESHOLD: 0.75° RMS or greater accuracy
(2) OBJECTIVE: 0.25° RMS or greater accuracy Threshold:
GNSS-2.10b: Selectable Constellations
(1) THRESHOLD: GPS (L1 & L2)
(2) THRESHOLD: Galileo
(3) THRESHOLD: GLONASS
(4) THRESHOLD: BeiDou
(5) THRESHOLD: QZSS
(6) OBJECTIVE: GPS (L5)
(7) OBJECTIVE: NavIC Threshold:
Threshold:
Threshold:
Threshold:
Threshold:
Threshold:
Objective:
Objective:
GNSS-2.10c: Selectable Satellite Based Augmentation System (SBAS)
(1) THRESHOLD: WAAS
(2) THRESHOLD: EGNOS (Europe)
(3) THRESHOLD: GAGAN (India)
(4) THRESHOLD: MSAS (Japan)
(5) THRESHOLD: QZSS (Japan)
(6) OBJECTIVE: ASAL (Algeria)
(7) OBJECTIVE: ASECNA (Africa/Indian Ocean)
(8) OBJECTIVE: BeiDou SBAS (China)
(9) OBJECTIVE: KAAS (Korea)
(10) OBJECTIVE: SDCM (Russia)
(11) OBJECTIVE: SPAN (Australia / New Zealand) Threshold:
Threshold:
Threshold:
Threshold:
Threshold:
Objective:
Objective:
Objective:
Objective:
Objective:
Objective::
| GNSS-2.11 Data (I/O) |
| GNSS-2.11a: NMEA data standards |
(1) THRESHOLD: NMEA 0183 (4.10 or greater)
(2) OBJECTIVE: NMEA 0183 (4.30 or greater)
(3) OBJECTIVE: NMEA 2000 (3.00 or greater)
(4) OBJECTIVE: NMEA OneNet (1.00 or greater) Threshold:
Objective:
Objective:
Objective:
GNSS-2.11b: Selectable (ON/OFF) output sentences (Threshold)
(1) GGA
(2) GLL
(3) HDT
(4) VTG
(5) GST
(6) GRS
(7) GSA
(8) DTM
| (9) ZDA | Threshold: | Provide a text file output for all Threshold/Objective NMEA sentences. |
| GNSS-2.11c: Selectable (ON/OFF) output sentences (Objective) |
(1) GNS
(2) RTE
(3) WPL
(4) THS
(5) RMC
(6) GBS
(7) GDC
(8) GFA
(9) GIR
(10) GRP
(11) GGC
(12) GMP
| (13) ROT | Objective: |
| GNSS-2.11d: Selectable output frequency 1 - 10 Hz (Threshold) |
(1) GGA
(2) GLL
(3) HDT
(4) VTG
(5) GST
(6) GRS
(7) GSA
(8) DTM
| (9) ZDA | Threshold: |
| GNSS-2.11e: Selectable output frequency 1 - 10 Hz (Objective) |
(1) GNS
(2) RTE
(3) WPL
(4) THS
(5) RMC
(6) GBS
(7) GDC
(8) GFA
(9) GIR
(10) GRP
(11) GGC
(12) GMP
| (13) ROT | Objective: |
| GNSS-2.11f: Selectable baud rates (Threshold) |
(1) THRESHOLD: 4800
(2) THRESHOLD: 9600
(3) THRESHOLD: 19200
(4) THRESHOLD: 38400
(5) OBJECTIVE: 57600
(6) OBJECTIVE: 115200
(7) OBJECTIVE: 230400 Threshold:
Threshold:
Threshold:
Threshold:
Threshold:
Objective:
Objective:
Objective:
GNSS-2.11g:
THRESHOLD: Provide two RS-232 serial output ports.
Threshold:
| GNSS-2.11h: | |
| OBJECTIVE: Provide three or more RS-232 serial output ports. | Objective: |
| GNSS-2.11i: |
OBJECTIVE: Provide two serial output ports that are configurable for RS-422 or RS-232.
Objective:
GNSS-2.11j:
OBJECTIVE: Provide three or more serial output ports that are configurable for RS-422 or RS-232 (Objective) Objective:
GNSS-2.11k:
OBJECTIVE: Provide configurable CAN output interface that supports CAN 2.0 or greater.
Objective:
GNSS-2.11l:
THRESHOLD: Provide network data interface via physical connection suitable for TCP/IP interface.
Threshold:
| GNSS-2.11m: OBJECTIVE: Provide network data interface suitable for multicast communication over UDP/IP interface. | Objective: |
| GNSS-2.11n: OBJECTIVE: Receiver must have a minimum of 20 NMEA outputs across all output interfaces. | Objective: |
| GNSS-2.11o: |
THRESHOLD: Receiver must have the capability to be assigned an Internet Protocol Version 4 (IPv4) address and communicate over IPv4 schema.
Threshold:
GNSS-2.11p:
OBJECTIVE: Receiver must have the capability to be assigned an Internet Protocol Version 6 (IPv6) address and communicate over IPv6 schema.
Objective:
GNSS-2.11q:
OBJECTIVE: Receiver TCP/IP interface must be configurable, allowing the operator to choose between an IPv4 or IPv6 schema for TCP/IP communication.
Objective:
| GNSS-2.12 Receiver Configuration Management |
| GNSS-2.12a: |
THRESHOLD: The GNSS must be configurable via a configuration file.
Threshold:
| GNSS-2.12b: | |
| THRESHOLD: The GNSS configuration file must be exportable/importable. | Threshold: |
| GNSS-2.12c |
OBJECTIVE: All GNSS configuration options must be available via the receiver interface directly.
Objective:
| GNSS-2.12d | |
| OBJECTIVE: GNSS must be configurable via web browser interface. | Objective: |
| GNSS-2.12e | |
| OBJECTIVE: The GNSS Web user interface must support user configurable password protection for configuration access. | Objective: |
| GNSS-2.13 Logistics |
| GNSS-2.13a: Supportability |
(1) THRESHOLD: For any software products, the contractor must provide all manufacturer software updates, and patches to correct defects, for the life of the product [i.e., until the “End of Life” (EoL) or “End of Support” (EoS)]. Software updates and patches must be made available to the government for all products procured under this Contract and replaced when End of Support (EoS) is reached.
(2) THRESHOLD: For any hardware products (utilizing firmware), the contractor must provide all manufacturer firmware updates to correct defects, for the life of the product [i.e., until the “End of Life” (EoL) or “End of Support” (EoS)]. Firmware updates must be made available to the government for all products procured under this Contract and replaced when End of Support (EoS) is reached.
(3) THRESHOLD: Contractor must provide notification timelines for software and/or firmware updates, product end of life, and repairability support.
| GNSS-2.13b: Configuration Management | |
| (1) THRESHOLD: Exact model number and capability of components must be available for order for the entirety of the contract period of performance. | Threshold: |
GNSS-2.13c: Reliability - Mean Time Between Failure (MTBF)
(1) THRESHOLD: Each item must have a reliability of 16,000 hours MTBF.
(2) OBJECTIVE: Each item must have a reliability of 18,000 hours MTBF.
Threshold:
Objective:
| GNSS-2.14 Delivery | |
| GNSS-2.14a: | |
| THRESHOLD: The product must be delivered to the Government within 90 calendar days of delivery order award. | Threshold: |
| GNSS-2.14b: | |
| OBJECTIVE: The product must be delivered to the Government within 45 calendar days of delivery order award. | Objective: |
| Warranty | |
| The contractor must provide, at a minimum, a one-year standard commercial warranty, which commences on date of installation on a USCG asset. Product warranties must include a product return policy. Any Original Equipment Manufacturer (OEM) warranties associated with products delivered under this contract/order must be available directly to the USCG. | Threshold: |
| Quantity |
The total quantity of GNSSs Receivers is 402 over a 5 year period. The total quantity of GNSS antennas over a 5 year period is 804 over a 5 year period.
Proposed Delivery Schedule Your proposed delivery schedule must be in the following format:
## calendar days after award of the Base Quantity ## calendar days after Option Quantities are exercised
File details come from the government source that posted it. Updated .