Attachment - DRAFT Statement of Work.pdf

STATEMENT OF WORK

(SOW)

Undersea Weapons and Undersea Defensive (UW/UD)

Family of Systems (FOS) Multiple Award Contract (MAC)

1.0 Background

Undersea Weapons encompass systems that deliver ordnance to a designated target and can operate independently from or in concert with submarines and other undersea weapons.

Undersea Defensive Systems encompass systems that obfuscate and destroy threats to friendly undersea and surface assets. Mission roles for Undersea Weapons and Undersea Defensive (UW/UD) Family of Systems (FoS) include: search, detection, classification, location, tracking, weapon targeting and placement, countermeasures, and communications.

The Undersea Warfare (USW) Weapons, Vehicles, and Defensive Systems Department (Code

85) of the Naval Undersea Warfare Center, Division Newport (NUWCDIVNPT) is responsible for all aspects of the development of Navy UW/UD systems, including torpedoes and defensive systems, associated test equipment, laboratory and test facilities, Modeling and Simulation (M&S), Test and Evaluation (T&E), and transition of new technologies from Science and Technology (S&T) and other research efforts. Code 85 performs system engineering and system integration tasking for all life cycle phases of UW/UD FoS. This includes requirements definition, design, development, integration, and test of product upgrades and ancillary test equipment; software development; prototype hardware procurement and production support activities; system performance analysis, operational readiness support, system integration, and systems engineering; and technical support for Foreign Military Sales (FMS).

The Navy is facing a rapidly changing and increasingly lethal threat environment globally. As a result, an increased demand for undersea weapons and defensive systems prototyping and experimentation supporting undersea dominance has driven funding investments from multiple sponsors to develop solutions to Fleet needs for the entire UW/UD FoS lifecycle.

1.1 Places of Performance

Places of performance will be identified in each individual order.

1.2 Authorized Users

NUWCDIVNPT Code 85 is the only authorized user.

1.3 Sponsors

The procurement and delivery schedule quantities to be awarded within this contract will be primarily funded by:

OPNAV Expeditionary Warfare Division (N95) OPNAV Surface Warfare Division (N96) OPNAV Undersea Warfare Division (N97) OPNAV Air Warfare Systems (N98) Office of Naval Research (ONR).

The Program Offices involved are:

The Columbia Class Program Office (PMS397) The Submarine Acoustic Systems Program Office (PMS401) The Undersea Weapons Program Office (PMS404) Unmanned Maritime Systems (UMS) Program Office (PMS406) The Undersea Defensive Warfare Systems Program Office (PMS415) Littoral Combat Systems (LCS) Mission Modules (PMS420) The Virginia Class Program Office (PMS 450) Office of Naval Research (ONR) Office of Naval Intelligence (ONI) Royal Australian Navy (RAN) under an Armaments Cooperative Agreement Defense Advanced Research Projects Agency (DARPA) The Strategic Capabilities Office (SCO)

Specific sponsors will be identified in each individual order.

1.4 Types of Funding

The following appropriations will be used to fund this requirement:

Research, Development, Test & Evaluation, Navy (RDT&EN) Operation and Maintenance, Navy (O&MN) Other Procurement, Navy (OPN) Weapons Procurement, Navy (WPN) Foreign Military Sales (FMS) Special Deposit (SPDP) Defense Working Capital Funds (DWCF) Research, Development, Test & Evaluation, Department of Defense (RDDA) Research, Development, Test & Evaluation, Air Force (RDAF) Operations and Maintenance, Department of Defense (OMDA) NUWC Overhead/Service Cost Center (SCC/CIP) Shipbuilding and Conversion, Navy (SCN)

2.0 Scope

The scope of this contract covers systems and subsystems required to support the advancement of the Undersea Weapons and Undersea Defensive Family of Systems (UW/UD FOS), including current UW/UD systems and subsystems as well as any future UW/UD systems and subsystems.

The scope of this contract also covers support for UW/UD prototypes not specifically developed under this contract vehicle, as well as on-going maintenance and support for current and future UW/UD systems and subsystems. The scope of this contract includes support for NIXIE, an antitorpedo countermeasure towed by surface vessels.

The current UW/UD systems include:

Surface ship, submarine, and air launched torpedoes Surface ship and submarine expendable countermeasures Surface ship and submarine towed persistent countermeasures Torpedo Detection, Classification, and Localization (TDCL) systems Unmanned Undersea Vehicle Detection, Classification, and Localization (UUV-DCL) systems Unmanned Undersea Vehicle undersea defensive system countermeasure sensor and payload systems Anti-Torpedo Torpedoes (ATT)

The contractor shall design, develop, fabricate, test, install, document and deliver rapid prototype material solutions associated with the development of Navy torpedoes and associated with the UW/UD products, systems, subsystems, and ancillary support equipment. These material solutions are intended to allow the Government to develop a sufficient understanding of alternative solution sets that are deemed critical in providing accelerated operational capability or in response to identified emergent threats. Material solutions will be employed in performance demonstrations to assess their operational utility, explore Anti-Submarine Warfare (ASW) and Anti-Surface Warfare (ASuW) development capabilities, mature technology, refine requirements and otherwise reduce the risk of current or anticipated capability gaps.

2.1 Functional Areas

Supplies and services under this contract are for research, development, prototyping, production, operations, maintenance, upgrades and all life cycle phases for the UW/UD FoS and include the following Functional Areas:

1. Payloads: Payloads complete a weapon or defensive system’s tasked mission.

Payloads may include a warhead section, a fleet exercise section, towed cables and systems, sensors or other modular payload systems. Sensors may be used to actively transmit or receive energy or to measure environmental conditions.

2. Hull and Structure: Hulls are the main body of weapon or defensive systems and may be made of a variety of materials such as aluminum or composite materials. Hulls may be free flood, dry or hybrid. Hulls include any pressure vessels. Structures include the ribs, bulkheads, seals, and joint connectors or bands. Also included in hull and structure are the outer coatings such as anodizing, paint, or other coatings.

3. Propulsion: The propulsion subsystem converts the energy supplied from the energy subsystem to kinetic energy to provide movement of the weapon or defensive system. Propulsion includes fuel or energy delivery; the motor or engine; gearing or transmission; shaft; propulsor, and control surfaces.

4. Energy Storage and Conversion: The energy storage and conversion subsystem may include an energy module; monitoring system; sensor amplification system;

emergency energy supply; energy conversion; and charging. Energy modules may include primary or secondary batteries, fuel cells, aluminum combustion, stored chemical energy, or other novel form of energy storage.

5. Electrical Power: The electrical power subsystem supplies and transfers data and power throughout the weapon or defensive system. Electrical power may include power supplies, amplifiers, energy storage, wiring, cabling, buses, connectors, power conditioning, and networking subsystems.

6. Software: Software includes the algorithms, programs, programming language and data used to direct the operation of a computer system, as well as documentation giving instructions on how to use them. Software also includes firmware. Software may be used in the weapon or defensive system; or as part of a system that supports or interfaces with the weapon or defensive system; or as part of the system that is used in ancillary equipment.

7. Non-Payload Sensors: Non-payload sensors are sensors that are organic to the weapon or defensive system and are required for the operation of the weapon or defensive system. Non-payload sensors may be installed on surface ships or submarines and integrated with the weapon or defensive system. Non-payload sensors may include sonar systems, transducers, temperature, pressure and conductivity sensors, Doppler velocity log, Global Positioning System (GPS), inertial measurement systems, accelerometers, and other non-acoustic sensor systems.

8. Guidance and Control System: The guidance and control system enables the weapon or defensive system to conduct its missions. The guidance and control system may include navigation, control surfaces and actuators, vehicle control, data recorder and storage, and communications. Navigation may include inertial navigation, nontraditional navigation, and other systems that provide improved navigation awareness. Communication may include physically tethered systems such as copper wires or fiber optics, over-the-air/radio frequency (RF) systems, and acoustic communications systems.

9. Launch Platform Interface and Shipboard Systems: Launch Platform Elements are the systems and subsystems that enable a weapon or defensive system to be integrated, controlled, deployed, launched, operated, and recorded from a launch platform. These systems and subsystems may include computers and associated electronics; hardware, software, data, electrical, and electrical interface systems; payload control systems; and towed system handling equipment. Air, rocket, or other non-traditional launch systems or platforms are included in this functional area.

10. Ancillary Equipment: Ancillary Equipment includes the systems and subsystems that support the maintainability and operation of the weapon or defensive system. These include, but are not limited to, depot factory test equipment, In-Service Support Equipment, logistics equipment, maintenance equipment, system surveillance equipment, stimulation equipment, and test vehicles.

11. Modeling and Simulation: This functional area consists of the application of a standardized, rigorous, structured methodology to create and validate a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process that is associated with the weapon’s or defensive system’s capabilities.

This functional area involves the use of models, including emulators, prototypes, simulators, and stimulators, either statically or over time, to develop data as a basis for making technical, strategic, or tactical decisions, and verifying and validating system requirements. This also includes the application of parallel processing and computing techniques to speed the execution rate of simulations.

12. Data Analytics: This functional area consists of software data analysis and display tools to provide insights into large volumes of structured system performance data. This includes descriptive analytics tools that identify trends, patterns, and cause -and effect relationships in historic data sets, predictive analytics tools that identify patterns that indicate future situations and behaviors, and prescriptive analytics tools that suggest actions to best take advantage of predicted scenarios. Data display tools include tools and interfaces that support the organization, structure, and presentation of data in ways that support learning and data-backed conclusions.

Important Note: The SOW Attachment 1, Functional Area vs. Requirements Matrix, maps each requirement in Section 4 of the SOW to each functional area.

3.0 Applicable Documents

The contractor shall perform the tasking required in Section 4.0 in accordance with (IAW) the below Applicable Documents (ADs), and any other program documents specified within individual delivery and task orders.

Inde x

Applicable Document Name Revision

Applicabl e

SOW

Tasks

3.1 ANSI/ISO/ASQ 9001, Quality Management Systems 2015 4.0.1.2

3.2 MIL-STD-31000B, Department of Defense Standard Practice, Technical Data Packages

Revision B (31

October 2018)

4.0.1.3

3.3 MIL-STD-46855A, Human Engineering Requirements for Military

Systems, Equipment, and Facilities

Revision A (24 May

2011)

4.2.1.4

3.4 Naval Systems Engineering Technical Review (SETR) Handbook Version 1 4.0.1.1

3.5 NAVSEA 05H Technical Review Manual (TRM)

Version

2.0 (18

Dec 2009)

4.0.1.1

3.6 NAVSEA Instruction 5000.8 Naval SYSCOM Risk Management Policy 21 July

4.0.1.1

3.7

OPNAVINST S5513.5C – Undersea Warfare Program Security Classification Guides (SCGs) SCG ID: 139.2, MK 48 ADCAP (MODS 5 and beyond), MK

50, AND MK 54 Torpedoes, as clarified by PMS404/0643 Memo “MK 54 Classification Guidance Clarification”

20 May

All

3.8 DoD Program Manager’s Guidebook for Integrating the

Cybersecurity Risk Management Framework (RMF) into the System Acquisition Lifecycle (Version 1.0)

Septembe r 2015 All

3.9 DoD Cybersecurity Test and Evaluation Guidebook (Version 2.0)

February

4.3

3.10 DoDI 8500.01 Cybersecurity

14 March

All

3.11

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

(https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodi/850001_20 14.pdf )

12 March

All

3.12 NIST SP800-30, Guide for Conducting Risk Assessments (http://csrc.nist.gov/publications/PubsSPs.html#800-30 )

Septembe r 2012 4.0.1.1

3.13 NAVSEA 9400.2-M, NAVSEA PIT-Control System Cybersecurity

Implementation Manual, (NAVSEA Manual, Ser 05H/096, dtd 06 Oct 2016) (Authorization document: NAVSEA Instruction, Ser 00/365, dtd 20 Sep 2016, Version 5 October

All

3.14 DoD Supply Chain Risk Management (SCRM) Key Practices and

Implementation Guide

February

All

3.15 DoD Security Technical Implementation Guidance (STIGs)

(https://public.cyber.mil/stigs/) N/A All

3.16 DoD Security Requirements Guides (SRGs) (https://public.cyber.mil/stigs/) N/A All

3.17 Manufacturing Readiness Level (MRL) Deskbook 2020

Version

4.0.1.1

3.18 DOD 5000.04-M-1 Contractor Cost Data Reporting Manual

Novembe r 2011

4.0.1.1

3.19 MIL-HDBK-2155 Failure Reporting, Analysis and Corrective Action Taken

Decembe r 1995

4.2.3

3.20 MIL-STD-882E System Safety Program Requirements

11 May

All

3.21 MIL-STD-130N Identification Marking of U.S. Military Property

Decembe r 2007

4.5

3.22 IEEE STD 12207 Systems and Software Engineering - Software life Cycle

Processes

Novembe r 2017 All

3.23 DoD 8570.01-M Information Assurance Workforce Improvement Program, incorporating change 4

Decembe r 2005 change 4 (10 Nov.

2015)

All

3.24 DOD 5220.22 National Industrial Security Program Operating Manual, incorporating change 3

18 March

Change 3 (10 Dec.

2021)

All

3.25 ANSI/EIA-649-C National Consensus Standard for Configuration

Management

February

All

3.26 ANSI/EIA-748-D Alliance Standard Earned Value Management Systems

January

4.0.1.1

3.27 SAE ARP 5580 Recommended failure modes and effects analysis (FMEA) practices for non-automobile applications

August

4.2.3

3.28 SAE AS5553D Counterfeit Electrical, Electronic, and Electromechanical

(EEE) Parts; Avoidance, Detection, Mitigation, and Disposition 14 April

4.2

3.29 SAE AS6462C Fraudulent/Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition Verification Criteria

Novembe r 2019 4.2

3.30 SAE AS6081 Fraudulent/Counterfeit Electronic Parts: Avoidance, Detection, Mitigation, and Disposition – Distributors

Novembe r 2012 4.2

3.31 SAE ARP6178 Fraudulent/Counterfeit Electronic Parts; Tool for Risk Assessment of Distributors

Decembe r 2011 4.2

3.32 SAE AS6174A Counterfeit Materiel; Assuring Acquisition of Authentic and Conforming Materiel

29 July

4.2

3.33 SAE AS6301 Compliance Verification Criterion Standard for SAE AS6081, Fraudulent/Counterfeit Electronic Parts: Avoidance, Detection, Mitigation, &

Disposition-Dist

January

4.2

4.0 Technical Requirements

The contractor shall perform the tasks in Section 4.0 in accordance with individual Task Orders and Delivery Orders (TO/DOs) and Applicable Documents (Section 3.0) and using Government Furnished Information (GFI) (Section 6.0) for the functional areas identified in Section 2.1.

For any severable work, as identified at the Task and Delivery Order level, the contractor shall perform tasking in accordance with Technical Instructions (TIs) issued with individual Task and Delivery Orders. TO/DOs will identify the specific tasks within the scope of this SOW to be performed as particular needs are identified. TO/DOs will also identify the specific system, Applicable Documents and GFI the Government anticipates will be required, and processes for performing the required tasking.

4.0.1 Program Management

4.0.1.1 Technical Interchange Meetings (TIMs) and Program Management Meetings

The contractor shall conduct and participate in TIMs including program management reviews (PMRs) and technical reviews. The contractor shall provide working level status and tasking updates, technical presentations and task reporting. The contractor shall conduct design reviews to present prototype concepts, review performance against requirements and specifications, identify risks and concerns, and validate design methods and approaches. The Government will establish the meeting schedule and the agenda. The contractor shall provide presentation materials and meeting minutes for all TIMs.

Deliverables:

The contractor shall deliver Presentation Material IAW CDRL A001 and Meeting Minutes IAW

CDRL A002.

4.0.1.2 Quality Assurance

The contractor shall deliver, for Government review and approval, a Quality Control Plan (QCP) that documents the processes that ensure conformance to TO/DO requirements and meet the requirements of AD 3.1. The contractor shall describe the Quality Management System methodology and approaches to be used under the contract in the QCP. The contractor shall provide a Program Management Plan (PMP) and Configuration Management Plan (CMP) for review and approval by the Government.

Deliverables:

The contractor shall deliver Quality Control Plans (QCP) IAW CDRL A003, Program Management Plans IAW CDRL A004, and Configuration Management Plans IAW CDRL A005.

4.0.1.3 Technical Data Packages

The contractor shall develop Technical Data Packages (TDP) that define conceptual design, developmental prototype or limited production design, and production level engineering drawings required for quantity production of the item or system. This includes TDPs for prototypes and any associated test equipment. The contractor shall produce TDPs IAW AD 3.2, consisting of one of three levels: (1) Conceptual Level, (2) Developmental Level, or (3) Production Level as specified in individual TO/DOs.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008.

4.0.1.4 Software Development Plan

The Contractor shall propose a Software Development Plan that is appropriate for the computer software effort to be performed under this contract. The Contractor shall submit the Software Development Plan only at the time of proposal submission and in accordance with CDRL A006.

4.1 CONCEPT DESIGN DEFINITION

4.1.1 Concept Design Analysis and Assessment Studies

The contractor shall perform engineering analysis, conceptual design studies, analysis of alternatives, and assessment studies for development of prototype systems, system of systems, engineered material and electromechanical devices to meet hardware and software system, operational and launch platform requirements defined in individual TO/DOs. The contractor shall perform trade studies, technical investigations and reviews to compare the performance, cost and development time associated with the applicable prototype options. The contractor shall evaluate tradeoffs of various designs as a function of constraints and dependencies including performance metrics, environmental conditions, physical limits, complexity, material composition, structural integrity, hydrodynamic stability, special security and safety features associated with system operation, and compatibility with other proposed and existing systems, components, or devices. The contractor shall assess capability advantages and disadvantages, feasible alternatives, key assumptions, sensitivity to changes in variables and technology risk.

The contractor shall document results of analysis and other findings in Design Analysis Reports, which includes draft computer aided design models and engineering drawings including conceptual designs and system layouts.

Deliverables:

The contractor shall deliver Design Analysis Reports IAW CDRL A009.

4.1.2 Performance Predictions

The contractor shall perform predictive analysis to describe the characteristics of the prototypes using mathematical formulations describing the dependency of system parameters on various external stimuli and operating conditions. The contractor shall develop models and simulations for candidate implementations using computer based modeling tools and numerical methods appropriate for the specific application as defined in the individual TO/DOs. The contractor shall derive metrics that form the basis of contractor comparisons and trade-offs. The contractor shall perform quantitative analysis to evaluate the metrics as a function of the applicable trade-space.

The contractor shall organize the metrics in tabular or graphical form to facilitate side-by-side comparison against various design options. The contractor shall provide a performance report documenting the analysis and other findings.

Deliverables:

The contractor shall deliver Performance Reports IAW CDRL A009.

4.1.3 Analysis of Operation

The contractor shall conduct analyses of current and future operations and missions and make recommendations to develop new system and subsystem solutions. The contractor shall use existing fielded systems as a baseline prior to recommending the development of new systems and subsystems. The contractor shall provide a report documenting the analysis results and recommendations.

Deliverables:

The contractor shall deliver Analysis & Recommendations Reports IAW CDRL A009.

4.1.4 Compatibility Analysis

The contractor shall conduct compatibility studies, draft and update TDPs for proposed prototypes to demonstrate compatibility with systems and their interfaces. The contractor shall evaluate the predicted performance of system interfaces, identify potential problems, and recommend and develop system changes to overcome identified problems.

The contractor shall address compatibility issues associated with current UW/UD systems and subsystems, launch platform systems, ancillary equipment, and laboratory integration equipment.

The contractor shall provide a report documenting the analysis results, draft computer aided design (CAD) models, and TDPs including system layouts.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008 and Compatibility Reports IAW CDRL A009.

4.1.5 Concept Specification Development and Review

The contractor shall provide TDPs that document prototype specifications and take into account operational performance, interfaces, cost, and schedule. The contractor shall conduct design reviews to present conceptual prototypes, review performance against requirements and specifications, identify risks and concerns, and validate design methods and approaches.

In the case of software, the contractor shall provide Algorithms that document the concept’s logical flow.

The contractor shall prepare a Design Review Information Package (DRIP) that presents the results of analysis, simulation, exploratory testing and other engineering activities. The contractor shall provide Concept Development Reports that document the feasibility of proposed specifications and specification modifications, and the potential of those proposed specifications and specification modifications to meet design requirements.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008, Concept Development Reports IAW CDRL A009, Algorithms IAW CDRL A009, and Design Review Information Packages (DRIP) IAW CDRL A00A.

4.2 PROTOTYPE DESIGN, DEVELOPMENT, FABRICATION, INTEGRATION AND TEST

4.2.1 Prototype Design and Development

As further delineated in TO/DOs, and following Government approval of Concept Design, the contractor shall design prototypes using GFI or designs generated from SOW 4.1 tasking. The contractor shall generate and document functional and detailed design of all electrical, mechanical, and software components. During Prototype Design and Development, the contractor shall document its approach to requirements allocation, risk management, configuration management, software integration, hardware integration and test and evaluation.

The contractor shall map high level requirements to specific components of the prototypes. The contractor shall conduct trade-off analysis of various design options and recommend an approach that best satisfies the Government’s requirements. The contractor shall perform engineering studies and prepare draft CAD models and engineering drawings including conceptual designs;

system layouts, detail and assembly drawings; printed circuit board layouts; artwork, schematics, block and wiring diagrams; and associated lists that depict adaptation of proposed prototypes onto applicable platforms, or adaptation of existing systems onto applicable platforms. The contractor shall provide detailed technical assessments, conduct compatibility studies and impact studies of the proposed prototypes. The contractor shall draft a TDP to document the attributes of the Government approved prototype design.

The contractor shall present design documents at technical reviews, for review and approval by the Government, to assess requirements at key milestones and readiness to enter the next technical phase of effort. Specific technical reviews will be identified in each individual order.

The contractor shall prepare and provide test plans and procedures for review and approval by the Government.

Deliverables:

The contractor shall deliver prototypes, Technical Data Packages (TDPs) IAW CDRL A008, Compatibility Reports IAW CDRL A009, Trade-off Analysis Reports IAW CDRL A009, and Test Plans & Procedures IAW CDRL A00B.

4.2.1.1 Prototype Electrical Design

The contractor shall design electrical components including selecting appropriate Commercial- Off-the-Shelf (COTS) parts. Electrical components include custom computer controller subsystems, circuit cards, programmable logic array firmware, other Application Specific Integrated Circuits (ASIC), interfaces, data buses, power supply and distribution, current or voltage protection, analog filters, amplifiers, analog to digital conversion, control electronics, cabling, cable harnesses, connectors and other electrical subsystems. The contractor shall provide TDPs and CAD models of the hardware architecture, electrical component schematics, circuit card layouts, connector and cable pinout diagrams, network routing diagrams, power supply interfaces and other components. The contractor shall perform testing to validate the electrical component design meets requirements.

Deliverables:

The contractor shall deliver prototypes, Technical Data Packages (TDPs) IAW CDRL A008, Electrical DRIPs IAW CDRL A00A, and Test Reports IAW CDRL A00C.

4.2.1.2 Prototype Mechanical Design

The contractor shall design mechanical components, including selecting appropriate Commercial-Off-the-Shelf (COTS) parts. Mechanical components include equipment and electronic enclosures, mounting equipment, special fixtures and jigs, related support equipment and attachment devices, handling equipment, electronic chassis, shock and vibration isolation mechanisms, noise isolation mechanisms, other environmental compatibility devices, acoustic and non-acoustic sensors or transducers, acoustic or nonacoustic windows, and other material designs intended for operational compatibility or reliability enhancement. The contractor shall assess the functionality and compliance of multiple design options using CAD. The contractor shall perform testing to validate the mechanical components meet requirements associated with physical constraints such as volume and weight, interference with other systems and components, safety, and reliability under shock and vibration conditions applicable to the prototypes’ application. The contractor shall provide a TDP documenting the mechanical design.

Deliverables:

The contractor shall deliver prototypes, Technical Data Packages (TDPs) IAW CDRL A008 and Mechanical DRIPs IAW CDRL A00A.

4.2.1.3 Prototype Software Design

The contractor shall design software and computer code to execute required functionality on all computers incorporated into prototypes. The contractor shall document the algorithm functionality, data flow, timing, memory management, and interface control planned for the software implementation. The contractor shall provide Algorithms, Software Requirements Specifications (SRS), Software Design Descriptions (SDD), Interface Requirements Specifications (IRS), and Interface Design Descriptions (IDD) that document the software design.

Deliverables:

The contractor shall deliver prototypes, Algorithms IAW CDRL A009, Software Requirements Specifications (SRS) IAW CDRL A00D, Software Design Descriptions (SDD) IAW CDRL A00E, Interface Requirements Specifications (IRS) IAW CDRL A00F, and Interface Design Descriptions (IDD) IAW CDRL A00G.

4.2.1.4 Prototype Human-Machine Interfaces (HMI)

The contractor shall design and document the interfaces between the system and human operators which include computer generated images (CGI) displayed on a computer screen, other graphical user interfaces (GUI), other visual indicators, and manual controls such as push buttons, touch screens or track balls as defined by AD 3.3. The contractor shall provide Human Engineering Design Approach Documents – Operator.

Deliverables:

The contractor shall deliver prototypes and Human Engineering Design Approach Documents – Operator IAW CDRL A00H.

4.2.1.5 Prototype Software and Firmware Development and Implementation

The contractor shall develop software and firmware that includes sensor acquisition, external interfaces, system control, signal processing, information processing, internal network data routing, performance monitoring, and fault isolation. After Government approval, the contractor shall implement software, firmware and computer code to execute required functionality on all computers incorporated into the prototypes.

The contractor shall develop a Software Test Plan (STP) for review and approval by the Government. The contractor shall test software and firmware modules under isolated conditions before integrating into larger subsystems, IAW the Government approved STP. The contractor shall provide built-in test code such as embedded interface simulation, storage of intermediate results, and software breakpoints to facilitate unit and subsystem testing. The contractor shall include unique numerical identifiers into code files to support version control and configuration management. The contractor shall provide Software Test Descriptions and Software Test Reports for each test.

The contractor shall integrate Government approved software and firmware on subsystems into a combined end-to-end system.

The contractor shall store the software and firmware on electronic media with a unique version identification label. The contractor shall provide Computer Software Products, Software Product End Item Documentation, Software Version Descriptions (SVD), Software User Manuals (SUM), Risk Management Framework (RMF) Documentation and Interface Control Documents

(ICD).

The contractor shall deliver prototypes, Software Test Plans (STP) IAW CDRL A00J, Software Test Descriptions IAW CDRL A00K, Software Test Reports (STR) IAW CDRL A00L, Computer Software Products IAW CDRL A00M, Software Product End Item Documentation IAW CDRL A00N, Software Version Descriptions (SVD) IAW CDRL A00P, Software User Manuals (SUM) IAW CDRL A00Q, Risk Management Framework (RMF) Documentation IAW CDRL A00R, and Interface Control Document (ICD) IAW CDRL A00S.

4.2.2 Prototyping

The contractor shall build, test and deliver prototypes. The contractor shall provide ancillary hardware and special support equipment, software or other configuration items to operate the prototypes in their intended environment. The contractor shall provide Built-in Test (BIT) capabilities and interfaces to support first article unit testing in a stand-alone environment in the completed assembly. Following Government acceptance of the prototypes, the contractor shall provide the prototypes accompanied by a Certificate of Compliance verifying the hardware, software and materials conform to approved drawings, standards and specifications.

Deliverables:

The contractor shall deliver prototypes, and Certificates of Compliance IAW CDRL A00T.

4.2.3 Prototype Integration and Verification Testing

The contractor shall generate, update and maintain plans and procedures for integrating, testing and evaluating the end-to-end prototypes, subsystems, modules, components and devices prior to operational demonstration. The contractor shall develop Design Verification Test (DVT) plans and procedures describing methods for validating limited functionality in a laboratory environment or land-based test facility, for Government approval. The contractor’s test plans shall document any proposed modification to and use of Government facilities or equipment to conduct DVT. The contractor’s test plans shall take into consideration weight constraints, environmental considerations and interfaces, compliance with all security and safety requirements, and test methods that minimize cost to the Government.

The contractor shall conduct DVT. The contractor shall provide all hardware and equipment to support DVT. The contractor shall arrange transportation of material and other external subsystems required for testing to the designated test location. The contractor shall execute DVT integration and validation tests IAW Government approved DVT procedures and document results for each test.

The contractor shall develop and maintain a database of trouble reports categorized by priority.

The contractor shall perform find-fix-repair activities of electronic components, mechanical components and software modules for failures during testing. The contractor shall deliver a DVT report describing the results of all testing, and identify DVT critical performance parameters measured, failures, design changes, and the status of the system. The contractor shall develop acceptance criteria for prototypes completing DVT, for Government approval. After passing Government approved acceptance criteria, the contractor shall deliver assembled prototypes.

The contractor shall deliver Design Verification Test (DVT) Plans and Procedures IAW CDRL A00B and deliver assembled prototypes as specified in individual task and delivery orders.

4.3 TEST AND EVALUATION

4.3.1 Test and Evaluation Planning

The contractor shall develop, update and maintain test plans and procedures to evaluate performance requirements of prototypes in the operational environment. The contractor shall address test objectives, performance metrics, platform requirements, personnel requirements, training, platform geometries, location options, equipment staging, timeline recommendations, actions to prevent mutual interference (PMI), safety requirements, environmental impact constraints, data recording and logging requirements, security restrictions, and information assurance restrictions. The contractor shall include modeling of prototype environment, simulation of test geometries and platform scenarios. The contractor shall assess safety hazards and develop mitigation plans, prepare documentation to support approval from applicable environmental compliance boards, and verify feasibility of data recording methods. The contractor shall submit test plans and procedures for review and approval by the Government.

Deliverables:

The contractor shall deliver Test Plans & Procedures IAW CDRL A00B.

4.3.2 Preparation for Testing

The contractor shall make all preparations needed to test the prototypes by executing test evolutions in the operational environment. After Government approval, the contractor shall perform upgrades, overhauls and tune-ups of test vehicles and equipment deployment apparatus to support testing in the operational environment for the required test duration. Prior to use of the equipment for repeated test trials, the contractor shall make repairs to the prototypes and support equipment in accordance with test objectives.

Prior to testing, the contractor shall prepare and provide materials on proper operation of test equipment, safety procedures and operation of the prototypes to support training of personnel assigned to testing.

The contractor shall package equipment for shipping and arrange for transport of equipment to the test sites and staging areas.

The contractor shall prepare a report detailing the test and support equipment developed, repairs and upgrades performed, and other preparations completed prior to executing a test.

The contractor shall deliver Test Preparation Reports IAW CDRL A00U.

4.3.3 Test Execution

The contractor shall conduct testing of prototypes in an operational environment IAW contractor developed, Government approved test plans to demonstrate, evaluate, verify and validate performance. The contractor shall provide test reports documenting test results. The Contractor shall provide a trip report summarizing the event including accomplishments, issues and problems encountered.

Deliverables:

The contractor shall deliver Test Reports IAW CDRL A00C and Trip Reports IAW CDRL A00V.

4.3.4 Post-Test Analysis

The contractor shall perform analysis and technical investigations of data collected during operational testing. The contractor shall assess system performance relative to test objectives and system technical requirements. The contractor shall generate time-space reconstruction parameters associated with test execution using recorded navigation data from the systems. The contractor shall use mathematical models and computer simulation tools to assess expected performance characteristics of the prototypes given the reconstructed environmental and positional conditions present during test execution. The contractor shall determine the root cause, generate alternative solutions, and produce recommended courses of action for test results that fail to meet expected performance requirements. The contractor shall compare test data with system performance requirements and document findings.

Deliverables:

The contractor shall deliver Post Analysis Reports IAW CDRL A009.

4.4 DEMONSTRATION, EXPERIMENTATION, FIELDING, AND OPERATION

The contractor shall provide engineering services to support Government execution of prototype demonstration, experimentation, fielding and operation. Demonstration and experimentation are performed as bench testing (e.g., laboratory), land based testing, in-water testing on-range, or in-water testing at-sea. The contractor shall use existing systems and subsystems as well as prototype systems and subsystems during the execution of this task. The contractor shall operate equipment, collect and organize data, and document results during execution of the demonstration. The contractor shall provide test reports documenting the outcome of test, demonstration and experimentation events. The contractor shall provide a trip report documenting the event including a summary of accomplishments, as well as issues and problems encountered. The contractor shall support Government integration of systems and the associated enabling systems. The contractor shall travel to the fielding site, operate equipment, collect and organize data, and document results.

The contractor shall provide training materials on the use and operation of the prototype equipment, train personnel and provide a training report documenting the training event, persons trained and completion status.

The contractor shall deliver Test Reports IAW CDRL A00C, Trip Reports IAW CDRL A00V, Training Reports IAW CDRL A00W, and Training Materials IAW CDRL A00X.

4.5 PROTOTYPE LOGISTICS, MAINTENANCE, AND MONITORING ACTIVITIES

4.5.1 Prototype Logistics and Maintenance

The contractor shall provide logistics and maintenance activities for prototypes and support materials to maintain and operate prototypes. The contractor shall provide ancillary hardware and special support equipment, software or other configuration items to operate the prototypes in their intended environment for a specified time period. The contractor shall prepare and provide shipping reports, maintenance support plans, installation procedures and support, spare parts lists, repair analyses and procedures, provisioning data, and Failure Mode, and Effects and Criticality Analysis (FMECA) reports related to logistics and maintenance of prototypes. The contractor shall maintain and produce technical manuals for systems and associated equipment.

The contractor shall maintain and repair all prototype systems, subsystems, and support equipment.

Deliverables:

The contractor shall deliver Shipping Reports IAW CDRL A00Y, Maintenance Support Plans IAW CDRL A00Z, Installation Procedures IAW CDRL A010, Spare Parts Lists IAW CDRL A011, Failure Mode, Effects & Criticality Analyses (FMECA) IAW CDRL A012, and Operational & Maintenance Instructions for R&D Equipment IAW CDRL A013.

4.5.2 Software Maintenance

On an on-going basis, upon receipt of GFI schedules, technical standards, system performance reports, and system trouble reports, provided in individual orders, the contractor shall perform troubleshooting, implement patches and improvements to software and computer code. The contractor shall describe any characteristics or changes to algorithm functionality, data flow, timing, memory management, and interface control. The contractor shall provide updated Technical Data Packages (TDP), Algorithms, Software Requirements Specifications (SRS), Software Design Descriptions (SDD), Interface Requirements Specifications (IRS), Interface Design Descriptions (IDD), and Action Summary Reports that document the changes the contractor made in the iterative maintenance process.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008, Algorithms IAW CDRL A009, Software Requirements Specifications (SRS) IAW CDRL A00D, Software Design Descriptions (SDD) IAW CDRL A00E, Interface Requirements Specifications (IRS) IAW CDRL A00F, Interface Design Descriptions (IDD) IAW CDRL A00G, and Action Summary Report IAW CDRL A009

4.5.3 Model and Simulation Maintenance

On an on-going basis, upon receipt of GFI schedules, technical standards, system performance reports, and system trouble reports, provided in individual orders, the contractor shall perform troubleshooting, and implement modifications and improvements to data models and simulations associated with the weapon and defensive system performance and operating environments. The contractor shall perform troubleshooting, and implement modifications and improvements to the processing and computing techniques used to run simulations. The contractor shall describe any characteristics or changes to algorithm functionality, data flow, timing, processing, memory management, and interface control planned. The contractor shall provide updated Technical Data Packages (TDP), Algorithms, Software Requirements Specifications (SRS), Software Design Descriptions (SDD), and Action Summary Reports that document the changes the contractor made in the iterative maintenance and development process.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008, Algorithms IAW CDRL A009, Software Requirements Specifications (SRS) IAW CDRL A00D, Software Design Descriptions (SDD) IAW CDRL A00E, and Action Summary Reports IAW CDRL A009.

4.5.4 Program Protection Assessment and Monitoring

On an on-going basis, upon receipt of GFI schedules, program protection requirements, and system technical data provided in individual orders, the contractor shall monitor and assess program protection issues related to known, emerging, and theoretical threats, attack vectors, system vulnerabilities, and DoD Risk Management Framework (RMF) requirements. The contractor shall provide updated Technical Data Packages (TDP) and Action Summary Reports that document the contractor’s assessment and recommendations.

Deliverables:

The contractor shall deliver Technical Data Packages (TDPs) IAW CDRL A008, and Action Summary Reports IAW CDRL A009.

4.6 TRANSITION TO PRODUCTION

4.6.1 Production Level Documentation

The contractor shall develop a production level TDP as described in Applicable Document 3.2.

The contractor shall include descriptions of candidate production system architecture, identification of parts, mechanical drawings, electrical schematics, software functional flow, computer network architecture, and operator-machine interfaces. The contractor shall revise existing TDPs to address obsolescence, environmental qualification testing, reliability, safety, and information assurance qualifications.

The contractor shall deliver Production TDPs IAW CDRL A008.

4.6.2 Low Rate Initial Production

The contractor shall manufacture Low Rate Initial Production (LRIP) units in support of verification of program requirements. Specific quantities of LRIP units will be identified in individual orders based on program requirements.

Deliverables:

The contractor shall deliver LRIP units.

4.6.3 Full Rate Production

The contractor shall manufacture Full Rate Production (FRP) units. Specific quantities of FRP units will be identified in individual orders based on program requirements.

The contractor shall deliver FRP units.

5.0 Progress Reports

The Contractor shall prepare a Contractor’s Status Report that indicates the progress of work, status of the program(s), and existing or potential problem areas for all assigned tasks. The Contractor shall submit the Contract Status Report for the same timeframe as each invoice submitted in the Wide Area Workflow (WAWF) Module of the Procurement Integrated Enterprise Environment (PIEE). CDRL A014.

The Contractor shall require each Contractor employee performing work at any NUWC Division Newport site, who have a Common Access Card (CAC) and an NMCI Account complete all required trainings. The required training and required training schedule is available at the following website:

https://wiki.navsea.navy.mil/pages/viewpage.action?spaceKey=NCOW&title=NUWCDIVNPT+ Workforce+Development+Program. See the pdf for Mandatory Training Instruction – Contractors Only.

The Contractor shall prepare and submit Training Completion Status Reports affirming all required training has been completed. The Training Completion Status Reports shall include the contract/order number, contactor employee name, specific training name, training course ID #, and completion date for all contractor employees asserting training completion. See the pdf for Mandatory Training Instruction – Contractors Only. Contact the COR identified in Section G if additional access instructions are needed. If specific training questions arise, contact the POC listed for the training in the pdf. CDRL AXXX – DI-MSC-80508B.

6.0 Government Furnished Information

Government Furnished Information (GFI) will be addressed in individual orders.

7.0 Quality Surveillance and Performance Standards

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables. Contractor performance will be evaluated in the areas of technical quality, cost control, schedule/timeliness, management, utilization of small business, and regulatory compliance as follows:

Technical Quality: The government will evaluate technical quality using the criteria defined in the Performance Requirements Summary Table (PRST), Attachment 2;

Cost Control: The government will evaluate the contractor’s effectiveness in forecasting, managing, and controlling actual costs in comparison to negotiated costs;

Schedule/Timeliness: The government will evaluate the contractor’s ability to meet negotiated milestones and delivery schedules;

Management: The government will evaluate the contractor’s ability to integrate and coordinate all activities needed to execute the contract/task order;

Utilization of Small Business: The government will evaluate the contractor’s compliance with the Small Business Subcontracting Plan and any small business subcontracting goals contained in the contract/task order;

Regulatory Compliance: The government will evaluate the contractor’s compliance with the terms and conditions of the contract/task order relating to applicable regulations and codes.

8.0 Exception From Information and Communication Technology Accessibility Requirements

The Government has determined that this procurement is an exception to the Information and Communication Technology (ICT) Accessibility Standards (36 C.F.R. Part 1194, Appendix A) because this is a National Security Systems. Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with the ICT Accessibility Standards (36 C.F.R. Part 1194, Appendix A).

9.0 Compliance With Information and Communication Technology Accessibility

Requirements

The Government has determined that this procurement is compliant with the Information and Communication Technology (ICT) Accessibility Standards (36 C.F.R. § 1194.3 - Chapter 2 E202 General Exceptions of Section 50 Refresh). The 508 compliant ID # and applicable EIT Accessibility Standards