FINAL_-_CDT_VPL_SOW_DO_X_TWV_Phase_2_-_20180914.docx

Statement of Work For the Common Driver Trainer (CDT) Virtual Product Line (VPL) for Delivery Order X – Tactical Wheeled Variant (TWV) Phase 2 Version 2.0

Prepared by U.S. Army PEO Simulation, Training, and Instrumentation (PEO STRI)

And

Marine Corps Systems Command, Program Manager Training Systems

14 SEPTEMBER 2018

12211 Science Drive Orlando, Florida 32826-3276

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors only, due to vulnerability information, effective 30 August 2018. Other request for this document shall be referred to U.S. Army PEO STRI, ATTN: SFAE-STRI-TRADE-VTS.

Engineering

Acquisition Logistics

Program Management

SOW-2017-067

W900KK-18-R-0037

Change History

Initial Release

Table of Contents

1.

v

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 procure, integrate, test, and upgrade capabilities to the Common Driver Trainer (CDT) Tactical Wheeled Variant (TWV) Phase 1 to produce Phase 2 systems in accordance with the CDT System Requirements Document (SRD), PRF-PT-685 with emphasis on the SRD for the CDT Virtual Product Line (VPL) System, Appendix D – Tactical Wheeled Variant (TWV) – Phase 2.

Introduction This Delivery Order (DO) will procure, integrate, produce, test, and upgrade new TWV capabilities to the CDT TWV systems.

The DO will incorporate the product line approach such as Live Training Transformation (LT2) and CPM Next. This SOW defines the specific tasks that PM TRASYS desires to have performed under the CDT TWV in support of CDT Virtual Product Line (VPL) for Phase 2. PM TRADE envisions Product Line (PL) management, integration, maintenance, and evolution of the CDT VPL assets under the CDT VPL IDIQ contract.

Goal and Objectives The objective of this DO is to start the CDT PL IDIQ and 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 procure a hardware and software Product Line (PL) ensuring standardization, commonality, synchronization, maximum reuse, core asset reuse, and interoperability within the CDT systems, and current/future LT2 PL assets and systems. The PL support must include dynamic mechanisms for multi-phase configuration management, PL integration, PL support, technology insertion and growth.

The goal of this DO is:

a. Configuration Management

b. Align & Support Product Integration (common standards and interfaces)

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

d. Reduce Costs

e. Leverage LT2 and CPM Next Processes & Procedures

f. CDT VPL Core Asset Integration BackGround The Marine Corps has a requirement for providing a high fidelity, realistic, and representative modeling of the operations associated with most tactical wheeled vehicles and their trailer components. The simulator shall be capable of providing effective training of tactical driver skills, prior to driving/operating actual vehicles. 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 shall be reconfigurable to accommodate the different vehicle variants as defined in the Common SRD with Appendices A-G, PRF-PT-685.

The CDT is a virtual driver training simulator that leverages technology to fill a need for wheeled, tracked and specialty vehicle driver training. The CDT TWV training system provides initial familiarization training, skills progression, and sustainment for tracked vehicles. The system provides capabilities that allow operators to become familiar with a realistic arrangement and operation of the vehicle, including starting and stopping procedures, monitoring instruments and familiarization with procedures employed while driving under various terrain, environmental, visibility and vehicle dynamics simulations. The CDT TWV shall replicate situations which cannot and should not be replicated in actual vehicles due to the high level of risk associated with emergency procedures and scenarios for training. Therefore, the CDT TWV shall also provide risk management and mitigation when exposing operators to possible unsafe and/or unreplicable situations.

The CDT TWV allows for training in all identified driving tasks as required for each variant, including individual and collective tasks. The CDT TWV variant will enable repetitively trained critical driver and crew tasks in simulated environments.

The CDT common components include the motion platform, Instructor Operator Station (IOS), After Action Review (AAR), visual system, and host system.

CDT TWV shall replicate the below USMC variants to include a standard configuration (i.e.dash) for each primary platform vehicle variant and variant specific software to replicate each vehicle variants specific characteristics of the listed vehicles for all vehicle variants types.

a. High Mobility Multipurpose Wheeled Vehicle (HMMWV) (new requirement to CDT)

· M1113

· M1114

· M1151

· M1151A1

· M1152

· M1152A1

· M1165

· M1165A1

· M1167

· M997A3 utility trucks

b. Medium Tactical Vehicle Replacement (MTVR) (new requirement to CDT)

· AMK/MK23 and AMK/MK25

· AMK/MK27 AND AMK/MK28

· AMK/MK29

· AMK/MK30

· AMK/MK31 7 Ton trucks

c. MK 23 MTVR w/MAS (Marine Armor System) (new requirement to CDT)

d. MRAP CAT III Buffalo (new requirement to CDT)

e. Joint Light Tactical Vehicle (JLTV) (new requirement to CDT)

f. Mine Resistant Ambush Protected (MRAP) (new requirement to CDT)

· 4x4 and 6x6 with Independent Suspension Systems (ISS)

g. MRAP All Terrain Vehicle (M-ATV) (new requirement to CDT)

· CAT I A1

· CAT I A1 ISS

· CAT II A1

· CAT II A1 ISS

· CAT I A2

· CAT I A2 ISS

· CAT II A2

· CAT II A2 ISS

· M1240

· M1240A1

· M1245

h. Logistics Vehicle System Replacement (LVSR) (new requirement to CDT)

· MKR18 ID 11313A

· AMKR18 ID 12481A

· MKR16 ID 11316A

· AMKR16 ID 12493A

i. Utility Task Vehicle (UTV) (Polaris RZR 04 Diesel) (new requirement to CDT)

j. Family of Tactical Trailers (new requirement to CDT)

· Light Tactical M 1101/M1102 Trailer

· Light Tactical

· M353 Trailer General Purpose

· MIOS

· Trailer Cargo 1 Ton

· MKS93 6 Ton 4 Wheel Cargo Trailer

· M149A2 Water Tank Trailer

· Engineer Equipment Trailer (EET)

· M777 Howitzer

· MK/AMK970

· Aircraft Refueler

· Palletized Load System Trailer (PLST) Each CDT system configuration contains the following capabilities for the modules, consoles or workstations to facilitate training in a network system as identified below:

1. Instructor Operator Station (IOS) After Action Review (AAR) Station Scenario Generation System (SGS) Semi-Automated Forces (SAF) Local Area Network (LAN) Drivers Vision Enhancer (DVE) TWV associated items TWV Assistant Driver’s Station associated items This DO will procure, integrate, test, and upgrade capabilities to CDT TWV systems based on the current CDT Common Architecture and leverage the Live Training Transformation (LT2) Construct as required.

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

Department of Defense Documents

MIL-PRF-32216

NAVMC

Evaluation of Commercial Off-the-Shelf (COTS) Manuals and Preparation of Supplemental Data

Systems Approach to Training

DODM 5200.01 Vol. 4

DODI 5200.46

DODM 5220.22M

DODI 5230.24

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

DODI 8500.01

Cybersecurity (CS)

DODI 8510.01

DOD 8570.01-M

DODI 8582.01

Risk Management Framework for DOD Information Technology

Information Assurance Workforce Improvement Program

Security of Unclassified DOD Information on Non-DOD Info Systems

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

IEEE Std 12207-2008

NSTISSP No. 11 IEEE Standard Systems and software engineering -- Software life cycle processes

National Security Telecommunications and Information System Security Policy – National Information Assurance Acquisition Policy

4. REQUIREMENTS

The tasks described in this SOW intend to address the approach toward CDT PL within LT2 Construct. In addition, the contractor shall procure new CDT vehicle variants, integrate, test, refresh hardware/software, and concurrency upgrade capabilities to CDT TWV systems. CDT TWV variants include the following vehicles and equipment:

a. High Mobility Multipurpose Wheeled Vehicle (HMMWV) (new requirement to CDT)

· M1113

· M1114

· M1151

· M1151A1

· M1152

· M1152A1

· M1165

· M1165A1

· M1167

· M997A3 utility trucks

b. Medium Tactical Vehicle Replacement (MTVR) (new requirement to CDT)

· AMK/MK23 and AMK/MK25

· AMK/MK27 AND AMK/MK28

· AMK/MK29

· AMK/MK30

· AMK/MK31 7 Ton trucks

c. MK 23 MTVR w/MAS (Marine Armor System) (new requirement to CDT)

d. MRAP CAT III Buffalo (new requirement to CDT)

e. Joint Light Tactical Vehicle (JLTV) (new requirement to CDT)

f. Mine Resistant Ambush Protected (MRAP) (new requirement to CDT)

· 4x4 and 6x6 with Independent Suspension Systems (ISS)

g. MRAP All Terrain Vehicle (M-ATV) (new requirement to CDT)

· CAT I A1

· CAT I A1 ISS

· CAT II A1

· CAT II A1 ISS

· CAT I A2

· CAT I A2 ISS

· CAT II A2

· CAT II A2 ISS

· M1240

· M1240A1

· M1245

h. Logistics Vehicle System Replacement (LVSR) (new requirement to CDT)

· MKR18 ID 11313A

· AMKR18 ID 12481A

· MKR16 ID 11316A

· AMKR16 ID 12493A

i. Utility Task Vehicle (UTV) (Polaris RZR 04 Diesel) (new requirement to CDT)

j. Family of Tactical Trailers (new requirement to CDT)

· Light Tactical M 1101/M1102 Trailer

· Light Tactical

· M353 Trailer General Purpose

· MIOS

· Trailer Cargo 1 Ton

· MKS93 6 Ton 4 Wheel Cargo Trailer

· M149A2 Water Tank Trailer

· Engineer Equipment Trailer (EET)

· M777 Howitzer

· MK/AMK970

· Aircraft Refueler

· Palletized Load System Trailer (PLST)

The USMC CDT TWV variants shall meet or exceed all requirements identified in the CDT SRD, PRF-PT-685.

Product Line (PL) Management and Processes The Contractor’s approach shall comply with the CDT VPL Base Statement of Work.

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 continue to transfer the CDT VPL IDE to the LT2 IDE. 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.

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

DI-SESS-81022D Configuration Audit Summary Report and Certification PL Core Assets Development and Evolution The contractor shall perform tasks and activities necessary to continue the evolution, and sustainment of the CDT PL Core Assets.

Product Development, Integration, Testing, and Fielding The contractor shall perform the necessary tasks and activities for product integration, prototype production, testing, fielding, and sustainment. The following table, at a minimum, shall provide a representative list of tasks and activities that are required for this DO:

CDT VPL LT2 Product-line Synchronization The contractor shall integrate 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 integration 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.

Support within CDT VPL The contractor shall actively support, as required, the integration 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.

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 IDE PL.

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.

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. Integration and fabrication progress

e. Expenditures to date and cost projections

DI-MGMT-80227 Contractor's Progress, Status, and Management Report Earn Value Management System (EVMS) N/A.

Integrated Master Schedule (IMS) The contractor shall integrate, 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) 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, at a minimum, 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 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. Integrate mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified.

Management Reviews and Subcontractor Management The contractor shall conduct Management Reviews (MR) 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 MRs 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.

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 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 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 at a minimum:

0. Hardware and software design status

0. Risk and problem identification

0. Subcontract management/progress

0. Data collection and modeling

0. Logistics planning

0. Test planning

0. Provisioning for training and technical publications status

0. Schedule status

0. Pre-selected topics of interest

0. Cybersecurity status and progress

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 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 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 integration. The contractor shall establish IPT charters and host regularly schedule IPT meetings or teleconferences. Management reviews shall use IPT meetings/teleconferences to address systems 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 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.

Intellectual Property Rights / Technical Data Rights The contractor shall provide the Government intellectual property rights and technical data rights identified in solicitation provision DFARS Subpart 252.227-7017 in any software and/or technical data developed under this contract with the Government. The Government will retain those rights for the life of this contract. The Government shall procure sufficient rights with the addition of new software and/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.

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

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.

Government Furnished Property (GFP) The CDT TWV USMC does not have any GFP.

Visitor Support N/A.

Operational Security (OPSEC) / Antiterrorism Training (AT) The contractor’s employees and all subcontractor’s employees shall complete all OPSEC training, as required, in the performance of tasks bounded by OPSEC requirements. The contractor shall attach certifications of completion to the contractor’s status report. 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 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.The contractor shall comply with all Operational Security, Cyber Security, Security Control Assessments and Base Access, procedures for performance or delivery in a foreign country, and all other security requirements IAW the CDT VPL SOW Base. If applicable, the contractor shall comply with all access and general protection policies and procedures for contractor requiring Common Access Card (CAC) IAW the CDT VPL SOW Base.

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

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) 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:

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

3. Remote access, via logon, to a DOD network using DOD-approved remote access procedures or

3. For a period of six months or more, the requirement of recurring physical access to multiple DOD or federally controlled non-DOD facilities on behalf of the DOD.

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.

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.

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 must be registered in the ATCTS at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the Information Systems (IS) and then annually thereafter. The Government will provide information and guidance regarding the ATCTS training requirement, if and when is required.

OPSEC Program The contractor shall comply with the Operations Security (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.

Requirements for OPSEC Training Per AR 530-1, Operations Security, 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: https://www.cdse.edu/catalog/index.html.

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 cybersecurity/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.

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 must be completed upon contract award.

Performance or Delivery in a Foreign Country N/A.

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.

Systems Engineering The contractor shall assist the Government in translating requirements and objectives, interface and cost, into preliminary, verifiable, functional requirements and objectives, while conducting cost-benefit trades to support refinement of the preliminary functional requirements. The contractor shall 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 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 integration of all implementing specifications. The procured design concept shall be from an established 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 integration.

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. The requirements and initial design documentation generated during the system definition stage shall guide subsystem integration. The Government shall conduct the System Requirements Review (SRR) at the completion of the systems definition stage for determining whether the system definition is sufficiently mature to progress to preliminary design stage. The contractor shall review system definition to ensure that:

1. The design is sufficiently mature to meet systems engineering criteria.

1. System functional requirements and system non-functional requirements (e.g., performance, design goals (e.g., Modular Open System Approach (MOSA)) are identified.

1. System-level risks adequately address to justify integration.

1. Trade-study data are adequate to substantiate that system requirements are achievable.

1. Interface requirements between human and products or subsystems identify performance, workloads, design constraints, and usability.

1. Selected CS products that are National Information Assurance Partnership (NIAP) validated or on the DOD Unified Capabilities (UC) Approved Products List (APL) (https://aplits.disa.mil/processAPList.do).

1. Decisions made in arriving at the system definition configuration support by analysis, test, and other technical data.

DI-IPSC-81431A System/Subsystem Specification (SSS)

DI-MGMT-82133 Requirement Traceability Verification Matrix, RTVM System Requirement Review (SRR) In order for the Government to authorize the contractor to proceed into the preliminary design phase, the contractor shall conduct the SRR as a product process assessment to ensure the system definition is complete. The purpose of the SRR is to ensure performance requirements, derived from overall requirements, is complete, properly identified, defined, testable, and consistent with schedule, risk, technology readiness, and other system constraints. The review shall include the presentation and discussion of information and data relating to the following:

1. System Requirements Document

1. System software functionality description

1. Preferred system solution definition

1. Hardware/software allocation

1. Human interfaces

1. Data collection

1. Test Plan

1. Present modeling and simulation (M&S) verification and validation (V&V) draft plan with focus on methodology

4.1.1.1.1 SRR Entrance Criteria:

Entry criteria for the SRR shall consist of:

a. Government review of the SRR (preliminary) presentation material indicates it is sufficient to support the SRR.

b. Documented results of the data collection and GFI/GFE tasks are complete.

c. Draft Requirements Traceability Matrix (RTM) document submitted for review.

d. M&S V&V draft plan with focus on methodology established.

4.1.1.1.2 SRR Exit Criteria:

The SRR shall be complete when:

a. Government concurrence that all required SRR topics have been satisfactorily presented, discussed, and documented

b. The system requirements, as disclosed, satisfy the requirements of PRF-PT-685

c. The system requirements detail and enable system functional definition, functional decomposition, test, and evaluation

d. The program risks are identified

e. The minutes and presentation materials have been submitted and agreed to

f. All action items have been assigned with suspense date for closure

g. Government acceptance of M&S V&V draft plan with focus on methodology

DI-ADMIN-81505 Report, Record of Meeting/Minutes Preliminary Design Phase The contractor shall ensure that the design considerations include systems functional requirements, systems non-functional requirements (e.g., performance, design goals (e.g., MOSA, and Human System Interfaces). The contractor shall ensure that functional design considerations integrate CS functional requirements and that these requirements are included throughout the integration process. The contractor shall decompose identified subsystem functions into lower-level functions and allocate functional and performance requirements to component-level functional and physical architectures. Each preliminary subsystem requirements, verification definition, and preliminary design-to baseline shall evolve into a subsystem requirement, verification definition, and design-to baseline. Preliminary component requirements, verification definition, and build-to baselines shall define the components and the subsystems. Final subsystem definition shall include identification of recommended components and interfaces; resolution of subsystem-level risks; assessment of component risks; and design for quality factors to include producibility, verifiability, usability, CS, supportability, trainability, and disposability for each subsystem. The contractor shall complete subsystem reviews for each subsystem at the completion of its preliminary design stage. The contractor shall document the results of the evaluation. Each review is to assure that:

1. The subsystem definition is sufficiently mature to meet systems engineering criteria

1. The subsystem functional requirements and non-functional requirements (e.g. performance, design goals (e.g. MOSA)) are identified in the subsystem design and are traceable to the system functional and non-functional requirements

1. Component allocations and preliminary component specifications are reasonable and provide a sound subsystem concept

1. Software architecture is described using four views:

3. Software module view

3. Software runtime view

3. Use case view

3. Software deployment view

1. Subsystem risks have been assessed and mitigated

1. Trade-study data are adequate to substantiate that subsystem requirements are achievable

1. Human system interfaces are identified and described in the subsystem design and are traceable to design requirements

1. Decisions made in arriving at the subsystem configuration definition are well supported by analysis and technical data

1. Security engineering processes are integrated into the design to achieve an integrated secure solution

1. Complete analysis of the proposed GFI/GFE/COTS/GOTS integrated solution conducted and any outstanding issues identified to the IPT for assessment.

The contractor shall present the CDT preliminary design to the Government at the Preliminary Design Review (PDR), for integration activities.

Detailed Design Phase As defined in this DO, the contractor shall complete subsystem design down to the lowest component level, and create a component requirements, verification definition, and build-to component baseline for each component. Final component definition shall include identification of recommended parts and interfaces; resolution of component-level risks and for each component, down to the lowest sub-component, the design for quality factors to include producibility, verifiability, usability, CS, supportability, trainability, and disposability. The contractor shall complete component reviews at the completion of the detailed design stage for each component with Government participation. The contractor shall integrate security engineering processes into the design to achieve an integrated secure solution. The contractor shall document the results of the evaluation.