FINAL_-_CDT_VPL_SOW_Base_-_20180803.docx

SOW-2017-001

W900KK-17-R-0029

Change History

3.2.11, 3.3.3 Add IEEE reference, Add “or equivalent” to CMMI Level III, Add iWATCH as mandatory. Update OPSEC

3.2.5, 3.2.5.4 3.3.1 3.3.5.7

3.3.1.2 and 3.10.1 Update Signature LTC and new APM Add subcontract management Update new DID RVTM Add Cybersecurity requirement of draft RMF submission Add Test Plan as new CDRL

ii

Table of Contents

1.

2. SCOPE

The U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Project Manager Training Devices (PM TRADE) and Product Manager Virtual Training Systems (PdM VTS) with Marine Corps Systems Command (MCSC) Program Manager Training Systems (PM TRASYS), intends to develop a joint solution to retrofit, procure, integrate, produce, test, refresh hardware/software, and upgrade capabilities to the Common Driver Trainer (CDT) systems. Additionally, PM TRASYS intends to fully replace the existing U.S. Marine Corps (USMC) Operator Driver Simulators (ODS) in accordance with the CDT System Requirements Document (SRD), PRF-PT-685.

1.1 Introduction

The single award CDT Virtual Product Line (VPL) Indefinite Delivery/Indefinite Quantity (ID/IQ) will incorporate a product line approach such as Live Training Transformation (LT2) and Consolidated Product-line Management (CPM) Next in support of the tasks described above. This SOW defines the general tasks that PM TRADE desires to have performed under the CDT VPL IDIQ contract in support of CDT VPL. PM TRADE envisions Product Line (PL) management, development, maintenance, and evolution of the CDT VPL assets under the CDT VPL IDIQ contract. Individual delivery orders (DOs) will define the detailed requirements in each respective delivery order (DO) SOW.

The CDT VPL contract facilitates the development, evolution, and maturity of the CDT VPL programs, products, and capabilities across the Army’s/Marine Corps virtual crew/individual driver trainers’ total life cycle. The CDT VPL contract will ensure product line relevancy via a consolidated, streamlined approach that protects, leverages, and matures the CDT VPL investment. Additionally, the CDT VPL contract will continue to evolve the CDT VPL assets and products. The CDT VPL contract will provide efficient, effective, and agile processes to accomplish development, production, fielding, Continuous Technology Refresh (CTR), obsolescence management, concurrency, upgrades, technology insertion, and disposal of legacy, obsolete hardware as needed. The contractor will ensure the following:

a. Elimination of duplication across development and sustainment efforts

b. Achieve a high degree of systematic reuse

c. Consolidation and reuse of shared assets across the product line

d. Use of a consistent set of tools and processes across the product line

e. Reduction in time to fielding

f. Increase of technology agility

1.2 Goal and Objectives

The objective of the CDT VPL IDIQ is to utilize the LT2 Governance to eliminate stove-piped development, obsolescence planning, improve system performance, improve operational readiness, and improve system maintenance while reducing total ownership costs. It is the objective of the contract to develop a hardware and software Product Line (PL) ensuring standardization, commonality, synchronization, maximum reuse, core asset reuse, and interoperability within the CDT systems, current/future LT2 PL assets and systems. The PL support will include dynamic mechanisms for multi-phase configuration management, PL development, PL support, technology insertion, and growth.

The CDT VPL contract should support the business goals of PdM VTS and are as follows:

a. Configuration Management

b. Product Line Tools & Methodologies Management

c. Engineering & Management Dashboards and Metrics

d. Reduce Development Cost & Complexity

e. Align & Support Product Development (common standards and interfaces)

f. Maximum Reuse Government Products (OneSAF and SE Core)

g. Reduce Development Costs

h. Leverage LT2 and CPM Next Processes & Procedures

i. CDT VPL Core Asset Development

1.3 Background

The U.S. Army PEO STRI and PdM VTS has a requirement for driver training simulators to support the Training and Doctrine Command (TRADOC) schools with institutional drivers training and to support operational units with sustainment drivers training. The CDT product line is the Army’s preferred solution for initial and sustainment driver trainer needs. This product line encompasses driver training simulators for military wheeled, tracked and specialty vehicles, to include both tactical / non-tactical vehicles with all utilizing a common system platform. Each CDT system will be reconfigurable to accommodate the different vehicle variants as defined in the product system specifications.

The systems will include the following variants:

a. Tank Variant (TV)

b. Tank Engineering Variant (TEV)

c. Tactical Wheeled Variant (TWV)

d. U. S. Army and USMC Mine Resistance Ambush Protected (MRAP) Variant (MV)

e. Stryker Variant (SV)

f. Joint Light Tactical Vehicle (JLTV)

g. High Mobility Multipurpose Wheeled Vehicle (HMMWV)

h. Medium Tactical Vehicle Replacement (MTVR)

i. Logistics Vehicle System Replacement (LVSR) (i.e. MKR18, AMKR18, MKR16 and AMKR16)

j. Capable of incorporating future vehicle variants training systems

The CDT and the USMC ODS are both virtual driver training simulators that leverage technology to fill a need for wheeled, tracked, and specialty vehicle driver training. The Government designed the CDT to meet specific training needs of institution and Major Army Commands (MACOM). The ODS is used to complement, licensing for tactical wheeled vehicles, entry and sustainment-level driver training. Both training systems provide initial familiarization training, skills progression, and sustainment for wheeled and tracked vehicles. The systems provide capabilities that allow students to become familiar with a realistic arrangement, operation of the vehicle, starting procedures, stopping procedures, instrument monitoring, instrument familiarization with procedures employed while driving under various terrain, environmental, visibility, and vehicle dynamics simulations.

Through the selection of scenarios, both systems train the physical and mental skills required to safely operate tactical vehicles. The systems permit the instructor to observe student driver performance, reactions to artificially induced malfunctions and emergency conditions through skills progression.

The CDT allows for training in all identified driving tasks as required for each variant, including individual and collective tasks up through platoon level. The CDT variants will provide the capability to train trainees to operate major appended subsystems. Appended subsystems will include, customer directed major system add-ons (e.g. plows, commander’s station, gunner’s station) based on the variant critical training requirements. The CDT variants will enable repetitively trained critical driver and crew tasks in simulated environments.

The CDT common components include the six degree-of-freedom (DOF) motion platform, Instructor Operator Station (IOS), After Action Review (AAR), visual system, and host system. The current ODS training system includes the CDT components plus three DOF facility based and three DOF trailer based platforms.

The U. S. Army has procured 53 CDT systems (13 in the Mobile Training Facility (MTF) configuration), all with various motion base stations, and 69 specific variant cabs. This includes a SV cab, MV cab, TV cab, TEV cab, and TWV cab under current development. The current driver training simulators for CDT allocate to vehicle configurations as follows:

1) SV consisting of a SV cab, ten software configurable instances with unique dynamics (each with slat armor option additionally) simulating equipment or components of the following:

a. Infantry Carrier Vehicle (ICV)

b. Mobile Gun System (MGS)

c. Reconnaissance Vehicle (RV)

d. Mortar Carrier (MC)

e. Commander Vehicle (CV)

f. Fire Support Vehicle (FSV)

g. Medical Evacuation Vehicle (MEV)

h. Anti-Tank Guided Missile Vehicle (ATGMV)

i. Nuclear, Biological and Chemical (NBC) Reconnaissance Vehicle (NBCRV)

j. Engineer Squad Vehicle (ESV) (Plow or Roller)

2) MV vehicle variants consisting of an MV cab, five hardware (dash kit) and software configurable instances with unique dynamics simulating equipment or components of the following:

a. RG 33L

b. RG 31

c. Caiman

d. MaxxPro with and without Independent Suspension System (ISS)

e. MRAP All-Terrain Vehicle (M-ATV)

3) TV vehicle variants consisting of a M1A2 SEPv2 cab baseline, three hardware (dash kit), and software configurable instances with unique dynamics simulating equipment or components (panels) of the following:

a. M1A1 (with plow or roller) (each effects dynamics)

b. M1A2 SEPv2 (with plow or roller) (each effects dynamics)

c. AutoFlug Variant (AV) cab hardware only used standalone for egress with modular AutoFlug or regular driver seat

4) TEV vehicle variants consisting of a M1A2 SEPv2 cab baseline with M1A1 panels, two hardware and software configurable instances with unique dynamics simulating equipment or components of the following:

a. Joint Assault Bridge (JAB) (adding or removing bridge effects dynamics)

b. Assault Breacher Vehicle (ABV) (adding or removing plow effects dynamics)

5) TWV vehicle variants consisting of a TWV cab, variant specific interchangeable dashes with other equipment, or components simulating the following:

a. M1083A1, 5-Ton Truck with M1095 Light Tactical Vehicle Trailer (LTVT)

b. M915 A3 Line Haul Truck with M872A4 Flatbed Trailer

c. M915 A5 Line Haul Truck with M872A4 Flatbed Trailer

d. M1120A4 Truck with M1077A1 Palletized Load System (PLS) Flatrack and M1076 Palletized Load System Trailer (PLST)

e. HMMWV

f. BUFFALO

g. MRAP

h. MATV

i. HIMARS Each CDT system configuration contains modules, consoles or workstations to facilitate training in a network system as identified below:

a. Instructor Operator Station (IOS)

b. After Action Review (AAR) Station

c. Scenario Generation System (SGS)

d. Semi-Automated Forces (SAF)

e. Joint Capabilities Release Logistics (JCR Log) Interface (TWV Only)

f. Local Area Network (LAN)

g. Drivers Vision Enhancer (DVE)

h. SV associated items

i. MV associated items

j. TV associated items

k. TV Rear View Sensor System (RVSS)

l. TEV associated items

m. TEV ABV Commander’s station associated items

n. TWV associated items This CDT VPL contract will be a joint effort to update, integrate, test, and produce the legacy Army’s CDTs and the USMC’s ODSs based on the current CDT Component Architecture. In addition, the CDT VPL contract will comply with the plans and processes identified in the Live Training Transformation (LT2) Governance.

To achieve specific networking training objectives, the CDT system will connect within the CDT family of platforms and interoperate with future external systems.

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.

2. APPLICABLE DOCUMENTS

2.1 Department of Defense Documents

MIL-STD-31000A

Technical Data Packages

TRADOC Regulation 350-70

DODM 5200.01 Vol. 4

DODI 5200.46

DODM 5220.22M

DODI 5230.24

Training, Army Learning Policy and Systems

Information Security Program

DOD Investigative and Adjudicative Guidance for Issuing the Common Access Card (CAC)

National Industrial Security Operating Manual (NISPOM) with Change 2

Distribution Statements on Technical Documents with Change 2

2.2 Other Documents

AR 25-2

AR 380-5

AR 380-10

AR 380-49

Information Assurance

Department of the Army Information Security Program

Foreign Disclosure and Contact with Foreign Representatives

Industrial Security Program

DFARS) 252.234-7001

DFARS 252.234-7002

Defense Federal Acquisition Regulation Supplement

3. REQUIREMENTS

The CDT VPL contract shall provide efficient, effective, and agile processes to accomplish development/new development of CDT vehicle variants, production, fielding, Continuous Technology Refresh (CTR), obsolescence management, concurrency upgrades, technology insertion, and disposal of legacy, obsolete hardware as needed. The requirements defined herein shall form the basis for all work that shall perform as part of the DOs the Government will issue under the CDT VPL ID/IQ contract for the CDT VPL. Each DO will specifically specify the tasks performed as derived from the CDT VPL ID/IQ contract base SOW.

Concurrency Upgrades:

The contractor shall design, develop, fabricate, integrate, test, validate, deliver, and install concurrency upgrades to the existing CDT simulators to allow them to be concurrent with the tactical vehicle capabilities. The concurrency upgrades shall conform to the CDT Product Line architecture. The concurrency upgrades shall meet or exceed all requirements identified in the CDT SRD, PRF-PT-685.

Continuous Technology Refresh:

The contractor shall design, develop, fabricate, integrate, test, validate, deliver, and install technology refreshes on CDT systems. The contractor shall perform the analysis to determine which components will require refreshed, refurbished, redesigned, and/or replaced. The contractor shall design a solution that reduces the hardware footprint, or total number of computers and the physical space they require. Technology Refresh shall conform to the CDT Product Line architecture with the goal of establishing a single CDT SW and HW baseline. Technology refresh shall conform to all Cybersecurity requirements. Technology Refresh shall utilize current version of the Government-owned software (e.g. OneSAF and SE Core) and any applicable legacy SW and/or HW designs in which the contractor chooses to implement, but not required, to meet or exceed all requirements identified in the CDT SRD, PRF-PT-685. For example, Technology Refresh shall address, but is not limited to:

a. CDT Software

b. CDT Computing Systems

c. CDT Visual Display and Image Generation

d. Network Infrastructure and Data Storage

e. Motion Base System

f. Dashboard Kits

g. Vehicle Cabs/Configurations

h. Audio/Sound System

The Government will provide copies of drawings (if/when available), Operator and Maintenance manuals (if/when available), and current Equipment Inventory Records (if/when available) included in the Technical Data Package.

New CDT Vehicle Variants:

The contractor shall design, fabricate, integrate, test, validate, deliver, and install new CDT vehicle variants. The new CDT vehicle variants shall replicate the tactical vehicle counterpart. New CDT vehicle variants shall consist of one or more of the following: complete new CDT system, new CDT cab, or dashboard kits. The new CDT vehicle variants shall conform to the CDT Product Line architecture. The new CDT vehicle variants shall meet or exceed all requirements identified in the CDT SRD, PRF-PT-685

As specified in each DO, the Government will identify the Technology Refresh, Concurrency Upgrades, and/or New CDT Vehicle Variants requirement(s).

3.1 Product Line (PL) Management and Processes

The contractor shall establish innovative, total system/subsystem life cycle management processes, which maintain or improve system’s performance, operational readiness, ensure relevancy, increase realism, and improve system maintenance while reducing total ownership costs and logistics footprint. CDT VPL will allow for development, production, fielding, technology insertion, upgrades, obsolescence management, and evolution/improvement of currently fielded systems for Product Managers operating within the CDT VPL life cycle support framework. CDT VPL shall leverage to the maximum extent possible the LT2 Governance core processes, ensuring end-to-end systematic reuse, governance, integration, alignment, synchronization, and configuration management with the PM TRADE LT2 PL and consolidated PL management strategy. If the developer is remote from the LT2 IDE, the contractors shall access all tools using a web browser within the IDE network or via the IDE web Virtual Private Network (VPN) external to the IDE network.

In support of the CDT VPL, the contractor shall perform the programmatic activities and optimize PL organizational structure aligning with the LT2 PL. The contractor’s approach shall ensure efficient PL processes for management and oversight of the PL technical activities, to include resources utilized across all CDT VPL DOs. The contractor shall ensure that everyone associated with this project have access to information required to properly perform his or her duties:

3.1.1 PL Configuration Management

The contractor shall implement a multi-dimensional PL Configuration Management Plan which executes PL Configuration Management and Software (SW) Version control across all CDT Core Assets and CDT Variants.

DI-SESS-80639D Engineering Change Proposal (ECP)

DI-SESS-80640D Request for Variance

The contractor shall perform tasks and activities necessary to continue the development, evolution, and sustainment of the CDT PL Core Assets. The Government will identify specific requirements in each DO.

3.1.3 Product Development, Integration, Testing, and Fielding The contractor shall perform the necessary product development integration, prototype production, testing, fielding, and sustainment tasks and activities. The Government will address the specific requirements in each DO. The following table, at a minimum, shall provide a representative list of tasks and activities that require by specific DOs:

3.1.4 CDT VPL LT2 Product-line Synchronization

The contractor shall develop and manage a software, hardware PL for all of the programs utilizing the CDT VPL contract. The contractor shall work with the Government and other stakeholders to update the CDT VPL governance policies and documentation to account for the development of the hardware PL. The contractor shall insure that PM TRADE leverages the LT2 Product Line existing Product line management & engineering processes to the maximum extent possible.

The contractor shall follow LT2 Configuration Management (CM) processes in accordance with the LT2 Product Line Configuration Management Operational Procedures Guide and the LT2 Operations Guide and LT2 Interface Control Documents (ICD). The contractor shall synchronize, populate, and maintain description data and other pertinent information for the CDT VPL systems and common components within the construct of the LT2 tools and processes. The contractor shall identify, describe, and track all of the work products, components, and systems’ baselines produced or utilized under this contract.

3.1.5 Support within CDT VPL

The contractor shall actively support, as required, the development and refinement of the systems and components fielded. The contractor shall support the system/product-line by implementing appropriate processes to support the CDT VPL. The contractor shall monitor direct components within the scope of CDT VPL systems and secondary (affiliated) components as well as maintain their component agreements/specifications. This support shall range between collection and adjudication of problems and issues, and providing assistance in verifying and/or installing hardware or software changes as issued via the CDT VPL repository.

3.1.6 System Problem Reporting

The contractor shall report any suspected design and/or capability inadequacies, as well as any performance anomalies that might indicate a systemic flaw/fault or require hardware PL or software PL re-baselining. The contractor shall include the nature of the suspected flaw, the time, and conditions surrounding the occurrence, and affected systems/locations. These reports shall be implemented, e.g. tools within the framework and processes utilized to support the CDT VPL.

3.1.7 Computer Hardware, Enterprise Software Solutions (CHESS) Program The contractor shall utilize the Army’s CHESS program. Under PEO Enterprise Information Systems (EIS), CHESS is the mandatory source for commercial Information Technology (IT) purchases. CHESS contracts provide IT products and services that comply with Network Enterprise Technology Command (NETCOM), Army and DOD policy and standards. Purchasers of commercial hardware and software shall satisfy their IT requirements by utilizing CHESS contracts and DOD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts shall require a waiver. A completed list of the on-line waiver process for CHESS contracts is located at https://chess.army.mil.

3.2 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 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

3.2.1 Earn Value Management System (EVMS)

N/A.

3.2.2 Integrated Master Schedule (IMS)

The contractor shall develop, implement, manage and update the contract Integrated Master Schedule (IMS). All program and technical reviews shall present the IMS which shall contain all exit criteria, accomplishments, critical events, predecessors events, successors events, and their dependencies. The IMS shall address and identify total program activities including activities performed by major subcontractors. Accomplished IMS activities and event times shall reflect any updated changes. 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)

3.2.3 Financial Management

The contractor shall plan, budget, schedule, and control resources allocated to meet the requirements of the contract. The contractor shall document and track status of all appropriated funds associated with the contract to include payments, cancellations, and invoices against each contract line/sub line item. The contractor shall document and track the status of all work directives issued and remaining balances.

DI-MGMT-81651 Contract Invoicing and Payment Report

3.2.4 Risk Management

The contractor shall prepare, implement, and maintain a cost, technical and schedule risk management process. This shall include risk detection and identification, assignment of risk categories, action triggers, and corrective action, tracking of compliance, reporting of status and planning for risk abatement. The contractor shall:

1. Identify and document moderate and high-risk items for each risk assessment area

1. Identify, implement risk handling approaches, and track over time each moderate and high-risk item

1. Document risk issues that have been successfully resolved and schedule each open item into the program IMS

1. Develop mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified

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

3.2.5.1 Post Award Conference (PAC) / Start of Work Meeting

As specified for each DO, the contractor shall conduct a combined PAC/Start of Work Meeting held at the contractor’s facility, at 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, Integrated Product Team (IPT) structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the CDT mission. The contractor shall document action items, due dates and coordinate resolution and track action items until closure. Action item closure shall require contractor and Government approval.

DI-ADMIN-81505 Report, Record of Meeting/Minutes

3.2.5.2 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 calendar 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 design status

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. Action item closure shall require contractor and Government approval.

DI-ADMIN-81505 Report, Record of Meeting/Minutes

3.2.5.3 Integrated Product and Process Management (IPPM)

The contractor shall establish and maintain a management process in conjunction with the LT2 Operations Guide and structure that integrates all design and production activities to optimize design, manufacturing, and supportability processes. The contractor shall utilize systems engineering tools and overlay a management concept that encourages the use of IPTs. The contractor’s IPPM shall interact with Government Contracting Officer Representative (COR) in its role as a customer. The contractor’s IPPM shall establish performance requirements, monitor and manage total program progress, and evaluate product quality.

The contractor shall establish an IPT structure to address major areas of system development (e.g., systems engineering, hardware design, software design, integrated logistics support testing). The contractor shall establish IPT charters and host regularly schedule IPT meetings or teleconferences. Management reviews shall use IPT meetings/teleconferences to address systems development status of activities, questions, and issues in a timely manner. The contractor shall document action items, due dates and coordinate resolution and track action items until closure. Action item closure shall require contractor and Government approval.

DI-ADMIN-81505 Report, Record of Meeting/Minutes

3.2.5.4 Subcontractor Management

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

3.2.6 Government Purpose Rights (GPR)

The contractor shall provide the Government no less than Government Purpose Rights in any software or technical data developed under this contract with Government. The Government will retain Government Purpose Rights for the life of this contract. Upon expiration of the contract, the Government will have unlimited rights in any applicable technical data. The Government shall procure sufficient rights with the addition of new software or hardware proposed for the CDT. The Government shall procure rights such that the Government can maintain / modify the system using Government personnel and third party contractors.

3.2.7 Government Furnished Information (GFI)

The Government will provide agreed upon 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 does not provide the technical data. The contractor shall be responsible to secure, protect, and maintain the data provided as GFI.

3.2.8 Transition Period

If the contractor is an unsuccessful offeror in any subsequent Government solicitation for these services or the contract terminates for any reason, the contractor shall provide support to the Government and the successor contractor ensuring an orderly transition to minimize impact on operational readiness. The contractor shall assist both the Government and successor contractor with GFI and Government Furnished Property (GFP) inventories, transition, requests for information and personnel management. The contractor shall provide the successor contractor access to the site and to all technical documentation and publications on a not-to-interfere basis during the transition phase-out period. The contractor shall permit the successor contractor to observe the contractor performing the support services and equipment operations on a not-to-interfere basis during the transition phase-out period. The contractor shall retain full responsibility for all services and equipment in accordance with the SOW until completion of the phase-out period. Transitional support provided to the Government shall not exceed a three month period.

3.2.9 Government Furnished Property (GFP)

Upon contract award, the contractor shall inventory all GFP and subsequently, maintain records of all GFP. 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 GFP. The contractor shall maintain the equipment in the same functional and physical state as received except for normal wear and tear.

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

3.2.11 Operational Security (OPSEC) / Antiterrorism Training (AT) The contractor’s employees and all subcontractor’s employees shall complete all Operations Security (OPSEC) training, 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.

All contractor employees, to include Subcontractor employees, requiring access Army and Marine Corps installations, facilities and controlled access areas shall complete AT Level I awareness training in accordance with AR381-12 within thirty (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 thirty (30) calendar days after completion of training by all employees and Subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil.

3.2.11.1 iWATCH Training The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This local developed training will 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 thirty (30) calendar days of new employees commencing performance with the results reported to the COR no later than sixty (60) calendar days after contract award.

3.2.11.2 Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC) The contractor and all associated sub-contractors 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:

a. Both physical access to a DOD facility and access, via logon, to DOD networks on-site or remotely

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.

The Government will address the specific RAPIDGate requirements in each DO if requires. The contractor shall obtain and maintain the base and installation access for employees; this includes RAPIDGate access if required by site. The RAPIDGate Program performs background checks and authenticates participants’ identities. Upon passing the background check, each participant receives a personalized RAPIDGate Credential. The participant presents the RAPIDGate Credential at installation perimeter gates to receive authorization to enter. Company enrollment and employee registration are renewable yearly.

3.2.11.3 AT Awareness Training for US Based Contractor Personnel Traveling Overseas All US based contractor employees and associated subcontractor employees shall take Government provided Area of Responsibility specific AT awareness training as directed by AR 525-13. The combatant commander with the unit AT Office being the local point of contact directs specific Area of Responsibility training content.

3.2.11.4 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 is required.

3.2.11.5 OPSEC Program

The contractor shall comply with the OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

3.2.11.6 Requirements for OPSEC Training

Per AR 530-1, Operations Security (OPSEC), new contractor employees shall complete Level I OPSEC training within thirty calendar days of their reporting for duty. All contractor employees shall complete annual OPSEC awareness training. The contractor shall ensure all applicable employees have completed OPSEC initial training and annual refresher training and shall certify that their work force has completed the training through the submission of completion certificates(s) to the COR within 30 days of arrival on the installation. OPSEC training for certification is located at the Defense Security Services website: http://cdsetrain.dtic.mil/opsec/idex.htm.

3.2.11.7 Cybersecurity (CS)/Information Technology (IT) Training All contractor employees and associated subcontractor employees shall complete the DOD CS awareness training before issuance of network access and annually thereafter. All contractor employees working CS/IT functions shall comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 within 30 days of contract award or employment. CS/IT training for certification is located at https://ia.signal.army.mil/dodiaa/default.asp.

3.2.11.8 CS/IT Certification

Per DOD 8570.01-M , Defense Federal Acquisition Regulation Supplement (DFARS) 252.239.7001 and AR 25-2, the contractor employees supporting CS/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DOD 8570.01-M shall be completed upon contract award.

3.2.11.9 Performance or Delivery in a Foreign Country

The contractor shall comply with DFARS clause 252.225-7043, Antiterrorism/Force Protection for Defense contractors Outside the US. Non-local national contractor personnel shall comply with theater clearance requirements.

3.2.11.10 Threat Awareness Reporting Program (TARP)

For all contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees shall receive annual TARP training by a counterintelligence agent or other trainer as specified in 2-4b.

3.3 Systems Engineering

The contractor shall assist the Government in translating requirements and objectives, interface and other design constraints including cost, into preliminary, verifiable, functional requirements and objectives, while conducting cost-benefit trades to support refinement of the preliminary functional requirements. The contractor shall develop and manage the CDT design (balanced with respect to performance, cost, schedule, and risk) and verify it meets the systems requirements, PRF-PT-685. The contractor shall assess proposed changes in the evolving functional architecture, physical hierarchy, and baselines and objectively trade alternatives to balance performance, cost, schedule, and risk prior to approval. The proposed solution will work within the existing footprint, power and Heating, Ventilation, and Air Conditioning (HVAC) building requirements. As part of the system design and component selection process requirement, CS shall consider all systems used to enter process, store, display, or transmit information. The contractor shall provide all tools, SW, and equipment necessarily to perform their duties.

The contractor shall develop and deliver the contractor’s Systems Engineering Management Plan (SEMP). The SEMP shall describe the contractor’s proposed efforts for planning, controlling, and conducting a fully integrated engineering effort. The purpose of the SEMP is to understand and evaluate the contractors’ engineering processes and procedures as part of the CDT VPL contract. The SEMP shall coincide with the Government’s Systems Engineering Plan (SEP).

The contractor shall use the SRDs associated with the CDT as the basis for development of all implementing specifications. The design concept shall establish one common software design baseline, one common hardware design baseline, and an open systems architecture, with system interfaces, products, practices, and tools, to support all vehicle variants development. The design concept shall base the engineering specifications and standards adopted by industry standards bodies or de facto standards (set by the market place). Performance, cost, industry acceptance, long term availability, supportability, and upgrade potential shall assist in determining selected designs and specifications. The Government’s intent is to maximize the CDT product-line and reuse the existing architecture (to include software and hardware design and implementation) to preserve and improve training capabilities.

3.3.1.1 System Definition Phase

The contractor shall define, document, manage, and apply a requirements definition process IAW IEEE Std 12207-2008, section 6.4.1 for all requirements and derived requirements from PRF-PT-685. The Requirements Definition phase shall require the creation of or update to the Requirements Traceability Verification Matrix (RTVM). The RTVM shall be a direct input to the System/Subsystem Specification. The RTVM shall capture requirements from traceability, analysis, validation, functional analysis, functional verification, synthesis and includes the capture of all elements resulting from test and evaluation efforts. The RTVM shall include the verification criteria for each requirement for testing purposes. The RTVM shall provide backwards and forward traceability, (i.e. the RTVM shall document each requirement from its source through definition, analysis, design, testing, and acceptance). The contractor shall institute a configuration review process with the Government for requirements review, approval, and control process to assist in the RTVM data entry decisions.

The contractor shall establish the definition of the system with a focus on system products required to satisfy performance requirements PRF-PT-685. The contractor shall complete the system, product, and subsystem interface requirements and verification definition, system and product requirements and verification definition, and preliminary subsystem requirement and verification definition; establish a system baseline; and complete technical reviews.