MUET_Phase 2_SOW_v1_20240530 (Baseline) Draft WM.pdf

STATEMENT OF WORK (SOW) 1

FOR THE 2

MULTI USE EGRESS TRAINER PROGRAM 3

(MUET) 4

VERSION 1 5

30 May 2024 9

Program Manager for Training Systems (PM TRASYS) 10

Marine Corps Systems Command (MARCORSYSCOM) 11

12211 Science Drive 12

Orlando, Florida 32826-3224 13

APPROVED BY: DATE: 16

Tom Sikora 17

Program Manager 18

DISTRIBUTION STATEMENT D - DISTRIBUTION AUTHORIZED TO DOD AND U.S. DOD CONTRACTORS 23 ONLY (ADMINISTRATIVE OR OPERATIONAL USE), DETERMINED ON 27 Mar 2024. OTHER REQUESTS FOR 24 THIS DOCUMENT SHALL BE REFERRED TO COMMANDING OFFICER, NAVAL AIR WARFARE CENTER, 25

TRAINING SYSTEMS DIVISION, PJM, 12211 SCIENCE DRIVE, ORLANDO, FL 32826-3224. 26

DESTRUCTION NOTICE - FOR UNCLASSIFIED, LIMITED DISTRIBUTION DOCUMENTS, DESTROY BY ANY 27 METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT. 28

TABLE OF CONTENTS 30

TABLE OF CONTENTS .............................................................................................................................. 2 32

FIGURES ..................................................................................................................................................... 3 33

1. BACKGROUND .................................................................................................................................. 4 34

1.1. Scope ........................................................................................................................................... 4 35

1.2. UET System Description ............................................................................................................. 4 36

1.2.1. MUET Description .............................................................................................................. 7 37

2. APPLICABLE DOCUMENTS ............................................................................................................. 7 38

2.1. Government Documents .............................................................................................................. 7 39

2.1. Non-Government Documents ...................................................................................................... 8 40

3. REQUIREMENTS ................................................................................................................................ 9 41

3.1. General Requirements ................................................................................................................. 9 42

3.2. Program and Data Management ................................................................................................ 10 43

3.2.1. Program Management ...................................................................................................... 10 44

3.2.2. Integrated Master Schedule (IMS) .................................................................................. 10 45

3.2.3. Risk Management ............................................................................................................. 11 46

3.2.4. Configuration Management (CM) ................................................................................... 11 47

3.2.5. Configuration Change Management ............................................................................... 11 48

3.2.6. Configuration Item (CI) ................................................................................................... 12 49

3.2.7. Baseline Management ....................................................................................................... 12 50

3.2.8. Configuration Control ...................................................................................................... 13 51

3.3. Conference(s), Meetings, Reviews, and Audits ......................................................................... 14 52

3.3.1. Post Award Conference .................................................................................................... 15 53

3.3.2. Integrated Product Team Meetings ................................................................................. 16 54

3.3.3. In-Process Reviews ............................................................................................................ 16 55

3.3.4. Technical Reviews ............................................................................................................. 18 56

3.3.5. Audits ................................................................................................................................. 20 57

3.4. Technical Data Package (TDP) ................................................................................................. 24 58

3.4.1. Interface Control Document (ICD) ................................................................................. 24 59

3.4.2. Requirements Traceability Verification Matrix (RTVM) ............................................. 24 60

3.4.3. Engineering Drawings ...................................................................................................... 24 61

3.5. Test and Evaluation (T&E) ........................................................................................................ 25 62

3.5.1. Responsibility for Tests .................................................................................................... 25 63

3.5.2. Test Authority ................................................................................................................... 26 64

3.5.3. Test Events ......................................................................................................................... 26 65

3.5.4. Test Plans and Test Procedures ....................................................................................... 28 66

3.5.5. Changes During FAT and SAT Testing .......................................................................... 29 67

3.5.6. Changes After FAT and SAT Testing ............................................................................. 29 68

3.5.7. Test Deficiency Reporting System ................................................................................... 29 69

3.6. Integrated Product Support (IPS) .............................................................................................. 29 70

3.6.1. Maintenance Planning ...................................................................................................... 30 71

3.6.2. Supply Support .................................................................................................................. 30 72

3.6.3. Provisioning ....................................................................................................................... 31 73

3.6.4. Manuals and Associated Supplemental Data ................................................................. 33 74

3.7. Packaging, Handling, Storage, and Transportation (PHS&T) ................................................... 34 75

3.8. Power ......................................................................................................................................... 34 76

3.8.1. Lithium Batteries .............................................................................................................. 34 77

3.9. UET Facilities ............................................................................................................................ 35 78

3.9.1. Facility Power .................................................................................................................... 35 79

4. SPECIAL REQUIREMENTS............................................................................................................. 35 80

4.1. Environment, Safety, and Occupational Health ........................................................................ 35 81

4.1.1. Accidents and Mishaps ..................................................................................................... 35 82

4.1.2. System Safety ..................................................................................................................... 35 83

4.1.3. Security Requirements ..................................................................................................... 36 84

4.1.4. Travel ................................................................................................................................. 37 85

4.1.5. Government Furnished Property (GFP) ......................................................................... 37 86

5. APPENDIX A CDRL LIST ................................................................................................................. 39 87

6. APPENDIX B ACRONYM LIST ....................................................................................................... 40 88

FIGURES 91

SECTION PAGE NO. 92

Figure 1-1: Underwater Egress Trainer (MAET and SVET, respectfully) ................................................... 5 94

Figure 1-2: Rotating Ring ............................................................................................................................. 6 95

Figure 1-3: Leveling Block ........................................................................................................................... 6 96

Statement of Work (SOW) 99

For Delivery Order (DO) 146 100

Product Line Management (PLM) 101

MUET SYSTEM TECHNICAL REFRESH 102

1. BACKGROUND 103

1.1. Scope 104

The government has requirements to perform a technical refresh of MULTI-USE EGRESS TRAINER(s) 105

(MUET) that includes fabrication of parts, installation and site acceptance testing for the following 106 locations: 107

• Camp Pendleton, CA. 108

• Del Mar, CA. 109

• Camp Blaz, Guam 110

• Camp LeJune, NC 111

• Okinawa, JP 112

• Honolulu, HA 113

This technical refresh will allow egress training for the Amphibious Combat Vehicle (ACV) and Joint 114

Light Tactical Vehicle (JLTV) platforms by replacing the current existing system designed for obsolete 115

Marine Corps vehicles and transportation platforms. 116

The technical refresh will include: 117

• Contractor procurement, fabrication, and integration of required technical refresh materials using 118 a government provided Technical Data Package (TDP). 119

• Packaging, Delivery and Installation to USMC UET Training Facilities 120

• Site Acceptance Testing (SAT) 121

• Contractor provided Training 122

• Delivery of all documentation and schematics to assemble, build, operate and maintain delivered 123 unit and documentation of procurement parts, material along with quantity and vendor source. 124

Important Technical Refresh Milestones will include: 125

• Post Award Conference (PAC) 126

• In Process Reviews (IPR)s 127

• Facilities Acceptance Test (FAT) Test Readiness Review (TRR) 128

• FAT 129

• Functional Configuration Audit (FCA) / Physical Configuration Audit (PCA) #1/ System 130

Verification Review (SVR) 131

• IPRT #4 / Independent Verification and Validation (IV&V) 132

• Site Acceptance Test (SAT) TRR 133

• SAT / PCA #2 134

Note: Some milestones (e.g. PAC) will be performed/achieved once, and some milestones (e.g. SAT) will 135 be performed/achieved for each delivery. 136

Products delivered as part of this technical refresh shall be capable of interfacing with additional systems 137 that makeup the UET. Interfacing systems descriptions and requirements are detail in Sec. 1.2 of this 138

SOW. 139

1.2. UET System Description 140

The purpose of the Underwater Egress Trainer (UET) is to enhance operator and passenger survivability, 141 regardless of the platform submitting to causal factors resulting in a rollover or submersion incident. The 142

UET provides a coordinated physical environment, in which the mental processes taught during the 143 academic portion of the training curriculum, can be applied, and practiced. UET training serves to make 144 an otherwise "unfamiliar” situation "familiar”, should it be encountered during emergency situations. The 145 current in-use UET training systems include the MAET and the SVET shown in Figure 1-1 146

Figure 1-1: Underwater Egress Trainer (MAET and SVET, respectfully) 148

The SVET and the MAET have the same modular core and rotational capabilities. The SVET is 149 dedicated to amphibious and ground vehicle replication and is being phased out since it replicates 150 vehicles that are obsolete and/or no longer in operation in the Fleet Marine Force (FMF). The ACV and 151 the JLTV are the new FMF vehicles currently in operation or planned for delivery and have created a new 152 and emerging requirement necessitating the need for the MUET in order to ensure realistic and 153 comprehensive training. 154

The current UET lifting system is the Model 12000 Cross Gantry Hoist (XGH) designed for use with the 155

MAET and the SVET. The SmartJib is a second UET lifting system planned for two new upcoming 156 locations. It is the Government’s intention for the MUET to comply with the rated lift capacity of the 157 existing XGH and planned SmartJib lifting systems and interoperate with existing XGH and SmartJib 158 control subsystems. The XGH is a cross gantry hoisting system and features dual lifting mechanisms, 159 integrated remote air brake system, user settable variable ditching speeds, advanced ditching monitoring, 160 effects sequencing, and control, as well as a pneumatically operated Redundant Retraction System (RRS) 161 to mitigate the risk of power failures during critical (submerged) periods of the UET training cycle. 162

Current XGHs are installed in both indoor and outdoor settings, integral to the facility, or mounted on 163 outdoor gantries. The SmartJib has all the same features and similar components as the XGH but is in a 164 jib crane configuration. 165

The MUET will interface with both the XGH and SmartJib lifting systems, training tank (pool), normal 166 pneumatic system (braking), and emergency braking system (RRS). The lifting capabilities of the XGH 167 and the SmartJib is 10,000 lbf when lifting training personnel. The MUET will be capable of being 168 raised out of a training tank by both the XGH and the SmartJib RRS system. The MUET will interface 169 and be controlled by both the pneumatic system (braking) and emergency braking system (RRS). The 170 braking system shall have a minimum operating pressure of 80 psi and a maximum of 120 psi. The RRS 171 system is pneumatic consisting of 300 (cf) with a minimum pressure of 2000 psi and a maximum of 2500 172 psi. 173

Figure 1-2: Rotating Ring 175

A circular rotation ring shown in Figure 1-2 shall fit around the center of the MUET frame on which a 176 rotation trolley rides. This rotation trolley contains the UET airbrake system and a means for attaching 177 the MUET to the lifting system’s connection point, the shackle connection to the leveling block shown in 178

Figure 1-3 that is on all XGH and SmartJib systems. The leveling block contains 3 key load bearing 179 components – the Main Support Pin (and the shackle) along with two Fall Arrest Strops (1 on each side). 180

Figure 1-3: Leveling Block 183

1.2.1. MUET Description 186

Much like the SVET, the MUET's purpose is to replicate a catastrophic, water born event in order to 187 provide a realistic egress-training package. The MUET shall replicate, as closely as possible, the form 188 and fit of the ACV and JLTV, specifically the ACV- Personnel variant and the JLTV-Combat Tactical 189

Vehicle variant. The MUET system shall be modular and capable of being reconfigured, to support the 190

ACV and JLTV ground and amphibious vehicles. The MUET shall interoperate with the existing XGH 191

12000 and SmartJib crane and hoist systems including the XGH12000 and SmartJib interfaces. The MUET 192 shall comply with the maximum lift capacity of the XGH 12000 and SmartJib. The MUET shall also be 193 capable of operating in existing UET pool facilities. 194

2. APPLICABLE DOCUMENTS 195

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

2.1. Government Documents 200

Document Designation Document Title

29 CFR 1910 Section 120 Occupational Safety and Health Standards

29 CFR 1926 Section 65 Safety and Health Regulations for Construction

Contract N61340-20-D-0025 Delivery Order (DO) #63

DFARS 252.211-7003 Defense Federal Acquisition Regulation Supplement (DFARS) Item

Unique Identification and Valuation

DON NERP Department of Navy (DoN) Environmental Restoration Program

Manual

DODM 5200.01 Volume 4 DoD Information Security Program: Controlled Unclassified

Information (CUI)

EM385-1-1 USACE Safety and Health Requirements Manual

HSPD-12 Homeland Security Presidential Directive 12: Policy for a Common

Identification Standard for Federal Employees and Contractors

MCO 4410.28 Marine Corps Order: Item Unique Identification (IUID) of Ground

Equipment

MCSCO 5400.5 Designation of Marine Corps Installations East-Marine Corps Base

Camp Lejune Regional Command Information Officer (CIO), Roles and

Responsibilities

MIL-HDBK-61B Configuration Management Guidance

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

MIL-STD-3018 Parts Management

MIL-STD-31000B Technical Data Packages

MIL-STD-882E Standard Practice for System Safety

MUET Performance United States Marine Corps Performance Specification for the Multi-

Specification Use Egress trainers (MUET)

Naval Systems Engineering

Policy

Memorandum of Understanding for an Introduction and Promulgation of the Naval Systems Engineering Guide

NAVFAC P-307 Weight Handling Program Management

OPNAVINST 5100.23G Navy Safety and Occupational Health Program Manual

OPNAVINST Form 5102.1 Navy and Marine Corps Mishap and Safety Investigation, Reporting, And Record Keeping Manual

OSHA Form 301 Occupational Safety and Health Administration's (OSHA) Injury and

Illness Incident Report

OSHA Near Miss Report Occupational Safety and Health Administration's (OSHA) Near-Miss

Incident Report Form

2.1. Non-Government Documents 201

Table 1 Non Government Documents 202

Document Designation Document Title

ASME Y14.100 Engineering Drawing Practices

ASME Y14.34 Associated Lists

ASTM D3951 Standard Practice for Commercial Packaging

IEEE 15288.2-2014 Institute of Electrical and Electronic Engineers Standard For

Technical Reviews And Audits On Defense Programs

SAE-GEIA-STD-0007 Logistics Product Data Handbook

3. REQUIREMENTS 205

The contractor shall perform technical refresh of the MUET family of systems to provide egress training 206 functionality for the Amphibious Combat Vehicle (ACV) and Joint Light Tactical Vehicle (JLTV) at the 207 following locations: 208

• Camp Pendleton, CA. 209

• Del Mar, CA. 210

• Camp Blaz, Guam 211

• Camp LeJune, NC 212

• Okinawa, JP 213

• Honolulu, HA 214

The contractor shall use the technical documentation provided as Government Furnished Information 215

(GFI) as the technical baseline for refresh. This technical baseline includes technical refresh 216 requirements, design, performance specifications and other technical documents used to describe the 217

MUET. This technical baseline includes requirements listed in “MUET-2-Perfomance Specification (P-218

Spec) 11_MAR_2024.pdf”. 219

This Technical Refresh shall include: 220

• Contractor procurement, fabrication and integration of required MUET upgrade Materials 221

• Packaging, Delivery and Installation to a USMC UET Training Facility locations 222

• Contractor provided Training 223 o Operator/Maintainer Required Training 224 o Instructor/Safety Diver Required Training 225

• Documentation 226

Program milestones and events shall include unless otherwise agreed to by government: 227

• PAC 228

• IPRs 229

• FAT TRR 230

• FAT 231

• FCA / PCA #1/ SVR 232

• IPR #4 / IV&V 233

• SAT TRR 234

• SAT / PCA #2 235

Program milestones and events (e.g. SAT) may be duplicated for each location. 236

3.1. General Requirements 237

The contractor shall technically refresh the MUET for the locations listed in Section 3 Requirements. 238

The MUET technical refreshes shall be capable of replicating a catastrophic, water born event to provide 239 realistic egress training. 240

The MUET shall replicate and be reconfigurable to, as closely as possible, the form and fit of the ACV, 241 and JLTV vehicles. 242

The MUET shall replicate the requirements and design detailed in the government provided technical 243 baseline. 244

The MUET shall interface with the existing MUET Training System Infrastructure without modification 245 to the existing infrastructure. 246

The MUET shall interface with both the XGH and SmartJib lifting systems, training tank (pool), normal 247 pneumatic system (braking), and emergency braking system (RRS). 248

The MUET shall comply to the maximum lift capacity of the XGH 12000 and SmartJib lifting systems. 249

The MUET shall be capable of being raised out of a training tank by both the XGH and the SmartJib RRS 250 system. 251

The MUET shall interface and be controlled by both the pneumatic system (braking) and emergency 252 braking system (RRS). The braking system shall have a minimum operating pressure of 80 psi and a 253 maximum of 120 psi. The RRS system is pneumatic consisting of 300 (cf) with a minimum pressure of 254

2000 psi and a maximum of 2500 psi. 255

The MUET shall capable of being operated at the existing UET pool facilities. 256

3.2. Program and Data Management 257

3.2.1. Program Management 258

The contractor shall provide the overall management and administrative effort necessary to ensure the 259 requirements of this contract are accomplished. The contractor shall identify risks in a timely manner, 260 such that corrective action plans can be developed by the contractor and approved by the Government, 261 prior to risk realization. 262

The contractor shall support weekly meetings to address the following areas with the Government: 263

1. Problems and proposed solutions 264

2. Identify risks and implement mitigation plans 265

3. Fielding timelines and production schedules 266

4. Plan of next month activities 267

5. Schedule and/or performance risk and risk mitigation measures 268

6. Logistics topics 269

7. Engineering topics 270

8. Facilities Engineering topics 271

The Government reserves the right to change the frequency of these meetings throughout the duration of 272 the contract, at any point. 273

The Contractor's Risk Management Status Report (CPMSR) shall include an executive summary, in a 274 format that is consistent with best commercial practices and addresses the overall status of the program. 275

Within the body, identify contract progress for the reporting period, contract financial and schedule status 276 to include critical path status, data from the contractor’s Integrated Master Schedule (IMS), completed 277 and upcoming travel, technical risks, risk mitigations, management issues, and meeting minutes for any 278 meetings accomplished during the reporting period. Highlights of any actions requested by the 279

Government, and when those actions are required to preclude programmatic or technical problems, shall 280 be included in the executive summary and body. The Government may increase the frequency and 281 content of the reports based on contractor performance. 282

CDRL B002 – Contractor's Risk Management Status Report (CPMSR) 283

3.2.2. Integrated Master Schedule (IMS) 284

The contractor shall develop, document, implement, control, and maintain an Integrated Master Schedule 285

(IMS) that presents the contractor’s and subcontractors’ schedules to meet the requirements of the 286 contract and the DO. The contractor shall develop and document a tiered scheduling system showing the 287 program milestones and prerequisite events, conferences, reviews, data submittals, and deliveries. The 288 contractor shall construct the IMS to ensure that the program milestones are met and to ensure that 289 deliveries meet the requirements of the contract. The IMS shall include all critical paths required to meet 290 the requirement of this DO. 291

The contractor shall revise the IMS, where necessary, to reflect contract changes. The contractor shall use 292 the IMS as a day-to-day execution tool and to periodically assess progress in meeting program 293 requirements. 294

The IMS shall be delivered to the government as a subsection or attachment to the CPMSR. 295

3.2.3. Risk Management 296

The contractor shall establish and maintain a risk management program to identify risks related to the 297 project. The contractor shall identify and track all risks and corrective actions required to mitigate the 298 risks. The contractor shall define and implement a risk assessment methodology that includes not only an 299 understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic 300 reassessment of these impacts on risk areas. 301

The contractor shall update, maintain, and execute program metrics to monitor issues and to determine the 302 likelihood of risks occurring. The contractor shall ensure that the risk management process is utilized to 303 manage risks across all facets of the contract, including subcontractor activities. 304

Risk shall be identified and reported to the government as a subsection or attachment to the CPMSR. 305

3.2.4. Configuration Management (CM) 306

Configuration Management (CM) is a technical process within systems engineering, which enables 307 technical control of program activities, system design, work products, requirements, interfaces, data, and 308 configurations; and changes to these, affecting cost, performance, and schedule. 309

The contractor shall provide, implement, and adhere to the Configuration Management Plan delivered in 310

DO #63 which outlined the contractor's strategy for identifying, creating, recording, reporting, changing, 311 controlling, and managing all Configuration Items (CIs) unless otherwise approved by the government. 312

CIs shall encompass all documentation, hardware, software, and firmware, along with versions, statuses, 313 relationships, configurations, and baselines. 314

The contractor shall establish and implement configuration control and approval processes required to 315 change a CI’s attributes to re-baseline the CIs, and to report the CI completion. 316

The contractor shall use an automated internal CM process to monitor, update, and control all 317 configuration documentation, physical media, and physical parts. 318

3.2.5. Configuration Change Management 319

The contractor shall establish a systematic and measurable change for the CM process to manage product 320 configuration changes and variances. The contractor shall effect changes to the baseline requirements via 321 an Engineering Change Proposal (ECP), and only after the ECP has been approved, using the change 322 process. The contractor shall: 323

1. Document and uniquely identify each change. 324

2. Classify requested changes to aid in determining the levels of review and approval. 325

3. Clearly and completely document request for change. 326

4. Consider the technical, support, schedule, and cost impacts of a requested change before making 327 a judgment to approve the change for implementation and incorporation in the system and its 328 documentation. 329

5. Determine potential effects of a change and coordinate impacts with the impacted areas of 330 responsibility. 331

6. Determine the effectivity for each change and identify which units of the system are to be 332 changed, the point of production break-in, and which units will be included in a retrofit. 333

7. Verify implementation of a change to ensure consistency between the system, its documentation, 334 and its support elements. 335

8. Document variances, when authorized by the appropriate level of authority. 336

3.2.6. Configuration Item (CI) 337

In coordination with the Government, the contractor shall develop methods to uniquely identify CIs and 338 associated documentation, such as specifications, drawings, manuals, plans, procedures, instructions, 339 software media, and other configuration-related documents. 340

3.2.7. Baseline Management 341

The Government will maintain Configuration Management for all baselines (Allocated, Functional and 342

Product Baselines). Contractor initiated changes shall be submitted via the Engineering Change Proposal 343

Proposal (ECP) or Request for Variance (RFV) processes. The Government Configuration Control Board 344

(CCB) will give approval of any changes via the ECP and/ or the RFV process. 345

3.2.7.1. Allocated Baseline (ABL) 346

Documentation that designates the CIs making up a system and then allocates the system function and 347 performance requirements across the CIs. It includes all functional and interface characteristics that are 348 allocated from those of a higher-level CI or from the system itself, derived requirements, interface 349 requirements with other CIs, design restraints, and the verification required to demonstrate the 350 achievement of specified functional and interface characteristics. The performance of each CI in the ABL 351 is described in its item performance specification. 352

3.2.7.2. Functional Baseline (FBL) 353

The approved functional requirements for a product or system describing the functional, performance, 354 interoperability, interface, and verification requirements established at a specific point in time and 355 documented in the functional configuration documentation. The MUET System Performance 356

Specification (SPS) and the System/Subsystem Specification (SSS) establishes the functional baseline. 357

The functional baseline shall be established after successful completion of the Requirement Review with 358 all associated documentation. Government approval via the ECP process shall be required prior to 359 making changes to the functional baseline. 360

3.2.7.3. Product Baseline (PBL) 361

The Product Baseline is the approved documentation that completely describes the functional 362 and physical characteristics of the CI and any required joint and combined operations 363 interoperability characteristics of a CI ((including a comprehensive summary of the other 364 environment(s) and allied interfacing CIs or systems and equipment). It consists of the Product 365

Configuration Document (PCD), which is the current approved technical documentation 366 describing the configuration of a CI during the production and deployment and operational 367 support phases of its life cycle. The PBL prescribes: 368

1. All necessary physical or form, fit, and function characteristics of a CI. 370

2. The selected functional characteristics designated for production acceptance testing. 371

3. The production acceptance test requirement. 372

4. All Allocated Configuration documentation to the item, so that if the item were to be re-produced, 373 the performance requirements for the item would also be included. 374

The PBL documentation includes the complete set of released and approved engineering design 375 documents, such as the engineering models, engineering drawings, and associated lists for 376 hardware, interface, and database design documents. The current configuration of the documents 377 that are considered the developmental configuration. The Product Baseline may include the 2-D 378 or 3-D engineering model of the hardware product. 379

3.2.8. Configuration Control 380

The contractor shall implement configuration control methods and procedures, which maintain the 381 integrity and traceability of an established baseline. Changes to established baselines shall only be made 382 after government approval of ECPs and Request for Variance (RFV) via the Configuration Control Board 383

(CCB) process. Sufficient supporting data to evaluate the proposed change, such as drawings, 384 supplemental drawings, sketches, specifications, manufacturer's datasheets, or software modification shall 385 be submitted with ECPs and RFVs. Changes shall be identified to the affected assembly serial number, or 386 if not part of an assembly, to the affected equipment serial number. The contractor’s configuration 387 control process shall be available for government review. The contractor shall submit all configuration 388 control documentation in a digital format specified by the Government. 389

3.2.8.1. Engineering Change Proposals (ECP) 390

ECPs shall be submitted by the contractor, and shall be limited to those that are necessary, or offer 391 significant benefit to the Government. MIL-HDBK-61 provides guidance concerning the classification of 392

ECPs. Class I ECPs shall be submitted by the contractor to the Technical Point of Contact (TPOC) when 393 changes are required to: 394

1. Correct deficiencies 395

2. Changes to an established Functional, Allocated, or Product Baseline interface or interoperability 396 requirements 397

3. Make a significant and measurable effectiveness change in the operational capabilities or logistics 398 supportability of the system 399

4. Effect substantial life cycle costs/savings 400

5. Prevent slippage in an approved production schedule 401

Class II ECPs shall be submitted by the contractor to the COR for approval for those engineering changes 402 that do not impact any of the factors listed above. As a minimum, ECPs shall contain the following 403 information: 404

1. Date prepared 405

2. Originator 406

3. ECP classification 407

4. ECP number 408

5. Reason/need for change 409

6. System designation (nomenclature, model, P/N) 410

7. Name of part (or lowest assembly) affected to include part numbers 411

8. Baselines affected (to include drawings, specifications, CAGE, revision level, etc.) 412

9. Title of change 413

10. Description of change 414

11. Effect on interfaces (interchangeability and interoperability) 415

12. Total costs/savings with supporting information 416

13. Retrofit information 417

14. Ozone depleting substances 418

15. Impact on any engineering disciplines (such as quality, environmental, safety, health, reliability, 419 maintainability, etc.) 420

16. Justification for change 421

17. Priority of change 422

18. Impacts to any logistics support elements (such as software, manuals, spares, tools, etc.) being 423 utilized by government personnel in support of the product 424

19. Alternatives evaluated or considered 425

No changes in scope or contract price shall be authorized without prior Program Contracting Officer 426

(PCO) approval via a modification to the contract. 427

CDRL A010 –Engineering Change Proposal (ECP) 428

3.2.8.2. Requests for Variance 429

The contractor shall process RFVs from current approved configuration documentation. Authorized 430 deviations are a temporary departure from the requirements and do not constitute a change in an approved 431 baseline. The Contracting Officer shall only approve any authorized deviation in writing. Where it is 432 determined that a change should be permanent, the contractor shall process an ECP. MIL-HDBK-61 433 provides guidance concerning the classification of RFVs. As a minimum, the RFV shall contain the 434 following information: 435

1. Date prepared 436

2. Originator 437

3. RFV classification (critical, major, or minor) 438

4. Designation for deviation (model/type, CAGE code, system designation, and deviation number) 439

5. Class of deviation 440

6. Part number affected 441

7. Cost/price data 442

8. Effectiveness 443

9. Description of deviation 444

10. Need for deviation 445

11. Effect on delivery schedule 446

12. Recommended corrective action 447

13. Alternatives evaluated 448

CDRL A011 – Request for Variance (RFV) 449

3.3. Conference(s), Meetings, Reviews, and Audits 450

Due to the complexity and high risk of the installation and integration effort the government shall require 451 a Conference(s), IPT meetings IPRs, Technical Reviews and Audits prior to the contractor shipping to site 452 to ensure that these custom-made materials fit the form, fit and function of the requirements. The 453

Conference(s), IPT meetings IPRs, Technical Reviews and Audits hereinafter are called "reviews". The 454 contractor shall plan, host, attend, coordinate, support, and conduct the reviews at government or 455 contractor facilities. The specific locations, dates, and duration of the reviews shall be as specified in the 456 contract schedule, or as mutually agreed upon. Reviews shall be conducted in a method agreed to by the 457

Government (i.e., at either the contractor or government facilities, videoconference, or via 458 teleconference). All face-to-face meetings shall be held at the contractor's facility unless the Government 459 and the contractor mutually agree upon an alternate location. 460

All such reviews shall be included in the IMS and may be held concurrently with the Government’s 461 approval. The contractor shall prepare agendas, presentation materials, and provide minutes and reports 462 following each review. Agendas, presentation materials, and minutes for IPT meetings shall be at the 463 government’s request only. 464

Action item closure shall require contractor submission and government approval. The contractor shall 465 make available facilities for government only meetings, during all conferences and reviews at the 466 contractor’s facility. Subcontractors shall attend meetings and reviews, when required to address key 467 elements. The Government reserves the right to cancel any review or to require any review to be 468 scheduled at critical points during the Period of Performance (PoP). Action item documentation, 469 assignment of responsibility for completion, and due dates shall be determined prior to adjournment of all 470 reviews. 471

A summary of all action items, responsible parties, and estimated completion dates shall be included with 472 the minutes IAW the CDRL. 473

CDRL B005 – Conference and Meeting Agenda 474

CDRL B006 – Conference and Meeting Minutes 475

CDRL B007 – Conference and Meeting Presentations 476

3.3.1. Post Award Conference 477

The first conference shall be the Post Award Conference (PAC) and shall occur at a mutually agreed upon 478 date within 30-calendar days after contract award. The purpose of the conference shall be to establish the 479 framework of the contractor and Government interaction during the performance period of the contract. 480

This meeting shall include the presentation and discussion of information and data relating to: 481

1. Introductions and contract overview 482

2. Action item documentation and reporting 483

3. Updated team contact list (names, phone numbers, and email addresses) 484

4. Presentation of a draft IMS 485

5. Identification of all critical paths within the IMS 486

6. Staffing plan 487

7. Program specific risk management 488

8. Site survey planning and timeline 489

9. Logistics 490

a. Long lead item identification and status 491

b. Spares 492

c. Special tools and test equipment 493

d. Obsolescence management 494

e. Warranty 495

f. Packing, Handling, Shipping & Transportation 496

g. Inventory (hardware/software) control 497

h. Item Unique Identification (IUID) Marking 498

i. Technical manuals, Operation and Maintenance (O&M) and COTS manual 499

10. Systems Engineering (SE) overview 500

a. Technical interchange meetings 501

b. Safety critical elements 502

c. Program specific Configuration Management (CM) overview (to include data 503 management) 504

d. Verification of Technical Baseline, and Critical Design Documentation. NOTE: Many of 505 the CDRLs required for the Entrance Criteria have been established as part of the 506

Technical Baseline from DO #63. 507

11. Contract management (i.e., invoicing, billing) Additional topics may be added to the agenda at 508 the Government’s request. 509

3.3.1.1. PAC Entrance Criteria 510

1. Government acceptance of agenda and presentation materials 511

2. Contractor submission and acceptance of the following CDRLs for government review: 512

CDRL B005 - Conference and Meeting Agenda 513

CDRL B007 - Conference and Meeting Presentations 514

3.3.1.2. PAC Exit Criteria 515

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 516 discussed, and documented 517

2. Contractor submittal and government acceptance of the PAC minutes 518

CDRL B006 – Conference and Meeting Minutes 519

3.3.2. Integrated Product Team Meetings 520

The contractor shall participate in Integrated Product Team (IPT) meetings, weekly or as required by the 521

Government, to discuss current contract status. The contractor shall prepare all meeting agendas, 522 presentation materials, and minutes at the government’s request. 523

A Program Management IPT shall be established as part of the contract. The IPT may include topics that 524 include all aspects as it relates to the schedule including production, deployment, and logistics. 525

3.3.3. In-Process Reviews 526

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

3.3.3.1. IPR #1 534

3.3.3.1.1. IPR #1 Entrance Criteria 535

1. Program execution and process control 536

2. Risk assessment 537

3. Program life-cycle budget and schedules 538

4. Contractor submission and acceptance of the following CDRLs for government review: 539

CDRL A003 – Interface Control Document (ICD) 540

CDRL A013 - Engineering Drawing Tree 541

CDRL B005 - Conference and Meeting Agenda 542

CDRL B007 - Conference and Meeting Presentations 543

CDRL C002 - OSHA Plan - Site Specific Health and Safety Plan 544

CDRL D001 - Maintenance Support Plan 545

3.3.3.1.2. IPR #1 Exit Criteria 546

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 547 discussed, and documented 548

2. Contractor submittal and government acceptance of the PAC minutes 549

CDRL B006 – Conference and Meeting Minutes 550

3.3.3.2. IPR #2 551

3.3.3.2.1. IPR #2 Entrance Criteria 552

1. Program execution and process control 553

2. Risk assessment 554

3. Program life-cycle budget and schedules 555

4. Contractor submission and acceptance of the following CDRLs for government review: 556

CDRL A008 - Configuration Audit Plan 557

CDRL A014 - Test Plan 558

CDRL B005 - Conference and Meeting Agenda 561

CDRL B007 - Conference and Meeting Presentations 562

CDRL D002 - Logistics Product Data 563

3.3.3.2.2. IPR #2 Exit Criteria 564

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 565 discussed, and documented 566

2. Contractor submittal and government acceptance of the PAC minutes 567

CDRL B006 – Conference and Meeting Minutes 568

3.3.3.3. IPR #3 569

3.3.3.3.1. IPR #3 Entrance Criteria 570

1. Program execution and process control 571

2. Risk assessment 572

3. Program life-cycle budget and schedules 573

4. Contractor submission and acceptance of the following CDRLs for government review: 574

CDRL A005 - Product Drawings and Models and Associated Lists (PDAL) 576

CDRL A012 - Commercial Drawings 577

CDRL B006 – Conference and Meeting Minutes 578

CDRL C003 - Safety Assessment Report 579

CDRL E001 - Operations and Maintenance Manuals 580

CDRL E002 - COTS Manual and Associated Supplemental Data 581

3.3.3.3.2. IPR #3 Exit Criteria 582

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 583 discussed, and documented 584

2. Contractor submittal and government acceptance of the PAC minutes 585

CDRL B006 – Conference and Meeting Minutes 586

3.3.3.4. IPR #4 588

The government anticipates the IPR #4 occurring after FCA/PCA#1/SVR and prior to the first delivery 589

SAT TRR. 590

3.3.3.4.1. IPR #4 Entrance Criteria 591

1. Program execution and process control 592

2. Risk assessment 593

3. Program life-cycle budget and schedules 594

4. Contractor submission and acceptance of the following CDRLs for government review: 595

CDRL B005 - Conference and Meeting Agenda 596

CDRL B007 - Conference and Meeting Presentations 597

3.3.3.4.2. IPR #4 Exit Criteria 598

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 599 discussed, and documented 600

2. Contractor submittal and government acceptance of the PAC minutes 601

CDRL B006 – Conference and Meeting Minutes 602

3.3.3.1.IPR #5 – PoP 603

After first article delivery additional IPRs shall occur quarterly as needed to monitor the progress of 604 follow deliveries. 605

3.3.3.1.1. IPR #5- PoP Entrance Criteria 606

1. Program execution and process control 607

2. Risk assessment 608

3. Program life-cycle budget and schedules 609

4. Contractor submission and acceptance of the following CDRLs for government review: 610

CDRL B005 - Conference and Meeting Agenda 611

CDRL B007 - Conference and Meeting Presentations 612

3.3.3.1.2. IPR #5 – PoP Exit Criteria 613

1. Government concurrence that all required PAC agenda items have been satisfactorily presented, 614 discussed, and documented 615

2. Contractor submittal and government acceptance of the PAC minutes 616

CDRL B006 – Conference and Meeting Minutes 617

3.3.4. Technical Reviews 618

To reduce the high risk of interoperability and integration issues the government has requirements to 619 procure and review technical documentation that supports all phases of the MUET technical refresh. To 620 support this the government has a requirement to perform a series of technical reviews to ensure the 621 contractor fully understands the scope and risks of the requirements involved and that the government 622 understands the documentation being received. 623

Technical reviews shall be conducted IAW Marine Corps Systems Command Order (MCSCO) 5400.5, 624

Naval Systems Engineering Policy, and the Institute of Electrical and Electronic Engineers (IEEE) 625

Standard 15288.2-2014. Details for each Systems Engineering Technical Review (SETR) event is 626 described in the following sections. 627

3.3.4.1. Test Readiness Reviews 628

Test Readiness Reviews (TRR) shall be conducted to assess test objectives, test methods and procedures, 629 test scope, safety, readiness for Government and contractor development test and evaluation, and whether 630 test resources have been properly identified and obtained. TRRs shall be held prior to any formal testing 631 for the record, when all applicable documentation for the system elements under test are sufficiently 632 complete and that all planning for personnel, test facilities, logistics and support equipment is sufficiently 633 robust to support a successful test. 634

At a minimum TRRs shall be held for FAT and SAT events. Note: With government approval some 635

TRRs may be waived after first article delivery. 636

3.3.4.1.1. Test Readiness Review Entry Criteria 637

Entry criteria for the review(s) shall consist of: 638

1. The Government acceptance for each TRR technical review products: 639

a. System technical documentation 640

i. The requirements to be verified by the test event include all approved changes. 641

ii. The configuration of the system or system element(s) under test is clearly 642 defined. 643

iii. Any design changes made to the system element(s) under test since PAC will not 644 adversely affect the formal test event. 645

iv. The system elements under test are under configuration control by the CM 646 organization and the configuration of each hardware and software element of the 647 system element(s) under test is documented. 648

v. No catastrophic or critical problems or deficiencies are open for the system 649 element(s) under test, where the problem criticality levels are as defined in the 650 program’s system safety policy or plan. 651

vi. The approved test plan with changes incorporated is robust enough to ensure the 652 full verification of all requirements to be verified by the test event. 653

vii. The test plan is consistent with the required verification methods and levels for 654 the requirements planned for verification by the test event. 655

viii. The test procedures are consistent with the required verification methods and 656 levels. 657

ix. Bi-directional traceability that is correct, complete, and consistent is provided 658 between the requirements to be verified by the formal test event and the test 659 procedures and test cases in which the requirements will be verified. 660

x. System-level tests stress the system within the intended mission environment(s). 661

a. Test environment 662

i. The test environment, including all hardware, software, emulators, and 663 simulators is sufficiently robust to adequately verify the requirements to be 664 verified. 665

ii. The test environment has the required components to support verification of 666 system security requirements. 667

iii. Sufficient validation has occurred prior to the planned test event to ensure that 668 the test environment will correctly perform the functions necessary to support the 669 test event. 670

a. Program execution and process control 671

iv. Personnel roles and responsibilities are documented, clear, and concise both for 672 the Government and contractor, including test witnessing requirements, and are 673 agreed to by the stakeholders. 674

v. Processes to be followed during test execution are defined and documented and 675 will result in a controlled and disciplined test execution. 676

vi. Appropriate security test facilities, test equipment, schedules, and personnel are 677 adequate and available to support the planned test event. 678

vii. All problems or deficiencies encountered during testing are appropriately 679 documented. 680

viii. The test log faithfully documents the execution of the test, including test start, 681 test end, interruptions, and anomalies. 682

b. Risk assessment 683

i. Technical risks are identified, and mitigation plans are in place. 684

a. Program life-cycle budget and schedules 685

i. Test schedules…