J-1-SOW (Updated 12082020).docx

Undersea Warfare Training Range (USWTR) Increment II and III In-Water Subsystem (IWS) and Atlantic Undersea Test and Evaluation Center (AUTEC) Sensor Replacement Program (ASRP)

Statement of Work Solicitation Number N61340-21-R-0006 USWTR Increments II and III and ASRP Revision 3 4 December 2020

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICE, AVIATION COMMON SYSTEMS AND COMMERCIAL SERVICES (PEO (CS))

NAVAL AIR SYSTEMS COMMAND, PMA205

PATUXENT RIVER, MD 20670

USWTR Increment II/III Statement of Work Initial Revision 3

DISTRIBUTION STATEMENT A. Approved for public release.

This page intentionally left blank

REVISIONS

Sheet Index

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

Management System

Table of Contents

List of Figures No table of figures entries found.

List of Tables

USWTR Increment II/III Statement of Work Rev2

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

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.

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 develop and build the above Underwater Training Ranges IAW the requirements defined in 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).

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), and the Southern California Anti-Submarine Warfare Range (SOAR). In addition, this TDP will be utilized to procure Atlantic Undersea Test and Evaluation Center (AUTEC) UTR, which allows for commonality across deep water training and test ranges. The contractor shall create shallow water product drawings leveraging GFI #6.1.32 (USWTR Increment I Technical Data Package) for the following West Coast Shallow Water Training Range (WC-SWTR): Tanner Bank (TB) Shallow Water Training Range (TB SWTR) and San Clemente Island (SCI) Shallow Water Training Range (SCI SWTR). This provides commonality across existing and new shallow water ranges as well as between the deep and shallow water ranges.

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 obtain environmental approvals and permits. Best management practices and environmental mitigation measures will be provided 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.

Specific Programs/Systems This section identifies the following six ranges and their location.

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

Specific Requiring Department Codes/Customers/Users of the Contract The requiring department codes/customers/users of this contract include the following:

Program Executive Office Aviation Common Systems and Commercial Services PEO(CS) NAVAIR Engineering, Navy Major Range and Test Facility Base (MRTFB) Program Management Division V542 Naval Undersea Warfare Center Division Newport, Code 70

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

Office of the Chief of Naval Operations (OPNAV), Technology Requirements and Test and Evaluation (N94)

PEO (CS)

NAVAIR Engineering, Navy MRTFB Program Management Division V542

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); All AUTEC tasks are funded by NAVAIR Engineering, Navy MRTFB Program Management Division V542 Applicable Documents In performance of this SOW, the contractor shall use and comply with applicable regulations, policies, and documents listed the documents provided in Table 1. If a conflict exists between the applicable document and the GFI, the GFI shall take precedence.

Table 1 Applicable Documents[footnoteRef:2] [2: Applicable documents are publically available]

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 PEO (CS) PMA205) during performance of meetings, reviews, site visits, and field installations at the ranges. The contractor shall propose, 90 calendar days in advance, IWS installation dates within the Government identified installation window identified in Installation subsections. The contractor shall provide a request to visit Government Furnished Facility (GFF) 30 calendar days in advance of contractor proposed 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 #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 #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 #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; PEO (CS), PMA205, Patuxent, Maryland). The performance shall be for meetings and events at NAVAIR.

The contractor shall safeguard classified information and meet the Security requirements outlined in the DD245 which includes OPSEC Requirements. 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 related 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 Controlled Unclassified Information (CUI). 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 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 CUI 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 Public Release (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 a proposed public release request to the Government for review and approval 30 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: PEO (CS), 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.

Task A (CLIN 0001, 0106, 0207, 0306, 0406, 0503, 0604, 0704, 0806, 0905) Technical Review: Technical Program Management

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 contractor shall conduct a Schedule Risk Assessment (SRA) semi-annually, which shall be facilitated by participants from the Government. The SRA shall be conducted in accordance with the Government, DI-MGMT-81861B and in CDRL A002.

The contractor shall add the following items to the IMS:

a) Manufacturing Time-Phase Schedule that logically represent events in the manufacturing process to ensure contract requirements are met including

a. Development, design, redesign, and test efforts for system elements,

b. Facility construction of modifications,

c. Design, fabrication, and delivery for special tooling, special test equipment and test support equipment

d. Implementation schedules of major elements of the manufacturing process

e. Development and testing of software necessary to support manufacturing or testing,

f. Subcontractor deliveries including Critical/Strategic Material deliveries,

g. Government property need dates,

h. First article inspections,

i. End item delivery schedules.

b) Plans for performing detailed software development activities, software schedules and milestones.

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

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

Technical Interchange and Program Management Meetings The contractor shall conduct, support, and attend semi-annual Technical Interchange Meetings (TIM) at the contractor’s facility. The Government will conduct semi-annual Program Management Reviews (PMR) at a Government facility IAW GFF #6.3.6 (Office Facilities; NAVAIR, PEO (CS), PMA205, Patuxent, Maryland) or #6.3.7 (Office Facilities; NUWCDIVNPT, Newport, Rhode Island). 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:

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

· Schedule status, variance, and schedule risk assessment

· Risk assessment and its mitigation

· Review of action items

· Summary of non-conformance items and request for variance Technical Review; System Engineering including the following:

· Model Based System Engineering (MBSE) effort, specifications, and interfaces

· Technical discussion of CDRL delivered and in-process, CDRL look ahead and address delinquent CDRL deliveries

· Cybersecurity status

· Test and Evaluation Program Plan status

· Diminishing Manufacturing Sources and Material Shortages (DMSMS)/Obsolescence Plan/Status

· Software development, metrics, and changes Technical progress and performance for Production Engineering, Procurement, Production, Test, Installation and Training including the following:

· Product Drawings/Models & Associated List new or revised from the previous meeting

· Assessment of manufacturing readiness

· Review of test planning and results

· Installation engineering and planning

· Integrated logistics support identified various subsections

· Status of procurements, time phased production status

The TIM/PMR immediately prior to the Test Readiness Review (TRR) (a SETR defined in this SOW subsection 4.2.16) shall include additional topics. The additional topics are TRR entrance criteria identified in applicable document #6.1.5 (USWTR System Engineering Plan). The additional topics will be an extra day after closing the TIM/PMR.

The TIM/PMR immediately prior to the Factory Acceptance Test (FAT) shall include additional topics. The additional topics are a specific review of the FAT plan. The additional topics will be an extra day after closing the TIM/PMR.

The TIM/PMR immediately prior to the Site Acceptance Test (SAT) shall include additional topics. The additional topics are a specific review of the SAT plan. The additional topics will be an extra day after closing the TIM/PMR.

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. 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 (subtitle: Contract Award Kickoff) within 10 calendar days after contract award (DACA). The contractor shall ensure major subcontractors participate in this TIM. The purpose shall define contract expectations including a review of the SOW and Government Furnished Information The second TIM/PMR shall be 90 days after the completion of the TIM (subtitle: Contract Award Kickoff). The second TIM/PMR will be a PMR.

Deliverables:

The contractor shall deliver the following:

· Report, Record of Meeting Minutes IAW CDRL A006

· Presentation Materials IAW A007

· Conference Agenda IAW A008

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 or the specifications. RFV shall include deviations from specifications.

Deliverables:

The contractor shall deliver the following:

· Request for Variance IAW CDRL A00H

Integrated Product Team Teleconferences The contractor shall participate in Government led Integrated Product Team (IPT) weekly program management and engineering teleconferences. Management and engineering teleconferences shall be on different days of the week and rotate weekly. 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

· Non-conformances, deficiencies, failure reports and corrective actions

· 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 30 calendar days after contract award. The contractor shall perform the first engineering teleconference within 45 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

· Conference Agenda IAW A008

Task B (CLIN 0001, 0106, 0207, 0306, 0406, 0503, 0604, 0704, 0806, 0905) Technical Review: System Engineering

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 develop and maintain 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 assessment reports.

The contractor shall use the Government’s Integrated Modeling Environment (IME) to perform Model Based System Engineering (MBSE). The contractor shall create and maintain a Systems Modeling Language (SysML) architectural USWTR IWS model utilizing the Cameo Systems Modeler (contractor supplied). The contractor model shall use 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 GFI #6.1.23 (USWTR System Model Management Plan), and GFI #6.1.43 (USWTR IWS baseline model). The model shall be employed for requirements analysis, functional allocation, physical component design, performance modeling to determine system performance, and external/internal definition and control. The contractor shall create the MBSE IWS system model comprising the SysML/Cameo artifacts and source files to the Government in the models native format. The contractor shall provide real-time review access to the IWS model at SETR events and TIMs. Government and contractor virtual collaboration via the IWS model shall occur throughout the system development process. Government and contractor access and exchange of Cameo model artifacts shall be enabled and occur from contract award to the end of the period of performance. The Government will provide access to the Government’s IME Teamwork Cloud.

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:

The contractor shall deliver the following:

· Systems Engineering Management Plan (SEMP) IAW CDRL A00E

· Quality Assurance Program Plan (QAPP) IAW CDRL A00F

· Quality Assessment Report (QAR) IAW CDRL A00A

· Computer Software Product End Items IAW CDRL A01R including an unlocked and unprotected USWTR IWS model

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. The location of layouts shall be identified in CDRL A01G.

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

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

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 Description (SSDD) IAW CDRL A00R

· Interface Control Document (ICD) IAW CDRL A00N, 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.

Deliverables:

The contractor shall deliver the following:

· System Safety Hazard Analysis Report (SSHAR) IAW CDRL A00U

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

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.

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

Software Development The contractor shall create a Software Development Plan (SDP) identifying the 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 Request (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

Data Management The contractor shall implement data management controls IAW applicable document #3.3.4 (ANSI/GEIA-859 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:

The contractor shall deliver the following:

· Data Accession List IAW CDRL A00Z

Cybersecurity For Information Technology systems developed under this contract, the contractor shall define its Cybersecurity Workforce (CSWF) requiring Cybersecurity (CS) certifications IAW applicable document #3.1.13 (DoD 8570.01M; Information Assurance Workforce Improvement Program) with level approval by the Government. Contractor personnel in the CSWF shall fulfill the certification requirements IAW DoD 8570M. All identified CSWF personnel identified by the contractor and level approved by the government are required to be certified with criteria IAW DoD 8570M within six months of contract award. The contractor shall provide a copy of CWSF certifications and a screenshot of their CompTIA dashboard to the Government. The contractor shall not be required to enter the CSWF certifications in the personnel system referenced in DoD 8570M.

The contractor shall develop systems and subsystems and manage 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 that are listed and approved in the Department of the Navy (DoN) Application and Database Management System (DADMS) (applicable document #3.2.4).

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 (STIG) or System and Network Attack Center (SNAC) guides, and Security Requirements Guides (SRG). 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…