W51EW725RA001_QandA_27Mar2025_Posted.xlsx
XLSX spreadsheet 19 KB Posted
- Solicitation number
- W51EW725RA001
- Issued by
-
Department of the Army
About this file
This document is a Questions and Answers (Q&A) spreadsheet for the West Desert Test Center (WDTC) Mission Support Services (MSS) Follow On Solicitation W51EW725RA001. The Q&A addresses key proposal submission details, including an increase in the technical volume page limit from 50 to 60 pages to accommodate new scenario-based requirements. The document reveals that the solicitation now includes two specific scenarios for offerors to address, which were incorporated based on industry feedback from site visits and pre-proposal conferences.
The Q&A clarifies several technical proposal requirements, including past performance documentation, letters of commitment, and property management plan submission. Notable clarifications include defining "level of support" as designated workshare or estimated portion of contract cost for team members, and confirming that the Property Management Plan must be submitted with the initial proposal. The solicitation is issued by the Department of the Army and seeks a mission support services contract with detailed technical and scenario-based response requirements.
View the file
Other files
Show all 34
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
RFP Q&A
| # | Source Document | Section and Paragraph(s) Numbers | Issue / Question | Government Response | Pending Amendment Action? |
| 1 | Solicitation | L.3.1.2.1.1 | We have been working a proposal response based on the Draft RFP and feel that 50 pages for Volume 1 Technical was tight, but workable; however, the new requirements to address two Scenarios, will make meeting the 50-page limit much more difficult. Would the Government please consider adding more page count to address the new scenarios? | The Government concurs to increase the page limitations for Volume I from 50 pages to 60 page. Amendment to L.2.3 pending. | Yes |
| 2 | Solicitation | L.3.1.2.1.1, Attachments 7 and 8 | The Section L requirements for the two scenarios are very similar to the Section L language that addresses the overall contract performance, including topics such as oversight & control, alignment, communication, improvements, and innovation. Many of these management practices that apply across the entire contract are still very relevant to how you would manage each scenario – resulting in redundant narrative in the proposal. It appears that Attachments 7 and 8 do not add any additional instructions to be addressed but serve more as reference documents for each scenario. Would the Government please confirm the areas of Attachments 7 and 8 that should be covered within L or that the L requirements are sufficient? If the L requirements are the elements offerors should focus on for each scenario, we assume it is acceptable for offerors to address both scenarios in a combined fashion? | The two scenarios were incorporated in response to feedback gathered from Site Visit and Pre-Proposal Conference questions from industry. The purpose is to give offerors an opportunity to outline their approach (as specified at L.3.1.2.1.1) to potential CWO requirements under the pending contract, more specific to the broad support described under the IDIQ requirement. While a response may include elements that are redundant to the overarching MSS contract support, instructions at L.3.1.2.1.1 are for specific address of the CWO requirements identified within Attachments 7 and 8. The Government will not instruct Offerors as to their individual approach to meeting requirements (at L.3.1.2.1.1). RFP remains unchanged. | No |
| 3 | Solicitation | L.3.1.2.1.1, Attachments 7 and 8 | Based on Answers to Questions during the draft RFP phase, the scenario-based approach was to assist in leveling the playing field with staffing and pricing the work. Since Section L and M requirements for Technical do not require information outside of what was already being required, we assume these scenarios are more of a staffing and pricing exercise to assist the Government in evaluating offeror’s staffing and pricing approaches. Is that a correct assumption? | See response to #2 above. |
| The Government will evaluate the proposals applicable to Attachment 7 & 8 in accordance with the associated Section L instructions and Section M evaluation criteria. | No | |||||
| 4 | Solicitation | L.3.2.1 | L.3.2.1 states “The summary shall also include a reference to the past performance contracts and their respective PWS cited for each team member and the associated tasks from the WDTC MSS PWS represented by each cited contract and its PWS.” Can the Government provide more specifics on what offerors must include in the Summary? Are we to include the entire PWS for each cited contract or a summary of the cited PWS’ paragraphs that are associated with WDTC MSS? | Offerors shall provide summary data, in whatever form they choose, that identifies the cited contracts' PWS scope/tasks/elements and the associated relevancy to the tasks as specified in the WDTC MSS PWS. RFP remains unchanged. | No | |
| 5 | Solicitation | L.3.2.2.1 | L.3.2.2.1 states “In addition, letters of commitment shall be included for all JV partners, major subcontractors, and / or teaming partners cited in order for past performance to be considered, with letters also identifying the specific work scope to be performed and level of support the entity is committing to offer for MSS and WDTC mission success.” Can the Government please define “level of support” in this context? Is it the designated workshare included in our executed Teaming Agreements? | Yes. "Level of support" is defined as designated workshare or the estimated portion of contract cost the team member (e.g., prime, JV entity, and/or subcontractor) is proposed to support. Amendment to L.3.2.2.1 pending to include this definition/clarity. | Yes | |
| 6 | Solicitation, |
CDRLs, and PWS L.4.3
CDRL A012
| PWS 3.1.1 | L.4.3 instructs bidders to submit a Property Management Plan with the proposal, however, PWS 3.1.1 and CDRL A012 states that the PMP shall be submitted 30 days after contract award. Please clarify when the PMP is due. | The Property Management Plan (PMP) is required at proposal submission per L.4.3. As specified at L.4.3, submission of the PMP in accordance with FAR 52.245-1 (specifically, FAR 52.245-1(f)), is part of the Contracting Officer's responsibility determination for the apparent contract awardee. PWS 3.1.1 (and CDRL A012) require the PMP submission within 30 days of contract award for subsequent sufficiency review by both the Government Property Administrator and the Contracting Officer. RFP remains unchanged. | No | |||
| 7 | Solicitation | L.2.3 | Will the Government please consider increasing the overall Volume I page limit to 60 pages to accommodate additional requirements in the Final RFP that were not previously in the Draft RFP? | See response to Question #1 above. | Yes |
File details come from the government source that posted it. Updated .