Attachment 1_Performance_Work_Statement_PWS_03Oct2024.pdf

CUI

PWS-2022-028

Version 1.0

3 OCT 2024

i

BASE PERFORMANCE WORK STATEMENT (PWS) FOR

160TH SPECIAL OPERATIONS AVIATION REGIMENT (AIRBORNE)

[SOAR(A)] SPECIAL OPERATIONS FORCES TRAINING,

ENGINEERING AND MAINTENANCE SUPPORT (SOF TEAMS) IV

U.S. ARMY

PROGRAM EXECUTIVE OFFICE FOR

SIMULATION, TRAINING AND INSTRUMENTATION (PEO STRI)

PRODUCT MANAGER FORCES TRAINING SYSTEMS

(PdM FTS)

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3276

Controlled by: PEO STRI

Controlled by: SFAE-STR-CTT CUI Category: General Procurement and Acquisition Distribution: D POC: John Farrell, 270-956-3703

Version 1.0

3 OCT 2024

ii

X Prepared By:

PdM FTS Aviation Lead Systems Engineer

Approved By:

PdM FTS Chief Engineer

Submitted By:

PdM FTS Aviation Assistant Program Manager

Version 1.0

3 OCT 2024

iii

CUI

REVISION LOG

Version Date Revision Description

1.0 3 OCT 2024 RFP Release

Version 1.0

3 OCT 2024

iv

CUI

TABLE OF CONTENTS

Section Title Page

1. SCOPE

Future TADSS Changes and Modification

Places Of Performance

Background

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

Program Management

3.1.1 Organization Structure

3.1.2 Financial Management

3.1.3 Program Meetings and Reviews

3.1.4 Program Communications

3.1.5 Transition with Outgoing/Incoming Contractor

3.1.6 Accident and Incident Notification and Investigation

3.1.7 Hazardous Materials (HAZMAT) Management

3.1.8 Quality Assurance

Security

3.2.1 Physical Security

3.2.2 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

3.2.3 Cybersecurity Measures

Operations Support of TADSS

3.3.1 Contract Metrics

3.3.2 TADSS Emerging Requirements

3.3.3 RESERVED

3.3.4 Operations Schedule

3.3.5 Start-Up/Preparation

3.3.6 TADSS Activation and Deactivation

3.3.7 Over and Above Services

3.3.8 Overtime/Surge

Logistics Support

3.4.1 Logistics Support Package (LSP)

3.4.2 Government Furnished Information (GFI)

3.4.3 Government Furnished Property (GFP)

3.4.4 Government Furnished Property (GFP) Inventory

3.4.5 Contractor Acquired Property (CAP)

3.4.6 Incidental Property

Version 1.0

3 OCT 2024

v

CUI

3.4.7 Repair Parts

3.4.8 Spares

3.4.9 Support Equipment

3.4.10 Test, Measurement and Diagnostic Equipment (TMDE)

3.4.11 Consumables and Expendables

3.4.12 Transportation, Shipping and Receiving

3.4.13 Diminishing Manufacturing Sources/Material Shortages (DMS/MS) and Supportability ... 31

Administration

3.5.1 Operational Support

3.5.2 Configuration Management (CM)

3.5.3 Software Reports

3.5.4 Government Installation Work Schedule

3.5.5 Reimbursement of Travel, Per Diem and Special Material Costs

3.5.6 Preservation, Packaging, Packing and Marking

3.5.7 Disclosure, Use and Protection of Proprietary Information

3.5.8 Addition Or Substitution of Key Personnel (Services)

3.5.9 Organizational and Consultant Conflicts of Interest (Services)

Maintenance

3.6.1 TADSS Hardware, Software Support and Maintenance

3.6.2 Spares Maintenance

3.6.3 Support Equipment Maintenance

3.6.4 Shipping/Receiving

Engineering Support

3.7.1 Advanced Computer Systems Support

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

3.7.3 Engineering Feasibility/Trade Studies and Analysis

3.7.4 Technical Data Management

3.7.5 Networking, Interfaces, and Interoperability Support

3.7.6 Distributed Operations

3.7.7 Government Purpose Rights

Facilities

Modification or Upgrade Installation

3.9.1 Pre/Post Modification Inspections

3.9.2 Modification Support

APPENDIX A SOF TEAMS TADSS Descriptions .............................................................................. A-1

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

A.1.1 DTT/CAPT Purpose/Description ............................................................................................ A-1

A.1.2 CAPT Major Components/Systems (per station): ................................................................. A-2

Version 1.0

3 OCT 2024

vi

CUI

A.2 Universal Mission Simulator (UMS-1, UMS-2, UAS RAAD) ...................................................... A-2

A.2.1 UMS Purpose......................................................................................................................... A-2

A.2.2 UMS Description ................................................................................................................... A-2

A.2.3 RAAD Description .................................................................................................................. A-2

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

A.3.1 LASAR CMS Purpose .............................................................................................................. A-3

A.3.2 LASAR CMS Description ......................................................................................................... A-3

A.4 A/MH-6M/R DTT ................................................................................................................... A-4

A.5 MH-47G Combat Mission Simulator (MH-47-1, MH-47-2 CMS) ............................................... A-4

A.5.1 MH-47G CMS Purpose .......................................................................................................... A-4

A.5.2 MH-47G CMS Description ..................................................................................................... A-4

A.6 MH-60M Combat Mission Simulator (MH-60-1, MH-60-2 CMS) .............................................. A-5

A.6.1 MH-60M CMS Purpose ......................................................................................................... A-5

A.6.2 MH-60M CMS Description .................................................................................................... A-5

A.7 NEXUS 3 Storage Access Network (SAN) ................................................................................. A-6

A.7.1 NEXUS 3 SAN Purpose ........................................................................................................... A-6

A.7.2 NEXUS 3 SAN Description ...................................................................................................... A-6

A.8 CMS Debrief Stations ............................................................................................................. A-6

A.8.1 CMS Debrief Station Purpose ................................................................................................ A-6

A.8.2 CMS Debrief Station Description ........................................................................................... A-6

A.9 Mission Rehearsal Exercise Training System (MRETS) ............................................................. A-7

A.9.1 MRETS Purpose/Description ................................................................................................. A-7

A.9.2 MRETS Components (Not all inclusive) ................................................................................. A-7

A.9.3 MRETS Software (Not all inclusive) ....................................................................................... A-7

A.10 RUNTIME X-IO Storage Area Network (SAN) ........................................................................... A-8

A.11 Just-In-Time (JIT) Publisher Common Database (CDB) 3.0 ....................................................... A-8

A.12 Flight Simulator Network (FSIMNET) ...................................................................................... A-8

Version 1.0

3 OCT 2024

vii

CUI

A.13 Mission Rehearsal Operations Center (MROC) ....................................................................... A-8

A.13.1 MROC Purpose ...................................................................................................................... A-8

A.13.2 MROC Description: ................................................................................................................ A-8

A.13.3 MROC Major Components: ................................................................................................... A-9

A.14 Visual Database Toolkit [Aechelon Database Generation System (DBGS) – Lite] ..................... A-9

A.15 Presagis Vega Prime CDB Viewer ............................................................................................ A-9

A.16 LASAR Containerized Flight Training Device (LASAR-2 CFTD) ................................................. A-10

A.16.1 LASAR CFTD Purpose ........................................................................................................... A-10

A.16.2 LASAR CFTD Description ...................................................................................................... A-10

A.17 Systems Integration Lab (SIL) ............................................................................................... A-11

A.17.1 SIL Purpose .......................................................................................................................... A-11

A.17.2 SIL Description (Notional) ................................................................................................... A-11

A.18 MH-47 Transportable Training Device (TTD) ......................................................................... A-11

A.18.1 MH-47 TTD Purpose ............................................................................................................ A-11

A.18.2 MH-47 TTD Description ....................................................................................................... A-11

A.19 MH-60 Transportable Training Device (TTD) (OPTION) .......................................................... A-12

A.19.1 MH-60 TTD Purpose ............................................................................................................ A-12

A.19.2 MH-60 TTD Description ....................................................................................................... A-12

A.20 A/MH-6 Transportable Training Device (TTD) (OPTION) ........................................................ A-12

A.20.1 A/MH-6 TTD Purpose .......................................................................................................... A-12

A.20.2 A/MH-6 TTD Description ..................................................................................................... A-12

A.21 Aircraft Flight Analysis, Mishap Investigation Support Lab and Simulator to Aircraft System Test and Evaluation Suite ....................................................................................................................... A-13

A.21.1 Aircraft Flight Analysis, Mishap Investigation Support Lab and Simulator to Aircraft System Test and Evaluation Suite Purpose ...................................................................................................... A-13

A.22 Aircraft Flight Analysis, Mishap Investigation Support Lab and Simulator to Aircraft System Test and Evaluation Suite Description ..................................................................................................... A-13

APPENDIX B CONTRACT DATA REQUIREMENTS LIST (CDRL) INSTRUCTIONS ................................. B-1

Version 1.0

3 OCT 2024

viii

CUI

B.1 Data Deliveries ...................................................................................................................... B-1

B.1.1 Delivery Dates ........................................................................................................................ B-1

B.1.2 Tailored Data Items ................................................................................................................ B-1

B.1.3 Final Submittal of Data ........................................................................................................... B-1

B.1.4 Classified Data ........................................................................................................................ B-1

B.1.5 Letter Of Transmittal (LOT) ..................................................................................................... B-1

B.2 Modification To Data Requirements ....................................................................................... B-2

B.3 Data Preparation ................................................................................................................... B-2

B.4 Marking Technical Documentation ......................................................................................... B-3

B.4.1 Distribution Marking System .................................................................................................. B-3

B.4.2 Marking Technical Data .......................................................................................................... B-3

B.4.3 Controlling Office ................................................................................................................... B-3

B.4.4 Method Of Transmittal ........................................................................................................... B-4

B.4.5 Deliverables Index listing ........................................................................................................ B-4

APPENDIX C REFERENCE DOCUMENTS ........................................................................................ C-1

C.1 Government Documents ........................................................................................................ C-1

C.2 Department of Defense (DOD) Security Instructions, Directives, and Manuals ....................... C-2

C.3 Non-Government Documents ................................................................................................ C-2

APPENDIX D ACRONYMS AND DEFINITIONS ................................................................................ D-1

Version 1.0

3 OCT 2024

CUI

PERFORMANCE WORK STATEMENT (PWS)

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

Special Operations Forces Training, Engineering and Maintenance Support

(SOF TEAMS) IV

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 (A/V), debrief, etc. The contractor shall provide management and logistical support to include labor, materials, consumables, tools and test equipment (TTE), maintenance and repair activities, minor engineering modifications, training, website, cybersecurity, and hardware/software/documentation configuration management to maintain all TADSS 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 (PMO) 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. Throughout this PWS, SOF TEAMS IV (ST IV) and SOF TEAMS may be used interchangeably.

Future TADSS Changes and Modification

As future TADSS(s) are developed and fielded, or existing devices require modification, relocation, deinstallation, 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 TADSS, support systems, maintenance, and operational support requirements, and/or additional simulators and simulations requiring Life Cycle Contractor Support (LCCS) services.

Places Of Performance

This PWS establishes the SOF TEAMS IV efforts required in support of the 160th Special Operations Aviation Regiment (Airborne) [SOAR (A)] at Ft. Campbell, KY. It is projected that there will be ECPs under this contract for work within the United States. The specific place of performance will be identified in the ECP. For the purposes of this contract, Continental United States (CONUS) means the 48 contiguous States and the District of Columbia, and Outside CONUS (OCONUS) means outside of the contiguous United States to also include the Non-Foreign OCONUS Area (the states of Alaska and Hawaii, the Commonwealths of Puerto Rico and the Northern Mariana Islands, Guam, and U.S. territories and possessions).

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 (PdM STS) starting in FY05. PdM STS was renamed Product Manager

Version 1.0

3 OCT 2024

CUI

Forces Training Systems (PdM FTS) in 2023. This PWS defines the effort for the 160th SOAR(A) Special Operations Forces Training, Engineering, and Maintenance Support (SOF TEAMS) IV. A list and brief description of the current 160th SOAR(A) TADSS is located in Appendix A of this PWS.

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

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.

2. APPLICABLE DOCUMENTS

The documents listed in Appendix C 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.

3. REQUIREMENTS

This 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 IV 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.

d) Provide a capability to analyze future efforts and initiatives resulting in rough orders of magnitude (ROMs) and/or 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.

Version 1.0

3 OCT 2024

CUI

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

f) Support and collaborate on third-party efforts.

The contractor shall submit the Small Business Utilization Report.

Deliverable: DI-MGMT-82041B, Small Business Utilization Report

3.1.1.1 Core Competencies

a) Cybersecurity Measures (PWS 3.2.3 and associated subsections)

b) Operations Support (PWS 3.3 and associated subsections)

c) Logistics Support (PWS 3.4 and associated subsections)

d) Configuration Management (PWS 3.5.2 and associated subsections)

e) Maintenance Support (PWS 3.6 and associated subsections)

f) Engineering Support (PWS 3.7 and associated subsections)

g) Modification or Upgrade Installation (PWS 3.9 and associated subsections)

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 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 In Accordance With (IAW) the CDRL.

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

3.1.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 Integrated Project Team (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 Government the minutes of meetings and reviews in accordance with (IAW) the Contract Data Requirements List (CDRL) and post the documents to the website.

https://armyeitaas.sharepoint-mil.us/teams/PdMSTS-SOFTEAMSIV/Shared%20Documents/SOF%20TEAMS%20IV/Acquisition%20Documentation/PWS/0_STIV_IDIQ_Base_PWS_30Nov23draft_ab.docx?web=1

Version 1.0

3 OCT 2024

CUI

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

a. All required action items, as mutually agreed by Government and contractor during the meeting/review, have been closed out or resolved.

b. The minutes and presentation material have been accepted by the Government.

c. The Integrated Master Schedule (IMS) accurately depicts activities, events, and dependencies.

d. Management and staffing plans are updated with progress towards assuming full performance responsibilities.

Deliverables: DI-ADMN-81249C, Meeting Agenda

DI-ADMN-81250C, Meeting Minutes DI-ADMN-81373, Presentation Material DI-MGMT-81605, Briefing Materials DI-MGMT-81861C, Integrated Program Management Data and Analysis Report (IPMDAR) Format 4-6

3.1.3.1 Program Management Review (PMR)

The contractor shall host and conduct quarterly PMRs for the initial base year and, shall conduct PMRs annually or 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 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 Program Schedule

b) CLIN Review

c) Current Issues

d) Contractual Concerns

e) Quality Assurance Surveillance Plan (QASP)

f) Planned and Funded Actions or Upgrades

g) Manning and Staffing

h) Risks

i) Action Item Review

j) Summary/Conclusion

Version 1.0

3 OCT 2024

CUI

3.1.3.2 Post Award Conference (PAC)

The contractor shall conduct a Post Award Conference (PAC) NLT 30 calendar days after contract award as directed by and coordinated with the Government. The focus of the PAC is to ensure the contractor is prepared to execute the requirements of the PWS and assume full performance on Contract Support Date (CSD). The contractor shall be prepared to discuss the phase-in plan and the respective responsibilities of all parties. The contractor shall brief their management plan, IMS, and staffing table detailing their progress to assume full performance. The contractor shall place emphasis on management plan implementation, operating procedures and transition plan. The contractor shall provide the agenda two business days in advance and shall address any agenda items requested by the Government. The Government and contractor may discuss proposed new and updated PWS requirements.

3.1.3.3 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.4 Program Communications

The contractor shall provide open, timely, and comprehensive sharing of information with the Government by using digital media (i.e., Office 365, PEO STRI CM Tool, Microsoft TEAMS, DOD SAFE, digital files, DVDs, hard drive, etc.), and electronic messaging (i.e., MS Teams, email) as appropriate. The contractor shall use MS Teams and telephonic/Web/App based conferencing where practical. The communication method shall be determined using the IPT process.

3.1.4.1 SOF TEAMS Web-based Platform

The contractor shall establish and maintain a SOF TEAMS web-based platform that serves as a gateway to information, services, and resources on the internet, referred to as “website” or “dashboard” for the purposes of this PWS. The website will be used to manage, at a minimum, all programmatic, operational, maintenance, supply and inventory data as permitted. The website shall be operational at end of contract transition. A review of the website shall be done at each PMR or as required by the Government. The website or dashboard shall be continually updated across the program Period of Performance (PoP) to promote new features identified by the Government or Contractor teams. 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 website shall satisfy the requirements listed below:

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

PAC.

Version 1.0

3 OCT 2024

CUI

b. The website shall not be hosted on a Government-provided server or service. The website shall be accessible by Non-classified Internet Protocol (IP) Router Network (NIPRNet) government 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 products used by the Government 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 provide a chronological record that traces the history and events related to website activity 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 and .pdf).

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

k. All CDRLs TRANSMITTAL/ACCEPTANCE/REJECTION tracking.

l. Conformed Contract.

m. All Contract Modifications including conformed copies.

n. All Work Orders (WOs) and Purchase Requests (PRs).

o. Burn rates of all non FFP Contract Line Item Numbers (CLINs) to include, at a minimum, the estimated-to-actual total cost per Work Order/Purchase Request (WO/PR). Data to be current with all WOs and PRs

p. All service agreements.

q. All contract invoices and quotes.

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

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

Version 1.0

3 OCT 2024

CUI

t. Not store classified data on the website.

u. Utilize password controls as required to protect sensitive data.

v. Quality assurance corrective action requests generated, maintained, and archived as appropriate.

w. Provide TADSS utilization.

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

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

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

aa. 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.5 Transition with Outgoing/Incoming Contractor

The contractor shall take all contract transition actions in accordance with the contractor’s proposal and the PWS to ensure 100% readiness to perform all contract responsibilities upon CSD.

3.1.5.1 Transition Phase-In

The Transition Phase-In (TPI) period will not exceed sixty (60) calendar days prior to CSD. During the TPI period the contractor shall prepare to and assume performance responsibility for the TADSS identified in Appendix A. The contractor shall take all actions necessary to minimize any impact on the operational readiness and capabilities of the TADSS during the TPI period. The contractor shall perform a joint property inventory with the cognizant Government representative(s) which will be initiated no later than thirty (30) calendar days prior to the end of the TPI 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) upon CSD. The contractor shall perform transition phase-in duties to include but not limited to:

a) Program Schedule during the TPI period

b) Staffing actions

c) Data library

d) Setting up communications capabilities

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

Version 1.0

3 OCT 2024

CUI

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

g) Implementation of SOF TEAMS IV Website

Deliverables: DI-MGMT-81947B, Government Furnished Property and Forecasting Report DI-MGMT-82173, Government Furnished Equipment (GFE) Inventory Report DI-MGMT-80441D, Government Property Inventory Report

3.1.5.2 Joint Meetings

A joint on-site transition meeting shall be conducted after contract award to discuss the contractor's transition plan and the respective responsibilities of all parties. A joint "Pre-CSD" meeting shall be conducted approximately two (2) weeks prior to CSD to discuss the contractor's readiness to assume full responsibility, outstanding maintenance and engineering issues and parts backlog and repair deadlines.

At the Government’s discretion, the transition meeting and/or the Pre-CSD Meetings may be conducted via video teleconferencing, telephone or combined into one (1) on-site meeting.

3.1.5.2.1 Contract Support Date (CSD)

The contractor shall complete transition requirements and assume full performance responsibility at

CSD.

3.1.5.3 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) calendar 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. At a minimum, the incumbent shall provide the succeeding contractor access to the site, simulators, training devices, training aids, equipment groups and associated systems; materials; and technical documentation and publications. In addition, as an on-the-job (OJT) function, the incumbent shall allow the succeeding contractor to observe (over-the-shoulder) the performance of all required maintenance and support tasks on a not-to-interfere with training and maintenance basis. The outgoing contractor shall retain full responsibility for SOF TEAMS until completion of the transition phase-out period. The contractor shall perform transition phase in duties to include but not limited to:

a) No later than thirty (30) calendar 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 property (GFP, CAP, TTE, GFI etc.) during the transition phase-out period

b) Facilitate the transfer of all SOF TEAMS GFI administrative access (i.e. Website and databases) information with the in-coming contractor

c) Provide to the Government a download/soft copy of all records and other support data stored in electronic systems (such as inventory control system, website) onto DVD compatible with Government Office 365 applications.

Version 1.0

3 OCT 2024

CUI

d) Be responsible for supplying replacements for missing or damaged items at the end of the contract performance period.

e) Provide an accurate listing of all parts at vendors for repair and all ongoing service agreements, 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: DI-MGMT-82173, Government Furnished Equipment (GFE) Inventory Report DI-MGMT-81947B, Government Furnished Property and Forecasting Report DI-MGMT-80441D, Government Property Inventory Report DI-MGMT-81945A, Phase-Out Transition Plan

3.1.5.4 Trainer Material Condition

During transition, the Government may perform inspections or tests (usually all or portions of the ATP, diagnostics, Daily Operational Readiness Test (DORT), mission test, etc.) to assess the material condition of each simulator, training device, training aid, equipment group and associated systems. The contractor shall be responsible to correct all conditions/deficiencies in trainer performance that degrade or preclude full exploitation of the trainer. All outstanding maintenance actions shall be completed as specified in this PWS prior to the end of the Transition Phase.

3.1.5.5 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 and valid ACAs shall be available for review upon Government request.

3.1.6 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 Contracting Officer (KO) 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.

Deliverable: DI-SAFT-81563, Accident/Incident Report

3.1.7 Hazardous Materials (HAZMAT) Management

The contractor shall implement a comprehensive HAZMAT/Waste Program, perform all handling, storage and on-station transportation of HAZMAT generated in the course of TADSS operations and maintenance.

The contractor shall provide HAZMAT management in accordance with local, state, and Federal laws, regulations, policies, and procedures. This shall include, but not limited to, the following:

Version 1.0

3 OCT 2024

CUI

a. HAZMAT data shall be available to personnel at all applicable locations

b. Reporting, recording, preventing, controlling, removing, and cleaning up accidental and intentional spills of HAZMAT in coordination with the local installation HAZMAT control activity

c. Identifying HAZMAT requirements in contract technical documentation, identifying alternative materials, evaluating the suitability of identified alternatives for use, and implementing alternatives

d. 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.

e. Responsible for the collection, inventory, handling, storing, 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 modifications to the local installation HAZMAT control activity.

f. Providing Department of Transportation (DOT) approved containers for storage and transportation

g. Preparation for disposal to include marking and labeling

h. Determining and testifying as to composition of chemical waste and characteristics through chemical analysis or historical data with resulting calculations

i. Providing employee training and certification IAW Base, local, state, and federal regulations

j. Maintaining Safety Data Sheets (SDSs) (formerly known as Material Safety Data Sheets (MSDSs);

and maintaining an internal tracking system for all HAZMAT and non-hazardous waste.

k. Be responsible for any additional expenses incurred as a result of contractor action or inaction, including, but not limited to noncompliance or violation of Federal, state, or local laws or regulations, inadequate records keeping, spills, failure to source separate wastes, or failure to provide chemical composition of wastes.

3.1.8 Quality Assurance

The contractor shall develop, implement, and maintain a Quality Control (QC)/Quality Assurance (QA) plan for the purpose of providing and maintaining confidence in contractor performance throughout the life of the contract. The plan shall be based on International Organization for Standardization (ISO) 9001 standards, except that ISO certification is not required. Contractor management shall be required to regularly review the quality assurance program and will address quality issues and risks at all PMRs. The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

3.1.8.1 QA Assistance during audits, inspections, and surveillances

The contractor shall provide assistance for inspections, audits, and surveillances upon request.

3.1.8.2 QA Reporting

The contractor shall report corrections to all discrepancies found during Government inspections, audits, and surveillances.

Version 1.0

3 OCT 2024

CUI

3.1.8.3 QA Response to Corrective Action Requests (CAR)

The contractor shall respond to Government Corrective Action Requests (CAR) within three (3) business days. Contractor responses will as a minimum contain the root cause of the discrepancy, completed, or proposed corrective action(s) and an actual or estimated completion date.

3.1.8.4 QA Follow-up

The contractor shall perform and document follow-up inspections within the Government-approved time period to verify corrective actions(s) achieved the desired result, and effectiveness in preventing repeat occurrences.

3.1.8.5 Quality Assurance Verification of Efforts

The contractor shall provide performance, hours, quality procedures, and inspection data on the website for verification of all program work efforts to Government designated representatives.

3.1.8.6 Quality Assurance Tracking System

The contractor shall provide, implement, and maintain a tracking system to record and track CARs, audits, surveillances, inspections, testing schedules and results. The contractor shall track corrective actions, analyze trends, and maintain quality assurance records and data.

Security

SOF TEAMS contractor personnel and subcontractors 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 to include but not limited to communications-security (COMSEC) information, Sensitive Compartmented Information (SCI) and Controlled Unclassified Information (CUI), Technical Information/Documents and For Official Use Only (FOUO) information. 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 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 Outside the Continental United States (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

Version 1.0

3 OCT 2024

CUI

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.2.1 Physical Security

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

3.2.1.1 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 with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by Department of Defense (DOD), Headquarters Department of Army (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 Federal Bureau of Investigation fingerprint check and a successfully scheduled NACI at the Office of Personnel Management. For contractors that do not require a CAC but require access to a DOD facility or installation, the contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (Army Directive 2014-05/AR 190-13); applicable installation, facility and area commander installation and 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.

Version 1.0

3 OCT 2024

CUI

The Security Officer and COR shall be notified in writing within 24 hours if an employee possessing a security clearance is discharged or voluntarily terminates employment. The contractor shall be responsible to collect and return to the COR any building, base access, or identification information (such as Government issued CAC) from personnel who are discharged or that voluntarily terminate their employment with the contractor.

3.2.1.2 Classified Material Destruction

The contractor shall assume responsibility for the destruction of all classified material generated as a result of simulator and training device utilization, maintenance, and engineering, and as may become necessary through revision of the technical data support package.

3.2.2 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

3.2.2.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 KO, 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:

http://jko.jten.mil/.

3.2.2.2 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.2.2.3 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.2.2.4 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…