Attachment_J1_-CCS-1.10.2-CCS_Mod_SOW-1.5_(Per_Amendment_0004).pdf

STATEMENT OF WORK

FOR THE

COMBAT CONVOY SIMULATOR MODIFICATION PROGRAM

VERSION 1.5

5 Oct 2017

Program Manager for Training Systems

Marine Corps Systems Command

12211 Science Drive

Orlando, Florida 32826-3224

DISTRIBUTION STATEMENT A: Approved for public release. Distribution is unlimited.

Statement of Work CCS Modification Program ii

TABLE OF CONTENTS

CCS SYSTEM MODIFICATION PROGRAM BACKGROUND AND DESCRIPTION .......................... 8 1

Scope ............................................................................................................................................ 8 1.1

CCS System Description .............................................................................................................. 8 1.2

APPLICABLE DOCUMENTS ............................................................................................................... 9 2

Government Documents ............................................................................................................... 9 2.1

Non-Government Documents ..................................................................................................... 10 2.2

REQUIREMENTS ............................................................................................................................... 11 3

Program and Data Management ................................................................................................ 13 3.1

3.1.1 Program Management

3.1.2 Common Access Cards (CAC)

3.1.3 Travel

3.1.4 Data Management

3.1.5 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

3.1.6 Contract Work Breakdown Structure (CWBS)

3.1.7 Assignment of Responsibility and Authority

3.1.8 Identification of Contractor Employees

3.1.9 Government Furnished Property (GFP)

3.1.10 Joint Battle Command – Platform (JBC-P) and Mounted Family of Computer Systems (MFoCS)

Risk Management ....................................................................................................................... 18 3.2

Meetings, Formal Reviews, Conferences, and Audits ................................................................ 18 3.3

3.3.1 Post Award Conference (PAC)

3.3.1.1 PAC Entrance Criteria:

3.3.1.2 PAC Agenda

3.3.1.3 PAC Exit Criteria

3.3.2 Integrated Product Team (IPT) Meetings

iii

3.3.3 In-Process Reviews (IPR)

Systems Engineering .................................................................................................................. 21 3.4

3.4.1 Technical Reviews

3.4.1.1 System Requirements Review / System Functional Review (SRR/SFR)

3.4.1.1.1 SRR/SFR Entrance Criteria

3.4.1.1.2 SRR/SFR Agenda

3.4.1.1.3 SRR/SFR Exit Criteria

3.4.1.2 Critical Design Review (CDR)

3.4.1.2.1 CDR Entrance Criteria

3.4.1.2.2 CDR Agenda

3.4.1.2.3 CDR Exit Criteria

3.4.1.3 Test Readiness Review (TRR)

3.4.1.3.1 TRR Entrance Criteria

3.4.1.3.2 TRR Agenda

3.4.1.3.3 TRR Exit Criteria

3.4.1.4 System Verification Review (SVR)

3.4.1.4.1 SVR Entrance Criteria

3.4.1.4.2 SVR Agenda

3.4.1.4.3 SVR Exit Criteria

3.4.2 Requirements Traceability Verification Matrix (RTVM)

3.4.3 Reliability and Maintainability Program

3.4.3.1 Procedures and Controls

3.4.3.2 Reliability Predictions

3.4.3.3 Failure Reporting, Analysis, and Corrective Action System (FRACAS)

3.4.3.4 Failure Modes, Effects and Criticality Analysis (FMECA)

3.4.4 Deficiency Reporting

Electromagnetic Environmental Effects (E3) .............................................................................. 29 3.5

3.5.1 Grounding, Bonding and Shielding

iv

Quality Management System ...................................................................................................... 29 3.6

Open System Architecture .......................................................................................................... 30 3.7

3.7.1 Design Approach Characteristics

3.7.1.1 Open Architecture

3.7.1.2 Modular, Open Design

3.7.1.3 System Requirements Accountability

3.7.1.4 Inter-component Dependencies

3.7.1.5 Life Cycle Management and Open Systems

3.7.1.6 Use of Standards

Producibility ................................................................................................................................. 32 3.8

Environment, Safety, and Occupational Health .......................................................................... 32 3.9

3.9.1 Accidents and Mishaps

3.9.2 System Safety

3.9.2.1 Safety Assessment

3.9.2.1.1 Safety Assessment Report

3.9.3 Lasers

3.9.4 Adverse Weather Conditions

3.9.5 Safety Placards, Signs, and Tags

Configuration Management (CM) Process ................................................................................. 34 3.10

3.10.1 Configuration Item (CI)

3.10.1.1 Configuration Status Accounting

3.10.2 Configuration Management Meetings/Audits

3.10.2.1 Interface Control Working Group

3.10.2.2 Functional Configuration Audit (FCA)

3.10.2.3 Physical Configuration Audit (PCA)

3.10.3 Baseline Management

3.10.3.1 Product Baseline

3.10.3.2 Allocated Baseline

v

3.10.3.3 Functional Baseline

3.10.4 Configuration Control

3.10.4.1 Engineering Release System

3.10.4.2 Engineering Change Proposals (ECP)

3.10.4.3 Requests for Variance

3.10.4.4 Notices of Revision

Engineering Drawings ................................................................................................................. 39 3.11

3.11.1 Product Drawings/Models and Associated Lists

Testing and Verification .............................................................................................................. 40 3.12

3.12.1 Test and Evaluation Program Plan (TEPP)

3.12.2 Test Plan

3.12.3 Testbed

3.12.4 Contractor Support to Government Testing

3.12.5 Reliability Testing and Reports

3.12.6 System Integration/Qualification Test (SIQT)

3.12.7 Production Acceptance Test & Evaluation (PAT&E)

3.12.8 System Stress Test

Cybersecurity .............................................................................................................................. 42 3.13

Integrated Logistic Support (ILS) ................................................................................................ 43 3.14

3.14.1 Logistics Integrated Product Team (IPT)

3.14.2 Maintenance Planning

3.14.3 CCS Maintenance Concept

3.14.3.1 CCS Field Maintenance

3.14.3.2 CCS Depot Maintenance

3.14.4 Parts Management Program

3.14.4.1 Parts List

3.14.5 Warranty Performance System

3.14.6 Item Unique Identification Data (IUID) Marking

vi

Supply Support ........................................................................................................................... 47 3.15

3.15.1 Provisioning Plan

3.15.2 Provisioning Technical Documentation

3.15.2.1 Provisioning Parts List (PPL)

3.15.2.2 Long Lead Time Items List (LLTIL)

3.15.2.3 Proposed Spare Parts List

3.15.2.4 Tools and Test Equipment

Technical Data Package (TDP) .................................................................................................. 48 3.16

Power .......................................................................................................................................... 48 3.17

3.17.1 Lithium Batteries

3.17.1.1 Lithium Battery Safety Qualification

3.17.2 Battery Charging

Technical Manuals ...................................................................................................................... 49 3.18

3.18.1 Operations and Maintenance (O&M) Manual

3.18.2 Commercial Items Component O&M Manuals

3.18.3 CCS System Component List (SL-3)

3.18.4 Change Pages/Modification Instructions

Support Equipment ..................................................................................................................... 49 3.19

3.19.1 Built-in test/built-in test equipment (BIT/BITE)

Instructional Media Package (IMP) ............................................................................................. 50 3.20

Modeling and Simulation (M&S) Verification and Validation (V&V) ............................................ 50 3.21

Packaging ................................................................................................................................... 50 3.22

Software ...................................................................................................................................... 51 3.23

3.23.1 Software Allocation

3.23.2 Computer Software Product End Items

3.23.3 Interface Control Document (ICD)

3.23.4 System/Subsystem Specification (SSS)

3.23.5 Interface Requirements Specification (IRS)

vii

3.23.6 System/Subsystem Design Description (SSDD)

3.23.7 Interface Design Description (IDD)

3.23.8 Database Design Description (DBDD)

3.23.9 Software Version Description (SVD)

3.23.10 Software Product Specification (SPS)

3.23.11 Software User Manual (SUM)

3.23.12 Firmware Support Manual (FSM)

3.23.13 Software Installation Plan (SIP)

Facilities ...................................................................................................................................... 53 3.24

3.24.1 Site Surveys

3.24.2 Trainer Facility Reports (TFR)

3.24.3 Facility Constraints

Reuse of Legacy CCS Components ........................................................................................... 53 3.25

3.25.1 Legacy CCS Components List

3.25.2 CCS Legacy Components Disposal

Terrain Databases ...................................................................................................................... 54 3.26

Training Scenarios ...................................................................................................................... 55 3.27

Camp Lejeune, NC CCS Installation .......................................................................................... 55 3.28

CCS Assumption of Responsibilities .......................................................................................... 55 3.29

LIST OF FIGURES

Figure 1 – Combat Convoy Simulator (CCS)

Figure 2 – Example IUID Construct 2 Label

Statement of Work CCS AAP

CCS SYSTEM MODIFICATION PROGRAM BACKGROUND AND DESCRIPTION 11

Scope 1.12

The primary purpose of this Statement of Work (SOW) is to modernize the hardware and software of the 3 in-service USMC Combat Convoy Simulator (CCS). 4

Modification: All planning, system design, production of system and system components, procurement 5 and shipping of parts and components, and other requirements in the SOW related to the first 15 months 6 of the contract. Includes all SETR events up to and including meeting the exit criteria of the first SVR IAW 7

SOW para. 3.4.1.4. Modification does not include installation of the modified systems. 8

Installation: All requirements identified in the SOW beginning 15 months after contract award with the 9 assumption of CCS responsibilities IAW SOW para. 3.29 and up to Government acceptance of each of 10 the delivered systems. Includes testing, delivery, and acceptance of each of systems. 11

The seven USMC CCS systems are located as follows: 12

• Camp Pendleton, CA. Quantity of 2. 13

• Camp Lejeune, NC. Quantity of 2. 14

• Marine Corps Air Ground Combat Center (MCAGCC), Twentynine Palms, CA. Quantity of 1. 15

• Marine Corps Base (MCB) Hawaii, HI. Quantity of 1. 16

• MCB Camp Smedley D. Butler, Camp Hansen, MCB Okinawa, Japan. Quantity of 1. 17

The two Navy CCS systems are located as follows: 18

• Naval Air Station (NAS) Point Mugu, CA. Quantity of 1. 19

• Naval Construction Battalion Center (NCBC) Gulfport, MS. Quantity of 1. 20

CCS System Description 1.221

The CCS is a simulator-based virtual environment to train convoy operations and basic tactics, techniques, 22 and procedures (TTP) for the driver, gunner, and passengers of the vehicle. The CCS consists of an 23

Instructor/Operator Station (IOS), After Action Review (AAR) system, four (4) High Mobility Multipurpose 24

Wheeled Vehicles (HMMWVs) (M1151 configuration), two (2) Medium Tactical Vehicle Replacements 25

(MK-23 configuration), Student Stations with integrated radio communication and Joint Capabilities 26

Release (JCR) software and Blue Force Tracker (BFT) hardware, image and sound generation systems, 27 and an internal communication network linking the six student stations with the IOS and linking two CCS 28 systems. The CCS is composed of Commercial Item hardware and software. 29

The CCS systems are housed in both modular trailers and real property Government facilities. The CCS 30 systems in Camp Pendleton, Camp Lejeune, Twentynine Palms, and MCB Hawaii are located in modular 31 trailers. The CCS systems in Camp Hansen, Point Mugu, and Gulfport are located in Government real 32 property facilities. 33

Figure 1 – Combat Convoy Simulator (CCS) 36

APPLICABLE DOCUMENTS 237

The most recent revision of the referenced document throughout the contract shall be used unless 38 otherwise specified. In the event of conflict between the applicable documents and this document, this 39 document shall take precedence. However, nothing in this document supersedes applicable laws and 40 regulations unless a specific exemption has been obtained. 41

Government Documents 2.142

21 CFR 1040 Code of Federal Regulations, Title 21, Part 1040, Performance Standards for Light-Emitting Products

29 CFR 1910.120 Hazardous Waste Operations and Emergency Response 29 CFR 1910.147 Control of Hazardous Energy (Lockout/Tagout) 29 CFR 1910.301 Design Safety Standards for Electrical Systems 29 CFR 1910.302 through 399 OSHA Electrical Safety 29 CFR 1926.65 Hazardous Waste Operations and Emergency Response DON NERP Department of Navy (DoN) Environmental Restoration Program Manual DODD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure DoDI 4650.01 Policy and Procedures for Management and Use of the

Electromagnetic Spectrum DoDI 5000.02 Operation of the Defense Acquisition System

STUDENT STATION

• Image Generation System

• Weapons System

• Communication System

• Sound Generation System

• Ownship Vehicle System

• Projection System

• Display System

• C-IED System

• C2 System

• Vehicle Chassis

• Binoculars

INSTRUCTOR/OPERATOR STATION

• Semi-Automated Forces System

• Exercise Control System

• AAR System

• Image Generation System

• C2 System

• Communication System

MTVR & HMMWV

• Actual vehicle cab

• Instrumented to simulate vehicle dynamics

NETWORK

• Connectivity between

IOS and SS

• Gateway connectivity to external systems

DoDI 5000.74 Defense Acquisition of Services DODI 8510.01 Risk Management Framework (RMF) for DOD Information Technology DODM 5200.01 Volume 4 DoD Information Security Program: Controlled Unclassified Information

(CUI)

EM385-1-1 USACE Safety and Health Requirements Manual FED-STD-313 Material Safety Data, Transportation Data and Disposal Data for

Hazardous Materials Furnished to Government Activities MCO 5104.1C Navy Laser Hazards Control Program MCO 5215.17D Marine Corps Technical Publication Management MIL-HDBK-217 Reliability Prediction of Electronic Equipment MIL-HDBK-419 Grounding, Bonding and Shielding for Electronic Equipment and

Facilities, Volume 1 of 2 Basic Theory MIL-HDBK-470 Designing and Developing Maintainable Products and Systems MIL-HDBK-502A Product Support Analysis MIL-HDBK-61A Configuration Management Guidance MIL-HDBK-781 Reliability Test Methods, Plans, and Environments for Engineering

Development, Qualification, and Production MIL-M-82376B Manuals, Technical: Operation and Maintenance Instruction for MIL-PRF-29612 Training Data Products MIL-PRF-32216 Evaluation of Commercial Off-The-Shelf (COTS) Manuals and

Preparation of Supplemental Data MIL-STD-129 Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property MIL-STD-1366 DoD Interface Standard for Transportability Criteria MIL-STD-2073-1 DoD Standard Practice for Military Packaging MIL-STD-3018 Parts Management MIL-STD-31000A Technical Data Packages MIL-STD-461G Requirements for the Control of Electromagnetic Interference

Characteristics of subsystems and equipment MIL-STD-464C Electromagnetic Environmental Effects Requirements for Systems MIL-STD-881 Work Breakdown Structures for Defense Materiel Items MIL-STD-882 Standard Practice for System Safety MIL-STD-961 Defense and Program-Unique Specifications Format and Content NAVMC 1553.1 Systems Approach to Training (SAT) User’s Guide NAVSEAINST 9310.1 Naval Lithium Battery Safety Program OPNAVINST 5100.23G Navy Safety and Occupational Health Program Manual SECNAVINST 5000.2 Department Of The Navy Implementation And Operation of the

Defense Acquisition System and the Joint Capabilities Integration and Development System

TM S9310-AQ-SAF-010 Technical Manual for Batteries, Navy Lithium Safety Program Responsibilities and Procedures, dated 15 July 2010

USMC MAG MARCORSYSCOM Acquisition Guidebook

Non-Government Documents 2.243

ANSI Z535.1-2006 Safety Color Code ANSI Z535.2-2002 Environmental and Facility Safety Signs ANSI Z535.3-2002 Criteria for Safety Symbols ANSI Z535.4-2002 Product Safety Signs and Labels ANSI Z535.5-2002 Accident Prevention Tags

ANSI/ASQC-Q9000-2000 Quality Management and Quality Assurance Standards: Guidelines for Selection and Use

ANSI/ASQC-Q9001-2000 Quality Systems – Model for Quality Assurance in Design/Development, Production, Installation, and Servicing

ANSI/ASQC-Q9004-2000 Quality Management and Quality System Elements ASME Y14.100 Engineering Drawing Practices ASME Y14.34 Associated Lists ASTM D3951 Standard Practice for Commercial Packaging ASTM D4169-01e1 Standard Practice for Performance Testing of Shipping Containers and Systems EIA RS-471 Symbol and Label for Electrostatic Sensitive Devices EIA-649 National Consensus Standard for Configuration Management GEIA-STD-0007 Logistics Product Data IEEE 1278.1-2012 Distributed Interactive Simulation – Application Protocols IEEE 1278.2-2015 Distributed Interactive Simulation – Communication Services and

Profiles IEEE 1516-2010 High Level Architecture – Framework and Rules IEEE 1516.1-2010 High Level Architecture – Federate Interface Specification IEEE 1516.2-2010 High Level Architecture – Object Model Template (OMT)

Specification IEEE 1516.4-2007 High Level Architecture – Recommended Practice for Verification, Validation, and Accreditation of a Federation – An Overlay to the High Level Architecture Federation Development and Execution Process

IEEE 200-1975 Standard Reference Designations for Electrical and Revision 1988 Electronics Parts and Equipment (ANSI/IEEE Y32.16)

NFPA 70 National Electrical Code SD-19 Life Cycle Cost Savings Through Parts Management SD-22 Diminishing Manufacturing Sources and Material Shortages

(DMSMS) Guidebook SD-84 Data Standard for the Preparation and Submission of Provisioning

Technical Documentation SISO-STD-013-2014 Standard for Common Image Generator Interface (CIGI)

REQUIREMENTS 344

The contractor shall perform a modernization modification of the hardware and software of the in-service 45

USMC Combat Convoy Simulator (CCS) in accordance with the CCS System Performance Specification 46 and requirements established in this SOW. The contractor shall design, integrate, produce, install, prepare 47 and deliver documentation defined in the CDRLs, provide logistics support and planning, provide technical 48 support, and deliver training materials and technical manuals with the modified CCS systems. 49

The contractor shall provide all materials, equipment, tools, personnel, and facilities necessary to 50 manufacture, integrate, fabricate, produce, install, and deliver the modified systems. 51

The contractor shall commence installation of the first CCS suite 15 months after contract award. 52

Installation shall commence once all required Systems Engineering Technical Review (SETR) events as 53 detailed in this document and the CCS Test and Evaluation Master Plan (TEMP) have been completed 54 successfully. 55

The installation and Government acceptance of the modified USMC CCS systems shall be accomplished 56 in such a way that one CCS suite is taken offline, modified, and reinstated at a time. Installation and 57

Government acceptance of each suite shall not exceed one month. As such, Installation and Government 58 acceptance of all seven USMC CCS suites shall not exceed 7 months (from the first day of installation of 59 the first CCS suite, to the day of Government acceptance of the seventh CCS suite). 60

Section F of the contract contains the required site-specific order sequence for modification, installation, 61 and delivery of modified systems. 62

Changes to the modification, installation, and delivery schedule and/or order may be directed by the 63

Contracting Officer at no additional cost to the Government prior to the Test Readiness Review (TRR). 64

Changes to the installation and delivery sequence may be directed by the Contracting Officer at no 65 additional cost to the Government prior to the Test Readiness Review (TRR). 66

The modification program shall encompass the replacement of: 67

• Hardware components, to include: 68 o Projectors 69 o Workstations 70 o Servers 71 o Monitors 72 o Network Devices 73 o Simulated Weapons System 74

Simulated weapons chassis may be reused 75 Existing air compression system shall be used 76 o Closed-circuit television 77 o Sound generation system 78 o FBCB2 stations to include MTVR student stations 79 o Radios on HMMWV vehicle platforms 80

• Software components, to include: 81 o Image generator 82 o Simulation 83 o Obsolete operating systems (OS) with USMC Approved operating systems identified in 84 the DON Application and Database Management System (DADMS) 85 o Simulated Weapons System Software 86 o FBCB2 software and hardware with new Joint Battle Command – Platform (JBC-P) 87 software and Mounted Family of Computer Systems (MFoCS) hardware 88

• Terrain databases and visual models to a format compatible with new image generator and 89 simulation software 90

The contractor shall provide, install, and mount new simulated radios on MTVR student station vehicles. 92 The contractor shall provide and install the adjustable military vertical lift platform on all vehicle student 94 stations. 95 The contractor shall provide and install two simulated M-22 Binoculars per CCS suite. 97 The contractor shall dispose of all obsolete and legacy equipment not utilized as part of the modification of 99 the CCS systems. 100

Program and Data Management 3.1101

3.1.1 Program Management 102

The contractor shall organize, coordinate, and control all program activities to ensure compliance with the 103 contract requirements and the timely delivery of the required products and services. The contractor shall 104 provide the necessary personnel, program management, engineering, logistics, administrative support, 105 materials, services, reports, equipment, and administrative support for contractor personnel, and facilities 106 in the performance of this contract. The contractor is an independent contractor. 107

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective 108 management of the resources assigned to meet the requirement. The contractor shall maintain continuity 109 between the support operations at various Contiguous United States (CONUS) and Outside CONUS 110

(OCONUS) training locations as well as the contractor's corporate offices. 111

The contractor shall monitor the progress and quality of all work performed. The contractor shall be 112 prepared to explain the reasoning, assumptions, and methodologies used in the performance of this 113 contract. 114

The contractor shall establish processes and assign appropriate resources to effectively meet the 115 requirements. The contractor shall respond to Government requests for contractual actions in a timely 116 fashion. The contractor shall have a single point of contact between the Government and contractor 117 personnel. The contractor shall maintain the currency of their employees by providing initial and refresher 118 training or certification(s) necessary to satisfy contract requirements. 119

The contractor shall develop and maintain a Program Management Plan in accordance with CDRL B001. 120

The contractor shall submit a Contractor’s Progress, Status and Management Report in accordance with 121

CDRL B002. 122

CDRL B001 – Program Management Plan 123

CDRL B002 – Contractor’s Progress, Status and Management Report 124

3.1.2 Common Access Cards (CAC) 125

The COR will identify and approve those contractor employees performing on this contract that require 126

CACs in order to perform their job function. In accordance with Headquarters, United States Marine 127

Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel 128 must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor 129 employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security 130

Investigation (PSI.) Prior to authorizing a CAC, the employee’s Joint Personnel Adjudication System 131

(JPAS) record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has 132 been submitted and accepted (opened). The minimum acceptable investigation is a T-1 or a National 133

Agency Check with Written Inquiries (NACI). If a contractor employee’s open investigation closes and is 134 not favorably adjudicated, the CAC must be immediately retrieved and revoked. 135

The contractor Facility Security Officers (FSOs) are responsible for notifying the MARCORSYSCOM 136

Security Director if any contractor performing on this contract receives an unfavorable adjudication after 137 being issued a CAC. The contractor FSO must also notify the MARCORSYSCOM Security Director of 138 any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning 139 any contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted. 140

Each CAC is issued with a “ctr@usmc.mil” e-mail account that the individual contractor is responsible to 141 keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any 142 unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to 143 their .com e-mail account. If the ctr.usmc.mil e-mail account is not kept active, the G-6 will deactivate the 144 account and CAC will lose its functionality. 145

CACs will only be issued to those contractors supporting this contract that have been authorized by the 146

COR. The COR will only authorize CACs for those contractors that meet current Homeland Security 147

Presidential Directive – 12 (HSPD-12) criteria and have a definitive requirement. 148

If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost 149 their eligibility to perform on MARCORSYSCOM contracts. CACs are not issued for convenience. 150

3.1.3 Travel 151

CONUS and OCONUS travel may be required. All travel requirements (including plans, agenda, itinerary, 152 or dates) shall be pre-approved by the Government (subject to local policy procedures), and is on a strictly 153 cost reimbursable basis. Trip reports are due to the COR in accordance with CDRL B003. 154

CDRL B003 – Trip/Travel Report 155

3.1.4 Data Management 156

The contractor shall develop, utilize, and maintain a secure, web-based, Commercial Item, Management 157

Information System (MIS) for the management of data under this contract. The MIS shall be capable of 158 collecting, producing, storing, and managing real-time operations, training, maintenance, supply, and 159 equipment inventory data and metrics. 160

The Government shall have user access to the MIS. The contractor shall be responsible for all the 161 hardware, software, and documentation necessary for the development, operation, and maintenance of 162 the MIS. 163

Any electronic databases or applications used to store, track, share, transmit or display information 164 pertaining to this contract shall be web-based and password restricted. 165

Government use of the MIS shall not require installation of client software on Government computer 166 systems. 167

The MIS shall, at a minimum: 168

• Be capable of recording and producing a real-time report of all maintenance actions in real-time 169 by CCS suite. The following maintenance data is required: 170 o Suite (i.e., CCS CPEN 1, CCS Hawaii, etc.) 171 o Type of maintenance being performed (corrective or preventative) 172 o Description of discrepancy 173 o Status of suite (i.e., degraded, deadline) and amount of time (in days) in status 174 o Configuration Items affected 175 o Description and history of corrective actions 176 o Task owner 177 o Repair parts (as required) and their shipping status (as applicable) 178 o Date and time stamp of all maintenance actions 179 o Service request history 180

• Be capable of producing real-time, automated Reliability, Availability, and Maintainability (RAM) 181 reports detailing the following metrics, per CCS suite, based on the CCS Nominal Mission Profile: 182 o Operational Availability (Ao) = (uptime)/(Uptime - Downtime) 183 o Mission Reliability R(t) = e^-λt where t = mission duration, λ = Failure Rate = Number of 184

Mission Essential Function Failures / Total Operating Hours 185 o Mean Time Between Operational Mission Failure = Total Operating Hours / Total Number 186 of Mission Essential Function Failures during Operating Period 187 o Mean Time Between Failure = Total Operating Hours / Total Number of Failures 188

Requiring Maintenance during Operating Period 189 o Mission Essential Function Failures = Number of Number of Mission Essential Function 190

Failures during Operating Period 191 o Non-Mission Essential Function Failures = Number of Number of Mission Essential 192

Function Failures during Operating Period 193 o Mean Time Between Maintenance = 1 / (λ + frequency of scheduled maintenance) 194 o Mean Time To Repair (mission essential) = Total Active Maintenance Time for Mission 195

Essential Failures / Number of Mission Essential Failures 196 o Mean Time To Repair (Non-Mission Essential) = Total Active Maintenance Time for Non-197

Mission Essential Failures / Number of Non-Mission Essential Failures 198

• Be capable of producing real-time, automated database transaction history report, by CCS suite 199 and location, detailing all MIS database transactions and the date and time of occurrence. 200

• Be capable of producing a user account report detailing active users, account inactivity, and 201 account privileges. 202

• Be capable of producing an MIS backup report detailing the date of backup performed, name(s) 203 and size(s) of files backed up, and the date of backup validation. 204

• Be capable of exporting real-time system data in comma separated values (CSV) by CCS suite. 205 The data shall include: 206 o System Description/Item nomenclature 207 o Serial Number 208 o Manufacturer Part Number 209 o Model Number 210 o Manufacture Year 211 o Manufacture Name 212 o CAGE Code 213 o Unique Item Identifier (UII), as applicable 214 o Validation Date of UII 215 o Validation Result (Pass/Fail) 216 o Verification Date of UII 217 o Verification Result (Pass/Fail) - Same 218 o Warranty Expiration Date, as applicable 219 o Quantity 220 o Dollar Amount 221 o Site Unit Identification Code (UIC) 222 o Location 223 o Sub-Location 224 o Condition Code 225 o Last Inventory Date/Time 226 o Acquisition Date 227 o Receipt Document Number 228 o Received By 229 o Local Receipts Date 230 o Original Placed in Service Date 231 o Material type, grade, and class, as applicable for laser components 232 o Report date and time 233

• Be capable of producing automated equipment accountability reports by CCS suite and location in 234 Adobe PDF format. 235

• Be capable of producing training and operations reports, by CCS suite, to include: 236 o Training Schedules (CCS system, location, unit name, date, start/end time, point of 237 contact) 238 o Return on Investment (ROI) Data IAW the CCS System Performance Specification. ROI 239 data shall be imported from each individual CCS suite and uploaded into the MIS no less 240 than monthly. 241

The contractor shall establish, maintain, and implement, as required, a data recovery process to ensure 242 data is not lost due to unanticipated occurrences. 243

The system shall include facilities for storage of all data developed or utilized for this contract, and shall 244 provide the Government with equal access to the data. The contractor shall ensure all data is centrally 245 available for Government review to ensure continuity of the system fabrication and supporting 246 documentation. 247

The MIS shall be compatible with the industry standard database format ISO/IEC 9075 (SQL) and 248

Microsoft Office version 2013 or greater. 249

The Government reserves the right to review all data associated with and developed for the CCS. 250

3.1.5 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) 251

The contractor shall manage the execution of the contract using an IMP and associated IMS as day-to-252 day execution tools and to periodically assess progress in meeting contract requirements. The IMP shall 253 be maintained and updated to reflect changes to the contract. The contractor shall report on contract 254 progress in accordance with the IMP at each technical review and other times at the Government’s 255 request and as detailed in this SOW. 256

The contractor shall revise the IMS, where necessary, to reflect the IMP. The contractor shall use it as a 257 day-to-day execution tool and to periodically assess progress in meeting contract requirements. The 258 contractor shall maintain and update the IMS to reflect changes to the contract or changes in the 259 contractor’s detailed execution activities or schedule. The IMS shall include the activities of the prime 260 contractor and all subcontractors. The contractor shall document all tasks and task dependencies, to 261 include all Government dependencies. 262

The IMS shall include a tiered scheduling system and depict the project’s critical path, all program 263 milestones, prerequisite events, conferences, reviews, data submittals, and deliveries required as part of 264 the contract. 265

Contract deliverables and subcontractor schedules shall be integrated into the contractor’s IMS. 266

CDRL B004 – Integrated Program Management Report (IPMR) - Integrated Master Plan (IMP) and 267

Integrated Master Schedule (IMS) 268

3.1.6 Contract Work Breakdown Structure (CWBS) 269

The contractor shall develop, maintain, and periodically update a CWBS that defines the work structures 270 required to successfully deliver all product-oriented (e.g., hardware, software, services, data, etc.) 271 requirements set forth in this document and the CCS System Performance Specification. The CWBS shall 272 serve as the framework for planning, schedule, and performance. 273

CDRL B005 – Contract Work Breakdown Structure 274

3.1.7 Assignment of Responsibility and Authority 275

The contractor shall identify the organizational elements responsible for the conduct of the activities 276 delineated in this SOW. Responsibilities shall be assigned and clear lines of authority defined for 277 determining and controlling the resources necessary to satisfy each element of this SOW. 278

CDRL B002 - Contractor’s Progress, Status and Management Report 279

3.1.8 Identification of Contractor Employees 280

The contractor shall provide to the COR a roster of contractor personnel assigned to the contract IAW 281

CDRL B006 Contractor’s Personnel Roster. 282

CDRL B006 - Contractor’s Personnel Roster 283

3.1.9 Government Furnished Property (GFP) 284

The contractor shall reference and adhere to the processes and steps detailed in the Government 285

Furnished Property (GFP) Process Flowchart provided as a contract attachment. 286

3.1.10 Joint Battle Command – Platform (JBC-P) and Mounted Family of Computer Systems 287 (MFoCS) 288

The contractor shall integrate the JBC-P software and MFoCS hardware into each Student Station and the 289

Instructor/Operator Station. The contractor shall establish network connectivity between the Student 290

Station vehicles and the Instructor/Operator Station in each CCS suite and configure the JBC-P software 291 and MFoCS hardware to allow data communication between the Student Stations and the 292

Instructor/Operation Station. 293

The contractor shall translate BLUFOR position/location information (PLI) within the synthetic environment 294 into a Variable Message Format (VMF) K05.01 Position Report message that can be interpreted by the 295

JBC-P software. 296

In order to gain access to the JBC-P software, the contractor shall be required to submit a Non-Disclosure 297

Agreement (NDA) to the US Army Communications and Electronics Command (CECOM), Program 298

Executive Office Command Control Communications-Tactical (PEO C3T), Joint Battle Command-Platform 299

(PM JBC-P) program. A current copy of the NDA form is included in Section J of the contract. The NDA 300 shall be submitted by the contractor as part of the contract proposal. 301

The contractor shall provide a means for the instructor/operator to configure the frequency of the VMF 302 messages sent from the synthetic environment. 303

Risk Management 3.2304

The contractor shall establish and maintain a risk management program to identify risks related to the 305 project. The contractor shall identify and track all risks and corrective actions required to mitigate the risks. 306

The contractor shall define and implement a risk assessment methodology that includes not only an 307 understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic 308 reassessment of these impacts on risk areas. The contractor shall update, maintain, and execute program 309 metrics to monitor issues and to determine the likelihood of risks occurring. The contractor shall ensure 310 that the risk management process is utilized to manage risks across all facets of the contract, including 311 subcontractor activities. 312

CDRL B007 – Contractor’s Risk Management Plan 313

CDRL B008 – Risk Management Status Report 314

Meetings, Formal Reviews, Conferences, and Audits 3.3315

The contractor shall plan, host, attend, coordinate, support and conduct the meetings, formal reviews, 316 conferences, and audits (hereinafter called "reviews"). The reviews shall be conducted at Government 317 and contractor facilities. Reviews requiring demonstration and/or examination of equipment shall be 318 conducted at the contractor's facility. All such reviews shall be included in the IMS and may be held 319 concurrently with the Government’s approval. The contractor shall prepare agendas and conference 320 presentation materials, and provide minutes and reports following each review. The Government reserves 321 the right to cancel any review or to require any review to be scheduled at critical points during the period 322 of performance. Action item documentation, assignment of responsibility for completion and due dates 323 shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, 324 and estimated completion dates shall be included with the minutes IAW the CDRL. 325

CDRL B009 – Conference Agenda 326

CDRL B00A – Conference Minutes 327

CDRL B00B – Presentation Material 328

3.3.1 Post Award Conference (PAC) 329

A Post Award Conference (PAC) shall be conducted between the Government and the contractor within 330 fifteen business days after contract (DAC) award. The purpose of the PAC is for the contractor to review 331 and demonstrate to the Government the management procedures, provide progress assessments, review 332 of technical and other specialty area status, and to establish schedule dates for near term critical 333 meetings/actions. The contractor shall present management, key personnel, and program implementation 334 processes. The details of the PAC will be finalized at time of award, but the Contractor can expect it to 335 occur in Orlando, Florida no-later-than within fifteen business days after contract (DAC). Participation via 336 teleconference or VTC is allowed. 337

3.3.1.1 PAC Entrance Criteria: 338

• Government Acceptance of agenda and presentation materials 339

• Contractor submission of the following CDRLs for Government review: 340

CDRL B001 – Program Management Plan 341

CDRL B004 – Integrated Program Management Report (IPMR) - Integrated Master Plan (IMP) and 342

Integrated Master Schedule (IMS)CDRL B005 – Contract Work Breakdown Structure 343

CDRL B009 – Conference Agenda 344

CDRL B00B – Presentation Material 345

CDRL B007 – Contractor’s Risk Management Plan 346

CDRL B008 – Risk Management Status Report 347

CDRL A001 – Supplier's Configuration Management Plan 348

CDRL A002 – System Safety Program Plan (SSPP) 349

CDRL A003 – Systems Engineering Management Plan (SEMP) 350

CDRL A004 – Test and Evaluation Program Plan (TEPP) 351

CDRL D001 – Parts Management Plan 352

CDRL D002 - Item Unique Identification (IUID) Marking Plan and IUID Marking Activity, Validation, and 353 Verification Report 354

CDRL D003 - Maintenance Support Plan 355

3.3.1.2 PAC Agenda 356

At a minimum, the agenda shall cover the following topics: 357

• Introduction and Overview 358

• Discussion and clarification of requirements 359

• Program Management Plan 360

• Risk Management Plan (RMP) and Risk Management Status Report 361

• Quality Control Program 362

• Integrated Master Plan (IMP), Integrated Master Schedule (IMS), critical path, milestones, and 363 deliverables 364

• Contractor Work Breakdown Structure (CWBS) 365

• Metrics collection processes, analysis, and reporting procedures 366

• Configuration Management 367

• System Safety Program Plan (SSPP) 368

• Contractor Site Surveys 369

• Subcontractor Management and organizational structure 370

• Integrated Logistic Support (ILS) Overview 371 o Training Program 373 o Provisioning Plan 374

Long lead item identification and status 375 Spares 376 Special tools and test equipment 377 o Obsolescence management 378 o Warranty 379 o PHS&T 380 o Inventory (Hardware/Software) Control 381 o Item Unique Identification (IUID) Marking 382 o Disposal of legacy CCS components 383

• Technical manuals 384

• O&M manuals 385

• Scenarios 386

• Management Information System (MIS) 387

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

Additional topics may be added to the agenda if required. 390

3.3.1.3 PAC Exit Criteria 391

• Evidence of contractor submission for an active and appropriate Federal Fire Arms License (FFL) 392 IAW the U.S. Department of Justice Bureau of Alcohol, Tobacco, Firearms and Explosives 393 Regulations. Historically, a Class 9 Dealer in Destructive Devices Federal Fire Arms License 394 (FFL) has met requirements comparable to the CCS. However, the contractor is responsible for 395 complying with all applicable laws and regulations regarding interaction with weapon systems tied 396 to this requirement. 397

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

• Government acceptance of PAC CDRLs 400

• Contractor submittal and Government acceptance of the PAC minutes. 401

CDRL B00A – Conference Minutes 402

3.3.2 Integrated Product Team (IPT) Meetings 403

The contractor shall participate in IPT meetings as required by the Government to discuss current contract 404 status. The contractor shall prepare all meeting agendas, presentation materials, and minutes. 405

The below IPTs shall be established as part of the contract: 406

• Program Management IPT 407

• System Engineer and Integration (SE&I) IPT 408

• Test and Evaluation (T&E) IPT 409

• Production and Deployment IPT 410

• Logistics IPT 411

CDRL B009 – Conference Agenda 412

CDRL B00A – Conference Minutes 413

CDRL B00B – Presentation Material 414

3.3.3 In-Process Reviews (IPR) 415

In Process Reviews (IPR) shall be held on a quarterly basis or as needed basis, at a date and location 416 mutually agreed upon. The Government reserves the right to cancel any review or to require any review to 417 be scheduled during the period of performance. The contractor’s progress, management, engineering, 418 integrated logistics support, administrative, assurance of compliance with contract requirements, program 419 status, funding, problem identification and resolutions shall be agenda items. Actual versus expected 420 performance of each area shall be addressed. The contractor shall prepare presentation materials 421 providing an overview of all agenda items. 422

CDRL B009 – Conference Agenda 423

CDRL B00A – Conference Minutes 424

CDRL B00B – Presentation Material 425

Systems Engineering 3.4426

The contractor shall establish and maintain an effective systems engineering program throughout the 427 design, testing and production processes. The systems engineering program shall be documented in a 428

System Engineering Management Plan (SEMP) aligned with the CCS Modification Program Systems 429

Engineering Plan (SEP). 430

CDRL A003 - System Engineering Management Plan (SEMP) 431

3.4.1 Technical Reviews 432

Technical reviews shall be conducted in accordance with MCSCO 5400.5, Naval Systems Engineering 433

Policy and the Marine Corps Systems Command Systems Engineering Technical Review (SETR) 434

Handbook, SIAT-HDBK-001 dated 06 August 2014. Details for each SETR event is described in the 435 following sections; 436

3.4.1.1 System Requirements Review / System Functional Review (SRR/SFR) 437

The purpose of the SRR/SFR is to confirm that the system requirements are sufficiently well understood to 438 permit the contractor to develop the initial system/sub-system level requirements. The SRR/SFR 439 determines the direction and progress of the systems engineering effort and the degree of convergence 440 upon a balanced and complete functional baseline. 441

3.4.1.1.1 SRR/SFR Entrance Criteria 442

The contractor shall be responsible for meeting the below entrance criteria prior to the start of the 443

SRR/SFR. 444

• Contractor completion of initial analysis of the Government provided CCS System Performance 445 Specification. 446

• Requests for Action (RFAs) from the PAC are closed 447

• Submission of the following CDRLs for Government review: 448

CDRL B009 – Conference Agenda 449

CDRL B00B – Presentation Material 450

CDRL A005 –System/Subsystem Specification (SSS) 451

CDRL A006 – Interface Requirements Specifications (IRS) 452

CDRL A007 – Technical Report – Study/Services (Requirements Traceability Verification Matrix (RTVM)) 453

CDRL A01B – FMECA Report 454

3.4.1.1.2 SRR/SFR Agenda 455

At a minimum, the agenda shall cover the following topics: 456

• Contractor organizational structure, key personnel, roles/responsibilities 457

• Systems requirements decomposition and associated verification methods 458

• Requirements traceability to the CCS System Performance Specification 459

• Technical and programmatic risks/opportunities 460

• Configuration management process 461

• Baseline management 462

• Hardware and software configuration items (CI) identification 463

• Reliability and Maintainability Program 464 o Reliability prediction updates 465 o Testability 466

• Integrated Master Plan (IMP), Integrated Master Schedule (IMS) and critical path 467

• Safety/critical requirements 468

• Site unique requirements 469

• Testbed status 470

• Technical Data Package (TDP) 471

Additional topics may be added to the agenda if required. 473

3.4.1.1.3 SRR/SFR Exit Criteria 474

• The system requirements, as defined in the system performance specification, satisfy the CPD 475

• System functional requirements decomposition defined in the SSS and IRS with associated 476 verification methods 477

• RMF requirements decomposed 478

• RTVM updated 479

• Technical and schedule risks identified and appropriate mitigation approaches and burn-down 480 plan identified 481

• Testbed plan identified to support subsystem FCA, SIQ, and RMF A&A 482

• Government acceptance of all SRR/SFR CDRL submissions including meeting minutes. 483

• Requests for Action (RFAs) from the SRR/SFR are closed 484

CDRL B00A – Conference Minutes 485

3.4.1.2 Critical Design Review (CDR) 486

The purpose of the CDR is to assess the system final design as captured in a Technical Data Package 487

(TDP) and other documentation for each proposed configuration item to be used in the system (product 488 baseline). 489

The CDR also ensures the system under review can proceed into production, demonstration, and test and 490 can meet the stated performance requirements within schedule constraints 491

3.4.1.2.1 CDR Entrance Criteria 492

The contractor shall be responsible for meeting the below entrance criteria prior to the start of CDR. 493

• Hardware and software list identified for inclusion in RMF package 494

• Requests for Action (RFAs) from the previous SETR event are closed 495

• Successful attainment of an active and appropriate Federal Fire Arms License (FFL) IAW the U.S. 496

Department of Justice Bureau of Alcohol, Tobacco, Firearms and Explosives Regulations. 497 Historically, a Class 9 Dealer in Destructive Devices Federal Fire Arms License (FFL) has met 498 requirements comparable to the CCS. However, the contractor is responsible for complying with 499 all applicable laws and regulations regarding interaction with weapon systems tied to this 500 requirement. 501

• Submission of the following CDRLs for Government review: 502

CDRL B009 – Conference Agenda 503

CDRL B00B – Presentation Material 504

CDRL A008 – System/Subsystem Design Description (SSDD) 505

CDRL A009 – Database Design Description (DBDD) 506

CDRL A00A – Interface Design Description (IDD) 507

CDRL A00B – Product Drawings and Models and Associated Lists 508

CDRL A00C – Trainer Facility Report (TFR) 509

CDRL A01B – FMECA Report 510

CDRL D004 – Parts List 511

CDRL D005 – Provisioning Parts List (PPLs) 512

CDRL D006 – Long Lead Time Items List (LLTIL) 513

CDRL D007 – Proposed Spare Parts List and Spares Cataloging Data Sheets 514

CDRL D008 – Special Equipment Tools and Test Equipment List 515

CDRL D009 – Legacy Component Reuse and Disposal List 516

CDRL F001 – Modeling and Simulation (M&S) Verification and Validation (V&V) Plan 517

3.4.1.2.2 CDR Agenda 518

At a minimum, the agenda shall cover the following topics: 519

• System Architecture 520 o Software Architecture 521 o Hardware Architecture 522 o Integration design 523

• CI internal and external…