LVCMS_Base_SOW.pdf

SOW XXX

25 April 2013

STATEMENT OF WORK

FOR THE

LIVE, VIRTUAL, CONSTRUCTIVE MODELING & SIMULATION (LVCMS)

ANTI-SUBMARINE WARFARE VIRTUAL AT-SEA TRAINING SYSTEMS (ASW VAST)

INDEFINITE DELIVERY/INDEFINITE

QUANTITY CONTRACT (ID/IQC)

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12350 RESEARCH PARKWAY

ORLANDO, FL 32826-3275

APPROVED BY: DATE:

Signature Authority #1

Program Management Office

Signature Authority #2

Engineering Management Office

Signature Authority #3

Logistics Management Office ii

Table of Contents

Section Title Page

1. SCOPE

1.1 Goals and Objectives

1.2 Background

1.3 Definitions

1.3.1 Commercial Item

1.3.2 Initial Support Kit (ISK)

1.3.3 Non-Developmental Item (NDI)

1.3.4 Trainer-Peculiar Equipment (TPE)

1.3.5 Interim Contractor Support (ICS)

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3. REQUIREMENTS

3.1 General Requirements

3.1.1 Scope of Tasking

3.1.2 Method of Tasking

3.1.2.1 SOW Approach

3.1.3 Deliverables

3.1.4 Program and Engineering Management

3.1.4.1 Work Planning and Scheduling

3.1.4.2 Risk Management

3.1.4.3 Cost Reporting

3.1.4.4 Subcontractor Management and Reporting

3.1.4.5 Integrated Product Teams

3.1.5 Information Management

3.1.5.1 Infoshare Website

3.1.5.2 Government/Industry Data Exchange Program (GIDEP)

3.1.6 Security

3.1.6.1 Security Requirements for DOs Involving Classified Information

3.1.6.1.1 Operations Security (OPSEC)

3.1.6.2 Security Requirements for DOs Involving Unclassified

Information

3.1.6.2.1 Personnel Security - Background Check (Physical Access to and

Working with DoD Installations)

3.1.6.2.2 Personnel Security – Background Checks (Contractor Facility)

3.1.6.2.3 Contractor – Owned Unclassified Network Security

3.1.6.2.4 Information Security Requirements for Protection of Unclassified

DoD Information On Non-DoD Systems iii

3.1.6.2.5 Information Assurance and Personnel Security Requirements for

Accessing Government Information Technology (IT) Systems -

Suitability/Positions of Public Trust

3.1.6.2.6 Information Security Requirements for Protection of Unclassified

DoD Information On Non-DoD Systems

3.1.7 Information Assurance

3.1.7.1 Third Party Software

3.1.7.2 Software Management System

3.1.7.3 Backup Management System

3.2 Detailed Technical Requirements

3.2.1 Post Award Conference CLIN 0001 (FFP)

3.2.1.1 Post Award Conference (PAC) for Base ID/IQC Award

3.2.2 Trainer Systems CLIN 0002 (FFP)

3.2.2.1 New Training Systems

3.2.2.1.1 Systems Engineering Processes

3.2.2.1.2 System Architectural Design

3.2.2.1.3 System Requirements Definition

3.2.2.1.4 System Requirements Analysis

3.2.2.1.5 Traceability

3.2.2.2 Modifications and Upgrades to Existing Training Systems

3.2.2.2.1 Systems Engineering Processes

3.2.2.2.2 System Architectural Design

3.2.2.2.3 System Requirements Definition

3.2.2.2.4 System Requirements Analysis

3.2.2.2.5 Traceability

3.2.2.3 Engineering Corrections

3.2.2.4 Software Development

3.2.2.4.1 Software Upgrades to Existing Simulations

3.2.2.4.1.1 Analysis, Design, and Development of a Modified Instructor

Station

3.2.2.4.1.2 Analysis, Design, and Development of Databases and Database

Editors

3.2.2.4.2 Software Requirements Analysis

3.2.2.4.2.1 Software Requirements Verification

3.2.2.4.3 Software Architectural Design

3.2.2.4.4 Software Detailed Design

3.2.2.4.4.1 Human Factors Engineering (HFE)

3.2.2.4.4.2 Interoperability

3.2.2.4.4.3 Software Detailed Design Verification

3.2.2.4.4.4 Programming High Order Language(s) (HOL) Selection

3.2.2.4.5 Implementation

iv

3.2.2.4.5.1 Software Implementation

3.2.2.4.5.2 Software Integration

3.2.2.4.5.3 Software Version Description

3.2.2.4.6 Software Product

3.2.2.4.6.1 Cold Start procedures

3.2.2.4.7 Configuration Management Program

3.2.2.4.8 Data Management

3.2.2.4.9 Item Unique Identification (IUID) Assignment

3.2.2.4.10 Conferences and Reviews

3.2.2.4.10.1 Security Requirements Review (SecRR)

3.2.2.4.11 Kick-Off Meeting for Contract Delivery Orders

3.2.2.4.11.1 System Requirements Review/System Functional Review

(SRR/SFR)

3.2.2.4.11.2 IPT Meetings

3.2.2.4.11.3 In-Process Reviews (IPRs)

3.2.2.4.11.4 Preliminary Design Review (PDR)

3.2.2.4.11.5 Critical Design Review (CDR)

3.2.2.4.11.6 Test Readiness Review (TRR) Conference

3.2.2.5 Presentation and Publication Products

3.2.2.5.1 Documentation

3.2.2.5.1.1 Technical Documentation

3.2.2.5.1.2 Technical Documentation (TD) Reviews

3.2.2.6 Information Assurance

3.2.2.6.1 Software Integrity Testing and Certification

3.2.2.6.2 IA Compliance

3.2.2.7 System Test and Evaluation (T&E)

3.2.2.7.1 Responsibility for Tests

3.2.2.7.2 Test Authority

3.2.2.7.3 T&E Program Planning

3.2.2.7.4 Test Resources and Facilities

3.2.2.7.5 Test Methods

3.2.2.7.6 Test Log

3.2.2.7.7 T&E Deficiency Reporting System

3.2.2.7.7.1 Deficiency Report (DR) Categories

3.2.2.7.8 T&E Program Components

3.2.2.7.8.1 In-process Inspections

3.2.2.7.8.2 Contractor Preliminary Inspection (CPI) (Developmental Testing, DT-1)

3.2.2.7.8.3 Test Readiness Review (TRR)

3.2.2.7.8.4 Conformance Inspections

3.2.2.7.8.4.1 Functional Configuration Audit (FCA)

v

3.2.2.7.8.4.1.1 Government Preliminary Inspection (GPI) (Developmental

Testing, DT-2)

3.2.2.7.8.4.1.2 Contractor Final Inspection (CFI) (Developmental Testing, DT-3)

3.2.2.7.8.4.1.3 Government Final Inspection (GFI) (Developmental Testing, DT-

4)

3.2.2.7.8.4.1.4 Joint Final Inspection (JFI) (Developmental Testing, DT-5)

3.2.2.8 Hardware Development

3.2.2.8.1 Hardware Upgrades to Existing Trainer Installations

3.2.2.8.2 Commercial and Non-Developmental Items (CaNDI)

3.2.2.8.3 Parts Standardization

3.2.2.8.4 Parts Management

3.2.2.8.5 Product Assurance Audits and Inspections

3.2.2.8.5.1 Physical Configuration Audit (PCA)

3.2.2.8.6 Installation and Configuration procedures

3.2.2.8.6.1 Automated Processes

3.2.2.8.7 System Validation

3.2.2.8.8 Electromagnetic Environmental Effects (E

) Engineering

3.2.2.8.8.1 Electrostatic Discharge (ESD) Management

3.2.2.8.9 Reliability and Maintainability (R&M) Engineering

3.2.2.8.10 Quality Management System (QMS) Requirements

3.2.2.8.11 Control of GFE

3.2.2.9 Integrated Logistics Support (ILS) Requirements

3.2.2.9.1 Inventory Management

3.2.2.9.2 Buy Through the Prime (BTTP)

3.2.2.10 Training Program

3.2.2.11 Travel

3.2.2.12 Research Products – Studies, Data, Analysis, Documentation

3.2.3 Trainer Systems CLIN 0003 (CPFF)

3.2.3.1 New Training Systems

3.2.3.1.1 Systems Engineering Processes

3.2.3.1.2 System Architectural Design

3.2.3.1.3 System Requirements Definition

3.2.3.1.4 System Requirements Analysis

3.2.3.1.5 Traceability

3.2.3.2 Modifications and Upgrades to Existing Training Systems

3.2.3.2.1 Systems Engineering Processes

3.2.3.2.2 System Architectural Design

3.2.3.2.3 System Requirements Definition

3.2.3.2.4 System Requirements Analysis

3.2.3.2.5 Traceability

3.2.3.3 Engineering Corrections

vi

3.2.3.4 Software Development

3.2.3.4.1 Software Upgrades to Existing Simulations

3.2.3.4.1.1 Analysis, Design, and Development of a Modified Instructor

Station

3.2.3.4.1.2 Analysis, Design, and Development of Databases and Database

Editors

3.2.3.4.2 Software Requirements Analysis

3.2.3.4.2.1 Software Requirements Verification

3.2.3.4.3 Software Architectural Design

3.2.3.4.4 Software Detailed Design

3.2.3.4.4.1 Human Factors Engineering (HFE)

3.2.3.4.5 Interoperability

3.2.3.4.5.1 Software Detailed Design Verification

3.2.3.4.5.2 Programming High Order Language(s) (HOL) Selection

3.2.3.4.6 Implementation

3.2.3.4.6.1 Software Implementation

3.2.3.4.6.2 Software Integration

3.2.3.4.6.3 Software Version Description

3.2.3.4.7 Software Product

3.2.3.4.7.1 Cold Start procedures

3.2.3.5 Configuration Management Program

3.2.3.6 Data Management

3.2.3.7 Item Unique Identification (IUID) Assignment

3.2.3.7.1 Conferences and Reviews

3.2.3.7.1.1 Security Requirements Review (SecRR)

3.2.3.7.2 Kick-Off Meeting for Contract Delivery Orders

3.2.3.7.2.1 System Requirements Review/System Functional Review

(SRR/SFR)

3.2.3.7.2.2 IPT Meetings

3.2.3.7.2.3 In-Process Reviews (IPRs)

3.2.3.7.2.4 Preliminary Design Review (PDR)

3.2.3.7.2.5 Critical Design Review (CDR)

3.2.3.7.2.6 Test Readiness Review (TRR) Conference

3.2.3.8 Presentation and Publication Products

3.2.3.8.1 Documentation

3.2.3.8.1.1 Technical Documentation

3.2.3.8.1.2 Technical Documentation (TD) Reviews

3.2.3.9 Information Assurance

3.2.3.9.1 Software Integrity Testing and Certification

3.2.3.9.2 IA Compliance

3.2.3.10 System Test and Evaluation (T&E)

vii

3.2.3.10.1 Responsibility for Tests

3.2.3.10.2 Test Authority

3.2.3.10.3 T&E Program Planning

3.2.3.10.4 Test Resources and Facilities

3.2.3.10.5 Test Methods

3.2.3.10.6 Test Log

3.2.3.10.7 T&E Deficiency Reporting System

3.2.3.10.7.1 Deficiency Report (DR) Categories

3.2.3.10.8 T&E Program Components

3.2.3.10.8.1 In-process Inspections

3.2.3.10.8.2 Contractor Preliminary Inspection (CPI) (Developmental Testing, DT-1)

3.2.3.10.8.3 Test Readiness Review (TRR)

3.2.3.10.8.4 Conformance Inspections

3.2.3.10.8.4.1 Functional Configuration Audit (FCA)

3.2.3.10.8.4.1.1 Government Preliminary Inspection (GPI) (Developmental

Testing, DT-2)

3.2.3.10.8.4.1.2 Contractor Final Inspection (CFI) (Developmental Testing, DT-3)

3.2.3.10.8.4.1.3 Government Final Inspection (GFI) (Developmental Testing, DT-

4)

3.2.3.10.8.4.1.4 Joint Final Inspection (JFI) (Developmental Testing, DT-5)

3.2.3.11 Hardware Development

3.2.3.11.1 Hardware Upgrades to Existing Trainer Installations

3.2.3.11.2 Commercial and Non-Developmental Items (CaNDI)

3.2.3.11.3 Parts Standardization

3.2.3.11.4 Parts Management

3.2.3.11.5 Product Assurance Audits and Inspections

3.2.3.11.5.1 Physical Configuration Audit (PCA)

3.2.3.11.6 Installation and Configuration procedures

3.2.3.11.6.1 Automated Processes

3.2.3.11.7 System Validation

3.2.3.11.8 Electromagnetic Environmental Effects (E

) Engineering

3.2.3.11.8.1 Electrostatic Discharge (ESD) Management

3.2.3.11.9 Reliability and Maintainability (R&M) Engineering

3.2.3.11.10 Quality Management System (QMS) Requirements

3.2.3.11.11 Control of GFE

3.2.3.12 Integrated Logistics Support (ILS) Requirements

3.2.3.12.1 Inventory Management

3.2.3.12.2 Buy Through the Prime (BTTP)

3.2.3.13 Training Program

3.2.3.14 Travel

viii

3.2.3.15 Research Products – Studies, Data, Analysis, Documentation

3.2.4 Training Event Technical Products CLIN 0004 (FFP)

3.2.4.1 Unit Level Training (ULT) and Fleet Synthetic Training (FST)

Participation

APPENDICES

Appendix Title Page

A Sample CDRL Requirements

B Acronym List

Statement of Work

Live, Virtual, Constructive Modeling & Simulation (LVCMS)

Anti-Submarine Warfare Virtual At-Sea Training Systems (ASW VAST)

Indefinite Delivery/Indefinite Quantity Contract (ID/IQC)

1. SCOPE

This Statement of Work (SOW) establishes the requirements for the LVCMS ASW VAST

ID/IQC.

1.1 Goals and Objectives

The Naval Air Warfare Center Training Systems Division (NAWCTSD) goals and objectives are to acquire the capability to design, develop, fabricate, test, modify, integrate, test, deliver, and maintain LVCMS ASW VAST training and simulation systems including aircraft and surface ship representations. The NAWCTSD intent is to establish a single award contract to a highly qualified contractor possessing excellent business practices and technical capabilities in order to increase responsiveness and flexibility in meeting customer needs.

1.2 Background

The LVCMS and ASW VAST family of training systems are built upon a common core foundation of sensor simulation and signal processing software. LVCMS ASW VAST systems also use Commercial Off-the-Shelf (COTS) hardware and Linux and Windows operating systems to emulate, simulate, and/or stimulate various Naval tactical systems for training purposes. The LVCMS and ASW VAST family of training systems are networked, PC-based deployable trainers designed to support integrated and coordinated ASW tactical training, Anti-Access Area-Denial (A2AD) and Cyber Warfare using Joint Semi Automated

Forces (JSAF) Navy Training Baseline (NTB) simulation. The current training system configuration is comprised of personal computers (PC), each PC system representing a mission training station in a particular aircraft (i.e. SH-60B, SH-60F, P-3C ), Ship-board system or combat systems which, when in a networked environment, allow for integrated mission training.

1.3 Definitions

The following definitions apply to this SOW.

1.3.1 Commercial Item

Per the Federal Acquisition Regulations, Part 2.101, “Commercial Item” means:

a. Any item, other than real property, that is of a type customarily used by the general public or by non-governmental entities for purposes other than governmental purposes, and--

(1) Has been sold, leased, or licensed to the general public; or,

(2) Has been offered for sale, lease, or license to the general public;

b. Any item that evolved from an item described in paragraph a. of this definition through advances in technology or performance and that is not yet available in the commercial marketplace, but will be available in the commercial marketplace in time to satisfy the delivery requirements under a Government solicitation;

c. Any item that would satisfy a criterion expressed in paragraphs a. or b. of this definition, but for--

(1) Modifications of a type customarily available in the commercial marketplace;

or

(2) Minor modifications of a type not customarily available in the commercial marketplace made to meet Federal Government requirements. Minor Modifications means modifications that do not significantly alter the non-governmental function or essential physical characteristics of an item or component, or change the purpose of a process. Factors to be considered in determining whether a modification is minor include the value and size of the modification and the comparative value and size of the final product. Dollar values and percentages may be used as guideposts, but are not conclusive evidence that a modification is minor;

d. Any combination of items meeting the requirements of paragraphs a., b., c., or e. of this definition that are of a type customarily combined and sold in combination to the general public;

e. Installation services, maintenance services, repair services, training services, and other services if--

(1) Such services are procured for support of an item referred to in paragraphs a., b., c., or d. of this definition, regardless of whether such services are provided by the same source or at the same time as the item; and

(2) The source of such services provides similar services contemporaneously to the general public under terms and conditions similar to those offered to the Federal

Government;

f. Services of a type offered and sold competitively in substantial quantities in the commercial marketplace based on established catalog or market prices for specific tasks performed or specific outcomes to be achieved and under standard commercial terms and conditions. For purposes of these services--

(1) “Catalog price” means a price included in a catalog, price list, schedule, or other form that is regularly maintained by the manufacturer or vendor, is either published or otherwise available for inspection by customers, and states prices at which sales are currently, or were last, made to a significant number of buyers constituting the general public; and

(2) “Market prices” means current prices that are established in the course of ordinary trade between buyers and sellers free to bargain and that can be substantiated through competition or from sources independent of the offerors.

g. Any item, combination of items, or service referred to in paragraphs a. through f. of this definition, notwithstanding the fact that the item, combination of items, or service is transferred between or among separate divisions, subsidiaries, or affiliates of a contractor; or

h. A Non-Developmental Item, if the procuring agency determines the item was developed exclusively at private expense and sold in substantial quantities, on a competitive basis, to multiple State and local governments.

1.3.2 Initial Support Kit (ISK)

The ISK includes:

a. Spares (repairable items) and repair parts that are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

b. Spares that support vendor hardware utilized by the device, which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

c. Support items that are not an integral part of the end item, but are required to inspect, test, calibrate, service, repair, or overhaul the end item, which are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

d. Items required for support of the trainer system (excluding common hand tools), which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

1.3.3 Non-Developmental Item (NDI)

Per the Federal Acquisition Regulations, Part 2.101, NDI means:

a. Any previously developed item of supply used exclusively for governmental purposes by a Federal agency, a State or local government, or a foreign government with which the

United States has a mutual defense cooperation agreement;

b. Any item described in paragraph a. of this definition that requires only Minor

Modifications (see 1.3.1, c., (2)) or modifications of a type customarily available in the commercial marketplace in order to meet the requirements of the procuring department or agency; or

c. Any item of supply being produced that does not meet the requirements of paragraph

a. or b., solely because the item is not yet in use.

1.3.4 Trainer-Peculiar Equipment (TPE)

The following types of equipment are defined as TPE:

a. Trainer equipment which has not been classified by the Government as a Commercial

Item, Government-Furnished Equipment (GFE), NDI, or Contractor Acquired Operational

Equipment (CAOE).

b. Commercial Item, NDI, GFE, or CAOE, that:

(1) Needs other than Minor Modifications (see 1.3.1, c., (2)) or modifications which are not of a type customarily available in the commercial marketplace to meet the requirements of the Delivery Order (DO), or:

(2) Does not have sufficient existing product documentation for Government logistic support.

1.3.5 Interim Contractor Support (ICS)

ICS consists of those technical and advisory services provided to the Government by the prime training system contractor at the training system installation site(s) by trained engineers and technicians. ICS requirements are those needed to advise and support

Government maintenance personnel in operating and maintaining the training system during the initial support period. ICS may consist of the following:

a. Identification and procurement of spares and repair parts.

b. All levels of maintenance and repair including labor, material, engineering, and logistics support.

c. Trainer operation.

d. Over the shoulder training

e. Compilation of usage and performance data.

f. Maintaining inventory of spares.

2. APPLICABLE DOCUMENTS

The following documents of the issue listed form a part of this SOW to the extent specified herein. In the event of conflict between the 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.

American National Standards Institute (ANSI) information and documents can be found at website http://www.ansi.org. Institute of Electrical and Electronics Engineers (IEEE) information and documents can be found at website http://www.ieee.org.

2.1 Government Documents

Department of Defense (DoD) and Department of the Navy (DoN) Security and Information

Assurance (IA) Instructions, Handbooks, Guides, and Policy Documents:

a. DoDI 8500.2 – Information Assurance (IA) Implementation, dated 6 February 2003

b. ISA Security Technical Implementation Guide (STIG) – Application Security and

Development STIG

c. DoDI 8510.01 – Information Assurance Certification and Accreditation Process

(DIACAP) 28 November 2007

d. DoN DIACAP Handbook (Unnumbered) – DoN DoD Information Assurance

Certification and Accreditation Process (DIACAP) Handbook series, dated 15 July

e. DoD 8570.01-M - Information Assurance Workforce Improvement Program dated 19

December 2005 (Incorporating Change 2, dated April 20, 2010)

The preceding documents are downloadable from:

http://nawctsd.navair.navy.mil/Resources/Library/IA/Index.cfm and DoD STIGs guides are at http://iase.disa.mil/

2.2 Non-Government Documents

Unless otherwise noted elsewhere in the document, the latest version of the listed documents shall apply.

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

(ASQC)

a. Quality Management and Quality Assurance Standards - Guidelines for Selection and

Use http://www.ansi.org/ http://www.ieee.org/ http://nawctsd.navair.navy.mil/Resources/Library/IA/Index.cfm http://iase.disa.mil/

b. Quality Systems - Model for Quality Assurance in Design/Development, Production, Installation, and Servicing

c. Quality Management Systems - Guidelines for Performance Improvements

d. Quality Management and Quality System Elements (Copies of the above documents are available from www.ansi.org or Global Engineering Documents, 15

Inverness Way, East Englewood, CO 80112.)

IEEE/Electronic Industries Association (EIA)

a. IEEE Standard for Distributed Interactive Simulation (DIS, Series 1278)

b. Industry Implementation of International Standard International Organization for

Standardization/International Electrotechnical Commission (ISO/IEC) 12207:1995 –

c. Standard for Information Technology - Software Life Cycle Processes (Copies of the above documents are available from http://www.ieee.org/ or IEEE Service Center, 445 Hoes

Lane, Piscataway, NJ 08854-1331.)

HLA Interface Specifications (obtainable by email to HLA@dmso.mil)

a. HLA Interface Specification Annex B: C++ API

b. HLA Interface Specification Version 1.3

c. HLA Object Model Template Specification (Version 1.3)

d. HLA Rules (Version 1.3)

3. REQUIREMENTS

3.1 General Requirements

Under this ID/IQC, the contractor shall provide engineering disciplines required to design, develop, integrate, test, deliver, and sustain the LVCMS and ASW VAST family of training systems, to include installation at the various locations. Detailed requirements and appropriate Contract Data Requirements List (CDRL) items for specific deliveries will be defined in each DO that will be issued under the terms and conditions of the ID/IQC.

3.1.1 Scope of Tasking

DOs will require specific research, engineering, logistics, and other efforts in support of the development of the LVCMS and ASW VAST family of training systems. Tasks may consist of any combination of the typical efforts described in this SOW. Disciplines of engineering expertise that may be required, singly and in combination, may be derived from the efforts described. These efforts shall include all or any combination of:

a. Engineering

b. Software development

c. Installation

d. Training of Government personnel

e. Engineering Corrections

f. Documentation preparation

g. System Test and Evaluation (T&E)

h. Logistics

i. Instructional systems analysis, design, and development http://www.ansi.org/ http://www.ieee.org/

3.1.2 Method of Tasking

Government requirements issued under the basic IDIQ Contract will be met through individual DOs with a DO SOW containing the requirements for specific tasks. Individual

DOs will be issued based on the SOW approach. The SOW approach is described in 3.1.2.1 below. Each awarded DO will contain a SOW and will usually also contain a NAWCTSD specification describing the specific products for that individual program requirement with respect to the performance, end item(s), delivery schedule(s), delivery address(es), performance milestones, Government reviews, travel, and where applicable, end item validation. DOs may be written against any portion of this SOW and may be issued at any time during contract performance. Additionally, the Government will include a set of data item requirements for the DO in the form of CDRL items. The contractor shall not perform any requirement until a DO setting forth the specific requirements to be performed has been executed by the Procuring Contracting Officer (PCO).

3.1.2.1 SOW Approach

In instances where the Government objectives are clearly defined, the Government may issue a DO based on the SOW approach. Under this approach, the Government will prepare a DO

SOW specifying the requirements. In addition to the DO SOW, the Government may include separate product performance requirements in the form of a Training System Requirements

Document (TSRD) or a performance specification when appropriate. The Government will also provide appropriate CDRL items (DD Forms 1423) and other required DO documentation to the contractor.

3.1.3 Deliverables

Each DO will contain as Exhibits, CDRLs (DD Form 1423s), citing the Data Item

Description(s) (DIDs) for the technical data and other information that shall be delivered with the DO. Appendix A is a listing of data items that may be required under individual

DOs. This listing is for information purposes only and is subject to change based on the requirements of the individual DOs.

3.1.4 Program and Engineering Management

The contractor shall organize, coordinate, and control all program activities to ensure compliance with the DO requirements and the timely delivery of the required product. The contractor shall provide the necessary program management, system engineering, design engineering, materials, equipment, facilities, testing, technical, management, logistics, and administrative requirements necessary for tasks described in this SOW and the efforts specified in each of the DOs awarded under this ID/IQC. Program management shall include continuous monitoring of available resources, task assignments, schedule and schedule constraints, and relevant technology constraints to provide recommendations related to program goals and objectives. Engineering management processes shall be coordinated via the Integrated Product Team (IPT) process, which is defined below in section 3.1.4.6. The contractor shall monitor program status in sufficient detail to permit understanding of program progress and risks with respect to achievement of planned milestones and activities, planning, costs (for CPFF), the LVCMS ASW VAST training system requirements, and design (hardware and software), problem areas, and planned corrective action. This status information shall be made available for review during the IPT meetings. The contractor shall prepare the Contractor’s Progress, Status, and Management Report (CPSMR) in accordance with (IAW) the CDRL requirements (B001) of each individual DO.

3.1.4.1 Work Planning and Scheduling

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

Program Management Report (IPMR) that presents the contractor’s and subcontractor’s schedules to meet the requirements of the DO. The contractor shall develop and document a tiered scheduling system showing the program milestones and prerequisite events, conferences, reviews, data submittals, and deliveries. The contractor shall construct the

IPMR to ensure that the program milestones are met and to ensure that deliveries meet the requirements of the DO. The contractor shall prepare the IPMR as required and specified in the individual DO IAW CDRL B005.

3.1.4.2 Risk Management

The contractor shall conduct risk management to systematically control the uncertainty in the project’s ability to meet cost, schedule, and performance objectives. The contractor shall conduct that part of risk management that directly impacts the technical effort and involves risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control. Risk management to product requirement objectives shall be covered at the program and technical reviews. The contractor shall use the contractor’s internal risk management tools to perform risk management. The contractor shall provide the Government visibility into the contractor’s tools, assessment, mitigation, and control techniques. When required in an individual DO, the contractor shall define, document, manage, and apply a risk management process IAW the IEEE Std 12207-

2008, section 6.3.4 or Naval SYSCOM Risk Management Policy. The contractor shall document risk management as part of the IPMR as required and specified in the individual

DO. The contractor shall provide a risk management planning process for this contract that identifies how key technology risks, planned risk mitigation activities, fallback options in case of insurmountable difficulty, and decision points in the program schedule will be made.

3.1.4.3 Cost Reporting

The contractor shall document current expenditure data for each Cost Plus Contract Line Item

(CLIN) within a DO. The contractor shall include the cost data in the Contractor’s Progress, Status, and Management Report.

3.1.4.4 Subcontractor Management and Reporting

When required in an individual DO, the contractor shall manage all subcontracts, including those that are Firm-Fixed Price (FFP). The contractor shall ensure the timely award of subcontracts, the integration of the subcontractor's plans into appropriate schedules, and the monitoring of the subcontractor's staffing plans, to include the execution of those staffing plans to the required levels with the required skills. The contractor shall ensure that the subcontractor’s efforts, to include technical, quality, configuration management, and risk processes are accomplished per contract requirements. The contractor shall integrate subcontractor reporting into the contractor’s IPMR as required and specified in the individual

DO. The contractor shall ensure that subcontractor’s use objective criteria to measure performance. The contractor shall integrate the principal subcontractors’ IPMRs into the contractor’s scheduling system. The contractor shall include the principal subcontractor’s

IPMRs in the contractor’s IPMR as required and specified in the individual DO IAW CDRL

B005.

3.1.4.5 Integrated Product Teams

The contractor shall define, document, implement, and maintain IPT structures for the duration of each DO. IPTs are the organizational structure resulting from Integrated Product

Development (IPD) implementation. The purpose of an IPT is to bring together the functions that have a stake in the performance of a product or process and concurrently make integrated decisions affecting that product or process. IPT membership shall consist of multi-functional stakeholders working together with a product-oriented focus. The IPTs will consist of Government and contractor personnel and have a Government chair. Each IPT shall be empowered to make critical life cycle decisions regarding the trainer system development. IPTs shall be applied at various levels ranging from the overall structure of an organization to informal groups functioning across existing units. Each IPT shall prepare the required planning documents (engineering plan, master schedule, and the like) for the system element to which it is assigned; shall develop and satisfy the specifications and baselines associated with the element; and shall complete the work outlined in tasking statements related to the element, including the technical reviews. The contractor shall ensure this methodology includes integration of engineering specialties and management of a totally integrated effort. The contractor shall provide the members of the IPT with visibility into the integration and test planning effort. The contractor shall identify problems and potential problems that could adversely impact system performance, cost and/or delivery schedule in a timely manner, accompanied by proposed solutions. The IPT process does not relieve the contractor of accountability and responsibility to perform in accordance with the requirements of this contract. The IPTs listed below shall be established for this ID/IQC as required by each DO. IPTs shall consist of Government and contractor personnel. IPT meetings shall be IAW Section 3.2.2.7.1.3 and 3.2.3.7.1.3.

a. Test and Evaluation IPT (T&E IPT) - The purpose of the T&E IPT is to create a forum suitable for maintaining a continuous interchange of test related issues and to identify and resolve potential problem areas related to a successful new trainer or trainer modifications T&E program. The T&E IPT shall be formed early in the new trainer or trainer modifications development program and shall consist of selected individuals from

NAWCTSD, Government Subject Matter Experts (SMEs), Fleet Project Team (FPT) members, and trainer contractor technical personnel. The T&E IPT shall be primarily concerned with events leading up to, and including, the Conformance Inspections.

b. The T&E IPT and its responsibilities shall be identified in the Test and Evaluation

Master Plan (TEMP). The TEMP shall be delivered in accordance with the CDRL (A008) for each DO. T&E IPT meetings shall be scheduled to coincide with scheduled requirements, design, progress, and Test Readiness Review (TRR) conferences.

c. Software/Information Assurance IPT (SW/IA IPT) - The purpose of the SW/IA IPT is to review and discuss software and IA design information (including technical documentation) and software and IA related issues, including those leading to a trainer type accreditation. The SW/IA IPT shall identify and resolve potential problem areas related to the trainer software and IA.

d. Integrated Logistics Support IPT (ILS IPT) - The purpose of the ILS IPT is to review and discuss logistic unique requirements and issues. The ILS IPT shall identify and resolve potential problem areas related to Configuration Management (CM), life cycle, provisioning, spares, and technical documentation requirements.

e. Synthetic Environment Database IPT (SEDB IPT) – This IPT shall be established as required by the individual DO. The purpose of the SEDB IPT is to provide the contractor better access to data and inputs from Government engineers. The SEDB IPT shall ensure that the databases comply with the LVCMS ASW VAST training system requirements.

SEDB IPT shall also identify, discuss, and resolve database related issues.

3.1.5 Information Management

When required in an individual DO, the contractor shall define, document, manage, and apply an information management process IAW the applicable version of IEEE Std 12207.

The contractor shall include the status of technical data deliveries in the IPMR cited above in section 3.1.4.

3.1.5.1 Infoshare Website

The contractor will be provided access to a secure NAWCTSD Infoshare Website to post and retrieve DO-related documents, data, and information. The NAWCTSD Infoshare Website meets current Federal Government, Navy, and NAWCTSD Information Assurance standards.

The contractor shall contact the NAWCTSD Infoshare point of contact listed in the DO to coordinate access to the NAWCTSD Infoshare Website. The contractor shall notify the

Government team via email when new or changed DO-related documents, data, and information are posted in the NAWCTSD Infoshare Website. Only unclassified data shall be posted in the NAWCTSD Infoshare Website.

3.1.5.2 Government/Industry Data Exchange Program (GIDEP)

When required in an individual DO, the contractor shall maintain procedures to enable participation in the GIDEP. If not a participant already, the contractor shall contact the

GIDEP Help Desk by calling (951) 898-3207 or access the GIDEP website at http://www.gidep.org within 30 days after ID/IQC award to obtain the guidance necessary to become a GIDEP participant. The mailing address is GIDEP Operations Center, P.O. Box

8000, Corona CA 92878-8000. Compliance with this requirement shall not relieve the contractor from complying with other provisions of the ID/IQC and each DO. The contractor shall insert this requirement in subcontracts hereunder exceeding $500,000. When so inserted, the word “contractor” shall be changed to “subcontractor.”

3.1.6 Security

The security requirements specified herein shall apply to the contractor and subcontractors.

Detailed security requirements including the following shall be as specified in each DO.

3.1.6.1 Security Requirements for DOs Involving Classified Information

The contractor shall safeguard classified information and meet the security requirements identified in the DD Form 254. The contractor shall enforce these safeguards throughout the life of the ID/IQC including the transport and delivery phases. A single DD Form 254 will be provided against the base ID/IQC and will be applicable to all DOs.

3.1.6.1.1 Operations Security (OPSEC)

The contractor shall provide OPSEC protection for classified information and sensitive information. Security policy, procedures, and requirements for classified information are provided in DoD 5220.22-M. The contractor shall safeguard sensitive and critical program information IAW the OPSEC Plan. The contractor shall enforce these safeguards throughout the life of the DO from development through sustainment. An OPSEC plan shall be delivered in accordance with the CDRL (A00B) for the base contract to document the contractor’s established security plan to address the protection of classified, proprietary, sensitive, and controlled unclassified information. The contractor may also be tasked to prepare individual OPSEC Plans, if so directed by the CDRL requirements of individual

DOs.

3.1.6.2 Security Requirements for DOs Involving Unclassified Information

The contractor shall comply with applicable on-site security regulations related to facility access and building access. The contractor shall safeguard all sensitive information and controlled unclassified information IAW the contractor’s locally established security plan (if the contractor already has an established local security plan). The contractor shall enforce these safeguards throughout the life of the DO including the transport and delivery phases and the disposition and storage of controlled unclassified information at DO completion.

3.1.6.2.1 Personnel Security - Background Check (Physical Access to and Working with

DoD Installations)

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

Government information systems IAW FAR 52.204-9. A National Agency Check with

Inquiries (NACI) or equivalent national security clearance (e.g. National Agency Check with

Local Agency Checks including Credit Check (NACLC)) will be required 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 NACI or equivalent. There will be no additional NACI 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 NACI (or equivalent) or who are under the escort of appropriately cleared personnel. Where escorting such persons is not feasible, a NACI (or equivalent) shall be conducted and favorably reviewed by the appropriate DoD component, agency, or activity prior to permitting such access. For contractor employees who do not have a security clearance, the contractor shall use the

Standard Form 85P (Questionnaire for Public Trust Positions) in order to obtain the CAC and access to controlled unclassified information. The contractor shall submit the Standard Form

85P to the NAWCTSD PCO for processing. This CAC requirement shall be cited against the applicable DOs.

3.1.6.2.2 Personnel Security – Background Checks (Contractor Facility)

Contractor personnel working in the contractor’s own facilities shall undergo the company internal vetting process prior to gaining access to U.S. Government-controlled unclassified information.

3.1.6.2.3 Contractor – Owned Unclassified Network Security

The contractor shall take means (defense-in-depth measures) necessary to protect the confidentiality, integrity, and availability of Government-controlled unclassified information in the same manner as the contractor would protect its own unclassified company proprietary information.

3.1.6.2.4 Information Security Requirements for Protection of Unclassified DoD

Information On Non-DoD Systems

The contractor shall safeguard unclassified DoD information stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information.

3.1.6.2.5 Information Assurance and Personnel Security Requirements for Accessing

Government Information Technology (IT) Systems - Suitability/Positions of Public Trust

When required in an individual DO, the contractor shall comply with the IA and personnel security requirements for accessing U.S. Government IT systems as specified in the DO. The contractor shall deliver the Information Technology (IT) Personnel Security Report IAW

CDRL A00C. Contractors requiring access to U.S. Government IT systems will be subject to a background check. The contractor shall review and become familiar with the suitability factors presented in 5 CFR 731.202(b), to use as an aid in their employee selection process.

The NAWCTSD Security Office will make final determinations of suitability for individual contractors.

3.1.6.2.6 Information Security Requirements for Protection of Unclassified DoD

Information On Non-DoD Systems

When required in an individual DO, the contractor shall safeguard unclassified DoD information stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information. The contractor shall:

a. Not process DoD information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control.

b. Protect information by no less than one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control.

c. Sanitize media (e.g., overwrite) before external release or disposal.

d. Encrypt the information that has been identified as Controlled Unclassified

Information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as thumb drives and compact disks, using the best available encryption technology.

e. Limit information transfer to subcontractors or teaming partners with a need to know and a commitment to at least the same level of protection.

f. Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS).

g. Encrypt organizational wireless connections and use encrypted wireless connection, where available, when traveling. When encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using no less than application-provided password protection level encryption.

h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

i. Not post DoD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts).

j. Provide protection against computer network intrusions and data exfiltration, including no less than the following:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

(2) Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services.

(3) Prompt application of security-relevant software patches, service packs, and hot fixes.

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., critical program information, Personally Identifiable Information (PII), export controlled information) when required by individual DOs.

3.1.7 Information Assurance

The contractor shall design, develop, document, integrate, verify, and deliver security architecture for all new trainers and trainer modifications that satisfies the System IA controls as defined in DoDI 8500.2, and meets the security and IA performance requirements specified in the NAWCTSD Specification. The contractor shall perform IA certification and accreditation requirements specified in each DO. IA requirements shall be as specified in the individual DO.

3.1.7.1 Third Party Software

The Contractor shall support Government efforts to ensure that shareware or freeware are not implemented unless compelling circumstances exists, in which case the developer shall evaluate and verify the software is free of malware, back doors or buffer overflows. If the application relies on third party software products or libraries selected by the developer, the developer shall ensure the components comply with all requirements within the Application

Security and Development STIG and shall report the shareware and freeware in the software documentation.

3.1.7.2 Software Management System

The Contractor shall support Government efforts to incorporate a centralized software management system to support updates to the Commercial Item software components used in the trainer, including anti-virus software.

3.1.7.3 Backup Management System

The Contractor shall support Government efforts to incorporate a backup management system that provides the means for the System Administrator to perform back up operations weekly for trainer components from one central location and restore, within time limits prescribed in individual DOs, to its previous state in case of catastrophic failures.

3.2 Detailed Technical Requirements

As required in individual DOs, the Contractor shall provide design, development, integration, test, delivery, and sustainment for the LVCMS, ASW VAST, A2AD and Cyber Warfare training systems, to include installation at the various locations. The Contractor shall design the training systems for compatibility with anticipated changes in products such as operating systems and JSAF NTB. The Contractor shall also design and develop training systems to be operable within the Navy Continuous Training Environment (NCTE) using JSAF NTB. The

Government laboratory for testing and integration of software and hardware is located in

Orlando, Florida. Currently, the LVCMS and ASW VAST family of training systems requiring sustainment and Fleet Synthetic Training (FST) on site engineering include:

Mission Rehearsal Tactical Team Trainer (MRT3), Bravo Aircrew Tactical Team Trainer

(BATTT), Bravo Romeo Acoustic Stimulation System (BRASS), High Fidelity Active

Sonar Training Command (HIFAST CMD), P-3 Air Crew Tactical Team Trainer (PACT3), Virtual Maintenance Performance Aide (VMPA), Virtual Anti-Submarine Warfare

(ASW)/Anti-Surface Warfare (ASUW) Tactical Air Controller (VASTAC), Effective Active

Acoustic Simulation/Stimulation (EFAAS), Sonobuoy Acoustic Training System (SATS), Common Distributed Mission Training Station (CDMTS), Single Ship Anti-Submarine

Warfare (SSASW) Team Trainer 14A12/14A12J, and Tactical Warfare Instructor Support

Environment (TACWISE). The Contractor shall provide the sustainment and FST on site engineering of these families of training systems at multiple sites including Naval Air Station

(NAS) Mayport, FL, NAS Jacksonville, FL, NAS North Island, CA, and multiple OCONUS

DoD sites.

The following sections describe and are representative of the tasks, technical data, and information the contractor may be required to provide in the individual DOs.

3.2.1 Post Award Conference CLIN 0001 (FFP)

3.2.1.1 Post Award Conference (PAC) for Base ID/IQC Award

An initial PAC shall be conducted at the contractor’s facility after the Base ID/IQC 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. The contractor shall prepare and deliver the Conference Agenda, Conference Minutes, and Presentation Material for the PAC IAW CDRL items B002, B003, and B004, respectively.

The PAC shall include the presentation and discussion of information and data relating to:

a. Introduction and Contract Overview

b. Discussion and clarification of SOW requirements

c. Program specific System Engineering Management Plan (SEMP) Overview

d. Program specific CM Plan (to include Data Management) Overview

e. Program specific Quality Assurance and Management Plan (QAMP) (to include

Software Quality Assurance) Overview

f. Program specific Risk Management Plan (RMP) Overview

g. Integrated Logistics Support (ILS) Program Overview

h. Program specific OPSEC and IA Plans Overview

i. IPT structure, membership, and responsibilities

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

k. Plan for action item reporting and status

l. Plan for metrics collection process, analysis, and reporting

3.2.2 Trainer Systems CLIN 0002 (FFP)

3.2.2.1 New Training Systems

When required by individual DOs, the contractor shall analyze, design, develop, fabricate, integrate, procure, deliver, install, and test, as well as…