NEXCOM V3_FAA Responses to Vendor Questions_20230127.pdf

NEXCOM Version 3 (V3) UHF/VHF Radio Procurement Questions and Updates

1. Since the previously anticipated third quarter calendar year 2022 timeframe for the NEXCOM V3 SIR release has passed, is there an updated timeframe for its release?

• FAA Response: Yes. The final NEXCOM V3 SIR release is now anticipated to post onto SAM.gov in January 2023. Updated: Now anticipated in late February 2023.

2. If an Offeror wanted to maintain the same physical cabling interface as V1 and V2 radios for ease of radio interchange and FAA training and support, could the FAA provide physical interface definition (pinouts) for the rear ports and in particular the primary cable for both V1 and V2 radios?

• FAA Response: The FAA will utilize the awardee’s cabling, therefore there is no need to tailor designs to the legacy pinouts.

3. Are there any challenges with the existing connectors or cabling that the FAA would like to see corrected in V3?

• FAA Response: Again, there is no need to tailor current pinouts.

4. In the most recent June 15, 2022 version of the NEXCOM V3 Radio Product Description (PD) update, in Section 3.3.2.1 (Reference Frequency Monitor Connector) there is a change to include condition for requiring a BNC connector. Is it an accurate understanding that if the stated condition does not exist in a vendor’s radio design, then there is no need or requirement for the BNC Connector?

• FAA Response: Yes, this is an accurate understanding. See NEXCOM V3 Radio PD excerpts below:

3.2.2.1.7.a. The frequency tolerance of the receiver reference frequency shall be within +/- 0.0001 percent (+/- 1 ppm) of its reference value for a period of one year following alignment over the full frequency range specified in section 3.2.1.2, and the temperature range specified in section 3.4.3.2 (Operating Conditions).

3.3.2.1.b. If a measurement of the receiver frequency reference is required to align the radio to meet the tolerance defined in 3.2.2.1.7.a, the connector shall be a female BNC with shielded termination.

5. Our understanding of the most recent June 15, 2022 version of the NEXCOM V3 Radio PD, Section 3.2.2.2.14 (Antenna Transfer Relay (ATR)), Note 2, is that if internal filters and automatic switching are sufficient to meet the requirements/configurations, then there is no need for external RF and Filter connectors. Please confirm our understanding.

• FAA Response: The FAA does not need access to the internal filters (assuming that a vendor’s design has automatic internal-filter switching); however the FAA does need vendors to provide access to Transmitter RF OUT, Receiver RF IN, and the three ATR ports as depicted in Figure 6.3 and Figure 6.4. Based on your question, NEXCOM V3 Radio PD, Section 3.2.2.2.14 (Antenna Transfer Relay (ATR)), Note 2 has been updated as seen in the excerpt below:

3.2.2.2.14 Antenna Transfer Relay (ATR)

k) The radio shall be equipped with external removable jumpers, or equivalent RF switches2, capable of operational use to provide connectivity between the following connectors:

1) The RF and ATR2 connectors,

2) The RF to FILTER IN connectors,

3) The FILTER OUT to ATR2 connectors, and

4) The receiver’s FILTER OUT to RF IN connector.

Note 2: Refer to Section 6 for illustrations of typical ATR configurations. The requirements in subsection k, for access to discrete internal RF and FILTER connectors, can be waived if the vendor can meet all of the FAA configurations called out in Figure 6.3 and Figure 6.4 with internal filter switching.

6. Can the FAA disclose any regular maintenance issues with the V1 and V2 radios that have impacted MTBF and MTTR?

• FAA Response: FAA cannot disclose this information.

7. Will any destructive testing be conducted during Operational Capabilities Test (OCT)?

Please confirm.

• FAA Response: No. The NEXCOM V3 OCT does not intend to be destructive.

There are no requirements for an unpackaged handling tactical transport drops (aka, drop test). The FAA will test AC and DC power at OCT. Voltages applied will not exceed the requirements’ tolerances as specified in the NEXCOM V3 Radio PD. The FAA will incrementally apply lower voltages to document where vendors’ radios either power off or cease operations.

8. Are there expected to be additional EMI and EMP requirements beyond what are in Section 3.4.4 of the current draft? Will any be evaluated during Operational Capabilities Test (OCT)?

• FAA Response: For the purposes of NEXCOM V3 Radio procurement evaluation, the FAA intends to only evaluate the requirements in NEXCOM V3 Radio PD Section 3.4.4.b using the Analysis evaluation method. See Excerpts below.

3.4.4 Electromagnetic Compatibility Requirements

a) The radio equipment shall meet the appropriate Federal Communications Commission (FCC) authorizations as defined in 47 CFR Part 2 and 47 CFR Part 15 of the Code of Federal Regulations.

{Note: For the purposes of the NEXCOM V3 Radio procurement evaluation this shall will not be evaluated, but will be compulsory for the awardee after contract award}.

b) Electromagnetic emission and susceptibility of the radio equipment shall not exceed the GROUND, NAVY limits of MIL-STD-461G requirements: CE-102, CS- 101, CS-114, CS 115, CS-116, RE-102, and RS-103.

3.4.5 FCC Equipment Certification

a) Equipment Certification shall be obtained from the FCC in accordance with FCC rules and regulations in 47 CFR Part 2 and 47 CFR Part 87.

{Note: For the purposes of the NEXCOM V3 Radio procurement evaluation this shall will not be evaluated, but will be compulsory for the awardee after contract award}.

9. Is there an opportunity to get a draft copy Section L, Section M and any Section L & M Attachments {e.g., Operational Capabilities Test (OCT) Plan} prior to final SIR so that vendors can better understand OCT expectations and begin planning/preparation?

• FAA Response: The FAA is developing draft SIR Sections L & M (i.e., Instructions to Offerors, Evaluation Factors for Award and OCT Test Plan); if an opportunity arises, these drafts may be provided via SAM.gov, prior to the Final SIR; however, as previously stated, it is contingent on their development and the FAA legal review processes.

10. In Section C.2.2 (Statement of Work) Table 1, the draft says “FAA-STD-021A (Note:

FAA is researching and is considering updating this standard to SAE EIA-649). Can the FAA confirm is a decision has been made as to which Configuration Management standard will be used?

• FAA Response: Yes. The final SOW will reference SAE EIA-649.

11. In most recent June 15, 2022 version of the NEXCOM V3 Radio PD, Section

3.2.3.1.1.1.4 {Network Supervisory System (NSS)}, this section describes what we believe to be a current --- in-place system (NSS) --- that the FAA uses to monitor and control all VoIP ATM components, including the V3 radios. Is that correct?

• FAA Response: No. The NSS requirements in the NEXCOM V3 Radio PD do not describe an “in-place” FAA system because the FAA does not currently monitor VoIP ATM components with an NSS. The NSS requirements and descriptions are from ED-137C Volume 5: Supervision. The “network components” that would be managed via a NEXCOM V3 NSS are the NEXCOM V3 receivers and transmitters themselves. Based on your question, the FAA has updated the NSS section to provide better clarity. See the updated excerpt below:

3.2.3.1.1.1.4 Network Supervisory System (NSS)

Network Supervision functions are performed by a centralized NEXCOM V3 Network Supervision System (NSS) with capability of supervising, monitoring and controlling network components (i.e., NEXCOM V3 Radios (i.e., receivers and transmitters). all components in the VoIP ATM system including the NEXCOM V3 radio equipment.

The NSS is the SNMP manager, while the agent (i.e., MIB object or MIB variable) provides the interface between the manager and the network components (i.e., NEXCOM V3 Radios (i.e., receivers and transmitters) being managed. The NSS is considered a network tool, not interfering nor superseding other systems that vendors may have been introducing for the management, configuration, and supervision of their NEXCOM V3 Radios equipment.

The following requirements are applicable to the NEXCOM V3 Radio MDTS:

a) The MDTS should have an NSS supervision function.

12. NEXCOM V3 Radio PD, Section 3.2.3.1.1.1.4 also describes that the MDTS we supply under the contract “should have an NSS supervision function.” We are a little confused over this language. Please clarify with a diagram on the various network management interrelationships

• FAA Response: The NSS requirement is a “should” because it is a desired requirement, but not a compulsory ‘shall’ requirement. FAA refers vendors to ED- 137C Volume 5: Supervision.

13. Continuing in NEXCOM V3 Radio PD, Section 3.2.3.1.1.1.4, are any other applications that the NEXCOM V3 MDTS needs to interface with?

• FAA Response: No.

14. Will the FAA be including evaluation criteria that addresses key cost saving measures regarding how vendors introduce planned product improvements (i.e., parts, software, and/or interfaces)?

• FAA Response: Evaluation criteria will not be added from a cost savings perspective; however, the FAA intends to include evaluation criteria that will have vendors' describe how their implemented processes handle configuration management and change control.

15. Will the FAA be including evaluation criteria to addresses key cost saving measures related to vendors identifying and explaining their approaches for addressing potential changes to VoIP and other industry standards?

• FAA Response: Evaluation criteria will not be added from a cost savings perspective; however, the FAA intends to include evaluation criteria that will have vendors' describe aspects of their Contractor’s Master Test Approach (CMTA), Technical Support Services Approach (TSSA), and how their implemented processes handle configuration management and change control.

16. Will the FAA consider including evaluation criteria that requires addressing how vendors handle parts obsolescence in their COTS products so the FAA will know what to expect in terms of process and costs?

• FAA Response: Evaluation criteria will not be added from a cost savings perspective; however, the FAA intends to include evaluation criteria that will have vendors' describe how their implemented processes handle parts obsolescence in their products.

17. Has the FAA authorized use of Voice over Internet Protocol (VoIP) radios for Air Traffic Control (ATC) communications in the National Airspace System (NAS)? If not, when?

• FAA Response: No, the FAA has not authorized use of VoIP for ATC communications in the NAS. The initial deployment of the NEXCOM V3 UHF and VHF Radios will have an In-Service Decisions (ISD) to provide ATC communications in an analog mode. Given the size of the United States and the number of remote communications facilities that require legacy radios to be replaced, the duration of the Phase 3 radio deployment will take a minimum of 10 years to complete. Over the next decade as VoIP communications matures, all FAA procurements for telecommunication services (i.e., FENS), radios (i.e. NEXCOM V3 Radios), Air/Ground Protocol Converters (APCs), and voice communication systems (VCS) will reach a point where the FAA will need to make enterprise-level determinations for where and when analog ATC communications can be transitioned to VoIP ATC communications. The NEXCOM Phase 3 Program requires NEXCOM V3 radios to be compliant with the ED-137C-Change 1 VoIP interoperability standard because when the future FAA infrastructure is collectively ready to transition to VoIP, the NEXCOM V3 radios will be VoIP capable. It is anticipated that after the initial ISD for operating in an analog mode, a separate and future ISD will be needed to authorize VoIP capable radios (e.g., NEXCOM V3 radios) to operate in their VoIP mode and provide ATC communications in the NAS.

18. We would like to bring to the FAA’s attention that there are 3 errors within the Section B

Pricing Model excel spreadsheet:

1. Throughout – Microphone CLINs throughout all tabs do not allow price entry.

2. AB CLINs 1001-1002 tab – 1001C VHF HPTX (iii) does not allow bidder to enter warranty cost. It is marked as “NSP”.

3. AB CLINs 9001-9002 tab – 9001A is mislabeled as “Quality System Plan (QSP)” when it should be “VHF RCVR”.

• FAA Response: Thank you for bringing these errors to our attention. We have corrected these errors in the FAA’s Section B Pricing Model excel spreadsheet.

*** Begin FAA Responses to Vendor Questions January 2023***

19. Table 3-16 (Item 4) asks for transmitter timeout default to be set to 30s, Table 3-18 (Item 7 and 8) asks for the default timeout to be set to 0s - what is the correct default value?

Please correct the table containing the wrong value.

• FAA Response: There is no “wrong” value, but clarity was needed to distinguish the compulsory (shall) and desired (should) wording:

o Table 3-16 defines compulsory requirements (i.e. shall129) where the transmitter timeout range is 5s to 300s; and 30s is the defined default; if should34 is not implemented.

o Table 3-18 defines desired requirements (i.e. should34). The desired requirement requests a range of 0s to 300 sec; and if implemented, then 0s is the default which disables the transmitter timeout.

o Table 3-18 also defines another desired requirement (i.e. Should35) to have the capability to have a timeout set per SIP session.

o The clarifier above has been added to shall129 and a separate note has also been added to Table 3-18 that states: “If 0 to 300s range is implemented, then 0s is the default, not 30s. Replaces default setting in Table 3-16 Parameter #4.”

20. Section 3.2.3 and its subsections refer to compliance with tables 3-16, 3-17 and 3-

18. Some requirements ask for compliance to all functions with a specific table, if the majority of the functions are compliant will any score be awarded?

• FAA Response:

o Table 3-16 - All parameters in Table 3-16 (FAA compulsory requirements) have their own corresponding shall. Compliance will be determined at each shall.

o Table 3-17 - All parameters in Table 3-17 (ED-137C/5 ANNEX 3 MIB) have their own corresponding shall and should requirements. Compliance will be performed at each relevant shall and should. FAA desired default requirement settings (“shoulds”) are shown in blue shading. Please note Table 3-17 did not apply “blue shading” to any default settings, applicable ranges or increments that have a corresponding FAA compulsory shall. Therefore while ANNEX 3 MIB may not define a compulsory default setting, applicable range or increment --- in some cases --- the FAA V3PD does. In these specific cases, the FAA V3PD requirement “shall” takes precedence (to avoid confusion) and they are included in Table 3-17 for consistency (i.e., shall3, shall143, shall144). In every other case, blue shading is applicable to individual desired (“should”) requirements.

o Table 3-18 - All parameters in Table 3-18 (FAA desired requirements) have their own corresponding should. Compliance will be performed at each should.

21. Requirements within 3.2.3.1.1.1.1 MDTS Protocols and MIB - If a vendor does not implement SNMP in their MDTS then requirements c to i cannot be achieved. 6.22 states the MDTS is dependent on vendor implementation and has no specific requirement to be SNMP based. It is the belief that 3.2.3.1.1.1.1 is requesting compliance to SNMP rather than MDTS functionality and is therefore requested that all mention of MDTS be removed.

• FAA Response: The FAA concurs with your assessment:

o Phrase “MDTS and” has been deleted from requirements c, d and e, such that they now begin with: “The radio MIB shall…” o Requirements f through i have been updated to read: “The MDT interface shall…” o Additionally 3.2.3.1.1.1.3 also updated c and d, to read “The MDT interface shall…”

22. Requirements 3.2.3 x) & 3.2.3.1.1.1.1 d) - Table 3-17 has some applicable ranges, default settings and/or increment values that do not conform to ED-137C {i.e., Table 3-17 item 9

- (4) should be snOrCarrier (sic) and (5) should be snAndCarrierOveride (sic)}

• FAA Response: Subsequent to the v1.5 (June 2022) version of the PD, some changes were made to receiver squelch requirements (i.e., shall88, shall93, should24) and yes, Table 3-16 item #15 and Table 3-17 item 9 - now include state (4) as snOrCarrierOverride and state (5) as snAndCarrierOverride.

23. Requirements 3.2.3 x) & 3.2.3.1.1.1.1 d) - Table 3-17 has some applicable ranges, default settings and/or increment values that do not conform to ED-137C {i.e., Items 11 and 12 -applicable ranges should be in dBm not W}

• FAA Response: FAA uses Watts (W) in all RF Output Power requirements (i.e., shall3, shall144, should42). Therefore the FAA aligned those units in Table 3-17 in accordance with other defined shalls and shoulds to avoid any confusion.

24. Requirements 3.2.3 x) & 3.2.3.1.1.1.1 d) - Table 3-17 has some applicable ranges, default settings and/or increment values that do not conform to ED-137C {i.e., and Increment should be 1dB not <0.25dB.}

• FAA Response: This comment was received during V3 Market Surveys; however, the request does not supersede or change the FAA requirement. The FAA requirement (i.e., shall143) will remain an increment of <0.25dB, not 1dB.

25. Requirement 3.2.2.1.8 f) - This requirement asks for the local audio output to be adjustable up to +10dBm. Requirement 3.2.2.1.1 d) states the local audio output is to be used with headset/headphones. It is believed that a level of +10dBm for headset/headphone use would result in dangerously high audible levels for a user. It is requested that the 3.2.2.1.8 f) requirement either be removed or the maximum level be reduced to safe listening levels such as +3dBm (+/-3dB). It is also noted that requirement

3.2.2.1.1 i) covers the same requirement for audio levels required and is probably more appropriate than quoting specific levels in this instance.

• FAA Response: FAA laboratory testing with headsets with various impedances shows that +10 dBm (10 mW), delivered to the 30 to 600 ohm load, provides a sufficient range of listening levels for the intended application. No change to shall72.

26. Requirement 3.2.3 aa) refers to item 6 - PTT Status, and table 3-16 item 11 - Squelch Break Status. However, please note that PTT Status is actually item 7 and Squelch Break Status is item 9.

• FAA Response: FAA has corrected these errant Table 3-16 references in shall212.

Thank you!

Shall # Should # FAA-E-37021 Paragraph Requirement

Shall Prioritization

Level

Should Prioritization

Level

1 3.2.d

The UHF high power transmitter,1,2,3 or UHF extended power transmitter,1,2,3 should1 be implemented as defined by the desired operational output power function in Table 3-1 and Table 3-11.

N/A High

39 3.2.1.5.3.a

The receiver shall39 detect the presence of any RF signal at the antenna port, break squelch, demodulate, and process and present audio to the respective audio interface ports, or be ready to respond to VoIP protocol handshaking requests using a static IP address, within 6 seconds of power reactivation1 from a facility service restoral.

High N/A

40 3.2.1.5.3.b

The transmitter shall40 re-accept any analog (discrete) push-to-talk (PTT) key from a respective PTT key interface, process any analog audio stream, and modulate an analog stream onto an RF carrier for transmission at the antenna port within 6 seconds of power reactivation1 from a facility service restoral, or be ready to respond to VoIP protocol handshaking requests using a static IP address within 6 seconds of power reactivation1 from a facility service restoral.

High N/A

52 3.2.2.1.2.b The receiver shall52 produce a SINAD of 10 dB or greater at the remote audio output when a standard desired signal of no more than −102 dBm is present at the receiver RF input2.

High N/A

9 3.2.2.1.5.a The VHF receiver should9 not have image frequencies within the 112.000 MHz to 150.000 MHz band. N/A High

10 3.2.2.1.5.b The UHF receiver should10 not have image frequencies within the 225.000 MHz to 399.975 MHz frequency band. N/A High

55 3.2.2.1.6.1.a

The sensitivity requirements defined in section 3.2.2.1.2 shall55 not be degraded by more than 3 dB in the presence of two undesired signals as defined in Case A of Table 3-5, with frequencies chosen such that one of the 3rd order products is located on the receiver operating frequency.

High N/A

Shall Prioritization

Level

Should Prioritization

Level

56 3.2.2.1.6.1.b

The sensitivity requirements defined in section 3.2.2.1.2 shall56 not be degraded by more than 3 dB in the presence of two undesired signals as defined in Case B of Table 3-5, with frequencies chosen such that one of the 3rd order products is located on the receiver operating frequency.

High N/A

57 3.2.2.1.6.1.c

The sensitivity requirements defined in section 3.2.2.1.2 shall57 not be degraded by more than 3 dB in the presence of two undesired signals as defined in Case C of Table 3-5, with the frequencies of the undesired signals offset from the receiver operating frequency by +2.0 MHz and +4.0 MHz, or –2.0 MHz and –4.0 MHz, respectively.

High N/A

58 3.2.2.1.6.1.d

The sensitivity requirements defined in section 3.2.2.1.2 shall58 not be degraded by more than 3 dB in the presence of two undesired signals as defined in Case D of Table 3-5, with frequencies chosen such that the 2nd order products are located on the chosen UHF receiver operating frequency.

High N/A

59 3.2.2.1.6.2.a

The sensitivity requirements defined in section 3.2.2.1.2 shall59 not be degraded by more than 2 dB in the presence of a standard undesired signal separated by ±0.5 MHz and at a level 70.0 dB above the rated desired signal.

High N/A

60 3.2.2.1.6.2.b

The sensitivity requirements defined in section 3.2.2.1.2 shall60 not be degraded by more than 2 dB in the presence of a standard undesired signal separated by ±1.0 MHz and at a level 75.0 dB above the rated desired signal.

High N/A

61 3.2.2.1.6.2.c

The sensitivity requirements defined in section 3.2.2.1.2 shall61 not be degraded by more than 2 dB in the presence of a standard undesired signal separated by ±1.5 MHz and at a level 80.0 dB above the rated desired signal.

High N/A

11 3.2.2.1.8.c The remote audio output level of the receiver should11 be adjustable in 0.25 dB steps or less. N/A High

13 3.2.2.1.8.g The local audio output level1 of the receiver should13 be adjustable in 0.5 dB steps or less. N/A High

Shall Prioritization

Level

Should Prioritization

Level

78 3.2.2.1.13.a

The remote audio output shall78 not be distorted by more than 2.0 percent in the presence of a standard desired signal for 30 percent modulation with any RF input level between −67 dBm and −27 dBm, for any input tones within the rated audio band for the relevant channel spacing configuration.

High N/A

79 3.2.2.1.13.b

The remote audio output shall79 not be distorted by more than 5.0 percent for 90 percent modulation with any RF input level between −67 dBm and −27 dBm, for any input tones within the rated audio band for the relevant channel spacing configuration.

High N/A

89 3.2.2.1.15.2.a

When both the Audio Signal-to-Noise (S/N) Squelch function and RF Carrier Squelch function are enabled (i.e., snAndCarrier), then the receiver remote and local audio shall89 be enabled when the received signal exceeds both the RF Carrier Threshold and the Audio S/N Threshold values defined in b) and e) below.

High N/A

90 3.2.2.1.15.2.b

The receiver Audio S/N Squelch Threshold value shall90 be adjustable in 1 dB steps or less in the range of +6 dB to +20 dB in the presence of a DSB-AM signal modulated 30 percent with a 1004 Hz tone.

High N/A

92 3.2.2.1.15.2.e The RF Carrier Squelch Threshold level shall92 be adjustable in 1 dB steps or less in the power range from – 102 dBm to –70 dBm.

High N/A

93 3.2.2.1.15.2.f The RF Carrier Squelch closing hysteresis shall93 not be less than 2 dB and not greater than 7 dB with respect to the squelch opening point1.

High N/A

97 3.2.2.1.15.3.a The squelch attack time shall97 not exceed 30 ms with any standard desired signal with an RF level between −102 dBm and −7 dBm.

98 3.2.2.1.15.3.c The squelch release time shall98 not exceed 35 ms. High N/A

Shall Prioritization

Level

Should Prioritization

Level

99 3.2.2.1.16.a

The sensitivity requirements defined in section 3.2.2.1.2 shall99 not be degraded by more than a specified value in the presence of a transmitter, configured to be a standard undesired signal except with an AM Depth of 90%, set for rated output power (see section 4.1.2.4), when the transmit-receive frequency separation and path isolation are as defined in Table 3-7.

High N/A

28 3.2.2.1.16.b

The sensitivity requirements defined in section 3.2.2.1.2 for the UHF receiver should28 not be degraded by more than a specified value in the presence of a transmitter, configured to be a standard undesired signal except with an AM Depth of 90%, set for rated output power, when the transmit-receive frequency separation and path isolation are as defined in Case D of Table 3-7.

N/A High

105 3.2.2.1.20.a

The sensitivity requirements of section 3.2.2.1.2 shall105 not be degraded by more than a specified level not later than the required attack time after insertion of a specified undesired signal as defined in Table 3-9.

High N/A

106 3.2.2.1.20.b The sensitivity requirements of section 3.2.2.1.2 shall106 be met not later than 150 ms after removal of an undesired signal as defined in Table 3-9.

30 3.2.2.1.23.h

The receiver should30 have SCT detection times of 1 second or less if signal differences are between 10dB to 22dB for frequency offsets between 15 Hz and 3 kHz.

N/A High

31 3.2.2.1.23.i

The receiver should31 have SCT detection times of 0.5 second or less if signal differences are less than 10 dB for frequency offsets between 15 Hz and 3 kHz.

N/A High

131 3.2.2.2.3.a

The transmitter modulation distortion shall131 not exceed 5 percent root mean square (RMS) with the transmitter modulated at 90 percent with any audio signal as specified for 25 kHz channel spacing in Table 3-10.

Shall Prioritization

Level

Should Prioritization

Level

132 3.2.2.2.3.b

The VHF transmitter modulation distortion shall132 not exceed 5 percent RMS with the transmitter modulated at 90 percent with any audio signal as specified for 8.33 kHz channel spacing in Table 3-10.

High N/A

136 3.2.2.2.4.f

The transmitter shall136 prevent modulation levels that exceed 100 percent for an audio signal that varies over the audio input level and frequency ranges specified in Table 3-10.

High N/A

38 3.2.2.2.4.g

The transmitter should38 prevent modulation levels that exceed 100 percent for a government furnished speech sample with input audio signals that varies over the audio input level and frequency ranges specified in Table 3-10.

N/A High

138 3.2.2.2.5.b

The transmitter shall138 operate at a VSWR of 2.0:1 or less, at all phase angles, with no damage, with no part exceeding dissipation limits, with no performance degradation, and maintain the power level setting within ±1 dB of the nominal setting as measured into a normal load, see section 4.1.4.

High N/A

139 3.2.2.2.5.c

The transmitter shall139 deliver not less than 50 percent of the set Continuous Wave (CW) RF signal power, into any impedance having a maximum VSWR of 3.0:1 at any phase angle2.

High N/A

144 3.2.2.2.5.k

The transmitter shall144 deliver the RF output level as defined in Cases A and B of Table 3-11 below into a normal load when transmitting a CW signal across the relevant operating frequency range of the radio2,3.

High N/A

42 3.2.2.2.5.l

The UHF high power transmitter should42 deliver the RF output level as specified in Case C of Table 3-11 into a normal load when transmitting a CW signal across the relevant operating frequency range of the radio1,2,3.

Shall Prioritization

Level

Should Prioritization

Level

147 3.2.2.2.6.a

The amplitude of each radio frequency back intermodulation product shall147 be no greater than a specified level when the transmitter (unmodulated and set for rated output power) is keyed and an undesired signal, with frequency separation and signal level as defined in Table 3-12 below, is fed into the transmitter output connector.

High N/A

148 3.2.2.2.7.a The transmitter shall148 have the capability to operate at a 100 percent duty cycle at its maximum rated output power. High N/A

152 3.2.2.2.9.a

The level of each carrier harmonic shall152 be less than −80.0 dBc (−65 dBm within the L5 (1164 to 1215 MHz) and L1 (1559 to 1610 MHz) band) when the transmitter, set for rated power, is keyed without modulation into a normal load.

High N/A

153 3.2.2.2.10.a

The transmitter’s first adjacent channel 25 kHz band-power, shall153 not exceed −40 dBc when it is modulated with a standard test signal and configured for 25 kHz channel spacing and rated output power.

High N/A

154 3.2.2.2.10.b

The VHF transmitter’s first adjacent channel 8.33 kHz band-power shall154 not exceed −30 dBc when it is modulated with a standard test signal and configured for

8.33 kHz channel spacing and rated output power.

High N/A

155 3.2.2.2.10.c

The transmitter’s adjacent channel 25 kHz band-power shall155 not exceed the limits as defined in Table 3-13 when it is modulated with a standard test signal and configured for 25 kHz channel spacing and configured for rated output power.

High N/A

156 3.2.2.2.10.d

The UHF transmitter’s adjacent channel 25 kHz band-power shall156 not exceed −130 dBc within the VHF band, as specified in this PD, when it is modulated with a standard test signal and configured for rated output power.

Shall Prioritization

Level

Should Prioritization

Level

167 3.2.2.2.12.1 c

The transmitter shall167 key when a remote key voltage between +8VDC (or the positive adjustable keying threshold, if should45 is implemented) and +48 VDC, or between -8VDC (or the negative adjustable keying threshold, if should45 is implemented) and -48VDC, is applied.

High N/A

45 3.2.2.2.12.1 i The transmitter remote key threshold level should45 be adjustable as defined in Table 3-14. N/A High

174 3.2.2.2.12.3 a

The transmit key time, including key debounce time, shall174 not exceed 30 ms as measured from the application of a key signal to the time when the transmitter is at 90 percent of the full power level.

High N/A

47 3.2.2.2.12.3 b The debounce circuit delay should47 not be less than 10 ms. N/A High

48 3.2.3.b The radio equipment should48 allow monitoring and control by interface and interoperation through a front panel interface1.

N/A High

64 3.2.3.2.1.a The radio front panel interface1 should64 implement all analog interface control functions required to setup or configure the radio without the need of an MDT.

N/A High

87 3.2.4.1.b The radio equipment should87 have more than one remote IP interfaces on its rear panel. N/A High

284 3.2.5.3.e The remote IP interface(s) shall284 support Voice over IP (VoIP) as described in ED-137C/1 specifications (excluding paragraphs 3.6.1.16, 3.6.1.17, 3.8.1.6, 3.8.1.7).

High N/A

90 3.4.1.9.e A ¼"-20 ground lug should90 be located on the lower right side of the radio equipment as viewed from the rear. N/A High

99 3.4.2.1.c Both AC and DC voltage inputs should99 be located on the lower right side1 of the radio equipment as viewed from the rear.