Attachment_J.3_PWS_TASK_ORDER_0002.pdf

M67854-17-R-7823

09/27/2017

Attachment J.3

Supporting Arms Virtual Trainer (SAVT)

Modifications

Performance Work Statement (PWS)

Task Order 2

08/25/2017 i

Record of Changes

Date Revision Reason for Change Entered by:

ii

Supporting Arms Virtual Trainer (SAVT) Modifications

Performance Work Statement (PWS)

1 Introduction

1.1 Mission

1.2 Background

1.3 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Business Relations

2.3 Contract Administration and Management

2.4 Subcontract Management

2.5 Data Management

2.5.1 Contractor’s Technical Proposal

2.5.2 Schedules

2.6 Facilities

2.7 Location and Hours of Work

2.8 Travel / Temporary Duty (TDY)

2.9 Plan, Host, Attend, Coordinate, Support and Conduct Meetings, Formal Reviews, Conferences, and Audits

2.9.1 Post Award Conference

2.9.2 In Process Review

2.9.3 Task Order Kickoff Meeting

2.10 Documents

2.10.1 Government Documents

2.10.2 Non-Government Documents

2.11 Government Furnished Property (GFP)

3 Performance Requirements

3.1 Contractor Logistics Support (CLS)

3.1.1 Provide Operation and Maintenance support of the SAVT System

3.1.1.1 Operational Readiness

3.1.1.2 Scenario Generation

3.1.1.3 Scenario Initialization and Generation

iii

3.1.1.4 After Action Review (AAR)

3.1.1.5 Training Scenario Adjustments

3.1.1.6 Preventative and Corrective Maintenance

3.1.1.7 On-Line Organizational Maintenance

3.1.1.8 Scheduled Preventative Maintenance

3.1.1.9 Off-Line Organizational (Intermediate) Maintenance

3.1.1.10 Surge Operator Support

3.1.1.11 Trainer Utilization Reporting

3.1.1.12 Quarterly Inventory

3.1.1.13 Modular Facility Maintenance

3.1.1.14 SAVT Test Berth Relocation

3.2 SAVT Modifications

3.2.1 Systems Engineering

3.2.1.1 Software

3.2.1.2 Hardware

3.2.3 System Safety Tasks

3.2.4 System Test and Evaluation (T&E)

3.2.5 Configuration Management Process

3.2.6 Technical Data Package (TDP)

3.2.7 Cybersecurity

3.2.8 Packaging

3.2.9 System Documentation Update

4 Special Requirements

4.1 Security and Safety

4.1.1 Security

4.1.2 Safety

4.2 Performance Start Up

4.3 Transition

4.4 Applicable Directives

4.5 Quality

4.5.1 Quality Control

iv

4.5.2 Quality Assurance Surveillance Plan (QASP)

5 Deliverables

6 Period of Performance

Table of SAVT Modification CDRLs

Performance Work Statement (PWS) 1

Supporting Arms Virtual Trainer (SAVT) Modifications 2

1 Introduction 3

The Supporting Arms Virtual Trainer (SAVT) is an immersive training environment that 4 provides a full color, real image, and wide-angle Primary Display system. The Primary Display 5 supports both direct viewing and viewing via simulation of night vision devices. The SAVT 6 device provides simulated equipment to support combined arms training. The SAVT device 7 provides an operators console consisting of an Instructor Operator Station (IOS), a Computer 8

Generated Forces (CGF) Subsystem, and a Man-In-The-Loop Flight Simulation Subsystem. The 9

SAVT After Action Review (AAR) room provides a seating area for approximately 20-30 10 students suitable for briefing and debriefing the students, each site defined by Government 11 provided facility layout drawing. The SAVT AAR device provides two large screen projection 12 systems viewable from the briefing room seating area. The SAVT device provides the following 13 secondary components in the briefing room; an IOS, and a CGF Subsystem. The SAVT device 14 provides a Video Combiner Subsystem to control routing of computer displays from the 15 secondary components to the large screen projection systems. The SAVT secondary components 16 provide the capability to monitor an active mission-based training event and/or perform AAR of 17 performance data captured during a mission-based training event. The device provides a sound 18 system in the AAR room for monitoring voice communications and battlefield sounds. This PWS 19 defines the requirements for SAVT Modifications, to include general and special requirements 20 and deliverables, in order to maintain and expand the capabilities of the SAVT's at the SAVT 21 locations and the SAVT test berth system. The Government maintains the source code for all 22

SAVT products. 23

1.1 Mission 25

The SAVT system is a simulator with sufficient sophistication and fidelity to train personnel to 26 control supporting fire, both air and ground delivered, for simulation qualification and currency 27 certification. 28

1.2 Background 30

The SAVT system provides training for Joint Tactical Air Controller (JTACs), Forward Air 31

Controllers (FACs), and Forward Observers (FOs) in the employment of Supporting Arms (SAs) 32 and Close Air Support (CAS). The SAVT system provides a standardized method for training 33

Tactics, Techniques, and Procedures (TTPs) for: Naval Surface Fire (NSF), Tactical Air (TA), 34

Artillery, and Mortar support in joint expeditionary operations. The SAVT training device 35 provides two (2) training environments; an immersive training environment and an AAR. The 36

SAVT system provides a mission-based training environment for two (2) students training in the 37 application of combined arms. The SAVT device provides the following capabilities; a voice 38 recognition student interface, intelligent agents for ground and air assets, intelligent agent 39 communications via synthetic speech, an event-based AAR, and an event-based grading system. 40

The SAVT grading system is based on the identified Joint Mission Essential Task Lists 41

(JMETLs) and Training & Readiness (T&R) manuals. The SAVT device provides a High-Level 42

Architecture (HLA) network environment with the ability to operate standalone or future 43 interoperability with other HLA compliant training devices. 44

1.3 Scope 46

This PWS identifies the SAVT Modifications that shall be performed on the SAVT sites and the 47

SAVT test berth. These SAVT Modifications include development, fabrication, production, 48 testing, and installation of the Lensatic Compass, STIM box replacement, Windows/Red Hat 49

Operating System upgrade and cybersecurity updates. 50

2 General Requirements 52

2.1 Non-Personal Services 53

Not applicable. 54

2.2 Business Relations 56

The contractor shall organize, coordinate and control all program activities to ensure compliance 57 with the PWS requirements and the timely delivery of the required products and services. The 58 contractor shall provide the necessary program management, engineering, materials, services, 59 equipment, facilities, testing, technical data, logistics, manufacturing and clerical support for the 60 efforts described. The contractor shall monitor the progress of all work that is performed. The 61 contractor shall be prepared to explain the reason, assumptions and methodologies that are used 62 in developing particular conclusions and alternatives in accomplishment of any effort. The 63 contractor shall provide corrective action plans, proposal submittals, timely identification of 64 issues, and effective management of subcontractors. 65

2.3 Contract Administration and Management 67

The contractor shall establish processes and assign appropriate resources to effectively 68 administer the requirements set forth in this PWS. The contractor shall respond to Government 69 requests for contractual deliverables. The contractor shall have a single point of contact between 70 the Government and contractor personnel who are assigned to support the contract. The 71 contractor shall assign work efforts and maintain proper and accurate time keeping records of 72 personnel who are assigned to work on the effort. The contractor shall be responsible for 73 performance of the requirements as defined and shall institute appropriate management actions 74 relative to subcontractor performance. Contractor employee clothing and shoes shall conform to 75 safety regulations. The contractor shall ensure all contractor and subcontractor personnel are in 76 compliance with applicable base regulations regarding appearance, conduct, safety and security. 77

The contractor shall provide for employees during designated Government non-work days or 79 other periods where Government offices are closed due to weather or security conditions. The 80 contractor shall maintain the currency of their employees. The contractor shall make necessary 81 travel arrangements for employees. The contractor shall provide necessary infrastructure to 82 support contract tasks. 83

2.4 Subcontract Management 85

The contractor shall be responsible for any subcontract management necessary to integrate work 86 performed on this requirement and shall be responsible and accountable for subcontractor 87 performance on this PWS. The prime contractor shall manage work distribution to ensure there 88 are no Organizational Conflict of Interest (OCI) considerations. Contractors may add 89 subcontractors to their team after notification to the PCO. 90

2.5 Data Management 92

The contractor shall establish a single, centralized system for management of all data required 93 under this contract. The contractor, in developing information that will be furnished to the 94

Government, shall make the maximum use of existing data and provide maximum multiple use 95 of technical information. Any electronic databases or applications used to store, track, share, 96 transmit or display information pertaining to this contract shall be web-based. Government use of 97 any data management system shall not require installation of client software on Government 98 computer systems (with the exception of Internet Explorer and Microsoft Office). Specific data 99 management functions shall include schedule control for deliverables, maintenance of 100 deliverables, and approval of deliverable format, distribution and delivery of data products. The 101 system shall include facilities for storage of all data developed or utilized for this contract, and 102 shall provide equal access to data by the Government. The contractor shall ensure all data is 103 centrally available for Government review to ensure continuity of the system fabrication and 104 supporting documentation. The Government reserves the right to review all data associated with 105 and developed for the SAVT modifications. 106

2.5.1 Contractor’s Technical Proposal 108

The contractor's Technical Proposal, as negotiated and accepted by the Government, shall be 109 incorporated by reference into this Task Order. Information contained in the offeror's proposal 110 regarding organization, staffing, manning levels, and experience or education qualifications of 111 personnel that are to be utilized in performance of this contract shall also be incorporated into the 112 resultant contract. Any changes in these arrangements are to be submitted to the contracting 113 officer in advance for approval. 114

2.5.2 Schedules 116

The contractor shall maintain an accurate schedule of program events and recommended 117 program schedules, including review and evaluation techniques, which provide for the earliest 118 delivery schedule while at the same time satisfying all requirements in a cost effective manner. 119

The program schedule shall include all significant events, and a Program Planning Milestone 120

Chart shall depict major tasks and events from start to completion of the contract. The contractor 121 shall notify the Government in writing of any anticipated or projected work stoppages or delays 122 that will impact schedules. 123

2.6 Facilities 125

Not applicable. 126

2.7 Location and Hours of Work 128

Task Order 2 shall be performed at the contractor's location with Government and contractor 129 supplied equipment. 130

Accomplishment of the requirements contained in this PWS requires work at contractor, 132 subcontractor, Government, and SAVT facilities. Normal Government workdays are Monday 133 through Friday except US Federal Holidays. Workers typically work eight (8) hours per day, 40 134 hours per week. SAVT locations normal hours of operation are based on the training cycles. 135

SAVT Locations: 136

1. Marine Corps Base, Camp Pendleton, California (modular facility) 137

2. Marine Corps Air-Ground Combat Center, Twenty-Nine Palms, California (modular facility) 138

3. Marine Corps Base, Camp Lejeune, North Carolina (modular facility) 139

4. Marine Corps Base Kaneohe Bay, Hawaii (modular facility) 140

5. Marine Corps Base, Camp Hansen, Okinawa, Japan * 141

6. SAVT Test Berth, Current Location NAWC-TSD Orlando, FL. Vendor Location to be 142 determined 143

*The contractor shall follow the Status of Forces Agreement (SOFA) for Okinawa Japan. 144

2.8 Travel / Temporary Duty (TDY) 146

All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the 147

Government (subject to local policy procedures), and is on a strictly cost reimbursable basis in 148 accordance with the Joint Travel Regulations (JTR). Costs for travel shall be billed in accordance 149 with the regulatory implementation of Public Law 99-234 and FAR 31.205-46 Travel Costs 150

(subject to local policy & procedures; may reference FAR). 151

2.9 Plan, Host, Attend, Coordinate, Support and Conduct Meetings, Formal 153

Reviews, Conferences, and Audits 154

The contractor shall plan, host, attend, coordinate, support and conduct the meetings, formal 155 reviews, conferences, and audits (hereafter called "reviews"). The reviews shall be conducted 156 either at contractor facilities or via teleconference. Reviews requiring demonstration or 157 examination of equipment shall be conducted at the contractor's facility. All such reviews shall 158 be included in the program schedule and may be held concurrently with the Government's 159 approval. The contractor shall prepare agendas and conference presentation materials, and 160 provide meeting minutes and reports following each review. The Government reserves the right 161 to cancel any review or to require any review to be scheduled at critical points during the Period 162 of Performance (PoP). Action item documentation and assignment of responsibility for 163 completion and due dates shall be determined prior to adjournment of all reviews. During the 164 course of the above described events the contractor shall record action items and other pertinent 165 information discussed during the event and provide the minutes to the Government In 166

Accordance With (IAW) Contract Deliverable Requirements List (CDRL) B003, Conference 167

Minutes and CDRL B004 Conference Agenda, as appropriate. 168

2.9.1 Post Award Conference 170

Not applicable. 171

2.9.2 In Process Review 173

In Process Reviews (IPR), if ordered shall be held at a minimum quarterly or as needed, at a date 174 and location mutually agreed upon. The Government reserves the right to cancel any review or 175 to require any review to be scheduled during the period of performance. The contractor’s 176 progress, management, technical support services, integrated logistics support, administrative, 177 assurance of compliance with contract requirements, program status, funding, problem 178 identification and resolutions shall be agenda items. Actual versus expected performance of each 179 area shall be addressed. The contractor shall prepare agenda, presentation materials, and minutes. 180

The IPR agenda shall include review of the following: 181

Contractor’s progress to include, but not limited to, the status of the overall 182 program, including the training system design (hardware and software), Quality 183

Management System (QMS), Configuration Management (CM), Electromagnetic 184

Environmental Effects (E3), testing, and production 185

Management 186

Technical support services (if any) 187

Integrated logistics support program review 188

Administrative 189

Assurance of compliance with contract requirements 190

Program schedule status 191

Funding Status 192

Problem identification and resolution 193

Review of program risks 194

Review of updated Requirements Traceability Matrix (RTM). 195

Review of Cybersecurity 196

CDRL B003 Conference Minutes / DI-ADMIN-81250B 198

CDRL B004 Conference Agenda / DI-ADMN- 81249B 199

2.9.3 Task Order Kickoff Meeting 201

The contractor shall host a Kickoff within 5 days of the Task Order 2 award. The Kickoff 202 meeting shall include the presentation and discussion of information and data relating to: 203

a. Introduction 205

b. Discussion and clarification of Spec and PWS requirements 206

c. Identification of the critical paths within the IMS (CDRL B001) 207

d. CDRL delivery schedule and status 208

e. Program specific Risk Management Planning approach and processes 209

f. Program Cybersecurity Implementation Planning approach and processes 210

g. IPT structure, membership, and responsibilities 211

h. Action item reporting and status 212

i. Long lead time item identification and status 213

j. Updated team contact list (names, IPT memberships, phone numbers, and email 214 address) 215

k. Defense Reutilization Management Office (DRMO) activities. 216

Kickoff Entry Criteria 218

Entry criteria for the Kickoff shall consist of Government concurrence with the following: 219

a. Government Acceptance of agenda (CDRL B004) 220

b. Submission of the following CDRLs for Government review: 221

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 223

CDRL B004, Conference Agenda / DI-ADMN- 81249A 224

CDRL B005, Presentation Materials / DI-ADMN-81373 225

Kickoff Exit Criteria 227

Exit criteria for the Kickoff shall consist of Government concurrence with the following: 228

a. Required Kickoff topics have been satisfactorily presented, discussed, and 229 documented. 230

b. Critical path discussions are complete, accurate, and realistic. 231

c. IPT structure, membership, and responsibilities are satisfactorily defined, 232 documented, and implemented. 233

d. Kickoff minutes (CDRL B003) and presentation materials (CDRL B005) have been 234 submitted and accepted. 235

e. Action items have been assigned with suspense date for closure. 236

CDRL B003, Conference Minutes / DI-ADMIN-81250B 238

CDRL B005, Presentation Materials / DI-ADMN-81373 239

2.10 Documents 241

The following documents specified, form a part of this PWS to the extent specified herein or as 242 part of Task Order 2. The most recent revision of the referenced document at the time of 243 contract shall be used unless otherwise specified. In the event of conflict between the applicable 244 documents and this PWS, the PWS shall take precedence. Nothing in this document, however, 245 supersedes applicable laws and regulations unless a specific exemption has been obtained. 246

2.10.1 Government Documents 248

DODI 8510.01 Risk Management Framework (RMF) for DoD Information 249

Technology 250

FED-STD-313 Material Safety Data, Transportation Data and Disposal Data for 251

Hazardous Materials Furnished to Government Activities 252

MIL-STD-129 Military Marking for Shipment and Storage 253

MIL-STD-882E Standard Practice for System Safety 254

MIL-STD-2073-1 DoD Standard Practice for Military Packaging 255

MIL-HDBK-61A Configuration Management Guidance 256

MCSCO 5400.5 Naval Systems Engineering Policy 257

SIAT-HDBK-001 Marine Corps Systems Command Systems Engineering Technical 258

Review (SETR) Handbook 259

2.10.2 Non-Government Documents 260

ASME Y14.24 Types and Applications of Engineering Drawings 261

ASME Y14.100 Engineering Drawing Practices 262

ASTM D3951 Standard Practice for Commercial Packaging 263

EIA-649 National Consensus Standard for Configuration Management 264

IEEE Std. 12207.1-1997 265

Standard for Information Technology – Software Life Cycle 266

Process – Life Cycle Data 267

2.11 Government Furnished Property (GFP) 268

GFP is defined as property in the possession of, or directly acquired by, the Government and 269 subsequently furnished to the contractor for performance of a contract. Government furnished 270 property includes, but is not limited to, Contractor Acquired Property (CAP), spares, and 271 property fabricated or furnished for repairs, maintenance, overhaul, modification, or otherwise 272 provided by the contractor (i.e., CAP) in performance of the contract. All GFP can be found on 273

Attachment J.6. 274

The COR and contractor shall each maintain an updated Status of Government Furnished 276

Property (GFP) Report on all Marine Corps assets in the contractors possession. 277

The contractor shall provide a written request for required GFI. The Government will furnish the 279

GFI identified upon receipt of the request, dependent on availability. The contractor shall 280 acknowledge receipt of GFI to the Management Control Activity (MCA). 281

CDRL C001 Logistics Product Data (LPD) / DI-SESS-81758A 283

CDRL D001 Government Property Inventory Report / DI-MGMT-80441B 284

3 Performance Requirements 286

The following section specifies the Performance Requirements and Elements for the contract. 287

3.1 Contractor Logistics Support (CLS) 289

Not Applicable 290

3.1.1 Provide Operation and Maintenance support of the SAVT System 292

3.1.1.1 Operational Readiness 294

Not Applicable 295

3.1.1.2 Scenario Generation 297

Not Applicable 298

3.1.1.3 Scenario Initialization and Generation 300

Not Applicable 301

3.1.1.4 After Action Review (AAR) 303

Not Applicable 304

3.1.1.5 Training Scenario Adjustments 306

Not Applicable 307

3.1.1.6 Preventative and Corrective Maintenance 309

Not Applicable 310

3.1.1.7 On-Line Organizational Maintenance 312

Not Applicable 313

3.1.1.8 Scheduled Preventative Maintenance 315

Not Applicable 316

3.1.1.9 Off-Line Organizational (Intermediate) Maintenance 318

Not Applicable 319

3.1.1.10 Surge Operator Support 321

Not Applicable 322

3.1.1.11 Trainer Utilization Reporting 324

Not Applicable 325

3.1.1.12 Quarterly Inventory 327

Not Applicable 328

3.1.1.13 Modular Facility Maintenance 330

Not Applicable 331

3.1.1.14 SAVT Test Berth Relocation 333

Not applicable. 334

3.2 SAVT Modifications 336

This PWS sets forth the work efforts required to design, develop, install, integrate, test, deliver 337 and prepare associated documentation, provide technical support, provide field service support, 338 provide training, develop updated technical manuals and deliver hardware and software 339 modifications. 340

Modifications activities include: 341

Student Component Input/Output System 342

Lensatic Compass 343

Windows/Red Hat Operating System Upgrades 344

Cybersecurity 345 o Software and Operating System updates 346 o Security Technical Implementation Guides 347 o Licenses, Keys, and Passwords 348 o Other Cybersecurity Requirements 349 new software versions/releases/upgrades 350 software patches 351 anti-virus updates 352

3.2.1 Systems Engineering 354

For all Modifications, the contractor shall establish and maintain an effective systems 355 engineering program throughout the design, testing and production processes. 356

The contractor shall be required to address/perform the following: 357

System Engineering Process 358

The contractor shall apply a system engineering approach to produce the USMC 359

SAVT product baselines that are verifiable from functional baselines for all training 360 products, as described in this PWS. The contractor shall document, implement, 361 control, and maintain a collection of technical plans, processes, and schedules 362 necessary to guide the project toward accomplishment of its objectives and proper 363 conclusion. The contractor shall establish a System Engineering Plan (SEP) that 364 details the technical planning of the IMS. The SEP shall be the planning document for 365 all technical efforts and shall describe the tailored application of the contractor’s 366

System Engineering Process. The SEP policies and procedures shall specify 367 requirements for the planning, implementation, and control of product and process 368 development. The contractor policies and procedures shall address the following: 369

a. The application of the SEP throughout the training system life cycle 370

b. The preparation and acceptance of the IMS 371

c. The preparation and acceptance of data deliverables 372

d. Monitoring and reporting technical progress of the program 373

e. The preparation for, and conduct of, technical reviews 374

f. The contents and maintenance of an integrated data repository 375

g. The implementation of the test and evaluation program 376

Technical Reviews: 377

Technical reviews shall be conducted in accordance with MCSCO 5400.5, Naval 378

Systems Engineering Policy and the Marine Corps Systems Command Systems 379

Engineering Technical Review (SETR) Handbook, SIAT-HDBK-001 dated 06 380

August 2014. 381 o System Requirements Review (SRR) / System Functional Review (SFR) 382

The contractor shall conduct a System Requirements Review (SRR) / System 383

Functional Review (SFR). The SRR/SFR is a multi-disciplined product and 384 process assessment to ensure that the system under review can proceed into 385 design and that all system requirements and derived functional performance 386 requirements are defined and consistent with cost, schedule, risk, and other 387 system constraints. The SRR/SFR shall assess the system functional requirements 388 and ensure that all required system performance is fully decomposed and is 389 traceable to the functional baseline (SAVT Performance Specification). At the 390

SRR/SFR, the contractor shall: 391

a. Identify and discuss resource availability to support the schedule 392

b. Present and discuss a schedule Critical Path 393

c. Provide current status vs. Critical Path 394

d. Provide a complete program organizational structure 395

e. Identify relevant contractor subject matter experts (SMEs) to be used during 396 development and testing 397

f. Show that all functional requirements are traceable to the system 398 requirements 399

g. Show that all explicit and derived requirements are quantified and 400 documented 401

h. Address the following applicable functional areas: 402

(1) Electromagnetic Environment Effects (E3) 403

(2) Environment, Safety, and Occupational Health 404

(3) Logistics 405

(4) Technical Data 406

(5) Facilities 407

(6) Cybersecurity 408

(7) Quality Management 409

(8) Configuration Management 410

i. Present the results of a comprehensive risk assessment for design, 411 integration, and test. 412

SRR/SFR Entry Criteria 414

Entry criteria for the SRR/SFR shall consist of: 415

a. Government concurrence that the Kickoff exit criteria have been met. 416

b. Delivery and acceptance (when applicable) of all the CDRL items 417 scheduled to be delivered prior to SRR/SFR. 418

c. Government concurrence that the contractor submitted SRR agenda is 419 complete and acceptable. 420

d. All Kickoff action items requiring contractor response have been 421 completed and closed. 422

e. IMS (CDRL B001) is resourced at reasonable levels with realistic 423 performance expectations. 424

f. Program technical risks identified. 425

g. Program execution risks identified. 426

h. Requirements Traceability Matrix (RTM). 427

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 429

CDRL B004, Conference Agenda / DI-ADMN- 81249A 430

CDRL B005, Presentation Materials / DI-ADMN-81373 431

SRR/SFR Exit Criteria 433

Exit criteria for SRR/SFR shall consist of Government determination of 434 acceptable risk in all the SRR/SFR elements listed above, and in the following 435 specific criteria: 436

a. All SRR/SFR issues were captured in Requests for Action (RFAs) and 437 properly adjudicated and assigned. 438

b. All SRR/SFR RFAs were completed (closed). 439

c. The required technical areas were represented at the review. 440

d. Functional requirements, as disclosed, will satisfy the training needs. 441

e. System functional definition and functional decomposition is detailed 442 enough to support preliminary detailed production. 443

f. System Functional Baseline been established to enable preliminary 444 design to proceed under Configuration Management 445

g. Processes and metrics are in place 446

h. Risks are known and are manageable for implementation of the 447 functional requirements into a preliminary design 448

i. Program schedule is executable within the anticipated cost and technical 449 risks 450

j. Program is properly staffed. 451

k. RMF requirements decomposed 452

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 453

CDRL B003, Conference Minutes / DI-ADMIN-81250B 454

CDRL B004, Conference Agenda / DI-ADMN- 81249A 455

CDRL B005, Presentation Materials / DI-ADMN-81373 456 o Preliminary Production Review (PPR) 457

The contractor shall conduct a Preliminary Production Review (PPR). The 458 purpose of the PPR is for the Government to formally review the activities and 459 work products generated by the contractor during the performance of the 460 preliminary production stage and to verify that the approach for the system 461 production is ready to proceed into the detailed production phase. The contractor 462 shall present and describe the training system and program status. The following 463 items shall be topics of discussion and presentation at the PPR: 464

a. Training system hardware and software, including: 465

(1) Instructor Operator Station (IOS) 466

(2) Trainee station 467

(3) Computational system 468

(4) Visual system 469

(5) Communication and audio systems 470

(6) Network 471

(7) Instructional system 472

(8) Software tools 473

(9) Use of developmental and Commercial and Non-developmental 474

(CaNDI) software and databases 475

(10) Trainer databases 476

(11) Software development files 477

(12) Hardware and software interfaces 478

(13) Design modularity and commonality 479

(14) Facility Integration Planning 480

b. Electromagnetic Environmental Effects (E3) impacts 481

c. Reliability and Maintainability (R&M), and Systems Safety program 482 progress, including R&M predictions and preliminary identification of 483 hazards 484

d. Logistics aspects and concerns 485

e. Parts management program progress and identification of long lead time 486 items 487

f. Item Unique Identification (IUID) marking of trainer equipment and the 488

Initial Spares Kit (ISK) 489

g. Test and evaluation 490

h. Cybersecurity 491

i. Program problem and risk areas, recommended solutions, and evaluation 492 of alternatives 493

j. Updated RTM 494

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 496

CDRL B005, Presentation Materials / DI-ADMN-81373 497

PPR Entry Criteria 499

Entry criteria for the PPR shall consist of: 500

a. SRR/SFR exit criteria met 501

b. Delivery of all the CDRL items scheduled to be delivered prior to PPR 502

c. Availability of updated RTM showing traceability of requirements. 503

d. Development of risk assessments and risk mitigation plans 504

e. R&M requirements have been allocated to the design 505

f. IMS shows critical path through Critical Production Review (CPR) 506

g. Program technical risk medium or lower 507

h. Program execution risk medium or lower 508

i. Submittal and acceptance of the PPR agenda 509

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 511

CDRL B004, Conference Agenda / DI-ADMN- 81249A 512

CDRL B005, Presentation Materials / DI-ADMN-81373 513

PPR Exit Criteria 515

Exit criteria and final acceptance of the PPR shall consist of: 516

a. Satisfactory discussion of the CDRL items that were part of the PPR entry 517 criteria 518

b. The updated RTM demonstrates forward and backward traceability 519

c. Satisfactory discussion of risk assessments and risk mitigation plans. Risks 520 and their respective mitigation plans are in place and manageable for 521 implementation of the functional requirements into a preliminary design. 522

d. Program schedule is executable within the anticipated cost and technical 523 risks 524

e. Program is properly staffed 525

f. Successful resolution and closure of all PPR action items 526

g. Availability of the PPR presentation materials 527

h. Per the IMS (CDRL B001), an executable schedule has been presented 528 within the existing budget 529

i. Submittal and acceptance of the PPR minutes 530

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 532

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 533

CDRL B003, Conference Minutes / DI-ADMIN-81250B 534

CDRL B005, Presentation Materials / DI-ADMN-81373 535 o Critical Production Review (CPR) 537

The contractor shall conduct a CPR. The purpose of the CPR is for the 538

Government to formally review the activities and work products generated by 539 contractor during the performance of the critical production stage and to verify 540 that the system is ready to proceed into the hardware/software coding, assembly, 541 and integration phase. The contractor shall present and describe the finalized 542 training system and program status, and address all changes made since the PPR. 543

The following items shall be topics of discussion and presentation at the CPR: 544

a. Training system hardware and software, including: 545

(1) IOS 546

(2) Trainee station 547

(3) Computational system 548

(4) Visual system 549

(5) Communication and audio systems 550

(6) Network 551

(7) Instructional system 552

(8) Software tools 553

(9) Use of developmental and Commercial and Non-554 developmental (CaNDI) software and databases 555

(10) Trainer databases 556

(11) Software development files 557

(12) Hardware and software interfaces 558

(13) Design modularity and commonality 559

(14) Facility Integration Planning 560

b. E3 impacts 561

c. R&M and System Safety programs progress, including updated R&M 562 predictions and hazards analysis results 563

d. Logistics design aspects and concerns 564

e. Provisioning Parts List (PPL) 565

f. Engineering Data for Provisioning (EDFP) 566

g. Technical Manuals 567

h. IUID marking of trainer equipment and ISK 568

i. Parts management program status 569

j. Test and evaluation 570

k. Cybersecurity 571

l. Program problem and risk areas, recommended solutions, and 572 evaluation of alternatives 573

m. Updated RTM 574

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 576

CDRL C001, Logistics Product Data (LPD) / DI-SESS-81758 577

CDRL C002, COTS Manuals and Associated Supplemental Data / DI-578

TMSS-80527C 579

CDRL C003, Logistics Product Data Provisioning Parts List (PPL) / DI-580

SESS-81758A 581

CDRL C004, Engineering Data for Provisioning (EDFP) / DI-SSESS-582

81758A 583

CDRL D002, Unique Identification (IUID) Marking and Verification 584

Report / DI-MGMT 585

CPR Entry Criteria 587

Entry criteria for the CPR shall consist of: 588

a. PPR exit criteria met 589

b. Delivery of all the CDRL items scheduled to be delivered prior to CPR 590

c. Availability of updated RTM showing requirements traceability 591

d. Availability of updated risk assessment and risk mitigation plans 592

e. Risks and their respective mitigation plans are in place and manageable 593 for implementation of the functional requirements into a preliminary 594 design 595

f. R&M requirements have been addressed in the design 596

g. All trade-off analyses complete 597

h. Logistics Analysis complete and plans established 598

i. Facility Integration Planning complete 599

j. IMS (CDRL B001) shows critical path through testing 600

k. Submittal and acceptance of the CPR agenda 601

j. Hardware and software list identified for inclusion in RMF package 602

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 604

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 605

CDRL B004, Conference Agenda / DI-ADMN- 81249A 606

CDRL B005, Presentation Materials / DI-ADMN-81373 607

CPR Exit Criteria 609

Exit criteria and final acceptance of the CPR shall consist of: 610

a. Satisfactory discussion of the CDRL items that were part of the CPR 611 entry criteria 612

b. The updated RTM demonstrates forward and backward traceability. 613

Satisfactory discussion of updated risk assessments and risk mitigation 614 plans. Risks and their respective mitigation plans are in place and 615 manageable for implementation of the functional requirements into a final 616 design. 617

c. Program schedule is executable within the anticipated cost and technical 618 risks 619

d. Program is properly staffed 620

e. Successful resolution and closure of all CPR action items 621

f. Availability of the CPR presentation materials 622

g. Per the IMS (CDRL B001), an executable schedule has been presented 623 within the existing budget 624

h. Submittal and acceptance of the CPR minutes. 625

i. Allocated baseline has been established 626

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 628

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 629

CDRL B003, Conference Minutes / DI-ADMIN-81250B 630

CDRL B005, Presentation Materials / DI-ADMN-81373 631

Open Systems Design 633

The contractor shall use an open systems approach as the preferred design strategy to: 634

(1) choose commercially supported specifications and standards for selected system 635 interfaces (external, internal, functional and physical), products, practices, and tools; 636 and (2) build open system architectures as the primary foundation in developing the 637 proposed system and its elements. Open systems is a system design philosophy that 638 uses widely-accepted, industry-approved interface standards that will allow 639 technological upgrades in system components to be easily inserted in the future. The 640 contractor shall identify the means for ensuring conformance to open systems 641 standards and profiles throughout the development process and provide evidence that 642 the process being used to manage the open systems approach supports open system 643 benefits such as portability, interoperability, technology insertion, vendor 644 independence, reusability, scalability, and commercial product based maintainability. 645

Requirements Traceability Matrix 646

The contractor shall provide Requirements Traceability Matrix (RTM) data to the 647

Government. The RTM uniquely identifies program requirements to ensure that the 648 requirements can be traced upward and downward and laterally for interfaces and 649 verified through all levels of the design, build, test, and verification phases of 650 development. 651

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 652

Generation of Specifications 654

The contractor shall establish a design baseline documented in the Prime Item Detail 655

Specification (PIDS). The PIDS shall be written to a clear level of understanding, 656 utilizing quantitative criteria as appropriate, to allow a clear understanding for further 657 requirements derivation into lower level documents, and criteria for test procedure 658 development. The contractor shall trace the Government provided system 659 specification requirements to the PIDS. 660

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 661

Reliability and Maintainability Program 663

The contractor shall maintain a comprehensive Reliability and Maintainability 664

(R&M) program to ensure the SAVT meet the R&M standards set forth in the 665

Performance Specification. The design shall be monitored throughout the entire 666 period of performance to identify and assess any changes, which would impact 667 reliability or maintainability. The contractor shall develop reliability analysis and 668 predictions as required to ensure compliance with the Performance Specification. 669

The program shall encompass all aspects of reliability with respect to design selection 670 of components, predictions, and testing. If it is determined that an item is a 671 throwaway, an analysis shall be performed at the next higher indenture level. The 672 contractor shall maintain and make available to the Government all R&M data on any 673 vendor or subcontractor supplied item and shall inform the Government of any part or 674 component, which will degrade system R&M requirements. 675 o Procedures and Controls 676

The contractor shall maintain procedures and controls, which ensure products, 677 obtained from suppliers, vendors and subcontractors meet reliability 678 requirements. 679

a. Establish, implement, and maintain documented procedures, which detect 680 and/or preclude the use of substandard or counterfeit parts in the production 681 process, and impose similar requirements on subcontractors. 682

b. Provide the Government with reasonable notice of any special R&M 683 program review meetings scheduled with subcontractors so Government 684 representatives may attend at their discretion. 685 o Reliability Predictions 686

The contractor shall provide reliability predictions based on a defined 687 configuration baseline. The contractor shall prepare and deliver a top-down 688 indentured reliability report to include the identification of the Mean Time 689

Between Failure (MTBF) for each maintenance-worthy item in addition to 690 identification of the system MTBF using best commercial practices. 691 o Failure Reporting, Analysis, and Corrective Action System (FRACAS) 692

The contractor shall develop a closed loop failure reporting system, procedures 693 for analysis of failures to determine the root cause, and documentation for 694 recording corrective actions taken. The Failure Reporting, Analysis, and 695

Corrective Action System (FRACAS) shall include uniform failure reporting, 696 failure analysis reports and corrective actions. All hardware/software failures 697 from system level down to the subassembly level shall be subject to these 698 requirements throughout the testing period including production and integration 699 testing, and during the post-production support period. The contractor shall 700 execute a single FRACAS database to encompass in-factory (testing), in-field 701

(production testing), and in-field (post-production) failure reporting and shall be 702 transferred to the Government upon conclusion of contract. The contractor shall 703 notify the Government of any failure impacting cost, schedule, producibility, 704 supportability, and cost of ownership or interface/performance. All failures, 705 critical and non-critical, shall be reported to the Government during meetings and 706 all SETR events. All failures shall be categorized as in-factory or in-field failures. 707

System operational hours (Elapsed Time Meter readings) shall be identified for 708 each failure occurrence and included in the FRACAS data structure. The 709 contractor shall assess the failure data for the identification of trends (5 or more 710 failures of the same root cause) and identify those trends in the monthly report. 711

Each FRACAS report shall, at a minimum, identify the root cause, and detail the 712 remedial action taken including parts replaced. The Government reserves the right 713 to conduct a Failure Review Board (FRB) throughout the contract. 714

CDRL A00J, Failure Analysis and Corrective Action Report (FACAR) / DI-715

SESS-81927 716

Government Access 717

The contractor shall provide the Government (and/or Government support 718 contractors) electronic access to its integrated development environment 719 throughout the term of the contract. 720

3.2.1.1 Software 722

For all software modifications, the contractor shall define, document, control and deliver to the 723

Government; all Trainer System Software (TSS) IAW sections 6.7 and 6.13 IEEE Std. 12207.1-724

1997. The contractor shall be required (per Task Order 2 and CDRL’s as delineated herein) to 725 address/perform the following: 726

System Software 728

The contractor shall define, document, control and deliver to the Government; all 729 trainer system software (TSS) IAW sections 6.7 and 6.13 IEEE Std. 12207.1-730

1997. All TSS developed in support of the SAVT shall be delivered with 731 corresponding source code, build tools, build procedures, executable code and 732 installation procedures. The delivery shall include compilation instructions. The 733 contractor shall deliver all software information CDRL A009 Software Version 734

Description (SVD) and executable software for the SAVT IAW CDRL A00F 735

Software Product Specification (SPS). The software delivery shall include all 736 software necessary to cold start the SAVT IAW the cold start section in the 737 specification. 738

CDRL A009, Software Version Description (SVD) / DI-IPSC-81442A 739

CDRL A00F, Software Product Specification (SPS) / DI-IPSC-81441A 740

Computer Software and Technical Data Rights 741

The Government shall have the minimum necessary rights to all technical data, 742 computer software, including firmware, and computer software documentation 743 necessary for competitive procurement throughout the lifecycle of the acquisition. 744

The minimum necessary rights are those which permit the Government to fully 745 support, maintain and modify the training device(s), including hardware and 746 software, in a competitive environment throughout the life cycle of the training 747 devices. Specifically, the Government intends to have the training devices 748 operated, maintained, modified and supported throughout their life cycle by a 749 competitively-awarded contract. Such effort may include modifications by third-750 parties in hardware and software to retain training integrity with the operational 751 equipment as it is changed, altered, enhanced or replaced; additional 752 modifications or changes to the hardware and software for training or other 753 purposes related to the training device (a modification is any change to the 754 software that produces a derivative); re-hosting the software on new or improved 755 hardware for the training devices; making additions to the hardware suite(s) 756 and/or combining the software with other software; providing the supporting 757 contractor(s) with access to the delivered software for any purpose whatsoever 758 related to the training device; and, use of the software and documentation by the 759 supporting contractor at its facility to perform its contractual requirement(s) for 760 purposes of the training devices. 761

3.2.1.2 Hardware 763

For hardware modifications, the contractor shall define, document, control and deliver to the 764

Government; all trainer system hardware. 765

CDRL A00A, Product Drawings/Models and Associated Lists / DI-SESS-81000E 766

3.2.3 System Safety Tasks 768

The contractor shall identify and evaluate environmental, safety, and health hazards, define risk 769 levels, and establish a program that manages the probability and severity of all hazards 770 associated with development, use, and disposal of the system in accordance with MIL-STD-882E 771

Tasks 205, 206, 207, 210. Residual risks will be evaluated by the Government in accordance 772 with MIL-STD-882E and accepted as appropriate prior to exposing people, equipment, or the 773 environment to known system related Environment, Safety, and Occupational Health (ESOH) 774 risks. The contractor shall identify all safety risks in the system safety documentation. The 775 contractor shall be required to perform the following: 776

System Safety Analysis and Assessment 777

The contractor shall perform and document a Safety Assessment in accordance with 778

MIL-STD-882E Task 301 to identify all safety features of the hardware, software, 779 and system design and to identify procedural, hardware and software related hazards 780 that may be present in the trainer including specific procedural controls and 781 precautions that should be followed. The SAR shall include a signed statement that all 782 identified hazards have been eliminated or their associated risks controlled to 783 acceptable levels and that the training systems are ready to field IAW CDRL A00G 784

Safety Assessment Report (SAR). 785

Material Safety Data Sheets 786

The contractor shall make available Material Safety Data Sheets (MSDS) to the 787

Government for review. MSDS’s shall be included in Safety Assessment Report. 788

ESOH Compliance Assessment 789

The contractor shall provide the Government with an assessment of applicable 790

Environment, Safety and Occupational Health (ESOH) laws and regulations, 791 identifying any potential compliance issues. ESOH compliance issues shall be 792 identified in Safety Assessment Report. 793

Site Safety 794

The contractor shall comply with all installation safety orders and or procedures. 795

Hazardous Material Use 796

The contractor shall receive Government approval prior to bringing hazardous 797 material onto the job site or prior to any other use in connection with this contract. 798

Allow a minimum of 10 working days for processing of the request for use of a 799 hazardous material. 800

Government shall consider any chemicals listed in one of the following sources to be 801 hazardous: 802

• 29 CFR 1910, Subpart Z, Toxic and Hazardous Substances, Occupational Safety 803 and Health Administration (OSHA). 804

• Threshold Limit Values for Chemical Substances and Physical Agents in the Work 805

Environment, American Conference of Governmental Industrial Hygienists, or 806

• Those hazardous substances prepared pursuant to Labor Code Section 3682. 807

Unforeseen Hazardous Material 808

The contractor shall stop work and notify the Government of any unforeseen 809 hazardous materials not previously indicated in design. The contractor shall make a 810 written request to the Government for approval of any unforeseen materials (i.e., 811

PCB, lead paint, and friable and non-friable asbestos) that may be hazardous to 812 human health upon disturbance during work operations. 813

Certification 814

The contractor’s on-site safety representative shall hold a valid OSHA 30-hour 815 certification. A copy of the individual’s certification shall be included in the Site 816

Specific Health & Safety Plan (SSHSP) CDRL A00H. 817

Accidents 818

All on-site accidents involving the contractor employees shall be reported to the 819

Government within one hour. The contractor shall conduct an investigation into all 820 accidents occurring on Government property involving Contractor employees and 821 report the findings of such an investigation to the Government within three working 822 days after occurrence. 823

CDRL A00G, Safety Assessment Report (SAR) / DI-SAFT-80102C 825

CDRL A00H, Site Specific Health and Safety Plan (SSHSP) / DI-ENVR-81375 826

3.2.4 System Test and Evaluation (T&E) 828

The contractor shall plan, coordinate, establish, and implement a comprehensive Test & 829

Evaluation (T&E) program that shall be designed to verify that the trainer and the integration of 830 all subsystems and equipment meet the technical and operational requirements as stated in this 831

PWS and the Task Order Specification.