1- KR AOC Ops_Admin training tools_Draft PWS_05 Jun 24.pdf

Air Operations Center (AOC) Operations Administrative Training Tools

05 June 2024

AFLCMC/HBBO

300 Exploration Way

Hampton, VA 23666

DISTRIBUTION STATEMENT A: Approved for public release: distribution is unlimited.

Revision History

Rev Number Date Description Sections RFI_DRAFT 1 05 June 2024 Draft requirement PWS All

Table of Contents

1. INTRODUCTION

1.1. PROGRAM BACKGROUND

2. SCOPE

2.1. REQUIREMENTS BACKGROUND

2.2. KEY PROGRAMMATIC OBJECTIVES

3. TECHNICAL REQUIREMENTS

3.1. C2WSPTT SYSTEM SUSTAINMENT

3.2. ACTT SYSTEM SUSTAINMENT…………………………………………………..10

3.3. CYBER SECURITY

3.4. SYSTEM SUPPORT

3.5. AGILE TEST, EVALUATION AND INTEGRATION

3.6. PROGRAM MANAGEMENT

3.7. PLANNING AND REPORTING

3.8. RISK MANAGEMENT

3.9. CONFIGURATION MANAGEMENT

3.10. TRANSITION

APPENDIX 1 - ASSOCIATE CONTRACTOR AGREEMENTS (ACA)

APPENDIX 2 – TERMS RELATIVE TO WAR, ARMED CONFLICT,

INSURRECTION, CIVIL OR

APPENDIX 3 – INVITED CONTRACTOR OR TECHNICAL REPRESENTATIVE

STATUS UNDER U.S. – REPUBLIC OF KOREA (ROK)

APPENDIX 4 – CONTRACT TO BE PERFORMED IN THE FEDERAL REPUBLIC OF

GERMANY ADMINISTRATIVE PROCEDURES FOR TECHNICAL EXPERT

STATUS AND ACCREDITATION (TESA)

APPENDIX 5 – OCONUS REQUIREMENTS FOR CONTRACTOR PERSONNEL

APPENDIX 6 – PERFORMANCE REQUIREMENTS SUMMARY: C2WSPTT/ACTT..27

APPENDIX 7 – ACRONYM LIST…………………………………………………………..…28

APPENDIX 8 – LIST OF APPLICABLE WEBSITES……………………………………

APPENDIX 9 – C2WSPTT TASK LIST………………………………………………...……32

APPENDIX 10 – C2WSPTT CURRENT CONFIGURATION…………………………

APPENDIX 11 – CURRENT C2WSPTT OPERATING LOCATIONS BY AOC SPO…..34

APPENDIX 12 – FUTURE OPERATING LOCATIONS (UP TO FIVE (5) ADDITIONAL

LOCATIONS PER YEAR)……………………………………………………..………………35

APPENDIX 13 – ACTT SCENARIOS………………………………………………………….36

APPENDIX 14 – CURRENT ACTT OPERATING LOCATIONS…………………………...38

1. INTRODUCTION

1.1. Program Background

1.1.1. The Air Operations Center (AOC) utilizes the AOC Communications Training Tool (ACTT) and the Command and Control Weapon System Part Task Trainer (C2WSPTT) as the primary training systems to provide realistic training for AOC Administrators (both System and Network) and Operators without having an impact on the Operational Environment.

1.1.2. ACTT is a training framework for AOC system and network administrators to accomplish Mission Qualification Training (MQT). ACTT provides an environment to conduct interactive training that is not possible on operational systems. It provides scenarios that focus on maintaining AOC systems, configuring AOC systems and troubleshooting common AOC problems. It also manages and documents training.

The ACTT Interactive capability provides interactive maintenance, configuration and troubleshooting scenarios/labs using virtual and physical resources. The Training Management capability provides training status and progress. Its Scenario Creation capability provides methods for creating training scenarios.

1.1.3. C2WSPTT is the modeling and simulation (M&S) tool that provides a small-scale, high-fidelity M&S capability to allow Air Operations Center (AOC) units to conduct in-garrison training without the need for outside agency support. It is designed to be used by operators to conduct interactive training that is not possible without negative impact on operational systems. The Training Management capability provides training status and progress. Its Scenario Creation capability provides methods for creating and sharing training scenarios. As a single system, it requires a minimum of a single Trainer/Controller. C2WSPTT queries the Air Operations Center (AOC) databases for scenario creation information and AOC mission data, provides data link inputs to Common Operational Picture, various US Message Text Format (USMTF) and Over The Horizon GOLD (OTH-GOLD) Intelligence messages, mission and force level updates to AOC systems, and interactive simulation control capabilities.

C2WSPTT uses the Flexible Analysis and Mission Effectiveness System (FLAMES) simulation engine as its core capability.

1.1.4. Both ACTT and C2WSPTT tools continue to evolve to accommodate warfighting doctrine and environment, event frequency, type, and stakeholder needs. Some events are recurring and scheduled in advance while others may be one-time engagements.

2. SCOPE

2.1. Requirements Background

2.1.1. This PWS sets forth the requirements for both the ACTT and the C2WSPTT contract.

This contract is primarily intended to support the Air Force Life Cycle Management

Center (AFLCMC), Program Executive Office (PEO) Digital for the Air Operations Center (AOC). The contractor shall build and sustain both ACTT and the C2WSPTT system IAW the requirements within the AOC Baseline. Additionally, the contractor shall continuously maintain the system in accordance with Cyber Security (CS) requirements to remain compliant with the Air Force (AF) Command and Control (C2) infrastructure as well as the current AOC weapon system. The contractor shall field/install/train ACTT and C2WSPTT as installed at the AOC sites (ACTT – Appendix 14, PTT Appendix 11) and provide an in-house capability to train locally on all active baselines as fielded to AOC units.

2.1.1.1. The contractor shall provide FLAMES and C2WSPTT expertise to units during preparation for exercises and provide help-desk support to the entire enterprise. There are currently thirty six (36) (Appendix 11) operating locations (total of 45 FLAMES licenses), including 19 AOC sites supported by the AOC System Program Office (SPO) that require C2WSPTT; however, the Government intends to use this contract to add additional operating locations (estimated at up to five (5) locations per year) during the period of performance in support of C2WSPTT needs.

2.1.2. Operational requirements of ACTT and C2WSPTT are driven by: the operational

Commanders for the AOC Enterprise; AOC Program Management Office; the Air Force Agency for Modeling and Simulation (AFAMS); and in coordination with the Joint Modeling & Simulation community. The scope of this contract will cover the sustainment, updating, integration & test, fielding, installation, training, exercise (for C2WSPTT only) and on-site support, and help desk activities associated with the present system and current AOC weapon system.

2.1.3. The contractor shall respond to schedule and programmatic changes of technical and operational requirements, implementation changes, and for C2WSPTT only, Federation (operational compatibility with other Government owned simulators).

2.2. Key Programmatic Objectives

2.2.1. The purpose of this contract is to obtain the services of a team to provide life-cycle management services for both ACTT and C2WSPTT. This includes sustainment (in garrison and on site at each unit), helpdesk, training, and support. The training systems are in operation, with on-going software updates for both related to functional upgrades, security/end-of-life, and taking advantage of efficiencies in technology. The Government does not require the contractor to maintain a physical presence at each site full time. The contractor may remote access and Temporary Duty (TDY) to support upgrade or exercise activities.

2.2.2. For C2WSPTT there are thirty-six (36) locations, to include South Korea, Hawaii, Alaska, Germany, Japan and locations within the Continental United States (CONUS) (Appendix 11).

2.2.3. C2WSPTT on-going software upgrades may also include technical refreshes from the main simulation engine upon which it relies.

2.2.4. The contractor shall provide engineering/subject-matter-expert (SME) support to remain synchronized with upgrades to the AOC 10.1 baseline. The contractor shall provide installation, training and exercise support for the C2WSPTT to meet Government requirements and comply with DoD CS guidelines. It should be noted that SME support shall include FLAMES expertise. This SME is required to have FLAMES expertise the first day after a fourteen (14) day transition period; there is no ramp-up time allotted for the SME to become proficient with FLAMES. The Government also requires FLAMES sustainment, specifically FLAMES integration and test work due to Risk Management Framework (RMF) requirements and controls, as well as licensing efforts, to support the C2WSPTT.

For ACTT there are twenty-three (23) locations worldwide. Locations include Korea, Hawaii, Alaska, Germany, Qatar (OCONUS) and the Continental United States (CONUS) (Appendix 14).

For ACTT contractor shall maintain configuration discipline of the system for the government and provide software change and problem fixes to the baseline, as required. This includes software and hardware updates provided through Agile Release Events (AREs), AOC Periodic Maintenance Updates (PMUs), Critical Security Updates (CSUs), Out of Cycle Events (OCEs) and Fast Tracks (FTs) events to remain in sync with the AOC operational baseline.

2.2.5. AOC weapon system integration and C2WSPTT Federation: The contractor shall provide engineering/SME support to remain synchronized with capabilities that support sustainment efforts to the AOC 10.1 baseline. Engineering/SME shall provide install support, training and exercise support for the C2WSPTT to meet Government requirements and comply with DoD CS guidelines. This includes appropriate support to ensure C2WSPTT is federated with Joint Live Virtual Constructive (JLVC), Joint Landing Component Constructive Training Capability (JLCCTC), and Battle Lab Collaborative Simulation Environment (BLSCE) federations.

2.2.6. Systems Sustainment: Sustain and update both ACTT and C2WSPTT suite as a consistent product through quality delivery and cost control with focus on:

- An agile, stable environment and velocity.

- Full use of automation.

- Full cooperation, teaming, and visibility with the Government team (including contractor support and Federally Funded Research and Development Center (FFRDC) support).

- A stable team size.

- This will include maintenance of the current fielded production baseline along with continuing sustainment.

2.2.7. Provide on-site Type 1 training for both ACTT and C2WSPTT, IAW AFI 36-2670 and AFI 13-1AOC, Vol 1, at Government and contractor locations, both in administration of the system itself as well as the operational use.

2.2.8. Test and Integration: Maintain C2WSPTT through agile style test and integration focused on JLVC, JLCCTC, and BLSCE federations; C2 interoperability, integration, and testing, as required.

3. TECHNICAL REQUIREMENTS

3.1. C2WSPTT System Sustainment

3.1.1. The contractor shall provide systems engineering support as a key member of an integrated team consisting of the: Program Management Office (PMO);

Government/contractor members of the M&S Federations; other designated support, sustainment, and integration C2 Contractors; and Government agencies. The contractor shall work as part of this integrated team to maintain the execution of C2WSPTT functionality.

3.1.2. The contractor shall develop, maintain, and deliver a Software Design Document.

Subject to review and approval by the Government. (CDRL A00x, Software Product Package)

3.1.3. The contractor shall provide all personnel, equipment, supplies, transportation, tools, materials, supervision and other items necessary to maintain, train, and support C2WSPTT as defined in this PWS. When this contract requires the contractor to work in a Government facility, the Government will furnish or make available working space, network access, and equipment. All materials will remain the property of the Government and will be returned to the responsible Contracting Officer Representative (COR) upon request or at the end of the contract period of performance. The use of Government sources in the purchase of Contractor Acquired Property (CAP) is authorized; authorization will be set up upon contract award.

3.1.4. The contractor shall use agile software methodology to sustain capability in short cycles.

3.1.5. The contractor shall develop, maintain, and deliver a Software Sustainment/Management Plan. A current copy of the document will be provided by the Government upon contract award to the contractor for updating. Subject to review and approval by the Government. (CDRL A00x, Software Product Package)

3.1.6. The contractor shall sustain the production baseline as well as work new Change

Requests (CRs) in support of the baseline. The contractor shall include user-prioritized CRs, rare urgent CRs, Deficiency Report (DR) fixes, and very time compressed urgent DRs.

3.1.7. The contractor shall deliver all software and all its components, capabilities, artifacts, and software support information including design information and compilation, build, and modification procedures for suite components. The contractor shall post these deliveries on the Government directed web site (i.e., Naval Lift). The contractor shall make current intermediate software artifacts available in real-time for informal review by the Government. In addition, the contractor shall provide an analysis on C2WSPTT integration to a Cloud Environment. Subject to review and approval by the Government. The Government directed web site (i.e., Naval Lift) URL and access will be provided upon contract award. (CDRL A00x, Software Product Package)

3.1.8. The contractor shall prepare and deliver C2WSPTT executable software or as

Virtual Machines (VMs), at the Government’s request. (CDRL A00x, Software Product Package)

3.1.9. The contractor shall develop, maintain, and deliver (via Government directed web site (i.e., Naval Lift) the following (CDRL A00x, Software Product Package): Software Product Specification, Software User Manual Software Version Description, Software Design Description, DoD Architecture Framework Information, Interface Design Description – Federation Documentation Vulnerability Scan, Compliance Report, and Bill of material

3.1.10. The contractor shall maintain compatibility at all times with external federations in which C2WSPTT participates to include JLVC, JLCCTC, and BLSCE federations, as required. (CDRL A00x, Software Product Package)

3.1.11. The contractor shall maintain compatibility with, and potentially share common sustainment and integration under Government direction with, other operational and future M&S and C2 systems, as defined by the applicable TO. Among these are: Air and Space Constructive Environment-Information Operations Suite (ACE-IOS), Theater Battle Management Core System- Force Level (TBMCS-FL), AOC Communications Training Tool (ACTT), North American Treaty Organization (NATO) Integrated Command and Control (ICC) software, GEOBASE and other system interfaces will be added via the CR Process in order to maintain the compatibility with current AOC 10.1 Baseline.

3.1.12. Software Tools: The contractor may use the Government directed web site (i.e., Naval Lift) software collaboration tools to increase efficiency, collaboration, effectiveness, and realize cost reduction. The use of these tools includes project tracking with JIRA and documentation management in Confluence. The contractor may also use other tools available in Government directed web site (i.e., Naval Lift) (e.g. Subversion, Git, code scanning tools like Fortify).

3.1.12.1. Commercial off The Shelf Software (COTS) and License Management:

In situations where the purchase of new COTS software is needed to satisfy the requirements of a particular delivery order, the contractor shall use available existing enterprise licenses, where available. Products will be obtained via the DoD Enterprise Software Initiative (ESI) Blanket Purchase Agreements (BPAs) when possible. The Government will purchase additional COTS products when software is not available through ESI / BPA. The updated listing of COTS software available from DOD ESI can be viewed on the web at www.esi.mil.

3.1.12.2. The contractor shall provide maintenance and support of C2WSPTT COTS (FLAMES) software licenses and manage COTS relationships to the overall system life-cycle including applications, license agreements, and software upgrades. The contractor shall provide asset inventory and services that track the financial aspects of an asset to include cost and depreciation, contract management, leases, maintenance agreements and service contracts.

The contractor shall provide support summary information to include the general terms and conditions, benefits, strategic and tactical directions, license ordering information, internal billing process, pricing and deployment and support of the products included in the agreement. (CDRL A00x, Government Furnished Property)

3.1.12.3. The contractor shall support common practices for ordering assets, tracking orders and assets, and tagging the assets. The contractor shall support application installation, operations, customer support, maintenance, sustainment, and configuration control, to include the procurement of supporting software licenses.

3.1.12.4. The contractor shall develop and deliver training materials and conduct training, as well as develop, maintain, and/or update student and instructor training programs and materials. Software user manuals, software installation and configuration manuals developed by the contractor shall be provided to the program office and the AOC sites.

3.1.13. The AOC sites IAW the testing and training schedules of the system being trained, per direction from the Government. Ensure training stays current with the services offered throughout the life of the contract. At a minimum, training is typically provided to unit-designated POCs, once per version, per site. As the system is updated to address End of Service (EOS) issues, analysis will determine if additional training is required. The typical class size is nine to twelve (9-12) personnel per site. (CDRL A00x, Training Baseline (TB) System Training Documentation)

3.1.13. Contractor Acquired Property (CAP): The contractor shall procure the necessary hardware and/or cloud tools to fulfill the requirement of this contract as CAP in accordance with FAR 52.245-1 – Government Property. The hardware tool shall be priced based on http://www.esi.mil/

General Services Administration (GSA) pricing; use of Government sources will be authorized upon award. All disposal shall be accomplished via Standard Form 1428, Inventory Disposal Schedule.

3.2. ACTT System Sustainment

3.2.1. The contractor shall maintain, sustain and update the current on-premise application. These tasks will focus on System development and sustainment, Information assurance (IA) and cybersecurity using DoD Risk Management Framework (RMF) process for Assessment and Authorization (A&A), System support, Agile test, evaluation and integration, Program management, Planning and Reporting, Risk Management and CM. (CDRL A00x, ACTT Software Product Package & CDRL A00x, ACTT Risk Management Framework (RMF) Package)

3.2.2. The contractor shall provide systems engineering support as a key member of an integrated team consisting of the PMO; other designated support, and integration C2 contractors; and Government agencies. The contractor shall work as part of this integrated team to sustain the execution of current and future ACTT functionality.

3.2.3. The contractor shall provide all personnel, equipment, supplies, transportation, tools, materials, supervision and other items necessary to build, maintain, train, and support ACTT as defined in this PWS. The Government will provide Government Furnished Property. Additionally, the Government will provide Government Furnished Information in the form of AOC weapon system baseline updates as approved by internal SPO processes. The Government will also provide the services available on the government provided website. The use of Government sources in the purchase of Contractor Acquired Property (CAP) is authorized: authorization will be set up upon contract award. (CDRL A00x, ACTT Government Furnished Property (GFP))

3.2.4. The contractor shall use agile software methodology to build and sustain capability in short cycles.

3.2.5. The contractor shall maintain, and deliver a Software Plan. Subject to review by the government.

(CDRL A00x, ACTT Software Product Package)

3.2.6. The contractor shall sustain the production baseline as well as work new CRs (including modernization efforts) in support of the baseline. The contractor shall include user-prioritized CRs, rare urgent CRs, DR fixes, and very time compressed urgent DRs.

3.2.7. The contractor shall deliver all software and all its components, capabilities, artifacts, and software support information including design information and compilation, build, and modification procedures for suite components. The contractor shall post these deliveries on the Lift/JTDS, where possible. In addition, the Contractor shall make current intermediate software artifacts available in real-time for informal review by the Government. The contractor shall prepare and deliver ACTT executable software or as Virtual Machines (VMs), at the Government’s request. (CDRL A00x, ACTT Software Product Package & CDRL A00x, ACTT Status Report)

3.2.8. Contractor shall maintain, and deliver (via government provided website) the following: Software Product Specification, Software User Manual, Software Plan, Risk Management Framework (RMF) CyberSecurity (CS) Products, Interface Design Description, Vulnerability Scans, Compliance Reports, Bill of Material) (CDRL A00x, ACTT Status Report & CDRL A00x, ACTT RMF Package)

3.2.9. The contractor shall maintain current ACTT AOC Master Baseline and continue to update virtual systems to most current AOC Releases as directed by the Government. The contractor shall provide Type 1 Training development as directed by the Government. The contractor shall coordinate with the AOC CM Team to add AOC systems to the ACTT AOC Master Baseline. The government will direct the priorities for the additional AOC systems. (CDRL A00x, ACTT Training Materials)

3.2.10. Software Tools: The contractor may use the Lift software collaboration tools to increase efficiency, collaboration, effectiveness, and realize cost reduction. The use of these tools includes project tracking with JIRA and documentation management in Confluence. The contractor may also use other tools available in Lift (e.g., Subversion, Git, code scanning tools like Fortify).

3.2.11. Commercial off The Shelf Software (COTS) and License Management: In situations where the purchase of new COTS software is needed to satisfy the requirements to update ACTT, the contractor shall use available existing enterprise licenses, where available. Products will be obtained via the DoD Enterprise Software Initiative (ESI) Blanket Purchase Agreements (BPAs).

The updated listing of COTS software available from DOD ESI sources can be viewed on the web at http://www.esi.mil.

3.2.12. The contractor shall provide maintenance and support of ACTT COTS software licenses and manage COTS relationships to the overall system life-cycle including applications, license agreements, and software upgrades. The contractor shall assist with asset inventory and services that track the financial aspects of an asset to include cost and depreciation, contract management, leases, maintenance agreements and service contracts. The contractor shall provide support summary information to include the general terms and conditions, benefits, strategic and tactical directions, license ordering information, internal billing process, pricing and deployment and support of the products included in the agreement. (CDRL A00x, ACTT GFP)

3.2.13. The contractor shall support common practices for ordering assets, tracking orders and assets, and tagging the assets. The contractor shall support application installation, operations, customer support, maintenance, sustainment, and configuration control, to include the procurement of supporting software licenses.

3.2.14. The contractor shall develop and deliver training materials and conduct training. Develop, maintain, and/or update student and instructor training programs and materials. Software user manuals, software installation and configuration manuals developed by the contractor shall be provided to the AOC sites IAW the testing and training schedules of the system being trained, per direction from the government. Ensure training stays current with the services offered throughout the life of the contract. As the system is updated to address End of Software issues, analysis will determine if additional training is required. The typical class size is 9-12 personnel per site. (CDRL A00x, ACTT Training Materials)

3.2.15. Contractor Acquired Property (CAP): The contractor shall procure the necessary hardware and/or cloud tools to fulfill the requirement of this contract as CAP in accordance with FAR section 52.245-1. Hardware tool shall be priced based on General Services Administration (GSA) pricing;

use of Government sources will be authorized upon award. Any disposal of CAP shall be accomplished via Standard Form 1428, Inventory Disposal Schedule.

3.3. Cyber Security

3.3.1. The contractor shall maintain the ACTT and C2WSPTT Certification and Accreditation (C&A) for operation with and on DoD Command, Control Communications, Computers (C4) systems IAW DoD and AF Certification & Accreditation policy, specifically DoDI 8510.01, RMF for DoD Information Technology (IT) (RMF-IT), and AFI 17-101, Air Force RMF Program .The contractor shall communicate vulnerabilities, as well as the state of the vulnerability (e.g., open,fix in progress, fix being tested, fixed), to the PMO. The contractor shall deliver material/reports in accordance with the National Industrial Security Program Operating Manual (DoD 5220.22-M). (CDRL A00x DoD RMF Package) http://www.esi.mil/

3.3.2. The contractor shall support security test and evaluation by the 96th Combined Test Wing or other independent Government evaluation facility, as required and directed by the Government.

3.3.3. The contractor shall comply with the National Industrial Security Program U.S.

Government Executive Order 13526 and shall ensure that cleared U.S. defense industry safeguards are in place for the protection of classified information in the contractor’s possession while performing work on this effort.

3.3.4. The contractor shall use Information Systems Security Engineering (ISSE) best practices to seamlessly incorporate requisite DoDI 8500.01, Cybersecurity, (March 14, 2014) requirements as identified by the system Authorizing Official (AO), throughout the entire process.

3.3.5. The contractor shall implement a CS approach that considers appropriate defenses to threats and ensures data availability, integrity, authentication, and confidentiality in accordance with DoD 8500-series requirements.

3.3.6. The contractor shall demonstrate and implement alignment of the software architecture and design with DoDI 8510.01, RMF for DoD Information Technology (IT), or current Cybersecurity (CS) requirements/processes.

3.3.7. The contractor shall provide support, source data, and analysis required to support the

Government in obtaining a software certification according to the latest process as determined by the designated Government officer. (CDRL A00x, RMF Package)

3.3.8. The contractor shall use a Source Code Analysis (SCA) tool to run security code scans and deliver the result to the Government. (CDRL A00x Technical Report – Study/Services)

3.3.9. The contractor shall work with the Information System Security Manager (ISSM) and

Government engineers to remediate and fix vulnerability findings continuously throughout the system lifecycle.

3.3.10. The contractor shall ensure the information system is compatible with, and uses, the

Assured Compliance Assessment Solution (ACAS), Information Assurance Vulnerability Alert Management (IAVAM), Security Content Automation Protocol (SCAP), and Security Technical Implementation Guides (STIGs) for vulnerability testing throughout the system lifecycle.

3.3.11. The contractor shall work with and accept input and feedback from the PMO ISSM during the process of this information system. The contractor shall retain final responsibility for satisfying certification requirements to obtain a software certification for the deployed systems under this effort.

3.3.12. The contractor shall provide a comprehensive CS design that meets requisite DoDI

8500.01 (March 14, 2014) and meets other CS requirements as stated in Government technical requirements documents as listed in this contract.

3.3.13. The contractor shall incorporate layered defense and resilience into the system architecture and design using the DoD RMF.

3.3.13.1. The contractor’s CS workforce shall maintain compliance with the CS contractor training and certification requirements in DoD Directive (DoDD)

8570.01 and DoD 8570.01-M, Defense Federal Acquisition Regulations Supplement (DFARS) 252.239-7001, and DFARS 2397103(b).

3.3.14. The contractor shall designate an individual as the contractor’s security lead. The security lead shall be knowledgeable in the RMF process and shall interact with the Government assigned CS personnel and participate in working groups/meetings. The security lead shall understand the DoD Authority to Operate (ATO) process and the Air Force tools that are used to maintain the ATO. The security leads shall have an understanding of ACAS, SCAP, STIGs, Group Policy Objects (GPOs) and Enterprise Mission Assurance Support Service (eMASS). The security lead shall have at least three (3) years of CS related experience and shall, at a minimum, be Information Assurance Technical (IAT) Level II certified in accordance with Table C3.T4 of DoD Manual 8570.01-M. The CS Lead shall have a current Air Force (AF) Common Access Card (CAC) and a Security Clearance of Top Secret. The Government will coordinate the provision of a CAC after contract award.

3.3.15. The contractor shall ensure all personnel are held accountable for securing code, including their subcontractors.

3.3.16. The contractor shall have the ability to process classified information. In the situation where information might become classified, the contractor shall use manual or automated methods to document the findings/vulnerabilities in a Classified Plan of Action & Milestone (POA&M) from a Government facility.

3.3.17. SECURITY: A DD 254 to the Top Secret/Special Compartmentalized Information

(TS/SCI) level will be issued as a part of this effort. Operations Security (OPSEC) requirements apply to this contract. OPSEC program managers will provide the appropriate Critical Information (CI) lists to the Contractor under separate cover.

Contractors conducting work on military installations will participate in the Installation OPSEC Program. Contractors will receive periodic training along with military and Government civilian counterparts. OPS EC program managers will provide the appropriate CI lists and the Program Protection Plan (PPP) to the contractor under separate cover. FAR Clause 52.204-2, FAR Clause 52.204-21 and DFARS Clause 252.204-7012 apply to this contract. These clauses deal with Information Protection and Protection of Information on Networks. (see Appendix 7 for website URL) (CDRL A00x, Program Protection Implementation Plan)

3.4. System Support

3.4.1. The contractor shall support event/exercises involving ACTT and C2WSPTT as directed by the Government. Exercise/event support is a priority for execution of the C2WSPTT program. The contractor shall provide reach back technical support to the Government supported training events as requested.

3.4.2. For C2WSPTT: The contractor shall support C2WSPTT exercise and events worldwide. The contractor shall be responsible for timely and complete submittal of the necessary information and forms directly to the appropriate Government Agency for the required passports, visas, licenses, and permits. The contractor shall be responsible for the sponsorship of its employees and their dependents and shall process said permits directly through the appropriate Government agency. Exercise support will include performing sustainment and maintenance efforts regardless of time zone disparity. The contractor shall maintain the C2WSPTT 95% threshold for simulation system availability with 95% objective simulation system availability during any exercise. The contractor shall provide on-site technical event and exercise support to include: pre-exercise preparation (development scenarios, build, event tests and documentation), model and integration support of event execution architecture, and on-site fixes (configuration changes, urgent DR changes). Estimate a total of twelve (12) site visits (includes six (6) trips CONUS and six (6) trips OCONUS), for one to two (1-2) personnel, for one to two (1-2) weeks in duration, each year.

3.4.3. For ACTT: The contractor shall support ACTT Training events worldwide. The Contractor shall be responsible for timely and complete submittal of the necessary information and forms directly to the appropriate Government Agency for the required passports, visas, licenses, and permits. The Contractor shall be responsible for the sponsorship of its employees and their dependents and shall process said permits directly through the appropriate Government Agency. Training support will include performing maintenance efforts regardless of time zone disparity. The contractor shall maintain the ACTT 95% threshold for system availability during any training.

3.4.4. The contractor shall provide ACTT and C2WSPTT Tier II Help Desk support.

3.4.4.1. The contractor shall provide Tier II Help Desk services to support Government events wherever/whenever ACTT and/or C2WSPTT are used.

Operating times of the Help Desk shall be Monday-Friday, 8am-5pm Central Standard Time (CST) (unless a shift is required in direct support to the warfighter and coordinated with the PMO) for technical assistance, support of multiple software versions, training, warranty, and maintenance.

The contractor shall provide an electronic capability for the user to send email or messages alerting the contractor of any issues. All requests shall be logged, recorded, actioned as appropriate, with results recorded. The contractor shall provide users and administrators the ability to contact the Help Desk by email, Defense Switched Network (DSN), or Commercial – Help Desk representatives shall provide on the spot help functions for callers; and respond to email inquiries within eight (8) hours. The contractor shall provide the Government with a 24/7 emergency point of contact in the event the system becomes non-operational during weekends or holidays. The contractor must have the ability to respond to Emergency Priority software patch requirements within twenty four (24) hours. The contractor shall have the Help Desk operational within seven (7) calendar days/five (5) business days of contract award. (CDRL A00x, Status Reports)

3.4.5. The contractor shall maintain a trouble ticket reporting system that tracks volume and closure rates of user tickets. This information is used to track the status of user tickets, ensure timely resolution, and ensure proper manning of the response team.

The contractor shall deliver the report IAW the CDRL to the Government. (CDRL A00x, Technical Report – Study/Services)

3.4.6. The contractor shall provide Progress, Status, and Management Reports and Status

Reports via Government directed web site (i.e., Naval Lift). (CDRL A00x, Status Report)

3.4.7. The contractor shall be available to attend and/or facilitate product demonstrations at the request of the user community and as directed by the PCO. Request for travel to attend these events shall be approved by the Government before any travel arrangements are completed.

3.5. Agile Test, Evaluation, and Integration

3.5.1. The contractor shall conduct and support system Test and Evaluation (T&E). The contractor shall document the T&E events and activities to be accomplished for the life of the program in a system Test and Evaluation Plan, and provide updates as required for any new and amended functions. The overarching plan shall describe the general approach of the test program. Test descriptions describing plans for specific tests shall be developed and submitted. Subject to review and approval by the Government.

3.5.2. For C2WSPTT, the contractor shall use accredited models when conducting simulated, component and end-to-end system testing. The contractor shall develop documentation consistent with MIL-STD-3022 to support the verification, validation, and accreditation of delivered models. As appropriate, the contractor shall supplement live tests with a Live, Virtual, Constructive (LVC) distributed simulation environment. Subject to review and approval by the Government.

3.5.3. For ACTT, the contractor shall perform in-plant testing, including, but not limited to, unit code tests, smoke tests, regression tests, quality assurance, security/vulnerability, and C2 integration testing as required. Government/contractor testing shall occur at any facility directed by the Government and is subject to review by the government.

3.6. Program Management

3.6.1. The contractor shall, in cooperation with the Government, conduct program control, quality assurance, configuration management, subcontract management, management of Government furnished resources, risk management, and security activities and shall employ a management process that can respond to dynamic changes in requirements (technical and/or schedule), requirements prioritization, and product implementation.

3.6.2. The contractor shall develop, update, and maintain a Data Accession List (DAL).

Data prepared by the contractor under this effort that is not a deliverable under a CDRL shall be identified on the DAL. Subject to review and approval by the Government. (CDRL A00x, Data Accession List)

3.6.3. Meetings:

3.6.3.1. Initial Kickoff: The contractor shall host the first kickoff/transition meeting within forty five (45) calendar days after contract award. This meeting results in the development of objectives for that period, review of CR/DRs, definition of architecture options, as well as the review and planning for testing and subsequent sustainment planning. The contractor shall focus on the technical, cost, and schedule portions of the program and may be held virtually or in person. The contractor shall plan the meeting, provide agenda, and track action items. The contractor shall provide conference minutes. (CDRL A00x, Technical Report – Study Services)

3.6.3.2. The contractor shall maintain a schedule including the activities of the prime contractor that captures the detailed tasks and timing of the work effort described in the contractor Work Breakdown Structure (CWBS) within the Government directed web site (i.e., Naval Lift) environment to include agile processes and sustainment, exercises/events, test, and product releases. (CDRL A00x, Technical Report – Study Services)

3.6.3.3. This agile-derived schedule shall correlate to the elements of the CWBS and be updated periodically (as requested by the Government) but no less often than the semi-annual Program Management Review (PMR) events, to accurately reflect the contract’s activities. Each CWBS item shall be directly linked to the schedule entry with appropriate sub-details. The agile schedule shall be used as a day-to-day execution tool and to periodically assess progress in meeting program requirements. The contractor shall provide the Government unhindered access to the agile scheduling tool and all project information. The contractor shall perform continuous analyses of the tasks and immediately report potential or existing problem areas and recommend corrective actions to eliminate or reduce schedule impact.

3.6.4. Associate Contractor Agreements (ACA)

3.6.4.1. The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the ACTT/C2WSPTT efforts which shall ensure the greatest degree of cooperation for the enhancement of the program to meet the terms of the contract (See Appendix 1 for instructions).

3.7. Planning and reporting

3.7.1. Contractor Work Breakdown Structure (CWBS)

3.7.1.1. The contractor shall develop a CWBS addressing maintenance, software enhancements, and management tasks. The CWBS shall address prime and any subcontractor and shall be maintained for the life of the contract. Subject to review and approval by the Government. (CDRL A00x, Technical Report- Study/Services)

3.7.2. Program Management Status Updates: The contractor shall submit a program management status to the Government monthly. The contractor shall present a status of software efforts, issues, CR/DR status, metrics, action item status, events, schedules, contract actions, and financial/cost matters/issues, and risks. Presentation materials shall be posted in Government directed web site (i.e., Naval Lift) Confluence. (CDRL A00x, Status Report)

3.8. Risk Management

3.8.1. The contractor shall implement a risk management process to identify, track, mitigate, and resolve all technical and programmatic risks for both the ACTT and C2WSPTT programs.

3.8.2. The contractor shall maintain the risk database on the Integrated Digital

Environment (IDE) (Government directed web site (i.e., Naval Lift).

3.9. Configuration Management (CM)

3.9.1. The contractor shall maintain a CM program visible on Government directed web site (i.e., Naval Lift). The CM program shall establish and maintain consistency of the product’s performance, functionality, and attributes with respect to its requirements.

The CM program shall establish and maintain control of all architectures, requirements, specifications, designs, drawings, interfaces, software, hardware, firmware, operational information, and documentation for the project. The contractor's CM process shall consist of configuration identification, configuration control, configuration status accounting, and configuration audits and shall provide the Government a CM plan. The contractor shall flow down CM processes to subcontractors and third party integrators. Subject to review and approval by the Government. (CDRL A00x, Technical Report – Study/Services)

3.10. Transition

3.10.1. The contractor shall develop a plan and execute transition-in activities at the start of the contract and transition and decommissioning activities at the end of the contract period. The transition and decommissioning plans shall address, with sufficient detail, the following activities (CDRL A00x, Software Transition Plan)

3.10.1.1. The contractor shall create a transition-in plan to be presented as part of the Initial Kickoff.

3.10.1.2. The contractor shall create a transition-out plan as directed by the Government.

3.10.1.3. The contractor shall transition both ACTT and C2WSPTT systems, architecture, technical requirements, documentation, GFP and usage information; identify and document any/all work remaining to be completed.

3.10.1.4. The contractor shall conduct knowledge transfer sessions as needed, to include briefings, training, and lessons learned.

3.10.1.5. The contractor shall transfer all trouble ticket database information for exercise/event activities.

3.10.1.6. The contractor shall transfer all knowledge of the CS processes for handling and tracking of Information Assurance Vulnerability Assessments (IAVAs), Time Compliance Network Orders (TCNOs), relevant patches, and functional application updates as they relate to both ACTT and C2WSPTT.

3.10.1.7. The contactor shall document all Point of Contact (POC) information.

3.10.1.8. The contractor shall transition all GFP as directed by the Government (CDRL A00x, Government Furnished Property)

Appendix 1 - Associate Contractor Agreements (ACA)

In accordance with paragraph 3.6.4 whenever entering into an ACA for any portions of the contract requiring joint participation in the accomplishment of the Government’s requirement the contractor shall include the following general information:

1. Identify the associate contractors and their relationships.

2. Identify the program involved and the relevant Government contracts of the associate contractors.

3. Describe the associate contractor interfaces by general subject matter.

4. Specify the categories of information to be exchanged or support to be provided.

5. Include the expiration date (or event) of the ACA.

6. Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

Appendix 2 – Terms Relative to War, Armed Conflict, Insurrection, Civil or Military Strife or Similar Conditions

In the event competent authority of the United States determines that due to war, armed conflict, insurrection, civil or military strife, or similar conditions, the safety of contractor/subcontractor personnel is threatened, the parties hereto will negotiate an equitable adjustment to the contract for costs incurred to retain such personnel in the Federal Republic of Germany or the Republic of Korea or to return such personnel and their dependents to the United States and secure replacements as applicable.

The conditions stated in the paragraph above of this clause shall be met, if and, when the United States Secretary of Defense, or any designated representative thereof, issues a determination that the safety of contractor personnel is threatened and defines the area affected. In such event, the parties shall negotiate the retention of contractor personnel in the Federal Republic of Germany or Republic of the Republic of Korea or the specified area, or removal of contractor personnel and/or their dependents from the Federal Republic of Germany or the Republic of Korea or the specified area, and the price adjustment(s) for such actions.

The contractor shall, to the extent that qualified personnel willing to serve in the Federal Republic of Germany or the Republic of Korea or the specified area are not available, be relieved of the requirement for continuing service in the Federal Republic of Germany or the Republic of Korea or that area during the period of hostilities. The return to the contractor's plant of any employee not willing to serve in the Federal Republic of Germany or the Republic of Korea or in such an area shall be determined to be for the convenience of the Government. However, the contractor shall make every responsible effort to provide uninterrupted contract performance by qualified personnel. The contract price shall be equitably adjusted by an amount arising from emergency evacuation of such personnel to the nearest place of safety and their return to the place of performance when and if appropriate. Likewise, the contract price shall be equitably adjusted by an amount associated with maintaining contractor presence in the hostile environment.

Notwithstanding the above, the activities and responsibilities of the United States Government (including both the United States Air Force and contractor services) under this program may be suspended at any time upon determination by the Secretary of State, or any designated representative thereof, that, due to war, armed conflict, insurrection, military or civil unrest, or any other conditions, the best interests of the United States so require. The parties hereto shall negotiate an equitable adjustment to the contract to reimburse the contractor for any special or additional costs resulting from such suspension.

Under no circumstances will contractor/subcontractor personnel be required to perform activities that would violate international laws of war and/or armed conflict or direct preparation thereof

Appendix 3 – Invited Contractor or Technical Representative Status Under U.S. – Republic of Korea (ROK)

Invited Contractor (IC) and Technical Representative (TR) status shall be governed by the U.S. - ROK Status of Forces Agreement (SOFA) as implemented by United States Forces Korea (USFK) Reg 700-19, which can be found under the "publications" tab on the US Forces Korea homepage.

(a) Definitions. As used in this clause-"U.S. - ROK Status of Forces Agreement" (SOFA) means the Mutual Defense Treaty between the Republic of Korea and the U.S. of America, Regarding Facilities and Areas and the Status of U.S. Armed Forces in the Republic of Korea, as amended.

"Combatant Commander" means the commander of a unified or specified combatant command established in accordance with 10 U.S.C. 161. In Korea, the Combatant Commander is the Commander, United States Pacific Command.

"United States Forces Korea" (USFK) means the subordinate unified command through which US forces would be sent to the Combined Forces Command fighting components. "Commander, United States Forces Korea" (COMUSK) means the commander of all U.S. forces present in Korea. In the Republic of Korea, COMUSK also serves as Commander, Combined Forces Command (CDR CFC), and Commander, United Nations Command (CDR UNC).

"USFK, Assistant Chief of Staff, Acquisition Management" (USFK/FKAQ) means the principal staff office to USFK for all acquisition matters and administrator of the U.S.-ROK SOFA as applied to US and Third Country contractors under the IC and TR Program (USFK Reg 700-19).

"Responsible Officer (RO)" means a senior DoD…