The file's text, extracted by GovTribe without its formatting.
Question Number
| Document/Section |
| Paragraph Number |
| Question/Issue/Concern |
| Answer |
| 1 |
| PSPEC / Section 3 |
| 3.19.21 |
| Requirement 3.19.21 states the vehicular power amplifier shall provide RF power amplification at a minimum of 20W PEP for frequencies above 90 MHz. We infer this means that power amplification of the MCHH radio is required in the VIK to a minimum of 20W PEP over the full frequency range of the MCHH up to 2.5Ghz. Please confirm and reword to specify the need for RF power amplification at a minimum of 20W PEP over the full frequency range of the MCHH. |
| Yes, power amplification of the MCHH radio is required in the VIK to a minimum of 20W PEP over the full frequency of the MCHH radio, except for the frequency requirement as stated in 3.19.20. |
| 2 |
| PSPEC / Section 3 |
| 3.13.1, 3.7.2, 3.19.21 |
| Due to cable loss and vehicular interconnects in a vehicular configuration, 2W RF output power per requirement 3.7.2 doesn’t appear to support USMC system requirement 3.13.1 in a vehicular configuration. We infer this means that power amplification of the MCHH radio is required in the VIK for the wideband channel. Please confirm and clarify to state the wideband channel requires amplification in the vehicular configuration. |
| Power amplification is required across the full frequency range on all channels of the MCHH in the vehicular configuration. |
| 3 |
| PSPEC / Section 3 |
| 3.23.1, 3.23.2, 3.23.3 |
| Please provide the specific version of WREN that is required, corresponding to the specifications in 3.23.1-3.23.3. |
| WREN version 1.0.0 located in the DoD Information Repository, is the required version. Any change from that version, if required during contract performance, will be addressed through the Waveform Compliance process. |
| Request a 2 week extension to the current proposal due date so that we have adequate time to prepare a comprehensive, quality proposal for the Government. With this extension, the new submission date would be November 1, 2021 @ 10 AM EST. |
| The Government has extended the proposal due date from 18 October to 22 October. |
| 5 |
| Pre-Solicitation and Solicitation |
In a previous pre-solicitation document titled MCHH+QandAs+from+Industry+Day_clean released on 18 August 2021, the Government’s response to Question 5 stated that the SOW will require the contractor to incorporate into existing radios, and deliver on new radios WREN TSM once the technology matures in accordance with the vendor’s proposed waveform roadmap.
Please confirm that offerors who do not have WREN TSM available as part of their base offering at the start of the contract will be required to upgrade radios previously delivered with these capabilities.
The Government confirms that WREN TSM will be required on all radios to include those, if applicable, previously delivered.
| 6 |
| Pre-Solicitation and Solicitation |
Section C
| L.2.8.2 |
| L.2.8.2 states that offerors who do not propose a solution that meets P-Spec Objectives described in 3.23.1, 3.23.2 and 3.23.3 at the time of proposal may propose a price for X022 in the same ordering period in which the offeror proposes a price for CLIN X023, WREN TSM ECP, and in all ordering periods to follow. |
If offerors are required to retroactively upgrade radios previously delivered but are not required to include the price of upgrading radios in prior periods, the “total evaluated price” calculated in accordance with M.5 would reflect an artificially low price. In addition, offerors who offer this objective capability on the first units shipped at the start of the contract would be significantly disadvantaged on total evaluated price. In order to evaluate all offerors on a fair and equal basis, please clarify how an Offeror should reflect the price to upgrade radios delivered in previous periods with WREN TSM.
If an offeror plans to price and deliver WREN through an ECP, they shall also provide pricing to update all radios previously delivered via CLIN X022, WREN TSM Upgrade. Language in L.2.8.2 amended.
Section C Statement of Work
| 3.13.2 |
| Section 3.13.2 states that Maintenance Manuals (CDRL E002) shall include no nonconforming, proprietary, or other marking that suggests the Government has other than unlimited rights to the deliverable. Maintenance manuals include detailed manufacturing and process data that Contractors are entitled to protect in accordance with DFAR 252.227-7013. The Offeror requests that the Government remove the requirement to provide unlimited rights to this technical data. |
| The Maintenance Manuals will be used specifically for maintenance purposes. Per the clause cited, “[t]he Government shall have unlimited rights in technical data that are—(v) necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data).” Detailed manufacturing or process data is defined as “technical data that describe the steps, sequences, and conditions of manufacturing, processing or assembly used by the manufacturer to produce an item or component or to perform a process.” The inclusion of detailed manufacturing and process data is not necessary to fulfill the purpose of enabling Marines to conduct maintenance using a manual on the MCHH in an operational context. |
Section C Statement of Work
| 3.14.3 |
| Section 3.14.3 requires that MCHH Maintenance Training materials (CDRL F001) shall include no nonconforming, proprietary, or other marking that suggests the Government has other than unlimited rights to the deliverable. Maintenance Training materials include detailed manufacturing and process data that Contractors are entitled to protect in accordance with DFAR 252.227-7013. The offeror requests that the Government remove the requirement to provide unlimited rights to this technical data. |
| The Maintenance Training materials will be used specifically for training Marines to perform maintenance. Per the clause cited, “[t]he Government shall have unlimited rights in technical data that are—(v) necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data).” Detailed manufacturing or process data is defined as “technical data that describe the steps, sequences, and conditions of manufacturing, processing or assembly used by the manufacturer to produce an item or component or to perform a process.” The inclusion of detailed manufacturing and process data is not necessary to fulfill the purpose of training Marines to perform maintenance on the MCHH. |
Section I Representations 52.204-26, 52.219-28, 52.223-22 and 52.225-18
| Section I includes representations 52.204-26, 52.219-28, 52.223-22 and 52.225-18. Should these representations be included with Section K in Volume I, Executive Summary? |
| Yes, all but 52.219-28 will be moved to Section K, as they are provisions. |
Section L & Attachment 4
| L.2.1, L.2.7.2 & L.2.7.3 |
| Section L.2.1 states that the Offeror shall omit all cost/price or past performance information from Volumes I-IV and VI. However, L.2.7.2 requires contractors to include in Volume VI small business subcontracting information associated with each project included in the past performance volume. In addition, Section L.2.7.3 and Attachment 4 require the offeror to include the total value of the proposal and break out the estimated value of self-performed work and subcontracted work. Please confirm that the Offeror can include cost/price and past performance information in Volume VI. |
| Yes, the offeror can include cost/price and past performance information in Volume VI. Amendment 0001 has updated Section L.2.1 to remove Volume VI from the list of volumes where cost/price or past performance information shall be omitted. |
Section L
| L.2.8.2 |
| L.2.8.2 states that Offerors proposing a solution that meets P-Spec Objectives described in 3.23.1, 3.23.2 and 3.23.3 at the time of proposal shall propose a price for CLIN X022, WREN TSMTM for all ordering periods. The offeror intends to include the price of WREN TSM as part of its base radio offering CLINs 001 and CLIN 002 in order to be compliant with the SOW and P-Spec. Please confirm that if WREN TSM is included in the price of the radio, CLIN X022 can be marked NSP. Also, to be fair and equitable between offerors, please confirm that the Government will choose TEP equitable quantities between offerors for CLINs 001, 002, and 022. |
| Section L.2.8.2 has been updated. |
If the offeror proposes a solution that includes WREN TSM, the offeror shall include the price of WREN TSM in the price of the radio in CLIN X001 and the offeror shall insert a price of $0 for CLIN X022, WREN TSM Upgrade and CLIN X023 WREN TSM ECP.
The pre-selected quantities for all CLINs will be the same across all offerors.
P-Spec
| 3.19.21 |
| “Vehicular Power Amplifier (20W). The MCHH vehicular power amplifier shall provide RF power amplification at a minimum of 20W PEP for frequencies above 90 MHz.” |
Please confirm that 3.19.21 applies to both NB channel and WB channel amplifiers for frequency coverage above 90 MHz as applicable.
Power amplification is required across the full frequency range on all channels of the MCHH in the vehicular configuration.
P-Spec Compliance Matrix_Final
| Instructions for Completion of P-Spec Compliance (Page 25) |
| Although “Instructions for Completion of P-Spec Compliance” on page 25 includes instructions for Column G- Comments, Column G has been removed from the table. Where should clarifying information be included in the proposal to assist the Government in assessing test data compliance to the specifications since Section 3.2 is limited to 15 pages and only key requirements? |
| The updated PSPEC Compliance Matrix is a MS Word Document and there are no columns or column letters assigned. Instructions on page 25 will be corrected. Clarifying information should be included in Volume III, Technical proposal. |
P-Spec
Solicitation Section C.
Statement of Work Section 4
Sections 3.4.2 and 3.9
| P-Spec Section 4 includes detailed functional verification methods and requirements not included in the SOW Section 3.9. Currently, the SOW only defines Human System Integration, Electromagnetic Interference/ Compatibility, Bonding and Shielding, and Electromagnetic Radiation Hazards. Would the Government please add First Article Test requirements to the SOW to match all of the verification requirements defined in the P-spec Section 4? |
| The Government will be able to verify that most PSPEC requirements are met during source selection by examining the included test reports. The four CDRLs required under SOW 3.9 will be used, post-award, to verify specific requirements that cannot be verified during source selection.” |
P-Spec
| 3.7.3 |
| “The MCHH shall provide no less than three levels (Low, Medium, High) of user selectable RF output power across all modulations and waveforms unless explicitly disallowed by waveform design.” |
Please confirm that:
1) The following level definition is acceptable for the handheld radio (dismounted) Narrowband Channel solution:
· LOW = 1W
· MEDIUM = 3W
· HIGH = 5W
2) Power Levels for the dismounted WB Channel are defined by the specific TSM preset configuration.
While the stated solution appears to be one that would meet the requirements, it is not the only interpretation or acceptable solution.
| 16 |
| CDRLs / A021 |
| 16. Remarks, BLK 12-13 |
| Question: Offeror understands the requirement to submit the Waveform Compliance Roadmap in section 4.4 of the proposal submission. Conflicting instructions are contained in the CDRL Delivery instructions, therefore will the Government remove the statement "Initial submission shall be delivered during pre-award" in the DD-1423 form? |
| The Government concurs and language will be removed from the CDRL. |
| 17 |
| RFP / Section C |
| 3.2.1.2 |
| Question: What is the duration of the expected PSPEC compliance test cycle for the 100 units shipped within 30 days of contract award? This information will assist vendors in detailing our performance plan in proposal submission. |
| The post-award testing will be used to validate PSPEC compliance for those requirements that could not be satisfactorily validated during source selection, using the test data submitted as part of the proposal. As such, the Government cannot prospectively predict the duration of testing that will be necessary. The Production and Delivery Schedule required by L.2.5.5 should be based on the offeror’s production and delivery capabilities, without respect to the duration of any compliance testing under SOW 3.2.1.2. |
| 18 |
| RFP / Section C |
| 3.2.1.2 |
| Question: In order to plan for up to 4000 radios a month and to complete the proposal submission Integrated Master Schedule, will the Government provide notional quantity information for CLIN X001 [MCHH] and CLIN X017 [MCHH Vehicle Integration Kit]? This information is necessary to set up supply chain relationships that would consequently benefit Industry and the Government. |
| The notional quantity for CLIN X001 is ~ 14,000 and for CLIN X017 is ~ 12,000. However, the Government retains the right to order quantities up to the maximum quantity stated in any CLIN. |
| 19 |
| RFP / Sections B and E |
| Section B CLINs and Section E |
| Question: Will the Government update the Inspection and Acceptance point to Source by local DCMA QAR? This allows for not only streamlined shipments but also greater flexibility for the US Government. In addition, it enables assets to be set aside as ship-in-place and ready for deployment when needed. |
| No, the Government does not wish to incur storage costs at the contractor facility. Inspection and Acceptance is at destination by Government. |
| 20 |
| RFP / Sections B and C |
| Section B CLINs 0020, 1020, and 2020 and Section C Paragraph 3.11.3 |
| Question: Will the Government please provide the appropriate SOW reference for CLINs X020 as they incorrectly reference Section 3.11.3, Provisioning Data which are CDRLS as opposed to orderable and pre-defined parts? |
Offerors are not required to price the Provisioned Items at the time of proposal. This CLIN will be negotiated post-award after receiving CDRLs IAW SOW Section 3.11.3. The CLIN description has been updated to read:
“Provisioned Items Ordering. Additional interoperable and interchangeable related ancillary parts to support MCHH based on the CDRLs provided IAW MCHH SOW paragraph 3.11.3”
| 21 |
| RFP / Sections B and C |
| Section B CLINs 0020, 1020, and 2020 and Section C Paragraph 3.11.3 |
| Question: Will the US Government clarify specifically what items should be included in the price of these CLINs or update to indicate it is "undefined" and will be removed from the pricing requirement? |
| See answer above. Solicitation will be amended to remove all X020 CLINs from the pricing workbook. |
| 22 |
| RFP / Section I |
| Full Text Clauses |
| Question: Please confirm if the submissions required in accordance with Section I of the solicitation should be included with the Section K submission? |
| Submissions required in Section I have been moved to Section K. All full text provisions that require contractor response are now solely in Section K and should be submitted along with material responsive to Section K. |
| 23 |
| RFP / Section M |
| M.5 Factor 2 |
| Concern: The Factor 2 Cost/Price evaluation approach is ambiguous. Section M references an "undisclosed, predetermined evaluation quantity for each CLIN". By failing to identify the product mix and quantities to be evaluated for each CLIN, specifically CLIN X001 and X017, offerors will be forced to speculate as to the agency’s minimum needs, resulting in competing proposals that do not price like to like quantities and therefore cannot be reasonably or consistently evaluated and compared. Please provide the evaluation product mix and quantities to be utilized such that offerors are able to submit proposals responsive to the requirements. |
| The Cost/Price evaluation approach is unambiguous. Because the Government does not have insight into offeror pricing, it has chosen not to dictate the price quantity discount ranges; instead, it invites offerors to propose price discounts if and where they occur for the offeror. The Government is using the same quantities to evaluate each offeror. The Indefinite Delivery Indefinite Quantity contract type is used precisely because the timing of Government orders cannot be accurately predicted. An offeror need not speculate as to the Government’s needs in order to identify where it will provide a quantity discount. |
| 24 |
| Pricing Workbook |
| General |
| Question: Will the USMC provide defined quantity ranges in the pricing workbook to ensure vendors are utilizing similar structures for consistent and fair evaluation. |
| The Government will not be defining quantity ranges in the pricing workbook. In order to evaluate price, the Government will set an undisclosed, predetermined evaluation quantity for each CLIN. This undisclosed, predetermined quantity will be uniformly applied to all offerors. Please see Section M.5 for further details. |
| 25 |
| RFP / Section L |
| L.2.2.2.1 |
| Question: This section specifies all elements of the SOW Cross Reference Matrix must be discussed in Volume III, Section 3, however the Waveform Compliance Roadmap is specified as part of Volume IV. Will the Government please adjust to reflect the cross-references may be to Volume III and/or Volume IV. |
| Section 3.5.3.2 has been removed from the SOW Cross Reference Matrix. The Waveform Compliance Roadmap shall be provided as part of Volume IV. |
| 26 |
| RFP / Section L |
| L.2.5.4 |
| Question: Reference L.2.5.4, will the Government please confirm all bidders are required to propose and price WREN-TSM [CLIN X022], as it is an objective requirement? |
| Offerors are not required to propose a price for CLIN X022 if the offerors propose a solution that includes WREN-TSM as a feature on CLIN X001. Offerors who do not propose a solution that meets PSPEC Objectives described in 3.23.1, 3.23.2, and 3.23.3 at the time of proposal shall propose a price for CLIN X023, WREN TSM ECP to incorporate WREN TSM as an ECP in the ordering period in which the offeror is capable of incorporating PSPEC Objectives described in 3.23.1, 3.23.2 and 3.23.3 into their solution. Additionally, offerors |
who do not propose a solution that meets PSPEC Objectives described in 3.23.1, 3.23.2, and 3.23.3 at the time of proposal shall propose a price for CLIN X022, WREN TSM Upgrade to upgrade all previously delivered radios in the same ordering period in which they propose CLIN X023, WREN TSM ECP and each ordering period thereafter.
| 27 |
| RFP / Section L and Pricing Workbook |
| L.2.8.2 |
| Question: To promote full and open competition and preclude a non-government entity from strongly influencing the outcome of the procurement process through preferential licensing and pricing practices, will the Government provide the WREN-TSM licenses as Government Furnished Equipment (GFE)? |
| No, the WREN-TSM licenses are expected to be included as part of the pricing provided in the proposals. |
| 28 |
| RFP / Section L |
| L.2.8.2 |
| Question: If the Government is unwilling to furnish the WREN TSM license as GFE, please describe how the Government will ensure that a non-governmental entity will not strongly influence the source selection process through preferential licensing and pricing practices contrary to full and open competition. For example, if vendor X is charged $3,000 WREN TSM License fee (exclusive of hardware costs), what methodology in the Government's TEP evaluation is there to confirm that vendor Y will be charged the $3,000 for the same WREN TSM License fee? |
| The Government cannot insert itself in agreements with subcontractors. |
| 29 |
| PSPEC / Section 3 |
| 3.1 |
| Concern: Please remove WREN-NB as an Objective requirement. WREN-NB is an early and evolving demonstration capability and has not been proven as mature or field ready. It lacks clarification to be able to assess porting and license costs, the process for bug fixes, performance guarantees, configuration control, lacks IR completeness, therefore WREN-NB should be removed as an Objective requirement to ensure full and open competition among vendors. |
| WREN-NB will remain as an objective requirement. |
| 30 |
| Justification and Approval |
| Various |
| Concern: Consistent with the 2020 NDAA Section 168 language, the WREN-TSM waveform would be placed into the Department of Defense Waveform Information Repository (IR), with all required documentation and guidelines associated with that task, or if defined as a COTS waveform, complete and full analysis through the JTNC Tactical Communications Marketplace. Specific to WREN-TSM, please provide a detailed listing of the Technical Data, source code, and documentation that are in the JTNC Information Repository and confirm it is complete or provide details regarding what remains to be delivered. |
| The source code and documentation for the relevant WREN-TSM version (as noted above) are located in the DOD Information Repository (IR). |
| 31 |
| Justification and Approval |
| Various |
| Question: Are the references to "DOD Certification" in the Justification and Approval documents referring to standardized JITC Certification requirements? If not, please define "DOD Certification". |
| The DOD certification referenced in the J&A is referring to the Command, Control, Communication, Computers, Cyber, Intelligence, Surveillance and Reconnaissance (C5ISR) Waveform Conformance and Interoperability Assessment. |
| 32 |
| Justification and Approval |
| Various |
| Question: For the purpose interoperability, for WREN-TSM, who will be the configuration control authority of the waveform to ensure interoperability and consistency, as historically this has been JITC’s charter. |
| C5ISR is the configuration control authority for the WREN waveform. |
| 33 |
| PSPEC / Section 4 |
| 4.23.1 |
| Question: For the purpose of proposing to the requirement in PSPEC 4.23.1, please provide the interoperability test plan referenced for WREN-TSM. |
| The interoperability test plan will be provided by C5ISR. The Marine Corps intends to accept test results from C5ISR for WREN waveform conformance and interoperability and will not separately test. |
United States Marine Corps