Rev 1 Attch 23 DO 04 LAV-25 SOW.pdf

STATEMENT OF WORK

FOR THE

GUNNERY TRAINING SYSTEMS (GTS) – LAV-25

TECHNOLOGY REFRESH AND CONCURRENCY UPGRADES

DELIVERY ORDER (DO) 0004

VERSION 1.0

27 January 2021

Program Manager for Training Systems Marine Corps Systems Command

12211 Science Drive Orlando, Florida 32826-3224

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD contractors only (Administrative or Operational Use) (2 April 2020). Other requests shall be referred to Program Manager, Training Systems, Marine Corps Systems Command, 12211 Science Drive, Orlando, Florida 32826-3224.

SOW-2019-0024

W900KK-21-R-0055

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

This page intentionally left blank.

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

RECORD OF CHANGES

Revision Number Date Change Description Approved By

1.0 27 Jan 2021 Initial Release

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Table of Contents

1. SCOPE

1.1 INTRODUCTION

1.2 GOAL AND OBJECTIVE

1.3 BACKGROUND

2. APPLICABLE DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

2.2 NON-GOVERNMENT DOCUMENTS

3. REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.1.1 INTEGRATED MASTER PLAN (IMP)

3.1.2 INTEGRATED MASTER SCHEDULE (IMS)

3.1.3 FINANCIAL MANAGEMENT

Earned Value Management Integrated Baseline Review

3.1.4 PRODUCT LINE MANAGEMENT AND PROCESSES

3.1.5 CONFIGURATION MANAGEMENT

3.1.5.1 Configuration Management Planning and Management

3.1.5.2 Configuration Identification

Configuration Change Management Configuration Status Accounting (CSA) Configuration Validation and Audit Contractor Internal Hardware Build-Up Audit Government Sample Audit to Verify Product Baseline Physical Configuration Audit (PCA) Software Configuration Management

Software Configuration Control Board Software Item Database Systems Engineering Interface Engineering Change Proposal (ECP) ECP Review Variances

3.1.6 TECHNICAL PERFORMANCE MEASURES (TPM)

3.1.7 RISK MANAGEMENT

3.1.8 MANAGEMENT REVIEWS AND SUBCONTRACTOR MANAGEMENT

Post Award Conference (PAC)/Start of Work Meeting

3.1.8.1.1 PAC Entry Criteria

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

3.1.8.1.2 PAC Exit Criteria

Program Management Reviews (PMR) Integrated Product Team (IPT) Meetings Technical Interchange Meetings (TIMs)

3.1.9 VISITOR SUPPORT

3.1.10 SUBCONTRACTOR MANAGEMENT

3.1.11 OBSOLESCENCE MANAGEMENT

3.1.12 DATA RIGHTS

3.1.13 GOVERNMENT FURNISHED INFORMATION (GFI)

3.1.14 GOVERNMENT FURNISHED EQUIPMENT (GFE)

3.1.15 SECURITY

Controlled Unclassified Information (CUI) Security Training

3.1.15.2.1 Threat Awareness Reporting Program (TARP)

3.1.15.2.2 Operation Security (OPSEC) Awareness Training

3.1.15.2.3 Insider Threat Training

3.1.15.2.4 DOD Annual Security Awareness Refresher Training

3.1.15.2.5 CUI Training

3.1.15.2.6 Unauthorized Disclosure of Classified Information of DOD & Industry

3.1.15.2.7 Anti-Terrorism (AT) Awareness Training for Contractor Personnel Traveling Overseas

3.1.15.2.8 AT Level I Awareness Training

3.1.15.2.9 iWATCH Training

3.1.15.2.10 Cybersecurity (CS) Information Technology (IT) Training and Certification

Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

Army Training Certification Tracking System (ATCTS) Registration for contractor Employees Who Require Access to Government Information Systems

3.2 SYSTEM ENGINEERING

3.2.1 SYSTEM DESIGN

System Definition Phase Preliminary Design Phase Final Design Phase Fabrication, Assembly, Integration and Test Phase

3.2.2 HARDWARE ENGINEERING

Hardware Requirements and Review

3.2.3 SOFTWARE ENGINEERING

Software Requirements and Review Software Design and Implementation Software Development Test Software Integrity Certification

3.2.4 HARDWARE AND SOFTWARE INTEGRATION

3.2.5 CYBERSECURITY (CS)

Cybersecurity Artifacts Cyber Security (CS) Control Review/RMF Package Security Control Assessment (SCA) Readiness Review SCA Event Information Assurance Vulnerability Management Program (IAVMP)

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Information Assurance Contractor Training and Certification

3.2.6 SPECIALTY ENGINEERING

Security Engineering Reliability, Availability and Maintainability (RAM) Engineering Safety Engineering Health Hazard Assessment Producibility Engineering Quality Engineering

3.2.6.6.1 Test Discrepancies

3.2.6.6.2 Test Discrepancy Processing

3.2.6.6.3 Test Discrepancy Severity

Human Factors Engineering Electromagnetic Environmental Effects (E3) Contaminate and Corrosion Control

Standardization

3.2.6.11 Integration of Third Party Products

3.2.7 TECHNICAL REVIEWS

System Requirement Review (SRR)

3.2.7.1.1 SRR Entrance Criteria

3.2.7.1.2 SRR Completion/Exit Criteria

3.2.7.1.3 SRR Products

Preliminary Design Review (PDR)

3.2.7.2.1 PDR Entrance Criteria

3.2.7.2.2 PDR Completion/Exit Criteria

3.2.7.2.3 PDR Products

Critical Design Review (CDR)

3.2.7.3.1 CDR Entrance Criteria

3.2.7.3.2 CDR Completion/Exit Criteria

3.2.7.3.3 CDR Products

3.2.8 PRODUCT DEFINITION DATA (PDD)

Maintenance Services

3.3 LOGISTICS

3.3.1 LOGISTIC PRODUCT DATA (LPD)

Initial Spares

3.3.2 TECHNICAL MANUALS

Training System Utilization Handbook (TSUH) System Maintenance Manual (SMM) Commercial Off-The-Shelf (COTS) Manuals Technical and COTS Manual Validation Technical Manual Verification

3.3.3 ITEM UNIQUE IDENTIFICATION (IUID)

3.3.4 SOFTWARE SUPPORT ENVIRONMENT

3.3.5 TRAINING

New Equipment Training (NET) Senior Instructor/Operator Training Instructor/Operator Training Maintenance Training

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

3.4 INTERIM CONTRACTOR SUPPORT (ICS)

3.5 INTEGRATED TESTING

3.5.1 TEST READINESS REVIEW (TRR)

3.5.1.1 TRR Entry Criteria

3.5.1.2 TRR Exit Criteria

3.5.2 IN-PLANT ACCEPTANCE TEST (IPAT)

3.5.3 CYBERSECURITY COMPLIANCE

3.5.4 OPERATION TEST SUPPORT

3.5.5 PRODUCTION QUALIFICATION TEST (PQT)

3.5.6 BASELINE SYSTEM TEST

3.5.7 ON-SITE ACCEPTANCE TEST (OSAT)

3.6 SITE ACTIVATION

3.6.1 SITE SURVEY

3.6.2 SITE PREPARATION

3.6.3 INSTALLATION TOOLS AND TEST EQUIPMENT

3.6.4 INSTALLATION SPARES

3.6.5 REMOVAL OF EQUIPMENT

3.7 SYSTEM TECHNICAL SUPPORT

3.8 OUTSIDE THE CONTINENTAL UNITED STATES (OCONUS) TRAVEL

3.9 SPECIFIC REQUIREMENTS

3.9.1 LAV-25 AGTS TECHNOLOGY REFRESH

Hardware Refresh

3.9.1.1.1 Institutional LAV-25 AGTS

3.9.1.1.2 LAV-25 DAGTS

3.9.1.1.3 LAV-25 TAGTS

3.9.1.1.4 LAV-25 PAAR

3.9.1.1.5 Hardware Assessment

Software Modifications

3.9.1.2.1 Software Commonality

3.9.1.2.2 Operating System

3.9.1.2.3 Software

IOS Hardware Upgrade Models Terrain Database Modification Technology Refresh Kits and Installation

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Appendix

Appendix Contents Page No.

A GFE 61

B GFI 62

C CM2 & Legacy Models List 63

D LAV-25 Mission Essential Function Failures

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

1. SCOPE

The United State Marine Corps (USMC), Marine Corps System Command (MARCOSYSCOM), Program

Manager for Training System (PM TRASYS) intends to conduct a technology refresh of all Light Armored

Vehicle -25 Advanced Gunnery Training System (LAV-25 AGTS) configurations and Pre-brief After Action

Review (PAAR). This effort will include:

• A hardware refresh of LAV-25 AGTS and PAAR

• Update software components and operating system (OS) to the latest Government approved version on the LAV-25 AGTS and PAAR

• Integration of CM2 models and US Army Gunnery Training System (GTS) terrain databases on the LAV-25 AGTS and PAAR

• Upgrade the Instructor Operator Station (IOS) to include the Plan View Display (PVD)

• Disposal of legacy LAV-25 AGTS components

1.1 INTRODUCTION

This SOW establishes responsibilities for performance of the tasks related to the procurement, integration, testing, cyber security certification, delivery and installation for the technology refresh to the existing LAV-25 AGTS.

1.2 GOAL AND OBJECTIVE

The goal is to conduct a technology refresh of all LAV-25 AGTS configurations and PAAR.

1.3 BACKGROUND

The LAV-25 AGTS provides advanced training capability, operational readiness, tactical proficiency, and crew training in precision gunnery and mission tactical skills to commanders, drivers, and gunners.

The LAV-25 AGTS trains Marines in operational skills, target acquisition, identification, and engagement with the LAV-25 main guns using both the primary and auxiliary fire control systems. Sighting equipment allows training against mobile and stationary threats and against single and multiple targets in realistic battlefield environments during day, night, and reduced visibility conditions.

There are five (5) LAV-25 AGTS configurations:

• LAV-25 Relocatable AGTS (RAGTS)

• LAV-25 Mobile AGTS (MAGTS)

• LAV-25 Permanent AGTS (PAGTS)

• LAV-25 Deployable AGTS (DAGTS)

• LAV-25 Tabletop AGTS (TAGTS)

Additionally, there are two (2) PAAR configurations:

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

• Relocatable PAAR (R-PAAR)

• Permanent (P-PAAR)

Below is a systems description of all the LAV-25 AGTS and PAAR configurations:

o Permanent AGTS (PAGTS). Full-fidelity training systems, which are installed in permanent facilities at the School of Infantry (SOI) West, Marine Corps Base (MCB) Camp Pendleton, CA.

o Relocatable AGTS (RAGTS). RAGTS is an AGTS packaged into a 20’ long by 8’ wide by 8.5’ high, non-expandable International Standards Organization (ISO)-type Government Issue shelter, and is fielded at base locations where permanent facilities are unavailable. RAGTS are installed on concrete pads and furnished with shore power. RAGTS includes Instructor/Operator Station

(IOS), crew station, driver station, visual subsystem, computational subsystem, and instructional subsystem.

o Mobile AGTS (MAGTS). MAGTS is a self-contained RAGTS mounted on a semi-trailer with on-board generators and environmental controls for use in remote locations including ranges.

MAGTS is operated with either shore power or generators.

o Permanent PAAR. PAAR is the hub that links the AGTS trainers together (PAGTS, MAGTS, RAGTS) to conduct section and platoon training. The PAAR station provides the instructor the capability to monitor the battlefield during section and platoon training. The PAAR provides the data logging and playback of section and platoon previously recorded exercises. The data includes the Plan View Display (PVD), 3-Dimension View (Stealth View) voice communication traffic. In addition, the PAAR also provides the print out take home package of the exercise performance report. Permanent PAAR (P-PAAR) is installed in permanent facility at the SOI

West.

o Relocatable PAAR. R-PAAR is a PAAR packaged into a 20’ long by 8’ wide by 8.5’ high, non-expandable International Standards Organization (ISO)-type Government Issue shelter, and is fielded at base locations where permanent facilities are unavailable.

o Deployable AGTS (DAGTS). DAGTS is intended and designed for use aboard ship and in classrooms. Although packaged in a rugged transit case, it uses the same software as RAGTS and MAGTS. DAGTS consists of a Commander (CDR) station, Gunner (GNR) station, and an

IOS. DAGTS supports individual training, collective training tasks, and gunnery qualification.

DAGTS can connect to other AGTS configurations (excluding TAGTS) to provide section- and platoon-level training.

o Tabletop AGTS (TAGTS). TAGTS is intended and designed for use aboard ship, in classrooms, and in remote locations. TAGTS includes all AGTS databases and exercises of the larger variants. It consists of three stations (Commander [CDR], Gunner [GNR], and IOS) and is comprised of touchscreen displays with GNR and CDR handles. TAGTS enables sustainment of

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

critical skills while aboard ship or deployed to any theatre of operation, and supports individual training tasks, collective training tasks, and gunnery qualification

CVTS is used by Marine Forces Pacific (MARFORPAC), Marine Forces Atlantic (MARFORLANT), Marine

Forces Reserves (MARFORRES) and formal schools. It was originally fielded in 2003 and was last updated in 2013. Several hardware and software items are obsolete and require replacement with more relevant technologies. Additionally, the Marine Corps intends to leverage common hardware and software product line with the Army’s Gunnery Training System (GTS) program.

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 GOVERNMENT DOCUMENTS

139053-3 Prime Item Development Specification (PIDS) for the US Army M1A2 SEP AGTS, Rev. P

17602273.2 Safety Assessment Report (SAR) for the USMC LAV-25 AGTS, Rev. C

23D-MCLAV25-A007 Prime Item Development Specification (PIDS) for USMC LAV-25 AGTS, Rev. F

24D-MCLAV-D006 Trainer Configuration Report for USMC LAV-25 DAGTS, Rev. C

29 CFR 1910.1200 Occupational Safety and Health Standards Toxic and hazardous Substances

56D-A003/A009-1 Computer Resources Integrated Support Document (CRISD) for LAV-25 AGTS, Rev. D

56D-MCLAV-25DAGTS-A001 Deployable Advanced Gunnery System (DAGTS) Safety Assessment Report, Rev. A

6455110 Computer Software Product End Item (CSPEI) for the USMC LAV- 25 AGTS/DAGTS, Rev. K

CNSSI 1253 Committee on National Security System Instruction (CNSSI) 1253 Systems

DFARS 252.211-7003 Item Unique Identification and Valuation

DFARS 252.225-7043 Antiterrorism/Force Protection for Defense Contractors outside the

US

DFARS 252.239-7001 Information Assurance Contractor Training and Certification

DOD 4500.54G DO Foreign Clearance Guide

DODM 5200.01, Vol. 3 DOD Information Security Program: Protection of Classified Information

DOD 8570.01-M Information Assurance Workforce Improvement Program

DODD 8140.01 Cyberspace Workforce Management

DODI 5200.48 Controlled Unclassified Information (CUI)

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

DOD 5220.22-M National Industrial Security Program Operating Manual

DODI 8500.01 Cybersecurity (CS)

DODI 8510.01 Risk Management Framework for DOD Information Technology

DODI 8582.01 Security of Unclassified DOD Information on Non-DOD Info Systems

FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel LT2-TRADE_PLAN-2013-00009 Live Training Transformation (LT2) Product Line Configuration LT2-TRADE-PLN-000384 Live Training Transformation (LT2) Operations Guide (Version H)

MCO 3070.2A Marine Corps Operations Security (OPSEC) Program

MCO 3302.1D Level I Antiterrorism (AT) Awareness

MCO 4410.28 Item Unique Identification (IUID) of Ground Equipment

MCO 5239.2 Marine Corps Information Assurance Program

MCSCO 5400.5 Naval Systems Engineering Policy

MCTM04-060-1 Training System Utilization Handbook for the USMC LAV-25 AGTS, Rev. N

MCTM04-061 System Maintenance Manual (SMM) USMC LAV-25 AGTS, Rev, F

MIL-HDBK-61 Configuration Management Guidance

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

MIL-STD-130 Identification Marking of US Military Property

MIL-STD-1472 Department of Defense (DOD) Design Criteria Human Engineering

MIL-STD-31000B Technical Data Packages

SP 800-171 Protecting Controlled Unclassified Information in Non-federal Systems and Organization

TM 6426334 LAV-25 DAGTS SMM, Rev. G

TM 6454357 LAV-25 Tabletop Advanced Gunnery System (AGTS) User Guide

2.2 NON-GOVERNMENT DOCUMENTS

CNSSI 1253F Committee on National Security Systems Instruction (CNSSI) 1253

EIA-649 National Consensus Standard for Configuration Management

GEIA-HB-0007-B Logistics Product Data Handbook

GEIA-STD-0007-B Logistics Product Data

IEEE STD 12207-2017 IEEE Standard Systems and software engineering – Software life cycle processes

IEEE STD 15288.2-2014 IEEE Standard for Technical Review and Audit on Defense Programs

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

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

TA-HB-0007-1 Logistics Product Data Reports Handbook

3. REQUIREMENTS

The contractor shall design, develop, produce, test, and install a technology refresh to the LAV-25 AGTS system and PAAR. Section F of the contract contains the required site-specific sequence for installation and delivery of refreshed systems.

3.1 PROGRAM MANAGEMENT

The contractor shall provide the overall management and administrative effort necessary to ensure the requirements of this contract are accomplished. Program management practices shall provide visibility into the contractors’ organization and techniques used in managing the program, specifically subcontractor and data management. The contractor shall track program progress utilizing metrics. The contractor shall consider life cycle costs while conducting trade studies and evaluating design alternatives. The contractor shall define and monitor metrics 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, document issues, and provide 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

f. Risks and mitigation plans

(DI-MGMT-80227) Contractor’s Progress, Status and Management Report

3.1.1 Integrated Master Plan (IMP)

The contractor shall implement, manage to, update, and maintain the contract IMP in accordance with the

Contracts Section F of this solicitation. The contractor shall develop the system in accordance with the

IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The contractor shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews and at Government discretion. The IMP shall depict the contract work breakdown structure.

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

3.1.2 Integrated Master Schedule (IMS)

The contractor shall develop, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The contractor shall develop the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the total program.

These network activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The network shall be implemented on a computer based program management control system which utilizes critical path method network analysis, accepts parametric data input, and can be utilized to determine a probabilistic estimate of the program schedules and cost for reporting project progress. The network activities time and cost data shall be updated to reflect accomplished activities and any changes in activity time and cost estimates. The contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6

3.1.3 Financial Management

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

The CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The contractor shall identify major elements of subcontracted work in the extended

CWBS. The contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives.

(DI-MGMT-81651) Contract Invoicing and Payment Report

Earned Value Management

Not required

Integrated Baseline Review

Not required

3.1.4 Product Line Management and Processes

The LAV-25 AGTS software, digital information, and documentation will reside on the Live Training

Transformation (LT2) portal. The LT2 portal is an Army repository for data and standards for the training community created under the CPMNext contract. Information uploaded by the contractor onto the LT2

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

portal may be available to other contractors on a need to know basis to perform work for the Army. The contractor shall provide a plan that documents a path to conformance with the LT2 Product Line

Operations and CM Guide. The LT2 CM portal and guides are located at www.lt2portal.mil. A Common

Access Card (CAC) is required to access the LT2 repositories.

3.1.5 Configuration Management

The contractor shall maintain a Configuration Management (CM) process for the control of all requirements, hardware, software, internal and external system interface configuration documentation, media and parts representing or comprising the system configuration items (CIs). The principles contained in EIA-649, National Consensus Standard for Configuration Management, and MIL-HDBK-61, Configuration Management Guidance, should be used for guidance as well as related MCSCO 5400.5:

Naval Systems Engineering Policy. The contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The contractor shall provide, maintain, and update configuration management procedures and processes for control of all hardware and software baselines.

The Government will maintain control of the functional baseline (FBL) defined by the PIDS.

(DI-SESS-80858C) Supplier’s Configuration Management Plan

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

The contractor shall identify unique identifiers for selected system attributes, system information and components (hardware and software) to be used as the basis for configuration management.

Configuration Change Management

The contractor shall establish a systematic and measurable configuration change management process for managing CM baseline configuration changes and variances. The LAV-25 AGTS PIDS establishes the functional baseline. Government approval shall be required for any changes to the functional baseline. The LAV-25 AGTS allocated baseline shall be established at closure of Preliminary Design

Review (PDR). The LAV-25 AGTS product baseline shall be establish upon the completion of the

Physical Configuration Audit (PCA). Section 3.1.5.13 of this SOW addresses changes to an established baseline. Once the product baseline has been established, configuration control will revert to the

Government for approval of all configuration changes.

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Configuration Status Accounting (CSA)

The contractor shall provide access to accurate, timely information about the system and its documentation through the CSA database. The contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current and historical data. The contractor shall:

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

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

c. Capture configuration information as it evolves.

Configuration Validation and Audit

The contractor shall validate and audit the system configuration information to ensure that requirement attributes are met and accurately documented. The contractor shall:

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

b. Maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements.

Contractor Internal Hardware Build-Up Audit

Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel and approved by the Quality Assurance (QA) Manager to verify the as-built configuration matches the design documentation prior to use of each part in production. During this process each product definition document will also be examined for proper format (compliance with

American National Standard Institute (ANSI) Y14 series standards), completeness, currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part. A record of each product attribute verified shall be maintained and available through the LT2 documentation repository.

Government Sample Audit to Verify Product Baseline

Not required.

Physical Configuration Audit (PCA)

The contractor shall support the Government in conducting the PCA by providing the necessary space, tools, equipment, personnel, and documentation required for the activity. The PCA is the formal technical examination of the system “as-built” configuration against its technical documentation to establish or verify the configuration item’s product baseline. It is used to examine the actual configuration of each item (down to the lowest level of repair) in order to verify that the related design documentation matches the physical configuration. The PCA addresses accuracy of the documentation to include inspection of

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

inventory/equipment lists, logistics product data summaries, documentation, drawings, spares and all manuals. The documentation and equipment shall be examined to verify that all applicable safety labels along with incorporating applicable warnings are incorporated. An initial PCA shall be conducted at the In

Plant Acceptance Test (IPAT) to review final documentation for logistics product data, documentation, drawings and manuals. Final PCA shall be conducted onsite to verify the as-installed system’s inventory/equipment list, safety labeling, and spares.

Each item shall be inspected to ensure:

a. Government property sticker is affixed in a prominent location

b. Verification of serial number and Item Unique Identification (IUID).

c. Equipment Inventory Records (EIR) shall contain the following data: Complete Item

Description, Original Part Number, National Stock Number (NSN), Serial Number, Quantity, Vendor Name, Vendor Point of Contact (POC), and Warranty Period.

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

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

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

Software Configuration Management

Not required.

Software Configuration Control Board

Not required.

Software Item Database

Not Required.

Systems Engineering Interface

The configuration management system must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The information architecture must permit capture of change information and notify affected team members.

Engineering Change Proposal (ECP)

Engineering Change Proposals (ECPs) shall be submitted by the contractor for all changes to established baselines.

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

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

ECP Review

In coordination with the Government, the contractor shall hold a requirements review on all proposed changes prior to the submittal of the engineering change proposal in order to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PM TRASYS, or a formal meeting at the contractor’s facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. The contractor shall also be responsible for generating minutes of the review and provide them to the Government for approval.

(DI-ADMN-81505) Report, Record of Meeting/Minutes

Variances

The contractor shall document the rationale and the potential impact to any LAV-25 AGTS system and its respective variances. The contractor shall obtain approval before varying from any Government-controlled baseline.

(DI-SESS-80640D) Request for Variance (RFV)

3.1.6 Technical Performance Measures (TPM)

Not required.

3.1.7 Risk Management

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

(DI-MGMT-81809) Risk Management Status Report

3.1.8 Management Reviews and Subcontractor Management

The contractor shall conduct Management Reviews at the request of the Government with a minimum of one every quarter. The Government and contractor shall mutually agree upon the review location. The

Management Reviews shall provide an accurate program overview and a detailed discussion of pre-selected topics. The contractor shall manage subcontractors and shall be responsible for the performance of subcontractors.

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Management reviews shall use IPT meetings/teleconferences to address systems production, status of activities, questions, and issues in a timely manner. The contractor shall prepare the meeting agendas, document action items, document due dates, coordinate resolution, and track action items until closure.

Action item closure shall require contractor and Government approval. At a minimum, the contractor shall conduct the following meetings and reviews:

(DI-ADMN-81505) Report, Record of Meeting/Minutes

(DI-ADMN-81605) Briefing Material

Post Award Conference (PAC)/Start of Work Meeting

The contractor shall conduct a PAC held at the contractor’s facility, at a mutually agreed upon date with the Government, within 20 working days after contract award. The purpose of the conference shall be to establish the framework of the contractor and Government interaction during the performance period of the contract. The contractor shall place emphasis on the operating procedures, methodologies, and processes used in the execution of the contract. The meeting shall include the contractor’s key team members identified in the proposal with emphasis on top level management of the program, agreement on metrics used as management indicators during the program and partnering approach to implement.

The contractor shall present the program IMS, Integrated Product Team (IPT) structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the AGTS mission. The contractor shall document action items, record due dates, coordinate resolution and track action items until closure.

3.1.8.1.1 PAC Entry Criteria.

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

The PAC Agenda shall include the following:

• Introduction and Overview

• Discussion and clarification of requirements

• Program Management Plan including subcontractors

• Risk Management Process and Report

• Quality Control Program

• Integrated Master Schedule (IMS), critical path, milestones, and deliverables

• Contractor Work Breakdown Structure (CWBS)

• Configuration Management Plan o Effective configuration identification o Change control o Status accounting o Audits of the total configuration, including hardware and software

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

• Integrated Logistic Support Overview o Revision of existing technical documentation (COTS and Operational and Technical manuals) o Parts provisioning and selection o Obsolescence management o Long lead item identification and status o Spares o Tools and test equipment (if applicable) o Warranty o Inventory (Hardware/Software) Control o Item Unique Identification (IUID) Marking Plan o Disposal of removed LAV-25 AGTS components

• Overview of GFI/GFE

• Overview of LT2

• Contract Management Plan (i.e. invoicing, billing)

3.1.8.1.2 PAC Exit Criteria.

The PAC exit criteria shall consist of the following:

• Government concurrence that all required PAC agenda items have been satisfactorily presented, discussed, and documented

• Government acceptance of PAC CDRLs

(DI-SESS-80858C) Supplier’s Configuration Management Plan

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6 (DI-ADMN-81505) Report, Record of Meeting/Minutes

(DI-MGMT-81605) Briefing Material

Program Management Reviews (PMR)

Not required.

Integrated Product Team (IPT) Meetings

The contractor shall host and participate in weekly IPT meetings with Government representatives which address the full spectrum of the program concerns including system engineering, schedule, financial, integrated logistics support, and testing. The contractor shall document and timely submit the minutes to the Government team members. The IPT shall include the followings:

a. Hardware and software design status

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

b. Risk and problem identification

c. Subcontract management/progress

d. Data collection and modeling

e. LAV-25 AGTS Government Furnished Equipment (GFE) planning and status

f. Logistics planning

g. Test planning

h. Provisioning for training and technical publications status

i. Schedule status

j. Pre-selected topics of interest

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

l. Obsolescence Management

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.

(DI-ADMN-81505) Report, Record of Meeting/Minutes

(DI-MGMT-81605) Briefing Material

Technical Interchange Meetings (TIMs)

The contractor shall conduct and participate in TIMs to be held at both Contractor and Government facilities. The specific locations, dates, and durations of the meetings shall be coordinated through the

IPT. The meetings shall be co-chaired by a Government and contractor representative. The contractor shall be prepared to explain the reasoning, assumptions, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare drawings and other data to aid in the presentations. The contractor shall have all the required personnel and resources present. The contractor shall make available facilities for Government-only meetings. The contractor shall prepare the meeting agendas and document the meeting results. Except where noted, meetings shall be considered fulfilled when all of the following items are completed:

• A formal review meeting has been conducted

• All action items responses have been documented and accepted by the Government.

• Submittal of meeting minutes

(DI-ADMN-81505) Report, Record of Meeting/Minutes

(DI-MGMT-81605) Briefing Material

3.1.9 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

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Government as required. The Government will provide no less than 48 hours advance notice for VIP visits.

3.1.10 Subcontractor Management

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

3.1.11 Obsolescence Management

The contractor shall implement an obsolescence management program. The contractor shall provide the

IPT a list of obsolete items and recommend solutions. The recommended solution shall be reviewed and approved by the Government.

3.1.12 Data Rights

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

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

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

c. Maintain, repair, modify, and upgrade a LAV-25 AGTS using Government personnel and other Government contractors

d. Compete future LAV-25 AGTS requirements and upgrades

3.1.13 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 additional information is required and not provided by the Government. The contractor shall be responsible to secure, protect, and maintain the data provided as GFI (See Appendix A).

3.1.14 Government Furnished Equipment (GFE)

The Government will provide one LAV-25 RAGTS, one LAV-25 DAGTS, and one LAV-25 TAGTS. The contractor shall also be responsible for the transportation of these systems from a Government location to the contractor’s facility and back to the Government location upon completion of the contract or per

Government direction (See Appendix B).

Upon contract award, the contractor shall inventory GFE provided and subsequently maintain records of all GFE. The contractor shall submit annual inventory reports to the Government. The contractor shall be

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

responsible for the maintenance, custody, control, movement, disposal, and storage of all GFE in accordance with Government provided Systems Maintenance Manual (SMM), Training System Utilization

Handbook (TSUH), and LAV-25 AGTS disposal plan.

(DI-MGMT-80441D) Government Property Inventory Report

3.1.15 Security

The contractor shall be in compliance with the security regulations and security requirements specified in

Contracts Security Classification Specifications, DD Form 254, and addendums sheets.

The contractor shall have a Secret facility clearance with no storage requirements. Based on various

DOs, the contractor will require access to Controlled Unclassified Information (CUI), Technical

Information/Documents, and Export Controlled Information.

Performance of this contract shall be worldwide as designated by individual DOs. The base ID/IQ DD254 will support the security requirements for this contract. Individual DD254s will not be issued for each DO unless it is outside of the security bounds of the base DD254.

Some positions/duties may not require a clearance but all positions/duties shall require investigation for duties and access to U.S. Government systems and technical information. The contractor shall ensure that employees performing under this contract have the appropriate clearance.

The contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified "Confidential," "Secret," or "Top Secret". The contractor shall comply with:

a. The Security Agreement (DD Form 441), including the National Industrial Security Program

Operating Manual (DOD 5220.22-M)

b. Any revisions to DOD 5220.22-M

c. Contract Security Classification Specification (DD254)

All contractor employees and subcontractor employees, requiring access to Marine Corps bases, installations, facilities and controlled access areas shall complete all actions required by base, installation, facility, and area commanders to gain access. All contractor and subcontractor employees shall comply with base, installation, and facility and area rules and regulations.

The information provided to the contractor will be unclassified and/or Controlled Unclassified Information

(CUI). The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. Any contractor personnel requiring access to U.S. Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust Position. The Company must notify the MCSC AC/S G-2 Personnel

Security Office (PERSEC Office) via encrypted e-mail to MCSC_Security@usmc.mil or 703-432-

3374/3952, within 24 hours, of any adverse/derogatory information associated with the 13 Adjudicative

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

Guidelines concerning any contractor performing on this contract, if they have been issued a CAC and/or a MCSC Building Badge.

Controlled Unclassified Information (CUI)

The contractor shall implement CUI marking requirements in accordance with DODI 5200.48.

Security Training

The contractor shall read and execute the below listed security training for Contractor employees who have security clearances and who are working on DOD contracts. .

3.1.15.2.1 Threat Awareness Reporting Program (TARP)

Not required.

3.1.15.2.2 Operation Security (OPSEC) Awareness Training

Per MCO 3070.2A Marine Corps Operations Security (OPSEC), the contractor employees working on this contract shall complete Level I OPSEC Awareness training. New employees shall be trained within 30 calendar days of their start date on this contract and annually thereafter. OPSEC Awareness training information and materials are available at (https://www.cdse.edu/catalog/elearning/GS130.html)

3.1.15.2.3 Insider Threat Training

The contractor and their subcontractors shall designate in writing a U.S. citizen as the Insider Threat

Program Official, per paragraph 1-202 of DOD 5220.22-M w/ change 2. All Contractors shall comply with

Insider Threat Training requirements, per paragraph 3-103 of DOD 5220.22-M w/ change 2. Insider

Threat program information and materials are available at

(https://www.cdse.edu/catalog/elearning/INT101.html)

3.1.15.2.4 DOD Annual Security Awareness Refresher Training

All contractor employees working on this contract with a security clearance shall complete the annual security awareness refresher training. New employees shall complete the initial security training and the security awareness refresher training annually thereafter. This training refreshes the employee’s basic understanding of initial security training requirements outlined in DODM 5200.01, Vol. 3, Encl. 5, the

National Industrial Security Program Operating Manual (NISPOM), and other applicable policies and regulations. This training is available at (https://www.cdse.edu/catalog/elearning/IF142.html)

3.1.15.2.5 CUI Training

All contractor employees who handle CUI shall take annual Center for Development of Security

Excellence (CDSE) CUI Training, which is required for all DOD and Industrial personnel with access to

CUI. New employees shall complete this training 30 days from start date of the contract. No CAC or password is needed to access the training website, which also provides a resource tab that lists https://www.cdse.edu/catalog/elearning/INT101.html https://www.cdse.edu/catalog/elearning/IF142.html

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

regulations, policies and more information on the subject. The training is available at

(https://securityhub.usalearning.gov/index.html)

3.1.15.2.6 Unauthorized Disclosure of Classified Information of DOD & Industry

Contractor employees working on this contract with security clearances shall complete the annual

Unauthorized Disclosure of Classified Information for DOD and Industry training. New employees shall complete this training 30 days from start date of the contract. This training provides an overview of what unauthorized disclosure is, specific types of unauthorized disclosure, common misconceptions about unauthorized disclosure, types of damage caused by unauthorized disclosure, and sanctions one could face if caught engaging in unauthorized disclosure. This training is available at

(https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=JS&course_number=-US080)

3.1.15.2.7 Anti-Terrorism (AT) Awareness Training for Contractor Personnel Traveling Overseas

The Contractor FSOs and associated subcontractor FSOs will brief and make available Government Area of Responsibility (AOR) specific AT Awareness Training and information to employees traveling overseas, as directed by MCO 3302.1D. Specific AOR training content is directed by the Combatant Commander with the unit Anti-Terrorism Officer (ATO) being the local point of contact. AT Level I Awareness Training meets this requirement and is available at the following website:

(https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=JS&course_number=-US007)

3.1.15.2.8 AT Level I Awareness Training

All contractor employees, to include subcontractor employees, requiring access to Military installations, Government Agency facilities, or Government-leased facilities and controlled access areas shall complete

AT Level I Awareness Training within 30 calendar days after contract start date. The contractor shall maintain certificates of completion for each affected Contractor and subcontractor employee for inspection or upon request by the COR or Contracting Officer (KO), if a COR is not assigned. AT level I

Awareness Training is available at the following website:

(https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=JS&course_number=-US007)

3.1.15.2.9 iWATCH Training

Not required.

3.1.15.2.10 Cybersecurity (CS) Information Technology (IT) Training and Certification

All contractor employees and associated subcontractor employees shall complete the DOD Cybersecurity

(CS) awareness training before issuance of network access and must be completed annually thereafter.

All contractor employees working in Cybersecurity Information Technology (CS/IT) functions shall comply with DOD training requirements per the Defense Federal Acquisition Regulation Supplement (DFARS)

252.239-7001, DoDD 8140.01, DoD 8570.01-M and MCO 5239.2 within 30 days of contract award or https://securityhub.usalearning.gov/index.html https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=JS&course_number=-US080

27 January 2021

“UNCLASSIFIED//FOR OFFICIAL USE ONLY”

employment. The baseline certification as stipulated in DOD 8570.01-M shall be completed upon contract award. CS/IT training for certification is located at (https://cs.signal.army.mil).

Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

The contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements accomplished by the installation Provost

Marshal Office, Director of Emergency Services, or Security Office. The contractor workforce shall comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity

Verification of contractor Personnel) as directed by DOD Headquarters, Department of the Army (HQDA), Department of the Navy and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National

Agency Check with Inquiries (NACI) or an equivalent or higher investigation. 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

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.

All contractor and contractor employees shall comply with all Government facilities rules and regulations.