SAM_PAO Chiller SOW Draft 07 April 2026.pdf

PDF 256 KB Posted

Attached to
Sources Sought - Polyalphaolefin (PAO) chillers and remote manifolds diagnosis and repair
Solicitation number
15797
Issued by

About this file

This is a Statement of Work (SOW) for the U.S. Air Force Software Directorate, dated April 6, 2026 (Version 1), for contract 521 SWES to diagnose and repair communication faults between Polyalphaolefin (PAO) chillers and remote manifolds at Hill Air Force Base (HAFB).

The contractor must provide all necessary personnel and equipment to troubleshoot and identify the root cause of communication failures between PAO chillers located in the Mechanical Room and remote manifolds in labs 263, 265, 185, and 266, then implement necessary repairs to restore full communication and functionality. The contractor must be a Subject Matter Expert (SME) on the specific PAO chiller system and initiate repairs as soon as possible to mitigate mission-critical risk, as the backup system failure has left laboratories dependent on a single primary PAO system. Performance will occur on-site at HAFB in an unclassified area. Travel may be required, and a testing laptop is only needed in the Mechanical Room. The contractor must deliver two Contract Data Requirements List items: Diagnostic Results of Investigation/Root Cause (Exhibit A001) and Results of Repairs (Exhibit A002), both due 30 days after testing. The government will provide necessary working space, utilities, and facility access but will not furnish equipment or materials. The contractor must comply with all security, force protection, antiterrorism, OPSEC, COMSEC, and data protection requirements, including OPSEC training for personnel with access to critical information and adherence to CUI marking standards. The contractor is responsible for obtaining and returning identification credentials within three business days of contract completion and must schedule all facility visits through the Government Sponsor with escort requirements.

View the file

Other files

File Type Posted
QUESTIONS AND ANSWERS.pdf PDF
Sources Sought Synopsis_04.22.2026.pdf PDF

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

STATEMENT OF WORK (SOW)

521 SWES

U.S AIR FORCE

4/6/2026 Version 1 ii

SOW Modification History

Date Change Paragraph # 06 April 2026 SOW Creation 07April 2026 SOW Updates iii

TABLE OF CONTENTS

1 INTRODUCTION

1.1 Purpose

2 DESCRIPTION OF WORK/OBJECTIVES/SERVICES

3 REFERENCE DOCUMENTS AND STANDARDS

3.1 Applicable Documents and Standards

4 CDRL SUMMARY

5 GENERAL INFORMAION

5.1 Travel

5.2 Place/Period of Performance

5.3 Data Rights Management

5.4 Cybersecurity and Data Protection Plan

5.5 Government Furnished Property (GFP)/Government Furnished Equipment (GFE)/ Government Furnished Materials (GFM)

5.6 Government-Provided Support

5.7 Security

5.8 Base Access

5.9 Display of Identification

5.10 Obtaining/Returning Identification

5.11 Communications Security (COMSEC)

5.12 Operations Security (OPSEC)

5.13 Conflicts of Interest

5.14 Inherently Governmental Functions

5.15 Conservation of Utilities

6 GOVERNMENT OBSERVATIONS

7 ENVIRONMENTAL

Appendix A – CDRLS

1 INTRODUCTION

1.1 Purpose

This requirement is to diagnose and repair communication faults between the Polyalphaolefin (PAO) chillers and remote manifolds located in labs 263, 265, 185, and 266. The work will require access to the PAO chillers in the Mechanical Room and the remote manifolds within each specified lab.

1.2 Scope

The contractor will be required to provide all necessary personnel and equipment to perform the following tasks:

• Troubleshoot: Investigate and identify the root cause of the communication faults between the PAO chillers and the remote manifolds.

• Repair: Implement the necessary repairs to restore full communication and functionality to the affected systems.

1.3 Background

This program is focused on ensuring the operational readiness of critical laboratory facilities that rely on a Polyalphaolefin (PAO) chiller system for cooling. PAO is a synthetic hydrocarbon oil used as a specialized coolant in high-performance applications, particularly in the aerospace and defense sectors, due to its excellent thermal stability and dielectric properties.

In this context, the PAO chiller system is essential for regulating the temperature of sensitive equipment in multiple labs (263, 265, 185, and 266).

The current situation is precarious because a communication fault has rendered the backup PAO system inoperative. The labs are now entirely dependent on a single, primary PAO system. This creates a significant operational risk: if the primary system fails, the entire laboratory will be forced to shut down, halting all related mission activities. Therefore, the immediate repair of the backup system is a mission-critical priority.

2 DESCRIPTION OF WORK/OBJECTIVES/SERVICES

The core requirement of this project is to restore the backup PAO chiller system to full operational status. This will be accomplished by diagnosing and repairing the existing communication faults between the main PAO chillers, located in the Mechanical Room, and the remote manifolds in each of the four designated labs.

To achieve this, the following services and actions are required:

• A contractor shall conduct a hands-on investigation at the facility to identify the root cause of the communication failures and execute the necessary repairs.

• The contractor must be a Subject Matter Expert (SME) on this specific PAO chiller system.

• The contractor shall initial the work to repair and restore full communication and functionality to the affected systems as soon as possible to mitigate the risk of a complete lab shutdown.

3 REFERENCE DOCUMENTS AND STANDARDS

3.1 Applicable Documents and Standards

The contractor shall comply with and maintain internal procedures aligned with the references and documents listed below. If the contractor does not already have established processes, the contractor shall utilize the references and documents for implementing program requirements.

The web site for Air Force Instructions (AFIs), Air Force Manuals (AFMANs), Air Force Forms (AF Form): is as follows and can be obtained from the Internet web site below. The contractor will be responsible for researching and abiding by all applicable supplements not contained in the table below. http://www.e-publishing.af.mil. All other references are available via general internet searches. Every effort has been made to ensure the listed references are current as of this writing, it is the Contractors responsibility to ensure the most recent version is utilized when referenced.

Regulation Date Description

Hill AFB Facility Design Standard 18 Feb 2021 General Reference

United Facilities Code (UFC) 1- 200-01

01 Oct 2020 Dept of Defense (DoD) Building Code

Intelligence Community Directive

(ICD) 705

Sensitive Compartmented Information Facilities

Joint Special Access Program Implementation Guide

11 April 2016 General References

National Security Council Instruction 7700

General References

4 CDRL SUMMARY

4.1 CDRL Information

4.1.1 Contract data shall be delivered electronically IAW the corresponding requirement for each Data Item listed in the table below. The contractor shall prepare and deliver data to the Government in contractor format except where specific forms are required. Data shall be formatted IAW the requirements specified for each Data Item listed in the table below.

4.1.2 The contractor shall ensure all technical data, including drafts and working papers, are marked and controlled IAW appropriate distribution statements and export control warning notices.

Exhibit Title SOW Paragraph

Delivery

A001 Diagnostic Results of Investigation/ Root

Cause

2 30 Days After Testing

A002 Results of repairs 2 30 Days After Testing

5 GENERAL INFORMAION

5.1 Travel

May be required as testing, diagnosis and repair shall be performed on site.

5.2 Place/Period of Performance

Testing and diagnostics on site at Hill Air Force Base (HAFB). Diagnose the reported communication faults between PAO chillers and remote manifolds in labs 263, 265, 185 and

266. Testing requires access to PAO chillers in ‘Mechanical Room’ and access to remote manifolds in each lab. A testing laptop is only required in ‘Mechanical Room.

5.3 Data Rights Management

All data rights under this contract shall be managed IAW applicable data rights clauses outlined in the FAR and DFARS. Specific clauses governing data rights are identified within this contract and shall dictate the level of rights granted to the Government for data, technical data, and computer software. The Contractor is responsible for adhering to these clauses to ensure full compliance. Any limitations on data rights must align with those specified in the completion of FAR 52.227-15, "Representation of Limited Rights Data and Restricted Computer Software."

Only the restrictions proposed and accepted under this clause will be considered valid under this contract.

5.4 Cybersecurity and Data Protection Plan

The contractor will not be using our network or IP. The PAOs are self-contained and will be accessed from our mechanical room that is in an unclassified area.

5.5 Government Furnished Property (GFP)/Government Furnished Equipment (GFE)/ Government Furnished Materials (GFM)

GFP/GFE/GFM is not required under the performance of this contract. GFP/GFE/GFM will not be issued to the contractor.

5.6 Government-Provided Support

The Government will provide necessary working space, including heat, light, ventilation, and electrical outlets for the use of contractors’ personnel. The Government will provide access to the necessary facilities where the equipment resides. Government telephones shall be used for official business only. The contractor shall be responsible for safeguarding all Government property provided for contractor use.

5.7 Security

5.7.1 The contractor shall comply with all Security, Force Protection, and Antiterrorism requirements. The contractor shall comply with local unit in- and out-processing procedures for all contractor personnel to ensure proper security-related briefings and debriefings are accomplished. Specific in- and out-processing checklists may be included at the task order level.

5.7.2 The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any Government property, facility, and installation at the sole discretion of competent Government authority if that authority determines such action is necessary to protect or preserve Government property, safety, and security, or to maintain good order and discipline.

5.7.3 Contractors shall not use any other form of identification to access any Government installation or facility while working on this contract except the issued credentials associated with the awarded contract or task order. Example:

using a military retiree card to access an installation to work on a contract.

5.7.4 Foreign nationals (FN) will not be escorted, or sponsored, onto the installation without being properly vetted. Any request must follow 309 SWEG OI 16-1404, Security Requirements section 7. FNs must be approved for access via the Foreign Disclosure Office and Air Force Office of Special Investigations

(AFOSI).

5.7.5 Should a security incident occur, the contractor shall:

5.7.6 Immediately report to the site location Group SM and COR all available facts related to each instance.

5.7.7 Take such precautions as the SM may reasonably require for security purposes.

5.7.8 Take reasonable and prudent action to establish control of the scene, prevent further violation, and to preserve evidence until released by proper authority.

5.7.9 Cooperate fully and assist Government personnel as the Government conducts an investigation of the violation.

5.7.10 Participate in the investigation until it is complete.

5.8 Base Access

The contractor shall schedule all visits and coordinate Base entry by contacting their Government Sponsor. The contractor will be escorted at all times.

5.9 Display of Identification

5.9.1 Air Force-issued identification badges and any contractor badges shall be worn at or above the waistline during the individual’s duty hours when not in a production or designated Foreign Object Damage (FOD) hazard area. The contractor shall procure their own lanyard and holder through their company identifying themselves as a contractor.

5.10 Obtaining/Returning Identification

5.10.1 During performance of the contract, the contractor shall be responsible for obtaining required identification for newly-assigned personnel. Returning of credentials shall be done on the last day of the contract when the PoP has ended or the requirement is considered complete. At the completion or termination of the contract, the contractor shall have three business days to out-process and terminate all their network user accounts and to return all access cards and base identification badges to the Security Manager (SM).

5.11 Communications Security (COMSEC)

5.11.1 All communications with DoD organizations are subject to COMSEC review.

5.11.2 The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations.

5.11.3 The contractor shall adhere to COMSEC procedures any time they place a call to, or receive a call from, a DoD organization.

5.11.4 The contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with official DoD information.

5.12 Operations Security (OPSEC)

5.12.1 Introduction of personnel electronic devices into Government spaces, laptops, tablet personal computers (PC)s, cellular phones, cameras, recording devices, and data recording/storage devices are strictly controlled and forbidden in most cases.

Contractor-issued equipment required for the performance of work shall be approved by the 309 SWEG SM, which may include both Collateral IPO and SAP APO offices. Photography and recording are not allowed in restricted areas and controlled areas except for official use and by approved photography letter only. NOTE: Unless otherwise stipulated in the contract, contact the Installation Public Affairs or SM for approval.

5.12.2 The contractor shall not discuss Government operations in public or over unprotected or unencrypted communications. Official Business CUI may only be transmitted as directed in the SOW as it adheres to CUI guidelines.

5.12.3 The Contractor shall not post to company websites, publications, newsletters, or other media any images, data, or information that reveal sensitive Government operations, personnel, equipment, and/or classified or CUI. When in doubt, company press releases related to this contract shall be coordinated through the Public Affairs Office prior to release.

5.12.4 The contractor shall not disclose to unauthorized third parties or post to unofficial sites (including all social networking sites) any images, data, or information that reveals sensitive Government operations, personnel, or equipment, including: tactics, techniques and procedures, production or work schedules, any visible or concealed modifications, upgrades, additions to Air Force installations, property or weapons or equipment; increases, change, or decreases in work/deployment frequency or Government personnel, project schedules, logistics or material delivery schedules; specialized equipment orders, deliveries, shipments, etc. (Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC § 793.) Unauthorized disclosures and attempts to solicit this type of information by unauthorized third parties or others not affiliated with this contract shall be reported to the SM and/or installation SFS, COR, and, if applicable, the company FSO and/or the Defense Security Service.

5.12.5 The contractor shall practice OPSEC and implement countermeasures to protect critical information (CI) and other sensitive unclassified information. Protection of CI shall include the adherence to and execution of countermeasures which the contractor initiates or as provided by OPSEC Manager or installation OPSEC Program Manager, for CI on or related to the SOW.

5.12.6 The contractor shall mark and protect any information IAW CUI to include e-mail and adhere to all CUI standards and policies.

5.12.7 Contractors who have access to CI shall have OPSEC training IAW AFI 10-701 (July 2019), Operations Security (OPSEC) table 4.1 Air Force OPSEC Training Requirements pg 32.

5.12.8 Contractor security admin may be required to access unclassified, CUI, Confidential, Proprietary and/or Sensitive Information held by the United States

Air Force (USAF) relating to the tasks to be performed under this contract. This information may belong to other contractors, third parties, or the USAF.

Contractor security admin personnel shall provide a completed copy of the nondisclosure Agreement to the Government PM, COR, and CO prior to performing work under this contract.

5.13 Conflicts of Interest

The Contractor shall not assign to the contract or task order performance, any person, including any employee of the U.S. Government, if employing that person would create a conflict of interest under any law, regulation or policy of the United States Government. Additionally, the Contractor shall not assign to the contract or task order performance, any person who is an employee of the Department of the Air Force, either military, reservist, or civilian, unless such person seeks and receives approval according to DoD Directive 5500.7-R and any other applicable regulation or policy of the Department of the Air Force or its subordinate commands, as applicable, including but not limited to Air Force Materiel Command.

5.14 Inherently Governmental Functions

5.14.1 None of the functions to be performed under this requirement are inherently Governmental. Additionally, no part of this SOW, the basic contract or any task order issued under the basic contract shall be construed to require the Contractor to provide personal services to the Government. The contractor shall comply with this SOW in its entirety.

5.14.2 The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes or has reason to believe any actions constitute or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the PM, COR, and PCO immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

5.15 Conservation of Utilities

The contractor shall instruct their employees in utilities conservation practices. The contractor shall be responsible for operating under conditions which prevent the waste of utilities.

6 GOVERNMENT OBSERVATIONS

During the PoP, Government personnel other than CO may, from time-to-time, observe contractor operations. However, these personnel may not interfere with contractor performance.

7 ENVIRONMENTAL

Weather Hazards. The contractor may encounter hazardous weather conditions including snow, heavy rain, lightning, extreme dust, and other conditions that warrant appropriate precautions.

APPENDIX A – CDRLS

1 INTRODUCTION
1.1 Purpose
2 DESCRIPTION OF WORK/OBJECTIVES/SERVICES
3 REFERENCE DOCUMENTS AND STANDARDS
3.1 Applicable Documents and Standards
The contractor shall comply with and maintain internal procedures aligned with the references and documents listed below. If the contractor does not already have established processes, the contractor shall utilize the references and documents for impl...
The web site for Air Force Instructions (AFIs), Air Force Manuals (AFMANs), Air Force Forms (AF Form): is as follows and can be obtained from the Internet web site below. The contractor will be responsible for researching and abiding by all applicable...
4 CDRL SUMMARY
4.1.1 Contract data shall be delivered electronically IAW the corresponding requirement for each Data Item listed in the table below. The contractor shall prepare and deliver data to the Government in contractor format except where specific forms are ...
4.1.2 The contractor shall ensure all technical data, including drafts and working papers, are marked and controlled IAW appropriate distribution statements and export control warning notices.
5 GENERAL INFORMAION
5.1 Travel
5.2 Place/Period of Performance
Testing and diagnostics on site at Hill Air Force Base (HAFB). Diagnose the reported communication faults between PAO chillers and remote manifolds in labs 263, 265, 185 and 266. Testing requires access to PAO chillers in ‘Mechanical Room’ and access ...
5.3 Data Rights Management
All data rights under this contract shall be managed IAW applicable data rights clauses outlined in the FAR and DFARS. Specific clauses governing data rights are identified within this contract and shall dictate the level of rights granted to the Gove...
5.4 Cybersecurity and Data Protection Plan
The contractor will not be using our network or IP. The PAOs are self-contained and will be accessed from our mechanical room that is in an unclassified area.
5.5 Government Furnished Property (GFP)/Government Furnished Equipment (GFE)/ Government Furnished Materials (GFM)
5.6 Government-Provided Support
5.7 Security
5.7.1 The contractor shall comply with all Security, Force Protection, and Antiterrorism requirements. The contractor shall comply with local unit in- and out-processing procedures for all contractor personnel to ensure proper security-related briefin...
5.7.2 The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any Government property, facility, and installation at the sole discretion of competent Government authority if that author...
5.7.3 Contractors shall not use any other form of identification to access any Government installation or facility while working on this contract except the issued credentials associated with the awarded contract or task order. Example: using a milita...
5.7.4 Foreign nationals (FN) will not be escorted, or sponsored, onto the installation without being properly vetted. Any request must follow 309 SWEG OI 16-1404, Security Requirements section 7. FNs must be approved for access via the Foreign Disclos...
5.7.5 Should a security incident occur, the contractor shall:
5.7.6 Immediately report to the site location Group SM and COR all available facts related to each instance.
5.7.7 Take such precautions as the SM may reasonably require for security purposes.
5.7.8 Take reasonable and prudent action to establish control of the scene, prevent further violation, and to preserve evidence until released by proper authority.
5.7.9 Cooperate fully and assist Government personnel as the Government conducts an investigation of the violation.
5.7.10 Participate in the investigation until it is complete.
5.8 Base Access
The contractor shall schedule all visits and coordinate Base entry by contacting their Government Sponsor. The contractor will be escorted at all times.
5.9 Display of Identification
5.9.1 Air Force-issued identification badges and any contractor badges shall be worn at or above the waistline during the individual’s duty hours when not in a production or designated Foreign Object Damage (FOD) hazard area. The contractor shall proc...
5.10 Obtaining/Returning Identification
5.10.1 During performance of the contract, the contractor shall be responsible for obtaining required identification for newly-assigned personnel. Returning of credentials shall be done on the last day of the contract when the PoP has ended or the req...
5.11 Communications Security (COMSEC)
5.11.1 All communications with DoD organizations are subject to COMSEC review.
5.11.2 The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations.
5.11.3 The contractor shall adhere to COMSEC procedures any time they place a call to, or receive a call from, a DoD organization.
5.11.4 The contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with official DoD information.
5.12 Operations Security (OPSEC)
5.12.1 Introduction of personnel electronic devices into Government spaces, laptops, tablet personal computers (PC)s, cellular phones, cameras, recording devices, and data recording/storage devices are strictly controlled and forbidden in most cases. ...
5.12.2 The contractor shall not discuss Government operations in public or over unprotected or unencrypted communications. Official Business CUI may only be transmitted as directed in the SOW as it adheres to CUI guidelines.
5.12.3 The Contractor shall not post to company websites, publications, newsletters, or other media any images, data, or information that reveal sensitive Government operations, personnel, equipment, and/or classified or CUI. When in doubt, company pr...
5.12.4 The contractor shall not disclose to unauthorized third parties or post to unofficial sites (including all social networking sites) any images, data, or information that reveals sensitive Government operations, personnel, or equipment, includin...
5.12.5 The contractor shall practice OPSEC and implement countermeasures to protect critical information (CI) and other sensitive unclassified information. Protection of CI shall include the adherence to and execution of countermeasures which the cont...
5.12.6 The contractor shall mark and protect any information IAW CUI to include e-mail and adhere to all CUI standards and policies.
5.12.7 Contractors who have access to CI shall have OPSEC training IAW AFI 10-701 (July 2019), Operations Security (OPSEC) table 4.1 Air Force OPSEC Training Requirements pg 32.
5.12.8 Contractor security admin may be required to access unclassified, CUI, Confidential, Proprietary and/or Sensitive Information held by the United States Air Force (USAF) relating to the tasks to be performed under this contract. This information...
5.13 Conflicts of Interest
5.14 Inherently Governmental Functions
5.14.1 None of the functions to be performed under this requirement are inherently Governmental. Additionally, no part of this SOW, the basic contract or any task order issued under the basic contract shall be construed to require the Contractor to pr...
5.14.2 The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contra...

5.15 Conservation of Utilities

6 GOVERNMENT OBSERVATIONS
7 ENVIRONMENTAL
Appendix A – CDRLS

File details come from the government source that posted it. Updated .