Draft USWTR_Increment_II_III_SOW 20200713.pdf

USWTR Increment II/III Statement of Work Initial Release

DISTRIBUTION STATEMENT A. Approved for public release.

Undersea Warfare Training Range (USWTR) Increment II and III In-

Water Subsystem (IWS)

Statement of Work Contract Number N61340-19-R-0115

USWTR Increments II and III Initial Release 13 July 2020

DEPARTMENT OF THE NAVY

NAVAL AVIATION TRAINING SYSTEMS AND RANGES PROGRAM OFFICE PMA205

NAVAL AIR SYSTEMS COMMAND

PATUXENT RIVER, MD 20670

This page intentionally left blank

REVISIONS

SYM DESCRIPTIONS ISSUE DATE APPROVED

0 Initial Release 2020713

Sheet

Index

Rev Sheet 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Acronym Listing

This section contains the definitions for the acronyms used in this document.

3D Three-dimensional AMW Amphibious Warfare ASP Acoustic Signal Processor ASW Anti-Submarine Warfare AUTEC Atlantic Undersea Test and Evaluation Center BARSTUR Barking Sands Tactical Underwater Range BIT Built in Test BSURE Barking Sands Undersea Range Expansion CA California CDRL Contract Data Requirements List CLIN Contract Line Item Number CI Configuration Item CC Common Criteria COTS Commercial off the Shelf CSA Configuration Status Accounting CSCI Computer Software configuration items CTS Cable Termination Shelter CUI Controlled Unclassified Information CWBS Contract Work Breakdown Structure CCIP Course Conduct Information Package DACA Days after Contract Award DADMS Department of the Navy (DoN) Application and Database Management System DAL Data Accession List DFARS Defense Federal Acquisition Regulation Supplement DPCS Display, Processing, and Control Subsystem DT Developmental Test DMSMS Diminishing Manufacturing Sources and Material Shortages DOD Department of Defense DoN Department of the Navy DOORS Dynamic Object Oriented Requirements System E31AR Electromagnetic Environmental Effects (E3) Integration and Analysis Report ECP Engineering Change Proposal ESOH Environmental, Safety, and Occupational Health EW Electronic Warfare FCA Functional Configuration Audit FACSFAC Fleet Area Control and Surveillance Facility FAT Factory Acceptance Test

FMECA Failure Modes, Effects, and Criticality Analysis FOUO For Official Use Only GFE Government Furnished Equipment GFF Government Furnished Facility GFI Government Furnished Information GFM Government furnished material GFP Government Furnished Property HWCI Hardware Configuration Item IAT Information Assurance Technical IAVMP Information Assurance Vulnerability Management Program IAW in accordance with ILS Integrated Logistics Support IMS Integrated Master Schedule Inc. Increment iPRR Incremental Production Readiness Review IPT Integrated Product Team IT Integrated Test ITAR International Traffic and Arms Regulation IUID Item Unique Identification IWS In-water subsystem m Meters M-Demo Maintenance Demonstration MIW Mine Warfare MBSE Model Based Systems Engineering NAVAIR Naval Air System Command NALF Naval Auxiliary Landing Field NAS Naval Air Station NBC Naval Base Coronado NIAP National Information Assurance Partnership Nm Nautical Miles Nm2 Square nautical miles NSW Naval Special Warfare O&M Operation and Maintenance OEM Original Equipment Manufacturer OSS Ocean Sensor System PCA Physical Configuration Audit PMR Program Management Review PMRF Pacific Missile Range Facility PDR Preliminary Design Review PRR Production Readiness Review QMS Quality Management System RDT&E Research, Development, Test, and Evaluation R&M Reliability and Maintainability Rx Receive

Rx-Tx_HF Receive Transmit High Frequency Rx-Tx_LF Receive Transmit Low Frequency RMF Risk Management Framework RPL Route Position List SCI San Clemente Island SCR Software Change Request SCTTR Southern California Tactical Training Range SDD Software Design Description SDP Software Development Plan SPR Security Policy Review SCI San Clemente Island SOAR Southern California Offshore Anti-Submarine Range SRG Security Requirements Guide SRS Software Requirement Specification SS Subsystem Specification SSDD Subsystem Design Description SSI Sea Shore Interface SEMP System Engineering Management Plan SES Shore Electronics System SETR System Engineering Technical Reviews SNAC System and Network Attack Center SRA Schedule Risk Assessment SSDD System/Subsystem Design Description SOW Statement of Work SCTTR Southern California Tactical Training Range SVR System Verification Review SysML Systems Modeling Language STR Software Trouble Report SWTR Shallow Water Training Range TB Tanner Bank TDP Technical Data Package T&E Test and Evaluation TEPP Test and Evaluation Program Plan TIM Technical Interchange Meeting TPM Technical Performance Measurement TPOC Technical Point of Contact TPSD Training Program Structure Document TCSD Training Course Support Document TR Technical Review TSPI Time and Space Positional Information USW Undersea Warfare USWTR Undersea Warfare Training Range

UCS Underwater communications system UR Undersea Range

UTR Underwater Training range UTS Underwater Tracking System WC-SWTR West Coast Shallow Water Training Range www World Wide Web

Use or disclosure of data contained on this page is subject to the restriction on the Title Page.

i

Table of Contents

1.0 Background

2.0 Scope

2.1 Specific Programs/Systems

2.2 Specific Requiring Department Codes/Customers/Users of the Contract

2.3 Sponsors

2.4 Type of Funds to be Applied

3.0 Applicable Documents

4.0 Technical Tasks

4.1 Task A Technical Review: Technical Program Management

4.1.1 Program Management Planning

4.1.2 Technical Interchange and Program Management Meetings

4.1.3 Request for Variance

4.1.4 Integrated Product Team Teleconferences

4.2 Task B Technical Review: System Engineering

4.2.1 Engineering Management Program

4.2.2 Item Unique Identification

4.2.3 In‐Water Subsystem Requirements Analysis and Functional Allocation

4.2.4 Physical Component Design and Interface Control

4.2.5 Environmental, Safety and Occupational Health

4.2.6 Reliability and Maintainability

4.2.7 Failure Modes, Effects and Criticality Analysis

4.2.8 Electromagnetic Compatibility and Interference Control

4.2.9 Software Development

4.2.10 Data Management

4.2.11 Cybersecurity

4.2.12 Suppliers Configuration Management Program

4.2.13 Configuration Audits

4.2.14 Diminishing Manufacturing Sources and Material Shortages

4.2.15 Test and Evaluation Program

4.2.16 System Engineering Technical Reviews

4.2.17 Corrosion and Corrosion Prevention Planning

4.2.18 Engineering Change Proposals

4.2.19 Production Readiness

4.3 Task C BARSTUR and BSURE Production and Installation Engineering

4.4 Task D AUTEC Production and Installation Engineering

4.5 Task E Deep Water Production Engineering Verification

4.6 Task F SOAR Production and Installation Engineering

4.7 Task G BARSTUR and BSURE Trunk Cable

4.8 Task H BARSTUR Internode Cable

4.9 Task J AUTEC Trunk Cable

4.10 Task K AUTEC Internode Cable

4.11 Task L BSURE Internode Cable

ii

4.12 Task M BARSTUR Procurement, Production and Test Cable Terminations

4.13 Task N BARSTUR Procurement, Production and Test In‐Water Subsystem

4.14 Task P AUTEC Procurement, Production and Test Cable Terminations

4.15 Task Q AUTEC Procurement, Production and Test In‐Water Subsystem

4.16 Task R BSURE Procurement, Production and Test Cable Terminations

4.17 Task S BSURE Procurement, Production and Test In‐Water Subsystem

4.18 Task T BARSTUR Installation

4.19 Task U BARSTUR Installation Tests

4.20 Task V BARSTUR Post Installation Test

4.21 Task W BARSTUR and BSURE Training

4.22 Reserved

4.23 Task Y AUTEC Installation

4.24 Task Z AUTEC Installation Tests

4.25 Task AA AUTEC Post Installation Test

4.26 Task BB AUTEC Training

4.27 Reserved

4.28 Task DD BSURE Installation

4.29 Task EE BSURE Installation Tests

4.30 Task FF BSURE Post Installation Test

4.31 Task GG BARSTUR and BSURE Corrective Maintenance (1 year technical support)

4.32 Task HH AUTEC Corrective Maintenance (1 Year Technical Support)

4.33 Task JJ WC‐SWTR Production and Installation Engineering

4.34 Task KK Shallow Water Production Engineering Verification

4.35 Task LL TB SWTR Internode Cable

4.36 Task MM SCI SWTR Internode Cable

4.37 Task NN WC_SWTR Trunk Cables

4.38 Task PP TB SWTR Procurement, Production and Test Cable Termination

4.39 Task QQ TB SWTR Procurement, Production and Test In‐Water Subsystem

4.40 Task RR SCI SWTR Procurement, Production and Test Cable Terminations

4.41 Task SS SCI SWTR Procurement, Production and Test In‐Water Subsystem

4.42 Task TT SOAR Trunk and Internode Cable

4.43 Task UU SOAR Production and Installation Engineering Technical Review

4.44 Task VV TB SWTR Installation

4.45 Task WW TB SWTR Installation Tests

4.46 Task XX TB SWTR Post Installation Test

4.47 Task YY TB SWTR Training

4.48 Reserved

4.49 Task AAA SOAR Procurement, Production and Test Cable Terminations

4.50 Task BBB SOAR Procurement, Production and Test In‐Water Subsystem

4.51 Task CCC TB SWTR Corrective Maintenance (1 year technical support)

4.52 Task DDD SCI SWTR Installation

4.53 Task EEE SCI SWTR Installation Tests

4.54 Task FFF SCI SWTR Post Installation Test

4.55 Task GGG SCI SWTR Training

4.56 Reserved

4.57 Task JJJ SOAR Installation

iii

4.58 Task KKK SOAR Installation Tests

4.59 Task LLL SOAR Post Installation Test

4.60 Task MMM SOAR Training

4.61 Reserved

4.62 Task PPP SOAR Corrective Maintenance (1 year technical support)

4.63 Task QQQ SCI SWTR Corrective Maintenance (1 year technical support)

5.0 Progress Reports

6.0 Government Furnished information

7.0 Quality Surveillance and performance standards

8.0 Exception from Electronic and Information Technology Acessibility Requirements

List of Figures

No table of figures entries found.

List of Tables Table 1. Applicable Documents Table 2 SETR Events and Configuration Audits Table 3 SETR Event CDRL Entry Criteria Table 4 Government Furnished Information

1.0 BACKGROUND

The primary Undersea Warfare Training Range (USWTR) mission is to increase fleet readiness through training and tactical development of submarine, surface ship, aircraft Anti-Submarine Warfare (ASW), and Mine Warfare (MIW) conducted in deep and shallow water. A secondary mission includes regional conflict operations involving the Naval Special Warfare (NSW), Electronic Warfare (EW), and Amphibious warfare (AMW) mission/operational capability areas.

The USWTR supports the development of realistic combat exercises through weapon firings at mobile targets. The USWTR will provide measurement of time/space positional information (TSPI) and tactical status data in near-real-time. TSPI measured in real-time minimizes the possibility of impact between weapons and targets and improves safety for manned submarine targets. The USWTR provides post-exercise analysis, evaluation, and feedback of training performance data.

2.0 SCOPE

The contractor shall deliver six Underwater Training Ranges (UTRs). Four deep (ocean water depth ≥ 685 meters) water UTRs, referred to as Increment III (INC III), shall be redeveloped and modernized by overlaying existing ranges. Two shallow (ocean water depth 0 ≤ 685 meters) water UTRs, referred to as Increment II (INC II), shall be new ranges.

The contractor shall create one deep water Technical Data Package (TDP) for the following deep water ranges: the Barking Sands Tactical Underwater Range (BARSTUR), Barking Sands Undersea Range Expansion (BSURE), the Atlantic Undersea Test and Evaluation Center (AUTEC) UTR, and the Southern California Anti-Submarine Warfare Range (SOAR). The contractor shall revise and update one shallow water TDP, provided as Government Furnished Information (GFI) for the following West Coast Shallow Water Training Range (WC-SWTR) shallow water ranges: Tanner Bank (TB) Shallow Water Training Range (TB SWTR) and San Clemente Island (SCI) Shallow Water Training Range

(SCI SWTR).

This SOW delineates tasking for the following: 1. production and installation engineering,

2. procurement, production, and test, and 3. installation, test and training of each of the six ranges. A range shall comprise three subsystems: an Ocean Sensor Subsystem (OSS), the Sea-Shore Interface (SSI), and Shore Electronics Subsystems (SES). Collectively, these subsystems (OSS, SSI, and SES) are referred to as the In-Water Subsystem (IWS).

The Government will provide environmental approvals and permits as GFI. The Government will provide as Government Furnished Property (GFP) a Display, Processing and Control Subsystem (DPCS) for integration testing with the contractor built IWS. The Government will operate the GFP.

2.1 Specific Programs/Systems

This section identifies the following six ranges and their location.

2.1.1 DEEP WATER: Atlantic Undersea Test and Evaluation Center (AUTEC), Andros Island, Bahamas,

2.1.2 DEEP WATER: Pacific Missile Range Facility (Barking Sands Tactical Underwater Range [BARSTUR] and Barking Sands Undersea Range Expansion [BSURE]), Kauai, Hawaii

2.1.3 DEEP WATER: Southern California Tactical Training Range (Southern California Anti-Submarine Warfare Range [SOAR]), San Diego, California

2.1.4 SHALLOW WATER: Southern California Tactical Training Range (Tanner Bank Shallow Water Training Range [TB SWTR] and a San Clemente Island [SCI SWTR]), San Diego California

2.2 Specific Requiring Department Codes/Customers/Users of

the Contract

The requiring department codes/customers/users of this contract include the following:

Naval Aviation Training Systems and Ranges Program Office PMA205 NAVAIR Engineering, Navy MRTFB Program Management Division V542 Naval Undersea Warfare Center Division Newport, Code 70

2.3 Sponsors

The sponsors and stakeholders for work that will support this contract are the following:

Naval Air System Command (NAVAIR) NAVAIR Engineering, Navy Major Range and Test Facility Base Program

Management Division V542

2.4 Type of Funds to be Applied

Six ranges support a wide range of programs and customers, there are two different types of funding that will be used on this contract:

Other Procurement, Navy (OPN) Research, Development, Test and Evaluation (RDTE)

3.0 APPLICABLE DOCUMENTS

In performance of this SOW, the contractor shall use the documents provided in Table 1.

Table 1. Applicable Documents

Number Title SOW Reference

3.1 DoD Issuances

3.1.1 MIL-STD-464C, Department of Defense Interface Standard:

Electromagnetic Environmental Effects, Requirements for Systems 4.2.8

3.1.2 MIL-STD-882E, 11 May-12 - System Safety 4.2.5

3.1.3 MIL-HDBK-217F Reliability Prediction of Electronic Equipment 4.2.6

3.1.4 https://public/cyber.mil/, and https://public.cyber.mil/ 4.2.11

3.1.5 DoD Instruction 8510.01 Risk Management Framework (RMF) For Dod Information Technology (IT) 4.2.11

3.1.6 DODI 5000.02; Operation of the Defense Acquisition System - December 2008; http://www.esd.whs.mil/DD/ 4.2.11

3.1.7 MIL-HDBK-61A Configuration Management Guidance 4.2.12

3.1.8 MIL-STD-810H, 31 Jan 19 - Environmental Engineering Considerations and Laboratory Tests 4.2.17

3.1.9 MIL-STD-889C, 22-Aug-16 - Dissimilar Metals 4.2.17

3.1.10 MIL-PRF 29612 Training Data Products 4.21, 4.26, 4.60, 4.47, 4.55

3.1.11 DoDM 5200.01, DoD Information Security Program , Volumes 1 through 4, http://www.esd.whs.mil/DD/ ALL

3.1.12 DoD 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM) ALL

3.1.13 DoD 8570.01M; Information Assurance Workforce Improvement Program 4.2.11

3.2 Navy Issuances

3.2.1 Naval SYSCOM Risk Instr Signed 21 July 2008 4.1.1

3.2.2 NAVAIR Hazard and Safety risk instruction 4.1.1

3.2.3 NAVAIRINST 4355.19E, SYSTEMS ENGINEERING TECHNICAL REVIEW

PROCESS (SETR) HANDBOOK 4.2.13, 4.2.16

3.2.4 Department of the Navy (DoN) Application and Database Management System (DADMS). http://www.esd.whs.mil/DD/) 4.2.11

3.2.5 Intentionally left blank

3.2.6 Naval Facilities Engineering Command (NAVFAC) P-307 – Management of Weight Handling Equipment

4.3, 4.18, 4.4, 4.28, 4.6, 4.43.2, 4.52, 4.57, 4.33, 4.44, 4.46

3.3 Industry Standards

3.3.1 ANSI/EIA-632 Processes for Engineering a System 4.2.1

3.3.2 INCOSE-TP-2003-020-01, Technical Performance Measurement 4.2.1

3.3.3 IEEE12207; Systems and software engineering -Software life cycle processes 4.2.9

3.3.4 ANSI/GEIA-859 Implmentation Guide for Data Management 4.2.10

3.3.5 ANSI/EIA-649 National Consensus Standard for Configuration Management 4.2.12

3.3.6 SAE STD-0016 Standard for Preparing a DMSMS Management Plan 4.2.14

3.3.7 ISO 9001:2015 Quality Management Systems 4.2.1

3.3.8 AS9100D Quality Management Systems 4.2.1

3.3.9 SAE AS6500 Manufacturing Management Program Plan 4.2.19

3.3.10 http://www.dodmrl.org/ 4.3, 4.4, 4.6, 4.33, 4.43

4.0 TECHNICAL TASKS

The tasks listed in section 4.0 shall be used throughout all section 4.0 subsections of this

SOW.

The contractor shall use GFI #6.1.1 (USWTR Inc. III In-Water Subsystem (IWS) Performance Specification) and GFI #6.1.31 (USWTR Increment II In-Water Subsystem Performance Specification) for these technical tasks. The contractor shall perform these tasks at Atlantic Undersea Test and Evaluation Center (AUTEC), Andros Island, Bahamas, Pacific Missile Range Facility (PMRF), Kauai, Hawaii, and the Naval Station Base (NBC), Coronado, California. The contractor shall adhere to the visitor policies identified in GFI #6.1.2 (Visitor policies at AUTEC), #6.1.3 (Visitor policies at PMRF), #6.1.4 (Visitor policies at SOAR), #6.1.6 (Visitor policies at NUWCDIVNPT) and #6.1.24 (Visitor policies at NAVAIR PMA205) during performance of meetings, reviews, site visits, and field installations at the ranges. The contractor shall notify the Government 90 calendar days in advance of contractor requested IWS installation dates within the Government identified installation window identified in Installation subsections. The contractor shall provide 30 calendar days in advance of contractor requested Government Facility site visits (other than installation) dates. The contractor shall request exceptions to these timelines to the Government Technical Point of Contact (TPOC) or designated representative on a case by case basis. The Government will provide approval of the contractor proposed installation dates, site visit dates and exceptions to timelines via email.

Contractor travel shall be IAW the following:

1. [Specific to AUTEC only] The contractor shall adhere to the visitor policies using GFI #6.1.2 during performance at AUTEC. Entry is required for performance at the Government Furnished Facility (GFF) #6.3.1 (Command and Control Building at AUTEC). During performance, the contractor shall pay for Government arranged flights between West Palm Beach and AUTEC.

2. [Specific to BARSTUR and BSURE only] The contractor shall adhere to visitor policies using GFI #6.1.3. Entry is required for performance at the Government Furnished Facility (GFF) #6.3.1 (Building 410 and 105 at PMRF).

3. [Specific to SOAR, WC_SWTR TB and SCI only] The contractor shall adhere to visitor policies using GFI #6.1.4. Entry is required for performance at the Government Furnished Facility (GFF) #6.3.1 (SOAR Cable Termination Shelter).

The Government will pay and arrange air transportation between NBC and Naval Auxiliary Landing Field (NALF), San Clemente Island (SCI).

4. [Specific to NUWCDIVPT only] Using GFI #6.1.6, the contractor shall adhere to visitor policies during performance at NUWCDIVNPT (GFF) 6.3.7 (Office Facilities;

NUWCDIVNPT, Newport, Rhode Island). The performance shall be for meetings and events at NUWCDIVNPT.

5. [Specific to NAVAIR only] Using GFI #6.1.24, the contractor shall adhere to visitor policies during performance at NAVAIR GFF #6.3.6 (Office Facilities; NAVAIR PM205, Patuxent, Maryland). The performance shall be for meetings and events at NAVAIR.

The contractor shall safeguard classified information and meet the security requirements identified in the DD Form 254. The contractor shall protect Controlled Unclassified Information (CUI) IAW applicable document #3.1.11 (DoDM 5200.01, DoD Information Security Program) and #3.1.12 (DoD 5220.22-M, National Industrial Security Program Operating Manual). CUI is defined as technical data such as recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process or to design, procure, produce, support, maintain, operate, repair, or overhaul material. The data may be graphic or pictorial delineation in media, such as drawings or photographs, text in specifications or relater performance or design type documents, or computer printouts. Examples of technical documents include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog item identifications, and related information and computer software documentation. The contractor shall mark all range position data (e.g. hydrophone and cable positions) as For Official Use Only (FOUO). The contractor shall use the following address on all data requiring a distribution statement: PEO (CS), PMA205, 47123 Buse Rd, RADM William A. Moffett Building, Patuxent River, MD 20670-1547. The contractor personnel shall only use contractor issued hardware devices to collect photographic and video data. The contractor shall enforce these security safeguards throughout the life of the contract including the transport and delivery phases.

The contractor shall perform Information security for the life of the contract as follows:

1. The contractor shall 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.

2. The contractor shall prevent U.S. Government controlled unclassified information from being placed or stored on peer-to-peer applications or social media applications on contractor owned networks, including Teleworker computer assets.

3. The contractor shall 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.

4. The contractor shall sanitize media (e.g., overwrite) before external release or disposal.

The contractor shall adhere to security and public release as follows:

1. The contractor shall ensure NAVAIR program related information and graphics intended for release to the public and/or posting on internet and World Wide Web (www) site is submitted through the NAVAIR Security Policy Review (SPR) process before release. The contractor shall include note pages in all briefings and slide presentations submitted to the NAVAIR organization that owns or controls the information for review and final release authorization.

2. The contractor shall submit proposed public release request’s to the Government for review and approval 120 calendar days prior to the requested release date.

3. Subcontractors shall forward public release requests via the contractor for endorsement before submittal to the Government for final concurrence.

4. All requests for public release shall be submitted to: Commander, Naval Air Systems Command, 47123 Buse Road, Building 2272, Attention: PMA205 COMS, Patuxent River, MD 20670-1547 using GFI #6.1.39 (NAVAIRINST 5720.10 Public Release Authorization Request).

5. The Contractor shall comply with U.S. Government export requirements.

6. The Contractor shall ensure the security procedures and controls identify, mark, safeguard and control distribution of Controlled Unclassified information (CUI) and classified information IAW applicable document #3.1.11 (DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM)) and #3.1.12 DoDM 5200.01, DoD Information Security Program, Volumes 1 through 4.

4.1 Task A Technical Review: Technical Program Management

4.1.1 Program Management Planning

The contractor shall develop, maintain and execute a management plan. The plan shall include the following: program planning and control, cost and scheduling, subcontractor control, financial management, data management, management and accountability for

GFP and GFI, systems engineering management, configuration management, and product support efforts.

The contractor shall develop and maintain an Integrated Master Schedule (IMS) covering the entire contract work scope. The contractor shall manage the execution of USWTR using the IMS. The contractor shall construct the IMS to follow the Contract Work Breakdown Structure (CWBS). The contactor shall perform an IMS schedule risk assessment (SRA) bi-annually with supporting narrative.

The contractor shall develop and execute a risk management plan risk IAW applicable document #3.2.1 [Naval SYSCOM Risk Instr Signed 21 July 2008] and #3.2.2 [NAVAIR Hazard and Safety risk instruction]).

The contractor shall develop and maintain a Contract Work Breakdown Structure (CWBS).

The CWBS element level shall go down to level five. The CWBS shall identify contractor, subcontractor, and major supplier responsibilities. The contractor shall provide a CWBS summary report for cost-plus-fixed-fee contract line items.

The contractor shall report performance using a contractor status report. The contractor shall report cost-plus-fixed-fee contract line items financial data using a funds and man-hour expenditure report. The reports shall include subcontractors. The reports shall include CWBS Level five.

Deliverables:

The contractor shall deliver the following:

Management Plan IAW CDRL A001, Integrated Master Schedule IAW CDRL A002, Contractor’s Risk Management Plan IAW CDRL A003 Contractor Status Report IAW CDRL A004 Funds and Man-hours Expenditure Report IAW CDRL A005 Contract Work Breakdown Structure IAW CDRL A00B Cost Breakdown Structure Summary Report IAW CDRL A00C

4.1.2 Technical Interchange and Program Management Meetings

The contractor shall conduct, support, and attend quarterly Technical Interchange Meetings (TIM) at the contractor’s facility. The Government will conduct Program Management Reviews (PMR) at a Government facility IAW GFF #6.3.6 (Office Facilities;

NAVAIR PM205, Patuxent, Maryland) or #6.3.7 (Office Facilities; NUWCDIVNPT, Newport, Rhode Island). One PMR per year shall be at the contractor facilities. The contractor shall support and attend PMRs. TIMs and PMRs shall alternate each quarter, e.g. first quarter a TIM, 2nd quarter a PMR, 3rd quarter a TIM, and etc. A TIM shall emphasize contractor technical performance. A PMR shall emphasize contractor cost and schedule performance. Each TIM/PMR the contractor shall present, at a minimum, the topics as follows:

Technical Review; Technical Program Management including the following:

o Contract/Funding actions (limited audience of Government TPOC or their designee and the prime contractor) o Schedule status, variance, and schedule risk assessment o Risk assessment and its mitigation o Review of action items o Summary of non-conformance items and request for variance

Technical Review; System Engineering including the following:

o Model Based System Engineering (MBSE) effort, specifications, and interfaces o Technical discussion of CDRL’s delivered and in-process, CDRL look ahead and address delinquent CDRL deliveries o Cybersecurity status o Test and Evaluation Program Plan status o Diminishing Manufacturing Sources and Material Shortages

(DMSMS)/Obsolescence Plan/Status o Software development, metrics, and changes

Technical progress and performance for Production Engineering, Procurement, Production, Test, Installation and Training including the following:

o Product Drawings/Models & Associated List new or revised from the previous meeting o Assessment of manufacturing readiness o Review of test planning and results o Installation engineering and planning o Integrated logistics support identified various subsections o Status of procurements, time phased production status

A meeting duration shall be a maximum of 3 days with anticipated average of 2 days.

The contractor shall accommodate ten Government or Government contractor employees’ at each meeting. One PMR per year shall accommodate fifty Government or Government contractor employees’. The contractor shall consolidate a TIMs/PMRs within a SETR event (subsection 4.2.16 of this SOW) if the events fall within 14 calendar days of each other.

The contractor shall record, and complete action items. The contractor shall create for each TIM/PMR meeting, presentation material and conference agenda.

The contractor shall host and perform the first TIM within 10 calendar days after contract award (DACA). The first TIM shall be a post award conference. The contractor shall ensure major subcontractors participate in this TIM. The purpose shall define contract expectations.

Deliverables:

The contractor shall deliver the following:

Report, Record of Meeting Minutes IAW CDRL A006 Presentation Materials IAW A007 Conference Agenda IAW A008

4.1.3 Request for Variance

The contractor shall submit a request for variance (RFV) for a product found to be non-conforming with the product definition information after the product has been produced by the production process. RFV’s shall include deviations from specifications. The contractor shall commence RFVs after Government approval of CDRL A01G (Product Drawings/Models & Associated List).

Deliverables:

The contractor shall deliver the following:

Request for Variance IAW CDRL A00H

4.1.4 Integrated Product Team Teleconferences

The contractor shall conduct Integrated Product Team (IPT) weekly program management and engineering teleconferences every year. Management and engineering teleconferences shall be on different day of the week. At management teleconferences, the contractor shall discuss the following:

Contract/Funding actions (limited audience of Government TPOC or their designee and the prime contractor)

Schedule status, variance, and schedule risk assessment, discussion of progress made towards completing planned work (including work conduction by subcontractors), Discuss plans for upcoming TIMs, PMR, and milestones, Provide staffing status, vacancies, and use of resources Test and Evaluation Program Plan status

At engineering teleconferences, the contractor shall discuss the following:

Technical progress and performance Risk assessment and its mitigation Installation engineering and planning Test and Evaluation Program Plan status Status of procurements, time phased production status Updates to contractor action items CDRL look ahead and address delinquent CDRL deliveries

The expected duration for each teleconference is one hour. The contractor shall perform the first management teleconference within 15 calendar days after contract award. The contractor shall perform the first engineering teleconference within 15 calendar days after contract award. The contractor shall record, track, and complete action items. The contractor shall provide conference agenda via email to the Government and their designee.

Deliverables:

The contractor shall deliver the following:

Report, Record of Meeting Minutes IAW CDRL A006

4.2 Task B Technical Review: System Engineering

4.2.1 Engineering Management Program

The contractor Systems Engineering Management Plan (SEMP) shall address all items under subsection 4.2 of this SOW. The contractor shall create and maintain a data accession list. The contractor shall prepare and use a Technical Performance Measurement (TPM) Program IAW applicable document #3.3.2 (INCOSE-TP-2003-020- 01, Technical Performance Measurement). The contractor shall include TPMs in the areas of IWS subsystem reliability, sensor acoustic performance, subsystem throughput requirements, subsystem power requirements, and range safety features within the IWS IAW GFI #6.1.5 (USWTR System Engineering Plan). TPMs shall be included in the contractors SEMP.

The contractor shall implement a Quality Management System (QMS) IAW applicable documents #3.3.7 (ISO 9001:2015 Quality Management Systems) and/or #3.3.8 (AS9100D Quality Management Systems) to be identified in a Quality Assurance Program Plan. The contractor shall be certified in either ISO 9001:2015 Quality Management Systems or AS9100D Quality Management Systems. The contractor shall identify and provide Government personnel access to their facilities on an annual basis for verification of quality systems. The contractor shall provide a quality report coincident with the plan.

As part of the Model Based System Engineering (MBSE) effort, the contractor shall create and maintain a Systems Modeling Language (SysML) architectural USWTR IWS model utilizing the Cameo Systems Modeler, GFI #6.1.1 (USWTR Inc. III In-Water Subsystem Performance Specification), GFI #6.1.31 (USWTR Increment II In-Water Subsystem Performance Specification), and #6.1.5 (USWTR System Engineering Plan). The model shall be employed for requirements analysis, functional allocation, physical component design, performance modeling, and external/internal definition and control. The contractor shall deliver (as part of A01G) models and associated data comprising the SysML/Cameo artifacts and source files to the Government in the models native format.

The contractor model shall include traceability to all applicable elements and verification requirements within the model. Verification related information shall include the source of the requirements, a summary of the verification evidence for each verification requirement, a listing of all verification results (e.g. test reports), a listing of all supporting documents/data used in the verification (e.g. verification plans and procedures), and the location of all listed data/documents. The model shall include the support equipment and/or adapters.

Deliverables:

Systems Engineering Management Plan (SEMP) IAW CDRL A00E Quality Assurance Program Plan (QAPP) IAW CDRL A00F Quality Assessment Report (QAR) IAW CDRL A00A Product Drawings/Models & Associated List IAW CDRL A01G

4.2.2 Item Unique Identification

The contractor shall develop an Item Unique Identification (IUID) Marking Plan to develop and incorporate Item Unique Identification (IUID) markings on Contractor-recommended and Government-approved subsystems/components. The contractor shall place ident-a-plates on the In-Water Subsystem and spares. The contractor shall obtain Government approval of label/ident-a-plates layouts prior to placement on the In-Water Subsystem and spares.

Deliverables:

The contractor shall deliver the following:

Item Unique Identification (IUID) Marking Plan IAW CDRL A01E Item Unique Identification (IUID) Marking Activity, Validation and Verification

Report IAW CDRL A01F

4.2.3 In-Water Subsystem Requirements Analysis and Functional Allocation Using a Model Based Systems Engineering (MBSE) USWTR IWS model, the contractor shall create and maintain a System/Subsystem Specification (SSS), Software Requirements Specification (SRS) and Interface Requirements Specification (IRS). The SSS shall conduct an IWS analysis to breakdown capabilities into discrete elements that total a set of system requirements and interfaces based upon GFI #6.1.1 (USWTR Inc.

III In, -Water Subsystem Performance Specification) and GFI #6.1.31 (USWTR Increment II In-Water Subsystem Performance Specification). The contractor shall further allocate requirements into the subsystems, specifications, and baseline documentation. The contractor shall create and maintain an interface control document using the data from the SSS, SRS, and the IRS.

Deliverables:

The contractor shall deliver the following:

System/Subsystem Specification (SSS) IAW CDRL A00K Software Requirements Specification (SRS) IAW CDRL A00L

Interface Requirements Specification (IRS) IAW CDRL A00M Interface Control Document (ICD) IAW CDRL A00N

4.2.4 Physical Component Design and Interface Control

Using the MBSE USWTR IWS model, the contractor shall define the IWS subsystems, auxiliary equipment, and support equipment performance and physical characteristics, component locations, materials, software, and interfaces. The contractor shall use the model results and create design descriptions and an interface control document.

Deliverables:

The contractor shall deliver the following:

Interface Design Description (IDD) IAW CDRL A00P Software Design Description (SDD) IAW CDRL A00Q System Subsystem Design Descriptions (SSDD) IAW CDRL A00R Interface Control Document (ICD) IAW CDRL A00N,

4.2.5 Environmental, Safety and Occupational Health

The contractor shall establish, implement, and manage an Environmental, Safety, and occupational Health (ESOH) program IAW applicable document #3.1.2 (MIL-STD-882E System Safety). The ESOH program shall perform system safety hazard analysis to identify hazards and assess risks for the total system design (including software) and for subsystem interfaces. The ESOH program objective shall reduce or eliminate hazards to equipment, personnel or the environment. The ESOH program shall reduce the use of hazardous materials and substances and generation of hazardous waste during the system life cycle. The contractor shall perform an analysis to assess the design from a hazardous substance and waste perspective. This analysis shall address hazardous substances used in the design and manufacturing process and hazardous substances required or generated during maintenance, use, demilitarization, salvage, and disposal of the system. The analysis shall identify all components and equipment, containing software whose performance, performance degradation, functional failure or inadvertent functioning, due to reasonable human errors, could result in a hazard. Specific mitigation efforts shall be identified and the residual risk after implementation in the analysis. The contractor shall address the impact of using less hazardous or nonhazardous alternatives or substitutes and provide rationale (performance, cost, etc.) for using each particular hazardous substance chosen.

System Safety Hazard Analysis Report (SSHAR) IAW CDRL A00U

4.2.6 Reliability and Maintainability

The contractor shall create a Reliability and Maintainability (R&M) program plan. The plan shall describe the conduct of the R&M program. The R&M Plan shall detail the IWS reliability and maintainability design and analysis process and contain, as a subset, fault detection and fault isolation. The Failure Modes, Effects, and Criticality Analysis (FMECA) approach, planning and integration for the IWS shall be included in the R&M Plan. The R&M Plan shall require that the functional block diagrams and mathematical models for the allocated baseline analyze hardware and software system/subsystem functions and evaluate risks associated with the achievement of all specified reliability and maintainability requirements. The contractor shall perform maintainability and reliability predictions using FMECA (see subsection 4.2.7 of this SOW) and applicable document #3.1.3 (MIL-HDBK-217F Reliability Prediction of Electronic Equipment).

Deliverables:

The contractor shall deliver the following:

Reliability and Maintainability Program Plan IAW CDRL A00V Reliability and Maintainability (R&M) Block Diagrams and Mathematical Models

Report IAW CDRL A00W Reliability and Maintainability Predictions Report IAW CDRL A00X

4.2.7 Failure Modes, Effects and Criticality Analysis

The contractor shall perform a Failure Modes and Effects Criticality Analysis (FMECA) for the IWS. The contractor shall utilize the functional block diagrams for the allocated baseline presented at Preliminary Design Review (PDR) to analyze hardware and software system/subsystem functions and evaluate risks associated with the achievement of all specified reliability requirements. The contractor shall analyze the detailed design to piece part levels to ensure that the specified reliability requirements can be achieved.

The FMECA shall account for the environmental and operating stresses of parts based upon the piece part analysis. The contractor shall utilize and maintain design de-ratings for all types of parts and materials to provide for reliable operation at the maximum operating stress levels.

The FMECA shall validate equipment/system block diagrams and predicted reliability values provided in functional and allocated baselines, identify all potential item and interface failure modes, evaluate each failure mode in terms of the worst potential consequences, identify the failure mode failure detection method and compensating provisions, and contain a Reliability Critical Items List.

The contractor FMECA submission prior to the PDR shall addresses 100% of the system functions. The subsequent FMECA submission prior to CDR shall support failure mode analyses that accurately represents the complete system configuration. The FMECA shall document all failure modes down to the piece part level. All single point failure modes having the most serious effects, particularly the single point failures which directly result in loss of function or create unsafe conditions shall be identified, evaluated and minimized via the design process. Additional FMECA submissions shall be required for design changes or failures during testing which identify failure modes not documented in the previous FMECA submission.

Deliverables:

The contractor shall deliver the following:

Failure Modes, Effects, and Criticality Analysis IAW CDRL A00Y Reliability Critical Items List IAW CDRL A01A.

4.2.8 Electromagnetic Compatibility and Interference Control

The contractor shall perform an Electromagnetic Environmental Effects (E3) Integration Analysis for the SES IAW applicable document #3.1.1 (MIL-STD-464C, Department of Defense Interface Standard: Electromagnetic Environmental Effects, Requirements for Systems). The results shall be used during the IWS production engineering. The results shall be documents in an Electromagnetic Environmental Effects (E3) Integration and Analysis Report.

Deliverables:

The contractor shall deliver the following:

Electromagnetic Environmental Effects (E3) Integration and Analysis Report

(E31AR) IAW CDRL A00G

4.2.9 Software Development

The contractor shall create a Software Development Plan (SDP) identifying the all contractor software processes. The SDP shall contain software schedules and milestones.

The contractor shall detail the processes and procedures for subcontractors and suppliers.

The SDP shall contain software metrics with the following: software quality, software schedule, software size (source lines of code), software organization (staffing volatility), requirements volatility, and processor/memory/bus utilization.

The contractor shall implement software development, measurement, metrics, and certification processes in accordance with applicable document #3.3.3 (IEEE 12207.2 Annex J Systems and software engineering -Software life cycle processes). These requirements shall be followed by subcontractors with software development activities.

The contractor shall implement software development processes, and those processes shall align IAW applicable document #3.3.3 (IEEE 12207.2 Annex J) priority schema for software defect priorities. The contractor shall generate a Software Change Report (SCR) when the need for a software change or a software deficiency/anomaly has been identified IAW this SOW subsection 4.2.18 (Engineering Change Proposals [ECP]).

Deliverables:

The contractor shall deliver the following:

Software Development Plan IAW CDRL A010 Software Development Summary Report IAW CDRL A011 Software Reuse Plan and Analysis IAW CDRL A012

4.2.10 Data Management

The contractor shall implement data management controls IAW applicable document #3.3.4 (Implementation Guide for Data Management). These controls shall address quality of data preparation, compliance with data specifications, timely delivery of data, and on-going scrutiny of the contract data requirement list for potential beneficial changes. The contractor shall establish a process to track all contractor developed documentation and provide reporting in a Data Accession List (DAL).

Deliverables:

Data Accession List IAW CDRL A00Z

4.2.11 Cybersecurity

The contactor cybersecurity workforce shall have Security+ (Plus) Certification upon submission or proposal. In performance of this task, the contractors cybersecurity workforce shall be trained and certified within 180 calendar days after contract award to information Assurance Technical (IAT) level 1 IAW applicable document #3.1.13 (DoD 8570.01M; Information Assurance Workforce Improvement Program). The contractor shall develop systems and subsystems and mange development using the DOD’s Risk Management Framework (RMF) process to ensure it meets cybersecurity compliance IAW applicable document #3.1.6 (DODI 5000.02; Operation of the Defense Acquisition System

- December 2008; http://www.esd.whs.mil/DD/). The contractor shall only acquire Commercial off The Shelf (COTS) software application listed and approved in the Department of the Navy (DoN) Application and Database Management System (DADMS).

The contractor shall create Information Assurance Vulnerability Management Program (IAVMP). The contractor shall use the IAVMP to identify, implement, mitigate and report system security patch and update status. The IAVMP shall include creating new, expanding existing, and updating existing Original Equipment Manufacturer. The contractor shall ensure that the In-Water Subsystem incorporates Cybersecurity-Enabled Operating Systems that have been validated or are under evaluation by National Information Assurance Partnership (NIAP) or Common Criteria (CC) scheme and are as follows:

1. Configurable IAW applicable DoD Security Technical Implementation Guides (STIGs) or System and Network Attack Center (SNAC) guides, and Security Requirements Guides (SRG’s). The STIG and SNAC guides are available at https://public.cyber.mil/ (applicable document #3.1.4).

2. Able to incorporate the DoD Information Assurance Vulnerability Management Program (IAVMP) in accordance with applicable document #3.1.6 (DODI 8500.2m Operation of the Defense Acquisition System - December 2008)

3. Supportable for the expected lifecycle of the system. The contractor shall ensure that the system shall incorporate the DOD licensed virus protection software available at the following DOD website: https://patches.csd.disa.mil (applicable document #3.1.4).

NAVAIR Program Cybersecurity Implementation Plan IAW CDRL A013 Naval Aviation Cybersecurity Test Reports IAW CDRL A014

4.2.12 Suppliers Configuration Management Program

The contractor shall develop and maintain a Supplier’s Configuration Management (CM) plan IAW applicable document #3.3.5 (ANSI/EIA-649 National Consensus Standard for Configuration Management) and #3.1.7 (MIL-HDBK-61A Configuration Management Guidance) program. The contractor shall require its subcontractor(s) and suppliers to comply the contractors plan. The plan shall identify Configuration Items (CI) inclusive of the determination of the types of configuration documentation required for each CI; the issuance of numbers and other identifiers affixed to the CIs configuration (including internal and external interfaces); the release of CIs and their associated configuration documentation; and the establishment of configuration baselines for CIs. The plan shall be used to coordinate and recommend selected hardware, software, and firmware configuration items for Government approval. The plan shall be used for maintaining the Government approved CI baselines. The plan shall ensure each succeeding baseline is traceable to, and a detailed extension of its predecessor(s).

Deliverables:

The contractor shall deliver the following:

Supplier’s Configuration Management Plan IAW CDRL A015 Configuration Status Accounting (CSA) Information IAW CDRL A016

4.2.13 Configuration Audits

The contractor shall host Government-led configuration audits at the contractor’s facilities IAW Table 2. Audits at subcontractor facilities shall be led by the contractor with Government participation. The contractor shall prepare for the audits IAW Tables 2 and 3, applicable document #3.2.3 (NAVAIR Instruction 4355.19E) and GFI #6.1.5 (USWTR System Engineering Plan). Table 2 correlates audits to contract line items. Table 3 identifies specific CDRLs used as entry criteria to the each event. The contractor shall develop a Configuration Audit Plan for PCA(s) and FCA(s). The contractor shall make available the test and analysis data for use by government attendees at each event. The Government will conduct audits on the lowest replacement unit subassemblies prior to insertion into the next assembly for which that subassembly is no longer visible. The contractor shall accommodate ten Government or Government contractor employees’ at each Audit. The contractor shall notify the Government ten business days in advance of an audit. The contractor shall provide and agenda for each audit.

The contractor shall prepare summary reports after each audit. The report shall document the procedures, conduct, discrepancies, and findings of the configuration audit.

The audit reports shall include disposition of all findings and certify all completed actions.

The Government will provide request for action(s) IAW GFI #6.1.25 (Requests for action) after each audit The contractor shall complete and implement all actions identified IAW GFI #6.1.25 (Requests for action). The contractor shall record, track, and complete action items.

The contractor shall deliver the following:

Configuration Audit Summary Report IAW CDRL A017 Report, Record of Meeting Minutes IAW CDRL A006

Configuration Audit Plan IAW A00S

4.2.14 Diminishing Manufacturing Sources and Material Shortages The contractor shall develop and maintain a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management plan IAW applicable #3.3.6 (SAE STD-0016 Standard for Preparing a DMSMS Management Plan).

The contractor shall perform DMSMS reporting and deliver a report. The report shall include identification of DMSMS/Obsolescence issues, comprehensive business case analysis of risks, cost and readiness impacts, best value alternatives, and strategies for issue resolution. The contractor shall modify the reliability critical items list coincident with the DMSMS report.