Fish Barrier IDIQ Asset Maintenance Answered Questions 03-Sep-2026.pdf
PDF 332 KB Posted
- Attached to
- Fish Barrier Maintenance and Repair IDIQ
- Solicitation number
- W912P626QA021
About this file
This file is a Questions and Answers document for a federal contract solicitation related to maintenance and repair services for fish barrier systems and associated infrastructure.
The solicitation uses simplified quote procedures under FAR 12 for commercial items, with quotes required to be submitted electronically through the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No specific file naming convention or separation of technical, price, and past performance files is required. Award is anticipated before September 30, 2026, for a four-year ordering period. The contract requires CMMC Level 1 compliance (revised in amendment P00001) and all offerors must complete FAR 52.212-1(b)(4) for technical submissions and all representations and certifications, including FAR 52.222-48. Past Performance submissions require no specific format but must include subcontractor names, addresses, and UEI if applicable. Travel costs for repair task orders must be priced according to Joint Travel Regulations at the task-order level, with assumptions reflected in base proposal pricing matrix tabs.
The scope encompasses preventive maintenance and repair services for chillers (quarterly FFP preventive maintenance including condenser and free-cooling coil cleaning annually), generators (annual maintenance and load testing October 1–November 15), IT equipment, control systems, camera systems, and access-card reader systems (including Rockwell FactoryTalk, Cisco switches, Dell servers, Johnson Controls Metasys, Pelco cameras, and related platforms). Contractors must maintain required certifications throughout contract performance but need not submit evidence with proposals. Maintenance reports must document work performed, labor, and parts; repair reports must include root-cause analysis and recommendations. Activity Hazard Analyses (AHAs) and Quality Control Plans are required post-award. Response-time requirements, inspection/maintenance frequency conflicts, and system architecture details were clarified through scope revisions. Contractor personnel requiring unescorted access must meet Government security requirements; urgent service needs do not waive security protocols. Repair work requiring separate pricing must be authorized via Task Order by a warranted Contracting Officer; verbal requests are not permissible.
View the file
Other files
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
Question No.
Solicitation Reference
Question Government Response
DFARS
252.204- 7025, pp.97–
98; DFARS
252.204- 7021, pp.43–
Please confirm the required CMMC level applicable to this procurement for proposal submission, award eligibility, contract performance, and subcontract flowdown. DFARS 252.204-7025 identifies CMMC Level 1, while DFARS 252.204-7021 identifies Level 2.
CMMC 1, revised in amendment P00001
SOW Section 2.5, pp.10–12
Please confirm whether inspection and maintenance of IT equipment, control systems, camera systems, and access-card reader systems is required annually or quarterly. The heading states annual inspection and maintenance, while the body text states quarterly inspection and maintenance.
Scope revised to clarify conflict.
SOW Section 5, p.14;
QASP, p.21
Please confirm the governing response-time requirement for troubleshooting/repair service calls. SOW Section 5 states repair service call work must begin within seven calendar days, while the QASP requires initial contact within four business hours and onsite response within two calendar days for Urgent requests and five calendar days for Routine request task orders.
Scope revised to clarify conflict.
Section L, pp.95–99;
Section M, pp.101–102
Please provide the required Past Performance submission format, including number of references, recency period, No specific format required, if intending to subcontract, indicated subcontractors, relevance criteria, page limits, required customer contact information, and whether subcontractor past performance may be submitted.
provide their address and
UEI.
SF 1449, p.1;
Section L, pp.95–99
Please confirm the required proposal submission method, including whether quotes are to be submitted by email, portal, PIEE, SAM.gov, or another method. Please also confirm any required file naming convention and whether separate technical, price, and past performance files are required.
Quotes must be submitted in PIEE as indicated on sam.gov and in PIEE, “All quotes must be submitted electronically through the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module at https://piee.eb.mil.” No required naming convention or separate files.
Section L, pp.95–99;
Section M, pp.101–102
Please confirm whether oƯerors are required to submit a separate technical approach narrative. Section M identifies Price and Past Performance as the evaluation factors, but the SOW and QASP contain multiple technical, safety, security, quality, staƯing, and reporting requirements.
We are not using FAR 15 procedures and have requested simplified quotes under FAR 12. We did not include any technical factor under FAR 52.212-2. On page 95,refer to FAR 52.212-1 (b)(4) for technical submissions. Required certifications shall be maintained throughout contract performance.
SOW Section 3, p.13
Please confirm whether oƯerors must submit evidence of valid certification for maintenance and repair of each system with the proposal, or whether such certifications must only be held and maintained during contract performance.
We are not using FAR 15 procedures and have requested simplified quotes under FAR 12. We did not include any technical factor under FAR 52.212-2. SOW does not mandate this as a preaward requirement; thus shows latter part of question. Required certifications shall be maintained throughout contract performance.
FAR 52.222-
48, pp.84–86
Please confirm whether all oƯerors must complete FAR 52.222-48, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment— Certification, regardless of whether the oƯeror claims the exemption.
Refer to FAR 52.212-1 (b)(8) Quoters must complete each representation and certification.
Pricing Matrix Read Me;
Section A, p.2
Please confirm whether oƯerors must complete all blue cells in the CSSC Fish Barrier IDIQ Pricing Matrix for all four contract periods, including routine FFP pricing, fully burdened labor-rate ceilings, and fixed repair markup percentages.
Confirmed.
Section H, p.24
Please confirm whether proposed travel costs for repair task order quotes must be priced in accordance with the Joint Travel Regulations at the task-order level only, or whether any travel assumptions must also be reflected in the base proposal pricing matrix.
Travel costs for repair task order quotes must be priced in accordance with the Joint Travel Regulations at the task-order level, and assumptions must also be reflected in the base proposal pricing matrix-refer to tab “Repair Pricing Factors” tab which are established ceilings in negotiating firm fixed price repair work.
Section A, p.2; Section B, p.3; FAR 52.216-18, p.31; FAR 52.216-22, p.33
Please confirm the anticipated award date and anticipated start date for the four-year ordering period.
Based upon actual award, which we anticipate to be before 9/30/26.
SOW Section 2.1, p.5
Please confirm whether the annual generator maintenance and load testing window of October 1 through November 15 applies to each calendar year of the contract, and whether any first-year adjustment will be made if award occurs near or after this window.
Not likely to be adjusted since award will be made before window, and suƯicient time for submittals to be approved.
SOW Section 2.1, p.5; SOW Section 4, p.14; QASP, p.21
Please confirm the required content for written maintenance and repair reports, including whether root cause analysis is required for all repairs, and whether a Government-provided report template will be furnished.
Maintenance and repair reports shall document the work performed, including labor and parts. Repair reports shall also include root-cause analysis and recommendations for future action. This is commercial, we will rely on contractor documents unless otherwise stated.
SOW Section 8.6, p.17
Please confirm whether AHAs must be submitted with the proposal or only after award for each task order prior to performance.
AHAs are required after award and prior to performance when applicable. The contractor is responsible for preparing an AHA for each applicable Task Order, and the AHA must be accepted prior to commencement of the applicable work.
SOW Section 10.2, p.18
Please confirm whether the contractor-specific Quality Control Plan must be submitted with the proposal or only after award prior to the Pre-Performance Conference.
Post Award.
SOW Section 2.5, pp.10–12 & Section 3.
Page 13.
Please confirm what technical qualifications, experience, training, certification, or licensure are required or suƯicient for the work
The contractor shall meet the certification requirements identified in Section 3 for maintenance and repair of the applicable described under this PWS, in particular, maintenance of IT equipment, control systems, camera systems, and access-card reader systems.
systems. Section 2.5 identifies the IT and control systems within the scope, including Rockwell FactoryTalk, Cisco managed switches, Dell PowerEdge servers, ThinManager/thin clients, Johnson Controls Metasys/BACnet, Pelco cameras, American Dynamics VideoEdge/Victor, Innometriks Cheetah, Software House iStar Ultra, and Tyco C-Cure 9000. The SOW does not identify additional minimum years of experience or specific OEM certifications beyond the requirements stated in the solicitation.
SOW Section 2.5, pp.10–12
Please clarify how maintenance of IT equipment, control systems, camera systems, and access-card reader systems is to be coordinated with mission and cybersecurity operations teams and what cybersecurity requirements are required within the scope of work.
The contractor shall perform the IT-system maintenance identified in Section 2.5, including applicable software and firmware updates, patches, network-traƯic analysis, server-cache maintenance, and license monitoring. The contractor shall comply with all applicable cybersecurity requirements contained in the solicitation and shall coordinate system changes with the Government as required.
Refer to CMMC.
SOW Section 2.5, pp.10–12
Please clarify the Government's cybersecurity governance requirements applicable to these systems, including:
The SOW does not establish specific ATO status, testing environments, cybersecurity scan
Authority-to-Operate (ATO) status Required cybersecurity documentation Patch management responsibilities Change management procedures Configuration control requirements Coordination requirements with Government cybersecurity personnel. EG:
Who authorizes deployment?
Are testing environments available?
Are maintenance windows established?
Are cybersecurity scans required prior to implementation?
Must cybersecurity documentation be updated following changes?
procedures, or detailed change-management procedures for the systems identified in Section 2.5.
The contractor shall comply with applicable Government cybersecurity requirements and the cybersecurity clauses incorporated into the contract. Software and firmware updates and patches identified in the SOW shall be performed as applicable. Refer to CMMC.
SOW Section 2.5, pp.10–12
The PWS identifies the multiple systems but does not provide suƯicient detail regarding system architecture, complexity, and maintenance boundaries. Please clarify:
Specific hardware and software components included in-scope.
Supported operating systems and software versions.
Required maintenance activities.
Required OEM certifications.
Whether support includes troubleshooting, software modification, database maintenance, application updates, communications
The systems identified in Section 2.5 constitute the IT/control systems within the scope of the SOW. The SOW identifies the major systems and equipment but does not provide a complete system architecture, software-version inventory, network diagram, or database architecture. Maintenance shall be limited to the systems and activities identified in the SOW and authorized Task Orders.
Quantities, makes and models will be provided in an upcoming amendment.
infrastructure, and testing & integration phases.
SOW Section 2.5, pp.10–12
For PWS services, in particular
– patching of FactoryTalk, ThinManager, Metasys, C- Cure, VideoEdge, Cisco, and other software-based systems, please clarify:
Which licenses are Government-furnished.
Which licenses the contractor must maintain or procure.
Responsibility for annual software support agreements.
Responsibility for OEM software subscription renewals.
Does the Government require the contractor to maintain OEM-authorized service provider status, manufacturer certifications, or active software support agreements?
The contractor shall monitor applicable software licenses and perform available software and firmware updates and patches as required by Section 2.5. The SOW does not specifically assign responsibility for all OEM software subscriptions, annual support agreements, or license renewals. Such requirements shall be handled in accordance with the applicable contract and Task Order requirements.
SOW Section 2.2, pp.8–10
Please clarify what materials, parts, consumables, and quantities are required or expected to be included in the contractor’s fixed-price quarterly chiller preventive maintenance.
The SOW does not establish specific quantities of replacement parts or consumables that must be maintained as part of the quarterly FFP preventive maintenance, but it is expected fluids would be topped oƯ for chiller.
SOW Section 2.2, pp.8–10
Please confirm whether any corrective maintenance is included in this RFP.
Corrective maintenance is a broad term. Repair work requiring separate pricing shall be handled as separately ordered work in accordance with Section H.
The contractor shall provide a quote for the required repair, and work shall not proceed until authorized through the applicable Task Order.
SOW Section 2.2, pp.8–10
Please confirm whether the contractor is required to maintain glycol on hand at each barrier with a chiller, and if so, please identify the required type, minimum quantity, storage requirements, and whether replenishment is included in preventive maintenance or treated as corrective maintenance.
The contractor is required to check glycol concentration for freeze protection.
SOW Section 2.2, pp.8–10
Is the contractor responsible for disposal of all waste, inclusive of fluids, off site?
Yes. See page 5.
SOW Section 2.2, p.9; FAR 52.223-12, p.27
Please confirm whether the contractor is required to supply refrigerant needed to maintain the chillers during the contract period, and whether refrigerant replacement or recharge is included in quarterly preventive maintenance or ordered separately as corrective maintenance.
The contractor is required to inspect for refrigerant leaks, check refrigerant levels, and balance refrigerant as necessary.
The SOW does not establish a specific quantity of refrigerant included in the quarterly FFP preventive maintenance. Refrigerant requirements beyond the routine maintenance activities (i.e. more than 10% and leak identified) shall be handled in accordance with the applicable contract and Task Order requirements.
Scope revised to reflect approximate refrigerant requirements.
SOW Section 2.2, pp.8–10
Please confirm whether water testing and water treatment for chiller/process loop systems are included in the scope of this RFP, and if so, please identify the required
Not required.
testing frequency, treatment standards, reporting requirements, and whether water filters are included.
SOW Section 2.2, p.9
Please identify the target glycol concentration required for freeze protection. If glycol concentration is found below the required target during inspection, please confirm whether correction is included in preventive maintenance or treated as corrective maintenance.
Scope revised to identify government furnished materials. We will have the specific glycol concentration fluid available for contractor use.
SOW Section 2.2, p.10
Please confirm the required condenser and free cooling coil cleaning frequency for chillers, including whether cleaning is required quarterly, annually, or only as needed based on inspection findings.
The contractor is required to clean the condensers and free-cooling coils as part of the annual chiller maintenance.
SOW Section 2.4, p.10;
SOW Section 2.7, pp.12–13
Please confirm whether exhaust fans, dampers, and split systems associated with the harmonic filter, Power Quality, Barrier IIA, CGBP, or related building systems are included in the inspection and maintenance scope.
Not required.
SOW Section 2.2, pp.8–10
Please confirm whether process loop water testing and treatment, pump and expansion tank inspections, piping and fitting inspections, tightening of unions and flange gaskets, repair or replacement of cracked fittings, and water flow device maintenance, including Omega paddlewheel maintenance, are included in the chiller or BAS maintenance scope.
Not required.
31 SOW Section
2.4 p. 10
Are there any exhaust fans and the dampers associated with Split Systems?
Not required.
SOW Section
2.5 pp. 10-12
What are the expectations of the BAS maintenance?
Examples below:
Sensor Calibration & Verification
Inspect for dust, heat stress, loose wiring
Test backup battery voltage; replace below 2.8V or older than 3 years
Review firmware, apply patches, check I/O mapping and trending logs
Stroke modulating valves end-to-end;
verify open/close positions.
Not required.
SOW Section 5, p. 14
Please provide a list of known existing deficiencies, out of-service conditions, recurring alarms, and deferred maintenance items for each asset category. Please also confirm that correction of preexisting deficiencies …
The SOW does not provide a comprehensive list of existing deficiencies, out-of-service conditions, recurring alarms, or deferred maintenance items for each asset category. Deficiencies identified during preventive maintenance shall be documented and addressed in accordance with the applicable contract and Task Order requirements.
Section H, p.
Verbal CORs requests are not permissible; all authorized repairs which cause in an increase in price is only authorized by a warranted Contracting OƯicer. Repair work requiring separate pricing shall be authorized through a Task Order issued by an authorized Contracting OƯicer. The contractor shall provide a quote for the repair work, and the contractor shall not proceed with separately priced repair work until the quote has been accepted and the applicable Task Order has been issued. A COR or TPOC request identifies the need for work but does not independently authorize separately priced repair work.
SOW Section 5, p. 14;
QASP, p. 21
… Revised scope.
SOW Section 7, pp. 15–16
Contractor, subcontractor, and vendor personnel requiring unescorted access must meet the applicable Government security and access requirements. Personnel who do not qualify for unescorted access shall coordinate escorted access with the Government representative. Urgent service requirements do not automatically waive applicable security requirements.
SOW Section 2.5, pp. 10–12
The SOW identifies the equipment and systems included within the scope but does not state that the Government will furnish a complete package consisting of all current
O&M manuals, product data, prior maintenance reports, asset history, prior maintenance cost data, passwords or credentials, software backups, and configuration records.
Information maintained by the Government may be made available to the contractor as appropriate and in accordance with applicable security and access requirements.
File details come from the government source that posted it. Updated .