Attachment 1 SOFTEAMS III PWS Ver 3.1.pdf

PDF 1023 KB Posted

Attached to
Special Operations Forces Training, Engineering and Maintenance Support 4 (SOF TEAMS 4) Federal contract opportunity
Solicitation number
W900KK-23-R-XXX2
Issued by
Department of the Army Materiel Command Contracting Command Orlando Contracting Center

View the file

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

PWS-2017-086

W900KK-19-C-0017

Version 3.1

1 June 2022

CUI

PERFORMANCE WORK STATEMENT (PWS) FOR

160TH SPECIAL OPERATIONS AVIATION REGIMENT (AIRBORNE)

[SOAR(A)] SPECIAL OPERATIONS FORCES TRAINING,

ENGINEERING AND MAINTENANCE SUPPORT (SOF TEAMS) III

U.S. ARMY

PROGRAM EXECUTIVE OFFICE

FOR SIMULATION, TRAINING AND INSTRUMENTATION

(PEO STRI)

PROJECT MANAGER FOR SPECIAL OPERATIONS FORCES

TRAINING SYSTEMS

(PM CT2 STS)

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3276

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD Contractors Only (Operational Use / Critical Technology) (2021). Other requests for this document must be referred to US DoD PEO STRI, 12211 Science Dr., Orlando, FL, 32826

WARNING -This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

Controlled by: PEO STRI Controlled by: PM STS CUI Category: CTI Distribution: D POC: John Farrell, 270-956-3703

W900KK-19-C-0017

Version 3.1

X Prepared By:

Systems Engineer John Farrell

Approved By:

Chief Engineer Alf Betancourt

Submitted By:

APM Darrell Wright

W900KK-19-C-0017

ii

REVISION LOG

Version Number Date Revision Description

1.0 26 Mar 2018 STIII RFP PWS

1.1 24 April 2018 Clarified efforts in paragraphs 3.5.5 and 3.7 and definitions in paragraph 4.2

1.2 14 May 2018 Added paragraphs 3.2.3 thru 3.2.8

1.3 10 July 2018 Corrected subparagraph numbering in paragraph 3.1.9.2.1, corrected references in paragraphs 3.3.1 and 4.2, and clarified efforts in paragraph 3.5.1.2

1.4 23 Jan 2019 Added paragraph 3.1.9.12 for RMF Contingency and Support, changed availability in paragraph 3.5.1 from 95% to 98%, and various administrative changes.

1.5 31 July 2019

- Modified para. “3.1.8.5 OPSEC Program”, by removing “In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure this individual becomes OPSEC Level II certified per AR 530-1.” Per OPSEC officer email dated 1 May, 2019.

- Modified para. “3.5.1.2 Contracted Training Time – Ft. Campbell, KY” to remove 13 hour CTT when two 47 CMS or 60 CMS are available for training which should have been incorporated in revision 1.4.

- Per GFP tasker from USSOCOM J42 modify to replace; CDRL A002 - DI-MGMT-80259, Physical Inventories Report with DI-ILSS- 80727, Government Furnished Material (GFM) by National Stock Number.

Removed following CDRLs: CDRL A017 - DI-MGMT-81947A, Contract Government Furnished Property Listing

- CDRL A018 - DI-MGMT-81947A, GFP Receiving Status Report

- CDRL A019 - DI-MGMT-81947A, Monthly CAP Purchase Request Status Report

2.0 28 Jan 2020

- Move UMS Support to Sabre Army Airfield (SAAF) Modification – -- 3.5.1.2, Removed UMS CTT verbiage -- 3.5.1.3, Change to RESERVED -- 3.5.1.7, Added SAAF UMS CTT Support (Option) -- 3.5.6, Over and Above Services clarification -- APPENDIX A, DBGS-Lite, SimLab, Other Updates

-- Global Change ULLS-A to ACN -- Typo corrections and clarifications

2.1 13 Feb 2020

Removed version 2.0 “APPENDIX A” additions below;

- 6.9.2 MRETS Components:

-- VR Kits: 8 VR MPK systems -- 2 MACE/ARMOR AR/VR stations -- 4 Immersive Training Environment computers (Back End Trainers) -- 2 Virtual Pilot Training systems. Components include computers, routers, seat system with flight controls.

- 6.15 Visual Database Toolkit

2.2 1 May 2020

- 3.1.9.4 - Changed “Xacta IA” to “eMASS” per ISSO

- 3.1.9.11.i - Replaced “weekly” with list of governing documents

- 3.5.1.7.1 UMS Support - Increased support from 8 hours per day to 16 hours per day (OPTION)

- 6.9.2 - Added back systems removed in version 2.1 “APPENDIX A”

- 6.15 - Visual Database Toolkit (VDBTK) Support added

- 6.16 - Presagis Vega Prime CDB Viewer Added

2.3 13 Jan 2021 - Rescinded

2.4 11 Feb 2021

- Updated references, manuals, regulations, etc. and DIDs

- 3.5.1.2, 6.17 - Added LASAR Containerized Flight Training Device (CFTD) CTT and description

- 3.5.1.7 - Removed funding options for more than 8 hours of UMS CLS if required

- 3.5.1.7.1 - Updated to 16 hrs of CLS (OPTION), 3.5.1.7.2 - Add 2nd SAAF UMS CLS for 20 hrs/day CTT (OPTION)

- 3.5.1.8 – Added MRETS Emerging Efforts

- 3.5.2 – REMOVED Engineering Support Contractor Performance Factor (ESCPF)

- 6.3.2 - Updated LASAR CMS description

- 6.18 - Added HELI CRAFT simulator

2.5 12 May 2021

- 3.5.1.7 - UMS Support – Merged past UMS CLS support requirements and added new 2nd UMS CLS support requirement.

- 5.54 Controlling Office address

- 6.13 “APPENDIX A”

3.0 20 Jan 22

-- Updated website links, added CUI markings, references, manuals, regulations, etc. and DIDs -- 3.1.7 Security – Added Army Directive 2014-05/AR 190-13 requirement -- 3.1.8.1 AT Level 1 Training – Changed from 30 to 60 days -- 6.6.2 MH60 CMS Description – Updated flight tool to Apple IPAD flight tool and added IOS laptop -- 6.9.2 MRETS Components – Added existing Mediasite system and RS3 acquired, 2 MH60 Crew Station mockups

3.1 1 Jun 22

- 3.1.9 - Cybersecurity Measures - various updates

- 3.2.2 - Configuration Management - Added baseline and cold-start processes

- 3.2.3 - Added “Juneteenth National Independence Day”

- 3.3.2 - Spares Maintenance - added software/hardware spares scanning requirement

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page iii

CUI

1. SCOPE

Modification and Changes

Background

2. APPLICABLE DOCUMENTS

Government Documents

Department of Defense (DoD) Security Instructions, Directives, and Manuals

Non-Government Documents

3. REQUIREMENTS

Program Management

3.1.1 Organization Structure

3.1.2 Financial Management

3.1.3 Core Competencies

3.1.3.1 Transition with Outgoing/Incoming contractor

3.1.3.2 Third Party Associate Contractor Agreements (ACAs)

3.1.3.3 Program Meetings and Reviews

3.1.3.4 Program Communications

3.1.3.5 Accident and Incident Notification and Investigation

3.1.4 Hazardous Materials (HAZMAT) Management

3.1.5 Government Furnished Information (GFI)

3.1.6 Government Purpose Rights

3.1.7 Security

3.1.7.1 Physical Security

3.1.8 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

3.1.8.1 AT Level 1 Training

3.1.8.2 Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

3.1.8.3 iWATCH Training

3.1.8.4 Army Training Certification Tracking System (ATCTS) Registration for Contractor Employees Who Require Access to Government Information Systems

3.1.8.5 OPSEC Program

3.1.8.6 Requirement for OPSEC Training

3.1.8.7 Cybersecurity/Information Technology (IT) Training

3.1.8.8 Cybersecurity/IT Certification

3.1.8.9 Handling or Access to Classified Information

3.1.8.10 Threat Awareness Reporting Program (TARP)

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page iv

CUI

3.1.8.11 Technology Control

3.1.9 Cybersecurity Measures

3.1.9.1 Certification Requirements

3.1.9.2 Information System Security Officer (ISSO)

3.1.9.3 Authority To Operate (ATO)

3.1.9.4 Authorizing Official (AO) Specific Instructions

3.1.9.5 Baseline Documentation

3.1.9.6 System Security Plan

3.1.9.7 Security Technical Implementation/Requirements Guides

3.1.9.8 Architecture Analysis

3.1.9.9 Assessment

3.1.9.10 Risk Management Framework (RMF) Support

3.1.9.11 Cybersecurity/Systems Management

3.1.9.12 RMF Contingency and Support

3.1.10 Quality Assurance

3.1.10.1 QA Assistance during audits, inspections, and surveillances

3.1.10.2 QA Reporting

3.1.10.3 QA Response to Corrective Action Requests (CAR)

3.1.10.4 QA Follow-up

3.1.10.5 Quality Assurance Verification of Efforts

3.1.10.6 Quality Assurance Tracking System

Administration

3.2.1 Operational Support

3.2.1.1 General Administration

3.2.1.2 Reporting

3.2.1.3 Contractor Manpower Reporting (CMR)

3.2.2 Configuration Management (CM)

3.2.2.1 Configuration Management Plan

3.2.2.2 Configuration Management Baselines

3.2.2.3 As-Built Configuration List (ABCL)

3.2.2.4 Control

3.2.2.5 Reports

3.2.3 Government Installation Work Schedule

3.2.4 Reimbursement of Travel, Per Diem and Special Material Costs

3.2.5 PRESERVATION, PACKAGING, PACKING AND MARKING

3.2.6 DISCLOSURE, USE AND PROTECTION OF PROPRIETARY INFORMATION

3.2.7 ADDITION OR SUBSTITUTION OF KEY PERSONNEL (SERVICES)

3.2.8 Organizational and Consultant Conflicts of Interest (Services)

Maintenance Support

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page v

CUI

3.3.1 Systems Maintenance

3.3.1.1 Hardware Maintenance

3.3.1.2 Software Maintenance

3.3.2 Spares Maintenance

3.3.3 Support Equipment Maintenance

3.3.4 Shipment

Logistics Support

3.4.1 Logistics Support Package (LSP)

3.4.2 Government Furnished Property (GFP) Inventory

3.4.3 Repair Parts

3.4.4 Spares

3.4.5 Support Equipment

3.4.6 Test, Measurement and Diagnostic Equipment (TMDE)

3.4.7 Consumables and Expendables

3.4.8 Transportation, Shipping and Receiving

3.4.9 Diminishing Manufacturing Sources/Material Shortages (DMS/MS) and Supportability .. 36

Operations Support of TADSS

3.5.1 Contractor Performance Factor (CPF)

3.5.1.1 Contractor Performance Factor (CPF) Calculation

3.5.1.2 Contracted Training Time – Ft. Campbell, KY

3.5.1.3 RESERVED

3.5.1.4 Contracted Training Time – Ft. Lewis, WA (Option)

3.5.1.5 Contracted Training Time – Hunter Army Airfield (HAAF), GA (Option)

3.5.1.6 Contracted Weekend Support Time - Ft. Campbell, KY

3.5.1.7 UMS Support, Sabre Army Airfield (SAAF), Ft. Campbell, KY

3.5.1.8 MRETS Emerging Efforts

3.5.2 Engineering Support Contractor Performance Factor (ESCPF)

3.5.2.1 Engineering Support CPF Calculation

3.5.2.2 Contracted Engineering Support Time

3.5.2.3 Scheduled External Engineering Notification

3.5.3 Operations Schedule

3.5.4 Start-Up/Preparation

3.5.4.1 Readiness Checks

3.5.5 TADSS Activation and Deactivation

3.5.5.1 TADSS Installation

3.5.5.2 TADSS De-Activation

3.5.5.3 TADSS Relocation

3.5.6 Over and Above Services

3.5.7 Overtime/Surge

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page vi

CUI

Engineering Support

3.6.1 Advanced Computer Systems Support

3.6.2 Requirements Analysis (RA) and Concept Exploration (CE)

3.6.3 Engineering Feasibility/Trade Studies and Analysis

3.6.4 Technical Data Management

3.6.4.1 Technical Data Security

3.6.4.2 Publication Change Requests (PCRs)

3.6.4.3 TADSS Training Equipment Summary

3.6.4.4 Develop ‘Orange Book’

3.6.5 Networking, Interfaces and Interoperability Support

3.6.6 Distributed Operations

Modification or Upgrade Installation

3.7.1 Pre/Post Modification Inspections

3.7.2 Minor Modification Support

4. ACRONYMS AND DEFINITIONS:

Acronyms

Definitions

5. CONTRACT DATA REQUIREMENTS LIST (CDRL) INSTRUCTIONS

Applicable Documents

Data Deliveries

5.2.1 Delivery Dates

5.2.2 Tailored Data Items

5.2.3 Approval of Data

5.2.4 Re-submittal of Data

5.2.5 Final Submittal of Data

5.2.6 DD Form 250 Requirements

5.2.7 Classified Data

5.2.8 Letter Of Transmittal (LOT)

Modification To Data Requirements

Data Preparation

Marking Technical Documentation

5.5.1 Distribution Marking System

5.5.2 Marking Technical Data

5.5.3 Distribution Statements

5.5.4 Controlling Office

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page vii

CUI

5.5.5 Export-Controlled Warning Statement

5.5.6 Destruction Notice

5.5.7 Method Of Transmittal

5.5.8 CDRL Index listing

6. APPENDIX A - SOF TEAMS III (STIII) Training Aids, Devices, Simulators, and Simulations (TADSS) Descriptions

MH-47G/MH-60M Desktop Trainer (DTT)/Cockpit Academic Procedural Tool (CAPT)

6.1.1 DTT/CAPT Purpose/Description

6.1.2 CAPT Major Components/Systems (per station):

Universal Mission Simulator (UMS-1, UMS-2)

6.2.1 UMS Purpose

6.2.2 UMS Description

A/MH-6M Light Assault/Attack Reconfigurable Combat Mission Simulator (LASAR-1 CMS)

6.3.1 LASAR CMS Purpose

6.3.2 LASAR CMS Description

A/MH-6M DTT

MH-47G Combat Mission Simulator (MH47-1, MH47-2 CMS)

6.5.1 MH47 CMS Purpose

6.5.2 MH47 CMS Description

MH-60M Combat Mission Simulator (MH60-1, MH60-2 CMS)

6.6.1 MH60 CMS Purpose

6.6.2 MH60 CMS Description

NEXUS XL Storage Access Network (SAN)

6.7.1 NEXUS XL SAN Purpose

6.7.2 NEXUS XL SAN Description

CMS Debrief Stations

6.8.1 CMS Debrief Station Purpose

6.8.2 CMS Debrief Station Description

Mission Rehearsal Exercise Training System (MRETS)

6.9.1 MRETS Purpose/Description

6.9.2 MRETS Components (Not all inclusive)

6.9.3 MRETS Software (Not all inclusive)

Simulation Accident Investigation Support Lab

6.10.1 Purpose

6.10.2 Description

W900KK-19-C-0017

Version 3.1

1 June 2022 Table of Contents

Section Title Page viii

CUI

RUNTIME X-IO Storage Area Network (SAN)

Just-In-Time (JIT) Publisher CDB 3.0

FSIMNET

Mission Rehearsal Operations Center (MROC)

6.14.1 MROC Purpose

6.14.2 Description:

6.14.3 MROC Major Components:

Visual Database Toolkit [Aechelon Database Generation System (DBGS) – Lite]

Presagis Vega Prime CDB Viewer

LASAR Containerized Flight Training Device (LASAR-2 CFTD)

6.17.1 LASAR CFTD Purpose

6.17.2 LASAR CFTD Description

HELI CRAFT

6.18.1 HELI CRAFT Purpose

6.18.2 HELI CRAFT Description

W900KK-19-C-0017

Version 3.1

1 June 2022

CUI

PERFORMANCE WORK STATEMENT (PWS)

160th Special Operations Aviation Regiment (Airborne) [160th SOAR(A)]

Special Operations Forces Training, Engineering and Maintenance Support

(SOF TEAMS) III

1. SCOPE

This Performance Work Statement (PWS) defines the efforts required for non-personal technical service support for the 160th SOAR(A) Training Aids, Devices, Simulators and Simulations (TADSS) and associated support systems/equipment to include but not limited to; Integration Labs, test beds, Networks, FIBER connectivity, Audio/Visual, Debrief, etc. The contractor shall provide management and logistical support to include labor, materials, consumables, tools and test equipment, maintenance and repair activities, minor engineering modifications, training, website, cybersecurity and hardware/software/documentation configuration management to maintain all devices in a state of full operational readiness. The contractor shall also provide fielding, logistical and relocation (as necessary) services to support future outstation requirements as they arise. This effort will be Firm Fixed Price (FFP) with Cost Plus Fixed Fee (CPFF) provisions. The FFP portion shall include all labor, Program Management Office requirements, website and all Phase-In and Phase-Out costs. The CPFF portion shall include over and above work requests, repair actions and service agreements, spares, tools and test equipment purchases.

Modification and Changes

As future TADSS(s) are developed and fielded, or if existing devices require relocation, de-installation and support; these efforts may be added to the contract via Engineering Change Proposal (ECP). At any time during the life of this contract, the Government may add or delete 160th SOAR(A) TADSS, support systems, maintenance and operational support requirements, and/or additional simulators and simulations requiring Life Cycle Contractor Support (LCCS) services.

Background

The need for this capability is identified in the United States Special Operations Command (USSOCOM) Memorandum for PEO STRI, dated 28 July 2004. This memorandum requires that LCCS efforts conducted at the 160th SOAR(A) be consolidated and managed under the purview of Product Manager Special Operations Forces Training Systems (PM STS) starting in FY05. This Performance Work Statement defines the effort for the 160th SOAR(A) Special Operations Forces Training, Engineering, and Maintenance Support (SOF TEAMS) III. A list and brief description of the current 160th SOAR(A) TADSS is located in Appendix A of this PWS. These TADSS support both real-world mission rehearsal and training requirements.

The SOA TADSS support the unique mission of the 160th SOAR(A) to equip, train, incident investigation and employ Special Operations Aviation (SOA) forces worldwide in support of contingency missions, the Joint Task Force (JTF) Commander and War-Fighting Geographic Combatant Commanders.

W900KK-19-C-0017

The 160th SOAR(A) Regimental S3 Simulations Officer supervises and prioritizes the operations of the SOA TADSS. The 160th SOAR(A) Systems Integration and Maintenance Office (SIMO) fields and integrates new systems and oversees the modifications to existing systems and components, provides oversight and conflict resolution with maintenance efforts to fielded systems.

The SOA TADSS are used to support the following operations (in priority order):

a) Special Operations Aviation Training Battalion (SOATB) training courses

b) Combat mission rehearsal

c) Aircrew assessments

d) Sustainment training

e) Evaluations

f) Research of flight safety and incident investigation

g) Refresher training

h) Device upgrades, certification, and fidelity testing

i) Practice for proficiency

j) Aviator familiarization

k) Capability demonstrations

l) Tactics Techniques and Procedures for Special Ops Missions

m) Battle Staff Training

n) VIP Demonstrations

2. APPLICABLE DOCUMENTS

The following documents form a part of this PWS to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this PWS, the contents of this PWS take precedence. Nothing in this PWS, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

Government Documents

OTHER PUBLICATIONS:

MIL-HDBK-61A(SE) - MILITARY HANDBOOK CONFIGURATION MANAGEMENT

GUIDANCE

W900KK-19-C-0017

Department of the Army Regulations

AR 25-1 - Army Information Technology

AR 25-2 - Army Cybersecurity

AR 380-5 - Army Information Security Program

AR 380-67 - Personnel Security Program

DA PAM 385-16 - System Safety Management Guide

DA PAM 385-10 - Army Safety Program

AR 700-138 - Army Logistics Readiness and Sustainability

AR 750-43 - Army Test, Measurement, and Diagnostic Equipment

TB 43-180 - Calibration and Repair Requirements for the Maintenance Of Army Materiel

TB 750-25 - Maintenance of Supplies and Equipment Army Test, Measurement, and Diagnostic Equipment (TMDE) Calibration and Repair Support (C&RS) Program

CNSSI 1253 - Committee on National Security Systems Instruction

(CNSSI) 1253

NIST SP 800-18 Rev. 1 - National Institute of Standards and Technology (NIST) Special Publication (SP) 800-18: Guide for Developing Security Plans for Federal Information Systems

NIST SP 800-37 Rev. 2 - National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37: Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy

NIST SP 800-53 Rev. 5 - National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Information Systems and Organizations

W900KK-19-C-0017

*Copies of the above DoD documents are downloadable from http://www.dtic.mil/whs/directives/index.html

*Copies of the above Department of the Army (DA) documents can be obtained from https://armypubs.army.mil/

Department of Defense (DoD) Security Instructions, Directives, and Manuals

04-IA-O-0001 Version 2.5 - BBP Army Password Standards

DoDD 2040.02 CE-01 - International Transfers of Technology, Articles, and Services

DoDM 5200.01 - DoD Information Security Program: Overview, Classification, and Declassification

DoD 5200.1-R - Information Security Program

DoD 5220.22-M - National Industry Security Program Operation Manual

(NISPOM)

DoDI 5230.24 - Distribution Statement on Technical Documents

DoDD 5230.25 - Withholding Unclassified Technical Data from Public Disclosure

DoDI 8500.01 - Cybersecurity

DoDI 8510.01 - Risk Management Framework (RMF) for DoD Information Technology (IT)

DoDI 8582.01 - Security of Unclassified DoD Information on Non-DoD Information Systems

DoD 8570.01-M - Information Assurance Workforce Improvement Program

Non-Government Documents

INDUSTRY STANDARDS

AIA/NAS 411 - Hazardous Materials Management Program

ANSI/EIA 649C - Configuration Management Standard http://www.dtic.mil/whs/directives/index.html

W900KK-19-C-0017

ASME-Y14.35 - Revision of Engineering Drawings and Associated Documents

ASME-Y14.100 - Engineering Drawing Practices

3. REQUIREMENTS

This Performance Work Statement (PWS) defines the requirements for non-personal technical services to support the 160th SOAR(A) TADSS. This effort consists of program management, administration, maintenance, logistics support, operational support, engineering support, and minor modifications to Special Operations Aviation (SOA) TADSS.

Program Management

The contractor shall provide an organization with the necessary resources to manage the overall SOF TEAMS III program. The contractor shall perform all management functions required to fulfill the requirements as stated in this PWS.

3.1.1 Organization Structure

The contractor shall provide an organization capable of successfully completing the requirements of this PWS, to include:

a) Provide management staffing.

b) Provide employees who possess a minimum SECRET security clearance or the ability to obtain one, prior to contract award.

c) Provide an experienced and highly competent technical staff to perform all functions identified within the scope of this PWS, where experience is defined under Key Personnel attachment of the contract.

d) Provide a capability to analyze future efforts and initiatives resulting in rough orders of magnitude (ROMs) and/or engineering change proposals (ECPs). The contractor shall provide the necessary staffing to perform these tasks with no negative impact to existing effort(s). The contractor shall provide a reach back or subcontract capability to perform these ECPs.

e) Provide qualified personnel that can travel in support of this contract.

f) Support third party vendor efforts.

3.1.2 Financial Management

The contractor shall plan, budget, schedule, and control all financial resources allocated to meet the requirements of the contract and within the funding limitations set forth under the individual contract line items. The contractor shall document, track and report the status of all appropriated funds associated with the contract, to include payments, invoices and cancellations against each contract line item and subline item. The contractor shall document and track to their internal work breakdown

W900KK-19-C-0017

structure which is consistent with their internal processes. These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status IAW the CDRL.

Deliverables: CDRL A001 - DI-MGMT-80227/T, Contractor’s Progress, Status, and Management Report

3.1.3 Core Competencies

a) Cybersecurity Measures (3.1.9 and associated subsections)

b) Configuration Management (3.2.2 and associated subsections)

c) Maintenance Support (3.3 and associated subsections)

d) Logistics Support (3.4 and associated subsections)

e) Operations Support (3.5 and associated subsections)

f) Engineering Support (3.6 and associated subsections)

g) Modification or Upgrade Installation (3.7 and associated subsections)

3.1.3.1 Transition with Outgoing/Incoming contractor

3.1.3.1.1 Transition Phase-In

The transition phase-in period will not exceed sixty (60) calendar days. During the transition phase-in period the contractor shall prepare to and assume performance responsibility for the TADSS identified in this PWS. The contractor shall take all actions necessary to minimize any impact on the operational readiness and capabilities of the TADSS during the transition phase-in. The contractor shall perform a joint property inventory with the cognizant Government representative(s) which will be initiated no later than thirty (30) days prior to the end of the transition phase-in period. After the inventory is completed and agreed to, the contractor shall be responsible for managing the inventory at all locations and be accountable for Government Furnished Property (GFP) and Government Furnished Information (GFI). The contractor shall perform transition phase-in duties to include but not limited to:

a) Staffing actions

b) Data Library

c) Setting up communications capabilities

d) Government Furnished Property (GFP) (Attachment of the contract) and Government Furnished Information (GFI) (Attachment of the contract) inventory

e) Participation in support requirements, scheduling and planning for training and other events that will occur after transition

f) Implementation of SOF TEAMS III Website

Deliverable: CDRL A002 - DI-PSSS-80727A, Government Furnished Material (GFM) by National Stock Number

W900KK-19-C-0017

3.1.3.1.2 Transition Phase-Out

If the contractor is an unsuccessful offeror in any subsequent Government solicitation for CLS of the 160th TADSS, the contractor shall, during the last sixty (60) days of this contract provide transition phase-out support to minimize any impact on the operational readiness and capabilities of the TADSS.

Repair and replacement of GFP will continue during the transition phase-out period. The contractor shall provide access to the site(s), LCCS activities, and to all documentation on a not-to-interfere basis during the new contract transition phase-in period. The outgoing contractor shall retain full responsibility for SOF TEAMS III until completion of the transition phase-out period.

No later than thirty (30) days prior to the expiration of this contract, the contractor shall coordinate and work jointly with the cognizant Government representative(s) to conduct a 100% inventory of all GFP and GFI during the transition phase-out period. The contractor shall facilitate the transfer of all SOF TEAMS Website information with the in-coming contractor. The contractor shall provide to the Government a download of all records and other support data stored in electronic systems (such as inventory control system, website) onto magnetic media. The contractor shall be responsible for supplying replacements for missing or damaged items at the end of the contract performance period.

The contractor shall provide an accurate listing of all parts at vendors for repair and all ongoing service agreements (if agreement period extends beyond annual contract performance period(s)), to include expected return dates and expiration/renewal dates. The contractor shall certify the inventory after completion of the inventory. If any GFP item(s) are not repaired or replaced under the current contract in the required transition period, the Government may initiate action to have the item(s) repaired or replaced using a work order.

Deliverables: CDRL A002 - DI-PSSS-80727A, Government Furnished Material (GFM) by National Stock Number

CDRL A016 - DI-AVCS-80700A, Computer Software Product End Items

3.1.3.2 Third Party Associate Contractor Agreements (ACAs)

The contractor shall enter into Associate Contractor Agreements (ACAs), as necessary, for exchanging data, accessing and using third party software and equipment, receiving technical support, working interface issues, transitioning LCCS and agreeing on equipment use and time for each specific work order or requirement. Signed, valid ACA’s shall be available for review upon Government request.

3.1.3.3 Program Meetings and Reviews

The contractor shall support program meetings and reviews as required with the content and purpose of each to be mutually determined and agreed upon by the IPT. The contractor shall plan the meetings and reviews to coincide with other events when possible. The contractor shall, at a minimum, be capable of providing status of the TADSS and be able to respond to data calls related to system availability, repairs and any foreseeable over and above, weekend or unscheduled maintenance through its coordination with key stakeholders to include, but not limited to the Government and other on-site contract personnel. The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at any particular conclusion, recommendation, or alternative in the accomplishment of the tasks required by the contract. The contractor shall generate and provide to the

W900KK-19-C-0017

Government the minutes of Conference and Review proceedings in accordance with (IAW) the Contract Data Requirements List (CDRL) and post the documents to the website.

The conferences, meetings, and reviews shall be considered fulfilled when all of the following items are completed:

a) All required action items, as mutually agreed by Government and contractor during the conference, have been resolved.

b) The minutes have been accepted by the Government

Deliverables: CDRL A006 – DI-MGMT-81605, Briefing Materials CDRL A010 - DI-ADMN-81250B, Conference Minutes

3.1.3.3.1 Program Management Review (PMR)

The contractor shall host and conduct quarterly PMRs for the initial base year and, shall conduct PMRs at Government discretion for all subsequent Option Years, if exercised. The PMR shall provide attendees with information regarding the issues, status, and planned activities of the program. Key SOF TEAMS III personnel from the contractor shall attend every PMR. The PMR shall be conducted IAW a jointly agreed upon schedule and meeting location. PMRs topics shall include, at a minimum:

a) Current Issues

b) Contractual Concerns

c) Quality Assurance Surveillance Plan (QASP)

d) Planned and Funded Actions or Upgrades

e) Manning and Staffing

f) Risks

g) Action Item Review

h) Summary/Conclusion

3.1.3.3.2 Integrated Project Team Approach

The contractor shall implement an Integrated Project Team (IPT) approach for this effort that includes both contractor and Government participants. The Government will act as co-chairperson for the IPT.

The IPT shall provide management oversight and overall guidance for all activities associated with this effort. The IPTs shall meet IAW a jointly agreed upon meeting schedule.

3.1.3.3.3 Post Award Conference (PAC)

The conference shall be held at 160th SOAR(A), Ft. Campbell, KY within thirty (30) calendar days following contract award. The contractor shall be prepared to discuss the phase-in plan and the respective responsibilities of all parties. The duration of the conference shall not exceed two (2) days.

The purpose of the conference is to ensure that the contractor is prepared to execute the work required

W900KK-19-C-0017

in the PWS. The contractor shall place emphasis on management plan implementation, operating procedures, transition plan and website overview.

3.1.3.4 Program Communications

The Contractor shall provide open, timely, and comprehensive sharing of information with the Government by using digital media (i.e., digital files, CDs, DVDs, etc.), and electronic messaging (i.e., email). The Contractor shall use telephonic / Web based conferencing where practical.

3.1.3.4.1 SOF TEAMS III Website

The contractor shall establish and maintain a SOF TEAMS III website. The website will be used to manage, at a minimum, all programmatic, operational, maintenance, supply and inventory data. The website shall be operational at end of contract transition. A review of the website shall be done at the first PMR with all issues resolved by the contractor prior to the next PMR. The contractor shall update website data upon completion of programmatic, maintenance, engineering, supply, operational or inventory action. At a minimum, this website information shall be updated every week by the close of business on Friday (5 PM (EST)).

The SOF TEAMS III website shall satisfy the requirements listed below:

a. Website access shall be provided to all key Government stakeholders, to be identified during the

PAC.

b. The website shall not be hosted on a Government provided server or service. The website shall be accessible by government unclassified networks.

c. Accessible twenty-four (24) hours a day, seven (7) days a week by all key Government stakeholders.

d. Provide reporting capability to include, at a minimum, export of information to Microsoft Office 2013 or later products as determined through the IPT process.

e. The capabilities for on-line review, routing, comment, electronic signature, acceptance, rejection and approval of all data shall be included.

f. The website shall include mechanisms to establish appropriate audit trails to identify the source of these responses and to maintain configuration control.

g. Program/contract action items of the contractor and its subcontractors/vendors, as well as Government action items. Each action item shall contain, as a minimum, the date noted, the assigned party or parties, a description of the action item, an ID (identification number), its current “open” or “closed” status, and the agreed to completion date. Action items shall never be cleared from the website.

h. Safety issue tracking.

i. All CDRLs (native format).

W900KK-19-C-0017

j. All CDRL DATA ITEM TRANSMITTAL/ACCEPTANCE/REJECTION (DITAR) forms.

k. Conformed Contract.

l. All Contract Modifications.

m. All Work Order Requests (WOR) and Purchase Requests (PRs).

n. Burn rates of all CPFF CLINs to include, at a minimum, the estimated-to-actual cost per WOR/PR.

o. All service agreements.

p. All contract invoices and quotes.

q. Provide backup of all associated data on the website.

r. Provide information on what resources the technical data library has and how to obtain the information.

s. No classified data shall be stored on the website.

t. The Contractor shall utilize password controls as required to protect sensitive data.

u. Quality Assurance Corrective Action Requests generated, maintained and archived as appropriate.

v. Allow determination of actual utilization and shall provide information on unused capacity.

w. Provide, but not limited to, metrics for TADSS: Utilization, Reliability (as Mean Time Between Failure (MTBF), and Maintainability (Mean Time to Repair (MTTR)).

x. Access to a repository of all SOF TEAMS Deficiency Reports (DRs).

y. The website shall include mechanisms to establish appropriate audit trails for all document revisions facilitated during the performance of this contract.

z. Thirty (30) business days prior to the end of the contract, the contractor shall provide to the Government all data, databases developed and documentation in commercial and/in non-proprietary format.

3.1.3.5 Accident and Incident Notification and Investigation

The contractor shall maintain a record of all accidents, incidents, and damage to property. In the event of an accident, incident, or discovery of a safety hazard, the contractor shall notify the appropriate local authorities as determined through the IPT process within two (2) hours and the PCO within twelve (12) hours. When a mishap occurs that involves damage to property or injury to personnel, the contractor shall immediately secure the accident scene without destroying any evidence and assist in the accident investigation. After any accident, incident, or discovery of a safety hazard the contractor shall take appropriate steps to correct the situation and shall document the corrective action taken.

W900KK-19-C-0017

Deliverable: CDRL A003 - DI-SAFT-81563A, Accident/Incident Report

3.1.4 Hazardous Materials (HAZMAT) Management

The contractor shall provide HAZMAT management in accordance with local, state, and Federal laws, regulations, policies, and procedures. The data shall be available to personnel at all applicable locations.

The contractor shall be responsible for inventorying, handling, packaging, and storing HAZMAT. The contractor shall be responsible for reporting, recording, preventing, controlling, removing, and cleaning up accidental and intentional spills of HAZMAT in coordination with the local installation HAZMAT control activity. The contractor shall be responsible for identifying HAZMAT requirements in contract technical documentation, identifying alternative materials, evaluating the suitability of identified alternatives for use, and implementing alternatives. The contractor shall be responsible for supporting the installation’s environmental coordinator, the U.S. Army Center for Health Promotion and Preventive Medicine (CHPPM), and local, state, and federal regulatory agencies in their missions. The contractor shall be responsible for the collection, inventory, documentation, packaging, and delivery of all HAZMAT waste acquired during TADSS maintenance and engineering support activities and in support of 160th SOAR(A) TADSS third party contractor modifications to the local installation HAZMAT control activity.

3.1.5 Government Furnished Information (GFI)

The Government will provide agreed upon technical data necessary to accomplish the objectives of this PWS upon contractor request, or at the earliest possible opportunity. All GFI will be provided in an as is condition. Requests for additional GFI made after award shall not be approved without prior determination and formal consent from the Government Procuring Contracting Officer (PCO). Upon completion of contract performance it shall be the contractor’s responsibility to properly pack and deliver all GFI to the Government designated location and/or to facilitate disposition with the designated Administrative Contracting Officer (ACO) associated with this contract.

3.1.6 Government Purpose Rights

Government Purpose Rights give the Government the ability to reproduce, modify, perform, display, use, disclose, or release the data for Government purposes without restriction. The contractor shall provide Government Purpose Rights in accordance with DFARS 252.227-7013 and -7014.

3.1.7 Security

SOF TEAMS III contractor personnel and subcontractors assigned to this project will require access to classified information and facilities that process classified information. All on site contractor personnel on a Government installation shall be a U.S. citizen qualified to possess and maintain an active SECRET security clearance. Contractor personnel performing work under this contract must have a SECRET-level clearance by contract award and must maintain that level of security required for the life of the contract. The security requirements are in accordance with the contract DD254. Any submission of an individual to work on site without a clearance must be approved by the Government Point of Contact (POC) at the Fort Campbell, KY facility.

Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and

W900KK-19-C-0017

Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations

The contractor shall have a law enforcement background check completed for all employees who will be entering Army-controlled installations or facilities. Documentation of these checks will be made available to the Contracting Officer’s Representative (COR) upon request. The contractor shall provide to the COR, seven (7) days in advance of the event, names and Social Security numbers (or equivalent identification numbers for non-U.S. citizens) of all employees who will need to enter Army-controlled installations or facilities. The contractor shall ensure that its employees entering Army-controlled installations or facilities have obtained access badges and passes in accordance with facility regulations and that these badges and passes are obtained in advance so as not to delay the accomplishment of contracted services. The contractor shall be responsible for coordinating with the appropriate Government point of contact at the Fort Campbell, KY security facility in the event of any personnel changes and shall adhere to local procedures for out processing and in processing of personnel. The contractor shall return all issued U.S. Government Common Access Cards, compound badges, and/or access passes to the COR when the contract is completed or when a contractor employee no longer requires access to the installation or facility.

3.1.7.1 Physical Security

The contractor shall adhere to Annex B (Intelligence) to the 160th SOAR (A) Admin SOP for safeguarding all government equipment, information, safes/vaults and other property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

3.1.8 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

3.1.8.1 AT Level 1 Training

All Contractor employees, to include Subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training in accordance with AR 381-12 within sixty (60) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected Contractor employee and Subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within thirty (30) calendar days after completion of training by all employees and Subcontractor personnel. AT level I awareness training is available at the following website: https://jko.jten.mil/courses/atl1/launch.html.

3.1.8.2 Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

Contractor and all associated Subcontractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply

W900KK-19-C-0017

with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DOD facility and access, via logon, to DOD networks on-site or remotely; (2) Remote access, via logon, to a DOD network using DOD -approved remote access procedures; or (3) Physical access to multiple DOD facilities or multiple non- DOD federally controlled facilities on behalf of the DOD on a recurring basis for a period of six (6) months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

3.1.8.3 iWATCH Training

The Contractor and all associated Subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within thirty (30) calendar days of contract award and within thirty (30) calendar days of new employees commencing performance with the results reported to the COR no later than sixty (60) calendar days after contract award.

3.1.8.4 Army Training Certification Tracking System (ATCTS) Registration for Contractor Employees Who Require Access to Government Information Systems

All Contractor employees with access to a Government information system must be registered in the ATCTS at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

3.1.8.5 OPSEC Program

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within ninety (90) calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will include the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. New and existing contractor employees must complete Level I OPSEC training annually.

3.1.8.6 Requirement for OPSEC Training

Per AR 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within thirty (30) calendar days of their reporting for duty. All Contractor employees must complete annual OPSEC awareness training. The contract shall ensure all applicable employees have completed OPSEC initial training and annual refresher training and shall certify that their work force has completed

W900KK-19-C-0017

the training through the submission of completion certificates(s) to the COR within thirty (30) calendar days of arrival on the installation. OSPEC training can be accomplished at the website:

https://jkodirect.jten.mil/Atlas2/page/coi/externalCourseAccess.jsf?v=1588955940157&course_prefix=J S&course_number=-US009.

3.1.8.7 Cybersecurity/Information Technology (IT) Training

All Contractor employees and associated Subcontractor employees must complete the DOD cybersecurity awareness training before issuance of network access and annually thereafter. All Contractor employees working cybersecurity/IT functions must comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 within six (6) months of employment.

Cybersecurity/Information Technology (IT) training can be accomplished at:

https://ia.signal.army.mil/dodiaa/default.asp

3.1.8.8 Cybersecurity/IT Certification

Per DOD 8570.01-M , Defense Federal Acquisition Regulation Supplement (DFARS) 252.239.7001 and AR 25-2, the Contractor employees supporting cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DOD 8570.01-M must be completed upon contract award.

3.1.8.9 Handling or Access to Classified Information

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret”. The Contractor shall comply with (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M) and (2) any revisions to DOD 5220.22-M.

3.1.8.10 Threat Awareness Reporting Program (TARP)

For all Contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), Contractor employees must receive annual TARP training by a counterintelligence agent or other trainer as specified in 2-4b.

3.1.8.11 Technology Control

The contractor shall adhere to the protection standards and guidance described in DoD Manual 5200.1R, the Acquisition Systems Protection Manual to prevent foreign intelligence collection and/or the unauthorized disclosure of information governed by the International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation (EAR) during the acquisition process. Distribution of unclassified Critical Program Information (CPI) (see DoD Manual 5200.1-R) shall be made in accordance with DoD directive 2040.2, International Transfer of Technology, Goods, Services, and Munitions. All such documents shall be properly marked in accordance with DoD Directive 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoD Directive 5230.25, Withholding Unclassified Technical Data from Public Disclosure.

https://ia.signal.army.mil/dodiaa/default.asp

W900KK-19-C-0017

3.1.9 Cybersecurity Measures

The contractor shall develop, manage and maintain a Cybersecurity program to guide management that includes the activities in the following paragraphs. The contractor shall comply with the Army Cybersecurity/Information Technology (IT) Certification process in accordance with DoD 8570.01-M, DFARS 252.239.7001, and AR 25-2. All contractor employees’ supporting RMF/IT functions shall be appropriately certified upon contract award and certifications must be maintained through the lifetime of contract. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award and maintained through the lifetime of contract. Contractor shall provide proof of certification upon request.

The contractor's Cybersecurity Program shall be managed through the Risk Management Framework (RMF) consistent with the principles established in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37 and IAW DoDI 8510.01. The Contractor shall identify, manage, maintain and verify Cybersecurity requirements, including Cybersecurity controls and RMF control document development. Security controls shall be implemented through Systems Engineering Technical Processes as follows: stakeholder requirements definition, requirements analysis, architecture design, implementation, integration, verification, and validation. The Contractor shall continue to implement the DoD best practices of Cybersecurity which include confidentiality, integrity, availability, authentication, and non-repudiation. Cybersecurity requirements shall be integrated into the overall Test and Evaluation (T&E) and System Development Lifecycle (SDLC) processes. Cybersecurity risks shall be identified and managed as part of the overall program risk management process (consisting of cost/schedule/performance risks). The Contractor shall support Cybersecurity Impact Evaluations (CIE) package for system modifications and reaccreditation as required due to major upgrades affecting the Cybersecurity posture of the system. In the test environment, the Contractor shall analyze, potentially implement and report compliance status for applicable security patches, including commercial patches, for the products installed on the baseline.

This is the start of the file's text. The full file is on GovTribe.

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