1. SOW - WTP - WWTP CCTV_19Aug26.pdf

Whiteman Air Force Base

STATEMENT OF WORK

Delivery/Installation of CCTV Security Cameras at Water Treatment

Plant/Waste-water Treatment Plant

Bldgs. 2001, 2005, 5034, 5035, 5036, And 50010

509 CES/CEO

19 August 2026

1.0 Introduction

1.1 Facility

1.1.1 The objective of this project is to provide new security cameras, monitors, video storage, and playback capability Whiteman AFB Water and Waste-water Treatment Plants and associated facilities.

2.0 Scope of Work

2.1 Description of Work

2.1.1 The contractor will coordinate with the government date and time of delivery and installation. A minimum of 48-hours’ notice is prior to delivery/installation is required.

2.1.2 Installation.

2.1.2.1 The contractor shall provide all labor, materials, tools, transportation, vehicles, and equipment necessary to install wired infrastructure cameras on the exterior of bldgs. 2001, 2005, pump station to the west of 2005, light pole east side 5032, 5034, 5035 (interior), 5036, 5048, 50010, and headworks station at waste-water plant. A total of 13 cameras will be installed, 11 cameras shall have the PTZ (pan-tilt-zoom) capability to be repositioned remotely from each of the monitoring sites, 2 cameras installed inside 5035 and headworks station are static cameras.

2.1.2.2 Once installed, the contractor shall connect the installed cameras and equipment to the standalone system without the need for internet connection, allowing feed to be viewed, monitored, controlled, and footage pulled for all water and waste-water treatment cameras from both monitor stations located in bldg. 2005 and 5034.

2.1.2.3 The camera system for building 2005 (central location) shall entail a system server, video storage with a (minimum 30 day continuous NVR/DVR video storage), and network connecting to all cameras at both plants, allowing for redundant control of the systems and the ability to centralize critical viewing footage via fiber optic cabling. System hard drives and servers are required to be mounted in existing server rack at building 5034 and a new rack installed in building 2005 to house new components. Complete system will be standalone without the need for internet connections to update, record, or store recordings, monitor cameras and update software if required. Any switches required for operation need to be managed switches with POE (power over ethernet) capabilities.

2.1.2.4 The Contactor shall install two viewing monitors: one each in bldg. 2005 and 5034

(minimum size for monitors is 40 inch). Both monitoring systems will be wall mounted: at facility

2005 it will be mounted on the south wall of the laboratory and at facility 5034 it will be mounted on the south wall. Also, the system must be provided with 3-axis keyboard to control camera operations. Existing outlets will be utilized to power the monitoring stations.

2.1.2.5 Approximate locations and heights of each camera are shown in the pictures in

Attachment 1. Government will provide mounting poles at NE corner of 2008 and at 5033

(headworks).

2.1.3 Testing and/or commissioning.

2.1.3.1 The contractor shall provide a one-year warranty on all newly installed system components, installation, and operation of the system.

2.1.3.2 The contractor shall perform testing of cameras and DVR after installation and resolve any/all issues or conflicts. Contractor shall ensure the system is operating trouble-free. The contractor will perform initial overview and provide at least a one-hour operator training for the system. The contractor shall also provide manuals and any other training materials.

2.1.4 Site restoration.

2.1.4.1 Any damage caused as a result of camera installation, paint, flashing, etc., shall be the responsibility of the contractor to repair.

2.1.4.2 Any damage to the grounds resulting from contractor vehicles or equipment shall be repaired and seeded by the contractor.

2.2 Supplementary Requirements

2.2.1 Parameters.

2.2.1.1 All work by the contractor will be performed Monday–Friday from 0730 to 1600.

2.2.1.2 The contractor is responsible for receiving and unloading all deliveries associated with this project.

2.2.1.3 The contractor is responsible for storage. The Government will not provide storage facilities. New cameras and equipment will not be stored outdoors or exposed to the weather.

2.2.1.4 Existing exterior cameras are to be left inoperable and as-is; they are not being removed as part of this effort. Existing conduits and fiber to cameras may be re-used, the government will not remove them. If direct buried cable is utilized it is required to have a built-in tracer wire.

2.2.1.5 The contractor shall be responsible for any damage to grounds, buildings, and equipment therein from their work performed, but not limited to walls, doors, door frames, and outdoor grassy areas.

2.2.1.6 The contractor shall keep the work site free from accumulations of waste material. Prior to leaving the work site each day, the contractor shall do an inspection of the immediate and adjacent work areas to ensure that all waste has been removed, and the area maintains a safe and tidy appearance. All waste shall be handled, transported, stored, and disposed of at the expense of the contractor in accordance with all applicable federal, state, and local laws.

3.0 Standards and Codes

3.1 Unified Facilities Criteria (UFC)

3.1.1 UFC 4-021-02 – Electronic Security Systems (ESS)

3.1.2 DAFGM 2024-32-01- Civil Engineer Control Systems Cybersecurity

4.0 Deliverables and Submittals

4.1 Products and Materials

4.1.1 Cameras

4.1.2 Monitors

4.1.3 System server

4.1.4 Proposed route of wired infrastructure

5.0 Attachments:

Attachment 1: two location photos

Attachment 2: additional verbiage

ATTACHMENTS

Attachment 1

Attachment 2

HEALTH AND SAFETY ON GOVERNMENT INSTALLATIONS

In performing work under this contract on a Government installation, the contractor shall:

1. Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this contract; and

a. Take such additional immediate precautions as the contracting officer may reasonably require for health and safety purposes.

2. The contracting officer may, by written order, direct Department of the Air Force Occupational

Safety and Health (AFOSH) Standards and/or health/safety standards as may be required in the performance of this contract and any adjustments resulting from such direction will be in accordance with the Changes clause of this contract.

3. Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the contracting officer, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

ELIMINATION OF USE OF

CLASS I OZONE DEPLETING SUBSTANCES (ODS)

Contractors shall not:

1. Provide any service or product with any specification, standard, drawing, or other document that requires the use of a Class I ODS in the test, operation, or maintenance of any system, subsystem, item, component, or process; or

a. Provide any specification, standard, drawing, or other document that establishes a test, operation, or maintenance requirement that can only be met by use of a Class

I ODS as part of this contract/order.

2. For the purposes of Department of the Air Force policy, the following products that are pure (i.e., they meet the relevant product specification identified in AFI 32-7086[AR2] ) are Class I ODSs:

a. Halons: 1011, 1202, 1211, 1301, and 2402;\

b. Chlorofluorocarbons (CFCs): CFC-11, CFC-12, CFC-13, CFC-111, CFC-112, CFC-113, CFC-114, CFC-115, CFC-211, CFC-212, CFC-213, CFC-214, CFC-

215, CFC-216, and CFC-217, and the blends R-500, R-501, R-502, and R-503;

and

c. Carbon Tetrachloride, Methyl Chloroform, and Methyl Bromide.

SECURITY INCIDENT REPORTING AND PROCEDURES

(a) The contractor shall follow the below guidance when a contract contains a DD Form 254, DOD Contract Security Classification Specification:

1. The contractor shall notify the Government Contracting Activity (GCA) of any security incident involving the potential or actual loss, compromise, or suspected compromise of http://static.e-publishing.af.mil/production/1/af_a4/publication/afi32-7086/afi32-7086.pdf https://usaf.dps.mil/sites/AFCC/AQCP/KnowledgeCenter/SitePages/DAF-Contracting-Compass/Part-23---Environment,-Sustainable-Acquisition,-and-Material-Safety.aspx?CID=dc7c8322-d1f4-42a2-9d82-62dcc05ddf79#_msocom_2

Top Secret, Secret, and/or Confidential information, referred to as classified information, when the incident is discovered at the contractor’s location.

i. The contractor shall conduct the requisite inquiry(ies) in accordance with 32 CFR

Part 117 and Cognizant Security Office (e.g., Defense Counterintelligence and

Security Agency) guidance.

2. Security incidents occurring at government performance locations where the contractor is categorized as a visitor will be processed and reported in accordance with government host security procedures.

3. Security incidents involving the potential or actual loss, compromise, or suspected compromise of Special Access Program and/or Sensitive Compartmented Information is under the jurisdiction of the GCA and the contractor shall follow GCA guidance in lieu of this requirement.

4. This requirement does not relieve the contractor from reporting requirements set forth in

32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and

Security Agency).

5. This requirement does not relieve the contractor from adhering to security incident guidance set forth by its Cognizant Security Office (e.g., Defense Counterintelligence and

Security Agency).

6. The contractor is responsible for ensuring all applicable subcontracts include these security incident reporting requirements.

7. If the lost or compromised information is beyond the jurisdiction of the U.S. Government and cannot be recovered (e.g., media leak, public website posting, or loss in a foreign country), the notification and location of the compromise (e.g., geographic location of unrecoverable equipment) shall be classified commensurate with the classification level of the compromised material to prevent further unauthorized disclosure in accordance with DoDM5200.01 Volume 3, Enclosure 6. The contractor will contact the GCA for instructions on how to communicate the notification prior to submission in all cases where lost or compromised information is beyond the jurisdiction of the U.S.

Government and cannot be recovered.

8. The contractor shall ensure all notifications determined to contain classified information are properly transmitted and marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

(b) Initial Notification of Security Incident

1. The contractor shall provide an initial notification of security incident to the GCA within

72 hours of discovery of any incident where classified information may have been subjected to loss, compromise, or suspected compromise for all security incidents involving the contractor’s location unless otherwise directed by contract requirements.

2. The initial notification to the GCA is considered Controlled Unclassified Information

(CUI) [CUI category OPSEC, FEDCON Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and shall be transmitted to the GCA through authorized means (e.g., encrypted email or DoD

SAFE).

3. If the initial notification contains classified information either by content or through classification through compilation, the contractor will contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

4. The initial notification shall contain the following information, as available at the time of report:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the notification to be classified by compilation, do not include and indicate as such in the initial notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Brief description of incident prompting initial notification. If incident directly or indirectly involved government personnel, include government personnel name(s), email address(s), and office information.

vii. Communicate whether it is possible for the contractor to properly retain and/or provide the suspected information in question for GCA classification review and/or damage assessment.

(c) Final Notification of Security Incident

1. The contractor shall provide a final notification to the GCA 10 business days from date of initial notification. If the final notification cannot be made 10 business days from the date of the initial notification, the contractor shall request an extension and receive approval in writing from the GCA.

2. The final notification to the GCA does not relieve the contractor from reporting requirements set forth by 32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and

Security Agency).

3. The final notification will be considered CUI [CUI category OPSEC, FEDCON

Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and sent through authorized means (e.g., encrypted email or DoD

SAFE).

4. If the final notification contains classified information either by content or through classification through compilation, the contractor is required to contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

5. The final notification shall contain the following information:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the report to be classified by compilation, do not include this information, and indicate as such in the final notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Detailed description of incident and include the following:

Sequence of events: When, where, and how did the incident occur?

What persons, situations, and/or conditions caused or contributed to the incident?

If incident originated with government personnel, include government personnel name(s), email address(s), and office information.

Include the name(s), email address(s), and office information of all government personnel involved, either directly or indirectly, as appropriate

If classified information is alleged to have been physically lost (e.g., lost classified document), what steps were taken to locate the material?

If security incident was categorized as a data spill, include measures taken to properly sanitize all impacted assets.

vii. Corrective actions taken to prevent future occurrences

viii. Result of inquiry (e.g., loss, compromise, suspected compromise, or no compromise)

ix. A copy of the supporting DD Form 254(s) associated with prime contract. If DD Form 254 cannot be provided, the contractor shall indicate the reasons why in the final report.

(d) Definitions

“32 CFR Part 117” means National Industrial Security Program Operating Manual. “Business days” means days that do not include federal holidays or weekends.

“Classified information” means information the government designates as requiring protection against unauthorized disclosure in the interest of national security, pursuant to E.O. 13526, Classified National Security Information, or any predecessor order, and the Atomic Energy Act of 1954, as amended. Classified information includes national security information (NSI), restricted data (RD), and formerly restricted data (FRD), regardless of its physical form or characteristics (including tangible items other than documents).

“Cognizant security agencies (CSAs)” means agencies E.O. 12829, sec. 202, designates as having National Industrial Security Program implementation and security responsibilities for its own agencies (including component agencies) and any entities and non-CSA agencies under their cognizance. The CSAs are: Department of Defense (DoD); Department of Energy (DOE);

Nuclear Regulatory Commission (NRC); Office of the Director of National Intelligence (ODNI);

and Department of Homeland Security (DHS).

“Cognizant Security Office” means an organizational unit to which the head of a CSA delegates authority to administer industrial security services on behalf of the CSA.

“Compromise” means an unauthorized disclosure of classified information.

“Data spill” means electronic transmission of classified information via unsecure means such as classified information transmitted over an unclassified network.

“DD Form 254” means the Department of Defense Contract Security Classification

Specification.

“Derivative classification” means incorporating, paraphrasing, restating, or generating in new form information that is already classified, and marking the newly developed material consistent with the classification markings that apply to the source information. Includes the classification of information based on classification guidance. The duplication or reproduction of existing classified information is not derivative classification.

“Final Notification of Security Incident” means contractor (or subcontractor) notification to the

Government Contracting Activity communicating the results of the inquiry conducted.

“Government Contracting Activity” means an element of a Component designated and delegated by the Component head or designee with broad authority regarding acquisition functions to include the appropriate resources and personnel (e.g., contracting officers or their designees, program managers, program offices, and security personnel) as defined in DoDM 5220.32, Volume 1.

“Initial Notification of Security Incident” means the contractor’s (or subcontractor) notification to the Government Contracting Activity of a security incident occurrence and surrounding details of occurrence.

“Inquiry” means the initial fact-finding and analysis process to determine the facts of any security incident and conducted to determine whether or not there was a loss of classified information or whether or not unauthorized personnel had, or could have had, access to the information.

“Loss” means the inability to physically locate or account for classified information.

“Security classification guide” means a documentary form of classification guidance issued by an Original Classification Authority that identifies the elements of information regarding a specific subject that must be classified and establishes the level and duration of classification for each such element.

“Security Incident” means an incident that results from the mishandling of classified information.

“Suspected Compromise” means when a result of no loss or compromise of classified information cannot be determined with certainty.