Performance Work Statement_31023.pdf

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

JOINT BASE CHARLESTON (JBC)

WATERSIDE SECURITY SENSORS (WSS)

WATERSIDE TRAFFIC REPLICATION (WTR)

FORCE PROTECTION DIVISION

AIR FORCE LIFE CYCLE MANAGEMENT CENTER (AFLCMC/HBU)

HANSCOM AFB, MA

27 JANUARY 2023

DOCUMENT: JBC-WSSWTR-PWS-001 (23JAN23)

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors for Administrative and Operational Use, 23 January 2023. Other requests for this document shall be referred to Force Protection Division, (AFLCMC/HBU), 3 Eglin Street, Bldg. 1612, Hanscom

AFB, MA 01731-2100.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

This page intentionally left blank.

DOCUMENT REVISIONS

DATE CHANGES

This page intentionally left blank.

TABLE OF CONTENTS

Section Page

1.0 PURPOSE

1.1 Scope

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Specifications, Standards, and Handbooks

2.1.2 Order of Precedence

3.0 REQUIREMENTS OVERVIEW

3.1 Tactical Security Location and Site

3.2 Contract Kick-Off

3.3 Watercraft Operations

3.3.1 Communications

3.3.2 Watercraft Behavior

3.4 Reporting and Close-Out

4.0 MANAGEMENT AND REPORTING

4.1 Program Management

4.2 Federal, State and Local Law Violations

4.3 Safety

4.4 Program Security

4.5 Electronic Data Interchange (EDI)

5.0 DELIVERABLES

1.0 PURPOSE

The mission of the Force Protection Integrated Base Defense Security System (IBDSS) Modernization Branch (AFLCMC/HBUM) is to rapidly deliver and integrate innovative IBDSS solutions in support of the Security Forces warfighter at fixed site and tactical locations across the globe. The objective is to acquire modern electronic security system solutions that add to a scalable and modular sensor suite to meet the diverse set of requirements from a variety of government stakeholders.

1.1 Scope

This Performance Work Statement (PWS) defines the required activities to provide Waterside Security (WSS) sensor observable water vessel traffic at the TC Dock on the Cooper River perimeter on Joint Base Charleston (JBC), South Carolina. The Contractor shall provide project, technical, and administrative support for project oversight toward achieving contract requirements. The on-site technical support coverage shall ensure there is no gap in support and response time capabilities (ref. Para 4). The Contractor shall manage the overall efforts of this delivery order and interface with the Government program office. The Contractor’s project management shall monitor, control, coordinate, and deploy a support capability to execute all site requirements supporting research on watercraft behavior in waterways abutting JBC base perimeters.

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Specifications, Standards, and Handbooks. The following specifications, standards, and handbooks, of the exact revision listed below, form a part of this document to the extent specified herein.

AF LIFE CYCLE MANAGEMENT CENTER (AFLCMC), HANSCOM AFB

IBDSS/ESE Security 15 Jun 11 Integrated Base Defense Security Classification Guide System / Electronic Security Equipment

(IBDSS/ESE) Security Classification Guide

Supply Chain Risk 15 Jan 14 Integrated Base Defense Security Management Plan System Program Supply Chain Risk

Management (SCRM) Plan

CUI Non-Nuclear CMD List 13 May 21 Non-Nuclear Configuration Management Database (CMD) Equipment Approval

ESE-TP-0023 Current Master Test and Turnover Plan

(Copies of above documents are available from AFLCMC/HBU, 3 Eglin Street, Bldg. 1612, Hanscom

AFB, MA 01731-2100.)

Non-Nuclear IBDSS SSP Ver.2 20 Nov 18 Non-Nuclear Integrated Base Defense Security System (IBDSS) System Security Plan (SSP) Version 2

IBDSS SSPs Current IBDSS System Security Plans Command Control Display Equipment and appropriate Annexes

(Copies of above documents are available from AFLCMC/HBU, 3 Eglin Street, Bldg. 1612, Hanscom

AFB, MA 01731-2100.)

AIR FORCE

AFPAM 63-113 17 Oct 13 Program Protection Planning for Life Cycle Management

(Copies of the above documents are available at: http://www.e-publishing.af.mil/)

2.1.2 Order of Precedence. In the event of a conflict between this document and the references cited herein, the more stringent requirement shall take precedence, unless directed otherwise by the Contracting Officer (CO). Nothing in this PWS, however, supersedes applicable federal, state and local codes and regulations unless a specific exemption has been obtained.

3.0 REQUIREMENTS OVERVIEW

The Contractor shall introduce four vessels spanning three categories of watercraft into the waterways abutting JBC, in South Carolina.

The required watercraft are:

1. Class A – John Boat, Jet Ski

2. Class I – Fishing Boat (Center Console)

3. Class II – Deep Sea Fishing Boat

The Contractor shall operate the watercraft in vicinity of (IVO) the TC Dock, exact location to be provided during contract kick-off, and shall operate each watercraft for two business days in coordination with the local Security Forces Squadron (SFS). The Contractor shall operate the watercraft in compliance with all local, state, and federal requirements of the waterway management. Operation of the watercraft shall include all normal authorized waterway activity, and specific operation may be specified during each operation window in contact with local SFS.

http://www.e-publishing.af.mil/)

3.1 Tactical Security Location and Site

The Contractor shall coordinate with base security and government liaison to perform tasks at the TC Dock on JBC of the Cooper River, South Carolina.

3.2 Contract Kick-Off

The Contractor shall coordinate a virtual kick-off meeting with Government personnel within 30-days of contract award to discuss details in a DRAFT Project Plan for watercraft availability and scheduling. Final Project Plan delivery shall be IAW with the CDRL. (CDRL A001)

3.3 Watercraft Operations

The Contractor shall, in compliance with agreed schedule, operate the selected watercraft IVO TC Dock, JBC, South Carolina for a total of five days of watercraft operations. Each vehicle shall be operated for 40 hours in the five day period in the following modes: Transiting, Idle - Non Transiting, and Off -Anchored, for a total of 160 hours. The estimated usage per Class is as follows:

Class A (2 Vessels): Run 8 hours, Off 3 hours, Idle 10 hours Class I (1 Vessel): Run 8 hours, Off 2 hours, Idle 5 hours Class II (1 Vessel): Run 6 hours, Off 3 hours, Idle 6 hours

In the event of inclement weather preventing any operations, one additional week of operations shall be coordinated with the Government.

3.3.1 Communication. The Contractor shall provide fully trained technical personnel with demonstrated ability to operate watercraft.

3.3.2 Watercraft Behavior. Watercraft behavior shall be determined by the test procedures established on the dates of execution.

3.4 Reporting and Close out

The Contractor shall deliver a written report on the watercraft operations conducted and observable information from the JBC waterways and perimeter. Reporting shall include, at minimum, any observations or risks of the waterway which impact normal operation of watercraft, and any observable biological elements. The report shall not be above controlled unclassified information (CUI) and shall be delivered NLT 14 days after the completion of watercraft operations. (CDRL A002)

4.0 MANAGEMENT AND REPORTING

The Contractor shall provide project planning, organization, staffing and control structures to the lowest practical level, and other tools as needed, to enable sufficient oversight for ongoing assessment of project performance and to plan tasks throughout the PoP. The Contractor shall ensure all planning, project control, quality, schedule, technical and financial objectives are met, by establishing strict project control processes to ensure mitigation of risks, minimal schedule variances, and adherence to budget.

4.1 Project Management. The Contractor shall provide project, technical, and administrative support for project oversight toward achieving contract requirements. The on-site technical support coverage shall ensure there is no gap in support and response time capabilities. The Contractor shall manage the overall efforts of this delivery order and interface with the Government program office. The Contractor’s project management shall monitor, control, coordinate, and deploy a support capability to execute all site requirements.

4.2 Federal, State and Local Law Violations

The Contractor shall perform the requirements of this contract in such a manner as to not violate any federal, state, or local laws, orders or instructions, to include all Codes of Federal Regulations (i.e., Occupational Safety and Health Act, Environmental Protection Act). The Contractor shall be solely responsible for any reporting requirements and repercussions resulting from such violations. No work requirements directed in this PWS shall supersede applicable laws and regulations. However, if conflicts arise in the interpretation of applicable rules and regulations, the Contractor shall notify the CO, in writing, and the CO will make the final determination.

4.3 Safety

The Contractor shall coordinate with each base safety office and shall be required to follow the guidance presented in the base safety briefing, covering topics such as: Occupational Safety and Health Administration, American National Standards Institute and National Fire Protection Agency standards, Mishap Reporting/Investigation, Environmental and HAZMAT Handling, Hazardous Chemical Reporting, Transporting HAZMAT, and Environmental Act Violations. The Government will provide force protection for Contractor employees commensurate with that given to Government personnel.

The Contractor shall coordinate with installation Security Forces to ensure compliance with base security requirements; installation and restricted area access; and escort requirements

4.4 Project Security

The Contractor shall ensure all key personnel which provide direct labor (for example, Project Manager, Liaison, IDS Designer and Draftsman) assigned to this contract shall be of U.S. citizenship. The Contractor shall implement a security program that safeguards Controlled Unclassified Information (CUI) IAW Contractor’s approved internal security processes. The security program shall be consistent with the National Industrial Security Program Operating Manual (DoD 5220.22M) and IBDSS/ESE Security Classification Guide.

4.5 Electronic Data Interchange (EDI)

The Contractor shall deliver CDRL data to the Government via the CDRL-specified e-mail addresses NLT than the delivery date also specified by the applicable CDRL item(s). The Contractor shall submit documentation in electronic formats compatible with Microsoft Windows operating system, and IAW the CDRL requirements. This requirement does not preclude Contractor delivery of hard copy CDRL items as required IAW with applicable CDRL instructions.

5.0 Deliverables

Contractor shall provide the following deliverables on contract. All CDRLs shall be provided in Contractor format.

CDRL DID Deliverable Description QTY Final Delivery

A001

DI-ADMN-

81249C (Meeting Agenda)

Project Plan

Provide project, technical, and administrative support for project oversight toward achieving contract requirements

NLT 4 days prior to onsite support.

A002

DI-QCIP-

81890 (Test

Report) Test Report

Deliver written report on the watercraft operations conduct and observable information from the JBC waterways and perimeter observations

NLT 14 days from conclusion of operations.