ATT_2_DRAFT_VIPER-SOW.pdf

ATTACHMENT 2

SECTION C – DESCRIPTION/SPECIFICATION/WORK STATEMENT

STATEMENT OF WORK

C.1 BACKGROUND

C.1.1 The Vessel Incapacitating Power Effect Radiation (VIPER) Program is a research and development based Operational Utility Assessment (OUA), which will provide a non-lethal, potentially reversible vessel stopping capability. The contractual performance requirements stated within, guide the development of the initial VIPER System. The VIPER System, through both requirement verification and operational employment, will provide a basis for future employment or transition to a Program of Record (POR).

C.2 SCOPE

The scope of the work to be performed by the Contractor during the development of VIPER System includes all of the following: Systems Engineering; Design and Fabrication; System Integration; Testing and Evaluation; as well as Production of Technical, Programmatic, Training, and Safety Data. As described in this SOW a down select will be made upon completion of PDR and the Government will move forward into the Critical Design phase with the selected contractor. This SOW will include a base contract beginning with design work leading to various design reviews and culminating with system acceptance at the end of a Testing and Evaluation period.

C.3 APPLICABLE DOCUMENTS

Applicable standards, practices, and procedures include the following:

C.3.1 International Standards:

ISO/IEC/IEEE 12207 Systems and Software Engineering – Software Life Cycle Processes, dated 15

November 2017 IEC 60529 Degrees of Protection Provided by Enclosures (IP Code), dated 29 August 2013 ASTM D3951-15 Standard Practice for Commercial Packaging, dated 1 December 2015 ASTM F1166-07 Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities, dated October 2013 ASTM-G-85 Annex A3 Standard Practice for Salt Spray (Fog) Testing, dated August 2018 ASTM-D-2863-17a Standard Test Method for Measuring the Minimum Oxygen Concentration to

Support Candle-Like Combustion of Plastics (Oxygen Index), dated June 2018 AOP-52 North Atlantic Treaty Organization (NATO) Allied Ordnance Publication

(AOP) 52, Guidance on Software Safety Design and Assessment of Munition- Related Computing Systems, dated 29 November 2016

C.3.3 Federal Standards and Specifications:

J-STD-001 Adoption Notice: Requirements for Soldered Electrical and Electronic

Assemblies, dated 19 July 2001

C.3.4 Department of Defense Standards and Specifications:

MIL-STD-464C Electromagnetic Environmental Effects Requirements for Systems, dated 1

December 2010 MIL-STD-882E Department of Defense Standard Practice: System Safety, dated 11 May 2012 MIL-STD-461G Department of Defense Interface Standard: Requirements for the Control of

Electromagnet Interference Characteristics of Subsystems and Equipment, dated 11 December 2015

MIL-STD-1310H Department of Defense Standard: Practice Shipboard Bonding, Grounding, and other Techniques for Electromagnetic Compatibility, Electromagnetic Pulse (EMP) Mitigation, and Safety, dated 12 August 2018

MIL-STD-1399/300A Military Standard: Interface Standard for Shipboard Systems (Section 300B) Electric Power, Alternating Current, dated 24 April 2008.

MIL-STD-1683B Department of Defense Design Criteria Connectors and Jacketed Cable, Electric, Selection Standard for Shipboard Use, dated 31 March 1989

MIL-STD-1353C Department of Defense Standard Practice: Electrical Connectors, Plug-In Sockets and Associated Hardware, dated 18 February 2014

MIL-DTL-24640C Detail Specification: Cables, Lightweight, Low Smoke, Electric, for Shipboard Use, dated 08 November 2011

MIL-DTL-24643 Detail Specification: Cables, Electric, Low Smoke Halogen-free, for Shipboard Use, dated 13 December 2011

MIL-STD-810G Department of Defense Test Method Standard: Environmental Engineering Considerations and Laboratory Tests, dated 14 April 2014

MIL-STD-167 Department of Defense Test Method Standard: Mechanical Vibrations of Shipboard Equipment, dated 2 November 2005

MIL-STD-901D Department of Defense Test Method Standard: Requirements for High Impact Shipboard Machinery, Equipment, and Systems, dated 29 July 2009

MIL-STD-1472G Department of Defense Design Criteria Standard Human Engineering, dated 11 January 2012

MIL-STD-2036A General Requirements for Electronic Equipment Specifications, dated 20 October 2000

MIL-STD-31000 Department of Defense Standard Practice for Technical Data Packages, dated 26 February 2013

MIL-STD-2073-IE (Change 2) Department of Defense Standard Practice for Military Packaging, dated 09 July

MIL-STD-129R Department of Defense Standard Practice for Military Marking for Shipment and Storage, dated 18 February 2014

MIL-STD-1686C Department of Defense Standard Practice: Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (excluding electrically initiated explosive devices), dated 25 October

MIL-STD-1474E Department of Defense Design Criteria Standard: Noise Limits, dated 15 April

MIL-STD-881C Department of Defense Standard Practice: Work Breakdown Structures for Defense Material Items, dated 03 October 2011

MIL-PRF-32216A Performance Specification: Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, dated 12 August 2011

No Designator Program Executive Office for Integrated Weapons Systems (PEO IWS)/Naval Sea Systems Command Research & System Engineering Warfare Systems (SEA 05H) Technical Review Manual (TRM) Version 2.0, dated 18 December 2009

C.3.5 Department of Defense Handbooks:

MIL-HDBK-310 Global Climatic Data for Developing Military Product, dated 23 June 1997 MIL-HDBK-217F Reliability Prediction of Electronic Equipment, dated 28 February 1995

(NOTICE-2)

MIL-HDBK-338B Electronic Reliability Design Handbook, dated 11 May 2012

(NOTICE-2)

MIL-HDBK-454B General Guidelines for Electronic Equipment, dated 15 April 2007 No Designator Joint Software Systems Safety Engineering Handbook, dated 27 August 2010

C.3.6 Other Government Documents, Drawings, and Publications:

The following other Government documents, drawings, and publications of the exact revision level shown form a part of this document to the extent specified herein:

NAVSEA OP 3565 /NAVAIR Electromagnetic Radiation Hazards (Hazards to Personnel, Fuel and Other

16-1-529 Volume 1 Flammable Material), dated 1 July 2008 NAVSEA OP 565 /NAVAIR Electromagnetic Radiation Hazards (Hazards to Ordnance), dated 01 July 2008 16-1-529 Volume 2 DoDI 5000.67 Prevention and Mitigation of Corrosion on DoD Military Equipment and

Infrastructure, dated 21 November 2017 DoDI 6055.11 Protecting Personnel from Electromagnetic Fields, dated 19 August 2009 DoDI 6055.12 Hearing Conservation Program (HCP), dated 25 October 2017 DoDI 8320.04 Implementing the Sharing of Data, Information, and Information Technology

Services for the DoD, dated 03 September 2015 DoDI 8500.01 Cybersecurity, dated 14 March 2014 DoDI 8510.01 Risk Management Framework for DoD Information Technology SECNAV 4440.34 DoD Item-Unique Identification Policy and Implementation Policy, dated 22

December 2009 OPNAVINST 5100.27B Navy LASER Hazards Control Program, dated 02 May 2008

C.3.7 Non-Government Publications:

The following documents of the exact revision listed below form a part of this document to the extent specified herein:

IEEE STD C95.1-2005 IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz, dated 19 April 2006

JESD625-B JEDEC/EIA Standard: Requirements for Handling Electrostatic-Discharge- Sensitive (ESDS) Devices, dated December 2011

ANSI Z136.1-2014 American National Standard for Safe Use of Lasers, dated 2013 ANSI/ASHRAE 34-2016 Safety Standard for Refrigeration Systems and Designation and Classification of

Refrigerants MOA between DoD and DHS DoD and USCG Cooperation on Cybersecurity and Cyberspace Operations, dated January 2017 COMDTINST M5500.13 U.S. Coast Guard Security and Information Assurance (SIA) Manual (Series)

C.3.8 Order of Precedence

Unless otherwise noted, in the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained.

C.4 REQUIREMENTS

C.4.1 Project Management Activities:

C.4.1.1 The Contractor shall designate one individual with whom the Government will interface for management and reporting. Contact information shall be provided via E-mail to the Contracting Officer’s Representative (COR) within five (5) calendar days of this award date.

C.4.1.2 The Contractor shall designate appropriate individual(s) as technical representatives with whom the Government Technical Lead and Systems Engineering Lead will interface. Contact information shall be provided via E-mail to the Government Leads within five (5) calendar days of this award date.

C.4.1.3 The Contractor shall maintain and report on an integrated master schedule (IMS) to identify and assess progress on all tasks. (CDRL A002)

C.4.1.4 The Contractor shall track and monitor staffing, financials and technical progress. The Contractor shall manage and communicate risk to the Government. (CDRL A017)

C.4.1.5 The Contractor shall coordinate with the Government to plan and execute a Contract Kick-Off meeting at the Government’s discretion. The Government may elect to conduct this meeting remotely and entirely over the telephone. (CDRL A018)

C.4.1.6 The Contractor shall provide, at a minimum, one (1) In-Process Reviews (IPRs) between Preliminary Design, TIM #1, and TIM #1. (CDRL A021)

C.4.1.7 The Contractor shall provide, at a minimum, one (1) In-Process Reviews (IPRs) between TIM #1 and TIM

#2. (CDRL A021)

C.4.2 Preliminary Design Phase:

C.4.2.1 The Contractor shall create a preliminary design for the VIPER System in accordance with (IAW) this SOW and the VIPER System Performance Specification (PSPEC). The Preliminary Design phase is intended to allow the Contractor to research and compile information and data supporting the preliminary design of the system.

C.4.2.2 The Contractor shall conduct a multi-disciplined technical review at both system level and component levels to ensure that the allocated baseline is established. The component-level preliminary designs shall be successfully completed for each major component before conducting the system-level preliminary design. The preliminary design shall complete the process of defining the technical requirements for each component, which shall be documented in the item performance specification of each component. (CDRL A004)

C.4.2.3 The Contractor’s design shall meet all of the requirements listed in this SOW and in the PSPEC.

C.4.2.4 At Government discretion, a VIPER System design that does not or may not meet requirements defined under Environmental Considerations of the PSPEC may be accepted under this contract. These requirements are related to system ruggedization and survivability. The Government must provide a detailed statement to this effect with its design approval to the Contractor as discussed in Section C.4.5.

C.4.2.5 The Contractor shall develop drawings of the VIPER System to thoroughly describe the design to the Government. These drawings shall clearly depict and identify the physical layout of all sub-components, penetrations for cables, exterior dimensions and footprint, all points to where the system is to be connected to the platforms systems, and all points where the human operator is expected to physically interact with the system. The Contractor shall also identify temporary alterations that will need to be performed in order to integrate the Preliminary Design on the platform. The Contractor shall include at least one 3-dimensional (3-D) view to clearly show form factor and system layout. (CDRL A003)

C.4.2.6 This phase would culminate with a Preliminary Design Review (PDR).

C.4.3 Preliminary Design Review - Technical Interchange Meeting (TIM) #1:

C.4.3.1 The Contractor shall conduct a PDR to confirm that the preliminary design logically follows the Contractor’s conceptual findings with their proposal and to meet VIPER System requirements. It will include emphasize software and hardware system and subsystem specifications and results in approval to proceed to CDR.

C.4.3.2 TIM #1 shall be held in person at the Contractor’s facility after contract award. The Government will provide a teleconference line for remote attendees.

C.4.3.3 At TIM #1, the Contractor shall present the proposed design for the VIPER System IAW this SOW.

(CDRL A021) The designs of the VIPER System presented to the Government shall meet the requirements of Section C.4.2 of this SOW. At TIM#1, the Contractor shall provide the following:

Drawings as described in this SOW Section C.4.2.5. (CDRL A003) A matrix of the requirements of Section C.4.2 and the VIPER System PSPEC including a description of how the Contractor’s design meets the requirements.

Review of the scope of development work, manufacturing processes, and manufacturing readiness to deliver the VIPER System.

Top-level discussion of the ruggedization and environmental survivability aspects of the proposed design with respect to the Environmental Considerations of the PSPEC.

Review of Risk Assessment including Risk Mitigation Strategies.

Initial schedule including all tasks in this SOW and highlighting major milestones/deliveries. (CDRL

A002)

C.4.3.4 The Contractor shall provide a technical report detailing the discussions held and to supplement the information presented at TIM #1. (CDRL A003, CDRL A004)

C.4.4 Critical Design Phase:

C.4.4.1 The Contractor shall create a final design for the VIPER System IAW this SOW and the VIPER System Performance Specification (PSPEC). The final design is intended to allow the Contractor to research and compile information and data supporting the final design of the system. The component-level critical design should be successfully completed for each major component before conducting the system-level critical design. It completes the process of defining the technical requirements for each component, which are documented in the item performance specification of each component. A successful completion of the critical design provides a sound technical basis for proceeding into fabrication, integration, and developmental test and evaluation. At completion of the critical design, the initial product baseline is taken under contractor configuration control until the physical configuration audit (PCA).

C.4.4.2 The Contractor’s design shall meet all of the requirements listed in this SOW and in the PSPEC.

C.4.4.4 The Contractor shall develop final drawings of the VIPER System in order to thoroughly describe the design to the Government. These drawings shall clearly depict and identify the physical layout of all sub-components, penetrations for cables, exterior dimensions and footprint, all points to where the system is to be connected to the platforms systems, and all points where the human operator is expected to physically interact with the system. The Contractor shall also identify alterations that will need to be performed in order to integrate the Critical Design on the platform. The Contractor shall include 3-dimensional (3-D) views to clearly show form factor and full system layout. (CDRL A003)

C.4.4.4.1 The Contractor shall conduct a platform integration study to identify appropriate dimensions and overall configuration of the VIPER System being proposed. (CDRL A019)

C.4.4.5 This phase would culminate with a Critical Design Review (CDR).

C.4.4.6 The Contractor shall conduct a CDR to confirm that the final design logically follows the Contractors conceptual findings with their proposal, the outcome of the PDR and to meet VIPER System requirements. The CDR will be multi-disciplined technical review, conducted at both system-level and component-level to ensure that the initial product baseline is established. (CDRL A006)

C.4.5 Critical Design Review - Technical Interchange Meeting (TIM) #2:

C.4.5.1 TIM #2 shall be held at the Contractor’s facility after TIM #1.

C.4.5.2 At TIM#2, the Contractor shall request Government approval of their design for the VIPER System to be delivered under this contract. The Government will approve the Contractor’s design prior to production of subcomponents to be used in software and hardware integration and Government acceptance testing.

C.4.5.3 The Contractor shall provide a summary slide presentation and a technical report. (CDRL A004). The presentation shall facilitate the TIM#2 meeting (CDRL A021). The Contractor shall provide the following as part of the TIM#2 technical report:

Updates to all items presented at TIM#1 (see Section C.4.3 (CDRL A003).

Detailed discussion of safety, ruggedization, and environmental survivability aspects of the design with respect to the Environmental Considerations of the PSPEC. Information delivered by the Contractor shall include steps and design considerations to ruggedize the VIPER System, anticipated tradeoffs/limitations/constraints for meeting all related requirements in the PSPEC, related testing requirements, and a summary of existing data with sources.

Repair and maintenance considerations as related to the Contractor’s design. This shall include discussion of expected failures, Contractor recommendations for sparing strategies, and anticipated obsolesce issues.

The Contractor shall identify which components are considered replaceable. This shall include considerations related to Section C.4.9 of this SOW.

Top five (5) technical risks including integration with the Government’s platform and Contractor-proposed risk handling strategies (e.g. risk acceptance, risk mitigation steps, etc.).

Mature draft versions (electronic copies) of documentation included in Section C.4.7 of this SOW. The specific documents required are the Contractor’s Configuration Management Plan (CMP) (CDRL A009), Quality Assurance Program Plan (QAPP) (CDRL A011), Hardware Requirements Specification (HRS) (CDRL A008), Interface Requirements Specification (IRS) (CDRL A007), Hardware Design Description (HDD) (CDRL A013), and the Contractor Work Breakdown Structure (CWBS) IAW MIL-STD-881C.

(CDRL A001)

C.4.6 Build of VIPER System:

C.4.6.1 This task shall be executed by the Contractor only after receipt of written approval from the COR at TIM #2 (SOW Section C.4.5).

C.4.6.2 The Contractor shall build and deliver one (1) VIPER System to be used in Government testing within twelve (12) months of receipt of approval for production. This system shall be built IAW the design approved by the Government.

C.4.6.3 The Contractor shall test all hardware prior to delivery to the Government.

C.4.6.3.1 Contractor testing shall be governed by and IAW the Contractor’s Quality Assurance Plan (QASP). It shall include all basic function checks possible without physically integrating onto the platform. Delivered VIPER System sub-components shall be functional and conform by verification to the design approved by the Government.

C.4.6.3.2 The Contractor shall provide detailed test reporting to the Government to ensure the delivered hardware conforms to the requirements of this SOW. The report shall include detailed results including a summary of the production acceptance test (PAT) procedure(s) used. (CDRL A005)

C.4.6.3 The Contractor shall label and mark the VIPER System IAW the PSPEC prior to delivery to the Government.

C.4.6.4 The Contractor shall build and deliver a testing mount that shall be capable of incorporating the VIPER System for use during developmental testing on a surrogate platform.

C.4.7 Factory Acceptance Testing (FAT):

C.4.7.1 The Contractor shall conduct a Test Readiness Review (TRR) prior to execution of Factory Acceptance Testing (FAT). The FAT shall consist of multiple test periods. Prior to each test period, the Contractor shall conduct a Test Event Review (TER). The TRR is conducted to ensure that the component/subsystem/system under review is mature enough to proceed into the major test cycle (i.e., FAT). The TER is conducted to focus on the subset of tests identified for an individual test period. At the TRR and TERs, the Contractor shall review planned test objectives, methods, procedures and statistical analyses and examine lower-level test results, test plans, test objectives, test methods and procedures to verify the traceability of planned tests to program requirements and ensure that required test resources have been properly identified and coordinated.

C.4.7.2 The Contractor shall coordinate all reviews (scheduling, location, security requirements, agenda, and content). The content of the TRR is defined in the Program Executive Office for Integrated Weapons Systems (PEO IWS)/Naval Sea Systems Command Research & System Engineering Warfare Systems (SEA 05H) Technical Review Manual (TRM) Version 2.0 and shall be tailored and agreed to by the Government. The Contractor shall host the TRR and TERs. (CDRL A021)

C.4.7.3 The Contractor shall conduct FAT on each VIPER System Subcomponent IAW Contractor-developed, Government-approved FAT Plan and FAT Procedures (CDRL A015). The Contractor shall document the results of the FAT in a FAT Report (CDRL A005). This test report shall include the Contractor’s assessment of system performance, document the completion of each test event, summarize the results of each test event, test data, and include any analysis, modeling and simulation (M&S), tests, or data used to verify each requirement.

C.4.7.4 The Contractor shall coordinate test events with Government participation. The Contractor shall conduct meetings to review test results with the Government.

C.4.7.5 The Contractor shall conduct FAT on the Full System along with the Government. As part of the FAT, the Contractor shall verify the accuracy and completeness of the Operations & Maintenance Manual (CDRL A012) referenced in Section C.4.9.2.

C.4.8 Configuration Management (CM):

C.4.8.1 The Contractor shall develop, maintain, and follow a Configuration Management Plan (CMP) describing the Contractor’s processes for controlling the configuration of hardware including hardware baselines and processes for modifying these baselines. The Contractor shall provide the Government with a copy of their CMP. (CDRL A009)

C.4.8.1.1 The Contractor shall summarize any modifications or recommended modifications to the Contractor’s CMP, QASP, any other delivered Contractor plan, and any delivered hardware baseline document in a Notice of Revision (NOR) provided to the Government. For hardware baseline documents, Government approved changes are required before they are made. (CDRL A010)

C.4.8.2 The Contractor shall control the configuration of the VIPER System IAW the Contractor CMP.

C.4.8.2.1 The Contractor shall participate in a joint Government/Contractor effort to designate configuration items (CI) to be managed by the Government and those to be managed by the Contractor. This shall ensure that the Contractor CMP is coordinated with the VIPER System Program CMP and the relevant sections of the VIPER System CMP will be provided as GFI. The Contractor shall recommend components and subcomponents to be designated as Hardware Configuration Items (HWCI) and Hardware Components (HWC) with descriptions and rationale for the selection of each. HWCs are sub-components of an HWCI.

C.4.8.3 The Contractor shall generate and maintain baseline documentation for the VIPER System and all related hardware items IAW the Contractor’s CMP.

C.4.8.3.1 The Contractor shall provide a Product Baseline Index (PBLI) showing the current listing of documentation included in the baseline for all CIs managed by the Contractor. The PBLI shall include the documents listed in C.4.8.3.2 through C.4.8.3. (CDRL A006)

C.4.8.3.2 The Contractor shall list in the PBLI and provide a Hardware Requirements Specification (HRS). The HRS shall list the requirements traceable to HWCI and HWC. The HRS shall include requirements to the derived technical level with traceability to the PSPEC and recommended verification method (test, demonstration, inspection, or analysis). (CDRL A008)

C.4.8.3.3 The Contractor shall list in the PBLI a Hardware Design Description (HDD). The HDD shall describe the design and architecture of the VIPER System including all HWCIs, HWCs, and interfaces. Included in the HDD shall be a list of HWCI and HWC delivered in a top-down breakout format. (CDRL A013)

C.4.8.3.4 The Contractor shall list in the PBLI and provide an Interface Requirements Specification (IRS). The IRS shall list the requirements for critical interfaces traceable to HWCIs. The IRS shall include requirements to the derived technical level with traceability to the PSPEC and recommended verification method (test, demonstration, inspection, or analysis). (CDRL A007)

C.4.8.3.5 The Contractor shall list in the PBLI and provide a Hardware Operations & Maintenance (O&M) Manual.

See Section C.4.9.2 of this SOW for details regarding the content of the O&M Manual. (CDRL A012)

C.4.8.3.6 HWCIs and HWCs shall be included in the PBLI. The Contractor shall provide the PBLI to the Government. (CDRL A006)

C.4.8.3.7 The Contractor shall list in the PBLI and provide a drawing package including up-to-date drawings from Section C4.4.4 of this SOW. The drawing package shall include dimensions, connections, part numbers of HWCIs and HWCs, descriptions, and color pictures of the VIPER System. (CDRL A003)

C.4.8.4 The Contractor shall establish a configuration status accounting (CSA) database that records and maintains the hardware configuration baseline documents. Digital copies of all current and historical versions of baseline documents generated or maintained by the Contractor shall be made available to the Government upon request.

(CDRL A016)

C.4.8.5 The CSA database shall also record the serial numbers and license numbers for all non-consumable items delivered to the Government.

C.4.8.5.1 For any HWCI identified for Government control, the Contractor shall provide form, fit, function, and interface documentation necessary for CSA.

C.4.8.6 Using the CSA database, the Contractor shall maintain information that allows traceability of vendor assigned serial numbers for all HWCIs and HWCs to the relevant Item Unique Identification (IUID). As an example, the vendor serial numbers of sensors integrated into the VIPER System should be traceable to the IUID of the VIPER System end product. The Contractor’s CSA database shall include the following hardware related data elements at a minimum:

• Date of entry

• USN serial number or IUID (as applicable)

• Vendor part number/CAGE code

• Vendor serial or license number

• Serialized part nomenclature

• Date installed (for components)

• Relevant testing results or references (as applicable)

• HAZMAT designation or considerations (as applicable)

C.4.8.7 The Contractor shall provide a complete electronic accounting to the Government for the delivered VIPER System IAW the Contractor’s CSA database. (CDRL A016)

C.4.9 Life Cycle Sustainment and Support (LCSS):

C.4.9.1 The Contractor shall perform, document, and provide to the Government the outcome of a Systems Hazard Analysis (SHA) to identify hazards and mitigation measures in the integrated system design including subsystems and human interfaces IAW Task 205 of MIL-STD-882E. Specifically considered shall be human health hazards as determined through a Health Hazard Analysis (HHA) focused on physical and ergonomic hazards IAW Task 207 of

MIL-STD-882E. (CDRL A014)

C.4.9.2 The Contractor shall provide an Operator’s and Maintenance Manual (O&M Manual) for the VIPER System using MIL-PRF-32216A as guidance. (CDRL A012)

C.4.9.2.1 The Contractor shall ensure all validated procedures work as written to accomplish the task described.

C.4.9.2.2 The Contractor shall correct any non-workable procedures provided within 2 weeks.

C.4.9.3 The Contractor shall provide a Provisioning Parts List (PPL) to the Government. The PPL must include all the parts that can be removed and replaced at the Operational- Level (O-Level) and the In-Service Engineering Agent (ISEA) level. Examples (for illustrative purposes only) are a battery at the O-Level and the sensors or the primary computing platform in VIPER System at the ISEA level. (CDRL A022)

C.4.10 Surrogate Platform T&E FSR Support:

The purpose of the test to be conducted on a surrogate platform is to verify system performance onboard a surrogate vessel in a representative operational environment prior to full system integration on the OUA Platform.

C.4.10.1 The contractor shall provide a VIPER System FSR for the duration of the test onboard the surrogate platform. This test is estimated to last up to eight (8) weeks.

C.4.10.2 The FSR shall have documented training and experience with the VIPER System and shall be considered a Subject Matter Expert (SME). The FSR shall also support the installation of the VIPER System onboard the surrogate platform as well as initial setup, calibration, checkout, troubleshooting, repair, and operation of the system.

C.4.10.3 The contractor shall participate in all planning meetings and provide input as required by the Government for documentation necessary for the test.

C.4.11 OUA Platform Integration:

C.4.11.1 The Contractor shall work with the Government during the Critical Design & Build phases to understand and refine the interfaces between the VIPER System and the platform. For a standalone system, the interfaces will be limited to ship’s power, mechanical installation and seawater cooling.

C.4.11.2 The Contractor shall work with the Government to develop a Platform Integration Plan and Procedures (CDRL A019) for the VIPER System. The Platform Integration Plan (CDRL A019) shall define the requirements and responsibilities pertaining to system installation, environmental factors, system checkout, installation material requirements, and recommended installation approach.

C.4.11.3 The installation design shall allow for accessibility and maintainability of Line Replaceable Units (LRUs) as much as practical by ensuring that there is enough room for personnel and tooling and connections are easily accessible. The system design including electrical cables, plumbing, pressure vessels, batteries, and chemicals shall adhere to all necessary ship safety requirements.

C.4.11.4 The Contractor shall maintain engineering estimates for specific items directly impacted by the VIPER System design that are included in ship’s budgets. These items include weights of plumbing, power cables, additional ship structure necessary for installation, and spares required to meet performance requirements. The Contractor shall include these engineering estimates in the Platform Integration Plan. (CDRL A019)

C.4.11.5 The Contractor shall work with the Government team throughout the period of this contract to ensure integration onto the OUA Platform. Dates and location of all joint Government-Contractor activities will be coordinated with the Contractor and must be mutually agreed upon.

C.4.11.6 The Government estimates that this support includes monthly teleconferences, and participation and attendance in two trips to the OUA Platform’s location.

C.4.11.7 The Contractor shall install the VIPER System IAW the Platform Integration Plan.

C.4.11.8 This support culminates with a one (1) year Operational Utility Assessment.

C.5 DELIVERY

C.5.1 The anticipated timeline from award to PDR is nine (9) months after award.

C.5.2 The anticipated timeline from PDR to Delivery of system is twenty-seven (27) months after PDR.

C.5.3 The anticipated period of performance from Delivery of system through the install and integration requirements is one (1) year.

C.6 TRAVEL

The Contractor shall be required to travel in performance of this contract. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be coordinated with the COR. All travel shall be conducted in accordance with FAR 31.205-46 Travel Costs and shall be pre-approved by the COR. The Contractor shall provide trip reports. (CDRL A020)

C.7 SECURITY

C.7.1 The Program Manager for this effort must possess a SECRET Security Clearance at time of award. The Contractor will have access to information and compartments with a SECRET classification. All deliverables associated with this contract are unclassified unless otherwise specified. Access to classified spaces and material and generation of classified material shall be in accordance with the attached DD Form 254. The Department of Defense Contract Security Classification Specification (DD Form 254) provides the security classification requirements for this contract. The Contractor shall obtain facility and personnel security clearances as required by the Department of Defense Industrial Security Program prior to starting to work on tasks requiring clearances.

Access to classified spaces and material and generation of classified material shall be in accordance with the NISPOM and the NSWCDD Command Security Manual. All data generated under this contract shall be classified in accordance with the guidance in the NISPOM and the NSWCDD Command Security Manual.

C.7.2 Unless otherwise stated all documents shall be marked at the Distribution C level.

C.7.3 For Official Use Only (FOUO) and Personally Identifiable Information (PII) generated and/or provided under this contract shall be safeguarded and marked as specified in DoD 5400.7-R Chapters 3 and 4. The contractor will have access to classified information only at another contractor’s facility or a Government activity.

C.7.4 Facility Clearance: The Contractor shall possess and maintain a SECRET facility clearance as verified within the Industrial Security Facility Database.

C.7.5 Physical Security: No safeguarding of classified material is authorized at the contractor facility.

Safeguarding will only be required at the actual performance site listed in Block 13 on the DD254. Actual performance site’s security regulations and guidelines will apply.

C.7.6 Electronic Spillages (ES) are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system (IS), media or hardcopy document possessing insufficient security controls to protect the data at the required classification level, thus posing a risk to national security (e.g., sensitive compartmented information (SCI) onto collateral, Secret onto Unclassified, etc.). The Contractor’s performance as it relates to ES will be evaluated by the Government. ES reflects on the overall security posture of NSWCDD and a lack of attention to detail with regard to the handling of classified information of IS security discipline and will be reflected in the Contractor's performance rating. In the event that a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.

C.7.7 NSWCDD Security will continue to be responsible for the corrective action plan in accordance with the security guidance reflected on the DOD Contract Security Classification Specification - DD254. NSWCDD Security will identify the Contractor facility and contract number associated with all electronic spillages during the investigation that involve Contractor support. NSWCDD Security will notify the Contracts Division with the Contractor facility name, contract number, incident specifics and associated costs for clean-up. The Contracting Officer will be responsible to work with the Contractor Facility to capture the costs incurred during the spillage clean up. The Contractor is also responsible for taking Information Security Awareness training annually, via their Facility Security Officer (FSO), as part of the mandatory training requirements. If a spillage occurs, additional training will be required to prevent recurrence.

C.7.8 Portable Electronic Devices (PEDs):

C.7.8.1 Non-government and/or personally owned portable electronic devices (PEDs) are prohibited in all NSWCDD buildings with the exception of personally owned cell phones, which are authorized for use in spaces up to and including Controlled Access Areas. The Contractor shall ensure the onsite personnel remain compliant with this PED policy. NSWCDD instruction defines PEDs as the following: any electronic device designed to be easily transported, with the capability to store, record, receive or transmit text, images, video, or audio data in any format via any transmission medium. PED’s include pagers, laptops, radios, compact discs and cassette players/recorders.

In addition, this includes removable storage media such as flash memory, memory sticks, multimedia cards and secure digital cards, micro-drive modules, ZIP drives, ZIP disks, CD-RWs, DVD-RWs, MP3 players, iPads, digital picture frames, electronic book readers, Kindles, Nooks, cameras, external hard dish drives, and floppy diskettes.

C.7.8.2 Personal Wearable Fitness Devices (PWFDs) marketed primarily as fitness or sleep devices are allowed in all Navy spaces where collateral non-Sensitive Compartmented Information (SCI), classified information is processed, stored, or discussed up to and including secret. User must ensure PWFD is compliant with all requirements in NAVADMIN 216/15, Cyber Hygiene Authorization to use Personal Wearable Fitness Devices (e.g., Fitbit, Jawbone UP, etc.) in Navy Spaces, dated 14 September 2015 and register PWFD in the NSWCDD Fitness Device Tracker.

C.7.8.3 PED’s belonging to an external organization shall not be connected to NSWCDD networks or infrastructure without prior approval from the NSWCDD Information Assurance and Compliance Branch. This approval will be granted using the TARIS form and action tracker process.

C.7.8.4 Personally owned hardware or software shall not be connected or introduced to any NSWCDD hardware, network or information system infrastructure.

C.7.9 Operations Security (OPSEC):

C.7.9.1 All Contractors (including Subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract to complete Government-sponsored and administered Operations Security (OPSEC) training. In addition, all Contractors should be aware of the Critical Information List (CIL) for the department they are supporting as well as the OPSEC plan for NSWCDD. Upon contract award, all identified Contractors (including Subcontractors) shall sign a Contractor's conformance statement and submit it to the NSWCDD COR named in block 13 of the attached DD-254 thereby acknowledging that they will meet the requirements of this contract. The COR shall contact their Department Training Coordinator to schedule key employees to attend the Government-sponsored OPSEC training. The Contractor must immediately notify the Government upon the discovery of any nonconformance with the OPSEC Plan.

C.7.10 Privacy Program Training:

C.7.10.1 Privacy Program Training. Privacy training is mandatory for all NSWCDD personnel (military, civilian, and Contractor) and must be completed annually. The Total Workforce Management System (TWMS) is the official database for workforce training and is the preferred tool for taking and recording privacy act training. All NSWCDD personnel are responsible for ensuring individual annual privacy training requirements are met.

C.8 ON-SITE ENVIRONMENTAL AWARENESS

C.8.1 The Contractor shall strictly adhere to all Federal, State and local laws and regulations, Executive Orders, and Department of Defense and Navy policies.

C.8.2 The Contractor shall ensure that each Contractor employee who has been or will be issued a Common Access Card (CAC) completes the annual NSWCDD Environmental Awareness Training (EAT) within 30 days of commencing contract performance and annually thereafter as directed by their NSWCDD training coordinator or their COR.

C.8.3 The Contractor shall ensure that each Contractor employee not required to complete the training described in part C.8.2 above (i.e., those who do not have and will not be issued a CAC) reads the NSWCDD Environmental Policy Statement within 30 days of commencing contract performance. This document will be available from the COR, however, the policy is also provided on the publicly-available NSWCDD website, https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office.

C.8.4 Within 30 days of commencing contract performance, the Contractor shall certify by e-mail to their COR that the requirements captured by C.8.2 and C.8.3 above have been met. The e-mail shall include each employee name and work site and shall indicate which requirement—C.8.2 or C.8.3 above--each employee has satisfied.

C.8.5 Contractor copies of the records generated by the actions described in C.8.2 and C.8.3 above will be maintained and disposed of by the Contractor in accordance with SECNAVINST 5210.8D.

C.9 ON-SITE SAFETY REQUIREMENTS

C.9.1 The Contractor shall strictly adhere to Federal Occupational Safety and Health Agency (OSHA) Regulations, Environmental Protection Agency (EPA) Regulations, and all applicable state and local requirements.

C.9.2 The Contractor shall ensure that each Contractor employee reads the document entitled, "Occupational Safety and Health (OSH) Policy Statement" within 30 days of commencing performance at NSWCDD. This document is available at:

https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office/Safety/Safety.html

C.9.3 The Contractor shall provide each Contractor employee with the training required to do his/her job safely and in compliance with applicable regulations. The Contractor shall document and provide, upon request, qualifications, certifications, and licenses as required.

C.9.4 The Contractor shall provide each Contractor employee with the personal protective equipment required to do their job safely and in compliance with all applicable regulations.

C.9.5 Contractors working with ionizing radiation (radioactive material or machine sources) must comply with NAVSEA S0420-AA-RAD-010 (latest revision) [provided upon request]. Prior to bringing radioactive materials or machine sources on base, the Contractor must notify the Command Radiation Safety Officer in the Safety & Environmental Office.

C.9.6 The Contractor shall ensure that all hazardous materials (hazmat) procured for NSWCDD are procured through or approved through the hazmat procurement process. Hazmat brought into NSWCDD work spaces shall be reviewed and approved by the Safety & Environmental Office prior to use by submitting an Authorized Use List addition form and Safety Data Sheet that shall be routed through the government supervisor responsible for the specific work area. The Authorized Use List addition form can be found at https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office/.

C.9.7 Upon request the Contractor shall submit their OSHA 300 Logs (injury/illness rates) for review by the Safety Office. If a Contractor's injury/illness rates are above the Bureau of Labor & Statistics industry standards, a safety assessment will be performed by the Safety Office to determine if any administrative or engineering controls can be utilized to prevent further injuries/illnesses, or if any additional PPE or training will be required.

C.9.8 Applicable Contractors shall submit Total Case Incident Rate (TCIR) and Days Away, Restricted and Transfer (DART) rates for the past three years upon request by the Safety Office. A Contractor meets the definition of applicable if its employees worked 1,000 hours or more in any calendar quarter on site and where oversight is not directly provided in day to day activities by the command.

C.9.9 The Contractor shall report all work-related injuries/illnesses that occurred while working at NSWCDD to the Safety Office.

C.9.10 The Contractor shall ensure that all on-site Contractor work at NSWCDD is in accordance with the NSWCDDINST 5100.1D Occupational Safety and Health Instruction, available at:

https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office/Safety/Safety.html

C.10 DIGITAL DELIVERY OF DATA

C.10.1 Delivery by the Contractor to the Government of certain technical data and other information is now frequently required to be made in digital form rather than in hardcopy form. The method of delivery of such data and/or other information (i.e., in electronic, digital, paper hardcopy, or other form) shall not be deemed to affect in any way either the identity of the information (i.e., as “technical data” or “computer software”) or the Government’s and the Contractor’s respective rights therein.

C.10.2 Whenever technical data and/or computer software deliverables required by this contract are to be delivered in digital form, any authorized, required, or permitted markings relating to the Government’s rights in and to such technical data and/or computer software must also be digitally included as part of the deliverable and on or in the same medium used to deliver the technical data and/or software. Such markings must be clearly associated with the corresponding technical data and/or computer software to which the markings relate and must be included in such a way that the marking(s) appear in human-readable form when the technical data and/or software is accessed and/or used. Such markings must also be applied in conspicuous human-readable form on a visible portion of any physical medium used to effect delivery of the technical data and/or computer software. Nothing in this paragraph shall replace or relieve the Contractor’s obligations with respect to requirements for marking technical data and/or computer software that are imposed by other applicable clauses such as, where applicable and without limitation, DFARS 252.227-7013 and/or DFARS 252.227-7014.

C.10.3 Digital delivery means (such as Internet tools, websites, shared networks, and the like) sometimes require, as a condition for access to and/or use of the means, an agreement by a user to certain terms, agreements, or other restrictions such as to “Terms of Use,” licenses, or other restrictions intended to be applicable to the information being delivered via the digital delivery means. The Contractor expressly acknowledges that, with respect to deliverables made according to this contract, no such terms, agreements, or other restrictions shall be applicable to or enforceable with respect to such deliverables unless such terms, agreements, or other restrictions expressly have been accepted in writing by the Contracting Officer and attached to the contract; otherwise, the Government’s rights in and to such deliverables shall be governed exclusively by the terms of this contract.

CONTRACT DATA REQUIREMENTS LIST (CDRL)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A attached hereto.

CDRL A001 Contract Work Breakdown Structure CDRL A002 Integrated Program Management Report CDRL A003 Commercial Drawings/Models and Associated CDRL A004 Technical Report – Study/Services CDRL A005 Acceptance Test Report (ATR) CDRL A006 Product Baseline Index (PBLI) CDRL A007 Interface Requirements Specification CDRL A008 System/Subsystem Specification

CDRL A009 Supplier’s Configuration Management Plan CDRL A010 Notice of Revision CDRL A011 Quality Assurance Program Plan CDRL A012 Operation and Maintenance Instructions for Research and Development (R&D) Equipment CDRL A013 System/Subsystem Design Description (SSDD) CDRL A014 Operating, Support, Health, and Safety Hazard Analysis Report CDRL A015 Test Procedure CDRL A016 Configuration Status Accounting Information CDRL A017 Contracting Officer’s Management Report CDRL A018 Presentation Material CDRL A019 System/Software Integration Plan CDRL A020 Trip-Travel Report CDRL A021 Technical Review Presentation Package CDRL A022 Provisioning Parts List (PPLs)