RKE2 Senior Engineering Support SOW.pdf

PERFORMANCE WORK STATEMENT (PWS)

for

CAOC-X RANCHER KUBERNETES ENVIRONMENT (RKE2) SUPPORT

at

JOINT BASE LANGLEY EUSTIS (JBLE) - 805 COMBAT TRAINNIG SQUADRON /

CAOC-X

1. INTRODUCTION. This Performance Work Statement (PWS) defines the requirements for the Contractor to provide senior-level RKE2 Subject Matter Expertise (SME) with the Engineering, Installation, Functional/Cyber Post Configuration, Performance Tuning, Validation, Technician Training, Troubleshooting and Execution support as further defined in this PWS at the 805 Combat Training Squadron / CAOC-X on Joint Base Langley-Eustis (JBLE), VA.

2. SCOPE. The contractor will provide RKE2 software and associated products/interfaces support to the

CAOC-X. All installs will be done in a hard airgap, i.e. SIPR.

2.1. Period of Performance. 365 days from contract award.

2.2. Place of Performance. The place of performance is Joint Base Langley-Eustis (JBLE), VA

2.3. Hours of Operation. The Contractor shall routinely work during normal operating hours of the site. Monday through Friday (0800-1700 hrs. Eastern), excluding federal holidays and base specific “Down Days”. “Down Days” can be identified by the government to the contractor once a detailed schedule has been given to the government. Any site work requested by the Contractor to be performed outside of normal duty hours shall be coordinated with the government’s contracting officer at least 21 working days in advance. Contractor shall accomplish the installation with minimum disruption of daily office activities.

2.4. Holidays/Down Days. The Contractor shall not perform work under this contract on US Federal holidays or site-unique down-days unless expressly authorized by the government’s contracting officer and coordinated with the base POC. Observed federal holidays for 2024 and 2025 period are:

• Independence Day - 4 July

• Labor Day – 2 September

• Columbus Day – 14 October

• Veterans Day - 11 November

• Thanksgiving Day – 28 November

• Christmas Day - 25 December

• New Year’s Day - 1 January

• Martin L. King Day – 20 January

• Washington's Birthday – 17 February

• Memorial Day – 26 May

3. REQUIREMENTS:

3.1. Management. The 805 CTS/CAOC-X shall serve as the focal point and COR to ensure Air Force and Department of Defense (DoD) standards are met throughout the period of performance of this project. All project actions shall be coordinated through the 805 CTS/CAOC-X Engineering Office.

3.2. Support Requirements. The 805 CTS/CAOC-X has requirements for senior level expertise supporting the design, installation, update, functional and cyber configuration, deployment, system validation, execution and troubleshooting of our RKE2 hosting environment for integration of new Command and Control (C2) capabilities for demonstrations, experimentation, user evaluations, etc. in support of the warfighter.

3.3. Integrated Master Schedule (IMS). The 805 CTS/CAOC-X shall serve as the focal point for the IMS.

3.4. Kick-Off Meeting. The contractor shall conduct a contract kick-off meeting at CAOC-X within 10 business days after contract award on a date coordinated and approved by the Government. The contractor will present any limiting factors related to supporting the RKE2 environment within

CAOC-X.

3.5. Experience with following products: The contractor shall have experience with the following:

• Grafana dashboards for instrumentation, both Prometheus and Loki are acceptable as data sources.

• Istio Service Mesh for bringing in geographically separate organizations into our current mesh. Shall the contractor have more experience with another service mesh such as Hashicorp (IBM) Consul that would be acceptable as long the contractor can assist with moving our current apps to another Mesh that has SIPR reciprocity.

• Knowledge with Markdown language to assist with writing documentation for continuity into an internal Wiki.

• Any experience with secrets management such as Bitnami’s Kube Seal or Conjur OSS that doesn’t require a Hardware Security Module (HSM) would be preferable, but not a hard requirement.

T

3.6. Security Requirements. The contractor shall:

3.6.1. Security Clearance. For each individual requiring base access in support of this project, the contractor shall enter into the Defense Information Security System (DISS) required personnel information. Contractors will identify their security officer to verify security clearances. Stated work and associated products shall be performed at a minimum of an active DoD SECRET security clearance. Personnel will be required to obtain a Common Access Cards (CAC) and complete Information Assurance Training for access to the AF network.

All CAC requests shall first be coordinated with the contractor’s security officer and then forwarded to the Government to verify CAC necessity. Classified systems access will be coordinated via the CAOC-X account management process.

3.6.2. Department of Defense (DoD) Directive 8570-1M Requirements. Per DoD Directive 8570, Contractor network installation personnel are required to possess Information Assurance Training (IAT) Level 2 Certification prior to starting work on this contract. To achieve this certification level, the Contractor is required (at a minimum) to have a Secret Clearance, CAC, Information Assurance Training, Need to Know, and an IAT Level 2 certification (CompTIA Security+ is most common).

3.7. Base, Restricted and Controlled Area Access. All contracted personnel shall comply with the base security policies for access to the base installation. The contractor shall coordinate with the site POC to obtain and return temporary badges and vehicle registrations. The contractor shall comply with AFFARS 5352.242-9000 Offeror Access to Air Force Installations that shall take precedence over this paragraph. Virginia is a participant in the Homeland Security REAL ID Act.

Contractor shall ensure compliance for all personal requiring access to Joint Base Langley-Eustis.

3.7.1. When applicable, the contractor shall coordinate with the site POC for security badges for access to restricted and/or controlled areas. Contractor personnel shall wear these badges at all times while in the secure areas. Personnel performing this work shall be U.S. citizens and have no criminal record. If access is denied, the contractor shall provide appropriately cleared personnel for access.

3.7.2. The contractor shall ensure company ID Badges are worn at all times that identify the individual, company name, and clearly indicate the wearer is a contractor.

3.7.3. Without notice, contractor access to base or work area may be delayed due to unannounced or un-projected government operational/mission requirements.

3.7.4. Personnel performing this work shall be U.S. citizens and have no criminal record. If access is denied, the contractor shall provide appropriately cleared personnel for access.

3.8. Risk Management. The 805 CTS/CAOC-X shall serve as the focal point for all Risk Management on this effort.

3.9. Requirements Verification. The 805 CTS/CAOC-X shall serve as the focal point for all Risk Management on this effort.

3.10. Safety. The contractor shall conform to the applicable regulations contained in the Operational Safety and Health Administration (OSHA) standards and comply with all local, state and federal safety guidelines.

3.10.1. Accident / Incident Reporting and Investigation. The Contractor shall record and report all available facts relating to each instance of accidental damage to Government property or injury to either Contractor or Government personnel to the Base Safety Office and COR. The Contractor shall secure the scene of any accident and wreckage until released by the accident investigative authority through the Contracting Officer. If the Government elects to conduct an investigation of the incident, the Contractor shall cooperate fully and assist the Government personnel until the investigation is completed.

3.11. Configuration Management (CM) and Risk Management Framework (RMF). The contractor shall:

3.12. Before installing any commercial or government software on a CAOC-X system, the vendor shall coordinate all media, documentation, etc. through the sites Configuration Control Board (CCB).

3.13. Check into CM team any Contractor developed “As-built” package illustrating the configuration of network, software, users, groups, permissions, configurations, lockdowns, etc.

of the CAOC-X RKE2 environment.

3.14. All software and hardware used for this effort must be accreditable using the RMF process. 805 CTS/CAOC-X ISSM shall serve as the focal point for all RMF efforts.