Draft SOW-ECDIS.docx

Statement of Work (SOW) for A Red Hat Enterprise Linux compatible Radar Communication and Control software application for integration with the Navy ECDIS software.

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 541, which is responsible for surface ship Electronic Chart Display Information System (ECDIS).

1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied

1.0.3 Government/Contractor Relationship

1.0.3.1 The services to be delivered under this Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

1.0.3.2 The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

1.0.3.3 Contractor personnel under this Contract shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

1.0.4 Employee Relationship:

1.0.4.1 The services to be performed under this Contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

1.0.4.2 Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

1.0.4.3 Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

1.0.4.4 It is the Contractor's, as well as the Government's, responsibility to monitor Contract activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

1.0.4.4.2 The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

1.1 BACKGROUND

The Navy ECDIS software is being developed to run on the Red Hat Enterprise Linux (RHEL) operating system (version 8.6) for the surface and submarine fleet. The Navy ECDIS software implements an interface to communicate with the AN/SPS‐73(V)12 Surface Search Radar System for purposes of receiving radar video and track data, sending track acquire requests, and controlling the SPS‐73 secondary radar processor.

A native Linux application library for Radar Communication and Control is desirable for integration with the Navy ECDIS software. Additionally, it is desirable to have a software that may have future expansion radar video distribution capability for other radars, including Sperry BridgeMaster series, Hensoldt Sharpeye, and other radars in the US Navy fleet.

1.2 SCOPE OF WORK

The Contractor shall provide software to meet or exceed the specifications found below. including a fleet-wide license for integration testing and fielding of the Navy ECDIS software.

2.0 APPLICABLE DOCUMENTS

· Navy Issuances https://www.secnav.navy.mil/doni/default.aspx

· DOD Issuances https://www.defense.gov/Resources/Forms-Directives-Instructions/

· NAVSEAINST Library https://www.navsea.navy.mil/Resources/Instructions/ The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

3.1 Software Application

The contractor shall provide a Radar Communication and Control software application to send and receive messages between the Navy ECDIS software and the AN/SPS‐73(V)12 Surface Search Radar System.

The Radar Communication and Control software application shall be able to output messages as well as register for and receive incoming messages as defined in the Navy ECDIS Interface Design Description (IDD), Document ID: 03956-5009694 Rev B, section 3.11 SPS-73 RDSCOMMS.

The contractor shall provide the Radar Communication and Control software application via minor modification of existing commercial software or any other method the contractor deems available.

The contractor shall provide video distribution interfaces for additional radars to include:

· Sperry BridgeMaster-E

· Hensoldt Sharpeye

· SPQ-9B

· SPS-67

The contractor shall provide documentation of the software, to include a technical manual describing software features, capabilities and limitations, and operation instructions.

The contractor shall provide an application programming interface (API) manual for software integration into a larger application software.

The contractor shall provide warranty and software support for ten years after initial delivery.

3.2 Licensing

A fleet-wide license for the Radar Communication and Control software application to facilitate the integration testing and fielding of the Navy ECDIS software.

3.3 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components

3.3.1 The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor may recommend a solution to include the impact on the contract price and delivery. The contractor shall not initiate any item redesign or incur any additional costs without the express, written authorization of the contracting officer.

4.0 DATA REQUIREMENTS

N/A

5.0 SECURITY REQUIREMENTS

5.4 OPERATIONS SECURITY (OPSEC)

5.4.1 The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. The NSWC Philadelphia Division's (NSWCPD) Critical Information List (CIL)/ CIIL (Critical Indicators and information list) will be provided on site, if warranted. Performance under this contract requires the contractor to adhere to OPSEC requirements, which may include the NSWCPD Contractor OPSEC Plan. When the NSWCPD Contractor OPSEC Plan is required, the contractor shall return acknowledgment of the plan within 15 days of receipt. During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCPD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCPD’s CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI) unless such FOCI has been appropriately mitigated through measures approved by the Defense Counterintelligence and Security Agency. Questions concerning these requirements shall be directed to the PCO.

5.4.2 CUI correspondence transmitted internally on the contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting Controlled Unclassified Information (CUI) in Non-federal Systems and Organizations.

Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.

5.4.3 NSWCPD’s CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to the PCO, and the COR who will forward the required to the NSWCPD Public Release Authority for review.

5.4.4 Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/compromise of government Classified or CI, Business Sensitive, Company Proprietary information related to this or other program must be immediately reported to the contractor's Facility Security Officer and Cognizant Security Office and/or the Naval Criminal Investigative Service, and the NSWC PD Security Division (Code 105).

5.5 RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED INFORMATION (CUI) All Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document. In accordance with DoDI 5200.48, CUI must be safeguarded to prevent Unauthorized Disclosure (UD). CUI export controlled technical information or other scientific, technical, and engineering information must be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR. Nonfederal information systems storing and processing CUI shall be protected per NIST SP-800-171, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and posting on social media websites (Facebook, Instagram, Twitter, LinkedIn, etc.) are prohibited. Destroy CUI associated with this contract by any of the following approved methods: A cross-cut shredder; a certified commercial destruction vendor; a central destruction facility; incineration; chemical decomposition; pulverizing, disintegration; or methods approved for classified destruction.

5.6 PLANNING, PROGRAMMING, BUDGETING AND EXECUTION (PPBE) DATA.

When contractor employees, in the performance of their duties, are exposed to Planning, Programming, Budgeting and Execution (PPBE) data, a Non-Disclosure Agreement (NDA) with all affected contactor personnel must be executed in coordination with the COR and PCO to ensure safeguarding disclosure of this data.

5.7 U-NNPI SECURITY REQUIREMENTS

N/A

6.0 PLACE OF PERFORMANCE

All items received by NSWCPD must be centrally received at the following address:

POC:

Anthony Dyszel

NSWCPD C541

215-806-1125 anthony.j.dyszel.civ@us.navy.mil

7.0 TRAVEL

8.0 GOVERNMENT FURNISHED PROPERTY

N/A

9.0 GOVERNMENT FURNISHED INFORMATION

N/A

10.0 PURCHASES

N/A

11.0 COUNTERFEIT MATERIAL PREVENTION

N/A

12.0 PERSONNEL

N/A

13.0 NSWCPD ELECTRONIC COST REPORTING AND FINANCIAL TRACKING (ECRAFT) SYSTEM

N/A

14. SPECIAL REQUIREMENTS

SOW-PWS Template 12 January 2024 version Page 11