SOW VPX Chassis - 20240625 (2).pdf

SOW-PWS Template 03 June 2024 version Page 1

Statement of Work (SOW) LHD/A Machinery Control Systems

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 515, which is responsible The Landing Helicopter Dock and Landing Helicopter Assault (LHD/A) Machinery Control Systems (MCS).

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

SOW-PWS Template 03 June 2024 version Page 2 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:

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

1.1 BACKGROUND

LHD 8, LHA 6 and LHA 7 Class Machinery Control Systems are currently experiencing obsolescence issues with respect to both their hardware/computer software configuration items (HWCI/CSCI) that will require a technology refresh and re-engineering to sustain shipboard tactical operations. Through the LHD/A MCS Tech Refresh program the legacy Versa Module Europa (VME) chassis has been replaced with the modernized VME Peripheral Component Interconnect with extents for both buses standards (VPX) chassis design. The VPX Chassis will be installed shipboard within the Data Acquisition Units (DAU), Gas Turbine Workstations (GTWS) and Deisel Generator Workstation (DGWS) enclosures. In order to ensure the LHD/A MCS Team maintains fully functioning modernized system capable of supporting the fleet and lab environment, a VPX Chassis will need to be identified.

1.2 SCOPE OF WORK

The Contractor shall provide hardware to meet or exceed the specifications found below.

Contractor shall utilize the design specifications and reference documentation to manufacturer VPX Chassis to support LHA6, LHD8 & LHA7 shipboard installation.

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/

2.1 Additional details and specifications can be found within the following reference documentation:

VPX Chassis Specs NSWC_NetList

These documents can be referenced at: www.website.gov

SOW-PWS Template 03 June 2024 version Page 3

The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

Contractor shall provide the following hardware and software components that meet or exceed the specifications defined below.

Qty. 75 VPX Chassis as defined below, manufactured and delivered by July 2025.

Qty. 75 VPX Chassis as defined below, manufactured and delivered by February 2027.

Qty. 75 VPX Chassis as defined below, manufactured and delivered by May 2031.

Qty. 118 VPX Chassis as defined below, manufactured and delivered by February 2027.

3.1 Specifications

VPX Chassis, with the following specifications:

‐ 5U (h) X 84HP (w) X 10.75” (d), ‐ Vertical orientation ‐ Accommodates 12x 3U x 160mm 1” pitch boards and 2x 3U x 160mm 2” pitch power supplies.

‐ Includes IEEE 1101.10 Extrusion profiles and 24x metal screwed in card guides ‐ Mountable with Jonathan 515QD-22-P rails.

‐ VPX Chassis shall be constructed out of Aluminum and include the following material and protective finishes:

• Side Plates - Chromate, Chemical conversion coating in accordance with

MIL-DTL-5541, Type I, Class 3, Color Yellow

• Front Panels - Chromate, Chemical conversion coating in accordance with

MIL-DTL-5541, Type II, Class 1A, Color Clear.

• Silkscreen Color - Black Per Enthone (HYSOL) #50-700

• No paint

‐ VPX Backplane shall be 3U, vertically oriented, with 12x VPX slots and 2x VITA 62 slots. All cards will communicate through the backplane with ethernet signals. Each of the 12x VPX slots shall be configured to the signal specifications defined by the NSWC Netlist documentation and maintain the following configuration:

• 2x 10G-KR/1G-KX ports between the switch and SBC slot (1-2)

• 1x 1G-KX port between the switch and each payload slot (3-9)

• 1x QSGMII port and 1x 1G-KX port between the switch and the companion card slots (10-12) ‐ Required operational temperature range: -40C to +75C ‐ Cooled by 3x 150CFM (P/N: FFB1212EH) and 2x 27.55CFM (P/N: AFB0612HH-A) fans that fit within the bottom footprint of the chassis. Air will flow from bottom to top through the chassis.

‐ No top and bottom covers for open air flow ‐ AC power inlet in rear and on/off switch in front ‐ Vertical handles on the front of the chassis to allow for racking out ‐ Bracketing on the backside for the addition of cable management ‐ Chassis payload must include:

• 12 slots 3U VPX plus 2 VITA 62 power supply slots

SOW-PWS Template 03 June 2024 version Page 4

1x Single Board Computer (SBC) Slot - Compatible with Curtiss- Wright P/N: VPX3-1260-A14DL5A

1x Network Switch Slot - Compatible with Interface Concept P/N:

ComEth4582a

3x Switch Companion Slots - Compatible with Interface Concept ComEth4582 Switch Extension Module P/N: 6605-010-783

7x Payload Slots - Compatible with the following North Atlantic Industries I/O Card P/Ns:

o 68G5-2-AD4AD4AD4JHC01-68, o 68G5-2-RT1RT1RT1JHC01-68, o 68G5-2-DA1Z00Z00JHC01-68, o 68G5-2-DT1DT1DT1JHC01-68, o 68G5-2-SC3SC3SC3JHC01-68

2x Power Supplies - Compatible with Switching Power P/N: VPX-

300P-COV-10HP

VPX Alignment Pins (pin_1 = top, pin_2 = bottom) Slot 1: pin1 = 90 degrees, pin2 = 90 degrees Slot 2: pin1 = 0 degrees, pin2 = 0 degrees Slot 3-9: pin1 = 270 degrees, pin2 = 270 degrees Slot 10-12: pin1 = 315 degrees, pin2 = 315 degrees Slot 13-14 (power supply only): pin1 = 270 degrees, pin2 = 45 degrees ‐ VPX backplane shall be equipped with a DIP switch (P/N: TDA08H0SB1) that is able to set the 8x DIO signals on the Curtiss Wright VPX3-1260-A14DL5A SBC ‐ The following ports will be routed from the VPX3-1260-A14DL5A SBC through the backplane out to the front panel of the chassis. Ports require connected dust covers for all ports and adhesive to secure connections to backplane.

• 2x RS232 COM Ports (P/N: CSMUZ9MF 2.5)

• 2x USB 2.0 Ports (P/N: USBPNLAFAM3)

• 1x DVI Port (P/N: VIC00001)

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

3.2.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

CDRL A001, Contract Status Report

5.0 SECURITY REQUIREMENTS

SOW-PWS Template 03 June 2024 version Page 5

5.1 SECURITY TRAINING

N/A

5.2 ON SITE WORK

N/A

5.3 DD254 REQUIREMENT

N/A

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).

SOW-PWS Template 03 June 2024 version Page 6

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

5.8 U-NNPI

6.0 PLACE OF PERFORMANCE

The contractors primary place of performance shall be at the contractor’s facility.

7.0 TRAVEL

N/A

8.0 GOVERNMENT FURNISHED PROPERTY

N/A

9.0 GOVERNMENT FURNISHED INFORMATION

N/A

10.0 PURCHASES

N/A

11.0 COUNTERFEIT MATERIAL PREVENTION

12.0 PERSONNEL

SOW-PWS Template 03 June 2024 version Page 7

13.0 NSWCPD ELECTRONIC COST REPORTING AND FINANCIAL TRACKING

(ECRAFT) SYSTEM

14.0 SPECIAL REQUIREMENTS

15.0 DELIVERY REQUIREMENTS AND POC

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

NSWC Philadelphia Division NSLC Detachment 1601 Langley Ave, Bldg. 542 Philadelphia, PA 19112

POC:

Mitch Soper

NSWCPD LHD/A MCS C515

215-897-2468 robert.m.soper7.civ@us.navy.mil

SOW-PWS Template 03 June 2024 version Page 8