W51EW726RA004_QandA_FINAL_posted 24Mar2026.xlsx
XLSX spreadsheet 33 KB Posted
- Attached to
- Solicitation US Army Operational Evaluation Command, Base Test Support Services Follow-on
- Solicitation number
- W51EW726RA004
- Issued by
-
Department of the Army
About this file
This is a Questions and Answers document for federal contract solicitation W51EW726RA004, containing 56 industry questions and government responses regarding the Base Test Support Services (BTSS) Follow-on procurement. The document addresses clarifications on proposal submission requirements, evaluation criteria, contract terms, and performance work statement specifications. Key amendments were indicated as pending, including modifications to past performance questionnaire procedures (L.3.2.7), clarifications on Sample Task Order proposal formatting and page limits (L.3.1.3), corrections to labor category instructions in the pricing matrix (L.3.3.4.1.3), PWS revisions regarding TMDE calibration responsibilities (PWS 3.5.2) and sensitive item inventory frequency (PWS 5.2.7.4), and updates to Section L.2.3 volume title nomenclature. The government confirmed that anonymous technical proposals must stand on their own without reference to current contracts or locations, past performance references may come from major subcontractors or teaming partners performing notable workscope, and both up to two past performance references and two major subcontractor entries (potentially from the same entity) are permitted within page limits.
The Q&A document clarifies numerous proposal preparation details, including that organizational charts may use 11x17 format (counting as one page), subcontractors valued under $5M may submit pricing data directly to the government via PIEE to protect proprietary information, and pre-award accounting system reviews or existing CPARS data satisfy accounting system adequacy requirements. The government declined to extend the three-year past performance recency window to five years, revise the major subcontractor definition to include critical hardware/services providers, or provide estimated workload metrics and geographic distribution assumptions, stating that offerors should be capable of developing solutions based on the defined PWS scope. Several responses clarified personnel security clearance requirements, OCONUS-specific provisions, and contract administration details regarding government-furnished property condition, motor pool locations across Fort Hood, Fort Bliss, and Fort Bragg, and eCRAFT reporting requirements.
View the file
Other files
Show all 21
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 | Document Page | Issue / Question | Government Response | Pending Amendment Action? |
| 1 | RFP | L.3.2.7 | We respectfully request that the Government allow Prime Contractors to provide PPQ responses to subcontractor performance. | The Government will amend L.3.2.7 to allow for subcontractor performance on a Government contract provided 2 separate PPQs are submitted for said contract. The first PPQ may be completed by the Government Prime contractor. The second PPQ shall be submitted to the current RFP Contracting Office POCs with Part I completed by the Offeror with the Government Prime contract POC for Government-to-Government coordination and PPQ response. Offerors shall note the evaluation will place a greater weight on the Government response. | Yes | |
| 2 | RFP | L.2.5.1 | 77 | With the submittal of an anonymous Technical proposal where the Government prohibits “any information that indicates the Offeror's (to include all team members) identification”, we highly recommend that the Government allows offerors to reference specific sites/locations they are currently supporting to establish both relevance and context for proposed solutions. For example, if we are performing work at Fort Hood today, can we cite our presence at Fort Hood? Will the Government please provide additional guidance on what is acceptable to include in the volume without creating a compliance issue with the referenced Section L language? | Requiring and subsequently evaluating sanitized proposals is appropriate to ensure the integrity of the source selection process and evaluator objectivity strictly to the contents of each proposal. Proposal information shall stand on its own, and an Offeror should be able to substantiate claims without identifying their entity or making any reference to a prior contract/prior program, to include work currently being conducted at Fort Hood, or any other location applicable to BTSS PWS requirements. That said, Offerors are not restricted from addressing their knowledge of the BTSS (operations, activities, location, etc.) in detailing their solution. RFP remains unchanged. | No |
| 3 | RFP | L.3.2.1 | 81 | The instructions state "...plus five pages for each major subcontractor or, teaming partner entry, with a maximum of two..." Is it acceptable to use 2 entries/references from the same subcontractor as long as total page count of (10) pages for major subcontractor(s) is maintained? | Yes. L.3.2.1 notes there is a maximum of 2 major subcontractor/teaming partner entries and does not specify the maximum of 2 cannot be proposed for the same/a single major subcontractor entity. RFP remains unchanged. | No |
| 4 | RFP | L.3.2.1 | 81 | In the final sentence, it states "...reference to the past performance contracts and their respective PWS paragraph(s) cited for each team member..." We assume that their respective means the BTSS PWS paragraphs that the prime, subcontractor or other teaming partner is expected to perform on BTSS. Is this correct? We want to ensure that the government is not asking for copies of the source contract and its PWS paragraphs. | No. "their respective PWS paragraph(s) cited" refers to the PWS paragraphs of the proposed past performance contract and then, tying that past performance to the associated tasks/PWS paragraphs of the BTSS Follow-on the applicable team member (prime, major sub) is proposing to perform under the BTSS Follow-on effort. RFP remains unchanged. | No |
| 5 | RFP W51EW726RA004_04Mar2026 | L.3.1.2 | Page 80 | Per section L.3.1.2 "A major subcontractor... is defined as a member of an Offeror's overall team whose subcontract is valued at or more than $5M of the total proposed cost." |
Recommend the Government consider defining a major subcontractor whose subcontract is valued at or more than $5M of the total proposed cost or who will be providing critical hardware/services.
| Rationale: This allows an offeror to take a best-of-breed approach in constructing its team by accounting for a relatively small, but important requirement within the areas of expertise. | The Government will not define a major subcontractor further. RFP remains unchanged. | No | |||||
| 6 | RFP W51EW726RA004_04Mar2026 | L.3.2.1, L.3.2.2 | Pages 81 & 82 | The "up to two (2)" past performance contract references allowed from "major subcontractors and / or teaming partners" is unclear. Are only "major" subcontractor teaming partners allowed to submit a past performance contract reference? Or can a teaming partner, with any amount of workshare, submit a past performance contract reference? | The "and / or" does not limit an Offeror to either major subcontractors OR teaming partners. The "up to two" past performance references may be cited from major subcontractor(s), teaming partners, or both. There is no workshare "requirement", however, it is unclear why an Offeror would include a past performance reference from any entity who wasn't performing a level of PWS workscope for evaluation of Relevancy (M.5.3.2.1). RFP remains unchanged. | No | |
| 7 | RFP W51EW726RA004_04Mar2026.pdf, | ||||||
| TE C DD1423_BTSS_03Mar2026.pdf | L.3.1.3, | ||||||
| CDRL A003 | Section L Page 81, | ||||||
| CDRL Page 4 | Section L.3.1.3 instructs offerors to "provide a complete TOP for the Sample Task Order..." |
For the Sample Task Order please confirm whether Offerors are required to submit a standalone, "complete TOP" (i.e., cover letter, full technical approach presentation/slides, and associated attachments) in addition to the written responses required by Section L, or whether responding to the content sub-elements identified in Section L.3.1.3.1 through L.3.1.3.4 (with cross-references indicating where that material would satisfy a CDRL requirement) is sufficient.
If a standalone "complete TOP", please confirm non-page-limited attachment allowances for Volume I. RESPONSE UPDATED FROM 13 MAR 2026 POSTING
Concur that clarification is needed. Pending amendment anticipated to change L.3.1.3 as follows:
| L.3.1.3 Subfactor Three: Sample Test, Sample Task Order Proposal (TOP) The Offeror shall provide a complete TOP in accordance with CDRL A003* and the elements below, for the Sample Task Order as provided at RFP Attachment 2 (A2). TOP Attachments are not subject to page limitations at L.2.3, but are restricted to fifteen (15) total pages, excluding the cover page and cost attachments submitted under Volume III. *Offerors shall note, the TOP proposed at Volume I shall include the job position/labor category and man hours required at CDRL A003 16.4(a), but all proposed costs required under 16.4 shall be included in Volume III, as applicable (i.e., within the Offeror's cost narrative and A4 Pricing Matrix). | Yes | ||||
| 8 | RFP | L.3.1.2.2 | 80 | L.3.1.2.2 states, "Organizational charts may be submitted via 11x17 page format, an exception to the page format specified at L.2.4.2 above. Each 11X17 page counts as one-page toward page limitations at L.2.3." |
| Given that certain graphics and tables may also require additional space for clarity and readability, we respectfully request that the Government consider allowing the use of the 11x17 page format for graphics and tables as well, not solely for organizational charts. | Any graphics and tables shall comply with page format requirements at Section L, as solicited. RFP remains unchanged. | No | |||||
| 9 | Given Facility Clearances are attached to CAGE code, we assume that the Joint Venture or managing partner needs to have the security clearance. Is this correct? | Yes, see PWS 1.6.2. RFP remains unchanged. | No | ||||
| 10 | RFP | L.1.3 and L.2.3 | 74 and 76 | Table under L.1.3 lists Volume I as Technical/Mission Capability. However, the table under L.2.3 lists it just as Technical. Please clarify correct Volume Title. | The correct Volume I Title is "Technical / Mission Capability." L.2.3 will be amended to reflect such. | Yes | |
| 11 | RFP | Section B CLIN 0005, 0006, 0007 | 4 and 5 | Does the government want to see the price build-up of labor and any other associated costs that were used to price the FFP line items? | While not required, Offerors may provide informal cost breakdowns of proposed cost/price of FFP CLINs. RFP remains unchanged. | No | |
| 12 | TE D GFP_as of 03Mar2026 | Requisitioned Tab | Is it possible to add locations to the listing of GFP? | No. GFP locations will be identified after contract award. RFP remains unchanged. | No | ||
| 13 | TE F-IML Listing_03Mar2026.XLSX | Is it possible to add locations to the listing and/or provide definitions for EJ4R and EJ4S? | See response to Q12. EJ4R and EJ4S are locations/naming conventions specified out of the GARMY system. RFP remains unchanged. | No | |||
| 14 | RFP | L.3.3.4.6 | 88 | "The Offeror is to include the fully burdened labor rate (FBLR) for each labor category as proposed by the subcontractor in Column N for all identified subcontract positions in the "Labor Build-up" tabs…....." (G&A, Subcontractor Handling rate, etc.) in Columns R through V and their fee in Column W." Respectfully request clarification on the labor build-up tabs and column delineation and if they are intended to be included within the Prime format? Or are column delineations intended to apply to the Attachment 04_Pricing Matrix? | In reviewing the question, the Government noted clarifications required at L.3.3.4.6 to update/correct Column references (as the referenced Column delineations are indeed tied to A4), and to ensure the Offeror's Cost Narrative clearly specifies the contract-type arrangement for all subcontracts. | Yes | |
| 15 | PWS | 5.2.7.4 | 46 | While this may be a contextual issue, it is clear that Sensitive Item inventories are conducted monthly per CDRL A006 and PWS 1.26. However, PWS 5.2.7.4 states that inventories are conducted quarterly. Will the government please clarify? | Army regulations indicate the timeline for inventories depending on the type of property. Sensitive Items shall be inventoried monthly, consistent with CDRL A006. PWS 5.2.7.4 will be amended to reflect/require the same, monthly inventories. | Yes | |
| 16 | RFP | L.3.3.2 | 84 of 112 | If an offeror timely submitted the request for a pre-award accounting system review described in L.3.3.2 and received confirmation from the contracting officer that no further information is requested at this time, does this satisfy the requirements of L.3.3.2? If not, what information should offerors include in response to L.3.3.2? | The evidence of an adequate accounting system (for purposes of administering a cost-type contract) shall be included in the proposal and referenced within the Cost proposal narrative. The information requested for "pre-proposal submission" at #1-6 of L.3.3.2 applies to potential Offerors who have not had an accounting system review by DCAA (or independent agency) in order to deem their system acceptable/approved. Offerors who have submitted PAS Checklists shall indicate such within the Cost proposal narrative. RFP remains unchanged. | No | |
| 17 | RFP | L.3.3.4.1.3 | 86 of 112 | The instructions state that offerors may insert additional rows for labor categories at the bottom of each section of the Pricing Matrix and use a blue font color to easily differentiate the added labor categories. Can the government clarify whether offerors can also delete any prepopulated labor categories that are not used, or should these remain in the Pricing Matrix with no assigned level of effort? | L.3.3.4.1.3 will be amended to include instructions that any pre-populated labor categories not proposed shall remain in the Pricing Matrix as solicited (or amended, if applicable), with no corresponding effort or costs assigned. | Yes | |
| 18 | Attachment 1 PWS | PWS 1.6.2.1 | 5 of 79 | Can the government confirm that the Informationa Technology Lead does not require a Top Secret clearance and can perform the functions of the position with just a Secret clearance? | Requirement/Clearance Level for the IT Lead is confirmed as specified at PWS 1.6.2.1. RFP remains unchanged. | No | |
| 19 | Attachment 1 PWS | 1.6.2.2 | 5 of 79 | PWS 1.6.2 states all personnel must have at minimum an active T3 clearance. Can the government confirm that the requirement for a T1 described in PWS 1.6.2.2 is not applicable, as all personnel must be cleared to a higher level (T3)? | All personnel hired under this contract who do not require a security clearance must have a Tier 1 (T1). The statement specifies all contract personnel who DO NOT REQUIRE a security clearance. PWS 1.6.2.1 specifies the clearance level required for the PM, LM, SM and IT Lead. RFP remains unchanged. | No | |
| 20 | Attachment 1 PWS | PWS 1.6.3.1 | 6 of 79 | Can the government confirm that references to escorting by host nation personnel applies only to potential performance in a foreign country, and that contract personnel do not require an escort during the course of normal CONUS performance? | Confirmed. Escorts noted in the PWS are applicable solely to OCONUS requirements. RFP remains unchanged. | No | |
| 21 | Attachment 1 PWS | PWS 1.6.3.4(3) | 6 of 79 | Can the government confirm that access to the OEC LAN requires at least an interim clearance (favorable results), and that a clearance that is only initiated (pending) is insufficient to access the OEC LAN? | The statement, "that a clearance that is only initiated (pending) is insufficient to access the OEC LAN" is incorrect. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management. RFP remains unchanged. | No | |
| 22 | Attachment 1 PWS | PWS 3.5.2 | |||||
| PWS 5.2.11 | 33 of 79 | ||||||
| 49 of 79 | PWS 3.5.2 states "The Government will provide calibration and repair services for Government provided TMDE…" As currently written PWS 5.2.11 requires the contractor to only coordinate TMDE calibration that is actually performed by the government. Can the government confirm that the contractor actually performs TMDE calibration up to Level T using the government-provided Calibration Lab referenced in PWS 5.2.11 and that offerors should propose a sufficient level of effort (such as a Metrology Technician) to perform calibration services, not simply coordinate services performed by the government? | PWS 3.5.2 will be amended to state the Government will provide the equipment and that calibration shall be conducted by the Contractor. | Yes | ||||
| 23 | Attachment 1 PWS | PWS 3.6.7 | 34 of 79 | PWS 3.6.7 describes the BTSS contractor's responsibility for grounds maintenance as "incidental." Can the government clarify the expectations for grounds maintenance responsibilities under this contract (i.e. up to 50 feet out from any contractor-occupied facility and fence line), or instead confirm that these services are provided by DPW and the BTSS contractor's responsibilities for grounds maintenance are truly incidental as described in PWS 3.6.7? | DPW does not specify a certain distance for contractor responsibilities and the requirements at PWS 3.6.7 are best defined within DPW's common levels of service. RFP remains unchanged. | No | |
| 24 | Attachment 2 Sample Test SOW | Section 1.1 of the Sample Test SOW lists one FLMNET of 25 days. The Milestones/Deliverables schedule (page 8 of 11) lists FLMNET 1 and 2. Can the government clarify whether there are one or two FLMNET in the Sample Task, and if there are two, update Section 1.1 with details on FLMNET 2 (duration, location, etc.)? | FLMNET is the name of specific training for the specific test event, which occurs at two separate levels, FLMNET 1 and 2. RFP remains unchanged. | No | |||
| 25 | Attachment 2 Sample Test SOW | Bullet #22 (page 6 of 11) states data will be collected by ATC personnel. The Milestones/Deliverables schedule (page 9 of 11) indicates the performance location of Excursion 1 is Aberdeen Proving Ground. Can the government clarify the location of Excursion 1 and whether contractor performance is required at Aberdeen Providing Ground? | Confirmed the location of Excursion/Phase 1 is APG. Yes, the contractor will be on site for this sample test. RFP remains unchanged. | No | |||
| 26 | Technical Exhibit D | ||||||
| Technical Exhibit F | PWS 1.5.6 confirms that the contractor must support base operations requirements at Fort Hood, Fort Bragg, and Fort Bliss. TE D and F do not include locations. Can the government provide locations for all equipment so that offerors can propose a sufficient level of effort to perform base operations functions and support the OEC equipment located at each site? | See response to Q12. RFP remains unchanged. | No | ||||
| 27 | Q&A Posted 3/13/26 | #6 | This answer contradicts Q&A #56 provided on 2/13/26, which confirmed that only teaming partners who meet the definition of major subcontractor can submit a past performance reference. Can the government confirm that past performance will only be considered from major subcontractors? | Response to #6 is accurate and valid for proposal action. That said, and as noted, the Government does not find value in an Offeror including a past performance reference from any entity who wasn't performing a (notable) level of PWS workscope for evaluation of Relevancy (M.5.3.2.1). RFP remains unchanged. | No | ||
| 28 | Q&A Posted 3/13/26 | #7 | CDRL A003 requires the technical approach to be provided in PowerPoint. Can the government clarify how offerors should reconcile this requirement with the standalone, 10 page limit for the Sample TOP? If the government wants PowerPoint slides, what formatting and font requirements apply? Does each slide count as one page? If a cover letter is required, does this count towards the 10 page limit? | The Government finds 15 pages, excluding the cover page and cost attachments (submitted under Volume III), as sufficient to provide a TOP. See updated response to Q7 and pending amendment. | Yes | ||
| 29 | Q&A Posted 3/13/26 | #7 | CDRL A003 requires an estimated cost summary as part of the technical approach. Can the government clarify whether cost information should be included in Volume I, or limited to only Volume III? | See (updated) response to Q7. | Yes | ||
| 30 | Attachment 2 (Sample Test SOW); Attachment 4 (Pricing Matrix) | The Sample Test outlines a 120-day operational test at two separate locations (Fort Stewart, GA and Fort Bragg, NC). However, the Pricing Matrix (Attachment 4) does not appear to provide a specific mechanism or cell to price Travel or Other Direct Costs (ODCs) for the Sample Task. Can the Government confirm if Offerors should include Travel/ODC pricing for the Sample Task, and if so, provide instructions on where this should be captured within Attachment 4? | See (updated) response to Q7. A4 will be amended to include a tab for Offeror's to propose Sample TOP Travel and ODCs (CLIN 0002). |
| Separately, and unrelated to any potential Offeror question submitted, A4 will be amended to correct formula/calculation errors as originally solicited. | Yes | |||||
| 31 | RFP | L.3.2.7 | Section L.3.2.7 requires Past Performance Questionnaires (PPQs) to be completed by Government POCs and submitted directly to the Contracting Office. Would the Government be willing to evaluate existing Contractor Performance Assessment Reporting System (CPARS) data in place of the PPQ, when available, to reduce the administrative burden on our contracting officers, CORs, and other Government POCs? | IAW M.5.3.3, all past performance information will be reviewed to include BOTH PPQs and CPARS information. RFP remains unchanged. | No | |
| 32 | RFP | L.3.3.4.6 and L.2.2.1.1 | Section L.3.3.4.6 requires CPFF subcontracts valued under $5M to submit a separate spreadsheet detailing labor rates, fringe rates, and the basis for the rates. To protect proprietary and sensitive pricing information from the Prime Offeror, can the Government confirm that these lower-tier subcontractors may elect to submit their unredacted pricing data directly to the Government via the PIEE Solicitation Module, consistent with the instructions for major subcontractors (as well as the direct submission instructions provided in Section L.2.2.1.1)? | Confirmed. L.3.3.4.6.1 will be amended to refer subcontractor proposals may elect to submit direct to the Government via PIEE, L.2.2.1.1. | Yes | |
| 33 | RFP | L.3.2 and M.5.3.2 | Will the Government consider amending the Past Performance recency criteria from three (3) years to five (5) years prior to the RFP issuance date? Over the past year, broader Government acquisition shifts and strategic realignments have led to an increased reliance on extending existing contracts rather than executing new recompetes. Consequently, highly relevant operational test support experience across the industrial base has been driven further into the past as opportunities to refresh that experience have been delayed. Extending the recency window to five (5) years would account for these macro-level acquisition trends and allow the Government to evaluate a broader, more competitive pool of highly relevant experience. | The Recency definition, and RFP remains unchanged. | No | |
| 34 | W51EW726RA004_QandA_posted+as+of+13Mar2026 | Question 7 | The new instructions state "…shall provide a complete TOP in accordance with CDRL A003…" Section L.3.3.1 prohibits cost/pricing data to be contained elsewhere in the proposal. Given CDRL A003 includes the cost attachment (section 16.4 - Estimate of Required Resources), we assume that requirement is fulfilled with the Sample TO tab within the Attachment 4 (A4) of Volume III and should not be included in Volume I. Is this correct? | Correct. See (updated) response to Q7. | Yes | |
| 35 | W51EW726RA004_QandA_posted+as+of+13Mar2026 |
RFP Question 4
| L.3.2.1 | // | ||
| 81 | Question #4 response references “PWS paragraphs of the proposed past performance contract.” However, there does not appear to be a requirement to include the file / full text of the proposed past performance. Please clarify whether this information is expected. If it is, kindly consider excluding it from the page count as an attachment to the end of the volume. | No. Offerors are not required to provide full text of the proposed past performance PWS paragraphs. The Government is able to verify via contract access and in coordination with PPQ respondents. RFP remains unchanged. | No |
| 36 | Attachment 1_BTSS PWS_03Mar2026 | PWS 5.5.1, 5.2.12, PRS #9 |
5.2.12.6, PRS #15 37, 49, 67
| 50 and 72 | PWS 5.5.1, 5.2.12, and PRS #9 only discuss Motor Pools at Fort Hood and Fort Bliss, yet PWS 5.2.12.6 and PRS #15 require "Submit an annual vehicle inventory to include Fort Bliss and Fort Bragg per AR 735-5 and DA Pamphlet 710-2." It is unclear where the Fort Bragg vehicles are to be parked, secured and/or maintenance performed since there is no mention of a motor pool at Fort Bragg. Please clarify. | There is no Motorpool on Fort Bragg. The base task order will have all GFP. The maintenance of that equipment will be in accordance with their Property Management System that is approved by the KO. The location of the equipment can/will move as required and dictated by mission requirements and KO approval. Fort Bliss has a small Motorpool that and is maintained by the contractor. RFP remains unchanged. | No | ||||
| 37 | Attachment 1_BTSS PWS_03Mar2026 | PWS 5.2.14 & 5.2.1.2. g | 52 & 40 | PWS 5.2.1.2.g discusses fabrication of signs and PWS 5.2.14 discusses the fabrication of only shipping crates, framing and signs. Is there any other fabrication required as part of the BTSS contract for such items as instrumentation mounting brackets or ay other metal fabrication, machining or welding as is typical in most T&E contracts? Please clarify. | No. There is nothing required for fabrication outside of what is stated in the PWS, as solicited. RFP remains unchanged. | No | |
| 38 | Attachment 1_BTSS PWS_03Mar2026 | PWS 5.2.14 | 52 | Are there any fabrication or machine shop facilities provided as Government Furnished Facilities (GFF)? | No. RFP remains unchanged. | No | |
| 39 | Attachment 1_BTSS PWS_03Mar2026 | PWS 5.1.1 | 37 | PWS 5.1.1 only discusses Base Operations for Motor Pool and Management, IT, Logistics, Faciliteis and Supply (twice in that paragraph) as only being performed at Fort Hood and Fort Bliss. Why is Fort Bragg not included in these Base Services? Please clarify. | The Fort Bragg location provides test support, not base services. RFP remains unchanged. | No | |
| 40 | RFP | L.2.2.1.1 |
L.3.3.4.6 75
| 88 | L.2.2.1.1 seems to require submission of subcontractor sealed package through PIEE. L.3.3.4.6 states submission directly to the government POCs, which references section L.1.4 that suggests submission via email. Please confirm how subcontractor packages should be submitted. | See response to Q32. | Yes | |||
| 41 | RFP | L.6.2 | 90 | Instructions require list of former Government employees involved in the proposal preparation, review, or feedback. As a SDVOSB, we hire a significant number of former military employees from all branches who serve various roles within the proposal process. Our subcontractor also hires former military personnel. Is it possible to provide qualifier(s) such as organization (e.g., MICCs, Ft. Hood, Ft. Bragg) and/or years since separation to make this requirement more manageable? | L.6.2 will be amended as follows: |
| L.6.2 Offerors shall identify any Offeror personnel involved in proposal preparation, review or feedback who are former Government employees (i.e., was a Government employee within five (5) years of this solicitation issue date), citing said personnel's prior Government position(s), role(s), date of departure from Government employment, and confirmation former Government employment was unrelated to prior BTSS contracts or BTSS requirements development in any way. | Yes | ||||||
| 42 | RFP | Section A.4.1 | Pg. 3 of 112 | In order to incorporate Government answers to industry questions, please consider extending the proposal due date by 2 weeks | No extension of the proposal due date will occur. RFP remains unchanged. | No | |
| 43 | RFP | PWS 1.5.4 | Pg. 4 | Are all the worksites working standard 40 hour weeks or are some sites regularly working 9/80’s? If so, please clarify the work hours/schedules for each of the sites. | If the "worksites" are referring to base operations work locations, those personnel maintain Government Facility Office and Operating Facility Operating Hours Monday through Friday, 0730 to 1630, except for US Holidays. RFP remains unchanged. | No | |
| 44 | RFP | PWS Part 4 | Pg. 36 | Will there be a requirement for the contractor to lease GSA Fleet vehicles in the new contract? If so, please provide the list of vehicles by type and quantity. | Possibly. The current fleet of NTV are provided as GFP, which will age out during the course of the Follow-on contract. The Contractor may be required to provide a proposal for GSA support, if/as required by the KO during contract administration actions. RFP remains unchanged. | No | |
| 45 | RFP | Section B | Section B identifies a 5-year ordering period (4 years, 11 months + phase-in), while CLIN 0005 (CDRLs) is listed as a 60-month period—can the Government clarify the exact period of performance alignment across all CLINs? | The period of performance across all CLINs is accurate as solicited within Section B. There are reporting requirements within the 30-day Phase-in and thus, CLIN 0005 accurately has a 60-month period. RFP remains unchanged. | No | ||
| 46 | RFP | Section B | CLIN 0001 (Labor) is CPFF while CLIN 0005 (CDRLs) is Firm Fixed Price—can the Government clarify how CDRL effort is separated from labor under the CPFF CLIN to avoid duplication or overlap? | CDRL requirements are clearly defined and able to be priced via a FFP construct. RFP remains unchanged. | No | ||
| 47 | RFP | Section F | Section F shows differing start dates (e.g., 01 Sep 2026 vs. 01 Oct 2026) across CLINs—can the Government clarify the intended contract start date and sequencing of CLIN execution? | CLIN 0003 and 0004 PoP is in error and will be amended to reflect a start of 01 Oct 2026. All other CLIN start (and end) dates are accurate and will remain unchanged. | Yes | ||
| 48 | RFP | Section F | Is the 30-day Phase-In (CLIN 0007) included within the overall period of performance or in addition to the 5-year ordering period? | The 30-Day Phase-in is included in the 5-year contract term. The Ordering Period for all CLINs is 4 Years, 11 Months, with the exception of CLIN 0005 as there are applicable CDRLs within Phase-in. RFP remains unchanged. | No | ||
| 49 | RFP | Section C | Section C references the PWS in Attachment 1, but key scope drivers (e.g., workload volume, test event frequency) are not clearly quantified; can the Government provide estimated workload metrics to ensure consistent proposal assumptions? | The PWS identifies the scope of work for this IDIQ effort and historical data, while acknowledged isn't a guarantee of future requirements, is provided for Offeror use. The Government cannot define expected distribution of future requirements. Offerors who understand the BTSS scope of requirements should be able to provide a technical solution (and associated cost proposal) to satisfy the Government's requirements. RFP remains unchanged. | No | ||
| 50 | RFP | PWS | The solicitation references diverse support environments (CONUS/OCONUS, test sites, installations), but does not define the expected distribution; can the Government clarify the anticipated geographic breakdown of effort? | The PWS identifies the scope of work for this IDIQ effort and historical data, while acknowledged isn't a guarantee of future requirements, is provided for Offeror use. The Government cannot define expected distribution of future requirements. Offerors who understand the BTSS scope of requirements should be able to provide a technical solution (and associated cost proposal) to satisfy the Government's requirements. RFP remains unchanged. | No | ||
| 51 | RFP | Section B | CLIN 0002 (ODCs) includes a Not-To-Exceed value, but no estimated annual breakout; can the Government clarify whether ODC usage is expected to be evenly distributed or event-driven? | ODC usage is subject to testing requirements throughout the period of performance of the IDIQ contract, however, the NTE values for CLIN 0002 are effectively broken out evenly across the contract term as specified at A4, Pricing Matrix. RFP remains unchanged. | No | ||
| 52 | RFP | Section B | Are there any ceilings or guidance for indirect rates (G&A, material handling) associated with ODCs and CAP, or should offerors assume fully burdened pricing without constraint? | NTEs for CLINs 0002-0004 are established at Section B. IAW RFP instructions (L.3.3.4), Offerors may propose a material handling rate (MHR) and/or G&A for CLIN 0002, which will be capped for the life of the contract. The proposed MHR or G&A itself is at the Offeror's discretion. RFP remains unchanged. | No | ||
| 53 | RFP | The solicitation references Government Furnished Property (GFP) and Facilities (GFF), but no inventory or condition baseline is provided; can the Government furnish a GFP/GFF listing with condition and availability at contract start? | All GFP will be provided in serviceable 10/20 condition with all maintenance services up to date/current. RFP remains unchanged. | No | |||
| 54 | RFP | Section A | Section A requires the use of the eCRAFT (E2) system but does not specify reporting frequency, data granularity, or integration expectations; can the Government clarify these requirements for proposal planning purposes? | Section A introduces the eCRAFT requirement, but details of the requirement are specified at PWS 1.27 with reporting requirement, to include frequency detailed at A021. RFP remains unchanged. | No | ||
| 55 | RFP | Section A | Section A notes formatting inconsistencies in the RFP, can the Government confirm that no evaluation impact will result from interpretation differences caused by formatting anomalies? | The formatting issues within the RFP (blue highlighted text, extra spacing, larger than standard tables) do not impact the substantive content and requirements of the solicitation. There is no "interpretation" to be made within the Section L and M requirements and as such, there is nothing for the Government to confirm. Evaluation of proposals will be IAW Section M, as stated. RFP remains unchanged. | No | ||
| 56 | Attachment 2 | Attachment 2 – Sample Test is missing from the final RFP documents. Can the Government provide the final Attachment 2? | Offeror question is unclear. The Contracting team has confirmed Attachment 2, which is the Sample Test (SOW) document was uploaded to both PIEE and sam.gov, Contracting Opportunities for W51EW726RA004 at the time of RFP issuance, 04 Mar 2026. RFP remains unchanged. | No |
File details come from the government source that posted it. Updated .