Attch 1_MCT_SOW_210027_20210930.pdf

SOW 210027

30 September 2021

STATEMENT OF WORK

FOR

Navy Expeditionary Combat Command (NECC)

Navy Expeditionary Logistics Support Group (NAVELSG)

Multi-Crane Trainer (MCT)

DEPARTMENT OF THE NAVY

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12211 SCIENCE DRIVE

ORLANDO, FL 32826

APPROVED BY: DATE:

Kate Williams

Program Manager, LCS MBT

Code GT32100

DISTRIBUTION STATEMENT A – Approved for public release; distribution is unlimited.

ii

Table of Contents

Section Title Page

1. SCOPE

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3. REQUIREMENTS

3.1 General

3.1.1 Program Management

3.1.1.1 Work Planning and Scheduling

3.1.1.2 Integrated Product Teams (IPTs)

3.1.1.3 Quality Management

3.1.1.4 Use of Contractor’s Inspection Equipment

3.1.1.5 Information Management

3.1.1.5.1 Data Management

3.1.2 Security

3.1.2.1 Personnel Security - Background Check (Physical Access to and

Working in DoD Installations)

3.1.2.1.1 Government-Issued Personal Identification Credentials

3.1.3 Cybersecurity

3.1.3.1 Cybersecurity RMF Assess and Authorize (A&A) Support

3.1.3.1.1 Authorization to Operate

3.2 Detailed Tasks

3.2.1 Trainer Design, Development, and Fabrication

3.2.2 Systems Engineering Processes

3.2.2.1 System Requirements Definition

3.2.2.2 System Requirements Analysis

3.2.2.3 Traceability

3.2.2.4 Software Requirements Analysis

3.2.2.4.1 Software Requirements Verification

3.2.2.5 Software Architectural Design

3.2.2.5.1 Software Architectural Design Verification

3.2.2.6 Software Detailed Design

3.2.2.6.1 Software Detailed Design Verification

3.2.2.7 Implementation

3.2.2.7.1 Software Implementation

3.2.2.7.1.1 Software Unit Construction and Testing

3.2.2.7.1.1.1 Software Code Verification

3.2.2.7.2 Software Integration

3.2.2.7.3 Software Integration Verification

3.2.2.7.3.1 Software Qualification Testing

3.2.2.8 System Integration

iii

3.2.2.9 System Qualification Testing

3.2.2.10 Device Transition

3.2.2.10.1 Software Installation

3.2.2.10.2 Software Product

3.2.2.10.2.1 Cold Start Procedures

3.2.2.10.2.2 Installation and Configuration Procedures

3.2.2.10.2.3 Media and Storage Devices

3.2.2.10.2.4 Cold Start and Installation Procedure Media

3.2.2.10.2.5 Automated Processes

3.2.2.10.2.6 Contractor Execution

3.2.2.11 System Validation

3.2.2.11.1 Software Acceptance Support

3.2.2.12 Reliability and Maintainability (R&M) Engineering

3.2.3 Conferences and Reviews

3.2.3.1 Project Kickoff (PK)

3.2.3.2 IPT Meetings

3.2.3.3 Technical Interchange Meeting (TIM)

3.2.4 Commercial and Non-Developmental Items (CaNDI)

3.2.5 Parts Standardization

3.2.5.1 Replacement of Parts

3.2.6 Product Assurance Audits and Inspections

3.2.7 System Test and Evaluation

3.2.7.1 Responsibility for Tests

3.2.7.2 Test Resources and Facilities

3.2.7.3 Test Methods

3.2.7.4 Test Criteria

3.2.7.5 Tolerance Data

3.2.7.6 Test Log

3.2.7.7 Test Environment

3.2.7.8 Changes During Testing

3.2.7.9 Changes After Testing

3.2.7.10 T&E Deficiency Reporting System

3.2.7.10.1 Deficiency Report Review Board

3.2.7.11 T&E Program Components

3.2.7.11.1 Factory Acceptance Test (FAT)

3.2.7.11.2 Government Acceptance Test (GAT)

3.2.7.11.2.1 GAT Exit Criteria

3.2.8 Integrated Logistics Support (ILS) Program

3.2.8.1 Bill of Materials for Logistics and Supply Chain Risk Management

3.2.8.2 COTS Documentation

iv

3.2.8.2.1 Training Device Warranties

3.2.8.3 Training

3.2.8.3.1 Instructor/Operator (I/O) Training Course

3.2.9 Facility Requirements

3.2.9.1 Equipment Installation

3.2.9.2 Electrical

3.2.9.3 Safety

3.2.9.4 Clean up and Repair

v

APPENDICES

Appendix Title Page

A Terms and Definitions

Statement of Work

For NECC Multi-Crane Trainer (MCT)

1. SCOPE

This Statement of Work (SOW) establishes the contractor tasks for the design, fabrication, installation, and test of the Multi-Crane Trainer (MCT) to be located at the Cheatham Annex, Naval Weapons Station Yorktown, Williamsburg, VA.

Definitions of terms applicable to this SOW are included in Appendix A.

2. APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1 Government Documents

SPECIFICATIONS:

Naval Air Warfare Center Training Systems Division (NAWCTSD)

PRF 210028 - NECC Multi-Crane Trainer Specification, dated 30

September 2021

OTHER PUBLICATIONS:

Code of Federal Regulations (CFR)

29 CFR 1910 - Occupational Safety and Health Standards

(OSHA standards are downloadable from http://www.osha.gov)

DoD and Department of the Navy (DoN) Security and Cybersecurity Documents

DODI 8510.01 - Risk Management Framework (RMF) for DoD

Information Technology dated 24 MAY 2016

NIST SP 800-53 National Institute of Standards and Technology (NIST)

Special Publication (SP) 800-53, “Security and Privacy

Controls for Federal Information Systems and

Organizations,” current edition

CNSSI 1253

- Committee on National Security Systems (CNSS)

Instruction No. 1253, Security Categorization and Control

Selection for National Security Systems, dated 27 MAR

(The NISPOM is available at http://www.dtic.mil/whs/directives/corres/pub1.html)

DoD Manuals

DoD 5010-12M - Procedures for Acquisition Management of Technical

Data

The above publication is available at http://www.dtic.mil/whs/directives/corres/pdf/501012m.pdf http://www.osha.gov/ http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pdf/501012m.pdf

United States (U.S.) Code

Title 10, Section 2451 - 2456 - Defense Standardization Program

(U.S Code is downloadable from http://uscode.house.gov/search/criteria.shtml)

United States Army Corps of Engineers

EM 385-1-1, 2014 - Safety – Safety and Health Requirements, date 30

November 2014

(Copies of this document are available from http://www.usace.army.mil/CESO/Pages/EM385-1-1.aspx)

Defense Federal Acquisition Regulations Supplement (DFARS)

DFARS 252.211-7003 - Item Identification and Valuation (Aug 2008)

(DFARS Clauses are downloadable from http://farsite.hill.af.mil/vfdfara.htm)

2.2 Non-Government Documents

INDUSTRY STANDARDS

American National Standards Institute (ANSI)/American Society for Quality (ASQ)/

International Organization for Standardization (ISO)

ANSI/ASQ/ISO Q9000-2015 - Quality Management Systems - Fundamentals and

Vocabulary

ANSI/ASQ/ISO Q9001-2015 - Quality Management Systems - Requirements

ANSI/ASQ/ISO Q9004-2009 - Quality Management Systems - Guidelines for

Performance Improvements

(Copies of the above documents are available from www.ansi.org)

ANSI/Institute of Electrical and Electronics Engineers (IEEE)

IEEE 830-1998 - IEEE Recommended Practice for Software

Requirements Specifications

ANSI/IEEE 1008-1987 - IEEE Standard for Software Unit Testing

IEEE 1233-1998 Edition

(R2002)

- IEEE Guide for Developing System Requirements

Specifications

IEEE 12207-2017 - Systems and Software Engineering – Software Life

Cycle Processes

IEEE 15288-2015 - Systems and Software Engineering – System Life Cycle

Processes

(Copies of this document are available from www.ieee.org or IEEE Service Center, 445 Hoes Lane, Piscataway, NJ 08854-1331.)

National Fire Protection Agency (NFPA)

NFPA - 101 - Life Safety Code 2018

(Copies of this document are available from http://www.nfpa.org/Catalog/ or National Fire Protection

Association, 11 Tracy Drive, Avon, MA 02322) http://uscode.house.gov/search/criteria.shtml http://www.usace.army.mil/CESO/Pages/EM385-1-1.aspx http://farsite.hill.af.mil/VFDFARA.HTM http://www.ansi.org/ http://www.ieee.org/ http://www.nfpa.org/Catalog/

3. REQUIREMENTS

3.1 General

3.1.1 Program Management

The contractor shall organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services. The contractor shall provide the program management, systems engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this SOW and NAWCTSD Specification PRF 210028. The contractor shall measure, record, monitor, and evaluate the progress of the work performed and costs incurred under the contract. The contractor shall provide updates during the monthly IPT meetings. The contractor shall prepare the Integrated Program Management Data and Analysis

Report (IPMDAR) in accordance with (IAW) the Contract Data Requirements List (CDRL)

(B001).

3.1.1.1 Work Planning and Scheduling

The contractor shall develop, document, manage, and apply an Integrated Master Schedule

(IMS) that presents the contractor’s plans and schedules to meet the requirements of the contract.

The contractor shall prepare the IMS IAW the IPMDAR CDRL.

3.1.1.2 Integrated Product Teams (IPTs)

The contractor shall implement an IPT structure for the duration of the contract. IPT membership shall consist of multi-functional stakeholders working together with a product-oriented focus.

3.1.1.3 Quality Management

The contractor shall define, document, manage, and apply a quality management process IAW

IEEE 12207-2017 and ANSI/ASQ/ISO Q9001-2015 (or equivalent quality management system).

The contractor may use ANSI/ASQ/ISO Q9000-2015 and ANSI/ASQ/ISO Q9004-2009 for guidance.

3.1.1.4 Use of Contractor’s Inspection Equipment

The contractor shall make measuring and testing devices available for use by the Government when required to determine conformance with contract requirements. The contractor shall provide the personnel needed to operate such devices and to verify calibration, accuracy, and condition.

3.1.1.5 Information Management

The contractor shall define, document, manage, and apply an information management process

IAW IEEE 12207-2017. The contractor shall include the status of technical data deliveries in the

IPMDAR cited above in 3.1.1.

3.1.1.5.1 Data Management

The contractor shall develop, manage, and implement a data management process for data deliverables. The contractor shall establish and implement procedures to manage the configuration of contractually required data. The contractor shall use DoD 5010-12M as guidance during the preparation of the CDRL items. The contractor can obtain copies of the

Data Item Descriptions (DIDs) cited in the CDRL items from the following web site:

http://quicksearch.dla.mil/qsSearch.aspx. The contractor shall ensure that all data item deliverables are delivered without read-write restrictions and without password protection.

3.1.2 Security

The security requirements specified herein shall apply to the contractor and subcontractors. The contractor shall comply with on-site security regulations related to facility access and building access. Contractor personnel shall possess proper security clearances IAW Form DD-254 of the contract to allow uninhibited access to the space where the trainer is to be installed. The contractor shall safeguard U.S. Government controlled unclassified information (sensitive information) IAW the contractor’s established security plan. The contractor shall enforce these safeguards throughout the life of the contract including the transport and delivery phases and the disposition and storage of controlled unclassified information at contract completion. If the contractor does not have an established security plan that addresses the protection of proprietary, sensitive, or controlled unclassified information, the Government will provide a template for the development of an Operations Security (OPSEC) Plan. Regardless of the contractor's established security plan, the contractor shall comply with the requirements specified in the following subordinate paragraphs.

3.1.2.1 Personnel Security - Background Check (Physical Access to and Working in DoD

Installations)

The Common Access Card (CAC) shall be the principal identity credential for supporting interoperable access to DoD installations, facilities, buildings, controlled spaces, and access to

U.S. Government information systems. A National Agency Check with Local Agency Checks including Credit Check (NACLC) or T3 shall be the minimal requirement for permanent issuance of the credential. The Government may issue the credential upon favorable return of the

Federal Bureau of Investigations (FBI) fingerprint check, pending final favorable completion of the NACLC/T3 or higher. There shall be no additional NACLC/T3 or equivalent submission for an individual holding a valid national security clearance. Access to restricted areas, controlled unclassified information (sensitive information), or Government equipment by contractor personnel shall be limited to those individuals who have been determined trustworthy as a result of the favorable completion of a NACL/T3 (or equivalent) or who are under the escort of cleared personnel. Where escorting such persons is not feasible, a NACLC/T3 (or equivalent) shall be conducted and favorably reviewed by the appropriate DoD component, agency, or activity prior to permitting such access. The contractor shall use the Standard Form 86 (Questionnaire for

Sensitive Positions) in order to obtain the CAC and access to controlled unclassified information.

The contractor shall submit the Standard Form 86 to the NAWCTSD Security Manager for processing.

3.1.2.1.1 Government-Issued Personal Identification Credentials

The contractor and subcontractor(s) shall account for all forms of U.S Government-provided identification credentials (CAC or U.S. Government-issued identification badges) issued to the contractor (or their employees in connection with performance) under the contract. The contractor shall return such identification credentials to the issuing agency at the earliest of the circumstances listed below, unless otherwise determined by the U.S. Government. The http://quicksearch.dla.mil/qsSearch.aspx contracting officer may delay final payment under the contract if the contractor or subcontractor fails to comply with these requirements.

a. When no longer needed for contract performance.

b. Upon completion of the contractor employee’s employment.

c. Upon contract completion or termination

3.1.3 Cybersecurity

The contractor shall design, develop, document, integrate, verify, and deliver a security architecture for the trainer that satisfies the DODI 8510.01 Risk Management Framework (RMF) security control set as defined in NIST SP 800-53R4 for a CNSSI 1253 Security Categorization of an NSS as (Confidentiality=Low), (Integrity=Low), (Availability=Low) and meets the

Cybersecurity performance requirements specified in PRF 210028.

3.1.3.1 Cybersecurity RMF Assess and Authorize (A&A) Support

The contractor shall support the RMF A & A processes to assist the Program Information

Systems Security Officer (ISSO) in obtaining an Authorization to Operate (ATO) for the trainer.

3.1.3.1.1 Authorization to Operate

The contractor shall prepare the Authorization to Operate (ATO) Package IAW the CDRL

(A001).

3.2 Detailed Tasks

3.2.1 Trainer Design, Development, and Fabrication

The contractor shall ensure all systems (including, but not limited to, hardware, software, networking, interfaces, etc.) are COTS to the maximum extent possible. The contractor shall design, document, develop, fabricate, integrate, test, validate, install, and deliver a reconfigurable

Multi-Crane Trainer (MCT) that meets the performance requirements specified in NAWCTSD

Specification PRF 210028.

3.2.2 Systems Engineering Processes

The contractor shall use system engineering processes to transform the performance requirements specified in NAWCTSD Specification PRF 210028 into an effective product, and to verify and validate the functionality of the delivered product.

3.2.2.1 System Requirements Definition

The contractor shall define, document, manage, and apply a requirements definition process

IAW IEEE 12207-2017.

3.2.2.2 System Requirements Analysis

The contractor shall define, document, manage, and apply a requirements analysis process IAW

IEEE 12207-2017 and IEEE 1233-1998 Edition (R2002). The contractor shall analyze the

NAWCTSD Specification PRF 210028 and SOW requirements to identify top level functional requirements. The contractor shall decompose the top level requirements into lower level functional requirements. The contractor shall analyze the interaction between systems, subsystems, and components to identify derived functional requirements. The contractor shall record NAWCTSD Specification PRF 210028 requirements, technical SOW requirements, and contractor decomposed and derived requirements within the Requirements

Traceability/Verification Matrix (RTVM).

3.2.2.3 Traceability

The contractor shall define, document, manage, and apply a process and mechanism to accomplish traceability between the requirements, allocated design baseline, implementation configuration items, and test procedures. The contractor shall utilize an electronic tool (e.g.

Doors, RequisitePro, Access Database, or Excel Spreadsheet) to accomplish the requirement traceability function. Traceability shall be bi-directional. Backward traceability shall permit each RTVM element to explicitly trace to a source reference from a previous stage of development. Forward traceability shall permit each RTVM element to explicitly trace to a reference in a later stage of development. The contractor shall provide the Government access to the traceability tool and its database. The contractor shall prepare the Scientific and Technical

Reports (Requirements Traceability and Verification Matrix (RTVM)) IAW the CDRL (A002).

3.2.2.4 Software Requirements Analysis

The contractor shall define, document, manage, and apply software requirements analysis IAW

IEEE 12207-2017. The contractor shall analyze and define software requirements IAW the criteria within IEEE 830-1998.

3.2.2.4.1 Software Requirements Verification

The contractor shall perform software requirements verification IAW IEEE 12207-2017.

3.2.2.5 Software Architectural Design

The contractor shall define, document, control, maintain, and implement a software architectural design IAW IEEE 12207-2017.

3.2.2.5.1 Software Architectural Design Verification

The contractor shall perform software architectural design verification IAW IEEE 12207-2017.

3.2.2.6 Software Detailed Design

The contractor shall define, document, control, maintain, and implement software detailed design

IAW IEEE 12207-2017.

3.2.2.6.1 Software Detailed Design Verification

The contractor shall perform software detailed design verification IAW IEEE 12207-2017.

3.2.2.7 Implementation

The contractor shall define, document, control, maintain, and perform implementation IAW

IEEE 15288-2015.

3.2.2.7.1 Software Implementation

The contractor shall define, document, control, maintain, and perform software implementation

IAW IEEE 12207-2017.

3.2.2.7.1.1 Software Unit Construction and Testing

The contractor shall define, document, control, maintain, and implement software construction

IAW IEEE 12207-2017. The contractor shall accomplish software unit testing IAW ANSI/IEEE

1008-1987.

3.2.2.7.1.1.1 Software Code Verification

The contractor shall perform software code verification IAW IEEE 12207-2017.

3.2.2.7.2 Software Integration

The contractor shall define, document, control, maintain, and implement software integration

IAW IEEE 12207-2017.

3.2.2.7.3 Software Integration Verification

The contractor shall perform software integration verification IAW IEEE 12207-2017.

3.2.2.7.3.1 Software Qualification Testing

The contractor shall define, document, control, maintain, and implement software qualification testing IAW IEEE 12207-2017.

3.2.2.8 System Integration

The contractor shall define, document, manage, and apply a system integration process IAW

IEEE 12207-2017.

3.2.2.9 System Qualification Testing

The contractor shall define, document, manage, and apply a system verification process IAW

IEEE 12207-2017.

3.2.2.10 Device Transition

The contractor shall define, document, manage, and apply a system transition and installation process IAW IEEE 15288-2015.

3.2.2.10.1 Software Installation

The contractor shall define, document, control, maintain, validate, and implement software installation IAW IEEE 12207-2017.

3.2.2.10.2 Software Product

The contractor shall define, document, control, maintain, validate, and prepare the trainer software. The contractor shall deliver the software, and databases required to meet the performance defined in this SOW and NAWCTSD Specification PRF 210028. The contractor shall deliver the Commercial Item software with the associated vendor manuals, documentation, physical media, warranty information, licenses, and installation/startup/configuration procedures.

The contractor shall transfer to the Government at device acceptance, the Commercial Item software licenses.

3.2.2.10.2.1 Cold Start Procedures

The contractor shall develop, document, control, maintain, validate and prepare, computational subsystem cold start procedures that meet the verification requirements specified in NAWCTSD

Specification PRF 210028. The contractor shall prepare a cold start procedure for each computational subsystem that is delivered with associated software source code. The contractor shall prepare a cold start procedure for each computational subsystem that is composed of contractor acquired discrete components (e.g. computer hardware, operating system, and application software), which are then integrated by the contractor. The contractor shall not use any type of disk image to accomplish a cold-start. The contractor shall develop cold start procedures:

a. For configuring applicable computer hardware settings such as in a Basic Input/Output

System (BIOS) or firmware

b. For installing and configuring each operating system, to include user accounts, network connectivity, device drivers, and Cybersecurity controls

c. For installing and configuring each software application

d. For installing the deliverable source code

e. For performing a software build(s) where executable program(s) are created from deliverable source code

f. For introducing Government-authorized source code changes; where the existing software build is removed and a new build is created

g. That consist of detailed descriptive action to be performed; the expected result following the action; and an area to document abnormalities, discrepancies, errors, and pass/fail status

h. That ensure that complex sequences of cold-start actions are broken down into discrete steps

i. That can be accomplished without referring to external documentation

j. That include listing the physical software media required to perform the cold-start

k. That include Commercial Item software activation data, such as serial numbers and key codes

3.2.2.10.2.2 Installation and Configuration Procedures

The contractor shall develop, document, control, maintain, validate, and prepare the installation and configuration procedures that meet the verification requirements specified in NAWCTSD

Specification PRF 210028. The contractor shall prepare installation and configuration procedures for each computational subsystem acquired as a tightly integrated, ready to use turnkey system. Turnkey describes a Commercial Item that is pre-built, in which everything needed is put together by a vendor and sold as a bundle. The contractor shall develop installation and configuration procedures:

a. For configuring applicable computer hardware settings such as in a BIOS or firmware

b. For restoring the system software, such as the operating system, applications and data, to the original delivered configuration.

c. For configuring the system software for use within the training device, such as user accounts, network connectivity, and Cybersecurity controls

d. That consist of detailed descriptive action to be performed; the expected result following the action; and an area to document abnormalities, discrepancies, errors, and pass/fail status

e. That ensure that complex sequences of installation and configuration actions are broken down into discrete steps

f. That can be accomplished without referring to external documentation

g. That include listing the physical software media required to perform the installation and configuration procedure

h. That include Commercial Item software activation data, such as serial numbers and key codes

3.2.2.10.2.3 Media and Storage Devices

The contractor shall provide to the Government the blank media and mass storage devices necessary to perform each subsystem cold start and installation procedure. The Government will retain custody and control of the media and storage devices created or used by the Government to accomplish testing. The contractor shall provide the additional media and mass storage devices necessary for the contractor’s internal archiving, development, testing, and other engineering and configuration management purposes.

3.2.2.10.2.4 Cold Start and Installation Procedure Media

The contractor shall prepare a unique set of physical media for each computational subsystem.

The contractor shall prepare the physical media required to perform each subsystem cold-start procedure with labeling that:

a. Is formatted consistently

b. Is permanently attached to the physical media

c. Identifies the software vendor name

d. Identifies the software product name

e. Identifies the software version number

f. Identifies the software release date

g. Identifies the contractor’s Configuration Control identifier

h. Identifies the total number of media pieces that compose each configured item

i. Identifies the individual piece number within a multiple piece item, such as “Disk 2 of 5” or “DVD 1 of 3”

3.2.2.10.2.5 Automated Processes

The contractor shall document, control, maintain, validate, and deliver all computational automated processes (e.g., scripts, batch files, job control language, kick-start, and slipstreamed media) in the same manner as software items.

3.2.2.10.2.6 Contractor Execution

The contractor shall execute and validate each subsystem cold start and installation procedure.

The contractor shall perform the entire cold start and installation procedure, step-by-step as written, and document the results of each step. The contractor shall present the results of each contractor-run cold start and installation procedure to the Government for review at the following Test and Evaluation (T&E) event. The contractor shall execute, document, correct and validate each cold start and installation procedure until no discrepancies exist.

3.2.2.11 System Validation

The contractor shall define, document, manage, and apply a system validation process IAW

IEEE 15288-2015 and the system T&E requirements specified herein.

3.2.2.11.1 Software Acceptance Support

The contractor shall define, document, control, and implement software acceptance support IAW

IEEE 12207-2017.

3.2.2.12 Reliability and Maintainability (R&M) Engineering

The contractor shall establish and maintain active and effective R&M programs that meet program objectives. The R&M programs shall ensure that the training system equipment, including Commercial Items (see A.1.1), Commercially available Off-The-Shelf (COTS) items

(see A.1.2), NDI (see A.1.5), and TPE (see A.1.6), meet the R&M requirements specified in

NAWCTSD Specification PRF 210028. The contractor shall include the R&M programs as topics of discussion during the scheduled program reviews.

3.2.3 Conferences and Reviews

The contractor shall conduct, attend, and participate in conferences and reviews to be held at the contractor facility. At the government’s discretion, meetings may be held online in lieu of in-person at the contractor facility. The specific locations, dates, and duration of the conferences shall be as specified in the contract. Conferences and reviews shall be chaired by a Government representative. The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare drawings and other data to aid in the presentations. The contractor shall have key personnel and support available to carry out the conference. The contractor shall prepare the Presentation Material and

Conference Minutes for the conferences and reviews IAW the CDRL (B002/B003). 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.

3.2.3.1 Project Kickoff (PK)

The first conference shall be the PK and shall occur no later than 30 days after contract award.

The purpose of the conference shall be to establish the framework of the contractor and

Government interaction during the performance period of the contract. At the PK, the contractor shall present an IMS showing the critical milestones and supporting events, including logistics, leading to these milestones. The PK shall include the presentation and discussion of information and data relating to:

a. Introduction and contract overview

b. Discussion and clarification of Specification PRF 210028 and SOW requirements

c. Presentation of a complete, accurate, and realistic IMS and detailed schedule with status

d. Identification of the critical paths within the IMS and detailed schedule

e. CDRL delivery schedule and status

f. Logistics

g. Training

h. Technical Documentation

i. Program specific OPSEC and Cybersecurity implementation plans

j. Program life cycle model selection and rationale

k. IPT structure, membership, and responsibilities

l. Action item reporting and status

m. Long lead time item identification and status

n. Updated team contact list (names, IPT memberships, phone numbers, and email addresses)

o. Metrics collection process, analysis, and reporting

3.2.3.2 IPT Meetings

The contractor shall attend and participate in IPT meetings to be conducted throughout the entire contract. IPT meetings shall provide a forum suitable for maintaining a continuous interchange of ideas, issues, and to identify and resolve potential problem areas. IPT meetings shall be documented in the conference minutes.

3.2.3.3 Technical Interchange Meeting (TIM)

The contractor shall conduct three Technical Interchange Meetings (TIM) during the course of the project. The first shall occur no later than 30 days after the PK and will ensure a common understanding of the requirements and expectations, including first draft of the RTVM. The second TIM shall occur about halfway through the project timeline to ensure good progress is being made on the production of the system, include a review of the Test Procedures to be used during the Factory Acceptance Test (FAT) and Government Acceptance Test (GAT), and will include the final RTVM. The third TIM shall occur shortly before FAT and be used to validate that the contractor is ready to conduct the FAT. At the third TIM, the contractor shall present test logs demonstrating previous successful execution of the test procedures that will be run during the FAT. The TIMs shall ensure that the required system performance is fully defined and is traceable to the functional baseline (NAWCTSD Specification PRF 210028). The TIMs shall be considered complete when all Requests For Action (RFAs) are signed off. Regardless of

Government interaction during the TIMs, the contractor shall maintain design responsibility for the system. At the TIMs, the contractor shall:

a. Identify and discuss resource availability to support the schedule

b. Present and discuss the schedule critical path

c. Provide current status vs. critical path

d. Discuss system requirements and the Test Procedures to satisfy the requirements

(1) Show that the functional requirements are traceable to the system requirements

(2) Show that the explicit and derived requirements are quantified and documented

e. Provide a complete program organizational structure

f. Identify relevant contractor Subject Matter Experts (SMEs) to be used during production and testing

g. Address the following applicable functional areas:

(1) Human systems integration

(2) Environment, safety, and occupational health

(3) Test and Evaluation (T&E)

(4) Logistics

(5) Technical Documents

(6) Facilities

(7) Interoperability

(8) Information Assurance (IA)

(9) Quality management

(10) Configuration Management (CM)

(11) Security

h. Review program risks

i. The contractor shall demonstrate that production engineering challenges are resolved, production processes and process controls are in place, parts and materials are on hand, and testing methods are provided.

3.2.4 Commercial and Non-Developmental Items (CaNDI)

The contractor shall fulfill the requirements of the contract through acquisition of CaNDI to the maximum extent practicable. CaNDI proposed by the contractor will be reviewed by the

Government to determine whether each proposed CaNDI component is, in fact, CaNDI. The

Government will also determine the extent to which the proposed CaNDI is practicable for off-the-shelf use within the Government’s logistical environment. The Government reserves the right to perform inspections and tests as deemed necessary to verify the practicability of items proposed as CaNDI for off-the-shelf use in the trainer.

3.2.5 Parts Standardization

The contractor shall comply with the Defense Standardization Program (U.S. Code Title 10, Section 2451 - 2456), which requires the achievement of the highest practicable degree in the standardization of items and practices used through the DOD.

3.2.5.1 Replacement of Parts

The Government reserves the right to inspect parts and materials used to design and manufacture the trainer equipment at any time through the end of any warranty period, to determine that only

Government authorized parts and materials have been used. Use of unauthorized parts and materials shall result in replacement by the contractor with an authorized part or material and correction of the assorted documentation and manuals. If unauthorized parts or materials are allowed to remain as a part of the trainer equipment, consideration shall be given to the

Government by the contractor. The consideration offered shall be reviewed as to its adequacy by the technical activity and negotiated by the Contracting Officer.

3.2.6 Product Assurance Audits and Inspections

The Government may perform audits and inspections of contractor conformance to contractual requirements at any time during the performance of the contract. The contractor shall make non-deliverable product assurance documentation and data available to the Government during these audits and inspections. The Government will provide notice to the contractor prior to conducting audits and inspections.

3.2.7 System Test and Evaluation

The contractor shall plan, coordinate, establish, and implement a T&E program 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 NAWCTSD Specification PRF 210028.

3.2.7.1 Responsibility for Tests

Unless otherwise specified herein, the contractor shall perform the specified test and inspections.

The Government reserves the right to perform tests and inspections that are deemed necessary to ensure that delivered supplies and services conform to the contract requirements.

3.2.7.2 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 NAWCTSD Specification

PRF 210028 and the contract. The inspection and testing facilities shall provide the environmental conditions required by the tests specified herein. The contractor shall ensure that the 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 the required testing events.

3.2.7.3 Test Methods

Tests shall be performed IAW the Government-accepted Test Procedure (TP) document and other Government-accepted test plans. 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 demonstrate compliance with all the requirements in the NAWCTSD Specification PRF 210028. Test results shall be documented in the

Test/Inspection Report. The contractor shall prepare the Test Procedures and the Test/Inspection

Report IAW the CDRLs (A003/A004).

3.2.7.4 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 audio 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.

3.2.7.5 Tolerance Data

Test tolerances shall be identified for all test criteria. Specified tolerances may be derived from the trainer specification, design criteria reports, manufacturing criteria, and operational equipment data.

3.2.7.6 Test Log

The contractor shall maintain a log of subsystem and system tests conducted in-plant and on-site.

Entries into the test log shall begin with the start of contractor and subcontractor engineering verification testing and continue until the completion of testing. The test log shall show (by date) equipment adjustments, modifications, failures, removal, replacements, and scheduled and unscheduled maintenance. The contractor shall make the test log available to the Government technical representative upon request.

3.2.7.7 Test Environment

The contactor shall conduct testing in a secure environment that meets the cybersecurity standards in section 3.1.3.

3.2.7.8 Changes During Testing

Changes made 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 changes have not invalidated the related test data.

3.2.7.9 Changes After Testing

Modifications or changes in design, which are determined to be necessary as a result of testing, shall be recorded in the contractor’s test log. Tests run prior to such modifications shall be repeated unless a Government technical representative determines that such changes have not invalidated the related test data.

3.2.7.10 T&E Deficiency Reporting System

The contractor shall implement a deficiency reporting system for tracking (identification, assignment, status, progress, resolution) hardware and software problems. In addition, the deficiency reporting system shall be used to track documentation problems including technical documentation and data errors. Government Deficiency Reports (DRs) shall be recorded and classified as Priority I through Priority III through the Deficiency Report Review Board (DRRB).

The Government DR categories are defined in A.1.3.

3.2.7.10.1 Deficiency Report Review Board

The DRRB membership shall include Government and contractor personnel. The DRRB members and processes shall be determined after contract award as part of the TIM meetings.

The DRRB will review and classify DRs.

3.2.7.11 T&E Program Components

The T&E program shall consist of the test phases described below:

a. Factory Acceptance Test (FAT) - At contractor facility prior to shipping

b. Government Acceptance Test (GAT) - After delivery and installation at Cheatham

Annex, Naval Weapons Station Yorktown, Williamsburg, VA

3.2.7.11.1 Factory Acceptance Test (FAT)

The contractor shall perform in-plant FAT IAW the Contractor-provided Government-accepted

Test Procedures (TP). The contractor shall conduct the tests incrementally and certify by signature that the specific test(s) have been completed and the documented results are correct and comply with NAWCTSD Specification PRF 210028 requirements. FAT shall include a complete run of the Government-accepted TP from start to finish. The contractor shall annotate procedural changes made and shall provide a copy of the annotated TP to the Government prior to the completion of the FAT. The contractor shall document the results in the Test/Inspection

Report. The contractor shall record tests results that do not comply with specification requirements as deficiencies. The contractor shall correct the deficiencies found prior to delivery.

3.2.7.11.2 Government Acceptance Test (GAT)

Upon completion of the installation of the trainer on-site, the contractor shall perform GAT IAW the Government-accepted TP. The contractor shall conduct the tests incrementally and certify by signature that the specific test(s) have been completed and the documented results are correct and comply with NAWCTSD Specification PRF 210028 requirements. GAT shall include a complete run of the Government-accepted TP from start to finish. The contractor shall document that the test procedures have been run start-to-finish as a complete test, without segregation of elements of individual tests. The contractor shall annotate procedural changes made and shall provide a copy of the annotated TP to the Government prior to the completion of the GAT. The contractor shall document the results in the Test/Inspection Report. The contractor shall record tests results that do not comply with specification requirements as deficiencies. The Government reserves the right to perform such additional tests as deemed necessary to ensure compliance with the specified requirements. Deficiencies found during GAT shall be corrected by the contractor and verified by the Government test team prior to Government acceptance of the trainer.

3.2.7.11.2.1 GAT Exit Criteria

The exit criteria shall consist of Government concurrence with the following:

a. A cold-start has been successfully performed to establish final software baseline.

b. Deficiencies identified have been documented, categorized for severity, and tracked to final resolution (DR sign-off and dismissal).

c. Priority I*, I, II, and III deficiencies have been corrected.

d. A complete TP test has been run after the final DR ready for re-test, within acceptable regression testing guidelines as determined by the Government.

e. Government mission testing has been performed successfully.

f. A copy of the final TP test results has been provided with the results recorded in the contractual testing documentation, including date/time of final results, and red-lines

(when necessary).

g. CM baseline (software and hardware) has been maintained throughout DR correction.

CM deficiencies identified during GAT have been corrected.

h. GAT has demonstrated that the test and support equipment necessary to execute the complete TP testing were used, documented, in calibration, and functioned properly.

i. Required QA standards have been satisfied and achieved.

j. The contractor’s QA representative, contractor’s test manager, and Government’s test director have signed off testing as complete.

3.2.8 Integrated Logistics Support (ILS) Program

The purpose of the ILS IPT is to review and discuss the status of the ILS program under development by the contractor and its subcontractors and all technical and administrative ILS problems that are beyond the scope of Engineering Progress and Design Conferences. The ILS

IPT shall identify and resolve potential problem areas that could affect the timely planning, implementation, and verification of the support program. All ILS elements shall be presented to the IPT. Specialists from the various ILS disciplines, including facilities engineering, shall attend the IPT meetings as necessary to discuss specific aspects of the ILS program. Additionally, the

ILS IPT shall review and discuss facility related items including, but not limited to, facility provided trainer connection points, and the design, and installation. If necessary, a facility working group shall be assembled to address facility concerns.

3.2.8.1 Bill of Materials for Logistics and Supply Chain Risk Management

a. The contractor shall prepare a Bill of Materials for Logistics and Supply Chain Risk

Management database in order to facilitate Government assessment of the design status, conduct logistics planning and analysis, influence program decisions, and verify that contractor performance meets system supportability requirements.

b. The contractor shall prepare the Bill of Materials for Logistics and Supply Chain Risk

Management IAW the CDRL (C001).

c. The BOM shall be developed in a manner to allow hardware items to be sorted by training device.

3.2.8.2 COTS Documentation

COTS documentation shall be provided by the contractor. COTS documentation for common equipment (example keyboards, mice, monitors, video cards, switches) is not required unless that equipment requires special modifications or set up, or the COTS manual includes detailed troubleshooting procedures, or the COTS manual contains detailed operational procedures required for the operation of the equipment. The contractor shall:

a. Ensure that all COTS documentation conforms to contract requirements.

b. Review the documentation and correct deficiencies or deviations in the manuals prior to the submission.

c. Ensure that all COTS documentation contains:

(1) Operation Instructions

(2) Testing and Troubleshooting Procedures

(3) Wiring Diagrams

(4) Parts Listings

(5) Maintenance Pertinent Information

(6) Drawings

d. Ensure all documentation is written in Standard American English (SAE) and IAW

CDRL requirements (E001).

3.2.8.2.1 Component Warranties

The contractor shall transfer to the Government ownership of all COTS warranties, guarantees, and services remaining in effect at device acceptance of each trainer. All COTS units shall have a warranty of no less than one year, if available from the COTS supplier that begins at

Government acceptance of the trainer. The contractor shall identify items that have extended warranties available and the cost associated with each. The COTS warranties shall include on-site repair services if available. The contractor shall identify the COTS equipment and delineate the warranties, guarantees, and service due the Government upon the Government taking possession of the equipment. The contractor shall prepare the Warranty Performance Report

IAW the CDRL (D001).

3.2.8.3 Training

The contractor shall develop and present the training course specified in the sub-section below.

The contractor shall provide training for Government Instructor/Operators. The contractor shall develop training documentation that support the training courses that will be conducted. The contractor shall prepare the following training documentation IAW the CDRL (F001).

a. Training Conduct Support Document (TCSD): Instructor/Operator Training

3.2.8.3.1 Instructor/Operator (I/O) Training Course

The contractor shall develop and conduct a five-day train-the-instructor training course; one day allotted for each crane type and the fifth day for the overall system. The training shall provide the necessary skills for instructors to operate the trainer and to train other personnel in the operation of the trainer. The class shall be sized to train 10 instructors.

3.2.9 Facility Requirements

The contractor shall follow federal and local safety regulations, electrical, building, and fire codes. All trainer facility equipment and installation work described herein shall be IAW the publications listed below. Where the UFC publications conflict with other publication in this section, the UFC shall take precedence.

3.2.9.1 Equipment Installation

The contractor shall deliver, off-load, assemble, and install training device equipment and support systems. During the installation, the contractor shall be responsible for opening, safeguarding, and closing all means of access into the training facility and training equipment.

The contractor shall be responsible for, and provide all the support equipment, special handling equipment, data, and qualified maintenance personnel needed to support the trainer equipment installation effort. The contractor shall be responsible for all damage to the equipment during removal, transportation, off-loading, installation, and test.

3.2.9.2 Electrical

The contractor shall verify sufficient facility provided electrical power and cooling to properly operate the training system. All electrical and mechanical work shall be performed IAW the requirements of Specification PRF 210028. The contractor shall provide and install the conduit and cable to connect the training device upgrades to the facility power. Use plenum rated communication cabling for all wiring run above ceilings and underneath raised flooring. All non-plenum rated cabling shall be installed in electric metallic tube (EMT). Any electrical work performed under this contract shall be performed by a locally licensed electrician. The contractor shall submit copies of the proposed licensed electrical subcontractor for Navy Facilities

Department (NAVFAC) review.

3.2.9.3 Safety

The contractor shall conform to the OSHA requirements for installation throughout the time the work is being performed. The contractor shall protect the lives and health of employees and other persons and prevent damage to property, materials, supplies, and equipment in accordance with

EM 385-1-1, 2014, NFPA - 101, and 29 CFR 1910. Prior to commencement of the work, the contractor shall meet with the Government to discuss and develop mutual understandings relative to the administration of safety per NAVFAC.

3.2.9.4 Clean up and Repair

The contractor shall clean dirt, spills, and debris, and remove and dispose of all waste resulting from contractor actions related to this trainer installation IAW Base safety and environmental management policies and procedures.