Att_07.1_CTC-IS_SOW.docx

STATEMENT OF WORK

FOR

LT2 COMBAT TRAINING CENTER

INSTRUMENTATION SYSTEM (CTC-IS)

POST DEVELOPMENT SOFTWARE SUPPORT (PDSS)

DELIVERY ORDER #3

SOW-2018-010

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI) 12211 Science Drive Orlando, FL 32826-3276

Engineering

Acquisition Logistics

Program Management

TABLE OF CONTENTS

REVISION LOG

PEO STRI

SOW-2018-010

15 Dec 2017 Version 1.0

PEO STRI

SOW-2018-010

15 Dec 2017 Version 1.0 iv

Scope

This Statement of Work (SOW) defines the requirements for the Combat Training Center Instrumentation System (CTC-IS) Post Development Software Support (PDSS) effort to be executed within the framework of the Live Training Transformation (LT2) Consolidated Product Line Management (CPM) environment. The efforts described in this SOW include the work required to support Life Cycle Management and maturation for the Instrumentation Systems software (SW) components at the Combat Training Centers (CTCs), to include the necessary processes and procedures to implement this effort within the LT2 CPM strategy and closely align with Life Cycle Product[-Line Management (LCMP) . The CTCs include the National Training Center (NTC), the Joint Readiness Training Center (JRTC), and the Joint Multinational Readiness Center (JMRC).

Introduction Background

The Combat Training Center Objective Instrumentation System (CTC OIS) Program fielded capabilities for the CTCs at the NTC at Fort Irwin, California; the JRTC at Ft. Polk, Louisiana. CTC OIS deployment was completed at the end of 2Q09 followed by transition to interim CPM ending 4Q09. CTC OIS modernized the instrumentation systems of the NTC and JRTC with new and enhanced capabilities, while integrating some legacy components into the Objective Instrumentation System (OIS) network. For purposes of this SOW, CTC-IS only includes those capabilities provided by OIS (as listed below), include the new range communication systems gateways and enterprise mobile architecture (e.g. mobile apps) and does not include the legacy instrumentation components beyond the OIS gateways (Table 1). The product team will provide engineering services, technology refresh, troubleshooting and bug fixes, training, real time software support and site activation.

Description of System

CTC-IS is an integrated system of computer SW and HW; workstations; databases; voice, video, and data recording, production, and presentation equipment; interface devices; and communication networks. It provides the tools for the Combat Trainer (CT) and the Training Analysts to collect, analyze, and present training performance feedback to the training unit in the After Action Review (AAR). Refer to Document Number PRF-PT-00115 Revision N for detail design description. The CTC-IS consists of the components and capabilities contained within Table 1 (see Section 3).

Applicable Documents

The following documents form a part of this SOW to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the latest issue of the Department of Defense Index of Specifications and Standards (Dodos) and supplement thereto.

Department of Defense Directives

Copies of the following applicable Department of Defense (DoD) Directives are available on the Worldwide Web (WWW) at URL: http://www.dtic.mil/whs/directives/.

Other Government Documents, Drawings and Publications

Copies of the following documents are available from ACC-Orlando, 12350 Science Drive, Orlando, FL 32826, or may be available at: http://quicksearch.dla.mil/ or http://www.lt2portal. mil.

Order of Precedence

In the event of conflict between the text of this SOW and the references cited herein, the text of the SOW shall take precedence.

Requirements

The contractor shall execute the functions of PDSS within the LT2 CPM framework in accordance with SOW-2018-007 and synchronized with the SOW-2018-009 Statement of Work for the CPM Construct and SOW-2017-033 Statement of Work for LT2 Hardware Product Line. The contractor shall accomplish PDSS tasks listed in paragraph 3 (including all sub-paragraphs) support the following conditions:

a. Correcting latent and emerging problems and deficiencies.

b. Improving software accuracy and dependability.

c. Achieve and maintain software stability

d. Increase system availability and eliminate exercise disruption

e. Implementing Army-mandated changes (i.e. migration from Windows server 2008 to Windows server 2016).

f. Implementing CTIA architecture changes as approved by the LT2 community.

g. Implementing Construct processes from requirement analysis to sustainment

h. Leverage LT2 HPL assets when its applicable (i.e. during tech insertion)

i. Integrating COTS software changes and updates.

j. Mitigating software and hardware obsolescence issues

k. Surge software support

Product Line Management, Organization and Processes Configurations Management (CM)

The contractor shall implement a CM process that establishes and maintains consistency of the CTC-IS items with its requirements and configuration information and peripheral systems. The CTC-IS CM process shall be fully integrated and synchronized with the LT2 CPM Construct processes. The CTC-IS consists of the following shared components and capabilities as listed in Table 1 as well as their associated responsible party.

Communications Infrastructure

CPM

Tracker Monitor

CPM

Portable WS - Support

Bar Code Scanner

CPM

Common Workstation

Work Area Peripherals

Archive and Repro

System External Gateway

(SEGW)

(DIS) Gateway

CPM

CPM

CPM

CPM

Air Warrior Gateway (DIS)

XML-to-CTIA Gateway

ADBS Gatway

TCN-to-XML Gateway

DIS-to-XML Gateway

Management Interface Provider (MIP)

CPM

Table 1. Shared Asset Mappings for HW and SW Packages

CM Planning

The contractor shall provide software CM planning to include projected software obsolescence and technical refreshment. The contractor shall also manage the implication of that planning. The contractor shall report on any baseline deviations during program technical reviews. All documentation delivered, such as Operator and Maintenance (O&M) manuals and training materials, and associated lists, shall reflect any changes to the product baselines. The contractor shall identify changes and impacts to the baseline using a Baseline Change Requirements (BCR). The Government will have the final review and approval authority over any change in product baselines.

Configuration Change Control

The contractor shall follow the LT2 Shared Asset Change Proposal (SACP) configuration change control process in accordance with the LT2 Operations Guide that ensures changes to the configuration baseline are identified, justified, recorded, coordinated, evaluated, and adjudicated by the Shared Asset Working Group (SAWG), Government Engineering Review Board (ERB) and the Government Program Manager.

Configuration Status Accounting

The contractor shall manage the capture and maintenance of CTC-IS configuration information necessary to account for the configuration of CTC-IS, as-is or will be implemented at each of the CTCs or other locations approved by the CTC-IS Government team.

Computer Hardware Enterprise Software Solutions (CHESS) Program

The contractor shall comply with the Army’s Computer Hardware, Enterprise Software Solutions (CHESS) program as defined within and across Delivery/Task Orders. Under PEO EIS, CHESS is the mandatory source for commercial their Information Technology (IT) purchases. CHESS contracts provide IT products and services that comply with NETCOM, Army and DoD policy and standards. Purchasers of commercial hardware and software must satisfy IT requirements by utilizing CHESS contracts and DoD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts requires a waiver. A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

System Support for Software Maintenance

The contractor shall implement a process for corrective and adaptive system software maintenance for the CTC-IS at the CTCs. These processes shall be integrated with, and utilize the LT2 CPM Construct. These processes shall synchronize with the LT2 CPM processes and procedures delineated in CPM Operation’s Guide. The contractor shall:

a. Provide engineering services for system software design, development, integration, verification, and validation.

b. Accept as GFE the CTC-IS Software Engineering Environment (SEE) and modify as required to meet the requirements of the contract. The contractor shall provide personnel and other necessary resources/services needed to support CTC-IS as a complete and cohesive software intensive system.

c. Follow the process described in SOW-2018-007 for the CPM Construct to track and prioritize problems, troubleshoot problems and identify root causes, fix and test, and then, semi-annually, implement at the sites while maintaining a CM baseline. The contractor shall establish a process which promotes documented interaction with the users (CTCs) to determine what changes or corrections are needed. The contractor shall establish a process whereby the CTC users are involved during baseline change efforts (e.g. capture user stories, capabilities demonstration events, etc.). The contractor shall coordinate their process with those on-site processes of the Warrior Training Alliance under the PD Field Ops support contract.

d. Administer fixes (outside of the semi-annual fixes) at NTC, JRTC, and JMRC as directed by the Government. Fix may require sending additional personnel to a CTC to correct the CTC-IS critical issues.

e. Provide and maintain applicable software licensing, subscription services, support agreements, warranties and extended maintenance agreements. The contractor shall identify different software and software licensing agreements, including cost and performance information to the Government.

f. Upload Core Instrumentation System (CIS) services/component related software and documentation into configuration management at the IDE and onto the LT2 Portal upon completion of services/component verification or as required to support engineering releases. All submittals to the LT2 configuration management repository at the IDE and LT2 Portal shall be in accordance with the LT2 Operations Guide.

g. Provide PDSS support to all three CTCs Live Fire (LF) subsystems (NTC, JRTC, and JMRC).

Hardware Product Line Synchronization

The contractor shall leverage HPL investments to support technology insertion, tech refreshment, obsolescence and failure rate management for the evolution/improvement of CTC-IS. The contractor shall synchronize all efforts of CTC-IS with HPL to achieve a holistic system of systems approach for the total life cycle systems management of the HPL and LT2 software P/L.

Figure 1: PM TRADE Product Line Synchronization Relationship Framework Rotational / On Site Support and Off Site Support

The contractor shall implement a process for rotational and onsite support of the CTC-IS at the CTCs. The contractor shall:

a. Provide onsite engineering support during and in-between rotations. Support shall consist of one men year level of effort at each site, NTC, JRTC and JMRC.

b. Onsite support personnel shall be the CPM representative at each site and act as the liaison officer with responsibity for coordinating responses to CTC-IS incidents between CTC operation groups, CPM Orlando, ATMP, and other CTC-IS stakeholders. Onsite support personnel shall collect quantitative and qualitiave data about the persfomrance of the system to include but not limited to issues, customer satification, user experience, merging mission needs. Onsite support personnel shall have the customer service skills to maintain good relationship with sites and stakeholders. Onsite support personnel shall communicatethe collected data and address all issues with Government team through the IPT. Onsite support personel shall provide status report after each rotation. Site support personnel shall support all software upgrades, installation and testing. Onsite support shall follow the established LT2 processes and offsite support guidance in the performance of the above tasks.

c. Onsite support personnel shall report to Government any critical issues which result into exercise disruption or major degradation within 2 hours of occurrence.

d. Onsite support shall continuously update the Government on critical issues until it is resolved and exercise resumes.

e. Onsite support shall maintain operational baseline and manage a remote connection from Orlando to NTC, JRTC and JMRC.

f. Be able to surge On site support personnel by rotating LT2 CPM software engineering team from the three CTCs as directed by the Government.

g. The contractor shall provide two men year 24 hours/ 7days active off site support during CTC rotations. The offsite personnel shall provide support remotely to all CTC connected sites (NTC, JRTC and JMRC). Offsite support personnel shall have software engineering experience with the ability to perform various software maintenance tasks, such as analyzing, locating and correcting programming errors/debugging, troubleshooting, and implementing enhancements. Site support personnel shall communicate and address all technical issues with Government team through the IPT.

h. The offsite support shall synchronize its activities with the onsite support team and maintain continuous communication with CTC Stakeholders, LT2 help desk and developmental teams.

i. In accordance with Army in Europe Regulation (AER) 715-9, Contractor Personnel in Germany – Technical Expert, Troop Care, and Analytical Support Personnel, the Contractor shall comply with all applicable local host-nation and international laws, rules, regulations, and policies, to include but not limited to the Technical Expert Status Accreditation (TESA) requirements for employees located in the footprint of US Army Europe (USAREUR). For any USAREUR positions needed to perform the scope of work, the Contractor shall determine whether to hire and employ TESA or Ordinary Residents (ORs) or a combination thereof, and is responsible for all business tax, regulatory compliance, and benefits implications of their employees’ status. More information can be found at the USAREUR DoD Contractor Personnel website at the following link: http://www.eur.army.mil/g1/content/CPD/docper/docper_germanyLinks.html

Testing

The contractor shall conduct a Test Readiness Review (TRR) prior to the start of formal test procedure execution; formal tests include the CTC lab verification test The contractor shall ensure that the test procedures for the modification effort traces to the system specifications. The contractor shall provide a copy of the Requirement Traceability Matrix (RTM) and brief it to the Government team during the TRR event. The contractor shall:

a. Conduct a Functional Qualification Test and provide integration and operator support as necessary for the new or upgraded capability which shall include operational use by trained operators at the CTC(s) through live training rotations as required.

b. Replicate or simulate the CTC operational environment during system levels of testing.

c. Conduct continuous system (regression) test. These events shall be synched with the development process. The contractor shall record and report the results after each event.

d. The contractor shall analyze the results of item testing and shall record the test and analysis results. Prior to the start of final test, the contractor shall upgrade the COTS products to the latest versions approved by the system software configuration control board.

DI-NDTI-80603A: Test Procedure DI - IPSC-81442A: Software Version Description(s) (SVD) DI-NDTI-80809B: Test/Inspection Report

Site Activation

The contractor shall coordinate with the CTC(s) for shipping and receiving, installation and integration, Government acceptance testing, and training of operators and maintainers. The contractor shall install, integrate, and perform a functional test of new capabilities and equipment at the fielding site.

System Security Certification and Accreditation

The contractor shall develop and maintain an CS process to guide management and design actions, document decisions, specify and track CS requirements, document certification efforts, and identify possible solutions. The contractor shall ensure the system meets all DoD and Army Regulations relating to and required for CS certification.

Cybersecurity (CS)

The contractor shall integrate CS into their management processes, document decisions, specify and track IA requirements, document certification efforts, identify possible solutions, and maintain operational systems security in accordance with (IAW) DoDI 8500.01, DoDI 8510.01 (RMF), CNSSI 1253, NIST SP 800-53, DoDI 8582.01 and AR 25-2. The contractor shall support accreditations under Risk Management Framework (RMF) IAW 8500.01 and DoDI 8510.01.

Implementation

The contractor shall implement protective measures to address identified vulnerabilities and weaknesses as directed by the Government. The contractor shall maintain Information Assurance and Vulnerability Alert (IAVA) & Security Technical Implementation Guide (STIG) compliance throughout the System Life Cycle. The contractor shall implement any required CS security controls. The contractor shall deliver all documentation required by RMF.

Verification

The contractor shall verify that protective measures appropriately address each specific security requirement. The contractor shall test the security controls appliances using Army approved IA tools to insure they meet a level of acceptability to the Certification Authority in preparation for certification.

Systematic Quality

The contractor shall comply with LT2 construct systematic quality requirements in support of CTC-IS software product. The contractor shall establish measurement points that quantify the performance of CTC-IS during rotation exercise including but not limited to system downtime, engagement pairing percentages, number of recovered events processed, number of site reported issues. The contractor shall capture and analyze the measurement points to continuously improve CTC-IS software product.

Certification and Accreditation

The contractor shall support the Government in the Risk Management Framework Security Assessment of the system in accordance with the RMF. The contractor shall address and implement the CS security requirements for the system based upon a Mission Assurance Category (MAC) Level and the Confidentiality Level (CL) as designated. For the period of performance of this contract, the contractor shall support the Government in maintaining IA compliance post-accreditation during events such as (a) Annual Security Review; (b) Annual Contingency Test; (c) Annual Security Control Test; and (d) Information Assurance Vulnerability Alerts and STIG compliance. The contractor shall:

a. Update all components of the RMF package necessary to maintain a fully accredited system. The contractor shall participate in all required RMF events.

b. Support the implementation of all required CS Controls, as well as supporting the successful testing, verification, and validation of those controls; test and implement all required STIG’s and IAVA’s and maintain successful Information Assurance Vulnerability Management (IAVM) throughout the development lifecycle of the system.

c. Support and maintain the accreditation of CTC-IS and assigned components throughout the lifecycle of the system.

Cybersecurity/Information Technology Training

All contractor employees and associated subcontractor employees shall complete the DOD IA Awareness Training before issuance of network access and annually thereafter. All contractor employees with privileged access working CS/IT functions must comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 at the start of work. Per DOD 8570.01-M , Defense Federal Acquisition Regulation Supplement (DFARS) 252.239.7001 and AR 25-2, the Contractor employees supporting cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DOD 8570.01-M must be completed upon contract award for the role to be performed.

Program Management

The contractor shall organize, coordinate, and control all program activities to ensure compliance with the contract requirements and timely delivery of required products and services.

Planning

The contractor shall establish and maintain a working Integrated Master Plan (IMP).

Cost Management

The contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the Delivery Order (DO). The contractor shall deliver a monthly contractor’s Progress, Status and Management Report.

DI-MGMT-81904: Contractor’s Progress, Status and Management Report (CPSMR) Risk Management

The contractor shall implement a risk management program that identifies, assesses, and mitigates risks to cost, schedule, and performance. The contractor shall provide a risk assessment report when requested by the Government.

Integrated Program Management Report (IPMR)

The contractor shall develop, and maintain an IPMR by logically networking detailed program activities. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the contract. The contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each scheduled activity and event.

DI-MGMT-81861A: Integrated Program Management Report (IPMR) Integrated Product and Process Development (IPPD)

The contractor shall establish and maintain a process for IPPD and participate in joint Government/contractor Integrated Product Teams (IPT) in a Performance-Based Business Environment to manage and integrate all tasks, activities, and data. The contractor shall facilitate Government insight into contract activities and establish working relationships with Government personnel that will enable continuing insight into all appropriate contract activities. The contractor shall ensure that all program documents are downloaded in the LT2 portal after Government approval.

Associate Contractor Agreements (ACAs)

The contractor shall maintain the capability to enter into ACAs for exchanging software data, accessing and using third party software and equipment, receiving technical support, working interface issues, transitioning to Life Cycle contractor Support (LCCS) and/or agreeing on equipment use and time. ACAs shall be maintained to achieve interoperability and common component goals, as applicable.

Sub-contractor Management

The contractor shall develop a Subcontractor Management Plan. The contractor shall maintain the capability to manage subcontractors in accordance with the Subcontractor Management Plan. The contractor shall integrate subcontractors into program IPT and program management and tracking systems such as management information systems, etc.

Reviews

The contractor shall coordinate and conduct quarterly Program Management Reviews (PMR) to provide a status of the program to the Government. The PMR shall provide a status and assessment of program cost, schedule, and performance with a flexible agenda responsive to current issues. The contractor shall update and brief the IPMR during the review.

General Protection and Credentialing Access and General Protection

The Contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Credentialing

The Common Access Card (CAC) shall be the principal identity credential only for those contractor employees supporting and requiring access to DoD installations, Government leased facilities, buildings and government information systems per FAR 52.204-9.

The prime and subcontractor shall coordinate with their government sponsor and complete DD Form 1172-2 in order to obtain a CAC. The prime and subcontractor employee will be issued a CAC only if duties involve one of the following:

· Require both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely;

· Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or

· Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more.

The prime and subcontractor employees must, at a minimum, have a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

The contractor shall ensure that all employees clearly display the prescribed identification at all times while they are working within government facilities and performing official duties in execution of contract requirements.

Contractor shall account for all forms of U.S Government-provided identification credentials issued to Contractor (or their employees including subcontractor employees in connection with performance) under the contract. Contractor shall return such identification credentials to the issuing agency at the earliest of any of the circumstances listed below, unless otherwise determined by the U.S. Government. The contracting officer may delay final payment under an individual DO if Contractor or subcontractor fails to comply with these requirements. The contractor shall return all identification credentials when;

1. No longer needed for contract performance.

2. Completion of Contractor employee’s employment.

3. Contract completion or termination.

Non-Credentialing

For contractors and all associated subcontractor employees that do not require CAC, but require access to a DoD facility or installation, shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

Post Award Conference

A post award conference shall be held at the contractor’s facility at a mutually agree to date after the award of the Deliver Order. The conference shall introduce the key IPT participants, identify points of contact and discuss both parties understanding of the scope of work and other contract issues.

Systems Engineering

The contractor shall provide the requisite engineering and management support to complete the CTC-IS PDSS within the LT2 CPM Construct and associated with the LT2 product line engineering and management philosophy. These tasks shall encompass the ancillary efforts associated with the development, dissemination, engineering, management, and maintenance of the product line components, and documentation.

Program and Design Reviews

The contractor shall conduct program and design reviews and applicable Technical Interchange Meetings for the Government and IPT members as required to execute and technically manage the CTC-IS PDSS and modernization efforts.

Supportability Engineering

The contractor shall perform supportability tradeoffs during the systems engineering process by considering the effect design decisions have on life-cycle cost, reliability, maintainability, and availability rates.

The contractor shall implement intelligent data analytics techniques to enhance support of CTC-IS and proactively identify risk areas and mitigate them. Data analytics is the process of collecting, organizing and analyzing large sets of data (potentially big data) to discover patterns and other useful information. The contractor shall leverage existing COTS product specialized to analyze large volumes of data for predictive analytics, data mining, text mining, forecasting, and system optimization.

Technical Data Management

The contractor shall provide technical data management to support system engineering processes, to provide the leadership and IPTs the key technical information required for sound decision making, and to facilitate the preparation of reports and reviews. The contractor shall continuously update the Technical Data Package (TDP) for the CPM CTC-IS core components and capabilities (listed in Table 1) and place them under configuration management.

Development Software Support Environment

The contractor shall ensure that the software support environment and the computer hardware and software are compatible, and that the software support system will facilitate the changing and upgrading of the software modules.

Logistics

The contractor shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. The contractor shall conduct trade studies, evaluate design and support alternatives, and establish system supportability preliminary design configurations consistent with system readiness and availability and life cycle cost goals. The contractor shall coordinate with existing LCCS using ACAs, develop initial fielding plans for the system and verify that the maintenance actions and support structure are aligned with the maintenance concept.

The contractor shall ensure the supportability of CTC-IS through planning, implementation, and verification of materials and services to meet the operational requirements. Readiness, availability, and supportability shall be the primary design factors. The contractor shall leverage LT2 initiatives (i.e., Lighthouse TDP initiative) in support of CTC-IS. The contractor shall adopt a support plan that minimize life cycle costs and maximize life cycle supportability by avoiding the use of proprietary items and recurring fees.

Logistics Support Analysis

The contractor shall identify support resources and infrastructure necessary for test and evaluation activities. The contractor shall analyze existing LCCS support structures and develop and define an optimized support infrastructure for production and deployment. The recommended support resources shall be sufficient to allow another contractor with comparable skills to assume operation, maintenance, and support of the system and sustain the system availability requirement. The contractor shall only use the form, fit, function, and interface requirements in the performance specifications for provisioning, training and maintenance planning.

Technical Publications

The contractor shall describe each O&M task in detail and in logical, systematic steps for the work to be accomplished. The O&M instructions shall accurately provide the technician with all the information needed to keep the equipment operational. It shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. All tools, test equipment and consumable items required to accomplish any maintenance or installation shall be identified just prior to and as part of the task. Government technical manuals (TMs) or Government-approved commercial O&M manuals shall be used as references for system and subsystem maintenance. All Government TMs and COTS manuals shall be reviewed to ensure changes, updates, revisions, or supplementation is not required to reflect the components actually being installed. All publications shall reflect the configuration of fielded hardware as documented in the product baseline. The contractor shall prepare O&M Manuals that provide instructions suitable for use by the intended audience of the system. The Operator Manual shall also include operator maintenance tasks such as preventive maintenance checks and services, inspection, lubrication, adjustment, and operator level repair and replacement tasks as needed. The contractor shall identify and document maintenance tasks for both levels of the maintenance concept. The contractor shall identify all required spare parts, consumables, tools, and test/support equipment associated with each task and identify the level of maintenance at which each task shall be performed.

Test Measurement and Diagnostic Equipment

The contractor shall develop alternative test procedures utilizing commercially available test equipment if special inspection equipment is developed and used for production.

Location of Training

The contractor shall conduct the training at the NTC, JRTC, and JMRC.

Course Completion Criteria

The contractor shall develop a criterion referenced performance test to measure the student’s ability to perform all job-related competencies.

Transition Planning

At the end of this DO, the contractor shall provide support for the transfer of PDSS responsibility to the Government or another contractor. Support shall include those services required to insure the effective, efficient transfer of responsibility as well as technical data, tools and test equipment and repair and spare parts, in sufficient detail and coverage to enable other personnel with comparable skills to the PDSS tasks as listed in this DO.

Language

The contractor shall provide all instruction, training materials and system documentation in the English language.

Disclosure of Information

The contractor shall comply with the protection standards and guidance described in DoD Manual 5200.1 to prevent foreign intelligence collection and/or the unauthorized disclosure of information.

CTC-IS PDSS Lab Environment

The contractor shall evolve, maintain, and run the Government provided CTC-IS PDSS Lab Environment located in the Integrated Development Environment (IDE) secured facility. The contractor shall be provided access to the IDE for cleared developers.

a. The contractor shall support component and product software development, integration and testing, CS implementation and testing, as well as verification of requirements required to support material releases to the CTCs.

b. The contractor shall ensure that CTC Lab supports all three CTC variance architecture.

c. The CTC lab shall contain all the necessary tools to simulate CTC operational conditions. This lab shall be utilized to ensure operational stability of the components, stability/accuracy of the interfaces, and assessment impacts of changes associated with other components within the product line.

d. The CTC-IS PDSS Lab shall provide support to the Help Desk, and ensure synchronization with the CM and management activities.

e. The CTC-IS PDSS Lab shall also support the common component development, common services development, and obsolescence remediation execution.

f. The contractor shall instantiate (as required) classified or unclassified integration labs, or extend the core integration lab to support individual products to ensure timely support and execution of changes to maintain operational readiness of the products.

Security The Contractor shall comply with the security regulations listed in the reference section of this document and the security requirements specified in Contracts Security Classification Specifications, DD Form 254 and addendums sheets.

The Contractor will be required to have a SECRET facility clearance with no storage requirements. Based on various task orders the Contractor could require access to a combination of collateral SECRET information, communications-security (COMSEC) information, Controlled Unclassified Information (CUI), Technical Information/Documents and For Official Use Only (FOUO) information only. If the security requirements of the contract or task order exceeds the requirements listed above, the GCA must have the SOW base DD 254 updated by the Cognizant Security Authority (CSA).

In performing this contract, the Contractor could have access to classified materials and information within the United States and overseas.

Performance of this contract will be worldwide as designated by individual Task Orders. Individual Task Orders will specify security clearance and security requirements within each PWS. Individual DD Form 254s will not be issued for each classified Task Order as the base DD 254 will be used.

Personnel Security The contractor shall issue security clearances only to those contractors who will have access to classified information. Some positions/duties may not require a clearance but all positions/duties will require investigation for duties and access to U.S. Government systems and technical information. The Contractor shall ensure that employees performing under this contract have the appropriate clearance not to exceed the requirements supported.

The contractor shall appoint a security officer who shall (1) be responsible for handling all security aspects of the work performed under this contract; (2) assure compliance with all DOD and US Army regulations regarding security listed in the reference section of this SOW. (3) shall establish and maintain an Insider Threat Program per DoDM 5220.22M para 1-202.

Security Training Security Training All contractor personnel have an individual and official responsibility for safeguarding national security information and controlled unclassified information, reporting derogatory information and properly responding to threat indicators. The contractor is required to meet the security training requirements listed below per DoDM 5220.22M NISPOM. The contractor shall make the training certificates of completion available to the Defense Security Services (DSS) on the requiring activity Industrial Security Specialist (ISS) during inspection and the COR upon request.

Antiterrorism (AT) Level I Training All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30-calendar days after the contract award or within 2-calendar workdays upon hire. The contractor shall submit certificates of completion for each affected contractor employee, to the COR, within 10 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://jko.sten.mil/courses/AT1/launch.html.

AT Awareness Training for Contractor Personnel Traveling Overseas Contractor employees and associated subcontractor employees shall receive Area Of Responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander when traveling into their AOR.

iWATCH Training The Contractor shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Officer). This locally-developed training shall be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 45 calendar days of contract award and within 30 calendar days of new employees commencing performance.

Threat Awareness Reporting Program (TARP) All contractors shall receive annual TARP training by a Counterintelligence (CI) agent or other trainers as specified in AR 381-12, 2-4b. The Contractor shall ensure its employees report threat-related incidents, behavioral indicators, and other matters of CI interest to the 2/13th G2 Office, the nearest military CI office, the Federal Bureau of Investigation, or the Defense Security Service.

OPSEC Awareness Training Contractor employees requiring access to Government installations, facilities and controlled access areas, shall complete Level I OPSEC Awareness training (IAW AR 530-1) within 30 calendar days after the contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable, and annually thereafter. New employees shall be trained within 30 calendar days of their reporting for duty and annually thereafter. The contractor shall make certificates of completion for each affected contractor employee and subcontractor employee available to the COR upon request OPSEC Awareness training is available at the following website: www.cdse.edu/popular/opsec.html Insider Threat Training The contractor and their subcontractors shall complete annual insider threat training and document employee participation. The contractor shall make certificates or sign in sheets of completion for each affected contractor employee and subcontractor employee available to the COR upon request. Information on the Insider Threat Program and Training is available at www.cdse.edu/itp-industry

Acronym List

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

R

S

T

U

V

W

Annex A: Contract Scope

This annex describes the work required under the Delivery Order. This annex should not be deemed as all inclusive. The contractor should consider all of the following tasks as necessary to fulfill the Delivery Order.

a. Maintain and manage the Combat Training Center Instrumentation (CTC IS) baseline.

b. Maintain and manage the CTC-IS PDSS Lab in the IDE.

c. Develop and deliver two updates to the CTC IS baseline per year. Delivery includes successful application of the baseline to the NTC, JRTC, and JMRC.

d. Develop and deliver two IAVA updates to the three CTCs per year.

e. Respond to critical baseline issues six times a year at each CTC. Response includes creating a patch, deploying the patch, and merging the patch into the next baseline release.

f. Maintain a configuration management system that tracks Discrepancy Reports and…