Attachment_2-CDT_VPL_SOW_MV_-_20180914.pdf

SOW-2017-069

W900KK-18-R0037

1. 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) intends to procure, integrate, test, refresh hardware/software, and provide continuous technology refresh capabilities to Common Driver Trainer (CDT) Mine Resistant Ambush Protected (MRAP) Variant (MV) systems in accordance with the CDT System Requirements Document (SRD), PRF-PT-685.

1.1 INTRODUCTION

This Delivery Order (DO), DO X will procure, integrate, produce, test, refresh hardware/software, and provide continuous technology refresh to new MV capabilities to the CDT MV systems.

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

1.2 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 develop 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 development, PL support, technology insertion and growth.

The goal of this DO is to:

a. Configuration Management

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

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

d. Reduce Development Costs

e. Leverage LT2 and CPM Next Processes & Procedures

f. 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 CDT is a virtual driver training simulator that leverages technology to fill a need for MRAP vehicles driver training. The Government designed the CDT to meet the specific training needs of institution and Major Army Commands (MACOM). The CDT MV training system provides initial familiarization training, skills progression, and sustainment for MRAP vehicles. The system provides capabilities that allow students 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. Through the selection of scenarios, the system trains the physical and mental skills required to safely operate tactical vehicles by permitting the instructor to observe student driver performance and their reactions to artificially induced malfunctions and emergency conditions through skills progression.

The CDT MV allows for training in all identified driving tasks as required for each variant, including individual and collective tasks up through platoon level. The CDT MV variant will provide the capability to train trainees to operate major appended subsystems. Appended subsystems will include, customer directed major system add-ons (e.g. commander’s station, gunner’s station) based on the variant critical training requirements. The CDT MV will assist in the training of MRAP tactical vehicle drivers.

The main components in the specific modules are the driver compartment, swappable dash panels with instruments and controls for the driver, space and visual constraint modules (if necessary) and the software required to operate the driver compartment and interact with the common modules in the CDT. The CDT MV variant 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 will provide continuous technology refresh to CDT MV systems at CONUS and OCONUS locations. Reconfigurable versions among MRAP vehicle platforms are MRAP All-Terrain Vehicle (M-ATV), CAT I, and CAT II. The CAT II serves as the CDT MV baseline vehicle.

The MRAP CAT I vehicles which include:

a. MaxxPro,

b. TVS Caiman 6x6,

c. RG33 4x4,

d. RG31 4x4, and

e. Cougar 4x4

The MRAP CAT II vehicles which include:

a. RG33L 6x6 and

b. Cougar 6x6

The MRAP All-Terrain Vehicle:

a. M-ATV

Each CDT system configuration also 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. Local Area Network (LAN)

f. Drivers Vision Enhancer (DVE)

g. MV associated items

h. MV Assistant’s station associated items

This DO X will procure, integrate, test, refresh hardware/software, and provide concurrency/upgrade capabilities to ten CDT MV systems based on the current CDT Component Architecture and leverage the Live Training Transformation (LT2) Construct as required.

The CDT system may expect to interoperate with external systems in the future. The CDT MV systems shall connect within the CDT family of platforms to achieve the specific networking training objective.

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

2.1 DEPARTMENT OF DEFENSE DOCUMENTS

MIL-STD-130N Identification Marking of U.S. Military Property

MIL-STD-40051-

2C

Preparation of Digital Technical Information for Page- Based Technical Manuals

MIL-STD-3046 Department of Defense (DOD) Interim Standard Practice, Configuration Management

MIL-STD-31000A Technical Data Packages

MIL-PRF-29612 Training Data Product Specification

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

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

DODI 8320.04 Item Unique Identification (IUID) Standards for Tangible Personal Property

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

2.2 OTHER DOCUMENTS

PRF-PT-685 System Requirements Document (SRD) for the Common

Driver Trainer (CDT): common, appendixes A to G

SOW-2017-001 Statement of Work for the CDT VPL

CNSSI 1253F

Committee on National Security Systems Instruction

(CNSSI) 1253

NIST SP 800-53

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

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

AR 381-12 Threat Awareness and Reporting Program

AR 530-1 Operations Security

AR 525-13 Force Protection Program

FAR clause 52.204-9

Personal Identity Verification of Contractor Personnel

Army Directive 2014-05

Policy and Implementation Procedures for CAC Credentialing and Installation Access for Uncleared Contractors

AR 190-13 Army Physical Security Program

29CFR1910.1200

Occupational Safety and Health Standards Toxic and hazardous Substances

EM 385-1-1 Department of Army Manuals, US Army Corp of

Engineers Safety and Health Requirements Manual 2014 (Manual is downloadable from www.usace.army.mil/CESO/Pages/EM385-1-1.aspx).

29 CFR 1910.119

Code of Federal Regulations (CFR), 29 CFR 1910 Occupational Safety and Health Standards (OSHA standards are downloadable from http://www.osha.gov) http://www.usace.army.mil/CESO/Pages/EM385-1-1.aspx http://www.osha.gov/

FARS

Sec.252.225-

Antiterrorism/Force Protection for Defense Contractors outside the US

GEIA-HB-0007-B Logistics Product Data Handbook

GEIA-STD-0007-

B

Logistics Product Data

NFPA 70 National Fire Protection Association (NFPA 70 National

Electrical Code, 2017 Edition (Copies of this document are available from http://www.nfpa.org/Catalog/ or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322)

29 CFR 1910 Occupational Safety and Health Administration (OSHA)

Regulations OSHA 1910, Subpart S Electrical (Copies of the above regulations are available from http://www.osha.gov)

8000001-PDD-

Common Driver Trainer Product Drawings/Models and Associated Lists

LT2-

TRADE_PLAN-

2013-00009

Live Training Transformation (LT2) Product Line Configuration Management Guide (Version AC)

LT2-TRADE-PLN-

000384

Live Training Transformation (LT2) Operations Guide (Version H)

DFARS) 252.234-

7001, DFARS

252.234-7002

Defense Federal Acquisition Regulation Supplement

IEEE Std 12207-

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 http://www.nfpa.org/Catalog/ http://www.osha.gov/

3. REQUIREMENTS

The tasks described in this SOW intend to address the approach toward CDT PL within LT2 Construct. In addition, the contractor shall procure, integrate, test, refresh hardware/software, and provide concurrency/upgrade capabilities to ten CDT MV systems at five CONUS locations and five OCONUS locations.

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

3.1 PRODUCT LINE (PL) MANAGEMENT AND PROCESSES

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.

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

DI-SESS-81022D Configuration Audit Summary Report and Certification

3.1.2 PL Core Assets Development and Evolution

The contractor shall perform tasks and activities necessary to continue the development, evolution, and sustainment of the CDT PL Core Assets.

3.1.3 Product Development, Integration, Testing, and Fielding

The contractor shall perform the necessary tasks and activities for product development 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:

Configuration Management Functional Analysis

Requirements Analysis System Engineering

Software Engineering System Design

System Integration Software Integration

Testing & Test Engineering Training

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

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:

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

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

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

d. 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 (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.

3.2.5.1 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

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

b. Risk and problem identification

c. Subcontract management/progress

d. Data collection and modeling

e. CDT 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. Cybersecurity status and progress

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

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.

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

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.

FAR Part 52.245-1, Government Property, shall determine the definitions, clauses, policies and procedures for Government Property, unless otherwise specified in this contract. Government property in the possession of the contractor shall be maintained and serviced to a fully operational state.

DI-MGMT-80441 Government Property Inventory Report

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. For estimating purpose in this DO, the Government estimates that there will five VIP visits.

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

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

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

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

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

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

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

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

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

3.2.11.9 Performance or Delivery in a Foreign Country

N/A.

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

DI-SESS-81785A Systems Engineering Management Plan (SEMP)

3.3.1 Systems Design

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. The requirements and initial design documentation generated during the system definition stage shall guide subsystem development. 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:

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

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

c. System-level risks adequately address to justify continued development.

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

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

f. 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).

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

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

a. System Requirements Document

b. System software functionality description

c. Preferred system solution definition

d. Hardware/software allocation

e. Human interfaces

f. Data collection

g. Test Plan

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

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

3.3.1.3 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 development 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 subsystem developed. 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. The purpose of each review is to assure that:

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

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

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

d. Software architecture is described using four views: 1) software module view; 2) software runtime view, 3) use case view, and 4) software deployment view

e. Subsystem risks have been assessed and mitigated to a level appropriate to continue development

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

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

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

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

j. 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).

3.3.1.4 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. The purpose of this review shall be to ensure that:

a. Each detailed component definition is sufficiently mature to meet measure of effectiveness and measure of performance criteria.

b. Component specifications are reasonable and provide a sound component concept.

c. Component and related life cycle process risks assess and mitigate to a level appropriate to support the fabrication, assembly, integration, and test phases.

d. Trade-study data are adequate to substantiate that detailed component requirements are achievable.

e. Software architecture describes using four views: 1) software module view; 2) software runtime view, 3) use case view, and 4) software deployment view.

f. Human system interfaces identify and describe in the detailed design and are traceable to design requirements.

g. The detailed software design (to include COTS/GOTS product name and version number) describes in terms of the satisfaction of functional and non-functional systems requirements.

h. Decisions made in arriving at the detailed component definition configuration supports analysis and technical data.

i. Security engineering processes integrates into the design to achieve an integrated secure solution.

j. Government approves inspection of all incremental development.

The contractor shall present the completed CDT PL design to the Government at the Critical Design Review (CDR).

3.3.1.5 Fabrication, Assembly, Integration and Test Phase

When inspection, analysis, demonstration, or tests determined product deficiencies exist, the contractor shall resolve any product deficiencies for the system, product, subsystem, assembly, or component. The contractor shall verify that the products designed satisfy specifications. The contractor shall integrate security engineering processes into the design to achieve an integrated secure solution. The contractor shall complete functional configuration audits, with Government participation, to verify that products have achieved requirements; that they satisfy the characteristics as specified in specifications, interface specifications, and other baseline documentation; and that test plans and procedures were complied. The contractor shall informally present results at the CDT IPT meeting.

3.3.2 Hardware Engineering

The contractor shall design, develop, integrate, assemble, and test CDT system hardware that satisfies the performance and CS requirements stated in the DO. The contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. The contractor shall document in the integrated database information gathered throughout each of the design stages. The contractor shall consider the development of hardware in context of a virtual environment product line; ensuring attention was given to architecture and reuse at each phase and DO.

3.3.3 Software Engineering

The contractor shall develop the system software and firmware; and maximize leveraging the PM TRADE LT2 processes for software development practices.