Attachment 04- Government Response to Questions A0001.xlsx
XLSX spreadsheet 83 KB Posted
- Attached to
- TRANSPORTATION_SUPPORT_FOR_TEXAS Federal contract opportunity
- Solicitation number
- 70CDCR26R00000021
- Issued by
- Immigration and Customs Enforcement
About this file
This file is a government Q&A response document addressing offeror questions regarding ICE's Request for Proposal (RFP) 70CDCR26R00000021 for statewide armed ground transportation, centralized dispatch operations, and a secure web portal supporting the 287(g) Program in Texas.
Scope and Services: The contract requires 24/7/365 transportation services covering all 254 Texas counties with a 30-minute statewide monthly average response time requirement. High-traffic areas (Dallas-Fort Worth, San Antonio, Houston) must be operational within 60 days of contract award; all other counties within 120 days. Services include pickup of detainees from state and local law enforcement agencies, transport to ICE facilities, and delivery to designated locations. The contractor must establish a centralized dispatch center (National Coordination Center) in the Nashville, Tennessee area and develop a stand-alone secure web portal for operations reporting and G-391 processing. Vehicle requirements specify vans or large SUVs with secure capacity for minimum four detainees, no more than five years old.
Pricing and Performance Terms: This is a firm-fixed-price (FFP) contract with 255 Contract Line Item Numbers—one monthly FFP for each of the 254 Texas counties plus a separate statewide monthly FFP for centralized dispatch services (CLIN 0255). All costs including mileage, fuel, vehicle maintenance, staffing, training, equipment, and transition activities must be embedded within the fixed monthly county prices regardless of actual transport volume. A separate transition CLIN covers the initial 120-day mobilization period. Pricing must align with Department of Labor prevailing wage determinations for the Detention Officer classification by county, with potential economic price adjustments under FAR 52.222-43 when wage determinations are updated. The base period is 12 months with a three-year option period. Personnel must maintain 100 percent staffing levels with vacancies filled within 30 calendar days, undergo ICE suitability determinations, and complete 40 hours of initial training plus 16 hours annual retraining (not including firearms qualification). The contract requires armed personnel with Texas Level III Commissioned Armed Security Officer licenses, current CPR/First Aid certification, and compliance with National Detention Standards 2026. No separate surge, overtime, or mileage CLINs will be established; all surge capacity must be absorbed within the fixed monthly prices. The contractor bears all costs for licenses, certifications, equipment, facility staging, vehicle acquisition and maintenance, dispatch operations, secure portal development, and personnel recruitment and training.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 2.2.1- 70CDCR26R00000021 A0003.pdf | ||
| A0002 70CDCR26R00000021.pdf | ||
| 2.2.1- Attachment 02- Pricing Template A0002.xlsx | XLSX spreadsheet | |
| 2.1.1-Attachment 05– G-391 Upload Template.xlsx | XLSX spreadsheet | |
| 2.2.1- Attachment 02- Pricing Template A0001.xlsx | XLSX spreadsheet | |
| 2.2.1- Attachment 01-PWS A0001.pdf | ||
| 2.1.1-Attachment 06– ICE Firearms Policy.pdf | ||
| A0001 70CDCR26R00000021.pdf | ||
| 2.2.1- Attachment 01-PWS.pdf | ||
| 2.2.1- 70CDCR26R00000021.pdf | ||
| 2.2.1- Attachment 04- Solicitation Question Template (1).xlsx | XLSX spreadsheet | |
| 2.2.1- Attachment 03- Consolidated Wage Determinations (1).xlsx | XLSX spreadsheet | |
| 2.2.1- Attachment 02- Pricing Template (1).xlsx | XLSX spreadsheet |
Show all 13
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Attachment 4- Solicitation Question Template | |||
| RFP Attachment | RFP Section/Page/Paragraph | Question | Response |
| RFP | L.3.2 | Due date for the written proposal elements is 8/10/26, however, there is is no listed due date for Volume III pricing. What is the due date for Volume III? | Pricing is included in the timeline for "Written Proposal Elements". |
| RFP | 2.0 | Can ICE provide a description of a "typical" service order? (e.g., phone call, G-391, etc.) | Anticipate phone calls into the NCC which are then forwarded to the contractor's dispatch team to arrange for transport. A G-391 or similar paperwork is transmitted to dispatch team for signatures from agency at pickup and signature from ICE at delivery. |
| 2.0 | Will all service calls come from the National Coordination Center and no other source? | For efficiency, all calls should come in through NCC. | |
| RFP | 2.0 | Will the contractor be conducting any detainee pickups " (direct turnover from state LEO's) on the road" (i.e., a traffic stop location) from state authorities? | Yes, there will be direct turnover from state and local agencies. |
| RFP | 2.0 | Without being deputized, and if direct turnover is required at other than a jail (under 287-g) or a federal facility, under what laws and specific conditions can the contractor legally assume custody? | ICE does not see any legal restrictions for transport. |
| RFP | 2.0 | Can ICE provide a description of a "typical" service order method? (e.g., phone call, G-391, etc.) | Typical service phone call is expected at NCC, where contract dispatch is co-located. Phone call will provide most required information. Any other information needed can be obtained from ICE personnel at the NCC or ICE personnel at the local ERO field offices in TX. |
| RFP | 2.0 | Are there specific locations within each county that must be staffed daily regardless of traffic, such as all county jails? | No. Staffing is model and locations of staffing is up to vendor. |
| RFP | 2.03 | If appropriations lapse, is the contractor guaranteed payment by the Government once appropriations are reinstated? | This contract will be Firm-Fixed-Price (FFP) and funded accordingly. |
| RFP | 2.04 | Is the contractror in any way liable for accepting custody of detainee that may be inadvertently turned over to us (i.e., an erroneous arrest)? | G-391 or similar paperwork ensures vendor is only transporting those arrested and being turned over to ICE. |
| RFP | 2.05 | How will this contract interact with the SNA AOR transportation contract with respect to intra facility transfers that fall within the SNA AOR contract? | This contract was not designed with interation in mind with other transportation contracts, although there is a realization that interaction is entirely possible. |
| RFP | 2.06 | Are the 3 metro areas listed as within 30 days DFW, SNA, and HOU the highest traffic areas of this contract? | Yes. PWS updated to reflect 60 days for the high traffic areas. |
| RFP | 2.07 | Is the contractor to presume that any service expansion would result in additional funding via an REA? | Changes in contract requirements would be completed via contract modification, not via REA. |
| RFP | 2.2.3 | Is the NCC currently activated? | No. |
| RFP | 2.2.3 | If the NCC is not operational by the contract start date, will the contractor be allowed a price adjustment to establish this function in Texas? | NCC is on schedule to be operational prior to contract start date. |
| Attachment 2/PWS | 2.2.3 | Dispatch Services. Is a separate CLIN going to be established for this or are to charge a specific county for this service or prorate the cost to all counties? | Yes, a standalone monthly FFP CLIN was established. See CLIN 0255 in the Pricing Attachment for "Centralized Dispatch Services" |
| PWS | 4.0.1.5 | What is the purpose (i.e., legal rationale) for the 30 minute response time? | 30 minutes is an operational requirement, not a legal requirement. |
| PWS | 4.0.1.5 | Can ICE provide any historical data (per county) as to number of service calls in the past 12 months? | There is no historic data regarding transport requests for 287(g) arrests from state and local law enforcement agencies. This contract is unique in this regard. |
| PWS | General | Is there a current contractor providing these services with incumbent employees that may be eligible for hire? | No, there is no incumbent contractor. This is a new requirement. |
| PWS | General | If the contractor's staffing plan calls for "static" staffing (i.e., a minimum number of staff on duty each 24 hour period in each county) will the contractor be paid the full monthly rate regardless of actual trips performed? | Yes, this is a FFP contract. Payment will be made in accordance with contract terms, on a fixed monthly basis, regardless of the number of trips performed. |
| PWS | 5.0.2 | The major "minimum" requirement that affects pricing is the 30 minute response time; this could require contractors to station teams and vehicles in each county in several locations (regardless of traffic) to enable pickups within 30 minutes. If the scope of work increases beyond the contractor's approved staffing plan, will the contract receive an REA for such demand? | The requirement is FFP, with a requirement of a "30" minute response time, regardless of number of trips or teams providing service. |
| PWS | 5.2.3 | Can the Government list the most common pickup locations or type of location) per county? | Not possible. Pickup locations will vary based on location of arrest or location of transport request. However high traffic areas center around Dallas-Ft. Worth, San Antonio, and Houston. |
| PWS | 5.2.4 | What happens if the contractor's average pickup time exceeds 30 minutes for a month (especially during first 3-6 months of performance)? | See the QASP and Acceptable Quality Levels for stated performance requirements. Contractors are expected to meet the 30 minute monthly average. |
| PWS | 5.2.7 | There are no surge CLINs in the price attachment. If surge services are required, will additional CLINs or Overtime CLINs be provided? | This is a FFP requirement, there are no plans on having a surge CLIN. |
| PWS | 5.2.8 | Will the daily operational report be provided by the contractor's National Coordination Center Staff and to whom will the report be submitted? | It is submitted to ICE-ERO, but this is part of the purpose for the secure website. The report can simply be uploaded to the website as opposed to emailing the report to various recipients. The ICE-ERO recipients simply need access to the secure website. |
| Attachment 01 | 5.3 | Will the contractor have to pay for space inside the National Coordination Center? | No. |
| Attachment 01 | 5.3 | Will response time requirement be measured from the receipt of transport request, confirmation with ICE ERO personnel, or dispatch of of transport team? | Clock starts at the dispatch of the transport team. |
| Attachment 01 | 5.4.1 | Is this website requirement an add on to any ICE ERO portals that the contractor will have to input information into? | No. Stand alone website/portal without connection to any ICE ERO portals. |
| PWS | 5.5.2 | Will ICE generate the initial G-391 including manifest or provide all required information to the contractor to generate the G-391? | ICE personnel at the NCC will provide the required G-391 information. |
| Attachment 01 | 5.6.1 | Is there a maximum expected detainee capacity? | No. |
| PWS | 5.7 & 7.3 | What is the requirement for Body Armor? | None required. |
| PWS | 6.2 | Initial staffing within the 120 transition period (and 30 day requirement for DFW/SNA/HOU) will certainly be impacted by the length of time requried for PSU to conduct security clearance investigations. What steps will ICE take to expedite the process to ensure initial staffing is provided within the required timeframes? (E.g., granting an preliminary clearance based on a nation criminal records check?) How long is the process to receive an preliminary clearance? | This contract is an operational priority for ICE and steps will be taken to expedite the process. PWS revised to reflect 60 days for DFW/SNA/HOU and 30 days regarding vacancies, given the potential challenges of PSU providing vetting/clearning. |
| Attachment 01 | 6.2 | Will the fitness screening be done at a predetermined ICE location that employees across the state will have to travel to? Or, is this done via NCIC system by ICE. | Completed via ICE OPR screening process. |
| PWS | 6.2 | If a contractor as part of its onboarding process conducts an extensive local, state and national criminal records check, domestic violence/child abuse, etc., background check, can the findings serve as a basis for the preliminary suitability determination? (Saves duplication of effort). | No, suitability must be processed through ICE/OPR Personnel Security Division. |
| Attachment 01 | 6.5 | How will the annual IT training be reported back to ICE? | A signed memo testifying that the included list of employees has completed the training will suffice. |
| PWS | 7.1.2 | Is the contractor requried to pay for staff security officer licenses? | Yes. All costs for licenses, certifications, etc. shall be borne by the contractor. |
| Attachment 01 | 7.4 | Are the required staffing levels equal to the contractor's approved staffing plan? | Other than the few positions noted such as dispatch operators and supervisor and project manager etc., the staffing levels are dictated by the contractor's ability to meet the 30 minute response time. |
| PWS | 7.4 | If after approval of the contractor's staffing plan for each county, additional staffing is required by ICE, will the contractor be provided with an REA to cover those costs in view of the current FFP monthly aggregate sum pricing. | This is a Performance Based FFP requirement, if staffing demands increase or decrease during contract performance, this would be the responsibilty on the contractor. |
| Attachment 01 | 7.4.3 | Will the government provide expedited clearences to meet the 10 colendar day replacement requirement? | This contract is an operational priority for ICE and steps will be taken to expedite the process. PWS revised to account for delays in suitability determination. PWS now reflects 30 days. |
| PWS | 8.1 | The RFP states initial training shall be not less than 24 hours. By so stating, for competive pricing, that encourages contractors to bid the minimum, when experienced contractors will provide more hours, especially firearms and Use of Force/Restraints. The RFP does not list PBNDS training in this section but the RFP requires cross training for all staff as detention and transportation officers. Can the minimum requirement be set at least at 40 hours? | PWS updated to 40 hours (not including firearms quals). |
| PWS | 8.1.2 | Does the 24 hour training requirement include time on the range for firearms qualification? | To align with other ICE transportation contracts, training requirements in PWS updated to 40 hours, not including firearms qualification. |
| 8.1.2 | Can the annual training be increased to 32 hours minimum to include firearms recert and CPR/First Aid. | PWS revised. Annual retraining changed to 16 hours (not including firearms qualifications). | |
| PWS | 8.2.1 | Does the 8 hour training requirement include time on the range for firearms qualification? | PWS revised. |
| PWS | 8.3.1 | If ICE identifies additional training requirements will the contractor receive an Equitable Adjustment to Price? | No. |
| PWS | 8.4.D | Why is AED training required? Are vehicles to be equipped with an AED? | AED requirement removed from PWS. |
| Attachment 01 | 9.3.2 | What is the model year requirement for a recent model SUV or Van? | Recent model defined as no more than five years old. |
| Attachment 01 | 9.4.1 | Will ICE be providing the encrypted radios, since contractors are not allowed to purchase radios with ICE configurations? | No. Communication with ICE or other law enforcement agencies would be via cell phones. |
| PWS | 10.1 | Will the information on the G-391 contain instructions for the use of restraints? (If detainees are not classified (High/Medium/Low Risk) who will authorize use of restraints? | See NDS 2016. |
| Attachment 01 | 11.0.1 | Will incidents like mass arrests require the contractor to purchase larger vehicles? If so, will emergency situations be grounds for an REA? | No. |
| Attachment 02 | Pricing Template | Are all transition costs meant to be included in the monthly price amount for base year? | See amendment. CLIN 0256 was established for the 120 day (4 month) transition period. |
| Attachment 02 | Pricing Template | Will a separate transition CLIN be provided? | See response above. |
| PWS | 14.4 | Can language be added to this section stating the outgoing contractor will access to all incumbent training records during the first 15 days of transition? | No. |
| Attachment 01 | 15.4.1 | Do Subcontractors have to be listed in the original written response to this RFP? | Yes. |
| Attachment 1 | 2.0.2/Appendix B | Appendix B lists delivery destinations; can we be provided with a list of pick up locations? Without that data its virtually impossible to calculate fuel costs and driver time. | Pick up locations are dependent upon where an arrest is made or where a state or local law enforcement agency requests transportation. |
| Attachment 1 | Appendix B | Can ICE provide parking space at its delivery locations? A possible approach that would save the Government money would be to revise the PWS to allow 2 hour pick up time (like the SNA AOR contract) and have transport teams dispatched from the delivery location to the pick up location and return. During non-transit time, the teams could assist ICE with hold-room surveillance and processing duties. | Individual ICE facilities may allow for parking at its location, however it is not a requirement in this contract for the individual ICE facilities to do so. |
| Attachment 01 | General | Will there be any stationary guard requirements after drop off? | None anticipated. |
| Attachment 03 | General | What county in Tennessee is the National Coordination Center located so contractors can use the correct Wage Determinations for the dispatch center? | Greater Nashville, TN area. Exact location is not yet known. |
| Attachment 01 | 17.2 | Due to continuous staffing and 24/7/365 availability requirements, will the contractor be able to bill for all counties every month, even if a county has no transport activity? | Yes, this is a FFP contract. Payment will be made regardless of the number of trips performed. |
| Attachment 03 | General | Will the government accept adjustments to pricing as soon as new Wage Determinations are released? | Contractors may submit a REA when Wage Determinations are updated via contract modification. |
| PWS | Section 2.0 Scope of Work, Page 1 and 2 | Please provide the last two years of historical transportation activity data, including transport requests by county, monthly and daily volumes, peak workload periods, cancelled transports, overnight stays, average detainees per transport, drive and wait times, transport duration, mileage, pickup and delivery locations, and any identifiable seasonal trends. | There is no historical data for transportation of 287(g) arrests. This contract will be the first of its kind. |
| PWS | Section 5.6 Task 6 - Vehicle Standards, Maintenance, Sanitation and Operational Readiness, Page 7 and 8, and Section 5.3 Task 3 - 24/7/365 Centralized Dispatch Operations Subsection 5.3.2, Page 6 | Please provide information regarding the current operational environment, including fleet size and composition, transportation staffing levels, dispatch center locations, and dispatch technology currently supporting transportation operations. | While other ERO transportation contracts exist, this one is specific to 287(g) and as such is the first transportation contract of its kind. |
| RFP | Section L.4.5 Proposal Content, Section 3) Volume III (Factor 3) Price, Page 111 | Is the monthly county-based CLIN intended to represent a fixed-price requirement regardless of transport volume, or is it based upon an anticipated workload assumption? If workload assumptions were used, please provide those estimates. | The monthly FFP CLINs are intended to be regardless of anticipated workload volume (trips). |
| PWS | Section 11.2 Emergency Operations and Surge Response, Page 32, Section 5.2 Task 2 - Geographic Coverage and 30-minute Response Capability, Subsection 5.2.7 Surge Operations, Page 5 | The PWS requires the contractor to support surge operations while maintaining response-time requirements to the maximum extent practicable. Please define the conditions that constitute a surge event and provide historical surge data for the past two years, including frequency, duration, transport volumes, and any peak staffing or fleet requirements experienced during surge operations. | A surge is an operational term whereby enforcement is focused on a specific geographic area or target for a determined timeframe. There is no historic transport data in support of 287(g) operations because this service of transportion of detainees from state and local partners to ICE does not currently exist. |
| PWS | Section 11.1 Emergency Preparedness and Contingency Plan, Subsection 11.1.4 The EPCP, Paragraph i, Page 31 | Can you provide the historical fuel usage? | The transportation services requested in this contract currently do not exist. Thus, there is no historic data regarding fuel usage. |
| RFP | Section L.4.5 Proposal Content, Section 3) Volume III (Factor 3) Price, Page 111 | Please clarify the intended invoicing methodology for transports involving multiple counties or destinations outside the originating county, including how shared resources and statewide operational costs should be allocated among county CLINs. | Each location has a set monthly FFP amount assuming that the detention occurs in that county. |
| RFP | Section L.3.1 Proposal Volumes and Phases, Paragraph b., Page 106 | Paragraph b references "The proposal shall consist of four separate volumes," however, only three are listed. Can you confirm there are three volumes required. | This is a typo, there are only 3 volumes. See Amended Section L.3.1 |
| PWS | Section 2.0 Scope of Work, Subsection 2.0.6, Page 2 | The PWS requires Dallas, Houston, and San Antonio operations within 30 days, although the transition period is 120 days. Should they all be 120 days? | PWS revised for Dallas/Ft. Worth, San Antonio, Houston operational within 60 days. All other areas, within 120 days. |
| PWS | Section 1.0 Background, Subsection 1.0.6, Page 1 | Would the Government consider revising this requirement so that the 30-minute response standard is measured from the scheduled pickup time rather than from the time of dispatch notification? | Most requests will be ad hoc, and thus cannot be scheduled in advance. |
| PWS | Section 12 Deliverables and Reporting Requirements, Subsection 12.2.3.7 Weekly County Coverage Certification Report, Page 35. Section 5.2 Task 2 - Geographic Coverage and 30-Minute Response Capability, Page 5 | The solicitation requires transportation coverage for all 254 Texas counties and a Weekly County Coverage Certification Report identifying assigned personnel and vehicles for every county. To support staffing and deployment planning, please provide the Government's assumptions regarding geographic coverage, including any estimated transport team distribution or operational coverage model anticipated to achieve the required response times. | Staffing model and deployment locations are up to the contractor. PWS language updated regarding Weekly Coverage Report. |
| PWS | Section 5.2 Task 2 - Geographic Coverage and 30 Minute Response Capability Subsections 5.2.1 through 5.2.4, Page 5 | This section states that response time performance is measured as a statewide monthly average, with a maximum allowable response time of 30 minutes calculated across all transport requests statewide. Please confirm whether the 30-minute requirement applies only to the calculated statewide monthly average, or whether individual transport requests are also expected to consistently meet the 30-minute response time standard. | Response time is calculated statewide on a monthly basis. |
| PWS | Section 7 Personnel Requirements and Key Personnel, Subsection 7.4 Staffing Continuity, Pages 20-21 | The PWS requires the contractor to maintain “100 percent of required staffing levels” and to replace vacant personnel within ten (10) calendar days. If staffing levels fall below 100 percent due to circumstances outside the contractor’s control (e.g., delays in Government suitability adjudications, EOD approvals, employee resignations, or medical leave), what contractual remedies, sanctions, payment deductions, or other performance impacts will be applied? Additionally, is there a defined acceptable staffing threshold or cure period before the Government initiates corrective actions or considers performance-based remedies? | PWS revised to reflect 30 calendar days. |
| PWS | Section 5.2 Task 2 - Geographic Coverage and 30-Minute Response Capability, Page 5; Section 5.3 Task 3 - 24/7/365 Centralized Dispatch Operations, Page 6 | To support compliance with response-time requirements, will transport manifests or scheduling information typically be provided in advance, and if so, what is the Government's expected notification timeframe? | Most requests will be ad hoc, and thus cannot be scheduled in advance. The contractor's centralized dispatch will coordinate the details of the transportation request and then dispatch a transport team. |
| RFP and PWS | L.4.5 Proposal Content, Section 3) Volume III (Factor 3) Price, Page 111 and PWS Section 2.0 Scope of Work, Subsection 2.1.2 Base Period, Page 2 | The solicitation includes a 120-day transition-in period as part of the base period; however, the pricing template does not include a separate Transition or Mobilization CLIN. Please clarify how offerors are expected to recover transition and mobilization costs. | See amendment. Transition CLIN is established. |
| RFP | Section F.3 Place of Performance, Page 7 | Transportation Officers perform mobile work that routinely originates in one county and traverses multiple counties and states. Please identify the applicable SCA wage determination methodology to be used, including whether compensation is based on the employee's assigned duty station, the pickup location, the destination location, or another methodology approved by DOL. | It is the responsibility of the contractor to ensure compliance with required DOL/SCA wages. The government has provided WD's for all 254 Texas counties. |
| RFP | Section H.10 In Accordance with FedRamp, Page 13 | If the Offeror does not currently possess a FedRAMP Authorized environment, but can demonstrate alignment with NIST SP 800-53 security controls, FIPS-compliant encryption, multi-factor authentication, vulnerability management, independent security assessments, and a documented plan to achieve any required authorization activities: |
Will DHS/ICE accept alternative evidence of security maturity, such as NIST SP 800-53 alignment, NIST SP 800-171 compliance, third-party penetration testing, and independent security assessments, in lieu of an existing FedRAMP Authorization?
| The contractor shall comply with all applicable hosting, cloud, cybersecurity, privacy, and authorization requirements in the solicitation, including PWS 5.4, PWS 13.0, and Appendix C. The portal is described as a stand-alone contractor-hosted system, but Appendix C requires ICE systems and data to be hosted within the ICE Cloud unless an ICE CIO-approved exception is obtained. No system may process or store ICE data until it has received an ICE Authorization to Operate. The required impact level will be determined by the Government under FIPS 199 and the solicitation currently identifies moderate-impact-equivalent controls for the portal. A FedRAMP-authorized commercial service may be proposed, but it must meet all ICE-specific requirements, including OCIO oversight, access, telemetry, security artifacts, continuous monitoring, and ATO requirements. The contractor is responsible for providing all required security documentation and assessments to support Government review. Government approval timelines are dependent on the completeness and acceptability of the submission and do not relieve the contractor of the Day 90 production requirement. | ||
| RFP | Section H.10 In Accordance with FedRamp, Page 13 | For the secure web portal required under this contract: |
1. Has DHS/ICE determined the FIPS 199 security categorization and required FedRAMP impact level (Low, Moderate, or High)?
2. Will the requirement be considered satisfied if the solution is hosted within an existing FedRAMP Authorized cloud environment, such as Microsoft Azure Government, with the Offeror implementing all required system-level security controls?
| 3. Is FedRAMP Authorization required for the contractor-developed portal/application itself, or only for the underlying hosting environment and associated security control framework? | The contractor shall comply with all applicable hosting, cloud, cybersecurity, privacy, and authorization requirements in the solicitation, including PWS 5.4, PWS 13.0, and Appendix C. The portal is described as a stand-alone contractor-hosted system, but Appendix C requires ICE systems and data to be hosted within the ICE Cloud unless an ICE CIO-approved exception is obtained. No system may process or store ICE data until it has received an ICE Authorization to Operate. The required impact level will be determined by the Government under FIPS 199 and the solicitation currently identifies moderate-impact-equivalent controls for the portal. A FedRAMP-authorized commercial service may be proposed, but it must meet all ICE-specific requirements, including OCIO oversight, access, telemetry, security artifacts, continuous monitoring, and ATO requirements. The contractor is responsible for providing all required security documentation and assessments to support Government review. Government approval timelines are dependent on the completeness and acceptability of the submission and do not relieve the contractor of the Day 90 production requirement. | |||
| PWS | Section 6.0 Security and Suitability Requirements, Page 9 | What are the authentication and identity management requirements for ICE personnel accessing the contractor-hosted secure portal? | A simple verification that the individual is an ICE employee is sufficient. | |
| RFP | Section L.4.5 Proposal Content, Section 3.1) Part 1 - Technical/Management Approach (Factor 1), Subsection 2. Web-based Secure Portal, Page 109 | Will the contractor-hosted secure portal require a formal DHS/ICE Authority to Operate (ATO), and if so, what authorization process and timeline should offerors anticipate? | The contractor shall comply with all applicable hosting, cloud, cybersecurity, privacy, and authorization requirements in the solicitation, including PWS 5.4, PWS 13.0, and Appendix C. The portal is described as a stand-alone contractor-hosted system, but Appendix C requires ICE systems and data to be hosted within the ICE Cloud unless an ICE CIO-approved exception is obtained. No system may process or store ICE data until it has received an ICE Authorization to Operate. The required impact level will be determined by the Government under FIPS 199 and the solicitation currently identifies moderate-impact-equivalent controls for the portal. A FedRAMP-authorized commercial service may be proposed, but it must meet all ICE-specific requirements, including OCIO oversight, access, telemetry, security artifacts, continuous monitoring, and ATO requirements. The contractor is responsible for providing all required security documentation and assessments to support Government review. Government approval timelines are dependent on the completeness and acceptability of the submission and do not relieve the contractor of the Day 90 production requirement. | |
| RFP | Section L.4.5 Proposal Content, Section 3.1) Part 1 - Technical/Management Approach (Factor 1), Subsection 2. Web-based Secure Portal, Page 109 | What specific security monitoring, audit log retention, vulnerability scanning, and reporting requirements apply to the secure portal environment? | The contractor shall comply with all applicable hosting, cloud, cybersecurity, privacy, and authorization requirements in the solicitation, including PWS 5.4, PWS 13.0, and Appendix C. The portal is described as a stand-alone contractor-hosted system, but Appendix C requires ICE systems and data to be hosted within the ICE Cloud unless an ICE CIO-approved exception is obtained. No system may process or store ICE data until it has received an ICE Authorization to Operate. The required impact level will be determined by the Government under FIPS 199 and the solicitation currently identifies moderate-impact-equivalent controls for the portal. A FedRAMP-authorized commercial service may be proposed, but it must meet all ICE-specific requirements, including OCIO oversight, access, telemetry, security artifacts, continuous monitoring, and ATO requirements. The contractor is responsible for providing all required security documentation and assessments to support Government review. Government approval timelines are dependent on the completeness and acceptability of the submission and do not relieve the contractor of the Day 90 production requirement. | |
| PWS | PWS Section 9.1 Dispatch Center - ICE 287 (g) National Coordination Center, Page 24 | Will internet service be provided for contractor personnel at the Nashville office, or will the contractor be responsible for procuring its own Internet connectivity? If contractor-provided Internet service is required, is adequate network cabling and infrastructure available within the contractor-assigned workspace to support the installation and use of that connection? | Contractor should be prepared to provide their own internet service. Theh location and cabling infrastructure of Nashville office is currently unknown. | |
| RFP; Attachment 01 - PWS | Sec. L.4.5 Vol III item 4, p.111 / General | Is this solicitation for an established, currently-performed contract (i.e., is there an incumbent providing these services today and a predecessor collective bargaining agreement), or is this a new requirement with no predecessor contract? If established, please confirm the predecessor CBA applies per Section L.4.5's entry-level pricing and post-award Request for Equitable Adjustment instructions. If this is confirmed to be a new requirement, please confirm those CBA/seniority-list/REA instructions are inapplicable and pricing should be based solely on the DOL wage determination for the 'Detention Officer' classification. | This is a new requirement.There are no known CBAs. | |
| RFP; Attachment 03 | Sec. L.4.5 Vol III item 4; Attachment 03 | Is there a current collective bargaining agreement (CBA) in place today covering employees who would perform this work (e.g., under an existing or predecessor contract), and if so, please identify it and confirm whether its wage/fringe terms will govern the initial period of performance. Separately, if contractor employees hired under this new contract subsequently organize and negotiate a CBA during performance, how would the resulting wage and fringe benefit obligations be handled under the firm-fixed-price CLIN structure -- through a Request for Equitable Adjustment, a revised wage determination, or some other contractual mechanism? | This is a new requirement. There are no known CBAs. | |
| RFP | Sec. L.3.1(b) p.106; L.4.5 p.108; M.6 p.116 | Section L.3.1(b) states the proposal 'shall consist of four separate volumes' but lists only three (Administration, Written Proposal, Price/Cost); please confirm three volumes are required. Separately, Section L.4.5 discusses Technical/Management and Past Performance content under a 'Volume II' heading while also stating 'Volume III consists of two parts,' and Section M.6 identifies Factor 1 content as 'Volume III.' Please confirm Factors 1 and 2 (Technical/Management, Past Performance) are both submitted in Volume II, and Factor 3 (Price) in Volume III. | See amendement. There are only 3 volumes. | |
| RFP | Sec. L.4.5 Part 1, pp.108-110 | The seven Factor 1 elements (Understanding of the Requirement, Web-Based Secure Portal, Fleet Plan, Staffing Plan, Operations Plan, Management Plan, Transition-In Plan) are not assigned between the 15-page Technical and 10-page Management limits. Please identify which elements count against each limit, particularly the Staffing Plan, Operations Plan, and Transition-In Plan. | See revised langauge. Part 1 submission now has a 25 page combined limit for offerors to submit both technical and management. | |
| RFP | Sec. L.4.5 Vol I item 1.c; SF33 Block 12 | Section L.4.5 (Volume I, item 1.c) states a proposal validity period of '[120]' calendar days in brackets, while SF33 Block 12 states 60 days. Please confirm the required minimum proposal validity period. | See Amendment. Requirement is 120 days | |
| RFP | Sec. L.4.5 Vol I / Combined synopsis | Section L does not list the Small Business Individual Subcontracting Plan as a Volume I element. Is the individual subcontracting plan due with the initial proposal, or requested only from the apparent successful offeror? | See RFP section L.4.5 (3). The SB Subcontracting plan is required in Volume III, to be included with the price proposal. | |
| RFP | Sec. L.4.5(4)(2) / M.6 / M.9 | Section L refers to the Small Business Individual Subcontracting Plan as 'Factor 4,' while Section M.6 lists only three evaluation factors (Technical/Management, Past Performance, Price) and M.9 discusses relative importance of only those three. Please clarify whether the subcontracting plan is a separately rated/weighted evaluation factor or a pass/fail administrative item evaluated within Factor 3 (Price). | This was a typo, see amendment removing "Factor 4" reference. | |
| Attachment 01 - PWS | PWS 12.1.2.a / 12.1 | PWS 12.1.2.a cites the 'G-391 Excel Upload Template' as Attachment X, which was not included in the solicitation. Please provide the applicable version of the template (or a sample blank Form G-391) or identify the required data elements, so offerors can accurately scope the secure portal's electronic form and TMO reporting functionality. | See Attachment 05-G-391 Upload Template | |
| Attachment 02; Attachment 01 - PWS | Attachment 02, CLINs 0001-0254; PWS 1.0.6 | The solicitation provides no transport volume, trip count, or mileage estimate. Will the Government provide workload data by county or region for each contract period? The 287(g) TX RFI response cited six trips per hub per day and nine FTE per hub; please confirm whether those figures remain the planning basis. | This is a new requirement. See PWS. | |
| Attachment 02 | Attachment 02, CLINs 0001-0254 (locked Location/Quantity cells) | Attachment 02 requires a separate, individually priced monthly CLIN for each of the 254 counties (Location and Quantity cells are locked; only Unit Price is editable). Given a statewide hub-and-spoke staffing model will serve multiple counties from a smaller number of physical staging locations, how should offerors allocate a hub's shared cost (facility, supervision, standby staffing) across the individual county CLINs it serves, when each county CLIN must be priced and invoiced as if independently staffed? | The government is seeking a firm-fixed-price for services in each county. | |
| Attachment 01 - PWS; Attachment 02 | PWS 1.0.6, 2.2.1, 5.2.1; Attachment 02 CLINs 0001-0254 | Could the Government advise as to which specific locations statewide (e.g., current and anticipated 287(g) partner agencies/counties, or a ranked list of expected pickup locations) the contractor would actually be expected to respond to, rather than a general requirement covering all 254 Texas counties? Identifying the real geographic distribution of anticipated activity would allow offerors to more accurately plan staging locations, team distribution, and pricing by county CLIN. | The operational requirement is for pick up of detainees from any location in Texas. Currently, the highest volume areas are in counties in and around DFW, SNA, and HOU. | |
| Attachment 01 - PWS | PWS 2.0.6, 5.2, 9.2 | Does the Government have a required minimum number of hubs or staging locations statewide, or is the contractor solely responsible for determining the number and placement of hubs necessary to meet the statewide 30-minute average response time and all-254-county coverage requirements? | There is no minimum number, nor locations required. The contractor is solely responsible for staffing and resource deployment to achieve the 30 minute response time average. | |
| Attachment 02 | Attachment 02, CLINs 0001-0254 | Every county CLIN carries an identical locked Quantity (12 months Base / 36 months Option) with no linkage to population, workload, or whether a 287(g) partner agreement even exists in that county. Please confirm the monthly price for a county CLIN is payable in full regardless of transport activity, and confirm whether the Government will accept a nominal or de minimis Unit Price for counties with no executed 287(g) agreement or no anticipated volume, or whether a substantively justified, cost-based price is required for all 254 CLINs regardless of expected activity. | Each CLIN will be FFP and paid monthly regardless of volume or activity. | |
| Attachment 02; Attachment 01 - PWS | Attachment 02; PWS 2.0.2 | Attachment 02 contains no mileage CLIN. Please confirm the fixed monthly county price covers all vehicle miles, including unloaded response, return, and repositioning legs, with no separate mileage reimbursement. | All mileage is to be included within the fixed monthly price. | |
| Attachment 02 | Attachment 02; PWS 9.0 | The solicitation does not separately address fuel. Please confirm fuel is to be priced within the monthly county CLINs, with no separate reimbursement or economic price adjustment. | Fuel is to be included within the monthly FFP CLIN. | |
| Attachment 01 - PWS; Attachment 02 | PWS 11.2; Sec. L.4.5 Part 1 Element 5 | PWS 11.2 references a surge example of '50 additional teams within 24 hours,' and Attachment 02 contains no separate surge CLIN. Is the 50-team figure a binding minimum surge capacity requirement, or an illustrative example offerors should independently size based on their own risk assessment? Is surge capability priced within the monthly county CLINs or ordered/compensated separately, and if priced within, what assumed frequency and duration of surge events should offerors plan for? | This seems to be from a prior version of the PWS and not included in the final version of the PWS. | |
| Attachment 01 - PWS; Attachment 02 | PWS 11.2; Attachment 02 (no surge CLIN) | If surge operations result in additional costs beyond what is embedded in the flat monthly county CLIN pricing (e.g., activating the '50 additional teams within 24 hours' EPCP scenario, or other emergency surge deployments directed by the COR), how would the contractor be compensated for those additional costs -- through a contract modification/Request for Equitable Adjustment, a dedicated surge CLIN or not-to-exceed line item, reimbursement of documented incremental costs, or some other mechanism? | There is no reference to "50 additional teams" in the PWS, Offerors are cautioned to use the PWS that was included in the RFP, and not to use any prior draft PWS's provided as part of a preceeding RFI. This contract will be FFP, therefore a not to exceed CLIN is not allowable. | |
| Attachment 02 | Attachment 02 table name 'TexasSCAWageDeterminations' | The Attachment 02 pricing table is internally named 'TexasSCAWageDeterminations.' Does this indicate the Government expects each county's Unit Price to be individually keyed to that specific county's SCA/DOL wage determination for the 'Detention Officer' classification? If so, will the Government confirm that Attachment 03 contains a distinct wage rate for all 254 counties (rather than a single statewide rate) and identify which wage determination corresponds to each county CLIN? | A listing of all 254 counties of Wage Determinations has been provided to offerors. The government does not understand the question posed. The RFP included a direct link to access all 254 WD's by each county in attachment 03. | |
| Attachment 02 | Attachment 02, CLIN 0255 'Centralized Dispatch Services' | CLIN 0255 ('Centralized Dispatch Services') is a single statewide monthly price with no location or labor-category breakdown, despite dispatch operations being physically performed in the greater Nashville, Tennessee area. Should the Basis of Estimate for CLIN 0255 be built on a Tennessee-applicable wage rate/structure rather than any Texas SCA wage determination, and will the Government identify the applicable wage determination for this CLIN? | Yes. A WD was not provided as the location of the NCC has not been publically announced. A WD will be provided upon award of that separate NCC contract. | |
| RFP; Attachment 02 | Sec. L.4.5 Vol III item 4; Attachment 02 Option Period column | The Option Period column in Attachment 02 provides a single Unit Price cell covering the full 36-month option period, with no mechanism to reflect annual SCA wage determination revisions within that period. Please confirm whether offerors should propose one flat, blended rate for the entire 36 months, and how FAR 52.222-43 economic price adjustments (if applicable) would be reconciled against a single, non-escalating Option Period Unit Price cell. | Correct. Offerors shall include a flat blended rate. In the event that WD's are modified into the contract during opion year performance, contractors would be able to submit REA's if necessary. | |
| RFP; Attachment 02 | Attachment 02 CLIN structure; Sec. L.4.5 Vol III item 4 | Attachment 02's CLINs are priced only against SCA wage determination labor (the 'Detention Officer' classification) tied to Attachment 03, with a single flat Unit Price per CLIN spanning the full 36-month Option Period. There is no separate CLIN, escalation mechanism, or line item to account for annual wage/salary growth for exempt management positions (e.g., Program Manager, Deputy Program Manager, Operations Manager, Training Manager, Fleet Manager) that fall outside the SCA wage determination. How should offerors account for anticipated management wage escalation over the 4-year period of performance -- through a separate management/G&A CLIN, through allocation within indirect (G&A) rates applied across the existing county CLINs, or through some other mechanism the Government intends to specify? | See Amendment. A program management CLIN (0267) has been established. Offerors may use the BOE narrative to explain their rationale. | |
| Attachment 02 | Attachment 02, row 260 (Contract Total) | Attachment 02 rolls up all 255 CLINs into a single Base Period Total, Option Period Total, and Contract Total. Please confirm whether award/price evaluation will be based on this aggregate contract total, or whether individual county CLIN prices will also be separately evaluated for reasonableness or unbalanced pricing across counties. | See Section M of the RFP. | |
| RFP; Attachment 02 | Sec. L.4.5 Vol III item 2 (BOE); Attachment 02 | Section L.4.5 requires a Basis of Estimate 'for each CLIN.' With 255 individual CLINs (254 counties plus dispatch) and no notes/assumptions column within the locked Attachment 02 template itself, is a single BOE methodology applied uniformly across all county CLINs sufficient, or does the Government require a separate, county-specific Basis of Estimate for each of the 254 individual county CLINs? | See Section L of the RFP. Offerors are not limited to solely using the excel pricing template to provide BOE narratives. Offerors may use Microsoft Word or Adobe PDF separately to provide the BOE narrative. | |
| Attachment 02 | Attachment 02, CLINs 0001-0254 (locked Quantity cells) | Attachment 02 confirms there is no separate Transition-In CLIN -- every county CLIN's Base Period Quantity is locked at a flat 12 months beginning with contract award, with no mechanism for partial-month or phased billing. This appears to conflict with PWS 2.0.6/14.1, which requires only the Dallas-Fort Worth/San Antonio/Houston metro counties to be operational within 30 days and the remaining counties to phase in over 120 days. Please confirm whether offerors are expected to price all 254 county CLINs as if full statewide service begins on day one of the Base Period, with the cost of the phased 120-day ramp-up absorbed into a single flat monthly Unit Price. | See amendment. Transition CLIN is established for initial 120 days (4 months). | |
| Attachment 02; Attachment 01 - PWS | Attachment 02; PWS 14.1.1, 17.0.1 | Since Attachment 02 confirms there is no distinct Transition-In CLIN and the Quantity/Location cells are locked (only Unit Price is editable), how should offerors reflect substantial up-front, non-recurring transition costs (recruiting, background investigations, vehicle acquisition/outfitting, facility stand-up, secure portal development) within a flat monthly Unit Price that must remain constant across all 12 months of the Base Period? | See amendment. Transition CLIN is established for initial 120 days (4 months). | |
| Attachment 01 - PWS | PWS 14.1 / 2.0.6 | Will the 120-day transition-in be a phased rollout (e.g., activating Dallas-Fort Worth, San Antonio, and Houston first, then expanding county-by-county/region-by-region across the remaining 254 counties), or is the Government expecting all 254 counties to be staffed and operational simultaneously at the end of the transition period? | The high traffic areas should be operational within 60 days, and the remainder of the state within 120 days. | |
| Attachment 03; Attachment 01 - PWS | Attachment 03; PWS 2.2.3, 5.3.2 | Attachment 03 covers the 254 Texas counties only, but dispatch is performed in the greater Nashville, Tennessee area. Which wage determination applies to dispatch personnel, and will the Government incorporate it by amendment? | Once the NCC contract is awarded, a WD for that area will be provided via contract modification. | |
| RFP; Attachment 02 | Sec. F.2; Sec. L.4.5 Vol III item 4 | The option period is a single 36 months at one fixed monthly rate, and Section L prohibits contingency pricing. How should offerors reflect annual wage determination revisions in that rate? Please confirm FAR 52.222-43 price adjustment applies at each revision. | Yes. 52.222-43 is already included in the RFP. See Section I.1. | |
| Attachment 01 - PWS | PWS 2.2.3, 9.1.1, 5.3.1 | The ICE 287(g) National Coordination Center is described as 'in the planning stages' and 'projected to become operational in 2026.' What is the expected date for contractor space availability at the NCC? If space is unavailable within the 120-day transition, will an interim contractor dispatch location be acceptable, and will transition milestones be adjusted accordingly? | Space at the NCC should be available by late September. If space is not yet available, an interim or alternate dispatch site is acceptable. | |
| RFP | Sec. H.4 vs. PWS 9.0 / 13.0 | Section H.4 requires the contractor to perform all tasks using Government-furnished IT 'on authorized Government networks' and 'at authorized Government facilities.' PWS Sections 9.0 and 13.0 require the contractor to furnish/operate its own statewide field, staging, and armory facilities, and to host a stand-alone secure web portal explicitly 'not connected to or integrated with any Government information system.' Please confirm Section H.4's network/facility restriction does not apply to the contractor's field operations, vehicles, or the contractor-hosted secure portal. | See PWS. | |
| Attachment 01 - PWS | PWS 6.0, 6.1.2, 6.2, 2.0.6 | What is OPR PSD's current average processing time for preliminary and final Fitness determinations? Will adjudications be prioritized during transition to support the 30-day standup of Dallas-Fort Worth, San Antonio, and Houston, and is OPR PSD resourced for the statewide personnel volume needed within 120 days? | PWS updated to account for fitness determination timelines. | |
| Attachment 01 - PWS | PWS 6.1.2, 6.2, 14.1.1 | If this is confirmed to be a new requirement with no incumbent contractor or existing cleared workforce to draw from, will the Government commit to working with the awarded vendor to expedite contractor employee security/suitability clearance processing (e.g., dedicated OPR PSD support, expedited preliminary Fitness reviews, batch submission handling) to support standing up an entirely new statewide workforce within the 30-day priority-metro and 120-day full-FOC timelines? | Duplicate question. See revised PWS. | |
| Attachment 01 - PWS | PWS 1.0.6, 4.0.1.5, 5.2.3 | The 287(g) TX RFI response reportedly stated there was no flexibility in the 30-minute standard and that all Texas pickup locations must be reached within 30 minutes. Please confirm the PWS's monthly statewide average standard supersedes that position, and state how the average is computed (e.g., simple average across counties, or weighted by county/volume). | RFI's are used for market research purposes. Utilize the PWS requirement within the RFP. | |
| Attachment 01 - PWS | PWS 1.0.6, 5.2.3 | The 30-minute statewide average applies uniformly across all 254 counties, including rural/low-population areas where achieving that standard requires significantly higher staffing density relative to demand. Would the Government consider a tiered response-time standard (e.g., 30 minutes in high-volume metro areas and 60-90 minutes in rural/low-volume counties) rather than a single statewide average, to allow a more efficient and cost-effective staffing model? | No. | |
| Attachment 01 - PWS | PWS 5.7.1 | Is there an ICE-approved list of specific 9mm duty pistol makes/models, or may the contractor select any standardized 9mm handgun meeting the stated specifications (chambered round, two spare magazines, Level III+ retention holster)? | Information can be provided upon award. | |
| Attachment 01 - PWS | PWS 9.4.1 | Please confirm whether body armor (soft and/or hard armor) is a required item of issue for armed transport personnel and, if so, the required protection level and whether it is contractor- or Government-furnished. | See PWS and NDS 2026. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .