2_SOW ESMF 20200827(Final Draft).pdf

Section C - Descriptions and Specifications

STATEMENT OF WORK

Engineering Technical Services for ENVIRONMENTAL AND SHIP MOTION FORECASTING (ESMF)

SYSTEM, NAVAL SURFACE WARFARE CENTER, CARDEROCK DIVISION

1. BACKGROUND and SCOPE OF WORK.

1.1. BACKGROUND.

The Office of Naval Research (ONR), in cooperation with the Naval Sea Systems Command (NAVSEA) Program Executive Office Ships (PEO Ships), and with the Military Sealift Command (MSC), established a Navy program to develop an ESMF system. The ESMF system would provide an operational capability that could measure, predict, and display environmental and ship motion parameters needed for ship operators to safely conduct seabasing operations at sea. The ESMF system threshold requirements were to demonstrate accurate ship motion and wave forecasting for time scales of interest (~5 minutes) in up to sea state 5 and ship speeds of up to 10 knots. The initial research and development (R&D) effort, which concluded in 2017, demonstrated utility for the seabasing application and showed promise for other at-sea operational applications. The secondary R&D effort began in 2018 and will be completed in 2021.

1.1.1. This ESMF system provides sea-based forces with environmental and ship motion forecasting as input to the Common Operation Tactical Picture (COTP), in order to forecast windows of opportunity for inter/intra-ship material and personnel movement. The ESMF system allows for single ship motion modeling and predictions, and for two ship motion modeling and predictions. The ESMF employs a customized X-Band marine radar to measure local wavefields and provides detailed sea-state information and wave timing. The specialized wave-sensing radar and an innovative signal processing method can forecast incident wave energy along the ship’s track and the resultant vessel motion predictions out to 60+ seconds in real-time. It provides queuing information for upcoming quiescent periods or conversely, imminent excessive motions, as well as recommends best courses/speeds to minimize motions based on the measured local wave energy spectrum. The ESMF system uses a reduced-order vessel motion prediction process that relies on a pre-calculated force-response database to allow for real-time computations. It uses Gravity (open-source, open-architecture) middle-ware to integrate sensor feeds, processing subroutines and user displays. This approach allows streamlined implementation of customized operator displays along with physics based models of specific vessels and unique equipment (e.g. cranes).

1.1.2. . There are currently two versions of the ESMF system. The first is the User Operational Evaluation System (UOES) which is a permanently installed system. It is currently installed on the Expeditionary Transfer Dock (ESD) ship United States Naval Ship (USNS) MONTFORD POINT and will be installed on an Expeditionary Fast Transport (EPF) ship in the near future. The major hardware subsystems of the ESMF UOES system consist of a User Workstation, a Primary Processing Unit (PPU), Coherent On Receive Radar (CORR), Ship Motion Sensor (SMS), Meteorological Sensor, and an Ethernet Switch. A system diagram describing the components of the UOES onboard the ESD can be found in Section 2.0 of the document “ESMF UOES for ESD User Manual, 29 November 2019” as referenced in Section 2.0 Applicable Documents. The second version of the ESMF system is called a Fly Away Kit (FAK). It is a portable version that is meant to be carried on and off ships for short term use (i.e. fleet exercises or demonstrations). All equipment is packed into pelican cases and can be installed/demobilized fairly quickly. The FAK consists of specialized sensors, a processing suite, and user workstations. There are currently two types of wave-sensing radars; either a modified Koden CORR 25kW X-band marine radar and Antenna or a Gamic Wave Sensing Radar and Antenna. There may be instances when a telescoping radar mast is needed if there isn’t existing structure on the ship for radar placement. The other sensors include a Meteorological (MET) Sensor and a Ship Motion Sensor (SMS) with Antenna Tree that includes dual Global Positioning System (GPS) antennas.

The control and processing unit(s) are met by two commercially available ruggedized embedded PCs, the Cincoze DS-1100. The user workstations that are typically placed on the bridge of a ship is a Dell 5290 laptop or similar system running Window 10 Professional 64-bit operating system. The ESMF User Interface runs on this processor and provides control of the system. Recent demonstrations where the FAK was utilized was onboard an Landing Platform/Dock (LPD) to support multiple National Aeronautics and Space Administration (NASA) Orion Recovery Tests; onboard USNS Pililaau in support of an exercise to resupply a Guided Missile Destroyer (DDG) from an

Large, Medium-Speed Roll-on/Roll-off (LMSR); and onboard a small ship in support of a Department of Energy (DOE) test. An example of a FAK system diagram used onboard the USNS Pililaau can be found under “System Description” on page 3 of the document “ESMF for LMSR/DDG Installation Plan 19 February 2020” as referenced in Section 2.0 Applicable Documents.

1.2. SCOPE OF WORK.

1.2.1. The scope of work for this contract consists of three tasks that are not taking place in a sequential order and can occur concurrently.

1.2.1.1. Start-Up Task: Contractor shall learn the ESMF system architecture to be able to analyze and understand the source code developed by the incumbent to be able to develop it further. The contractor shall configure the existing land-based UOES replica at their facility. Once the source code has been reviewed, the contractor shall test the source code, generate new test data files for test cases, and be able to validate the data from a previous at-sea test event.

1.2.1.2. Task 1: This task is system support. The contractor shall provide engineering support to design, fabricate, install, and sustain any existing and new UOES versions of the ESMF system onboard ESDs and EPFs. The engineering support will also include providing ESMF system support for test events and fleet experimentations.

The contractor shall be able to support any test event and fleet experimentations at sea by providing engineering support to design, fabricate, install, and sustain the FAK version of the ESMF system on either MSC, U.S. Navy ships, and other DoD ships/vessels of opportunity that becomes present.

All UOES and FAK ESMF system installations, operational tests, system sustainment and test event support requires the contractor to travel to a wide variety of locations both within the Continental United States (CONUS) and Outside the Continental United States (OCONUS). The expected work distribution, but not limited to, by performance location is Mid Atlantic US (30%); Northeast US (2%); US Gulf Coast (5%); Southwest US (30%);

Northwest US (5%); Other/OCONUS 30%. OCONUS locations typically include, but are not limited to, Guam, Saipan, Japan, Hawaii, Spain, Croatia, and Italy.

The contractor shall work on various installations, system support, and test support efforts at several sites/ships simultaneously, CONUS and OCONUS.

The installation (includes an at-sea Operational Check (OPCHECK) after the system has been installed) can range pending the type of system being installed. A FAK system installation can range anywhere from 4 days to a week pending the size of the vessel. A UOES system installation can range anywhere from 4-6 weeks pending the size of the vessel. The contractor shall accomplish all work in accordance with local, state, and federal laws. The contractor shall follow all environmental and safety regulations. All workmanship and processes shall be in accordance with industry standards.

Any test event or fleet experimentation that takes place that the contractor shall be required to support can range from 1- 3 weeks. This would include the time required for the contractor to perform a demobilization of the FAK system at the end of the test.

When travel is required to a U.S. Navy, MSC, or DoD ship/vessel, the contractor shall request the Government TA’s assistance to coordinate with the required ship’s COR, Captain, Chief Mate or Port Engineer the requested travel dates, the contractor’s intent(s) for the visit, and the proper protocol for the contractor to gain access to the ship.

The contractor shall provide any required security information requested by the ship prior to travelling to the ship and have the necessary information approved. Once the contractor has travelled to the ship, the contractor shall check in at the quarter deck and request to meet with the designated POC (i.e. chief mate, port engineer). The contractor must follow all requests set forth by the ship’s Captain or Master while onboard.

All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the PCO or the COR.

The contractor shall ensure that travel costs are in accordance with Federal Acquisition Regulation (FAR) 31.205-46 Travel Costs and adhere to the Joint Travel Regulations at http://www.defensetravel.dod.mil/site/travelreg.cfm.

http://www.defensetravel.dod.mil/site/travelreg.cfm

1.2.1.3. Task 2: This tasks will consist of the contractor providing proof of concepts and new applications of where the ESMF system can be applied. The contractor shall provide proof of concepts for integrating the ESMF radar system into both SPQ-9B and Next Generation Surface Search Radar. The contractor shall also provide application concepts of the ESMF system installed onboard DDG-51 class, Guided Missile Cruiser (CG)-47 class, or DDG-1000 class vessels.

1.2.1.4. Task 3: During this task, the contractor shall improve hardware and software designs of both the UOES and FAK versions of the ESMF system in order to enhance radar processing schemes for wave measurements and forecasting for a range of environments and ship configurations. The contractor shall perform tests of the improved hardware or software at the contractor’s facility. The contractor shall develop documentation to capture any new designs and or changes to the hardware and software of the ESMF system.

1.2.2. This contract will have an ordering period of five years from the effective date of contract award for the issuance of TOs. All TOs issued under this proposed contract will be completed within one year after the end of the ordering period.

1.2.3. The Product Service Codes (PSC) for this contract are: AD93, AD23, and AD24.

2. APPLICABLE DOCUMENTS

2.1. DoDI 5000.64, Accountability and Management of DoD Equipment and Other Accountable Property, 19 May 2011

2.2. ESMF UOES for ESD User Manual, 29 November 2019

2.3. ESMF UOES for ESD System Technical Manual 15 May 2019

2.4. ESMF_ESD Technical Data Package 15 May 2019

2.5. ESMF for LMSR/DDG Installation Plan 19 February 2020

Note: The Contractor shall utilize the latest version of the standards, specifications, and references listed above. Where amendments or revisions have been made after award, the Contractor shall comply with the most recent versions upon written approval by, or instruction from, either the Procuring Contracting Officer (PCO) or the Contracting Officer’s Representative (COR).

3. TECHNICAL and PROJECT MANAGEMENT REQUIREMENTS

3.1. ESMF SYSTEM DESIGN, FABRICATION, INSTALLATION, AND SUSTAINMENT SUPPORT

3.1.1. User Operational Evaluation System (UOES) Support. The contractor shall support the fabrication, installation, and ongoing sustainment of existing and new UOES ESMF systems on U.S. Navy, MSC, and Department of Defense (DoD) ships/vehicles of opportunity as defined in a TO. Ships/vehicles can include, but not limited to, ESDs and EPFs. The support the contractor shall provide includes final system assembly, documentation support for installation approvals, system set up and/or tear down, movement of the UOES components between the ships, system operating support during at-sea testing events and fleet experimentation / exercises, maintenance of the UOES, repair, training, and system performance reviews.

3.1.2. Fly Away Kit (FAK) Support. The contractor shall support the fabrication, installation, and ongoing sustainment of existing and new FAKs to be used on U.S. Navy, MSC, and Department of Defense (DoD) ships/vehicles of opportunity as defined in a TO. Ships/vehicles can include, but not limited to, DDGs, CGs, LPDs, and T-AKRs. The support the contractor shall provide includes shipboard installation, documentation support for installation approvals, system set up and/or tear down, movement of the FAK components between the ships, system operating support during at sea testing events and fleet experimentation/exercise, maintenance of the FAKs, repair, training, and system performance reviews.

3.1.3. ESMF System Improvements. The contractor shall improve the ESMF system design and software for ease of operation, utility, and accuracy over a range of environmental and ship configurations. The contractor shall develop and deliver improvement concepts for implementation in a technical report. (CDRL A009) The contractor may reference existing system diagrams, user manuals, and system technical manuals in Section 2 describing the current state of the ESMF.

3.1.3.1. Develop Enhanced Processing Schemes. The contractor shall develop enhanced processing schemes for wave measurement and forecasting to enable application to challenging wave propagation environments, including varying bathymetry and currents, and nonlinear wave propagation.

3.1.3.2. Investigate Enhanced Processing Schemes. The contractor shall investigate feasibility and development of enhanced radar processing schemes for ocean surface wind measurements and forecasting to enable application toward improved wave forecasting and potential application to naval operations

3.1.3.3. Enhance Processing. The contractor shall enhance the wave signal processing of new radar data filtering techniques to improve wave measurement performance. Dynamic algorithms will use data quality analysis to automatically adjust to varying conditions to optimize the wave measure process. This will ultimately improve the course and speed recommendation model and ship motion forecast model that is part of the user interface.

3.1.3.4. Adapt Approach. The contractor shall adapt the wave forecasting and ship modeling approach to accommodate new platforms and applications onboard, but not limited to, U.S. Navy Destroyers and Cruisers and other government ships that provide a good fit in the future.

3.1.3.5. Incorporate Modeling. The contractor shall incorporate modeling of alternate mechanical systems in the motion prediction process, coupling the responses of cranes for example, to the wave-driven ship motions.

3.1.3.6. Develop Interface Components. The contractor shall develop enhanced application-specific user interface components for demonstration of new capabilities including new ship types, but not limited to, U.S. Navy Destroyers and Cruisers) and supported operations onboard an ESD and EPF.

3.1.3.7. Perform Field-Testing. The contractor shall perform field-testing out at sea onboard U.S. Navy, MSC or DoDships/vehicles of opportunity to demonstrate newly developed capabilities, and the performance and utility of the FAK or UOES system in a real sea environment.

3.1.4. Adapt, Develop, Install, and Sustain the ESMF System Application to Additional Ships/Vehicles and Operations

3.1.4.1. Technical Report on Adapting ESMF System. The contractor shall develop and deliver a technical report on adapting the ESMF UOES or Fly Away Kit system to additional ships/vehicles. (CDRL A009)

Ship Surveys – The contractor shall conduct ship surveys of the ships/vehicles of which the ESMF UOES or Fly Away Kit system will be adapted to. The ship survey will include determining optimal locations for system equipment such as radars, antennas, and cable runs.

Drawings of ships/vehicles do not always provide accurate representation of the ship, requiring the contractor to perform a ship survey to better understand the ship/vehicle. The contractor will provide their findings as part of the conceptual study report (CDRL A009)

3.1.4.2. Conceptual Study Report of ESMF System. The contractor shall develop and deliver a technical report providing a conceptual study of the ESMF UOES or Fly Away Kit system on additional ships as defined in TOs.

(CDRL A009)

3.1.4.3. Adapt ESMF System. The contractor shall adapt ESMF UOES or Fly Away Kit system for ships/vehicles and operations as specified in TOs. The contractor shall research the application of generalized ship motion models to specific ship classes and other vehicle platforms. They will then develop prototypes of the ships, including hull/vehicle specific motion models.

3.1.4.4. Install and Support ESMF System. The contractor shall install and support the ESMF UOES or Fly Away Kit system or prototype onto U.S. Navy, MSC or DoD ships/vehicles of opportunity based on Government approved concepts. This support includes set up, repair, training, operation & sustainment and tear of the ESMF system or prototype. The support required shall require the contractor to be at sea for testing and operating the equipment. A TO will provide specifics on length of sea trial and destinations. The contractor shall reference the document “ESMF for LMSR/DDG Installation Plan 19 February 2020” as called out in Section 2.0 Applicable Documents.

3.2. DESIGN, TRAINING, AND SUPPORT DELIVERABLES FOR THE ESMF SYSTEM AND

SUSTAINMENT

3.2.1. Hardware Design Deliverables/Lists. The contractor shall produce a Technical Data Package (TDP) to include Computer-Aided Design (CAD) drawings, 2D/3D Models (can be generated with any CAD software), and associated textual information for the development, fabrication, and support of prototype systems (CDRL A002).

Contractor shall reference Section 2.2 “ESMF_ESD Technical Data Package 15 May 2019” as an example of what to include in the TDP. A TDP Option Selection Worksheet will be provided by Government, when issuing orders where this requirement is ordered.

3.2.2. Hardware Design Review. The contractor shall conduct Hardware Design Reviews that are scheduled upon request by the Government, to review the engineering associated with the design, manufacturing, and assembly of new ESMF system components. The Hardware Design may take place at either the contractor or government facility, or via conference call. Hardware Design Reviews may take place during an In-Progress Review if scheduling permits to allow for cost savings. At these Hardware Design Reviews, the contractor shall deliver a technical report with the results of analysis, address design changes made, and recommend design changes as a result of development and operational tests including trade-off impacts. The Government will consider whether to approve design changes at the conclusion of the Hardware Design Reviews. The contractor shall incorporate all design changes approved during the design review. The contractor shall provide meeting agenda and minutes.

(CDRLs A004, A006, and A009)

3.2.3. Installation Engineering Deliverables/Lists. The contractor shall prepare and deliver shipboard installation engineering plans and technical analysis reports with appropriate detail to allow plans to be approved by the required classification society (i.e. American Bureau of Shipping (ABS)), regulatory body, and/or Government agency (Military Sealift Command (MSC), Naval Sea Systems Command (NAVSEA)) as specified on individual TOs. (CDRLs A009 and A011).

3.2.4. Installation Design Review. The contractor shall conduct Installation Design Reviews that are scheduled upon request by the Government, to review the engineering associated with new system installation plans. The Installation Design Review may take place at either the contractor or government facility, or via conference call.

The Installation Design Review may take place during an In-Progress Review if scheduling permits to allow for cost savings. During this review the contractor shall deliver a technical report with the results of analysis and address installation changes made during the development process. All design changes presented at the Installation Design Review meeting must be approved by the Government. The contractor shall incorporate all approved design changes into the final installation design. The contractor shall provide meeting agenda and minutes. (CDRLs A004, A006, and A009)

3.2.5. Test Plans, Test and Evaluation, and Acceptance Reports. The contractor shall prepare and deliver operational test plans prior to installation onboard a ship. Immediately after installation of the UOES or Fly Away Kit ESMF System, the system shall be operationally tested by the contractor while the contractor is onboard, and again by the contractor while underway at sea (if initial testing occurs in harbor or pierside), for compliance to test plans. A TO will provide specifics on length of the at-sea operational test and destinations. An acceptance report shall be delivered to Government after each test (CDRLs A003 and A010)

3.2.6. User Manuals. The contractor shall prepare and deliver a detailed User Manual (A016) that details the operation of the ESMF system for ship’s personnel use. A System Technical Manual (A012) of the ESMF system shall also be prepared and delivered along with the User Manual for ship’s personnel use to describe a maintenance plan to maximize the longevity of the system. The User Manual shall include a recommended list of spare parts.

Both manuals shall be updated based on operational-use and feedback from ship operators and crew personnel.

(CDRLs A012 and A016)

3.2.7. Installation and Installation Support. The contractor shall perform the installation of the system while the ship is pierside. In the event the ship is not pierside due to uncontrollable circumstances, the contractor shall perform the installation of the system while the ship is in harbor, or while at sea (per the Captain’s/Master’s discretion). The contractor shall provide on-site engineering support at the installation location, to support the analysis of the technical characteristics, assembling, diagnostics, validation and test plans, and field changes. The contractor shall provide meeting minutes and technical analysis reports. (CDRLs A006 and 3.2.7, 3.2.11).

3.2.8. Hardware Familiarization. The contractor shall conduct initial system familiarization training sessions for ship board operators immediately following the completion of shipboard installations and testing of the system onboard the ship. The training will be provided to acquaint the Captain’s bridge crew with ESMF capabilities, limitations, and operations. Contractor shall prepare and deliver training slides prior to training and lessons learned after the training. (CDRLs A004 and A006). The ship’s operators may request the contractor to perform in-person training onboard the ship when a new crew comes onboard. The in-person training shall coincide with a regular scheduled ship visit for the contractor to perform maintenance and system checks while at sea if possible.

3.2.9. Engineering Change Proposals (ECPs). The contractor shall prepare and deliver ECPs. The contractor shall prepare and deliver Notice of Revision (NOR) to request change to delivery requirements to include drawings, documentation, or hardware. (CDRLs A007 and A008).

3.2.10. Computer Software Product. The contractor shall prepare and deliver system software and test case software and data files. (CDRL A015).

3.2.11. Computer Software Development Documentation. The contractor shall prepare and deliver a technical report describing any software development or modifications, as associated to the tasking in section 3.1.3, to address improvements and additional ship class/vehicle applications. (CDRL A009).

3.2.11.1. Subsections. Within the technical report, it shall include the following subsections or appendices.

• Use Cases;

• Functional requirements document;

• Detailed design documents (software diagrams included);

• Hardware Interface Control Documents (ICD);

• Software ICDs; and

• Test Cases

• Algorithm Specification – clearly defining all complex algorithms and mathematical functions

• Software Issues – outstanding software issues and ways to mitigate

• Software maintenance

3.2.12. Computer Software Familiarization. The contractor shall conduct familiarization training sessions associated with the system software and test case software and data files onboard the ship. The initial training will be performed in person after system installation onboard the ship. This training can coincide with Hardware Familiarization Training. The contractor shall prepare and deliver training slides prior to training in accordance with CDRL A019 and provide any recommendations/lessons learned from the training in accordance with CDRL A006.

As software is updated by the contractor, the contractor shall provide updated software training material to the ship’s operators. The ship’s operators may request the contractor to perform in-person training onboard the ship when a new crew comes onboard. The in-person training shall coincide with a regular scheduled ship visit for the contractor to perform maintenance and system checks if possible.

3.3. TRANSFER OF MATERIALS BETWEEN SPONSORS

3.3.1. Loaning of FAK. The U.S. Navy intends to loan a FAK to other U.S. Government entities of their discretion for testing. Use of the FAK will be mutually beneficial for both the U.S. Navy and other government entities’ missions. NSWC Carderock intends to issue appropriate DD-1149 forms to transfer the FAK to other U.S.

Government entities.

3.3.1.1. Procedures. The following are the procedural details regarding the transfer of each Fly Away Kit:

• The contractor shall transfer the FAK from their storage facility to the ship of opportunity;

• The contractor shall setup and install the FAK onboard the ship of opportunity;

• The contractor shall ride on the ship of opportunity and operate the FAK during the entire test;

• Once test is complete, the contractor shall transport the FAK back to their storage facility; and

• Upon arrival back to the contractor’s storage facility, the Carderock COR will issue an 1149 transferring the FAK back to the ESMF contract.

3.4. GENERAL PROJECT MANAGEMENT REQUIREMENTS

3.4.1. Project Manager. The Contractor shall appoint and maintain a Project Manager (PM) for this contract and the associated TOs. A clear line of project authority shall exist among all organizational elements supporting this requirement.

3.4.1.1. Management Program. The Contractor shall develop and implement a management program to facilitate the efficient and effective execution of the contract requirements.

3.4.1.2. Task Completion. The PM shall be responsible for ensuring the accomplishment of all tasks required by this contract.

3.4.1.3. Administration. The PM shall organize, plan, schedule, implement, control, analyze, and provide reports as required for each TO.

3.4.1.4. Contractor Resources. The PM shall have resources and authority to ensure efficient and timely program execution and shall be the contractor's focal point for all required tasks.

3.4.1.5. Contract Status. The contractor's PM shall be prepared at all times to present and discuss the status of contract activities, requirements, and issues.

3.4.1.6. Contractor’s Point of Contact (POC). The PM shall be the primary POC for all work performed under the contract.

3.4.1.7. PM Government Coordination. The PM shall keep the Contracting Officer’s Representative (COR) informed of any performance issues, cost or financial concerns, and potential problems that, if unresolved, will adversely affect the contractor’s performance, schedule or costs, and take all appropriate measures to mitigate adverse impact to the contract.

3.4.2. Monthly Status Report. The contractor shall prepare and deliver a monthly status report (CDRLs A001).

A list of deliverables and Trip/Travel Report shall be provided along with the monthly status report (CDRLs A017 and A018).

3.4.3. Meetings and In-Progress Reviews (IPR). The Contractor shall participate in technical meetings and IPRs to communicate the status of actions, objectives, and milestones. These include recurring meetings outlined below. The Contractor shall provide read ahead briefings and presentation material for each meeting or IPR (CDRL A004, A005). Additionally, the Contractor shall perform post-meeting services including providing meeting minutes for comment and approval, itemized lists of critical actions by office of primary responsibility, and estimated timelines to completion. (CDRL A006)

3.4.3.1. Base Year Kick Off Meeting. The Contractor shall conduct an initial contract-level informational brief.

The agenda should include a Contract Overview, an introduction to key personnel and workflows, workload plans including Key Personnel assignments, lines of communication, and priorities of work.

3.4.3.2. Quarterly IPR meeting. The Contractor shall conduct a contract-level informational brief outlined at the contract and individual TO level. The agenda shall include updated workflows; workload plans; Key Personnel assignments; and a review of CLINs by funding and labor categories by man-hours, cost, schedule, and performance, including forecasts.

3.4.3.3. Technical Advisement Sessions. The Contractor shall participate in ad hoc meetings in direct support of the program management and the development of TOs, and to provide onsite subject matter expertise in selected forums necessitating consultation.

3.4.4. Data Requirements

3.4.4.1. Technical Data. The Government obtains rights in technical data, including a copyright license, under an irrevocable license granted or obtained for the Government by the contractor. It is anticipated that technical data will be produced, furnished, or acquired in the performance of this contract. The data type, quantity or quality, and format of the data to be delivered is specified in the Contract Data Requirements List (CDRL), Exhibit A, of this contract.

3.4.4.2. Government Rights. The Contractor shall adhere to the definitions and terms specified in DFARS 252.227-7013 and DFARS 252.227-7014 and other applicable clauses and provisions of this solicitation/ contract delineating the respective rights and obligations of the Government and the Contractor regarding the use, reproduction, and disclosure of such data.

3.4.4.3. Protecting Data. Establish and maintain adequate procedures for protecting technical data delivered to or stored at the repository from unauthorized release or disclosure;

3.4.4.4. Controlling Release of Data. Establish and maintain adequate procedures for controlling the release or disclosure of technical data from the repository to third parties consistent with the Government's rights in such data;

3.4.4.5. Delivering Data. When required by the Contracting Officer’s Representative, deliver data to the Government on paper or in other specified media;

3.4.4.6. Currency of Data. Be responsible for maintaining the currency of data delivered directly by Government contractors or subcontractors to the repository;

3.4.4.7. Non-Disclosure Agreement. Obtain use and non-disclosure agreements, as prescribed by DFARS 227.7103-7, from all persons to whom government purpose rights data is released or disclosed; and

3.4.4.8. Disclosure of Data. Indemnify the Government from any liability to data owners or licensors resulting from, or as a consequence of, a release or disclosure of technical data made by the data repository contractor or its officers, employees, agents, or representatives.

3.4.4.9. Distribution Statements. Distribution statement requirements will be noted on applicable CDRLs. The Contractor shall mark all data in accordance with the required distribution statement.

3.4.4.10. List of Deliverables. The Contractor shall draft and provide a comprehensive deliverable list including all data items required and delivered, and all delivered materials for TOs issued (CDRL A003). Additionally, the Contractor shall submit as an attachment to the Monthly Status Report. Substantiating documentation for tangible items shall include a DD Form 1149 (Requisition and Invoice/Shipping Document), as an attachment.

3.5. LOGISTICS:

3.5.1. Packing, Handling, Storage, and Transportation (PHS&T).

3.5.1.1. Prepare, and Deliver. The contractor shall complete all required delivery documentation, prepare materials/assembly for delivery, and deliver equipment to destinations, including Continental United States (CONUS) and outside CONUS (OCONUS) locations.

3.5.1.2. Documentation. The contractor shall prepare, maintain, and provide records of DD Form 1149 shipping documentation for all Contractor Acquired Material (CAM) or Contractor Acquired Property (CAP) transferred to the Government, and Government Furnished Material (GFM) and Government Furnished Equipment (GFE) transferred to the contractor by the Government. The contractor shall ensure that signed DD Form 1149s are obtained from the receiving activity and kept for record. All DD Form 1149s shall include contract number and CLIN/SLIN number, and be made available for inspection by the Government upon demand. The contractor shall follow In Transit Guidance Outlined in DODI 5000.64.

4. GOVERNMENT FURNISHED PROPERTY (GFP), CONTRACTOR ACQUIRED

MATERIAL (CAM), AND GOVERNMENT FURNISHED INFORMATION (GFI).

4.1. GFP. GFP consist of Government Furnished Material (GFM) and Government Furnished Equipment (GFE). The Government will provide the GFP (GFM and GFE) as specified in each TO. Serially managed items shall be managed in accordance with DFARS 252.211-7007. Non-serially managed items are those provided to the Contractor by the COR and require only the event of GFP receipt to be reported. All GFP is the property of the U.S.

Government and shall not be transferred to any individual or agency, public or private, without the express written approval of the PCO. GFP shall only be used to execute requirements under this TO. All GFP shall be returned to the Government at the conclusion of the contract unless otherwise directed by the COR. The contractor shall provide a GFP report bi-annually (CDRLs A014)

4.2. CAM. The contractor shall provide a CAM inventory report bi-annually. (CDRL A013)

4.3. GFI. The Government will provide GFI when issuing a TO. GFI includes, but is not limited to, technical documents; drawings; electronic media files or data; ship alterations; scheduling requirements; and test plans. GFI shall be handled in accordance with its classification markings. Copies of all physical and electronic GFI shall be returned to the Government at the completion of the associated TO. Unclassified Naval Nuclear Propulsion Information (U-NNPI) data/information and all classified data/information will be handled and stored in accordance with the DD Form 254.

4.4. GOVERNMENT PROVIDED SOFTWARE. The Government will provide any specialized, Government-owned software required to complete tasking in an issued TO. The Contractor shall be responsible for acquiring any commercial off the shelf (COTS) software required to complete assigned tasking.

4.5. NON-DISCLOSURE AGREEMENTS. Contractor shall have contactor employees sign non-disclosure agreements as required for sensitive technical data associated with the performance of TOs.

4.6. COST Material costs will consist of design configurations to include the UOES, FAK, and assemblies/subassemblies. The Contractor shall assemble, deliver, modify and maintain materials identified under CLIN XXXX. Quantity and configurations of the hardware obtained for the execution of this contract shall be optimized to minimize hardware costs for training installations while reliably executing both the tactical and trainer software. The Bill of Materials for any delivery shall be submitted for approval prior to ordering of any items Packing Materials and Shipping to and from Navy facilities will be required. The materials required for this effort will include, at a minimum a User Workstation, a Primary Processing Unit (PPU), Wave Sensing Radar, Ship Motion Sensor (SMS), Meteorological Sensor, GPS antennas, and an Ethernet Switch

5. PERSONNEL REQUIREMENTS

5.1. PERSONNEL QUALIFICATIONS. The Contractor shall provide capable personnel with qualifications and experience levels, security clearances, and necessary licenses, certifications, and training as noted in Attachment 03, Personnel Qualifications, in Section J to perform the work at the Contractor’s designated site.

5.2. IDENTIFICATION. In the performance of TOs, Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as such and by displaying distinguishing badges or other visible identification for meetings with Government personnel at either the Contractor’s designated site, a Government facility, or onboard a ship. Contractor personnel shall appropriately identify themselves as Contractor employees during telephone conversations and in formal and informal written correspondence including email.

5.3. BADGING. The Contractor shall obtain identification badges from the Government for all Contractor personnel requiring access to Government property for any necessary meetings, or aboard ships. Contract employees shall ensure identification badge are visible at all times while on Government property. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to applicable regulations concerning the use and possession of the badges. The Contractor shall be responsible for ensuring that all identification badges issued to Contractor employees are returned to the appropriate Security Office within 48 hours following completion of the TO, relocation or termination of an employee, and upon request by the Contracting Officer’s Representative.

6. SECURITY REQUIREMENTS

6.1. FACILITIES REQUIREMENTS: The contractor shall comply with the requirements of DD Form 254 included in Section J due to the nature of the work and secret clearance request.

7. DUTY LOCATION and TRAVEL REQUIREMENTS

7.1. DUTY LOCATION. The primary place of performance is the Contractor’s or Subcontractor’s facilities. Other places of performance worldwide are contingent upon emergent requirements and will be identified within each TO.

7.2. TRAVEL. The Contractor will be required to perform travel, as identified within each TO.

7.2.1. Continental United States (CONUS). CONUS travel will be required to technical and IPR meeting locations; to U.S. ports and shipyards based on ship/vehicle locations, to equipment vendor facilities, and to test locations. CONUS travel destinations may include, but not limited to, Norfolk, VA; Little Creek, VA; Newport News, VA; San Diego, CA; Portland, WA; Washington DC; Memphis, TN; Charleston, SC; Jacksonville, FL;

Houston, TX,; and Philadelphia, PA.

7.2.2. Outside Continental United States (OCONUS). OCONUS travel will be required to participate in technical meetings, visit equipment vendor facilities, visit ship locations for site surveys, ship checks, test events, or stays in ports-of-call while in transit (termed “remain overnight”) for an extended sea-trial event. OCONUS travel destinations may include, but not limited to, Hawaii, Japan, Singapore, Croatia, Philippines, Guam, Saipan, Italy, Bahrain, and Dubai.

7.2.2.1. Travel Restrictions. OCONUS travel is restricted to the Geographic Combatant Commands (GCCs) of US Northern Command (NORTHCOM), US Pacific Command (PACOM) and US European Command (EUCOM) Area of Operations (AOR) less Israel, Georgia, Azerbaijan, Armenia, and Ukraine.

7.2.2.2. Authorization. The contractor shall obtain all requisite Combatant Commander (COCOM) and Department of State authorizations PRIOR to travel and in accordance with the electronic Foreign Clearance Guide (eFCG, available at https://www.fcg.pentagon.mil). This includes mandatory and minimum pre-travel requirements such as itinerary, training, and preventative medicine.

7.2.2.3. Authorization Lead Time. Lead times to obtain travel authorizations vary and must be planned well in advance. The contractor is NOT authorized to depart the CONUS without final authorizations from cognizant authorities stipulated in the eFCG. The COR will coordinate all Foreign Travel Clearance requirements on behalf of the contractor and serve as liaison with external agencies.

7.2.2.4. Additional Responsibilities. Operational Area Clearance, passport coordination; obtaining visas;

immunizations; security awareness and training.

CYBERSPACE INFORMATION TECHNOLOGY/CYBERSECURITY

WORKFORCE (CYBER IT/CSWF)

8.1. GOVERNING POLICY. The following applies to all contractor personnel performing duties in cyberspace under this contract or task order (hereinafter “contract”). Such personnel will be designated as members of the Information Assurance Workforce (IAWF), also known as the Cyberspace Information Technology/Cybersecurity Workforce (hereinafter “Cyber IT/CSWF”). All Cyber IT/CSWF members must meet the mandated qualification and compliance requirements for their duties as well as be designated by the NSWCCD Commanding Officer in writing as members of the Cyber IT/CSWF. All Cyber IT/CSWF members must meet their requirements prior to beginning contract performance, and maintain them throughout contract performance.

8.1.1. Regulations and Policies. The requirements for Cyber IT/CSWF contractor personnel are based on the following regulations and policies:

8.1.1.1. Defense Federal Acquisition Regulation Supplement (DFARS) clause subpart 239.71 (Security and Privacy for Computer Systems)

8.1.1.2. DFARS clause subpart 239.7102-3 (Information Assurance Contractor Training and Certification),

8.1.1.3. Department of Defense (DoD) 8570.01-M, Information Assurance Workforce Improvement Program, Incorporating Change 4 and;

8.1.1.4. DoD Directive (DoDD) 8140.01 Cyberspace Workforce Management, dated 11 August 2015

8.2. REQUIREMENTS FOR CONTRACTORS USING GOVERNMENT-OWNED INFORMATION

SYSTEMS OR NETWORKS

8.2.1. Applicable Forms:

8.2.1.1. Defense Information Systems Agency (DISA) Cyber Awareness Challenge. All must complete the Defense Information Systems Agency (DISA) Cyber awareness challenge prior to being granted access, and each USG fiscal year (1 Oct - 30 Sep) thereafter.

8.2.1.2. Systems Authorization Access Request – Navy. All must complete a System Authorization Access Request – Navy (SAAR-N). The SAAR-N is valid for the length of the contract period of performance. Note:

Training in addition to 1.a. above may be required based on information classification and as identified by the NSWCCD security office.

8.2.1.3. Privileged Access Agreement and Acknowledgement of Responsibilities Form (PAA). Those with duties requiring privileged access as defined in DoD 8570.01-M must complete a Privileged Access Agreement and https://www.fcg.pentagon.mil/

Acknowledgement of Responsibilities Form (PAA). The PAA is an annual requirement (based on last signature date) and must identify each system the individual is authorized to access and the operating system/computing environment (OS/CE). Those requiring privileged access must provide proof of training for each OS/CE when requesting privileged access, unless the Information Assurance Workforce Certification Matrix (Appendix X, Section X) specifies that a certification is required.

Note: PAA holders are required to have a satisfactorily adjudicated security clearance, including a T5 investigation, and may be subject to random polygraph examinations.

8.2.2. Code 104 Contractors:

8.2.2.1. Assessment and Authorization/ Risk Management Framework/ Authority to Operate. Create Assessment and Authorization (A&A)/Risk Management Framework (RMF)/Authority to Operate (ATO) boundaries registered in Enterprise Mission Assurance Support Service (eMASS).

8.2.2.2. Life-Cycle Maintenance. Provide life-cycle maintenance upkeep in eMASS to an accredited boundary.

Note: Cyber IT/CSWF contractor personnel may support the efforts specified in 2.a. and b. above through the Change Control Board (CCB), excluding updates to eMASS and the artifacts retained therein.

8.3. CYBER IT/CSWF IDENTIFICATION

8.3.1. IAWF Certification Matrix. The attached IAWF Certification Matrix (Appendix X, Section X) identifies those labor categories, which are designated as Cyber IT/CSWF and the qualification requirements for each category. The Contractor shall provide the following information to the Contracting Officer’s Representative (COR) for each Cyber IT/CSWF personnel (both Key and Non-Key) who the Contractor intends to assign to perform under the applicable TO. For Key Personnel, this information must be submitted in the proposal; for non-key personnel, this information may be submitted after contract award, but must be submitted prior to the start of contract performance:

8.3.1.1. Name. Person’s name,

8.3.1.2. Labor Category. Person’s assigned labor category, if appropriate,

8.3.1.3. Individual Qualifications. Proof of person’s individual qualification(s) for the assigned labor category, designation as Information Assurance Technician (IAT) or Information Assurance Manager (IAM), and IAT/IAM level as identified in DoD 8570.01-M. This proof includes, but is not limited to, baseline certification and, if applicable, training certificate(s) for all OS/CE for which they have privileged access.*

*Note: Qualifications or certifications meeting higher-level requirements may be used to fulfill lower position requirements. Example: A CISSP normally used for a level III requirement may be used to fill a level II position.

8.3.2. Specified Qualification Requirements. The Contractor is responsible for ensuring all identified contractor personnel comply with all specified qualification requirements prior to performance, and tracking its personnel to ensure that their qualification certifications do not lapse during the contract period of performance.

The Contractor shall notify the COR if any of its Cyber IT/CSWF personnel fail to obtain or maintain any Cyber IT/CSWF qualification(s) during the contract period of performance and replace such personnel with qualified personnel as directed by the COR or Contracting Officer. Upon request, the Contractor shall provide documentation to the COR that its personnel have all necessary certifications and qualifications and have met all continuous learning requirements, including requirements for certification(s), certification maintenance, and proof of continuing education and/or sustainment training required for Cyber IT/CSWF functional responsibilities.

8.4. CYBER IT/CSWF QUALIFICATION,CERTIFICATION, AND CONTINUOUS EDUCATION

REQUIREMENTS

8.4.1. Cyber IT/CSWF Qualifications. All contractor Cyber IT/CSWF personnel must meet baseline certification requirement prior to beginning contract performance and sustain the qualification requirements for their duties in accordance with DoD 8570.01-M. The Contractor shall not provide any personnel who does not meet the minimum Cyber IT/CSWF baseline qualification requirements for the functions they will perform.

8.4.2. Continuing Learning Requirements (CLR). Per DoD 8570.01-M, all Cyber IT/CSWF personnel are required to participate in at least 40 hours of continuous learning per calendar year. This requirement is separate from any CLR necessary for certification and qualification maintenance, although continuous learning hours obtained in the course of qualification or certification maintenance may count towards the annual requirement.

8.5. CYBER IT/CSWF DESIGNATION

8.5.1. Designation Letter.

8.5.1.1. COR Responsibilities. Following receipt and verification of the contractor’s proposed Cyber IT/CSWF information, the COR will issue a Cyber IT/CSWF designation letter to each of the contractor’s personnel performing Cyber IT/CSWF duties. The Designation Letter verifies the qualifications required for the labor category in which the contractor Cyber IT/CSWF personnel will provide services.

8.5.1.2. Terms. The government-issued Designation Letter does not create an independent or separate contract or agreement between the contractor Cyber IT/CSWF personnel and the Government. In addition, it does not change the scope of the contract or any of its terms or conditions

8.6. CYBER IT/CSWF PERSONNEL REPLACEMENTS OR CHANGES IN DUTY

8.6.1. Replacements/Changes. If the Contractor replaces any Cyber IT/CSWF personnel or changes the duties identified in the Cyber IT/CSWF Certification Matrix during contract performance, the Contractor shall coordinate with the COR and the Cyber IT/CSWF PM of the personnel change. Initial and final notification must be in writing, and comply with the above instructions for the replacement personnel. This is in addition to any other contractual requirements regarding substitution of personnel.

8.7. ACCESS TERMINATION

8.7.1. Access and Authorization. Contractor Cyber IT/CSWF personnel’s access to, and authorization to perform functions on, DON IS(s) shall be terminated upon the end of contract performance or upon any of the following conditions:

8.7.1.1. Qualifications. The person fails to maintain the required Cyber IT/CSWF qualifications for the labor category in which the personnel is performing;

8.7.1.2. Certifications. The person fails to maintain the required Cyber IT/CSWF certification(s) for the labor category in which the personnel is performing;

8.7.1.3. Continuous Learning. The person fails to meet the required Cyber IT/CSWF continuous learning requirements while performing;

8.7.1.4. Performance. The person is no longer performing under this contract; or

8.7.1.5. Cyber IT/CSWF Functions. The person is no longer performing Cyber IT/CSWF functions under this contract; or

8.7.1.6. Regulations. The person is in violation of any other Cyber IT/CSWF regulations or policies as determined by the Government.

8.8. BILLING

8.8.1. Invoicing

8.8.1.1. Training/Certification Testing.