Attch 08 DO 01 SOW_Abrams_20200817.docx

SOW-2019-0021

W900KK-21-D-XXXX

12 June 2019 Statement of Work for the Gunnery Training Systems (GTS) – Abrams Tech Refresh, Concurrency, and Production Delivery Order (DO) XXXX Version 1.0

Prepared by U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

Engineering

Date: _________ Date: __________

Acquisition Logistics

Date: __________ Date: __________

Program Management

Table of Contents

SCOPE

The U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Project Manager Soldier Training (PM ST) and Product Manager Virtual Training Systems (PdM VTS) intends to retrofit, procure, integrate, produce, test, refresh hardware/software, and upgrade capabilities for the Abrams Gunnery Training Systems (GTS) in accordance with the M1A2 System Enhancement Package (SEP) v2 Advanced Gunnery Training System (AGTS) Prime Item Development Specification (PIDS), M1A1 Conduct of Fire Trainer-AGTS (C-AGTS) System Specification (SS), and the Abrams AGTS Interface Control Document (ICD) for Abrams Crew/Platoon Records. This Statement of Work (SOW) defines the scope of tasks that PdM VTS desires to have performed under the Indefinite Delivery/Indefinite Quantity (ID/IQ) Gunnery Training System (GTS) contract.

Introduction This SOW establishes the responsibilities for performance of tasks related to the production, testing, delivery, and installation of tech refreshes, concurrency upgrades, and production systems. There are Contract Line Item Numbers (CLINs) to configure, integrate, deliver, and install hardware and software tech refresh and concurrency upgrades, as well as to acquire new Abrams AGTS devices.

Goals and Objectives The objective of this DO is to tech refresh all M1A2 SEP v2 AGTS and M1A1 C-AGTS training devices, upgrade the existing M1A2 SEP v2 AGTS devices with the Field Modification 3 (FM3) upgrade, and produce additional mobile M1A2 SEP v2 AGTS devices.

The goals of this DO are to:

a. Tech refresh all M1A2 SEP v2 AGTS, M1A1 C-AGTS, and associated Pre-Brief/After Action Review (PAAR) systems

b. Replace obsolete legacy hardware components

c. Update software components, including Operating Systems (OSs) to the latest Government-approved versions

d. Maximize reuse of current training subsystem components

e. Reduce lifecycle support costs

f. Achieve Risk Management Framework (RMF) certification

g. Upgrade the M1A2 SEP v2 AGTS to be concurrent with the FM3 upgrade on the tactical vehicle

h. Produce additional mobile M1A2 SEP v2 AGTS devices that match the upgraded configuration Background PdM VTS has a requirement to update the M1A2 SEP v2 AGTS and M1A1 C-AGTS training system software and hardware baselines with a tech refresh and concurrency upgrades. This effort includes permanent, relocatable, mobile, and PAAR systems. The level of effort includes software and hardware upgrades for 56 M1A2 SEP v2 AGTS, 5 M1A1 C-AGTS, 12 M1A2 SEP v2 PAAR, and one M1A1 C-AGTS PAAR systems, with hardware spares to support the updated configuration. This effort will also include options for the production of 18 additional mobile M1A2 SEP v2 AGTS devices. In addition, the system will undergo Cybersecurity certification under the Risk Management Framework (RMF).

APPLICABLE DOCUMENTS

The following documents are applicable to this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of the SOW will be the governing requirement.

Government Documents

DFARS 252.225.7040

Contractor Personnel Supporting U.S. Armed Forces Deployed Outside the United States

DFARS 252.239.7001

Information Assurance Contractor Training and Certification

DOD 4500.54-G

DODD 8140.01

DOD Foreign Clearance Guide

Cyberspace Workforce Management

DOD 8570.01-M

Information Assurance Workforce Improvement Program

Non-Government Documents

REQUIREMENTS

Program Management The Contractor shall provide the overall management and administrative effort necessary to ensure the requirements of this contract are accomplished. The Contractor shall track program progress utilizing metrics. The Contractor shall consider life cycle costs while conducting trade studies and evaluating alternatives. The Contractor shall define and monitor metrics and Technical Performance Measures (TPMs) to evaluate each critical technical and management process and the conformance of evolving products with contract, cost requirements, and objectives. The Contractor shall identify progress, issues, and status of the program. The Contractor shall identify problem areas and corrective actions required to eliminate or reduce schedule impacts. The Contractor shall, at a minimum, report the following:

a. Problems and solutions

b. Time-lines and schedules

c. Plan of next month activities

d. Development and fabrication progress

e. Expenditures to date and cost projections

(DI-MGMT-80227) Contractor's Progress, Status and Management Report Integrated Master Plan (IMP) The Contractor shall implement, manage to, update, and maintain the contract IMP. The Contractor shall configure the system in accordance with the IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The Contractor shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews, and at government discretion. The IMP shall depict the contract work breakdown structure.

Integrated Master Schedule (IMS) The Contractor shall plan, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The Contractor shall plan the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the total program. These network activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The network shall be implemented on a computer based program management control system which utilizes critical path method network analysis, accepts parametric data input, and can be utilized to determine a probabilistic estimate of the program schedules and cost for reporting project progress. The network activities time and cost data shall be updated to reflect accomplished activities and any changes in activity time and cost estimates. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6 Financial Management The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item.

The CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

(DI-MGMT-81651) Contract Invoicing and Payment Report Earned Value Management Not required Integrated Baseline Review Not required Contractor Manpower Reporting Application (CMRA) Not required Product Line Management and Processes In support of the GTS product line, the Contractor shall develop a white paper to describe their approach and processes for managing the GTS product line. The Contractor’s approach shall ensure efficient product line processes for management and oversight of the product line technical activities, to include resources utilized across all GTS product line DOs.

All Abrams GTS software, digital information, and documentation will reside on the Live Training Transformation (LT2) portal. The LT2 portal is an Army repository for data and standards for the training community created under the CPMNext contract. Information uploaded by the Contractor onto the LT2 portal may be available to other Contractors on a need to know basis to perform work for the Army. The Contractor shall provide a plan that documents a path to conformance with the LT2 Product Line Operations and CM Guide. The LT2 portal and guides are located at (https://www.lt2portal.mil/). A Common Access Card (CAC) is required to access the LT2 CM repositories.

(DI-MISC-80711A) Scientific and Technical Reports Configuration Management The Contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs). The Contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The Contractor shall provide, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline (FBL) defined by the system performance specification, interface control documents, and software requirement specifications.

Configuration Management Planning and Management The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The configuration management process shall include changes made to the Cybersecurity (CS) configuration and associated documentation. The Contractor shall:

1. Plan implementation of the CM functions for the context and environment in which they are to be performed and manage in accordance with the planning

1. Determine the specific CM value-adding functions and levels of emphasis

1. Document how your organization will implement CM functions to provide the consistency between the system’s attributes, system definition information and the system’s configuration information, throughout the applicable phases of the life cycle

1. Identify resources required to implement the CM functions and ensure they are applied throughout the system’s life cycle

1. Assess the effectiveness of CM plan implementation and performance of the configuration management functions with performance measurements

1. Flow down responsibility for CM performance to subcontractors

1. Plan and identify information status levels for managing system configuration information and ensure that transmitted data products are usable Configuration Identification The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management. The Contractor shall:

1. Define the functional, performance, interface and physical attributes of the system and components

1. Determine the systems composition using its product definition information

1. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved

1. Assign unique unit identifiers to individual components of the system

1. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier

1. Uniquely identify information so that it can be correctly associated with the applicable configuration of the system

1. Apply information identification rules to maintain representation and version relationships

1. Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval

1. Establish complete, valid, and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed

1. Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to the system or within the system Configuration Change Management The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances. Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall:

a. Document and uniquely identify each change

b. Classify requested changes to aid in determining the levels of review and approval

c. Clearly and completely document request for change

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment to approve the change for implementation and incorporation in the system and its documentation

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility

f. Determine the effectivity for each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit

g. Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements

h. Document variances, when authorized by the appropriate level of authority Configuration Status Accounting The Contractor shall provide access to accurate, timely information about the system and its documentation through the integrated database. The Contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current and historical data. The Contractor shall:

0. Systematically record, safeguard, validate, and disseminate system information

0. Establish methods, processes and procedures to provide controlled access to system information

0. Capture configuration information as it evolves Configuration Verification and Audit The Contractor shall verify and audit the system configuration information to ensure that requirement attributes are met and accurately documented. The Contractor shall:

0. Verify the system attributes through a systematic comparison with the associated results of system tests, analyses, inspections, demonstrations or simulation models

0. Maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements Contractor Internal Hardware Build-Up Audit Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel approved by the QA Manager to verify the as-built configuration matches the configuration documentation prior to use of each part in production. During this process each product definition document will also be examined for proper format (compliance with American National Standards Institute (ANSI) Y14 series standards), completeness, currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part. A record of each product attribute verified shall be maintained and available through the LT2 documentation repository.

Government Sample Audit to Verify Product Baseline After completion of acceptance testing and any required configuration modifications, but prior to formal acceptance, the final product baseline shall be verified by the government by reviewing a representative number of drawings, associated technical manuals, logistics management information and manufacturing instructions to determine their accuracy in accordance with the final product configuration.

Physical Configuration Audit (PCA) The Contractor shall support the Government in conducting the PCA by providing the necessary space, tools, equipment, personnel, and documentation required for the activity. The PCA is the formal technical examination of the system “as-built” configuration against its technical documentation to establish or verify the configuration item’s product baseline. It is used to examine the actual configuration of each item (down to the lowest level of repair) in order to verify that the related configuration documentation matches the physical configuration. The PCA addresses accuracy of the documentation to include inspection of inventory/equipment lists, logistics product data, documentation, drawings, spares and all manuals. The documentation and equipment shall be examined to verify that all applicable safety labels along with incorporating applicable warnings are incorporated.

In addition to the PCA, the Contractor shall provide the necessary space, tools, equipment, personnel, and documentation required for the Government to perform the inspection of the complete system inventory. Each item shall be inspected to ensure Government property sticker affixed in a prominent location.

a. Verification of Serial number and Item Unique Identification (IUID). All items requiring an IUID marking, per contractual guidance, shall be marked with an IUID label that is constructed of a material capable of lasting the life of the item/system in its intended environment and operation. The IUID data shall be entered into the central registry for accountability/visibility

b. Equipment Inventory Records (EIR) for Government property accountability, Government specified format and data elements are accurate. Equipment record shall contain the following data: Complete Item Description, Original Part Number, National Stock Number (NSN), Serial Number, Quantity, Vendor Name, Vendor Point of Contact (POC), and Warranty Period

c. Cable naming, source, destination, and numbering details are on both ends of the wiring

The Contractor shall correct all discrepancies found by the Government during verification of the “as-built” drawings. The drawings shall include complete system level drawings of all equipment, wiring, network topology, and system architecture. Drawings shall either be new or revised with changes incorporated.

(DI-SESS-81022D) Configuration Audit Summary Report and Certification Software Configuration Management The Contractor shall establish and document a software configuration management process. The Contractor’s software configuration management plan may be incorporated into the software configuration process plans or may be a separate configuration management plan.

Software Configuration Control Board The Contractor shall establish and maintain a software configuration control board or equivalent responsible for configuration control of its software configuration items and related software products. The software configuration control board will be responsible for COTS (including open source) management including product and version identification. The Contractor shall obtain approval of the system Integrated Product Team (IPT) prior to committing to use any version of any COTS product. The Contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported.

Software Item Database The Contractor shall capture software data in an integrated database. The Contractor shall produce software item data to populate the software database. The software item database shall have the capability to establish, modify, make available, and maintain the integrity of the database. The Contractor shall maintain the system software item database until transition to the Government.

A schema shall be implemented for identification of software items and their versions. The Contractor shall perform the following: identification and recording of change request, analysis and evaluation of the changes; approval or disapproval of the request, and implementation, verification, and release of the modified software item. The database shall contain an audit trail whereby each modification, the reason for the modification, and authorization of the modification can be traced.

Systems Engineering Interface The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management system must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The information architecture must permit capture of change information and notify affected team members.

Engineering Change Proposals (ECP) The Contractor shall document and the IPT shall review all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), the contract schedule, and the general provisions of the contract.

(DI-SESS-80639D) Engineering Change Proposal (ECP) ECP Review In coordination with the government, the Contractor shall hold a requirements review on all proposed changes prior to the submittal of the engineering change proposal in order to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PEO STRI, or a formal meeting at the Contractor’s facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. The Contractor shall also be responsible for generating minutes of the review and provide them to the Government for approval.

(DI-ADMN-81505) Report, Record of Meeting/Minutes Variances The Contractor shall document the rationale and the potential impact to any Abrams GTS and its respective variances. The Contractor shall obtain approval before varying from any government-controlled baseline.

(DI-SESS-80640D) Request for Variance (RFV) Technical Performance Measures (TPM) The Contractor shall select technical performance parameters that reflect key indicators of program success. TPM parameter inter-relationships shall be depicted through construction of tiered dependency trees similar to the specification tree. Each parameter shall be correlated with a specific CWBS element. Parameters to be reported at each management review shall be selected from the total parameters tracked and shall be identified in the integrated master plan. As the configuration activity progresses, the achievement to data shall be tracked continually for each of the selected technical performance parameters. If the data falls outside the tolerance band a new profile or current estimate shall be established immediately. The current estimate shall be determined from the “achievement to date” and the remaining time and budget. An analysis shall be accomplished on the variation to determine the causes and to assess the impact on higher level parameters, on interface requirements, and on system cost effectiveness. For performance in excess of requirements, opportunities for reallocation of requirements and resources shall be assessed.

Risk Management The Contractor shall establish and maintain a risk management program to identify risks related to the project. The Contractor shall identify and track all risks and corrective actions required to mitigate the risks. The Contractor shall implement a risk assessment methodology that includes not only an understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic reassessment of these impacts on risk areas. The Contractor shall update, maintain, and execute program metrics to monitor issues and to determine the likelihood of risks occurring. The Contractor shall ensure that the risk management process is utilized to manage risks across all facets of the contract, including subcontractor activities.

(DI-MGMT-81809) Risk Management Status Report Management Reviews and Subcontractor Management The Contractor shall conduct Management Reviews at the request of the Government with a minimum of one every quarter. The Government and Contractor shall mutually agree upon the review location. The Management Reviews shall provide an accurate program overview and a detailed discussion of pre-selected topics. The Contractor shall manage subcontractors and shall be responsible for the performance of subcontractors.

The Contractor shall establish an IPT structure to address major areas (e.g., systems engineering, hardware configuration, software solutions, integrated logistics support, testing). The Contractor shall establish IPT charters and host regularly scheduled IPT meetings or teleconferences. Management reviews shall use IPT meetings/teleconferences to address systems production, status of activities, questions, and issues in a timely manner. The Contractor shall prepare the meeting agendas, document action items, document due dates, coordinate resolution, and track action items until closure. Action item closure shall require Contractor and Government approval. At a minimum, the Contractor shall conduct the following meetings and reviews:

Post Award Conference (PAC) / Start of Work Meeting The Contractor shall conduct a combined PAC/Start of Work Meeting held at the Contractor’s facility, at a mutually agreed upon date with the Government, within 20 working days after contract award. The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall place emphasis on the operating procedures, methodologies, and processes used in the execution of the contract. The meeting shall include the Contractor’s key team members identified in the proposal with emphasis on top level management of the program, agreement on metrics used as management indicators during the program and partnering approach to implement. The Contractor shall present the program IMS, IPT structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the GTS mission. The Contractor shall document action items, due dates and coordinate resolution and track action items until closure.

PAC Entrance Criteria The PAC entrance criteria shall consist of: Government acceptance of the PAC agenda, presentation materials, and the IMS.

The PAC Agenda shall include the following:

· Introduction and Overview

· Discussion and clarification of requirements

· Program Management Plan including subcontractors

· Risk Management Process and Report

· Quality Control Program

· IMS identifying critical path, milestones, and deliverables

· CWBS

· Configuration Management Plan

· Integrated Logistic Support Overview

· Revision of existing technical documentation (COTS & Technical manuals)

· Parts provisioning and selection

· Obsolescence management

· Long lead item identification and status

· Spares

· Tools and test equipment (if applicable)

· Warranty

· Inventory (Hardware/Software) Control

· Item Unique Identification (IUID) Marking Plan

· Disposal of removed GTS components

· Overview of current Management Information System (MIS)

· Contract Management Plan (i.e. invoicing, billing) PAC Exit Criteria The PAC exit criteria shall consist of the following:

· Government concurrence that all required PAC agenda items have been satisfactorily presented

· Government acceptance of the PAC CDRLs

· Submittal and Government acceptance of the PAC minutes Program Management Reviews (PMR) The Contractor shall conduct program management reviews on a quarterly basis in accordance with the IMS. The first PMR shall be no more than 90 working days after the combined PAC/ Start of Work Meeting. The Procuring Contracting Officer (PCO) and the Contractor shall mutually agree upon the location of the PMRs. The Contractor shall coordinate and provide all facilities and infrastructure for Government-Contractor meetings and separate breakout rooms for Government only meetings during the PMR. The PMR shall provide a program overview and shall include as a minimum:

a. Hardware and software configuration status

b. Risk and problem identification

c. Subcontract management/progress

d. Data collection and modeling

e. GTS Government Furnished Equipment (GFE) planning and status

f. Logistics planning

g. Test planning

h. Provisioning for training and technical publications status

i. Schedule status

j. Pre-selected topics of interest

k. CS status and progress (copies of all CS documents in draft format)

l. Human Factors Engineering

Status and information at the review shall reflect currency since the previous review. When possible, other program reviews such as technical reviews, technical manual reviews, etc. shall combine into the PMR. The Contractor shall also be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, coordinate resolution, and tracking of action items until closure.

Integrated Product Team (IPT) Meetings The Contractor shall host and participate in bi-weekly IPT meetings with Government representatives which address the full spectrum of the program concerns including system engineering, schedule, financial, integrated logistics support, CS, and testing. The Contractor shall document and timely submit the minutes to the Government team members.

Technical Interchange Meetings (TIMs) The Contractor shall conduct and participate in TIMs to be held at both Contractor and Government facilities. The specific locations, dates, and durations of the meetings shall be as specified in the IMS. The meetings shall be co-chaired by a Government and Contractor representative. The Contractor shall be prepared to explain the reasoning, assumptions, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The Contractor shall prepare drawings and other data to aid in the presentations. The Contractor shall have all the required personnel and resources present. The Contractor shall make available facilities for Government-only meetings. The Contractor shall prepare the meeting agendas and document the meeting results. Except where noted, meetings shall be considered fulfilled when all of the following items are completed:

· A formal review meeting has been conducted

· All action items requiring Contractor response have been documented and posted

· Submittal of meeting minutes Visitor Support The Contractor shall host Very Important Person (VIP) visits, arrange for, and provide demonstrations of system performance, program progress, and other system characteristics when notified by the Government as required. The Government will provide no less than 24 hours advance notice for VIP visits.

Subcontractor Management The Contractor shall manage and have agreements with subcontractors and partners as required. The Contractor shall integrate subcontractors and partners into program IPTs. The Contractor shall ensure the requirements of this contract apply to all subcontracts and associate contracts.

Obsolescence Management The Contractor shall implement an obsolescence management program. The Contractor shall analyze and recommend solutions after identifying any obsolete parts. The recommended solution shall be reviewed and approved by the Government.

Data Rights The Contractor shall obtain and deliver a minimum of Government Purpose Rights for all CDRLs, technical data, metrics, non-commercial software, and hardware, such that the Government can:

a. Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction

b. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes

c. Maintain, repair, modify, and upgrade a GTS using Government personnel and other Government Contractors

d. Compete future GTS requirements and upgrades

The Contractor shall disclose any part of their configuration data items that the Government does not have the minimum of Government Purpose Rights.

Government Furnished Information (GFI) The Government will provide available technical data necessary to accomplish the objectives of this contract upon Contractor request, or at the earliest possible opportunity. The Contractor shall secure alternate data collection or generation methods if the Government is unable to provide the technical data. The Contractor shall be responsible to secure, protect, and maintain the data provided as GFI.

Government Furnished Equipment (GFE) Upon contract award, the Contractor shall inventory all GFE and subsequently maintain records of all GFE. The Contractor shall submit annual inventory reports to the Government. The Contractor shall be responsible for the maintenance, custody, control, movement, disposal, and storage of all GFE. The Contractor shall maintain the equipment in the same functional and physical state as received except for normal wear and tear.

The Contractor shall also be responsible for the transportation of one mobile and one permanent GFE system from a Government location to the Contractor’s facility and back to the Government location upon completion of the contract or per Government direction.

(DI-MGMT-80441C) Government Property Inventory Report Operations Security (OPSEC) The Contractor’s employees and all subcontractors’ employees shall complete all OPSEC training specified in the following paragraphs, as required, in the performance of tasks bounded by OPSEC requirements. The Contractor shall attach certifications of completion to the Contractor status reports. The Contractor shall identify and include in the Contractor’s status report a list of required personnel and their required training for review and approval by the Government.

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

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

Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC) The Contractor and all associated subcontractors’ employees shall provide all information required for background checks to meet installation access requirements accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. The Contractor workforce shall comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD Headquarters, Department of the Army (HQDA), Department of the Navy 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.

Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Government will issue a CAC to Contractor employees only if duties involve one of the following:

At the discretion of the sponsoring activity and based on a favorable review of the Federal Bureau of Investigation (FBI) fingerprint check and a successfully scheduled NACI at the Office of Personnel Management, the Government will issue a CAC.

Army Training Certification Tracking System (ATCTS) Registration for Contractor Employees Who Require Access to Government Information Systems All Contractor employees with access to a Government information system shall be registered in the ATCTS at commencement of services, and shall successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter. The Government will provide information and guidance regarding the ATCTS training requirement, if and when it is required.

OPSEC Program Not required OPSEC Training Per AR 530-1, OPSEC, new Contractor employees shall complete Level I OPSEC training within 30 calendar days of their reporting for duty. All Contractor employees shall complete annual OPSEC awareness training.