STC_NGMP_RFP_Questions_and_Answers_4Jan17.pdf

PDF 47 KB Posted

Attached to
Special Operations Forces (SOF) Tactical Communications (STC) Next Generation ManPack (NGMP) Radio
Solicitation number
H92222-17-R-0008
Issued by

About this file

STC NGMP RFP Questions and Answers 4Jan17

View the file

Other files

File Type Posted
H92222-17-R-0008_Amend_0003_25Jan17.pdf PDF
Atch_03_NGMP_Price_Matrix_(CLINs_and_ELINs)_25Jan17.xlsx XLSX spreadsheet
NGMP_Section_L_Amend_3_25Jan17_(with_Track_Changes).docx DOCX document
Atch_01_NGMP_PS_25Jan17.pdf PDF
STC_NGMP_RFP_Q_A_25Jan17.pdf PDF
H92222-17-R-0008_Amend_0003_Conformed_25Jan17.pdf PDF
Atch_01_NGMP_PS_25Jan17_(with_Track_Changes).docx DOCX document
STC_NGMP_RFP_Questions_and_Answers_Batch_2_CORRECTED_12Jan17.pdf PDF
H92222-17-R-0008_Amendment_02_with_Track_Changes_11Jan17.docx DOCX document
Atch_01_NGMP_PS_9Jan17_with_Track_Changes.docx DOCX document
H92222-17-R-0008_Amendment_02_11Jan17.pdf PDF
H92222-17-R-0008_Amendment_02_Conformed_11Jan17.pdf PDF
STC_NGMP_RFP_Questions_and_Answers_Batch_2_11Jan17.pdf PDF
Atch_01_NGMP_PS_9Jan17.pdf PDF
H92222-17-R-0008_Amendment_01_6Jan17.pdf PDF
Atch_01_NGMP_PS_14Dec16.pdf PDF
Atch_05_NGMP_GFP_List_20Dec16.pdf PDF
Atch_01_NGMP_PS_14Dec16_Amend_01_with_Track_Changes.docx DOCX document
Atch_02_DD254_25_W-FOUO_Addendum_15Dec16.pdf PDF
H92222-17-R-0008_Amendment_01_Conformed_6Jan17.pdf PDF
H92222-17-R-0008_Amendment_01_with_Track_Changes_6Jan17.doc DOC document
Atch_04a_Warranty_Tracking_Information.xlsx XLSX spreadsheet
H92222-17-R-0008.pdf PDF
Atch_01_NGMP_PS_21Nov16.docx DOCX document
Atch_07_-_Q_and_A_Template.xlsx XLSX spreadsheet
Exhibit_D_NGMP_CDRLs_D001-D0021_2Nov16.pdf PDF
Atch_03_NGMP_Price_Matrix_(CLINs_and_ELINs).xlsx XLSX spreadsheet
Atch_02_DD254_with_FOUO_Addendum_14Oct16.pdf PDF
Atch_04b_Source_Of_Repair_Instructions.xlsx XLSX spreadsheet
Atch_05_NGMP_GFP_List_3Nov16.pdf PDF
Atch_06_Nameplate_Example_16May16.xlsx XLSX spreadsheet
Show all 31

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ITEM #

SECTION

NUMBER NAME OF SECTION COMMENT TYPE

(select from drop down)

QUESTIONS / COMMENTS

(If questions contain proprietary or SS Sensitive information offerors must Clearly annotate the restrictions within each question) Government Reponses

SECTIONS "A-M"

1 A Solicitation/Contract Form Substantive

Section A states that the Government intends to order approximately 7,507

STC NGMP.

For threshold capabilities provided as internal or external mission modules, what ratio of modules to NGMP radios will be used when the Government determines Total Evaluated Price (TEP) for the proposals?

What ratio of Vehicle Mount Systems (VMS) to NGMP radios will be used when the Government determines Total Evaluated Price (TEP) for the proposals?

For evaluation purposes the TEP will be calculated on a 1 to 1 ratio to the NGMP radio quantities selected for CLIN 0001 for those modules proposed as internal or external mission modules to radios. The Government will not provide the quantity of VMS systems that will be evaluated in determining the TEP. However, as a two channel system the Government expects that the VMS will be adopted for the majority of currently fielded vehicle mounted systems.

2 C Descriptions and Specifications Administrative SOW 14.0 (Program Security) indicates "Contractor is required to maintain a Secret facility clearance", while DD-254 1.a indicates that a Top Secret facility clearance is required. Please clarify this discrepancy.

Amendment 0001 will be issued to modify the SOW 14.0 to reflect the "Top Secret Facility" requirement.

3 C Descriptions and Specifications Administrative

SOW 14.0 (Program Security) indicates "Contractors will not require additional accesses (NATO, FGI, Focal Point, etc.) in performance of this effort", while DD-254 10.g indicates that access to NATO Information is required. Please clarify this discrepancy.

Amendment 0001 will be issued to revise the SOW to reflect NATO, Foreign Government Information (FGI) and Focal Point accesses are required.

4 F Deliveries or Performance Substantive

Section F, FAR clause 52.211-9: For clarification purposes, Contractor recommends updating paragraph (a) to read: All remaining deliveries, after the delivery of Delivery Order 0001, shall be in accordance with the following schedule.

Amendment 0001 will be issued to modify Section F, FAR clause 52.211-9 paragraph (a) to read "(with the exception of Delivery Order 0001 for the initial baseline radio delivery)." Additionally, Section L.4.2 has been revised to include reference to this clause as part of the conformed contract submission and subsequent responsibility determination.

5 J List of Attachments Administrative Based off changes to Attachments 01, 02, and 05; this list needs to be updated.

Amendment 0001 will be issued to and include updated dates for Attachments 01, 02, and 05 since these three attachments have been updated.

6 L Instructions, Conditions and Notices to Bidders Substantive

Section F, FAR clause 52.211-9: For clarification purposes, Contractor recommends updating paragraph (a) to read: All remaining deliveries, after the delivery of Delivery Order 0001, shall be in accordance with the following schedule.

Section L does not include reference to 52.211-9 intentionally. 52.211-9 is separate from Factor 1, Subfactor 2, Schedule, and will be reviewed as part of the administrative criteria via the conformed contract copy submittal.

Reference Section L.4.2, Amendment 0001.

7 L Instructions, Conditions and Notices to Bidders Substantive

L.1.1.1 Critical Performance Capabilities (CPC). Included in the CPC table is:

Land Mobile Radio (LMR) / APCO 25 Phase 1 & 2. Bidder suggests allowing evidence for "P25 capability" in general and not specifying the need for evidence of both Phase 1 and 2. Specific implementation details of Phase 1 and Phase 2 will be addressed in the proposal.

Amendment 0001 will be issued and modifies Section L.1.1.1 to state "Regarding APCO 25, the Government will accept applicable evidence of P25 implementation for either Phase 1 or Phase 2 capabilities."

8 M Evaluation Factors for Award Substantive

Paragraph M.1.1, second paragraph, is confusing starting with the 11th line from the top of the paragraph. The confusion is with the sentence that is addressing proposed objective capabilities that are incorporated into the radio within 6 months or less after availability of production radios. Please clarify intent of this paragraph.

The intent is to clarify that only proposed objectives and/or increased capabilities that will be considered in the evaluation are those that are either

a) available at the time of baseline radio delivery and/or b) would require a software update only within 6 months after the delivery of the baseline radio.

Amendment 0001 will be issued to clarify this further within both Sections L.1.1 and M.1.1

9 M Evaluation Factors for Award Substantive

L.1.1 and M.1.1 allows "Objectives and/or additional capabilities that are software-based only and can be incorporated into the NGMP radio" to be delivered within 6 months or less after the initial production radios are scheduled for delivery. Bidder suggests that this be modified to allow 12 months after initial production so that the Government will be able to receive as many objective and additional capabilities as possible.

Sections L.1.1 and M.1.1 will remain 6 months after initial delivery for those proposed objectives not available within the baseline radio upon initial delivery.

Performance Specification (PS)

10 Attachment 1 NGMP Government Performance Specification (PS) Substantive Is it the Governments intent/requirement that NGMP Mission Modules be interchangeable with NGHH Mission Modules?

No. There is no requirement for NGMP Mission Modules to be interchangeable with NGHH Mission Modules or vice versa. They are separate contracting initiatives; however, having interchangeable Line Replaceable Units such as antennas, cabling, and mission modules is optimal.

11 Attachment 1 NGMP Government Performance Specification (PS) Substantive

2.3 Order of Precedence. Bidder recommends that contracted product specification should take precedence. This will maximize the Government's ability to achieve the specific intents of the NGMP contract, and this is consistent with prior Government contracts for similar products.

Military Standards shall take precedence unless explicitly waived by the Government on a case-by-case basis.

12 Attachment 1 NGMP Government Performance Specification (PS) Substantive For 3.1.1 (NGMP Description) is it the intent for the supplier to deliver a 2

Channel headset/microphone assembly included in the CLIN 0001 price?

Yes since there is no requirement for an embedded speaker in the NGMP radio.

13 Attachment 1 NGMP Government Performance Specification (PS) Administrative

Many of the paragraph numbers that are aligned with the objectives in Appendix C are not consistent with the paragraph numbering in the main body of the PS.

Amendment 0001 will be issued to include revised paragraph numbers that to align Appendix C with the paragraph numbering in the PS.

14 Attachment 1 NGMP Government Performance Specification (PS) Administrative Are objective capabilities identified in the PS but are not listed in Appendix C will be considered favorably during evaluation if proposed?

Amendment 0001 will be issued to revise Appendix C such that all objective capabilities and waveforms identified in the PS are included and rank ordered in Appendix C.

15 Attachment 1 NGMP Government Performance Specification (PS) Substantive

For 3.1.2 (Accessories) Bidder suggests making VDC voltage consistent with other similar requirements within the RFP by changing range from 9-32 VDC to 10-32VDC.

Amendment 0001 will be issued to revise Paragraph 3.1.2 to reflect 10-32

VDC.

16 Attachment 1 NGMP Government Performance Specification (PS) Substantive

There appears to be a contradiction between Table 1 and Appendix C regarding the STD-CDL waveform. STD-CDL is identified in Table 1 as a threshold and in Appendix C as an objective. Which is correct?

Amendment 0001 will be issued and include a PS REV 1, and correct Appendix C to reflect that The STD-CDL is a threshold waveform.

17 Attachment 1 NGMP Government Performance Specification (PS) Substantive

A CCM-700 is identified in paragraphs 3.5.4- Table 1, 3.5.5.1 and 3.13.2.6 however, is this actually supposed to be CCM-700A and is the CCM-700A actually required since the KIV-700A contains the same algorithm?

Amendment 0001 will be issued and include PS REV 1 which amends the PS to remove the CCM-700 reference from Table 1 and paragraphs 3.5.5.1 and 3.13.2.6. The CCM-700A is not required since the coalition/NATO algorithm is embedded in the KIV-700A.

18 Attachment 1 NGMP Government Performance Specification (PS) Substantive

The following objective requirements are indicated in the body of the PS but are not listed in Appendix C of the PS. Please add these requirements to Appendix C such that their relative importance can be understood.

3.2 Configuration Parameters - Load configuration files-ADDED TO C

3.2.1.2-ADDED TO C

3.2.1.3-ADDED TO C

3.2.2.2-ADDED TO C

3.5.4, Table 1 - Key Storage-ADDED TO C 3.5.4, Table 1 - Waveforms (missing all but Tactical 466ER) ADDED TO C 3.5.4, Table 1 - Waveform Detection ADDED TO C

3.5.5.4 ADDED TO C

3.6.3 ADDED TO C

3.8.1.2.3 ADDED TO C

3.8.1.2.4 ADDED TO C

3.8.1.2.11.5 ADDED TO C

3.9.2.1 ADDED TO C

3.10.1.1 ADDED TO C

3.13.1.7 ADDED TO C

3.14.1.1.1 ADDED TO C

4.1.2.1.1 ADDED TO C

4.3.2.4.1 ADDED TO C

Amendment 0001 will be issued amending the PS to add the Objectives to Appendix C.

19 Attachment 1 NGMP Government Performance Specification (PS) Administrative

The following objective requirements in Appendix C require that their PS Paragraph number and/or Description be revised to match the revised numbering and text in the body of the PS.

3.2.1 (old #)

3.4.2.2 (old #) Table 2 (Frequency Ranges)

3.4.3.1 (old #)

3.8.4.4 (old #)

3.8.4.5 (old #)

3.8.4.6 (old #)

3.8.4.7 (old #)

3.8.4.8 (old #)

3.10.1.1 (old #, 2 instances)

3.12.1.4 (old #)

3.15.1.5.1 Table 5 (old table #)

4.2.1 (old #)

Amendment 0001 will be issued amending the PS to correlate the language and paragraph numbering with Appendix C.

20 Attachment 1 NGMP Government Performance Specification (PS) Administrative In Appendix C, for Waveforms, should there be a comma between "VNW" and

"STD-CDL Rev H"?

Amendment 0001 will be issued amending the PS to add a comma between VNW and STD-CDL.

21 Attachment 1 NGMP Government Performance Specification (PS) Administrative 3.5.5.4 should start a new paragraph. Amendment 0001 will be issued amending the PS to correct the paragraph numbering.

22 Attachment 1 NGMP Government Performance Specification (PS) Administrative The second instance of 3.5.5.4 should be numbered 3.5.5.5. Amendment 0001 will be issued amending the PS to correct the paragraph numbering.

23 Attachment 1 NGMP Government Performance Specification (PS) Substantive Is 3.5.5.4 intended to represent an ISR video stream "white list"? Yes, paragraph 3.5.5.4 is intended to represent the requirement for an ISR video stream White List.

24 Attachment 1 NGMP Government Performance Specification (PS) Substantive

Pertaining to 3.5.4 Table 1 Security & 3.5.5.1, is KGV-135A considered an acceptable NSA Type 1 approved ISR encryption? As stated, CCM-700 does not exist. Does the USG mean CCM-700A? If KIV-700A is required, then it should be a deferred threshold based upon its Type 1 NSA certification timeline. The CCM-700A is a separate NSA certified and NATO endorsed module. Is the CCM-700A required? Or is the requirement referring to the NATO certified algorithm included in the KIV-700A?

Yes the KGV-135A is an acceptable Type I encryption but it is no longer in production, remaining inventory is limited and it is not available for NGMP production. Amendment 0001 will be issued to remove CCM-700 from Table 1 and paragraph 3.5.4. The ICD and MIL SPECs are available today for KIV-700A implementation and the Government anticipates KIV-700A availability prior to contract award. Since the KIV-700A will be GFE the Government will consider deferring the ISR schedule if modules are not available when expected. The CCM-700A is not required since the coalition/NATO algorithm is embedded in the KIV-700A.

25 Attachment 1 NGMP Government Performance Specification (PS) Administrative In Appendix C, for Waveforms, should there be a comma between "VNW" and

"STD-CDL Rev H"?

Amendment 0001 will be issued amending the PS to add a comma between VNW and STD-CDL.

26 Attachment 1 NGMP Government Performance Specification (PS) Substantive

STD-CDL is listed in PS Appendix C as an Objective waveform. PS Table 1 lists STD-CDL as a Threshold waveform. Please clarify this apparent discrepancy.

The STD-CDL is a threshold waveform. Amendment 0001 will be issued amending Appendix C accordingly.

27 Attachment 1 NGMP Government Performance Specification (PS) Substantive 3.13.5.3 (OTAT, OTAR and OTAZ). Please clarify the intention of OTAZ. It has previously been deleted from other parts of the specification.

The OTAZ is a NGMP Threshold requirement as stated in the PS, paragraph 3.13.5.3.

28 Attachment 1 NGMP Government Performance Specification (PS) Substantive

3.2 (NGMP Configuration Parameters) Do both the Unified Networking Configuration Tool (UNCT) and the Unified Radio Configuration Application (URCA) need to be able to configurable all radio parameters?

No, however as an Objective, "All aspects of the radio configuration are configurable by a single user interface including SRW, MUOS, and WNW (O)."

29 Attachment 1 NGMP Government Performance Specification (PS) Substantive

For 3.2.1.2 ("The only exception to this requirement is waveforms that are currently required to be configured through the use of the Joint Tactical Radio System (JTRS) Enterprise Network Manager (JENM) such as SRW, MUOS, and WNW. These waveforms must have a configuration file output from JENM that is easily importable into the Unified Networking Configuration Tool.

All aspects of the radio configuration are configurable by a single user interface including SRW, MUOS, and WNW (O)."), is the entire paragraph the objective requirement or just the last sentence?

The entire paragraph is a threshold except for the last sentence.

Amendment 0001 will be issued amending Paragraph 3.2.1.2 for clarification purposes.

30 Attachment 1 NGMP Government Performance Specification (PS) Substantive

3.2.1.3 (Unified Networking Configuration Tool)

- With regard to the sentence, “All firmware upgrades shall come from OEM for any feature contained within the radio,” does this mean that any update to a radio feature should also be accompanied by an update to the Unified Networking Configuration Tool?

- With regard to the sentence, “Must have the ability to build a functional mission profile and load it into in any position available for wideband communications,” does “position” refer to preset position? And is this requesting that only that preset waveform configuration is updated and the rest of the radio configuration remains untouched?

No. The paragraph does not mean that, "any update to a radio feature should also be accompanied by an update to the Unified Networking Configuration Tool." Only those firmware updates that require a change to the Unified Networking Configuration Tool are required. The term position refers to a "preset position." Only the preset waveform configuration should be updated and the rest of the radio remains unchanged. However, when cloning, all radio configurations including preset waveform configurations and any additional changes made by the Tool or the operator shall be updated.

31 Attachment 1 NGMP Government Performance Specification (PS) Substantive

For 3.2.2.1 (Networking Architecture) Is this a unified web interface or can this be a single interface? If this is web based does it have to served off of the radio?

A single interface is acceptable.

32 Attachment 1 NGMP Government Performance Specification (PS) Substantive

For 3.2.2.2 (Networking Architecture) With regard to the sentence, “The user interface shall contain a network mapping and monitoring capability similar in nature to SolarWinds,” can more specifics be provided on the monitoring capabilities that are desired? Is the radio providing these capabilities?

The paragraph refers to the user interface of the Unified Radio Configuration Application which would be monitoring network performance parameters and displayed on an end user device. While many of the network parameters are generated by the radio the Unified Radio Configuration Tool provides the monitoring capability.

33 Attachment 1 NGMP Government Performance Specification (PS) Substantive For 3.2.2.2 (Networking Architecture) Bidder believes that this should say "… loadable by USB or Ethernet verses "and"? Please clarify.

Loadable by USB or Ethernet. Amendment 0001 will be issued to clarify paragraph 3.2.2.2.

34 Attachment 1 NGMP Government Performance Specification (PS) Substantive For 3.3.2.2.5 (Networking Architecture) Duplicate requirement number.

Should be labeled 3.3.2.2.6 Amendment 0001 will be issued to correct the PS paragraph numbering.

35 Attachment 1 NGMP Government Performance Specification (PS) Substantive STD-CDL is listed in PS Appendix C as an Objective waveform. PS Table 1 lists STD-CDL as a Threshold waveform. Please clarify this discrepancy.

Amendment 0001 will be issued to delete STD-CDL from Appendix C as an Objective.

36 Attachment 1 NGMP Government Performance Specification (PS) Substantive

3.13.2.1 (Cryptographic Requirements) Please elaborate on what is meant by “compatible with the AKMS/KMI key distribution and net management systems”? Are AKMS and EKMS identical in this regard?

The NGMP shall be compatible with both Electronic Key Management System and the Army Key Management System.

37 Attachment 1 NGMP Government Performance Specification (PS) Administrative 3.9.4.6.1 (Broadband SATCOM) Please mark this paragraph as objective (O) so as be consistent with Appendix C. Amendment 0001 will be issued amending Paragraph 3.9.4.6 accordingly.

38 Attachment 1 NGMP Government Performance Specification (PS) Administrative 3.9.4.6.1 (Broadband SATCOM) Please mark this paragraph as objective (O) so as be consistent with Appendix C. Amendment 0001 will be issued amending Paragraph 3.9.4.6 accordingly.

39 Attachment 1 NGMP Government Performance Specification (PS) Administrative 4.1.2.1.3 (Device Size) The requirement for LMR-400 cabling is missing a

"shall" Amendment 0001 will be issued amending Paragraph 4.1.2.1.3 accordingly.

40 Attachment 1 NGMP Government Performance Specification (PS) Substantive

4.3.2.2 (Interfaces) Bidder suggests that this requirement should allow for backwards compatibility with "other radio antennas identified in the proposal".

This would allow industry to propose the best trade of compatibility with all other possible radios (manpack, handheld, legacy, and modern radios).

Amendment 0001 will be issued amending Paragraph 4.3.2.2 to provide clarification.

41 Attachment 1 NGMP Government Performance Specification (PS) Substantive

4.3.2.3 (Interfaces) antennas. In 3.1.1 the Government expresses the desire for industry to propose optimum antenna combinations that maximize performance and also minimize weight and the number of antennas. In order to accomplish this, bidder suggests that 3:1 VSWR should be allowed for both NB and WB. Otherwise, the Government will cause operators to carry more antenna combinations without achieving improved RF performance range during missions.

The Government understands the trade off and accepts the potential of additional antennas necessary to achieve the stated VSWR requirement.

42 Attachment 1 NGMP Government Performance Specification (PS) Substantive 4.3.3.1 and 4.3.3.3 (Electrical) appear to be conflicting requirements. Please clarify.

Amendment 0001 will be issued amending Paragraphs 4.3.3.1 and 4.3.3.3 for clarification purposes.

43 Attachment 1 NGMP Government Performance Specification (PS) Substantive

Para 3.5.4, 3.5.5, and Table 1: Industry understands that in order to meet new operational requirements, the Government included new and significant changes to the ISR video receive capability from what was previously published in the Draft RFP. These include KIV-700A, CCM-700, 44 Mbps data rates, HUB battery charging while NGMP is turned off, ISR waveform save as a preset from auto detect, ISR analog video encode, and selectively flood data (white list filtering).

Given the significant business and financial impacts from these technical changes, bidder suggests the following alternative which can help the Government best achieve the operational requirement, allow bidders to make better investment tradeoffs, and promote competition in industry. Bidder respectfully requests the Government consider making ISR a Pre-Planned Product Improvement (P3I) with two separate CLINs/ELINs that allow for bidding of both a non-recurring engineering (NRE) effort and a production capability unit price.

The Government has considered making the ISR receive capability a Pre- Planned Product Improvement (P3I). While some technical aspects did change between the draft and final RFP, the Government considers the Thresholds achievable and therefore the requirement remains unchanged in the Final RFP.

44 Attachment 1 NGMP Government Performance Specification (PS) Substantive

Section 3.8.1.1 Table-2 and section 3.8.1.2.1, G.729 vocoder is specified in addition to AMR5.9. Currently TSM-X only supports AMR5.9 (5.9kbps) and MELPe (2.4kbps) vocoder. G.729 vocoder requires 8kbps per voice channel, therefore consumes more wireless bandwidth, especially for 16 voice channels. Does Government intend to require voice to be transmitted over the air in native G.729 vocoder format, or only intend to support G.729 vocoder for interface over the wired interface for purposes such as VOIP integration?

Amendment 0001 will be issued amending Table 2 and paragraph 3.8.1.2.1 such that the G.729 vocoder is removed as a requirement.

DD254

45 Attachment 2 DD254 Administrative SOW 14.0 (Program Security) indicates "Contractor is required to maintain a Secret facility clearance", while DD-254 1.a indicates that a Top Secret facility clearance is required. Please clarify this discrepancy.

Reference response to item number 2

46 Attachment 2 DD254 Administrative

SOW 14.0 (Program Security) indicates "Contractors will not require additional accesses (NATO, FGI, Focal Point, etc.) in performance of this effort", while DD-254 10.g indicates that access to NATO Information is required. Please clarify this discrepancy.

Reference response to item number 2

47 Attachment 5 GFP List Substantive The "Use As Is" column designates "FALSE". This indicates the Government should repair any item not in working condition. Will there be a remedy to repair, or should this be a priced item? Please clarify.

Amendment 0001 will be issued amending Attachment 5 to show "True" for the "Use As Is" column. GFP contained within this attachment will be provided for contractor use in the condition in which the item was provided.

Attachment 3 Price Matrix

Exhibit D CDRLs

Warranty

GFP List

Nameplate Example

MATRIX

File details come from the government source that posted it. Updated .