DRAFT PRD COMPLIANCE MATRIX 3 MAR 2021.xlsx
XLSX spreadsheet 61 KB Posted
- Attached to
- Combat Net Radio Federal contract opportunity
- Solicitation number
- W15P7T-21-R-0009
About this file
This is a Request for Information (RFI) issued by the U.S. Army seeking information on potential Combat Net Radio (CNR) solutions. The Army is conducting market research to inform the development and planning of a new CNR requirement. Interested parties are requested to respond with a white paper and completed Performance Requirements Document (PRD) Compliance Matrix by March 15, 2021. The scope of effort includes engineering, software and hardware development, testing, documentation, training, and program management to deliver an upgraded radio meeting the PRD's threshold requirements while pursuing objectives such as increased temperature tolerance and faster boot times. The Army envisions a demonstration event in October 2021 for vendors to showcase proposed solutions. Responses to the RFI should not exceed 12 pages and must address the PRD, 18 questions posed, and business size and security clearance information.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| CNR RFI 12 Mar 21 Revision 3 Highlighted_Changes.pdf | ||
| CNR RFI QA_consolidated_12Mar21 Revision 3.xlsx | XLSX spreadsheet | |
| DRAFT PRD - 3 MAR 2021.pdf | ||
| RFI Question Comment Feedback Matrix Spreadsheet.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
TAB A CNR DO1
| Column 1 | Column 2 | Column 3 | Column 4 | ||||
| Line | PRD Reference | Specification | Req | Compliant Y/N | Included in Baseline Radio Y/N | Separately Orderable Capability Y/N | Other Waveforms Certification |
| 1 | 3 | SINCGARS2 | T | ||||
| 2 | 3.1 | SINCGARS2 Receiver-Transmitter (RT) (SINCGARS2-RT). The SINCGARS2-RT shall demonstrate: |
*NSA Certification.
*JITC Waveform Conformance *JITC Interoperability Assessment *SCA Certification 2.2 or later from the Joint Tactical Networking Center (JTNC) *Spectrum Standards Compliance *Analysis which documents that personnel in full Mission Oriented Protective Posture (MOPP) IV protective gear can successfully operate and maintain the radio.
*Analysis which documents that the radio can be operated for 72 hours while contaminated.
*Analysis which documents that the radio can be decontaminated using existing solvents.
| *For any requirements not complete at time of contract award, the vendor shall submit for approval a low-risk plan to achieve proof of compliance within the Delivery Order period. | T | |||
| 3 | Technical Specifications | |||
| 4 | 3.1.1 | Characteristics | T | |
| 5 | 3.1.1.1 | Frequency Range | T | |
| 6 | 3.1.1.1.1 | Shall cover the frequency range from 30-88 MHz for narrow band channels. | T | |
| 7 | 3.1.1.1.2 | Shall operate in 25kHz bandwidths supporting both all modes of the legacy SINCGARS waveform and all modes of the upgraded SINCGARS 3.1 waveform. | T | |
| 8 | 3.1.1.1.3 | Shall operate in 50kHz bandwidths supporting waveforms requiring it. e.g. WREN-NB. | O | |
| 9 | 3.1.1.1.4 | Shall cover the frequency ranges from 225 MHz and higher for other waveforms. | O | |
| 10 | 3.1.1.2 | Receive Characteristics | T | |
| 11 | 3.1.1.2.1 | Shall meet the receiver sensitivity levels as specified in Tables 3-1 and 3-2. | T | |
| 12 | 3.1.1.2.2 | CNR Residual Bit Error Rate (BER). The receiver shall provide a residual BER of not greater than one in 106 bits in single channel (SC) mode and no greater than one in 105 bits in frequency hopping (FH) mode and enhanced operating mode (EOM) with a 16 kbps digital data signal when the radio frequency (RF) level at the receiver is at least ?89 dBm for both plain text (PT) and cypher text (CT) modes. | T | |
| 13 | 3.1.1.2.3 | CNR Receiver Selectivity. The receiver shall meet the selectivity requirements in Table 3-3. | T | |
| 14 | 3.1.1.2.4 | The CNR RF receive signal sensitivity shall not be degraded more than 3 dB when a continuous wave (CW) signal is operating at 25 W with at least 10% frequency separation between center frequencies and 35 dB of antenna isolation. NOTE: Antenna isolation is defined as the amount of attenuation between the PA transmit output port of the second channel to the PA receive input port of the first channel. | T | |
| 15 | 3.1.1.2.5 | The CNR Radio Set shall maintain a spurious response rejection of at least 60 dB for signal bandwidths up to 1.5 MHz and frequency offsets greater than +/- 5% from the carrier. | T | |
| 16 | 3.1.1.3 | Transmit Characteristics. Shall meet all range, call completion rate and message completion rate requirements during all modes of operation. | T | |
| 17 | 3.1.1.3.1 | The CNR-RT shall provide the ability to set transmit power levels. | T | |
| 18 | 3.1.1.3.2 | The CNR-RT shall provide at least 37 dBm (+/- 2 dB) of RF output power measured at the Radio RF output port for all frequencies when operating at High Power. | T | |
| 19 | 3.1.1.3.3 | The CNR-RT shall provide at least 22 dBm (+3.0, -2.0) dB of RF output power measured at the Radio RF output port for all frequencies when operating at Medium Power. | T | |
| 20 | 3.1.1.3.4 | The CNR-RT shall provide at least -3 dBm (+1.5, -1.5 dB) of RF output power measured at the Radio RF output port for all frequencies when operating at Low Power. | T | |
| 21 | 3.1.1.3.5 | The CNR Radio Set transmitted spurious output level shall be attenuated at least 50 dBc below carrier frequency when operating at maximum power level. | T | |
| 22 | 3.1.1.3.6 | Voice shall have a 90% or greater Call Completion Rate (CCR) while meeting range requirements. | T | |
| 23 | 3.1.1.3.7 | Data shall have an 85% or greater Message Completion Rate (MCR) while meeting range requirements. | T | |
| 24 | 3.1.1.3.8 | The CNR Radio Set shall provide a voice call completion rate of at least 80% in F1/F1 or F1/F2 retransmission scenario with another CNR radio when measured at the receiving radio, not the retrans radio. | T | |
| 25 | 3.1.1.3.9 | CNR dismounted service shall have a single hop (point-to-point without relaying) range in open terrain no less than 5km. | T | |
| 26 | 3.1.1.3.10 | CNR dismounted service shall have a single hop (point-to-point without relaying) range in open terrain no less than 10km. | O | |
| 27 | 3.1.1.3.11 | Mounted CNR unamplified service shall have a single hop (point-to-point without relaying) range in open terrain no less than 10km. | T | |
| 28 | 3.1.1.3.12 | Mounted CNR amplified service shall have a single hop (point-to-point without relaying) range in open terrain no less than 20km for SINCGARS. | T | |
| 29 | 3.1.1.3.13 | Mounted CNR service shall have a single hop (point-to-point without relaying) range in open terrain no less than 30km for SINCGARS. | O | |
| 30 | 3.1.1.3.14 | Mounted CNR service shall have a single hop (point-to-point without relaying) range in open terrain no less than 40km for SINCGARS. | O | |
| 31 | 3.1.1.3.15 | The CNR Radio Set shall support a transmit duty cycle of at least 50% for a minimum of at least 5 minutes. | T | |
| 32 | 3.1.1.3.16 | The CNR RT shall sustain no damage when a Radio Frequency (RF) output port is open or shorted. | T | |
| 33 | 3.1.1.4 | Physical Characteristics | T | |
| 34 | 3.1.1.4.1 | The size of the CNR Radio shall be equal to or less than the cubic measurement of a legacy RT-1523F in each dimension. Note: the SINCGARS RT shall be capable of being installed in the existing SINCGARS mounting adapter (i.e., AM-7239). | T | |
| 35 | 3.1.1.4.2 | The weight of the CNR Radio shall be equal to or less than the weight of a legacy RT-1523F: 5.5 lbs or 7.8 lbs with battery. | T | |
| 36 | 3.1.1.5 | Built-in-Tests | T | |
| 37 | 3.1.1.5.1 | The CNR Radio shall perform Power On Self-Test (POST) to determine operational status. | T | |
| 38 | 3.1.1.5.2 | For field and organizational level maintenance, the CNR Radio shall provide Built In Test (BIT) functionality to troubleshoot down to Line Replaceable Unit (LRU) level. The BIT diagnostics shall be capable of fault detection of at least 95% of all faults and must be capable of fault isolation of at least 90% of detected faults. | T | |
| 39 | 3.1.1.6 | Connectors and Interfaces | T | |
| 40 | 3.1.1.6.1 | The CNR-RT shall interface with the legacy VRC mounts, pin configuration, handsets, intercom interfaces, locking mechanism, amplifiers and the INC (Internet Controller) for mounted operation and digital fires. | T | |
| 41 | 3.1.1.6.2 | Radio shall provide Type N Female RF interfaces for all dismounted antennas. | T | |
| 42 | 3.1.1.6.3 | Shall allow the RT to be installed/uninstalled without any special tools and/or equipment. | T | |
| 43 | 3.1.1.6.4 | Shall provide an audio connector and support U-283/U key fill or adapter. | T | |
| 44 | 3.1.1.6.5 | Shall provide electrical interface for headsets, speaker/microphone, and handset in accordance with MIL-DTL-55116C. | T | |
| 45 | 3.1.1.6.6 | The CNR Radio RT shall provide legacy serial data interface in accordance with MIL-STD-188-114A as shown below for compatibility with legacy Fires support systems: | T | |
| 46 | 3.1.1.6.6.1 | The audio/data connectors shall be compatible with the following physical electrical interface requirements: | T | |
| 47 | 3.1.1.6.6.2 | The audio/data connector shall meet the following requirements: | T | |
| 48 | 3.1.1.6.6.2.1 | Voltage levels per MIL-188-114A into a single load. | T | |
| 49 | 3.1.1.6.6.2.2 | To assure RCV mode, the external device shall satisfy one of the following: | T | |
| 50 | 3.1.1.6.6.2.2.1 | No more than 100microA may flow out of pin into an (unbiased) open circuit. | T | |
| 51 | 3.1.1.6.6.2.2.2 | Present greater than +3.5 Vdc if external voltage source is applied to pin. | T | |
| 52 | 3.1.1.6.6.2.2.3 | Apply a resistance of 25K Ohms to ground for pure resistive loads. | T | |
| 53 | 3.1.1.6.6.2.3 | To assure XMT mode, the external device shall satisfy at least one of the following: | T | |
| 54 | 3.1.1.6.6.2.3.1 | External circuit shall be capable of sinking up to 500microA while ensuring 0.0V – 0.5/+0.25V at the pin. | T | |
| 55 | 3.1.1.6.6.2.3.2 | External load resistance shall be less than or equal to 400 Ohms to ground for pure resistive loads. | O | |
| 56 | 3.1.1.6.6.2.4 | To assure INACTIVE state, the external device shall satisfy one of the following: | T | |
| 57 | 3.1.1.6.6.2.4.1 | No more than 100microA may flow out of pin into an (unbiased) open circuit. | T | |
| 58 | 3.1.1.6.6.2.4.2 | Present less than -3.5Vdc if external voltage source is applied to pin. | O | |
| 59 | 3.1.1.6.6.2.4.3 | Apply a resistance of greater than or equal to 150K Ohms to ground for pure resistive loads. | O | |
| 60 | 3.1.1.6.6.2.5 | To assure ACTIVE state, the external device shall satisfy at least one of the following: | T | |
| 61 | 3.1.1.6.6.2.5.1 | External circuit shall be capable of sinking up to 200microA while ensuring 0.0V plus or minus 0.5Vat the pin. | O | |
| 62 | 3.1.1.6.6.2.5.2 | External load resistance shall be less than or equal to 25k Ohms to ground for pure resistive loads. | T | |
| 63 | 3.1.1.6.7 | Shall provide the capability to receive and transfer digital data between a computer or Mobile Hand-Held Common Operating Environment End User Device (MHH COE EUD) and the CNR-RT via Ethernet over Universal Serial Bus (USB) 2.0 or higher Type B Micro or provide applicable adapter to support data applications over Universal Serial Bus (USB) 2.0 or higher. This requirement refers to the capability, not a specific cable. | O | |
| 64 | 3.1.1.6.8 | Shall be able to connect an external Precision GPS device. An external Precision GPS is defined as an external Precision GPS that meets current Selective Availability Anti-Spoofing Module (SAASM) requirements. | T | |
| 65 | 3.1.1.6.9 | Shall provide Simple Network Management Protocol Version 3 (SNMPv3) interface to allow monitoring and control of the radio. | O | |
| 66 | 3.1.1.6.10 | Shall provide a push-button or other mechanical interface to allow the radio operator and maintainer to access operational status, control functions and parameters, and zeroize the RT from the front panel. | T | |
| 67 | 3.1.1.6.11 | Shall provide built-in display/Human Machine Interface (HMI). When mounted, the radio will either present the front panel of the RT toward the user or have an HMI integrated into the mounting hardware that controls the RT and is presented towards the user as the mounted system’s front panel. | T | |
| 68 | 3.1.1.6.11.1 | Front Panel | T | |
| 69 | 3.1.1.6.11.1.1 | Shall provide a front panel keypad interface similar in function to the existing RT-1523E/F radio. The front panel keypad shall be capable of selecting the following operational parameters: | T | |
| 70 | 3.1.1.6.11.1.2 | Preset channel (e.g. 8 SC, 6 FH) | T | |
| 71 | 3.1.1.6.11.1.3 | RF Transmit Power (LO, MED, HI, PA) | T | |
| 72 | 3.1.1.6.11.1.4 | Mode (SC, FH, FH2, RBSA) | T | |
| 73 | 3.1.1.6.11.1.5 | COMSEC (PT, CT, CT2) | T | |
| 74 | 3.1.1.6.11.1.6 | Volume Control/Whisper Mode | T | |
| 75 | 3.1.1.6.11.1.7 | Display Backlight Control | T | |
| 76 | 3.1.1.6.11.1.8 | Data Rate and Selection (SDM Data Rate, EDM Data Rates) | T | |
| 77 | 3.1.1.6.11.2 | The CNR-RT HMI shall provide operators and maintainers with the ability to check the following functions with precise visual feedback at any given time: | T | |
| 78 | 3.1.1.6.11.3 | For the CNR-RT’s functions: | T | |
| 79 | 3.1.1.6.11.3.1 | Radio power (battery charge) status | T | |
| 80 | 3.1.1.6.11.3.2 | Most recent Built-in test Status. | T | |
| 81 | 3.1.1.6.11.3.3 | Radio Based Situational Awareness (RBSA) status | O | |
| 82 | 3.1.1.6.11.3.4 | Radio software version number | T | |
| 83 | 3.1.1.6.11.3.5 | Crypto status | T | |
| 84 | 3.1.1.6.11.4 | For the Narrowband Channel: | T | |
| 85 | 3.1.1.6.11.4.1 | Frequency Hopping Mode: (SC, FH, FH2, and FH3) | T | |
| 86 | 3.1.1.6.11.4.2 | Plain text vs. Cypher text (legacy) or Crypto Modernized CT2 | T | |
| 87 | 3.1.1.6.11.4.3 | Transmitting power/signal strength | T | |
| 88 | 3.1.1.6.11.4.4 | Receive signal strength | T | |
| 89 | 3.1.1.6.11.4.5 | Alphanumeric Preset numbers with at least 5 digits | T | |
| 90 | 3.1.1.6.11.4.6 | Net ID (identification). | T | |
| 91 | 3.1.1.6.11.4.7 | Narrowband Operating Frequency | T | |
| 92 | 3.1.1.6.11.4.8 | Volume level | T | |
| 93 | 3.1.1.6.11.4.9 | Shall display the results of the last BIT for review | T | |
| 94 | 3.1.1.6.11.4.10 | Shall display the results of the last 25 BITs for review. | O | |
| 95 | 3.1.1.6.11.5 | All presets must be accessible and the radio’s controls must be able to perform all tasks without need for an ancillary device or detachable HMI. | T | |
| 96 | 3.1.1.6.11.6 | The HMI shall provide operators and maintainers with the ability to check GPS confidence of an attached PNT device with precise visual feedback at any given time. | O | |
| 97 | 3.1.1.6.11.7 | The HMI shall provide operators and maintainers with the ability to check for Interference. (When the radio receives RF energy within the channel that degrades reception, the radio shall report to the user. Applicable equally to intentional jamming and unintentional interference.) | O | |
| 98 | 3.1.1.6.11.8 | The HMI shall be readable with 10,000 foot-candle, direct sunlight. | T | |
| 99 | 3.1.1.6.11.9 | The HMI shall be readable with Generation III Night Vision Goggles. | T | |
| 100 | 3.1.1.6.11.10 | CNR-RT shall allow control of the HMI display brightness from off to maximum. | T | |
| 101 | 3.1.1.6.11.11 | The CNR-RT shall provide the user the capability to input numerical and alpha numeric characters via a keypad device. | T | |
| 102 | 3.1.1.6.11.12 | The built-in display shall be readable when the RT is mounted. | T | |
| 103 | 3.1.1.6.11.13 | A remote HMI in the form of an application for Mission Command systems shall be provided that is capable of selecting presets, controlling the radio’s volume, and displaying relevant information for mounted operation. | T | |
| 104 | 3.1.1.6.11.14 | The RT and mount shall interface with the legacy PSN-11 Handheld Remote Control. | T | |
| 105 | 3.1.1.6.11.15 | The radio shall be able to support Fires Missions by following the legacy audio specifications for the SINCGARS RT-1523 radio capable of communicating with at least the following sub-systems that use the standards of the TACLINK card: | T | |
| 106 | 3.1.1.6.11.15.1 | ULTRALINK | T | |
| 107 | 3.1.1.6.11.15.2 | Forward Observer System (FOS) | T | |
| 108 | 3.1.1.6.11.15.3 | Mortars Fire Control System (MFCS) | T | |
| 109 | 3.1.1.6.11.15.4 | Advanced Field Artillery Tactical Data System (AFATDS) | T | |
| 110 | 3.1.1.6.11.15.5 | Pocket Sized Forward Entry Device (PFED Increment II) | O | |
| 111 | 3.1.1.6.11.15.6 | Precision Fires-Dismounted (PF-D) | O | |
| 112 | 3.1.1.6.11.16 | The CNR-RT shall support the following Physical/Link modulation & rates (in bps) when interfacing using a digital synchronous interface to the TACLINK card: NRZ at rates 600, 1200, 1200N, 2400, 2400N, 4800, 4800N, 9600N, 16K. | T | |
| 113 | 3.1.1.7 | Data Interfaces. Shall permit connection to a platform or local computer via a serial interface. | T | |
| 114 | 3.1.1.7.1 | Shall provide a serial RS-232 interface for operation at rates of 1200, 2400, 4800, and 9600 bps to allow transmission of data using computers and commercial "Xmodem" software. | T | |
| 115 | 3.1.1.7.2 | Shall provide front panel control via the RS-232 interface. | T | |
| 116 | 3.1.1.7.3 | Shall provide a synchronous serial MIL-STD-188-114 interface for Packet Data. The Packet transfer rate shall be 16 kbps. | T | |
| 117 | 3.1.1.7.4 | Shall support MIL-STD-188-220C with X.21 packet data interface. | T | |
| 118 | 3.1.1.7.5 | Shall provide an analog data interface to support AD1 operation. | T | |
| 119 | 3.1.1.7.6 | Shall provide an analog data interface to support TACFIRE AD2 operation. | T | |
| 120 | 3.1.1.7.7 | Shall provide a serial connection to the Internet Controller (INC) device located in the Vehicle adapter. | T | |
| 121 | 3.1.1.7.8 | Shall support serial interfaces with the RS-422 and 423 interfaces. | T | |
| 122 | 3.1.1.7.9 | SNAP Interface. Shall provide a SNAP Interface for radio control of the FHMUXand accept BIT information from the Internet Controller and the FHMUX. | T | |
| 123 | 3.1.1.8 | Power | T | |
| 124 | 3.1.1.8.1 | Shall provide capability to use battery power when dismounted with common primary and rechargeable batteries. | T | |
| 125 | 3.1.1.8.2 | Shall allow the replacement of primary power source(s) without any special tools and/or equipment. | T | |
| 126 | 3.1.1.8.3 | The CNR-RT shall be able to operate the legacy SINCGARS and SINCGARS CT2 waveforms using all modes specified in the Compliance Matrix in a dismounted networks for voice or data operations at maximum transmit power in an operational environment, with 6:3:1 (Listen, Receive, Transmit) for no less than 8 hours while meeting 3.1.1.4.1. | T | |
| 127 | 3.1.2 | Waveforms and Services | T | |
| 128 | 3.1.2.1 | The CNR-RT’s Waveform Mode Storage, Planning, and Network Management | T | |
| 129 | 3.1.2.1.1 | Shall store all provided waveforms and required operational parameters simultaneously. | T | |
| 130 | 3.1.2.1.2 | Shall store all data encrypted while at rest in accordance with current National Security Agency (NSA) guidelines for NSA-controlled data (e.g. keying material (KEYMAT)) using a split key that is reloadable by soldiers in the field. Examples of this are JOSEKI or Watari split keys. | T | |
| 131 | 3.1.2.1.3 | Shall provide the ability for radio software, COMSEC, and mission data to be loaded via USB mass storage device drag and drop method. | T | |
| 132 | 3.1.2.1.4 | Shall store all Sensitive Unclassified Data at Rest encrypted in accordance with DoD CIO requirements in a way that precludes extraction or copying. | T | |
| 133 | 3.1.2.1.5 | Shall integrate with government owned planning and network management systems. | O | |
| 134 | 3.1.2.2 | Waveform and Mode Selection: | T | |
| 135 | 3.1.2.2.1 | Waveform modes shall be user selectable. Example: Change mode of SINCGARS. | T | |
| 136 | 3.1.2.2.2 | Shall be able to switch waveform modes, or to a different waveform and mode, in less than 2 minutes for waveforms supported on that channel. (e.g. SINCGARS voice to SINCGARS data mode) | T | |
| 137 | 3.1.2.3 | Reserved | ||
| 138 | 3.1.2.4 | Cold Start/Warm Start | T | |
| 139 | 3.1.2.4.1 | During cold start the radio shall power on, instantiate waveform(s) and assign mode(s) or configuration parameters and be fully operational within 7 minutes. Cold start is the process of configuring HW (installing antennas, and handmics, etc.), powering up, loading cryptographic KEYMAT and mission plan, entering necessary parameters, and configuring a radio’s software/applications to allow the radio to enter into its operational state and join a network. | T | |
| 140 | Cold start is normally required after such software items as waveforms, waveform operating parameters, crypto keys, and presets have been uninstalled from the radio and powered down. Cold start does not include the reloading of the radio operating environment (OE) or those radio services applications necessary to put the CNR-RT into a state in order to receive the software required to operationally configure the radio. | |||
| 141 | 3.1.2.4.2 | During warm start the radio shall power on, instantiate waveform(s) and assign mode(s) and configuration parameters to be fully operational within 30 seconds. Warm start is conducted after a radio has been successfully loaded by the operator (completion of cold start) or has previously been in an operational state and contains all the necessary radio software/ applications and assembly of components to allow the set to enter into a state of operation. | T | |
| 142 | Warm start process may consist of using a channel instantiated waveform and modifying its waveform parameter sets, (e.g., keys, presets, frequencies) to allow the operator to enter into a different network using the same waveform that is currently instantiated on the channel. Warm start may also consist of tearing down a radio’s channel and instantiating a new waveform and its parameter sets from memory unto the channel to allow the operator to enter into a new required network. | |||
| 143 | 3.1.2.5 | In the event of an EW (in-band jamming) attack, the CNR Radio shall be able to rejoin an established voice network within 60 seconds from the end of the attack. | T | |
| 144 | 3.1.2.6 | In the event of an EW (in-band jamming) attack, the CNR Radio shall be able to rejoin an established voice network within 15 seconds from the end of the attack. | O | |
| 145 | 3.1.2.7 | The CNR-RT shall allow transmit and receive operations simultaneously without interference to/from other dismounted or mounted systems with appropriate frequency management practices and utilization of appropriately filtered antennas. | T | |
| 146 | 3.1.3 | Common Management Information Base (MIB) | O | |
| 147 | 3.1.3.1 | Shall implement MIBs to provide key data for use during and post-mission. | T | |
| 148 | 3.1.3.2 | Shall implement the Program Manager for Tactical Radios (PM TR) Common MIB V2 for all channels and control of the radio. The PM TR Common MIB V2 specification is available in the PM TR Configuration Control Repository (PM TR CCR). | T | |
| 149 | 3.1.3.2.1 | Shall provide management capability (monitor/control) through application programming interfaces (APIs) or protocols which map to the ThingMagic® Mercury API. | T | |
| 150 | 3.1.3.2.2 | Shall support Over The Air Monitoring via interface to the Common MIB. | T | |
| 151 | 3.1.3.2.3 | Shall provide remote control capability for the radio through APIs or protocols which map to the Mercury API /PM TR Common MIB. | T | |
| 152 | 3.1.4 | Reserved | ||
| 153 | 3.1.5 | Global Positioning System (GPS) | T | |
| 154 | 3.1.5.1 | Internal GPS | O | |
| 155 | 3.1.5.1.1 | Shall provide an integrated GPS capability. | T | |
| 156 | 3.1.5.1.2 | Shall be able to connect external SAASM GPS or M-Code GPS to radio via cable in lieu of internal non-SAASM. | T | |
| 157 | 3.1.5.1.3 | Shall include an antenna to receive GPS signal as part of the system for dismounted use. | T | |
| 158 | 3.1.5.1.4 | The CNR-RT, when operating waveforms for transmitting Position Location Information (PLI) over the RBSA protocol or Internet Protocol (IP) data, shall use Variable Message Format (VMF) K5.01 in accordance with the MIL-STD-6017 and MIL-STD-6017A series with VMF header in accordance with MIL-STD-2045-47001C, as appropriate. | T | |
| 159 | 3.1.5.1.5 | Position location information (PLI) shall be accurate within 10 meters, with clear sky view and a minimum of 4 satellite signals acquired, where GPS signal is available. | T | |
| 160 | 3.1.5.2 | External GPS Interface Requirements | T | |
| 161 | 3.1.5.2.1 | Shall utilize Precise Position Service (PPS) GPS when both PPS and commercial GPS signals are available. | T | |
| 162 | 3.1.5.2.2 | Shall be able to receive time and position data via GPS-153 formatted message from external devices. Examples: DAGR or M-Code module. | T | |
| 163 | 3.1.5.3 | Shall be able to utilize GPS timing provided by the platform via VICTORY Data Bus integration. | T | |
| 164 | 3.1.6 | Communications Security (COMSEC). For the purposes of this section, the term “keys” includes system keys, certificates, and Firefly vectors as well as user traffic keys. | T | |
| 165 | 3.1.6.1 | Key Management | T | |
| 166 | 3.1.6.1.1 | Shall be capable of using the existing Simple Key Loader (SKL) to load COMSEC and presets for SINCGARS and legacy waveforms. | T | |
| 167 | 3.1.6.1.2 | Shall be capable of using the Next Generation SKL to load COMSEC and presets. | O | |
| 168 | 3.1.6.1.3 | Shall be compatible with the Key Management Infrastructure (KMI) and follow-on KMI systems. | O | |
| 169 | 3.1.6.1.4 | Shall support Over The Air Management of cryptographic keying material using both Saville Automatic Re-Key (SARK) Tx/Rx and the methods detailed in the SINCGARS CT2 specification, as appropriate to the waveform in use during the re-key event. | T | |
| 170 | 3.1.6.1.4.1 | Shall support transmit and receipt of Over-the-Air Rekey (OTAR) of cryptographic keying material using a Government approved method such as the Joint Tactical Networking Center (JTNC) Information Repository (IR) Over-the-Air Server Service (OSS) Application Note (CDRL A040) for the Enterprise Over The Air Management (eOTAM) 2.0, Document Number RCPN 946-20R9-001, or newer for waveforms other than SINCGARS if offered. | O | |
| 171 | 3.1.6.1.4.2 | Shall support Over-the-Air Transfer (OTAT) of cryptographic keying material using a Government approved method such as the Joint Tactical Networking Center (JTNC) Information Repository (IR) Over-the-Air Management (OTAM) Application Note 1.3 dated November 2018, or newer for waveforms other than SINCGARS if offered. | O | |
| 172 | 3.1.6.1.4.3 | Shall support Over-the-Air Zeroization (OTAZ) of cryptographic keying material using a Government approved method such as the Joint Tactical Networking Center (JTNC) Information Repository (IR) Over-the-Air Management (OTAM) Application Note 1.3 dated November 2018, or newer for waveforms other than SINCGARS if offered. | O | |
| 173 | 3.1.6.1.5 | Shall support remote zeroization of keys individually or collectively for waveforms other than SINCGARS if offered. | O | |
| 174 | 3.1.6.2 | Key Handling and Storage | T | |
| 175 | 3.1.6.2.1 | Shall be capable of operating with Unclassified (CUI) and Classified (Secret) COMSEC. | T | |
| 176 | 3.1.6.2.2 | Shall support update of an existing COMSEC key from an attached SKL without requiring human intervention to modify existing presets. | T | |
| 177 | 3.1.6.2.2.1 | Shall support update of an existing COMSEC key from an attached Next Generation Key Loader device without requiring human intervention to modify existing presets. | O | |
| 178 | 3.1.6.2.2.2 | Shall support manual zeroization of keys individually or collectively. | T | |
| 179 | 3.1.6.3 | Key Retention | T | |
| 180 | 3.1.6.3.1 | Shall be capable of retaining mission variables for at least 144 hours after loss of primary power. | T | |
| 181 | 3.1.6.3.2 | The CNR Radio shall provide a hold up battery (HUB) solution with capability to retain core WATARI or JOSEKI variables with a 12 month or greater operational life. | T | |
| 182 | 3.1.6.3.3 | The CNR Radio shall provide an internal hold up battery (HUB) with capability to retain core WATARI or JOSEKI variables (without external power e.g. Shelf-Life Extension Module) with a 5 year or greater operational life. | O | |
| 183 | 3.1.6.3.4 | Holdup battery shall be field replaceable. | T | |
| 184 | 3.1.6.3.5 | Holdup battery shall automatically recharge itself from the radio’s power. | O | |
| 185 | 3.1.7 | CNR-RT Environmental Testing | T | |
| 186 | 3.1.7.1 | Shall not degrade environmental compliance of extant mount that the CNR-RT fits within. | T | |
| 187 | 3.1.7.2 | Altitude (Low Pressure) | T | |
| 188 | 3.1.7.2.1 | Shall withstand low pressure storage at an altitude of 15,000 ft. above sea-level in accordance with MIL-STD-810G, Method 500.5, Procedure I – Storage/Air Transport. | T | |
| 189 | 3.1.7.2.2 | Shall be operable at an unpressurized altitude of 15,000 ft. in accordance with MIL-STD-810G, Method 500.5, Procedure II – Operation/Air Carriage. | T | |
| 190 | 3.1.7.3 | Temperature | T | |
| 191 | 3.1.7.3.1 | Shall operate in temperatures ranging from -30° C to +55° C verified by testing in accordance with MIL-STD-810G, Methods 501.5, Procedure II – Operation and 502.5, Procedure II – Operation. | T | |
| 192 | 3.1.7.3.2 | Shall operate in temperatures ranging from -30° C to +71° C verified by testing in accordance with MIL-STD-810G, Methods 501.5, Procedure II – Operation and 502.5, Procedure II – Operation. | O | |
| 193 | 3.1.7.3.3 | Shall withstand storage temperatures from -30° C to +71° C verified by testing in accordance with MIL-STD-810G, Methods 501.5, Procedure I – High Temperature Storage and 502.5, Procedure I – Low Temperature Storage. | T | |
| 194 | 3.1.7.3.4 | Shall withstand storage temperatures from -55° C to +71° C verified by testing in accordance with MIL-STD-810G, Methods 501.5, Procedure I – High Temperature Storage and 502.5, Procedure I – Low Temperature Storage. | O | |
| 195 | 3.1.7.4 | Rain | T | |
| 196 | 3.1.7.4.1 | Shall be capable of operating in 10.2 cm (4 inches) of rain per hour and 64 kph (40 mph) wind for 40 minutes verified by testing in accordance with MIL-STD-810G, Method 506.5, Procedure I – Rain and Blowing Rain. | T | |
| 197 | 3.1.7.5 | Humidity | T | |
| 198 | 3.1.7.5.1 | Shall operate and be impervious to humidity with relative humidity from 5% to 95% non-condensing and conditions of mist and fog as verified by testing in accordance with MIL-STD-810G, Method 507.5, Procedure II Aggravated. | T | |
| 199 | 3.1.7.5.2 | Shall survive storage in hot, humid conditions as verified by testing in accordance with MIL-STD-810G, Method 507.5, Procedure II Aggravated. | T | |
| 200 | 3.1.7.6 | Fungus | T | |
| 201 | 3.1.7.6.1 | Shall withstand, in both operating and non-operating conditions, exposure to fungus growth as encountered in tropical climates and not support fungal growth verified by testing in accordance with MIL-STD-810G, Method 508.6 using Table 508.6-I. | T | |
| 202 | 3.1.7.7 | Salt-Fog | T | |
| 203 | 3.1.7.7.1 | Shall be resistant to the corrosive effects of salt-sea atmosphere verified by testing in accordance with MIL-STD-810G, Method 509.5. | T | |
| 204 | 3.1.7.8 | Sand and Dust | T | |
| 205 | 3.1.7.8.1 | Shall withstand exposure to fine dust particles, in wind speeds of 1,750 feet per minute, and sand particles, in wind speeds of 5,700 feet per minute, verified by testing in accordance with MIL-STD-810G, Method 510.5, Procedure I, Blowing Dust and Procedure II, Blowing Sand. | T | |
| 206 | 3.1.7.9 | Vibration | T | |
| 207 | 3.1.7.9.1 | Shall be operational during and after undergoing vibration induced by vehicular transport (both tracked and wheeled) over all types of roads and cross country terrain and vibration associated with transportation verified by testing in accordance with MIL-STD-810G, Method 514.6, Procedure II, Loose Cargo Transportation. | T | |
| 208 | 3.1.7.10 | Shock | T | |
| 209 | 3.1.7.10.1 | The specified system and individual items within the equipment shall be operational during and after undergoing shock associated with servicing and handling, and during ground, rail, sea and air transport. Vehicular mounted equipment shall not break away when subjected to crash hazard conditions verified by testing in accordance with MIL-STD-810G, Method 516.6, Procedure I – Functional Shock and Procedure V – Crash Hazard Shock Test. | T | |
| 210 | 3.1.7.11 | Temperature Shock | T | |
| 211 | 3.1.7.11.1 | Shall be tested in accordance with MIL-STD 810G, Method 503.5, Procedure I, using the low temperate of -30° C ,and successfully pass such test. | T | |
| 212 | 3.1.7.12 | Immersion | T | |
| 213 | 3.1.7.12.1 | Shall be capable of being powered on during and operational after immersion of the RT in at least 2 meters of seawater for 30 minutes verified by testing in accordance with MIL-STD-810G, Method 512.5, Procedure I – Immersion. | T | |
| 214 | 3.1.7.12.2 | Shall include a watertight battery connection that interfaces with batteries and permits immediate operation of the CNR Radio after immersion in at least 2 meters of seawater for 30 minutes. | T | |
| 215 | 3.1.7.12.3 | Shall include a watertight RF connection that interfaces with an antenna and permits immediate operation of the CNR Radio after immersion in at least 2 meters of seawater for 30 minutes. | T | |
| 216 | 3.1.7.13 | Solar Radiation | T | |
| 217 | 3.1.7.13.1 | Shall operate in an environment with solar loading and operate after exposure as specified in accordance with MIL-STD-810G, Method 505.5, Procedure I – Cycling, Temperature Cycle A1. | T | |
| 218 | 3.1.7.14 | Electromagnetic Environmental Effects (E3) Survivability | T | |
| 219 | 3.1.7.14.1 | Shall withstand the effects of High Altitude Electromagnetic Pulse (HEMP) in accordance with MIL-STD-2169B. | T | |
| 220 | 3.1.7.14.2 | Shall be able to perform mission essential communication functions following exposure to Near Strike Lightening (NSL) events in accordance with MIL-STD-464C. | T | |
| 221 | 3.1.7.14.3 | Shall comply with Electro Static Discharge (ESD) requirements of MIL-STD-464C. | T | |
| 222 | 3.1.7.14.4 | Explosive Atmosphere. Shall not induce ignition when operated at maximum operating temperature or maximum loads in the presence of explosive atmosphere. | T | |
| 223 | 3.1.7.14.5 | The CNR Radio shall meet EMI control requirements CE106, CS114, CS115, CS116, RE101, and RE102 of MIL-STD-461F. These requirements are clarified in this PRD, which are in addition to requirements subordinate to TEMPEST, NSA cert, and JITC certification. | T | |
| 224 | 3.1.8 | Other Requirements and Capabilities | T | |
| 225 | 3.1.8.1 | Presets: Shall have the storage capacity to store 50 presets. | T | |
| 226 | 3.1.8.2 | Audible Status: The radio shall provide audible status, alerts and cues. | T | |
| 227 | 3.1.8.3 | Shall utilize Tactical Public Key Infrastructure (PKI) certificates issued from Army to validate communications from the network manager and prevent unauthorized access or remote procedure calls. | O | |
| 228 | 3.1.8.4 | The CNR Radio shall be interoperable with Army network management tools and shall support the network manager capabilities to plan, implement, manage, control, identify, and configure user access and profile parameters of the network to include, but not limited to; voice call group participation and physical network presets. | T | |
| 229 | 3.1.8.5 | The CNR Radio shall implement Cyber and EW defense. | T | |
| 230 | 3.1.8.5.1 | The CNR Radio shall implement TRANSEC to mitigate RF playback attacks. | T | |
| 231 | 3.1.8.5.2 | The CNR Radio shall log detected invalid emissions as potential EW events and alert the user within 10 seconds. | O | |
| 232 | 3.1.8.5.3 | The CNR Radio shall transmit a report to higher echelons via the Electronic Warfare Program Management (EWPMT) any invalid or interfering emissions as potential EW events. | O | |
| 233 | 3.1.8.5.4 | The CNR Radio shall log invalid attempts to execute commands as potential Cyber events and alert the user within 10 seconds. | O | |
| 234 | 3.1.8.5.5 | The CNR Radio shall transmit a report to higher echelons via the Electronic Warfare Program Management (EWPMT) any invalid attempts to execute commands as potential Cyber events. | O | |
| 235 | 3.1.8.6 | The CNR Radio shall implement Cyber and EW offense. | O | |
| 236 | 3.1.8.6.1 | The CNR Radio shall perform a scan of the RF spectrum to log energy detects (power level, time, center frequency). | O | |
| 237 | 3.1.8.6.2 | The CNR Radio shall have the ability to synchronize transmit (center frequency, bandwidth, and precision time) with other radios on network to perform distributed EW/CYBER. | O | |
| 238 | 3.1.8.6.3 | The CNR Radio shall have the ability to operate on a open source software framework like OpenCPI. | O | |
| 239 | 3.1.8.7 | The CNR Radio shall be capable of radio set cloning between other CNR Radios. | O | |
| 240 | 3.1.8.8 | The CNR Radio processing resources shall be less than 50% occupied while running any configuration of the SINCGARS waveform to include Field-Programmable Gate Array (FPGA) and accompanying General Purpose Processor (GPP). Rationale: the 50% is a target that assures waveform software upgrades would not overwhelm the selected hardware. Although upgrades and processor space or memory space are not linear relationships the intent is to allow overhead for future growth. | O | |
| 241 | 3.1.8.9 | The CNR Radio shall have the capability to assign network addressing to devices connected to it when operating an IP-based data waveform. | O | |
| 242 | 3.1.8.10 | The CNR Radio shall be capable of performing distributed processing through multiple interfaces (RS-232, RS-422, RS-423, USB, network waveform, etc). | O | |
| 243 | 3.2 | Dismounted SINCGARS2 Radio Set Capabilities. The SINCGARS2 Radio shall demonstrate: |
* The capabilities required by PRD 3.1 when the SINCGARS2 Radio is combined with the legacy handsets and antenna(s) required for dismounted operations.
* Operational Availability (Ao) of 96% (Threshold) and 99% (Objective).
* Material Availability (Am) of 75% (Threshold), 96% (Objective) for a population of 100,000 radios.
* Mean Time Between Essential Function Failure (MTBEFF) no less than 477 (Threshold) and 683 (Objective) hours.
* 86% (Threshold) and 90% (Objective) probability of operating over a 72-hour period without an essential function failure.
| * Ability to adjust data rates, revert to voice-only, change waveform modes, and alternate between frequencies to continue operations, in a degraded mode, during Cyber and EW threat conditions. | T | ||
| 244 | 3.3 | Mounted SINCGARS2 Radio Set Capability. The Mounted SINCGARS2 Radio Set shall demonstrate: |
* The capabilities required by PRD 3.1 when the SINCGARS2 Radio is combined with the legacy hardware required for mounted operations.
* Operational Availability (Ao) of 94% (Threshold) and 97% (Objective) per channel.
* Mean Time Between Essential Function Failure (MTBEFF) of no less than 386 (Threshold) and 517 (Objective) hours per channel.
* 83% (Threshold) and 87% (Objective) probability of operating over a 72-hour period without an essential function failure.
| * Configuration power consumption draw of no more than 15 Amps. | T | |||
| 245 | 3.3.1 | Mounted CNR Functions (M-CNR) | T | |
| 246 | 3.3.1.1 | Shall allow the CNR-RT to be installed/uninstalled without any special tools and/or equipment. | T | |
| 247 | 3.3.1.2 | Power Management | T | |
| 248 | 3.3.1.2.1 | Shall accept prime power to the RT from the legacy mount and run off the vehicular power. | T | |
| 249 | 3.3.1.2.2 | Shall operate continuously when powered from vehicle power of 20-32 VDC. | T | |
| 250 | 3.3.1.2.3 | Shall charge a common rechargeable battery installed within the RT. | O | |
| 251 | 3.3.1.2.4 | Shall permit use of the radio’s battery while vehicle power is off, for low power operation without use of vehicle power amplifier while vehicle electricity is offline, or while the platform is restarting. Ability to operate while the vehicle is powered off is a soldier selectable capability so that the radio does not require reboot or waveform re-instantiation. | O | |
| 252 | 3.3.1.3 | VICTORY | O | |
| 253 | 3.3.1.3.1 | The M-CNR Radio shall provide an interface to an Ethernet-based In-Vehicle-Network (IVN) as specified in section 9.5.1 of the VICTORY 1.9 specification. | T | |
| 254 | 3.3.1.3.2 | The M-CNR Radio Installation Kit, shall provide a Precision Time Protocol (PTP) client to receive time information via PTPv2 as specified in section 8.1.1.1.2 of the VICTORY 1.9 specification. | O | |
| 255 | 3.3.1.3.3 | Shall be compliant with VICTORY standard specifications Version 1.9 or later. | O | |
| 256 | 3.3.1.3.3.1 | The M-CNR Radio Installation Kit, shall subscribe to and receive multicast position information from the data interface of a position service as specified in section 8.1.2.1 of the VICTORY 1.9 specification. | O | |
| 257 | 3.3.1.3.3.2 | The M-CNR Radio, shall support the VICTORY IVN Data Radio Management interface in accordance with section 9.5.1 of the VICTORY 1.9 specification. | O | |
| 258 | 3.4 | The CNR-RT shall operate the SINCGARS waveform, meeting capabilities for legacy and modernized SINCGARS as shown in Table 3-6. See TAB B CNR DO1. | T | |
| 259 | 3.5 | Capabilities and Configurations | ||
| 260 | 3.5.1 | Route and Retransmission. Shall provide Route and Retransmission Capabilities equivalent to the legacy SINCGARS radio being upgraded including F1/F1 and F1/F2. | T | |
| 261 | 3.5.2 | CNR Radio Remote HMI. Shall provide a CNR Radio remote physical HMI that is capable of selecting presets, controlling the radio’s volume, and displaying the same information as required in paragraph 3.1. | T | |
| 262 | 3.5.3 | Mounted CNR Radio HMI. Shall provide a M-CNR Radio HMI that will mount securely in the vehicle interior and is capable of selecting presets, controlling the radio’s volume, and displaying the same information as required in paragraph 3.1. | T | |
| 263 | 3.5.4 | Mounted CNR Radio Remote HMI. Shall interface with the AN/PSN-11 Handheld Remote Control Radio Device (HRCRD) C-12493/U, 2-wire adapter, or CDU. | O | |
| 264 | 3.5.5 | Mounted CNR Radio Remote HMI. Shall provide the ability to operate in remote 2-wire SRCU mode. | O | |
| 265 | 3.5.6 | CNR Radio Dual Mount. Shall permit mounting and operation of two CNR Radios as a replacement for the legacy rack, e.g. SINCGARS VRC-91. In general, the intention is to install the CNR in existing SINCGARS VRC kits. For a new vehicle type that did not have any radios or previous installation kits, this dual mount could serve as an alternative to a refurbished legacy mount. | T | |
| 266 | 3.6 | Objective Waveforms and Services. The waveforms and services under 3.6 shall include all software as necessary to meet the capability. | O | |
| 267 | 3.6.1 | TSM (TSMTM will be referred to as TSM) and WREN-TSM Waveform | O | |
| 268 | 3.6.1.1 | Shall provide TSM waveform 6.1 capability with Secret And Below (SAB) voice and data. | T | |
| 269 | 3.6.1.2 | Shall provide TSM waveform 6.1 capability with Controlled UNCLASSIFIED Information (CUI) voice and data. | T | |
| 270 | 3.6.1.3 | Shall provide Warrior Robust Enhanced Network (WREN) TSM 6.1 or later waveform capability IAW CERDEC specifications while completing the associated Government (CERDEC) Waveform Conformance and Interoperability Assessment for Controlled Unclassified Information (CUI) voice and data as defined in the WREN INFOSEC Design Document v1.3 or later. Compliance with the WREN INFOSEC design documentation includes DHCP, COMSEC, TRANSEC, and Key Management functions. | T | |
| 271 | 3.6.1.4 | WREN Wideband (WREN TSM) SECRET and Below (SAB). | T | |
| 272 | 3.6.1.4.1 | Shall provide to NSA WREN TSM 6.1 or later incremental development software and documentation for the waveform capability for SECRET and BELOW (SAB) voice and data as defined in the WREN INFOSEC Design Document v1.3 or later. Compliance with the WREN INFOSEC design documentation includes DHCP, COMSEC, TRANSEC, and Key Management functions. Shall provide the Vendor's Engineering Change Proposal (NSA ECP) with the accompanying software baseline and supporting documentation to NSA and be accepted for NSA staffing not later than 15 November 2021. | T | |
| 273 | 3.6.1.4.2 | Shall provide WREN TSM 6.1 or later waveform capability IAW CERDEC specifications while completing the associated Government (CERDEC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document v1.3 or later. Compliance with the WREN INFOSEC design documentation includes DHCP, COMSEC, TRANSEC, and Key Management functions. Shall obtain CERDEC Waveform and Interoperability Assessment not later than 15 November 2021. | T | |
| 274 | 3.6.1.5 | The channel spacing (RF selectivity) in TSM shall be sufficient for 1.2 MHz channel bandwidth to tolerate the presence of any other TSM network separated in frequency by 10 MHz center frequency spacing at full (handheld) power and 100 meters distance with no degradation in performance. | T | |
| 275 | 3.6.1.6 | The channel spacing (RF selectivity) in TSM shall be sufficient for 1.2 MHz channel bandwidth to tolerate the presence of any other TSM network separated in frequency by 5 MHz center frequency spacing at full (handheld) power and 100 meters distance with no degradation in performance. | O | |
| 276 | 3.6.1.7 | The TSM service shall provide configurable voice and data at various security levels. | T | |
| 277 | 3.6.1.7.1 | The CNR Radio channel operating TSM shall support Unclassified Voice and Unclassified Data simultaneously. | T | |
| 278 | 3.6.1.7.2 | The CNR Radio channel operating TSM shall support Secret Voice and Secret Data simultaneously. | O | |
| 279 | 3.6.1.7.3 | The CNR Radio channel operating TSM shall support Unclassified Voice and Secret Data simultaneously. | O | |
| 280 | 3.6.1.7.4 | The CNR Radio channel operating TSM shall support Secret Voice and Unclassified Data simultaneously. | O | |
| 281 | 3.6.1.7.5 | The CNR Radio channel operating TSM shall support Unclassified Voice while simultaneously supporting both Unclassified Data and Secret Data. | O | |
| 282 | 3.6.1.7.6 | The CNR Radio channel operating TSM shall support Secret Voice while simultaneously supporting both Unclassified Data and Secret Data. | O | |
| 283 | 3.6.1.8 | The Warrior Robust Enhanced Network-TSM (WREN-TSM) service shall provide configurable voice and data at various security levels. | T | |
| 284 | 3.6.1.8.1 | The CNR Radio channel operating WREN-TSM shall support Unclassified Voice and Unclassified Data simultaneously. | T | |
| 285 | 3.6.1.8.2 | The CNR Radio channel operating WREN-TSM shall support Secret Voice and Secret Data simultaneously. | T | |
| 286 | 3.6.1.8.3 | The CNR Radio channel operating WREN-TSM shall support Unclassified Voice and Secret Data simultaneously. | O | |
| 287 | 3.6.1.8.4 | The CNR Radio channel operating WREN-TSM shall support Secret Voice and Unclassified Data simultaneously. | T | |
| 288 | 3.6.1.8.5 | The CNR Radio channel operating WREN-TSM shall support Unclassified Voice while simultaneously supporting both Unclassified Data and Secret Data. | O | |
| 289 | 3.6.1.8.6 | The CNR Radio channel operating WREN-TSM shall support Secret Voice while simultaneously supporting both Unclassified Data and Secret Data. | T | |
| 290 | 3.6.1.8.7 | The CNR Radio channel operating WREN-TSM shall support monitoring one Unclassified audio Talk Group while talking on another Unclassified audio Talk Group. | T | |
| 291 | 3.6.1.8.8 | The CNR Radio channel operating WREN-TSM shall support monitoring one Unclassified audio Talk Group while talking on another Secret audio Talk Group. | O | |
| 292 | 3.6.1.8.9 | The CNR Radio channel operating WREN-TSM shall support monitoring one Secret audio Talk Group while talking on another Secret audio Talk Group. | O | |
| 293 | 3.6.2 | WREN-Narrow Band Waveform. Shall provide WREN-Narrowband (WREN-NB) capability IAW CERDEC specifications while completing the associated Government (CERDEC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document v1.3 or later. Compliance with the WREN INFOSEC design documentation includes DHCP, COMSEC, TRANSEC, and Key Management functions. | O | |
| 294 | 3.6.2.1 | The CNR Radio channel operating WREN-NB shall support Unclassified Voice and Unclassified Data simultaneously. | T | |
| 295 | 3.6.2.2 | The CNR Radio channel operating WREN-NB shall support Secret Voice and Secret Data simultaneously. | T | |
| 296 | 3.6.2.3 | The CNR Radio channel operating WREN-NB shall support Unclassified Voice and Secret Data simultaneously. | O | |
| 297 | 3.6.2.4 | The CNR Radio channel operating WREN-NB shall support Secret Voice and Unclassified Data simultaneously. | O | |
| 298 | 3.6.2.5 | The CNR Radio channel operating WREN-NB shall support Unclassified Voice while simultaneously supporting both Unclassified Data and Secret Data. | O | |
| 299 | 3.6.2.6 | The CNR Radio channel operating WREN-NB shall support Secret Voice while simultaneously supporting both Unclassified Data and Secret Data. | O | |
| 300 | 3.6.2.7 | The CNR Radio channel operating WREN-NB shall support monitoring one Unclassified audio Talk Group while talking on another Unclassified audio Talk Group. | T | |
| 301 | 3.6.2.8 | The CNR Radio channel operating WREN-NB shall support monitoring one Unclassified audio Talk Group while talking on another Secret audio Talk Group. | O | |
| 302 | 3.6.2.9 | The CNR Radio channel operating WREN-NB shall support monitoring one Secret audio Talk Group while talking on another Secret audio Talk Group. | T | |
| 303 | 3.6.2.10 | Shall provide WREN Narrowband waveform capability in the S-Band frequency range IAW CERDEC specifications while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document and the WREN NB INFOSEC specification. | O | |
| 304 | 3.6.2.11 | Shall provide WREN Narrowband waveform capability in the L-Band frequency range IAW CERDEC specifications while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document and the WREN NB INFOSEC specification. | T | |
| 305 | 3.6.2.12 | Shall provide WREN Narrowband waveform capability in the UHF Band frequency range IAW CERDEC specifications while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document and the WREN NB INFOSEC specification. | T | |
| 306 | 3.6.2.13 | Shall provide WREN Narrowband waveform capability in the VHF Band frequency range IAW CERDEC specifications while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessments for SECRET And Below (SAB) voice and data as defined in the WREN INFOSEC Design Document and the WREN NB INFOSEC specification. | O | |
| 307 | 3.6.3 | Other Waveforms | O | |
| 308 | 3.6.3.1 | Other Waveform 1. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O | |
| 309 | 3.6.3.2 | Other Waveform 2. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O | |
| 310 | 3.6.3.3 | Other Waveform 3. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O | |
| 311 | 3.6.3.4 | Other Waveform 4. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O | |
| 312 | 3.6.3.5 | Other Waveform 5. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O | |
| 313 | 3.6.3.6 | Other Waveform 6. Shall include while completing the associated Government (CERDEC/JITC) Waveform Conformance and Interoperability Assessment at the appropriate security level for that waveform. | O |
TAB A, DO 1, TECHNICAL PRD COMPLIANCE MATIX: PRD Dated DDMM20201 Solicitation Number: W15P7T-21-R-0009 Offeror's Company: __________________________________________ PRD Para 3.1 Receiver Transmitter Nomenclature/Part #: ___________________________________ Preparer's Name: __________________________________________ PRD Para 3.5.5 Mounted CNR Radio HMI Nomenclature/Part #: ___________________________________ Signature: __________________________________________ PRD Para 3.5.6 CNR Radio Dual Mount Nomenclature/Part #: ___________________________________ Date: __________________________________________
The purpose of the "TAB A CNR DO1" is for the Offeror to self-certify to the PRD requirements that their Mission-Ready SINCGARS2 Radio achieves. In reponse Column 1 “Compliant Y/N” , the Offeror shall indicate for all thresholds and objectives, compliance with the technical requirement by indicating a "Y" or "N" for the proposed radio identified by the Nomenclature/Part Number. All items certified in Column 1 shall also be certified in Column 2 and/or 3. In response Column 2 “Included in LR Baseline Radio Y/N”, the Offeror shall indicate whether or not the technical requirement certified in Column 1, is included in the offered baseline radio by indicating a "Y" or "N". Column 3 identifies additional capabilites that may be offered and priced separately from the baseline SINCGARS2-RT. For Column 3, the offeror shall certify to the capabilites that are included in the additional CLINs referencing the capabilities. In response Column 4 “Other Waveforms Certifications”, the Offeror shall indicate the CLIN and title of the Waveform(s) in accordance with the PRD section. For Columns 1-3, the Offeror shall not provide a response other than "Y" or "N". For all columns, the Offeror shall not leave any PRD threshold requirement blank, or indicate "N" for any PRD threshold or objective that was previously certified "Y" under the contract.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .