f_SAVT_TO2_SOW_DRAFT.pdf

STATEMENT OF WORK

FOR

SUPPORTING ARMS VIRTUAL TRAINER (SAVT)

TASK ORDER 2 – SYSTEM MODIFICATIONS

Prepared By

MARCORSYSCOM

PROGRAM MANAGER FOR TRAINING SYSTEMS

12350 RESEARCH PARKWAY

ORLANDO, FLORIDA 32826-3224

DISTRIBUTION F. Further dissemination only as directed by PROGRAM MANAGER, TRAINING SYSTEMS, MARINE CORPS SYSTEMS COMMAND (SAVT), 12211

SCIENCE DRIVE, ORLANDO, FLORIDA 32826-3224.., (29 March 2017) or higher DoD authority.

M67854-17-R-7823 04/14/2017

Attachment XXXX

Revision History

Revision Affected Paragraph(s) Changes

Table of Contents

1 Scope

2 Applicable Documents

2.1 Military Standards and Specifications – Mandatory Compliance

2.2 Military Standards and Specifications – Guidance Only

2.3 Federal Standard – Mandatory

2.4 Drawings

2.5 Handbooks – Guidance Only

2.6 Other Government Documents

2.7 Non-Government Documents

3 Requirements

3.1 Program and Data Management

3.1.1 Program Management (CDRL B002)

3.1.2 Subcontractor Management

3.1.3 Data Management

3.1.3.1 Technical Proposal

3.1.3.2 Schedule Planning

3.1.3.3 Assignment of Responsibility and Authority

3.2 Government Furnished Property (GFP)

3.2.1 Government Furnished Material (GMS)/Equipment (GFE) (CDRL C001)

3.2.1.1 Acknowledgement Report for GFE (CDRL C002)

3.2.1.2 Acceptance Inspection Report for GFE (CDRL C003)

3.2.2 Government Furnished Information (GFI) (CDRL C004)

3.2.2.1 Acknowledgement Report for GFE (CDRL C005)

3.3 Meetings, Formal Reviews, Conferences, and Audits

3.3.1 Contractor Responsibilities for Reviews

3.3.2 Post Award Conference

3.3.2.1 PAC Entry Criteria

3.3.2.2 PAC Exit Criteria

3.3.3 In-Process Review

3.4 Systems Engineering

3.4.1 Systems Engineering Process

3.4.2 Technical Review

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

3.4.2.1.1 SRR/SFR Entry Criteria

3.4.2.1.2 SRR/SFR Exit Criteria

3.4.2.2 Preliminary Production Review

3.4.2.2.1 PPR Entry Criteria

3.4.2.2.2 PPR Exit Criteria

3.4.2.3 Critical Production Review

3.4.2.3.1 CPR Entry Criteria

3.4.2.3.2 CPR Exit Criteria

3.4.3 Open Systems Design

3.4.4 Requirements Traceability Matrix

3.4.5 Generation of Specifications

3.4.6 Reliability and Maintainability Program

3.4.6.1 Procedures and Controls

3.4.6.2. Reliability Predictions

3.4.7 Government Access

3.5 Software

3.5.1 System Software

3.5.2 Computer Software and Technical Data Rights

3.5.3 System Safety Tasks

3.5.3.1 System Safety Analysis and Assessment

3.5.3.2 Material Safety Data Sheets

3.5.3.3 ESOH Compliance Assessment

3.5.4.4 Lithium Battery Safety Assessment

3.5.3.5 Site Safety

3.5.3.6 Hazardous Material Use

3.5.3.7 Unforeseen Hazardous Material

3.5.3.8 Certification

3.5.3.9 Accidents

3.6 System Test and Evaluation (T&E)

3.6.1 Responsibility for Tests

3.6.1.1 Test Authority

3.6.1.2 T&E Program Planning

3.6.1.3 Test Resources and Facilities

3.6.2 Test Methods

3.6.2.1 Test Criteria

3.6.2.2 Tolerance Data

3.6.2.3 Alignment

3.6.2.4 Test Log

3.6.2.5 Changes During Testing

3.6.2.6 Changes After Testing

3.6.3 T&E Deficiency Reporting System

3.6.3.1 Deficiency Report (DR) Categories

3.6.4 T&E Program Components

3.6.4.1 In-Process Inspections

3.6.4.2 Baseline Configuration Audit (BCA)

3.6.4.3 Incremental Contractor Preliminary Inspection (ICPI)

3.6.4.4 Test Readiness Review (TRR)

3.6.4.4.1 TRR Entry Criteria

3.6.4.4.2 TRR Exit Criteria

3.6.4.5 Conformance Inspections

3.6.4.5.1 Functional Configuration Audit

3.6.4.5.2 Government Preliminary Inspection

3.6.4.5.2.1 GPI Exit Criteria

3.6.4.5.3 Joint Final Inspection

3.6.4.4.3.1 JFI Entry Criteria

3.6.4.4.3.2 JFI Exit Criteria

3.6.4.5.4 Physical Configuration Audit

3.6.4.5.4.1 Preliminary PCA

3.6.4.5.4.2 Final PCA

3.6.4.5.4.3 On-site Pre-modification Inspection (PMI)

3.7 Configuration Management Process

3.7.1 Configuration Management Meetings and Audits

3.7.1.1 Baseline Management

3.7.1.1.1 Functional Baseline

3.7.1.1.2 Allocated Baseline

3.7.1.1.3 Product Baseline

3.7.1.2 Configuration Control

3.7.1.2.1 Engineering Release System

3.7.1.2.2 Engineering Change Proposals (CDRL A00B)

3.7.1.2.3 Requests for Deviation (CDRL A00C)

3.8 Technical Data Package (TDP)

3.9 Cybersecurity

3.9.1 Initial Risk Management Framework (RMF) Meeting

3.9.1.1 IA Certification and Accreditation Support

3.9.1.1.1 IA Vulnerability Management Program (IAVMP)

3.9.1.1.2 IA Contractor Training and Certification

3.9.1.2 Information Security

3.9.1.3 Documentation Deliverables

3.9.1.4 Network Scans

3.9.1.5 Analysis of the System Development Life Cycle (SDLC)

3.10 Packaging

3.11 System Documentation Update

4 Deliverables

4.1 Documentation

4.1.1 Government Furnished Information/Equipment

1. SCOPE

This SOW sets forth the work efforts required to design, fabricate, install, and test the Supporting Arms Virtual Trainer (SAVT) modifications, as stated in the associated document “System Specification for Supporting Arms Virtual Trainer (SAVT) Task Order 2 – System Modifications”. The existing SAVT locations are as follows:

a. Marine Corps Base, Camp Pendleton, California

b. Marine Corps Air-Ground Combat Center, Twenty-Nine Palms, California

c. Marine Corps Base, Camp Lejeune, North Carolina

d. Marine Corps Base, Kaneohe Bay, Hawaii

e. Marine Corps Base, Camp Hansen, Okinawa, Japan

f. *Marine Corps Air Station (MCAS), Yuma, Arizona (Not included in this Task Order)

g. SAVT Test Berth currently NAWCTSD, WSIL, Orlando, FL. (to be relocated)

The tasks required in this SOW are within the scope of the “Supporting Arms Virtual Trainer (SAVT) Contractor Logistical Support (CLS), Post Deployment Software Support (PDSS) and Non-PDSS Performance Work Statement (PWS)” document. The contractor is responsible for providing all/specific material, personnel, tools, services and necessary support documentation needed to complete the tasks identified in this SOW.

*MCAS Yuma SAVT system is not included in this Task Order. Future Task Order option may be requested at a later date specific to this site.

2. APPLICABLE DOCUMENTS

The following documents specified form a part of this Statement of Work (SOW) to the extent specified herein. The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. All second tier and below references cited in mandatory compliance documents shall be considered as guidance only.

Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1. Military Standards and Specifications - Mandatory Compliance

MIL-STD-129 Military Marking for Shipment and Storage

MIL-STD-882E Standard Practice for System Safety

MIL-STD-961 Defense and Program-Unique Specifications Format and

Content

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

MIL-STD-31000A Technical Data Packages

2.2. Military Standards and Specifications - Guidance Only

Not Applicable.

2.3. Federal Standard - Mandatory

FED-STD-313 Material Safety Data, Transportation Data and Disposal Data for Hazardous Materials Furnished to Government Activities

2.4. Drawings.

Not Applicable.

2.5. Handbooks - Guidance Only.

MIL-HDBK-61A Configuration Management Guidance

MCSCO 5400.5 Naval Systems Engineering Policy

SIAT-HDBK-001 Marine Corps Systems Command Systems Engineering

Technical Review (SETR) Handbook

2.6. Other Government Documents

Unless otherwise stated, the following documents may be obtained from http://www.dla.mil/HQ/InformationOperations/DocumentServices/ or DLA Document Services, 5450 Carlisle Pike Bldg. 09, PO Box 2020, Mechanicsburg, PA 17055-0788.

DoD 4000.25-1-M Military Standard Requisitioning and Issue Procedures

(MILSTRIP)

DODI 8510.01 Risk Management Framework (RMF) for DoD Information

Technology

2.7. Non-Government Documents

ASME Y14.24 Types and Applications of Engineering Drawings

ASME Y14.100 Engineering Drawing Practices

ASTM D3951 Standard Practice for Commercial Packaging

(Copies of ASTM documents are available from www.astm.org or American Society for Testing and Materials International, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.)

EIA-649 National Consensus Standard for Configuration

Management

(EIA documents are available from the related associations that were the former EIA sectors www.eia.org.)

IEEE Std. 12207.1-1997 Standard for Information Technology – Software Life

Cycle Process – Life Cycle Data

3. REQUIREMENTS

The contractor shall perform all tasks required and delineated in this SOW to design, develop, integrate, test, produce, manufacture, deliver and prepare associated documentation, provide logistic support, provide technical support, provide field service support, provide training, develop updated technical manuals and deliver the SAVT modifications in the quantity specified in the contract. The contractor shall provide all materials, equipment, hard tooling, personnel, and facilities necessary to manufacture, fabricate, integrate, produce, and deliver the types and quantities of deliverables specified by the contract.

3.1. Program and Data Management

3.1.1. Program Management (CDRL B002)

The contractor shall establish and maintain program management practices throughout the period of performance. Program management practices shall provide visibility into the Contractors’ organization and techniques used in managing the program, specifically Subcontractor and data management. Documentation shall be readily available to Government representative(s) during planned visits.

CDRL B002 Contractor’s Progress, Status and Management Report / DI-MGMT-80227

3.1.2. Subcontractor Management

The contractor is responsible for performance of requirements delineated in this SOW, and shall institute appropriate management actions relative to Subcontractor performance.

Requirements that are contractually specified shall apply to Subcontractor performance;

however, the contractor shall be accountable for compliance of Subcontractors and is responsible for ensuring all deliverable products comply with the contract requirements.

http://www.eia.org/

3.1.3. Data Management

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

3.1.3.1. Technical Proposal

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

3.1.3.2. Schedule Planning

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

The program schedule shall include all significant events, and a Program Planning Milestone Chart shall depict major tasks and events from start to completion of the contract. The contractor shall notify the Government in writing of any anticipated or projected work stoppages or delays that will impact schedules.

3.1.3.3. Assignment of Responsibility and Authority

The contractor shall identify the organizational elements responsible for the conduct of the activities delineated in this SOW. The contractor shall assign responsibilities and define clear lines of authority for contractor determination and control of contractor resources necessary to satisfy each element of this SOW. The following contractor positions shall constitute "key personnel". The contractor in writing shall appoint all persons filling these key personnel positions. The contractor shall notify the Government within ten days of making changes regarding authority, responsibility, or identity of contractor employees who are key personnel during the period of performance.

a. Program Manager. The contractor shall designate a Program Manager (PM) who shall possess sufficient corporate authority to manage all elements of contractor performance and responsibility under the contract. The PM shall serve as the primary point of contact between the contractor and the Government, and be responsible for the management of all contractor activities related to the contract.

b. Systems Engineer. The contractor shall designate a Systems Engineer who shall manage all engineering elements of contractor performance and responsibility under the contract.

c. Test Engineer. The contractor shall designate a Test Engineer who shall manage all test and engineering elements of contractor performance and responsibility under the contract.

d. Configuration Management (CM) Manager. The contractor shall designate a CM

Manager who shall manage all CM elements of contractor performance and responsibility under the contract.

e. Environment, Safety, and Occupational Health (ESOH) Manager. The contractor shall designate an ESOH Manager who shall manage all environment, safety and occupational health elements of contractor performance and responsibility under the contract.

f. Integrated Logistic Support (ILS) Manager. The contractor shall designate an ILS

Manager who shall manage all ILS elements of contractor performance and

g. Quality Assurance (QA) Manager. The contractor shall designate a QA Manager who shall manage all quality related elements of contractor performance and

h. Training Manager. The contractor shall designate a Training Manager who shall manage all training related elements of contractor performance and responsibility under the contract.

i. Lead Information Systems Security Engineer (ISSE). The contractor shall designate an ISSE who shall lead all RMF activities in support of the contract.

j. Installation Lead. The contractor shall designate an Installation Lead who shall possess sufficient authority to manage, direct, execute and control all elements related to the installation of the modified CCS systems.

3.2. Government Furnished Property (GFP)

GFP is defined as property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract. Government furnished property includes, but is not limited to, spares and property furnished for repairs, maintenance, overhaul, or modification.

3.2.1. Government Furnished Material (GFM)/Equipment (GFE) (CDRL C001)

The contractor shall provide a written request for required GFM/GFE. Upon receipt of the request, the Government will notify the contractor of the availability of requested GFM and will furnish the GFM/GFE, dependent on availability. The contractor shall be responsible for the receipt, accountability, security, storage, and reporting of the GFM/GFE provided. The contractor shall sign an accountability agreement for the GFM/GFE annually, or as requested by the Government.

CDRL C001 Request for Government Furnished Material (GFM/GFE) / DI-MGMT-80408B

3.2.1.1. Acknowledgement Report for GFE (CDRL C002)

The contractor shall acknowledge receipt of GFM/GFE to the Management Control Activity

(MCA).

CDRL C002 Receipt of Government Material Report / DI-MGMT-80389B

3.2.1.2. Acceptance Inspection Report for GFE (CDRL C003)

The contractor shall inspect and inventory all GFE received and identify and report all discrepancies or deficiencies, including associated repair costs, such as labor, material, and test, to restore the GFE to like new condition.

CDRL C003 Acceptance Inspection Equipment Report / DI-MGMT-81979

3.2.2. Government Furnished Information (GFI) (CDRL C004)

The contractor shall provide a written request for required GFI. The Government will furnish the GFI identified upon receipt of the request, dependent on availability.

CDRL C004 Request for Government Furnished Materiel (GFI) / DI-MGMT-80408B

3.2.2.1. Acknowledgement Report for GFE (CDRL C005)

The contractor shall acknowledge receipt of GFI to the Management Control Activity (MCA).

CDRL C005 (GFI) Receipt of Government Material Report / DI-MGMT-80389B

3.3. Meetings, Formal Reviews, Conferences, and Audits

3.3.1. Contractor Responsibilities for Reviews

The contractor shall plan, host, attend, coordinate, support and conduct the meetings, reviews, and conferences. The reviews shall be conducted at Government and contractor facilities.

Reviews requiring demonstration and/or examination of equipment shall be conducted at the contractor's facility. All such reviews shall be included in the program schedule and may be held concurrently with the Government’s approval. The contractor shall prepare minutes (CDRL B003 DI-ADMIN-81250B, Conference Minutes) conference agendas (CDRL B004 DI-ADMN- 81249A, Conference Agenda) and conference presentation materials (CDRL B005 DI-ADMN-81373, Presentation Material), and reports following each review. The Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance. Action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes. Except where noted herein, conferences and reviews shall be considered fulfilled when the following items are completed:

a. A formal meeting has been conducted and the conference and reviews are presented to the Government.

b. Topics required for discussion and presentation have been covered.

c. Action items requiring contractor response have been resolved.

d. The Government has accepted the conference minutes.

CDRL B003 Conference Minutes / DI-ADMIN-81250B CDRL B004 Conference Agenda / DI-ADMN- 81249A CDRL B005 Presentation Materials / DI-ADMN-81373

3.3.2. Post Award Conference

The contractor shall host a Post Award Conference (PAC) at the contractor's facility within 30 days after Contract Award. The PAC shall be conducted jointly by the Government and the contractor. The purpose of the PAC is for the contractor to review and demonstrate to the Government the management procedures, provide progress assessments, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings/actions. The contractor shall present management, key personnel, and program implementation processes. At the PAC, the contractor shall present an IMS (CDRL B001 DI-MGMT-81861) showing the critical milestones and supporting events, including logistics, leading to these milestones. The PAC shall include the presentation and discussion of information and data relating to:

a. Introduction and Contract Overview

b. Discussion and clarification of Spec and SOW requirements

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

d. CDRL delivery schedule and status

e. Program specific Risk Management Planning approach and processes

f. Program Cybersecurity Implementation Planning approach and processes

g. IPT structure, membership, and responsibilities

h. Action item reporting and status

i. Long lead time item identification and status

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

k. Defense Reutilization Management Office (DRMO) activities.

3.3.2.1. PAC Entry Criteria

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

a. Government Acceptance of agenda (CDRL B004) and presentation materials (CDRL

B005)

b. Submission of the following CDRLs for Government review:

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

3.3.2.2. PAC Exit Criteria

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

a. Required PAC topics have been satisfactorily presented, discussed, and documented.

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

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

d. PAC minutes (CDRL B003) and presentation materials (CDRL B005) have been submitted and accepted.

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

CDRL B003 Conference Minutes / DI-ADMIN-81250B

CDRL B005, Presentation Materials / DI-ADMN-81373

3.3.3. In-Process Review

In Process Reviews (IPR) shall be held at a minimum quarterly or as needed, at a date and location mutually agreed upon. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The contractor’s progress, management, technical support services, integrated logistics support, administrative, assurance of compliance with contract requirements, program status, funding, problem identification and resolutions shall be agenda items. Actual versus expected performance of each area shall be addressed. The contractor shall prepare agenda, presentation materials, and minutes for all IPR IAW CDRL B003 DI-ADMIN-81250B, Conference Minutes and CDRL B004 DI-ADMN-81249A, Conference Agenda.

The IPR agenda shall include review of the following:

• Contractor’s progress to include, but not limited to, the status of the overall program, including the training system design (hardware and software), Quality Management System (QMS), CM, E3, testing, and production

• Management

• Technical support services (if any)

• Integrated logistics support program review

• Administrative

• Assurance of compliance with contract requirements

• Program schedule status

• Funding Status

• Problem identification and resolution

• Review of program risks

• Review of updated Requirements Traceability Matrix (RTM).

• Review of Cybersecurity

CDRL A001, Prime Item Detail Specification (PIDS) / DI-SDMP-81493 CDRL B003, Conference Minutes / DI-ADMIN-81250B

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

3.4. Systems Engineering

The contractor shall establish and maintain an effective systems engineering program throughout the design, testing and production processes.

3.4.1. Systems Engineering Process

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

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

b. The preparation and acceptance of the IMS

c. The preparation and acceptance of data deliverables

d. Monitoring and reporting technical progress of the program

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

f. The contents and maintenance of an integrated data repository

g. The implementation of the test and evaluation program

3.4.2. Technical Reviews

Technical reviews shall be conducted in accordance with MCSCO 5400.5, Naval Systems Engineering Policy and the Marine Corps Systems Command Systems Engineering Technical Review (SETR) Handbook, SIAT-HDBK-001 dated 06 August 2014.

3.4.2.1. System Requirements Review/System Functional Review (SRR/SFR)

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

a. Identify and discuss resource availability to support the schedule

b. Present and discuss a schedule Critical Path

c. Provide current status vs. Critical Path

d. Provide a complete program organizational structure

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

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

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

h. Address the following applicable functional areas:

(1) Electromagnetic Environment Effects (E3)

(2) Environment, Safety, and Occupational Health

(3) Logistics

(4) Technical Data

(5) Facilities

(6) Cybersecurity

(7) Quality Management

(8) Configuration Management

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

3.4.2.1.1. SRR/SFR Entry Criteria

Entry criteria for the SRR/SFR shall consist of:

a. Government concurrence that the PAC exit criteria have been met.

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

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

d. All PAC action items requiring contractor response have been completed and closed.

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

f. Program technical risks identified.

g. Program execution risks identified.

h. RTM.

3.4.2.1.2. SRR/SFR Exit Criteria

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

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

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

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

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

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

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

g. Processes and metrics are in place

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

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

j. Program is properly staffed.

k. RMF requirements decomposed

3.4.2.2. Preliminary Production Review

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

a. Training system hardware and software, including:

(1) Instructor Operator Station (IOS)

(2) Trainee station

(3) Computational system

(4) Visual system

(5) Communication and audio systems

(6) Network

(7) Instructional system

(8) Software tools

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

(10) Trainer databases

(11) Software development files

(12) Hardware and software interfaces

(13) Design modularity and commonality

(14) Facility Integration Planning

b. Electromagnetic Environmental Effects (E3) impacts

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

d. Logistics aspects and concerns

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

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

Spares Kit (ISK)

g. Test and evaluation

h. Cybersecurity

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

j. Updated RTM

3.4.2.2.1. PPR Entry Criteria

Entry criteria for the PPR shall consist of:

a. SRR/SFR exit criteria met

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

c. Availability of updated RTM showing traceability of requirements.

d. Development of risk assessments and risk mitigation plans

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

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

g. Program technical risk medium or lower

h. Program execution risk medium or lower

i. Submittal and acceptance of the PPR agenda

3.4.2.2.2. PPR Exit Criteria

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

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

b. The updated RTM demonstrates forward and backward traceability

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

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

e. Program is properly staffed

f. Successful resolution and closure of all PPR action items

g. Availability of the PPR presentation materials

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

i. Submittal and acceptance of the PPR minutes

3.4.2.3. Critical Production Review

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

a. Training system hardware and software, including:

(1) IOS

(2) Trainee station

(3) Computational system

(4) Visual system

(5) Communication and audio systems

(6) Network

(7) Instructional system

(8) Software tools

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

(10) Trainer databases

(11) Software development files

(12) Hardware and software interfaces

(13) Design modularity and commonality

(14) Facility Integration Planning

b. E3 impacts

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

d. Logistics design aspects and concerns

e. IUID marking of trainer equipment and ISK

f. Parts management program status

g. Test and evaluation

h. Cybersecurity

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

j. Updated RTM

3.4.2.3.1. CPR Entry Criteria

Entry criteria for the CPR shall consist of:

a. PPR exit criteria met

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

c. Availability of updated RTM showing requirements traceability

d. Availability of updated risk assessment and risk mitigation plans

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

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

g. All trade-off analyses complete

h. Logistics Analysis complete and plans established

i. Facility Integration Planning complete

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

k. Submittal and acceptance of the CPR agenda

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

3.4.2.3.2. CPR Exit Criteria

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

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

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

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

d. Program is properly staffed

e. Successful resolution and closure of all CPR action items

f. Availability of the CPR presentation materials

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

h. Submittal and acceptance of the CPR minutes.

i. Allocated baseline has been established

3.4.3. Open Systems Design

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

3.4.4. Requirements Traceability Matrix

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

3.4.5. Generation of Specifications

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

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

3.4.6. Reliability and Maintainability Program

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

3.4.6.1. Procedures and Controls.

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

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

b. Provide the Government with reasonable notice of any special R&M program review meetings scheduled with subcontractors so Government representatives may attend at their discretion.

3.4.6.2. Reliability Predictions.

The contractor shall provide reliability predictions based on a defined configuration baseline.

The contractor shall prepare and deliver a top-down indentured reliability report to include the identification of the Mean Time Between Failure (MTBF) for each maintenance-worthy item in addition to identification of the system MTBF using best commercial practices.

3.4.7. Government Access

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

3.5. Software

3.5.1. System Software

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

CDRL A009, Software Version Description (SVD) / DI-IPSC-81442A CDRL A00F, Software Product Specification (SPS) / DI-IPSC-81441A

3.5.2. Computer Software and Technical Data Rights

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

3.5.3. System Safety Tasks

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

3.5.3.1. System Safety Analysis and Assessment

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

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

3.5.3.2. Material Safety Data Sheets

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

3.5.3.3. ESOH Compliance Assessment

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

3.5.3.4. Lithium Battery Safety Qualification

The contractor shall develop a safety data package that shall document and demonstrate the stability of design and validity of the lithium battery selection IAW NAVSEAINST 9310.1B and TM S9310-AQ-SAF-010. The contractor shall provide data from contractor testing of the complete system/item.

The contractor shall document all contractor and Government lithium battery safety assessment efforts in the SAR. The SAR shall include the lithium battery risk assessment, recommendations, procedures and other corrective actions to reduce hazards to an acceptable level.

3.5.3.5. Site Safety

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

3.5.3.6. Hazardous Material Use

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

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

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

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

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

3.5.3.7. Unforeseen Hazardous Material

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

3.5.3.8. Certification

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

(SSHSP) CDRL A00H.

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

3.5.3.9. Accidents

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

3.6. System Test and Evaluation (T&E)

The contractor shall plan, coordinate, establish, and implement a comprehensive Test & Evaluation (T&E) program that shall be designed to verify that the trainer and the integration of all subsystems and equipment meet the technical and operational requirements as stated in this SOW and the USMC SAVT specification.

3.6.1. Responsibility for tests

Unless otherwise specified in the contract, the contractor shall be responsible for the performance of all test requirements. The Government reserves the right to perform tests that are deemed necessary to ensure that delivered supplies and services conform to the contract requirements.

3.6.1.1. Test authority

Test results shall be recorded by a responsible officer of the contractor’s organization during contractor’s inspections and certified by a Procuring Contracting Officer’s (PCO’s) representative. Government inspection results will be recorded by the PCO’s representative.

3.6.1.2. T&E program planning

The contractor shall develop and document the structure and objectives of the trainer T&E program. The contractor shall continuously reassess and refine the T&E program as trainer development, production, and testing progresses.

3.6.1.3. Test resources and facilities

The contractor shall furnish the inspection and testing facilities, equipment, and personnel required to ensure that the training system meets the requirements of the USMC SAVT specification and the contract. The inspection and testing facilities shall provide the environmental conditions required by the tests. The contractor shall ensure that all contractor personnel, test equipment, test facilities, other supporting equipment, spare assemblies and parts, test and data logs, and other items necessary for testing are available for the start and during all phases of testing.

3.6.2. Test methods

The contractor shall prepare the Test/Inspection Report (TIR) CDRL A002 and the Test Procedures (TP) CDRL A003. Test, examination, demonstration, inspection, and verification procedures shall be documented in the TP and shall be written so that a qualified technician can perform the tests. The TP shall include all of the tests, examinations, demonstrations, inspections, and verifications specified in the USMC SAVT specification. When two or more quantitative readings are required simultaneously, the test method shall provide an automated means for data collection to the maximum extent practicable. No calculations, extrapolations, or other mathematical processing shall be required, or allowed, as part of an ongoing test to arrive at the expected results, unless approved by the Govt. Test results shall be documented in the Test/Inspection Report..

CDRL A002, Test/Inspection Report (Test Results) / DI-NDTI-80809B CDRL A003, Test Procedures (TP) / DI-NDTI-80603

3.6.2.1. Test Criteria

The test criteria for tests and examinations shall include both quantitative and qualitative performance data of the operational system(s). Quantitative test criteria shall be used to the maximum extent possible. Qualitative data such as video, photographs, and tape recordings, obtained from operational system or subsystem performance, may be used as test criteria whenever quantitative test criteria is not practical or is not measurable, and the requirement for simulation or stimulation realism can only be judged qualitatively. Government approval is required for any test criteria that is not based on actual operational system performance data.

Where appropriate, test criteria for individual inspections, tests, demonstrations, and examinations shall consist of both quantitative and qualitative test criteria. As a complement to quantitative test results, qualitative comparisons of visual, video, and aural presentations shall be provided.

3.6.2.2. Tolerance Data

Test tolerances shall be identified for all test criteria. Each test tolerance and the source from which the specified tolerances are derived shall be identified in the TP. Specified tolerances shall be derived from the trainer specification, design criteria reports, manufacturing criteria, and operational equipment data.

3.6.2.3. Alignment

The contractor shall perform all necessary equipment alignments prior to the initiation of each increment of the T&E program.

3.6.2.4. Test Log

The contractor shall maintain a log of all subsystem and system tests conducted in-plant and on-site. Entries into the test log shall begin with the start of contractor/subcontractor engineering verification testing and shall continue until the completion of testing. The test log shall show (by date) all equipment adjustments, modifications, failures, removal, replacements, and scheduled and unscheduled maintenance. The log shall be made available to the Government technical representative upon request.

3.6.2.5. Changes During Testing

Changes made in the alignment, programming, or adjustments during the T&E program, shall be recorded in the contractor’s test log. Tests conducted prior to such changes shall be repeated, unless a Government technical representative determines that such…