c_1_10_2_SAVT_PWS_TASK_ORDER_2.pdf

M67854-17-R-7823 06/30/2017

Supporting Arms Virtual Trainer (SAVT) Modifications

Performance Work Statement (PWS) Task Order 2

Version 1.0 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.1.1.15 Mobilization

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

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

4.4 Applicable Directives

4.7 Quality

4.7.1 Quality Control

4.7.2 Quality Assurance Surveillance Plan (QASP)

iv

5 Deliverables

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.1.1.15 Mobilization 336

Not applicable. 337

3.2 SAVT Modifications 339

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

Modifications activities include: 344

• Student Component Input/Output System 345

• Lensatic Compass 346

• Windows/Red Hat Operating System Upgrades 347

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

3.2.1 Systems Engineering 357

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

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

• System Engineering Process 361

The contractor shall apply a system engineering approach to produce the USMC 362 SAVT product baselines that are verifiable from functional baselines for all training 363 products, as described in this PWS. The contractor shall document, implement, 364 control, and maintain a collection of technical plans, processes, and schedules 365 necessary to guide the project toward accomplishment of its objectives and proper 366 conclusion. The contractor shall establish a System Engineering Plan (SEP) that 367 details the technical planning of the IMS. The SEP shall be the planning document for 368 all technical efforts and shall describe the tailored application of the contractor’s 369 System Engineering Process. The SEP policies and procedures shall specify 370 requirements for the planning, implementation, and control of product and process 371 development. The contractor policies and procedures shall address the following: 372

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

b. The preparation and acceptance of the IMS 374

c. The preparation and acceptance of data deliverables 375

d. Monitoring and reporting technical progress of the program 376

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

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

g. The implementation of the test and evaluation program 379

• Technical Reviews: 380

Technical reviews shall be conducted in accordance with MCSCO 5400.5, Naval 381 Systems Engineering Policy and the Marine Corps Systems Command Systems 382 Engineering Technical Review (SETR) Handbook, SIAT-HDBK-001 dated 06 383 August 2014. 384 o System Requirements Review (SRR) / System Functional Review (SFR) 385

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

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

b. Present and discuss a schedule Critical Path 396

c. Provide current status vs. Critical Path 397

d. Provide a complete program organizational structure 398

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

f. Show that all functional requirements are traceable to the system 401 requirements 402

g. Show that all explicit and derived requirements are quantified and 403 documented 404

h. Address the following applicable functional areas: 405

(1) Electromagnetic Environment Effects (E3) 406

(2) Environment, Safety, and Occupational Health 407

(3) Logistics 408

(4) Technical Data 409

(5) Facilities 410

(6) Cybersecurity 411

(7) Quality Management 412

(8) Configuration Management 413

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

SRR/SFR Entry Criteria 417

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

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

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

c. Government concurrence that the contractor submitted SRR agenda is 422 complete and acceptable. 423

d. All Kickoff action items requiring contractor response have been 424 completed and closed. 425

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

f. Program technical risks identified. 428

g. Program execution risks identified. 429

h. Requirements Traceability Matrix (RTM). 430

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 432 CDRL B004, Conference Agenda / DI-ADMN- 81249A 433 CDRL B005, Presentation Materials / DI-ADMN-81373 434

SRR/SFR Exit Criteria 436

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

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

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

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

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

e. System functional definition and functional decomposition is detailed 445 enough to support preliminary detailed production. 446

f. System Functional Baseline been established to enable preliminary 447 design to proceed under Configuration Management 448

g. Processes and metrics are in place 449

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

i. Program schedule is executable within the anticipated cost and technical 452 risks 453

j. Program is properly staffed. 454

k. RMF requirements decomposed 455

CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 456 CDRL B003, Conference Minutes / DI-ADMIN-81250B 457 CDRL B004, Conference Agenda / DI-ADMN- 81249A 458 CDRL B005, Presentation Materials / DI-ADMN-81373 459 o Preliminary Production Review (PPR) 460

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

a. Training system hardware and software, including: 468

(1) Instructor Operator Station (IOS) 469

(2) Trainee station 470

(3) Computational system 471

(4) Visual system 472

(5) Communication and audio systems 473

(6) Network 474

(7) Instructional system 475

(8) Software tools 476

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

(CaNDI) software and databases 478

(10) Trainer databases 479

(11) Software development files 480

(12) Hardware and software interfaces 481

(13) Design modularity and commonality 482

(14) Facility Integration Planning 483

b. Electromagnetic Environmental Effects (E3) impacts 484

c. Reliability and Maintainability (R&M), and Systems Safety program 485 progress, including R&M predictions and preliminary identification of 486 hazards 487

d. Logistics aspects and concerns 488

e. Parts management program progress and identification of long lead time 489 items 490

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

Initial Spares Kit (ISK) 492

g. Test and evaluation 493

h. Cybersecurity 494

i. Program problem and risk areas, recommended solutions, and evaluation 495 of alternatives 496

j. Updated RTM 497

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 499 CDRL B005, Presentation Materials / DI-ADMN-81373 500

PPR Entry Criteria 502

Entry criteria for the PPR shall consist of: 503

a. SRR/SFR exit criteria met 504

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

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

d. Development of risk assessments and risk mitigation plans 507

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

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

g. Program technical risk medium or lower 510

h. Program execution risk medium or lower 511

i. Submittal and acceptance of the PPR agenda 512

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 514 CDRL B004, Conference Agenda / DI-ADMN- 81249A 515 CDRL B005, Presentation Materials / DI-ADMN-81373 516

PPR Exit Criteria 518

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

a. Satisfactory discussion of the CDRL items that were part of the PPR entry 520 criteria 521

b. The updated RTM demonstrates forward and backward traceability 522

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

d. Program schedule is executable within the anticipated cost and technical 526 risks 527

e. Program is properly staffed 528

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

g. Availability of the PPR presentation materials 530

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

i. Submittal and acceptance of the PPR minutes 533 CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 535 CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 536 CDRL B003, Conference Minutes / DI-ADMIN-81250B 537 CDRL B005, Presentation Materials / DI-ADMN-81373 538 o Critical Production Review (CPR) 540

The contractor shall conduct a CPR. The purpose of the CPR is for the 541 Government to formally review the activities and work products generated by 542 contractor during the performance of the critical production stage and to verify 543 that the system is ready to proceed into the hardware/software coding, assembly, 544 and integration phase. The contractor shall present and describe the finalized 545 training system and program status, and address all changes made since the PPR. 546 The following items shall be topics of discussion and presentation at the CPR: 547

a. Training system hardware and software, including: 548

(1) IOS 549

(2) Trainee station 550

(3) Computational system 551

(4) Visual system 552

(5) Communication and audio systems 553

(6) Network 554

(7) Instructional system 555

(8) Software tools 556

(9) Use of developmental and Commercial and Non-557 developmental (CaNDI) software and databases 558

(10) Trainer databases 559

(11) Software development files 560

(12) Hardware and software interfaces 561

(13) Design modularity and commonality 562

(14) Facility Integration Planning 563

b. E3 impacts 564

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

d. Logistics design aspects and concerns 567

e. Provisioning Parts List (PPL) 568

f. Engineering Data for Provisioning (EDFP) 569

g. Technical Manuals 570

h. IUID marking of trainer equipment and ISK 571

i. Parts management program status 572

j. Test and evaluation 573

k. Cybersecurity 574

l. Program problem and risk areas, recommended solutions, and 575 evaluation of alternatives 576

m. Updated RTM 577 CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 579 CDRL C001, Logistics Product Data (LPD) / DI-SESS-81758 580

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

TMSS-80527C 582

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

SESS-81758A 584

CDRL C004, Engineering Data for Provisioning (EDFP) / DI-SSESS-585 81758A 586 CDRL D003, Unique Identification (IUID) Marking and Verification 587 Report / DI-MGMT 588

CPR Entry Criteria 590

Entry criteria for the CPR shall consist of: 591

a. PPR exit criteria met 592

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

c. Availability of updated RTM showing requirements traceability 594

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

e. Risks and their respective mitigation plans are in place and manageable 596 for implementation of the functional requirements into a preliminary 597 design 598

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

g. All trade-off analyses complete 600

h. Logistics Analysis complete and plans established 601

i. Facility Integration Planning complete 602

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

k. Submittal and acceptance of the CPR agenda 604

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

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 607 CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 608 CDRL B004, Conference Agenda / DI-ADMN- 81249A 609 CDRL B005, Presentation Materials / DI-ADMN-81373 610

CPR Exit Criteria 612

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

a. Satisfactory discussion of the CDRL items that were part of the CPR 614 entry criteria 615

b. The updated RTM demonstrates forward and backward traceability. 616 Satisfactory discussion of updated risk assessments and risk mitigation 617 plans. Risks and their respective mitigation plans are in place and 618 manageable for implementation of the functional requirements into a final 619 design. 620

c. Program schedule is executable within the anticipated cost and technical 621 risks 622

d. Program is properly staffed 623

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

f. Availability of the CPR presentation materials 625

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

h. Submittal and acceptance of the CPR minutes. 628

i. Allocated baseline has been established 629

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 631 CDRL B001, Integrated Master Schedule (IMS) / DI-MGMT-81650 632 CDRL B003, Conference Minutes / DI-ADMIN-81250B 633 CDRL B005, Presentation Materials / DI-ADMN-81373 634

• Open Systems Design 636

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

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

• Requirements Traceability Matrix 649

The contractor shall provide Requirements Traceability Matrix (RTM) data to the 650 Government. The RTM uniquely identifies program requirements to ensure that the 651 requirements can be traced upward and downward and laterally for interfaces and 652 verified through all levels of the design, build, test, and verification phases of 653 development. 654

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

• Generation of Specifications 657

The contractor shall establish a design baseline documented in the Prime Item Detail 658 Specification (PIDS). The PIDS shall be written to a clear level of understanding, 659 utilizing quantitative criteria as appropriate, to allow a clear understanding for further 660 requirements derivation into lower level documents, and criteria for test procedure 661 development. The contractor shall trace the Government provided system 662 specification requirements to the PIDS. 663

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

• Reliability and Maintainability Program 666

The contractor shall maintain a comprehensive Reliability and Maintainability 667 (R&M) program to ensure the SAVT meet the R&M standards set forth in the 668 Performance Specification. The design shall be monitored throughout the entire 669 period of performance to identify and assess any changes, which would impact 670 reliability or maintainability. The contractor shall develop reliability analysis and 671 predictions as required to ensure compliance with the Performance Specification. 672 The program shall encompass all aspects of reliability with respect to design selection 673 of components, predictions, and testing. If it is determined that an item is a 674 throwaway, an analysis shall be performed at the next higher indenture level. The 675 contractor shall maintain and make available to the Government all R&M data on any 676 vendor or subcontractor supplied item and shall inform the Government of any part or 677 component, which will degrade system R&M requirements. 678 o Procedures and Controls 679

The contractor shall maintain procedures and controls, which ensure products, 680 obtained from suppliers, vendors and subcontractors meet reliability 681 requirements. 682

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

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

The contractor shall provide reliability predictions based on a defined 690 configuration baseline. The contractor shall prepare and deliver a top-down 691 indentured reliability report to include the identification of the Mean Time 692 Between Failure (MTBF) for each maintenance-worthy item in addition to 693 identification of the system MTBF using best commercial practices. 694 o Failure Reporting, Analysis, and Corrective Action System (FRACAS) 695

The contractor shall develop a closed loop failure reporting system, procedures 696 for analysis of failures to determine the root cause, and documentation for 697 recording corrective actions taken. The Failure Reporting, Analysis, and 698 Corrective Action System (FRACAS) shall include uniform failure reporting, 699 failure analysis reports and corrective actions. All hardware/software failures 700 from system level down to the subassembly level shall be subject to these 701 requirements throughout the testing period including production and integration 702 testing, and during the post-production support period. The contractor shall 703 execute a single FRACAS database to encompass in-factory (testing), in-field 704 (production testing), and in-field (post-production) failure reporting and shall be 705 transferred to the Government upon conclusion of contract. The contractor shall 706 notify the Government of any failure impacting cost, schedule, producibility, 707 supportability, and cost of ownership or interface/performance. All failures, 708 critical and non-critical, shall be reported to the Government during meetings and 709 all SETR events. All failures shall be categorized as in-factory or in-field failures. 710 System operational hours (Elapsed Time Meter readings) shall be identified for 711 each failure occurrence and included in the FRACAS data structure. The 712 contractor shall assess the failure data for the identification of trends (5 or more 713 failures of the same root cause) and identify those trends in the monthly report. 714 Each FRACAS report shall, at a minimum, identify the root cause, and detail the 715 remedial action taken including parts replaced. The Government reserves the right 716 to conduct a Failure Review Board (FRB) throughout the contract. 717

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

SESS-81927 719

• Government Access 720

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

3.2.1.1 Software 725

For all software modifications, the contractor shall define, document, control and deliver to the 726 Government; all Trainer System Software (TSS) IAW sections 6.7 and 6.13 IEEE Std. 12207.1-727 1997. The contractor shall be required (per Task Order 2 and CDRL’s as delineated herein) to 728 address/perform the following: 729

• System Software 731

The contractor shall define, document, control and deliver to the Government; all 732 trainer system software (TSS) IAW sections 6.7 and 6.13 IEEE Std. 12207.1-733 1997. All TSS developed in support of the SAVT shall be delivered with 734 corresponding source code, build tools, build procedures, executable code and 735 installation procedures. The delivery shall include compilation instructions. The 736 contractor shall deliver all software information CDRL A009 Software Version 737 Description (SVD) and executable software for the SAVT IAW CDRL A00F 738 Software Product Specification (SPS). The software delivery shall include all 739 software necessary to cold start the SAVT IAW the cold start section in the 740 specification. 741

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

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

• Computer Software and Technical Data Rights 744

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

3.2.1.2 Hardware 766

For hardware modifications, the contractor shall define, document, control and deliver to the 767 Government; all trainer system hardware. 768

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

3.2.3 System Safety Tasks 771

The contractor shall identify and evaluate environmental, safety, and health hazards, define risk 772 levels, and establish a program that manages the probability and severity of all hazards 773 associated with development, use, and disposal of the system in accordance with MIL-STD-882E 774 Tasks 205, 206, 207, 210. Residual risks will be evaluated by the Government in accordance 775 with MIL-STD-882E and accepted as appropriate prior to exposing people, equipment, or the 776 environment to known system related Environment, Safety, and Occupational Health (ESOH) 777 risks. The contractor shall identify all safety risks in the system safety documentation. The 778 contractor shall be required to perform the following: 779

• System Safety Analysis and Assessment 780

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

• Material Safety Data Sheets 789

The contractor shall make available Material Safety Data Sheets (MSDS) to the 790 Government for review. MSDS’s shall be included in Safety Assessment Report. 791

• ESOH Compliance Assessment 792

The contractor shall provide the Government with an assessment of applicable 793 Environment, Safety and Occupational Health (ESOH) laws and regulations, 794 identifying any potential compliance issues. ESOH compliance issues shall be 795 identified in Safety Assessment Report. 796

• Site Safety 797

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

• Hazardous Material Use 799

The contractor shall receive Government approval prior to bringing hazardous 800 material onto the job site or prior to any other use in connection with this contract. 801 Allow a minimum of 10 working days for processing of the request for use of a 802 hazardous material. 803

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

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

• Threshold Limit Values for Chemical Substances and Physical Agents in the Work 808 Environment, American Conference of Governmental Industrial Hygienists, or 809

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

• Unforeseen Hazardous Material 811

The contractor shall stop work and notify the Government of any unforeseen 812 hazardous materials not previously indicated in design. The contractor shall make a 813 written request to the Government for approval of any unforeseen materials (i.e., 814 PCB, lead paint, and friable and non-friable asbestos) that may be hazardous to 815 human health upon disturbance during work operations. 816

• Certification 817

The contractor’s on-site safety representative shall hold a valid OSHA 30-hour 818 certification. A copy of the individual’s certification shall be included in the Site 819 Specific Health & Safety Plan (SSHSP) CDRL A00H. 820

• Accidents 821

All on-site accidents involving the contractor employees shall be reported to the 822 Government within one hour. The contractor shall conduct an investigation into all 823 accidents occurring on Government property involving Contractor employees and 824 report the findings of such an investigation to the Government within three working 825 days after occurrence. 826

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

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

3.2.4 System Test and Evaluation (T&E) 831

The contractor shall plan, coordinate, establish, and implement a comprehensive Test & 832 Evaluation (T&E) program that shall be designed to…