MTCCS-III_Base PWS_ver.3.5.pdf

PDF 478 KB Posted

Attached to
MISSION TRAINING COMPLEX CAPABILITIES SUPPORT (MTCCS) III
Solicitation number
W900KK-26-SSN-MTCCS-III
Issued by

About this file

Performance Work Statement Summary

This is a Performance Work Statement (PWS) for the Mission Training Complex Capabilities Support (MTCCS) III contract, an Indefinite Delivery Indefinite Quantity (ID/IQ) Multiple Award Task Order Contract (MATOC) effective as of January 27, 2026. The contract supports the Department of the Army's Mission Training Complex, which provides collective training and sustainment on Army Mission Command Information Systems (MCiS), the Command-and-Control Warfighting Function, and Mission Command doctrine using Live, Virtual, Constructive, and Gaming (LVC-G) models. The contract may be utilized at any MTC or Regional Simulation Center location worldwide and serves Army Commands, Army Service Component Commands, Army Corps, and Direct Reporting Units.

The PWS is organized into three primary task areas and five supporting task areas. Primary tasks include: (1) Training and Exercise Support covering collective training, exercise planning, scenario development, exercise control, information operations, and After Action Reviews; (2) Simulation Support encompassing constructive simulations, intelligence simulations, virtual training systems, and Games for Training; and (3) Cybersecurity and Risk Management Framework (RMF) compliance. Supporting tasks include Plans and Operations, Technical Services and Support, Information Management, Training Environment Integration, and Logistics. Key requirements specify that contractor personnel must obtain and maintain appropriate security clearances (ranging from Secret to TS/SCI), complete mandatory training (cybersecurity, anti-terrorism, OPSEC, CTIP), comply with RMF and DoD cybersecurity standards, and support exercises ranging from squad-level to theater-level operations. The contractor must provide dedicated exercise planners, technical support for network infrastructure, database creation and management, MCiS administration, geospatial products, and comprehensive logistical support. Performance standards emphasize quality, timeliness, and compliance with applicable Army doctrine and regulations, with specific standards to be detailed in individual Task Order PWS documents.

View the file

Other files

On GovTribe

Work with this file

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

Text version

CUI /// PROCUREMENT SENSITIVE

Performance Work Statement (PWS) For

Mission Training Complex Capabilities Support (MTCCS) - III

Version 3.0 As of 27 January 2026

Contents

C.1. GENERAL

C.1.1. Introduction C.1.2. Objectives

C.1.3. Scope C.1.3.1. Performance Work Statement (PWS)

C.1.3.2. Performance Standards

C.1.4. Contract Employee Status C.1.4.1. Employment of Government Personnel

C.2. GENERAL REQUIREMENTS

C.2.1. Task Order (TO) Management

C.2.2. Quality Control Program C.2.2.1. Quality Assurance

C.2.3. Security Management

C.2.3.1. Security Policy Compliance C.2.3.2. DD Form 254

C.2.3.3. International Traffic in Arms Regulations (ITAR) C.2.3.4. Personnel Security Clearances

C.2.3.5. Defense Information System for Security (DISS) C.2.3.6. Derogatory Information

C.2.3.7. Access to Installations and Facilities

C.2.3.8. Operational Security (OPSEC) C.2.3.9. Access and Handling of Information

C.2.3.10. Physical Security C.2.3.12. Sensitive Compartmented Information Facility (SCIF)

C.2.4. Personnel Requirements C.2.4.1. Privileged Access

C.2.4.2. Personnel Conduct

C.2.4.3. Identification of Contractor Employees C.2.4.4. Required Government Accounts

C.2.4.5. Accompanying the Force C.2.4.6. Employee Termination

C.2.5. Personnel Training Requirements

C.2.5.1. Cybersecurity/Information Assurance (IA) Training

C.2.5.2. New Equipment Training (NET) C.2.5.3. Anti-Terrorism (AT) Training

C.2.5.4. OPSEC Training C.2.5.5. Combating Trafficking in Persons (CTIP)

C.2.5.6. Other Training C.2.5.7. Government Funded Training

C.2.5.8. Professional Development Certification

C.2.6. Surge Support C.2.7. Reserved

C.2.8. Contractor Manpower Reporting Application (CMRA) C.2.9. Material/Data Rights

C.2.10. Applicable Publications (See Attachment XXX-Tech Exhibit)

C.3. PERFORMANCE REQUIREMENTS

C.3.1. General Tasks

C.3.1.1. Reporting C.3.1.2. Scheduling and Event Coordination

C.3.2. Training and Exercise Support, and Integration C.3.2.1. Collective Training

C.3.2.2. Exercise Planners C.3.2.4. Scenario Development and Management

C.3.2.5. Event Life Cycle Support

C.3.2.6. Exercise Support Plan (ESP) C.3.2.7. Exercise Design Products

C.3.2.8. Exercise Control (EXCON) and Response Cells C.3.2.9. Information Operations (IO)

C.3.2.10. AAR

C.3.2.11. Multinational (MN) Support

C.3.2.12. Academic Support

C.3.2.13. Non-Standard Events C.3.3. Not Used

C.3.4. Leader Training C.3.4.1. Leader Training Products

C.3.5. Cybersecurity and Risk Management Framework (RMF) C.3.5.1. Cybersecurity and RMF Program

C.3.5.2. Cybersecurity/Information Assurance (IA)

C.3.5.3. Organizational Inspection Program (OIP) Network Documentation C.3.5.4. Incident Handling (IH) and Incident Reporting (IR) Support

C.3.5.5. Continuity of Operations (COOP)/Disaster Recovery (DR C.3.6. Technical Services and Support

C.3.6.1. Technical Overview C.3.6.2. Network Enclave Management

C.3.6.3. Training Networks

C.3.6.4. Training Network and Systems Management C.3.6.5. External Simulation Network Management

C.3.6.6. Strategic and Operational Networks C.3.6.7. System Administration (SA)

C.3.6.8. Encryption System Management C.3.6.9. Tactical Radio Network Systems

C.3.6.10. Network Configuration Management

C.3.6.11. Day-to-Day Technical Support C.3.7. Information Management (IM)

C.3.7.1. Information Management Support C.3.7.2. Assistance to MTC Workforce

C.3.7.3. Information Management (IM) SOP C.3.7.4. Portal/Websites Creation

C.3.7.5. Manage Information Storage

C.3.7.6. Exercise/Event Technical Historical Data Sets (HDS) C.3.8. Training Environment Integration

C.3.8.1. Systems Integration Support C.3.8.2. MCiS Stimulation

C.3.9. Constructive Simulation Support C.3.9.1. Constructive Simulation Support

C.3.9.2. Administer Constructive Federation Environment and Model Servers

C.3.9.3. Constructive Model Database Creation C.3.9.4. Constructive Client Training

C.3.9.5. Operate Constructive Simulation Client C.3.9.6. Event Test Support

C.3.10. Intelligence Simulation Support C.3.10.1. Intelligence Simulation Planning, Configuration, and Execution

C.3.10.2. Operate Intelligence Simulation Client

C.3.10.3. Intelligence Simulation Integration C.3.10.4. Intelligence Simulation Operation

C.3.11. Virtual Simulations / Games for Training (GFT) Support C.3.11.1. Virtual Training Systems

C.3.11.2. Games for Training (GFT) C.3.11.3. GFT/Virtual Training Systems Scenario Development

C.3.11.4. GFT/Virtual Training Systems Test and Evaluate

C.3.12. Mission Command Information Systems (MCiS) C.3.12.1. MCiS Support to Training

C.3.12.2. Operate MCiS C.3.12.3. Individual Training Support (MCiS Training)

C.3.13. Geospatial Management C.3.13.1. Geospatial Products

C.3.13.2. 3D Geospatial Models

C.3.13.3. Emerging Geospatial Generation Technologies C.3.13.4. Geospatial Generation System and Security Administration

C.3.14. Logistics Support to Training C.3.14.1. Logistics Support to Training

C.3.14.2. Material Support to Training C.3.15. Event Set-up and Recovery

C.4. LOGISTICAL SUPPORT

C.4.1. Government Provided Items and Services C.4.1.1. Government Provided Facilities

C.4.1.2. Facilities Support C.4.1.3. Property Management

C.4.1.4. Equipment C.4.1.5. Office Communications and Automation

C.4.1.6. Materials

C.4.1.7. Use of Vehicles C.4.1.8. Services. Not applicable

C.4.2. Contractor Furnished Items and Responsibilities C.4.2.1. Facility Clearance

C.4.2.2. Contractor Purchases

C.5. RESERVED

C.6. DEFINITIONS AND ACRONYMS

C.6.1. Definitions. (See ATTACHMENT X –DEFINITIONS) C.6.2. Acronyms. (See ATTACHMENT X –ACRONYMS)

C.1. GENERAL

C.1.1. Introduction. The Department of the Army (DA) G 3/5/7 has designated the Mission Training Complex (MTC) as the vehicle for providing collective training and sustainment on Army Mission Command Information Systems (MCiS), the Command-and-Control Warfighting Function (WfF), and the Army’s approach to

Mission Command (MC) using a variety of tools and Army fielded systems. This doctrine outlining the MTC mission is found in the Army’s Training Circular (TC) 6 series. MTC’s supports small unit (Squad through Company), Medium units

(Battalion through Brigade), and large units (Echelons above BDE) in training environments replicating Multidomain Operations. The Army fields digital MCiS to units from platoon through theater level. MTC’s focus on realistic and demanding training. MC focuses our support on a unit’s organizational leadership and supporting staff. MC doctrine requires Commanders and their staffs to issue intent-based orders, which empowers units at every echelon with the freedom to improve and adapt in a complex Operating Environment (OE). Organizational leaders and their staffs must conduct realistic and relevant training, which builds trust within formations that translates to mission accomplishment on the battlefield. Live, Virtual, Constructive, and Gaming (LVC-G) models and simulations are required to create realistic and challenging training events that closely replicate conditions a unit would face on the battlefield.

C.1.2. Objectives. The Contractors shall support individual through collective MC training, WfF training, the Military Decision-Making Process (MDMP), Games for

Training (GFT), the Joint Operational Planning Process (JOPP), NATO Operational - Level Planning Process, mission rehearsal, and constructive simulations exercises.

Constructive simulation training exercises include planning, preparation, set-up, execution, and recovery. These training events and exercises may occur concurrently or separately. The Contractor shall assist the Government in providing constructive simulation, GFT resources, and adaptive and responsive training for the individual through echelons above Brigade (EAB). The Contractor shall be capable of combining events into a simultaneous synthetic environment using the simulations and MCiS fielded to MTC. These services support U.S. Army Title 10 training, deployment training events, and Mission Rehearsal Exercises (MRE). These services also support Joint, Combined, NATO, and service component commander, staff and leader constructive simulation training and assistance in executing the

Combatant Commanders’ engagement strategy.

C.1.3. Scope. MTCCS-III is an Indefinite Delivery Indefinite Quantity (ID/IQ), Multiple Award Task Order Contract (MATOC). The contract is structured for maximum flexibility in providing for an expedited ordering process to satisfy the needs of customers primarily at the Army Commands, Army Service Component Commands

(ASCC), Army Corps, and Direct Reporting Units (DRU). This contract may be utilized at any MTC or Regional Simulation Center (RSC) location worldwide. Specific regulations, directives, standard operating procedures (SOPs), locations, etc. will be identified at the Task Order (TO) level. MTCCS-III contractor(s) will provide support in the following three primary task areas and five Supporting task Areas:

Primary Task Areas Task 1: Training and Exercise Support

Task 2: Simulation Support Task 3: Cybersecurity and Risk Management Framework (RMF)

Supporting Task Areas Task 4: Plans and Operations

Task 5: Technical Service and Support Task 6: Information management

Task 7: Training environment integration Task 8: Logistics

Supporting task areas are considered integral to supporting the Primary task areas and SHALL NOT be ordered on a stand-alone basis for any task order.

C.1.3.1. Performance Work Statement (PWS). This MATOC PWS conveys the basic scope and performance requirements, however not every task included here will be used in each Task Order (TO); to this effect all tasks in this PWS shall be read to include, “as directed in the TO”. Individual TO PWS will provide the specific tasks and subtasks required by their requiring organization. Specific standards, metrics and assessment measures will be identified in the issued TOs. The general basis for performance standards provided in this PWS will reflect one or more of the following measures for the work to be done:

• Quantity (how much or how often must the service be performed)

• Quality (the required acceptable level of service)

• Timeliness (the timeframe/period for submission/performance).

C.1.3.2. Performance Standards. The performance standards in this MATOC PWS provide the general basis for measuring the performance of each requirement associated with the standard. Where metrics are cited for any general standard, they are used for the purpose of providing examples. Within the context and scope of the MTCCS-III PWS, it is the responsibility of the TO PWS to resolve and clarify the requirements and performance standards gained from the MTCCS PWS. For a given subtask in the MTCCS-III PWS, the absence of performance standards infers that the issuance of the standards will be solely from TO PWS.

C.1.4. Contract Employee Status. All personnel performing work under this PWS shall be employees of the Contractor and shall not be considered or treated as employees of the Government.

C.1.4.1. Employment of Government Personnel. The Contractor shall not employ any employee of the United States Government, either military or civilian, if such employment would create a conflict of interest, nor employ any of their relatives or individuals with whom the Government employee has a covered relationship, if such employment would result in a violation of Department of Defense (DoD) Regulation 5500.07-R, Joint Ethics Regulation (JER). This regulation restricts Government employees from engaging in several activities that create an appearance of impropriety or otherwise violate the law, including certain activities involving interaction with Contractors and their employees.

C.2. GENERAL REQUIREMENTS.

C.2.1. Task Order (TO) Management. The Contractor shall provide overall management and administrative efforts necessary to ensure that TO requirements are accomplished in accordance with the PWS.

C.2.2. Quality Control Program. The Contractor shall develop and maintain a quality control program to ensure service performance in accordance with this PWS and subordinate TO. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services.

C.2.2.1. Quality Assurance. The Government will evaluate the Contractor’s performance under this contract throughout the relevant TO period of performance (PoP). The Government will monitor the Contractor's performance by performing checks as contained in a TO Quality Assurance Surveillance Plan (QASP) (See Attachment X). The TO COR may inspect for compliance with contract terms throughout a TO PoP. The TO COR’s evaluation will be based on the Contractor’s compliance with the requirements set forth in this PWS and the TO PWS.

C.2.3. Security Management. This PWS and subordinate TO are for operations and operational services employing equipment that may contain classified information up to and including Top Secret/Sensitive Compartmented Information (TS/SCI). The

Contractor shall comply with all applicable security requirements—physical, personnel, and information. The Contractor shall ensure personnel perform physical security, classified information security, and cybersecurity tasks IAW applicable regulations to safeguard classified information and equipment, high value Government purchased and owned equipment, and software. The Contractor shall obtain all required certifications and clearances, including personnel security clearances.

C.2.3.1. Security Policy Compliance. The Contractor shall comply with Federal Acquisition Regulation (FAR) 52.204-2, Security Requirements. The Contractor shall comply with security policies and standard operating procedures (SOP) at MTC and RSC sites as well as applicable DoD, Army, Army Command, Army Component

Command (ACC), and local Command security regulations and policies.

C.2.3.2. DD Form 254. The security requirements in this TO are in accordance with the attached DD Form 254. The Government will provide the DD Form 254 (See Attachment 3) to the prime Contractor during Phase In and before the start of each exercised Option Year. The Contractor shall provide the DD Form 254 for all sub- Contractors on the contract for the same period. The Government and the Contractor will use the Army Centralized Contracts and Security (ACCS) Portal for these actions.

C.2.3.3. International Traffic in Arms Regulations (ITAR). ITAR is a set of US

Government https://www.law.cornell.edu/wex/regulation regulations that control the import and export of defense products and services. The purpose of ITAR is to safeguard national security, and to further American foreign policy interests.

C.2.3.3.1. The Contractor shall acquire and maintain proper licensing and clearance by the Department of State to allow technical data exportation. ITAR licensing acquisition timelines will be determined by the Government and stated in each TO

PWS.

C.2.3.3.2. The Government will identify Countries participating in events or exercises during event planning based on individual TO requirements.

C.2.3.4. Personnel Security Clearances. The services provided under this PWS and subordinate TO require Secret clearances and in some cases TS clearances with access to SCI. All Contractor personnel performing work under a TO shall have at the minimum, an Interim Secret clearance with US ACCESS at start of full performance and shall maintain the level of security required for the life of the TO. A Contractor employee failure to maintain a valid security clearance shall result in the Contractor employee not being allowed to perform duties contained in a TO. Such failure of an employee does not relieve the Contractor from timely performance of the TO requirements. All Contractor personnel requiring privileged accounts on classified

Government Information Systems and/or networks require a Single Scope Background Investigation (SSBI) or Tier 5 investigation, to include a current SSBI- Periodic Reinvestigation (SSBI-PR), or Tier 5 Reinvestigation (Tier 5R) if applicable, even if the individual does not require access to information classified as TOP

SECRET.

C.2.3.4.1. SECRET Access. Contractor personnel requiring SIPRNET accounts shall have a final SECRET Clearance.

C.2.3.4.2. TOP SECRET Access. Contract personnel requiring routine access to a

SCI facility (SCIF) shall have a final TS/SCI clearance. Contractors who operate the https://www.law.cornell.edu/wex/regulation

Upper Enclaves for WARSIM, ACE-IOS, IEWTPT or other systems as designated by the Government shall have a CI-POLY prior to operating the systems.

C.2.3.4.3. Sensitive Compartmented Information (SCI) Access. The Contractor

FSO shall establish an Army Centralized Contracts and Security (ACCS) portal account with Intelligence and Security Command (INSCOM) by emailing usarmy.belvoir.inscom.list.contractor-support-element@army.mil. The FSO shall ensure the accurate CAGE codes registration with ACCS. The Contractor shall nominate personnel to receive SCI Indoctrination based on their duties and place of work. The individual TO Government SCI contract monitor (CM), is the final approving authority regarding SCI indoctrinations.

C.2.3.5. Defense Information System for Security (DISS). The Contractor shall vet all employees through (DISS), or its successor system, to ensure they have proper background checks for Common Access Card (CAC) and security badges. The FSO shall enter accurate CAGE codes and personnel status in DISS for assigned Contractor personnel. The Contractor shall submit information into DISS for each contract employee providing support under this contract.

C.2.3.6. Derogatory Information. The FSO shall immediately notify the relevant TO Security Manager (Government) and CM (as appropriate) upon receipt of any reported derogatory information that might adversely affect any Contractor employee's clearance or access.

C.2.3.7. Access to Installations and Facilities. The Defense Biometric Identification System (DBIDS) provides access to US Army and DoD installations. All Contractor employees working under this PWS and subordinate TO shall possess a valid, up-to-date CAC (according to their accreditation status) and current registration in DBIDS through the local Installation Access Control Offices.

C.2.3.7.1. Installation Access Compliance. The Contractor shall comply with applicable facility and local installation access and local security policies and procedures. The Contractor workforce shall comply with all personal identity verification requirements as directed by DoD, Headquarters, Department of the Army

(HQDA), and/or local policy. The Contractor shall provide all information required for background checks as required by local authorities.

C.2.3.8. Operational Security (OPSEC). The Contractor shall comply with all applicable DoD, Department of the Army (DA), and local security regulations and procedures during the performance of this PWS and subordinate TO. The Contractor shall safeguard, and not disclose procurement sensitive information, computer systems and data, Privacy Act data, and Government personnel work products obtained or generated in the performance of this PWS. Neither the Contractor nor any of its sub-contract service providers shall disclose or cause to disseminate any information concerning operations of military activities to unauthorized personnel.

Such action(s) could result in violation of the contract and possible legal actions.

C.2.3.8.1. OPSEC SOP. The Contractor shall develop an Operational Security

(OPSEC) Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the Government per AR 530-1. The

Contractor shall identify an individual to serve as the OPSEC Coordinator IAW the

TO.

C.2.3.9. Access and Handling of Information.

C.2.3.9.1. Privacy Act and Sensitive Information. The Contractor shall comply with requirements of DoD Directive (DODD) 5400.11 regarding control of privacy act information. Specifically, the Contractor shall ensure that any personally identifiable information (such as, but not limited to, individuals names and associated personal contact information or social security numbers) is restricted to access required for execution of this TO and is not disclosed or stored on any unsecure systems.

Personnel shall adhere to the Privacy Act, (5 U.S.C. § 552a) and applicable Agency rules and regulations. Contractor personnel shall not divulge, or release, privacy data or information developed or obtained in the performance of this contract award until made public or the government specifically authorizes.

C.2.3.9.2. Handling of Classified Material. The Contractor shall secure classified information IAW DoD, DA, and local Command policies and regulations. The

Contractor shall safeguard and sanitize classified material, removable media and equipment with classified information IAW AR 25-2 Information Assurance, AR 380-5

Department of the Army Information Security Program and NIST Special Publication 800-88 Guidelines for Media Sanitization. The Contractor will provide material not verified as being free of classified information to the Government for appropriate disposal. The Contractor shall not access, download, or further disseminate any classified information outside the execution of the defined contract requirements.

C.2.3.9.3. Release of Information. The Contractor shall release no classified information to a "non-U.S. citizen" without prior written approval from the responsible

TO COR. The Contractor shall not release any news (including photographs and films, video, public announcements, or denial or confirmation of same) or

Government related information on any subject matter within this PWS or any phase of any program herein to the media or any other unauthorized users without the prior written approval of the responsible TO COR. The Contractor shall release no controlled unclassified information without prior written approval from the responsible

TO COR.

C.2.3.10. Physical Security. The Contractor shall safeguard all Government equipment, information, and property provided for Contractor use in accordance with the local Government Security SOP and applicable Army Regulations. At the close of each work period, Contractor personnel shall secure all Government facilities, equipment, and materials IAW DoD, U.S. Army, and local Command physical security policies and SOPs. The Contractor shall assist the Government in identifying, reporting, and correcting physical security and information assurance violations.

C.2.3.12. Sensitive Compartmented Information Facility (SCIF). The Contractor shall provide operational support and management for SCIF at selected MTC locations as directed by the Government in subordinate TO.

C.2.4. Personnel Requirements.

C.2.4.1. Privileged Access. Contractor employees requiring privileged information system accounts shall comply with appropriate Information Assurance Technical (IAT)/Information Assurance Management (IAM) Level baseline certification, computing environment (CE), and recertification procedures (as applicable) outlined in DoDD 8140.01, DoD 8570.01-M, AR 25-2, AR 380-67, all related DoD and Army Cybersecurity policies and regulations. Contractor employees requiring privileged access shall have a certification in the primary CE that they will operate in, and certificates of training for all subsequent CE. Contractor personnel may be required to obtain multiple CE certifications or certificates of training if they are responsible for administering services/systems that span multiple CEs. Contractor personnel failing to meet IAT/IAM requirements will immediately have all privileged access accounts revoked. The Contractor is responsible for in-processing, out-processing, and managing the required certification documentation, appointment orders, and privileged access agreements of their employees on the Army’s Training &

Certification Tracking System (ATCTS). Quarterly, the Contractor shall assist the Government in validating positions requiring privileged accoun ts on information systems.

C.2.4.2 IA Certification. In accordance with DoD 8570.01-M, Contractor employees shall have appropriate DoD IA baseline and appropriate CE certifications for the components, devices, and operating system(s) they support, as required by this PWS and subordinate TO. Contractor personnel shall obtain the appropriate certifications prior to beginning work on a TO. The Government will not give any exceptions to this requirement. The Government will consider the designated position unfilled until the individual has met the baseline and CE certification requirements for his/her position.

For the time the positions remain unfilled by appropriately qualified and certified individuals, the Contractor may not receive the associated funding for said unfilled positions. The Government provides a six (6) month grace period to Contractor personnel who change IAT or IAM levels, specifically moving from a lower to a higher level to comply with baseline and CE requirements at the new level. Contractor personnel who do not achieve certification or full compliance at the end of the six (6) month grace period, will revert to the previously held IAT or IAM level, and will lose any permissions/access to Government Information Systems or services that require a higher category of certification.

C.2.4.2. Personnel Conduct. The Contractor is responsible for the performance and conduct of Contractor and subcontractor employees. The Contractor shall ensure that the conduct of Contractor employees does not bring discredit upon the U.S Army. Personnel employed by the Contractor in the performance of this PWS or any representative of the Contractor entering the Installation shall abide by the security regulations listed in a TO and shall be subject to Government checks as necessary.

C.2.4.3. Identification of Contractor Employees. All contract personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties shall identify themselves as Contractor personnel to avoid creating an impression in the minds of members of the public, they are Government officials (FAR 37.114(c)). The Contractor shall ensure all documents or reports the Contractor produces are suitably marked as Contractor products. The Contractor shall ensure appropriate disclosure of Contractor participation during meetings, conferences, phone calls, and electronic messaging.

C.2.4.3.1. Contractor-Provided Badges. The Contractor shall provide employees with easily readable identification badges.

C.2.4.3.2. Government-Provided Badges. The Government will provide all Contractor personnel with identification credentials (i.e. a security badge) displaying first name, middle initial, and employee’s last name, employee’s security clearance level, status as a contractor, and the employees’ photograph . Contractor employees shall have the Government issued identification credentials in their possession and visible while on Government property.

C.2.4.4. Required Government Accounts.

C.2.4.4.1 DoD Enterprise Email Account. The Contractor shall ensure all Contractor employees performing services under this TO obtain and maintain an DoD

Enterprise Email Account. Contractor personnel shall initiate an account request for the respective designated Government representative to approve. The Contractor shall establish an account within three (3) working days of the Contractor employee receiving his/her CAC. Changes in account status will be coordinated with the designated Government representative within three (3) days of the change.

Contractors will have a DoD Enterprise Email Account provisioned prior to issuance of SIPRNet Tokens or ASCL Tokens. Contractor personnel are required to follow the local Government organization’s in -processing policy to ensure proper provisioning of accounts and services.

C.2.4.4.2. Army Training and Certification Tracking System (ATCTS). All Contractor and associated subcontract personnel with access to government information systems shall be registered in the ATCTS at commencement of service at https://atc.us.army.mil.

C.2.4.4.3. Classified Accounts. The Contractor shall be responsible to ensure Contract employees requiring access to classified networks for duty execution will have the appropriate accounts.

C.2.4.5. Accompanying the Force. Contractors shall comply with Defense Federal

1151579333.CIV

Comment on Text Replaced by the Account Validation System (AVS) following ATCTS sunsetting 1 May 25

Acquisition Regulation Supplement (DFARS) Clause 252.225-7040 requiring performance or delivery in a foreign country. Contractors shall comply with DFARS

Clause 252.225-7043 and with the requirements of AR 525-28, Personnel Recovery.

In addition to AT/OPSEC considerations, all U.S. and non-local national Contractor employees will comply with the travel requirements in the DoD Foreign Clearance Guide (FCG), available at https://www.fcg.pentagon.mil/fcg.cfm. For more information on Contractor travel requirements, see paragraph C.2.9. Contractor

Travel. There shall be no mission failure due to failure to comply with the requirements of this paragraph.

C.2.4.6. Employee Termination. The Contractor shall notify the TO COR and Security Office of employee termination as soon as the termination date is known.

The Contractor shall ensure Contractor employees leaving a TO return all Government issued items such as CAC PRIV, keys, and Government issued badges.

The Contractor shall expedite the transfer of Government property if applicable. The Contractor shall provide the TO COR with written proof that all Government issued item have been returned NLT three (3) calendar days of Contractor employee termination date unless the COR grants a temporary delay. The Contractor shall ensure that contract personnel terminated for cause immediately surrender all

Government issued security badges, network access tokens, keys and key cards, to the Government. The Government will immediately revoke all access to Government Information Systems and services, and physical access to Government facilities.

C.2.5. Personnel Training Requirements. The Contractor shall provide a fully trained and certified workforce. The Contractor is responsible to provide training for Contractor personnel and to keep them abreast of advances in the state-of-the-art, or for training Contractor employees on equipment, computer languages, and computer operating systems that are available on the commercial market. When required training is available from the Government and there is an associated cost to the training, the Government may provide this training to the contractor.

C.2.5.1. Cybersecurity/Information Assurance (IA) Training. All Contractor employees and associated subcontractor employees must complete the DoD Cyber Awareness Challenge Training and read/sign an IT User Agreement before issuance of network access and annually thereafter.

C.2.5.2. New Equipment Training (NET). The Government may provide NET in conjunction with new simulations, MCiS, and/or changes to major information system platforms (e.g., operating systems, networks, or other hardware or software) or technology (MCiS include standard U.S. Army, U.S. Joint, and NATO systems). The Contractor shall support this training at the designated site with all applicable personnel and is responsible for cross-training subsequent employees as required.

For software changes that the Government determines does not require a NET, the Contractor shall evaluate the changes and incorporate appropriate in -house training for their personnel to maintain proficiency. If the NET does not occur at the MTC, the Government will pay travel costs to bring Contractor personnel to the training site.

C.2.5.3. Anti-Terrorism (AT) Training.

C.2.5.3.1. AT Level I Training. All Contractor employees shall complete AT Level I awareness training within 30 calendar days of new employees’ commencing work on this TO and annually thereafter. The Contractor shall submit certificates of completion for each Contractor employee and subcontractor employee to the. AT Level I awareness training is available at https://jkodirect.jten.mil/Atlas2/page/login/Login.jsf. The requirement for this training is covered in Department of Defense Instruction Number 2000.16, “DoD AT Standards”.

C.2.5.3.2. AT Awareness Training for Contractor Personnel Traveling Overseas.

Contractors required to travel overseas while performing requirements of this contract shall comply with the DoD Foreign Clearance Guide (FCG) at https://www.fcg.pentagon.mil/fcg.cfm and the Department of State Travel Warnings at http://travel.state.gov. There shall be no mission failure due to non-compliance.

C.2.5.3.3. iWatch Training. iWatch is a community awareness program created to educate the Army community about behaviors and activities that may have a connection to terrorism and criminal activity. The Contractor and all associated subcontractors working within an Army-controlled installation, facility, or area, shall brief all employees on the local iWatch program (training standards provided by the

Antiterrorism Officer for the requiring activity). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity. iWatch training can be accessed at https://www.mepcom.army.mil/Home/Contractors/.

C.2.5.4. OPSEC Training. All Contractor employees shall complete Operational Security (OPSEC) training. Per AR 530-1, Operations Security, new Contractor employees shall complete Level I OPSEC training within 30 calendar days of reporting for duty. All Contractor employees shall complete annual OPSEC awareness training.

C.2.5.5. Combating Trafficking in Persons (CTIP). All Contractor employees shall complete CTIP training. Per DoD Instruction 2200.01, “Combating Trafficking in

Persons” and FAR 22.27, 52.222.50, Combating Trafficking in Persons, new Contractor employees shall complete certification training within 30 calendar days of reporting for duty. All Contractor employees shall complete annual CTIP awareness training.

C.2.5.6. Other Training. Other mandatory Government training may be required to meet local, Army Command, ACC, HQDA, and DoD mandatory training directives.

For example: Threat Awareness and Reporting Program (TARP), ISOPREP, and Controlled Unclassified Information (CUI). The COR will inform the Contractor when new training requirements emerge.

C.2.5.7. Government Funded Training. The Government may fund training identified to accomplish specific tasks due to required equipment/system fielding and/or new or emerging requirements. Contractor employee training may be authorized by a TO COR when the Government determines it to be in the best interest of the Government. Government Funded training may occur if the specific training is advantageous to the Government.

C.2.5.8. Professional Development Certification. The Contractor shall ensure their workforce is trained, certified, and current with Army training doctrine, MTC SOPs, and training requirements.

C.2.6. Surge Support. At Government discretion, Surge Support may be required to provide services to meet temporary increased training requirements for specific or non-standard training events. The Contractor, together with the COR, determine the most cost-effective way to meet the increased training requirements. The Contractor, at the direction of the COR, shall analyze the training requirement, first determining if the surge support can be met by “flexing” current Contractor personnel hours. If the requirement exceeds the ability of the Contractor to “flex” hours, then the Contractor shall conduct a detailed analysis to determine whether providing overtime to current on-site personnel or bringing in additional “surge” personnel is the most cost-effective way to meet the requirement. For surge support requests that the Contractor is unable to accomplish under the fixed price structure, the Contractor shall present the COR with a detailed Rough Order of Magnitude (ROM) and detailed manning document to determine costs to. Performance shall not begin until the COR issues Travel Approval Request (TAR) or provides verbal approval in advance. The COR will determine the period of performance at the time the TARs are exercised.

C.2.7. Reserved.

C.2.8. Contractor Manpower Reporting Application (CMRA). The Contractor shall ensure ALL Contractor labor hours (including subcontractor labor hours) required for the performance of services under this TO are reported via a secure data collection site. The Contractor (and all subcontractors providing direct labor under this TO) shall report complete and accurate data for the labor executed during the period of performance during each Government fiscal year (FY), which runs from October 1 to September 30. The Contractor shall input the data into the appropriate CMRA reporting tool, accessed via a secure web site at https://sam.gov. While inputs may be reported any time during the FY, the Contractor shall report all data no later than

October 31 of each calendar year. The Contractor shall enter initial data into the appropriate CMRA tool, filling in all required data fields, to establish the basic contract record no later than 15 working days after receipt of TO award or contract modification incorporating this clause. The Contractor shall notify the COR when the basic contract record has been established in the appropriate CMRA tool.

Contractors may direct technical questions to the sam.gov help desk at https://sam.gov/content/help.

C.2.9. Material/Data Rights. The Government has unlimited rights to all technical data, documents, websites, and training material produced under this contract. All technical data, documents, materials, and created websites, to include the source codes of any software produced under a TO, shall be Government-owned and the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. The rules governing these assertions are prescribed in DFARS clauses 252.227-7013 Rights in Technical Data Noncommercial Items and DFARS 252.227-7014 Rights in Noncommercial Computer Software and

Noncommercial Computer Software Documentation.

C.2.10. Applicable Publications (See Attachment XXX-Tech Exhibit).

C.3. PERFORMANCE REQUIREMENTS.

C.3.1. General Tasks. The Contractor shall support the various exercises and training events, provide design planning, scenario development, and coordination for all events; preparation of the training (hardware and software) and the facility; provide technical assistance to the Government during the execution phase; support After Action Review (AAR); and operate and restore the training facility and areas to normal configuration.

C.3.1.1. Reporting. The Contractor shall prepare and submit periodic reports in accordance with each TO.

C.3.1.2. Scheduling and Event Coordination. The Contractor shall assist the Government with planning, scheduling, and controlling the resources allocated to meet the requirements identified in each TO. The Contractor shall assist the Government to coordinate, track, and de-conflict the usage of all MTC resources (personnel, equipment, and facilities). The Contractor shall update and maintain the

MTC calendars, record all training events and exercises requests, including individual, staff, and unit levels. The Contractor shall review the master calendar and inform the government of any potential conflicts or issues with projected training.

This calendar shall be kept current and display all MTC events, as the Government directs.

C.3.2. Training and Exercise Support, and Integration.

C.3.2.1. Collective Training. The Contractor shall provide collective training, exercise and integration support, training event design, planning, and constructive simulation support for (but not limited to): Military Decision-Making Process (MDMP), Staff Training Exercise (STX), Field Training Exercise (FTX), Command Post Exercise (CPX), Tactical Exercise without Troops (TEWT), Mission Rehearsal Exercise (MRE or MRX), and Warfighter Exercise (WFX) as defined in FM 7-0, 1151579333.CIV

Comment on Text We need to consider including or rolling in high level language to allow exercise and integration support for CTC rotations. This is most common currently in USARPACs RSC with the JMPRC (JMSC-IP as constructive sim provider) but may become more widespread as the enterprise training environment is fleshed out through modernization. The NGC / NGC2 change training in a way we don’t yet know, so we need to stay as flexible as possible to meet modernization requirements.

1151579333.CIV

We need a hook so the TOs include workload data collection associated with their training events, individual and collective. The Army is moving towards live modeling, which requires that we feed workload into the calculus for programming requirements in the PPBE. Standard training broken apart from non-standard training.

Training. The Contractor shall develop and replicate a realistic training environment that encompasses the dimensions and complexities of military operations. Training

Scenarios shall be focused on current operations (CUOPS) training, Military Decision Making (MDMP) and across all WfF identified by the unit commander. The

Contractor shall provide staff training events using simulations as directed by the Government. The Contractor shall provide over-the-shoulder support to the training audience, as the Government directs, to assist the training audience working through staff processes related to an exercise.

C.3.2.1.1. Large Training Events. Large training events or exercises typically occur at the Brigade through Corps-level and are multi-echelon (and increasingly multinational) events designed to train and stress the command and staff interactions between echelons. Large events and exercises are typically (but not exclusively) stimulated with a high-resolution federation of simulations (i.e. Joint Land Component

Constructive Training Capability (JLCCTC), the Joint Live Virtual/Constructive federation (JLVC), or a similar capability). Large events are typically planned using the Joint Exercise Life Cycle (JELC) with planning events normally occurring over

12–24-month period preceding execution. Large events and exercises normally run between 12 and 24 hours per day, over 10 to 14 consecutive days. Schedules may vary based on individual TO requirements.

C.3.2.1.2. Home station Training. The Contractor shall provide collective staff training, unit staff Drills, functional and integrated command post training events, and training mission command tasks outline in the Combined Arms Training Strategy

(CATS) based on a commander’s training objectives. BDE and below level training events and exercises usually occur over a 2–5-day period. BDE and below training events normally run 12-18 hours per day; 24-hour training events occur but are the exception. Schedules may vary based on individual TO requirements.

C.3.2.1.2.1. Medium Training Events. Medium training events typically occur at the battalion and brigade level and can be multi-echelon events. A low-overhead simulation, such as DXTRS or LOTS, or a constructive ground simulation or simulation federation such as JLCCTC or JLVC, are used to provide a Common Operating Picture (COP) for training or a Master Scenario Event List (MSEL) to achieve training objectives. Training Scenarios typically focus on current operations training, MDMP, or on specific Warfighting Functions such as Fires or Intelligence.

C.3.2.1.2.2. Small Training Events. Small unit training is typically focused on squad, platoon and company level (Company/Battery/Troop), using Games for Training

(GFT) or other virtual systems.

C.3.2.2. Exercise Planners. The Contractor shall provide dedicated exercise and simulations/technical planner(s) for each exercise and event. The Contractor shall provide dedicated exercise planning and execution expertise for replicating the dynamic complexities of the Operating Environment (OE) and OPFOR in compliance with Army Regulation (AR) 350-2 (OE/OPFOR Program).

C.3.2.4. Scenario Development and Management. The Contractor shall provide scenario creation, development, documentation, maintenance, and management services. The Contractor shall be responsible for maintaining knowledge and experience to provide products at two levels above the rotational unit, IAW current doctrine across and within each US WfF functional areas as appropriate to meet training objectives.

C.3.2.4.1. MSEL and Storyline Management. The Contractor shall provide storyline and master scenario events list (MSEL) development and synchronization throughout the planning process. The Contractor shall participate in, and as required lead, storyline and MSEL development conferences during the planning process. The

Contractor shall deliver Storyline and MSEL products IAW timelines established in the ESP and shall conform to guidance developed during scenario planning meetings and discussions and validated by the Government. The Contractor shall be prepared to provide dynamic scripting during execution, as the Government directs.

C.3.2.4.2. MSEL Tools. The Contractor shall execute MSEL management and operate current MSEL management tools as the Government directs. The Contractor shall provide system administration and configuration management functions for Government designated exercise/event MSEL tool servers.

C.3.2.5. Event Life Cycle Support. The Contractor shall participate in all events, as the Government directs. The Contractor shall provide SME support during all phases of exercise planning. The Contractor shall provide input, and as required, develop the draft planning products for exercise design and technical planning products.

Input and draft products shall be feasible, achievable, and supportable. The

Contractor shall meet the published exercise and events timelines. The Contractor shall support all testing events such as Risk Reduction Events (RRE), Event

Functional Tests (EFT) Event Operational Tests (EOT), and Operational Readiness Tests (ORT), and other tests as the Government directs. These events may occur outside the MTC footprints in allied and partner countries.

C.3.2.5.1. Event Life-Cycle Management. The Contractor shall assist the

Government with the management and administration of planning events. This shall include preparatory steps such as developing the calling message, setting the agenda and timeline, defining syndicates and syndicate deliverables. During execution of the event, when the Government directs, the Contractor shall lead the events. The Contractor shall meet all event timelines and requirements for event deliverables as determined in planning meetings.

C.3.2.6. Exercise Support Plan (ESP). For each exercise or event, IAW the JELC, the Contractor shall provide written input to the ESP that details how the Contractor will support the exercise, to include staffing, room build, and logistics support. The

Contractor shall provide Contract personnel, by name, against required positions IAW the Exercise Support Manning Document (ESMD). The Contractor shall provide ESP and ESMD input to the Government lead planner IAW the lead planner’s guidance and established suspense dates.

C.3.2.7. Exercise Design Products. The Contractor shall provide all required exercise products the Government directs, in support of an exercise. Exercise design products are those products defining the operational requirements of the exercise.

C.3.2.7.1. Product Creation. The Contractor shall create Operations Orders (OPORDS) and related products to support exercises. The Contractor shall provide products written and formatted in accordance with current applicable doctrine, as directed by the Government.

C.3.2.7.2. Operations Orders. The Contractor shall produce and develop operations orders (OPORDs) and related relevant annexes, Graphic Overlays, FRAGOs, and data products, up to Theater level Operations in accordance with current doctrine, as the Government directs. The Contractor shall write operations orders at the echelon(s) as the Government directs. The Contractor shall synchronize orders to the exercise objectives and facilitate the Training Audience meeting its training objectives.

C.3.2.7.3. Operational Graphics. The Contractor shall create and provide graphics with the OPORDs and FRAGOs in mediums compatible with current Mission

Command operating systems. The Contractor shall develop and produce graphical products as the Government directs. Graphics shall include Maneuver, Fires, Logistics, Intelligence, and other specialized graphics as the Government directs.

C.3.2.7.4. Additional Exercise Products. To ensure the training audience meets the training or exercise objectives, un-forecasted or un-planned products (such as FRAGOs or INTSUM) may be necessary based on the outcomes of Training

Audience activity and/or direction of the Senior Trainer or Exercise Director. The Contractor shall be prepared to produce additional FRAGOs that may depart from or alter previous pre-rotational FRAGOs in terms of mission, units, locations, and times.

The Contractor shall deliver the Exercise Products in a timeline the Government directs.

C.3.2.7.5. Opposing Forces (OPFOR) Support. The Contractor shall develop threat products that support the exercise intelligence planner and SIO during exercise planning and execution. These products include, but are not limited to, an OPFOR operational- command level operations order based on OPFOR doctrine, emerging hybrid threats, and current Threat Tactics, Techniques, and Procedures (TTP).

Products and services shall be accurate and delivered on time as specified in the Exercise Directive or training support plans. As part of MSEL and OPFOR development, the Contractor shall develop scripted products that mimic real-world intelligence product formats.

C.3.2.7.4. Exercise Technical Documentation. The Contractor shall develop all technical (RMF/Configuration Management) documentation required…

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

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