SOW.docx

Statement of Work (SOW) Analog Multiplexer Test Routine Development and Repair

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 554, which is responsible for IN-SERVICE DDG-51 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 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

DDG-51 Contract 2 and Contract 3 Hull’s Data Interface Units (DIUs) utilize numerous Analog Multiplexer (MUX) circuit card assemblies (CCAs) for signal processing. These CCAs are essential for operation of the ships engineering plant, including LM2500 Gas Turbine Modules (GTMs) and Gas Turbine Generators (GTGs). These CCAs experience high failure rates and are in short supply with 1-2 year lead times. Timely and reliable repair of these MUX cards is essential to the DDG-51 fleet’s execution of its mission.

1.2 SCOPE OF WORK

NSWCPD Code 554 is looking for engineering and technical services for the development, programming, and validation of a circuit card test program set for Analog MUX (P/Ns 63E917152G1 and 63E917172G1) for use in an automated circuit card test and diagnosis system. The circuit card test program should perform Functional Card Testing (FCT) utilizing card edge connectors to stimulate each channel, verifying analog ranges as well as monitoring memory addresses to verify end to end functionality in order to narrow CCA failures down to an ambiguity group of components. In-Circuit Testing (ICT) should be utilized afterwards to determine the exact components that have failed. NSWCPD Code 554 will provide seven “F” condition Analog MUX to be utilized in the creation of the card test program. The contractor shall utilize the program to perform a diagnosis on each of the 7 MUX cards. These seven Analog MUX will serve as a demonstration of successful repair and will be returned to NSWCPD Code 554 for validation of repair upon completion of the test program along with reports containing failed circuits and components, generated from the test program.

2.0 APPLICABLE DOCUMENTS

NA

3.0. REQUIREMENTS

The performer shall develop a functional test routine for the 63E917152G1 and 63E917172G1 Analog MUX CCAs.

The performer shall utilize circuit card edge connections to power and test the 63E917152G1 and 63E917172G1 Analog MUX CCAs.

The functional test routine shall test all circuits and components on the 63E917152G1 and 63E917172G1 Analog MUX CCAs.

The performer shall provide evidence of individual circuit test routines as a deliverable.

The performer shall provide reports of the individual damaged components on each 63E917152G1 Analog MUX CCA as a deliverable.

The performer shall attempt repair on all 7 63E917152G1 Analog MUX CCAs provided by NSWCPD.

The performer shall replace any damaged components on each 63E917152G1 and 63E917172G1 Analog MUX CCAs.

The performer shall repair all 63E917152G1 Analog MUX CCAs provided by NSWCPD which are not deemed damaged beyond repair.

The performer shall provide evidence and reasoning behind determination that any MUX CCA is damaged beyond repair.

The performer shall send all 63E917152G1 Analog MUX CCAs that have been deemed damaged beyond repair back to NSWCPD.

The performer shall provide test results from the functional test routine of each repaired 63E917152G1 Analog MUX CCA as proof of repair.

4.0 DATA REQUIREMENTS

All Contract Data Requirements Lists (CDRLs) identified shall be delivered electronically, unless otherwise stated. While Contractor’s format is acceptable, Government’s approval of the format and content is required. All CDRLs shall reflect both prime and subcontractor data, if applicable, at the same level of detail.

CDRL A001 – Government Property Inventory Report

5.0 SECURITY REQUIREMENTS

5.1 OPERATIONS SECURITY (OPSEC)

5.1.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.1.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.1.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.1.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.2 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.

6.0 PLACE OF PERFORMANCE

All work associated with this SOW shall occur at the vendor’s facility.

7.0 GOVERNMENT FURNISHED PROPERTY

GFP is required for completion of tasks under this SOW. All Government Furnished Property is 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 originating Contracting Officer.. Accountability for Government Property under this task order shall be managed in accordance with FAR Part 45 and DFARS Part 245 as well as the Government Property clauses in the Task Order, regardless of whether the property is Contractor Acquired Property (CAP), GFP, or received directly from another commercial source as a deliverable from a Government issued contract.

Additional Government Property accountability requirements are outlined in the following Directives and Instructions and shall be adhered to as applicable:

· DODI 4161.02, Accountability & Management of Government Contract Property

· DoDM 4140.01, DoD Supply Chain Material Management Procedures: Material Returns, Retention and Disposition

· DODI 5000.64, Accountability & Management of DoD Equipment and Other Accountable Property

· OPNAVINST 4440.26B, Operating Materials & Supplies and Government Furnished Material Management

· SECNAVINST 5200.43A, Property Management

All GFP identified in Attachment “GFP Attachment – Analog MUX” will be provided no later than 30 days after contract award.

7.1 Reporting

The Contractor shall perform reporting functions and actions to maintain an accurate accounting of property. Receipt Reporting: DFARS 252.245-7005 “Management and Reporting of Government Property” requires the Contractor to report receipt of all GFP using the PIEE GFP Module.

7.2 Shipping Notification

FAR 52.245-1 requires the Contractor to report when GFP is returned to the Government. DFARS 252.245-7005 “Management and Reporting of Government Property” requires this notification be in the form of a shipment through the GFP Module in PIEE.

7.3 Inventory Reporting

FAR 52.245-1 requires the Contractor to periodically perform, record, and disclose physical inventory results. While the FAR clause does not define “periodically,” SECNAVINST 5200.43A requires on-hand inventory count reports to support property type specific inventory requirements as set forth in their respective governing instructions. The contractor shall provide an inventory report in accordance with CDRL X. The Government Property Inventory Report outlines the frequency of reporting based on property type per contract needs. If the contractor does not possess any GFP, the Government Property Inventory Report shall reflect no GFP on-hand as required on the reporting schedule.

The Contractor shall provide support within a reasonable time after the Government’s written request to support any Government audit in which GFP, or its related documentation, is requested as part of normal audit processes.

7.4 Lost, Damaged or Stolen GFP Reporting

FAR clause 52.245-1 requires the Contractor to investigate and report to the Government all incidents of property loss as soon as the facts become known. DFARS 252.245-7005 “Management and Reporting of Government Property” further requires the Contractor to report lost, damaged or stolen Government property using the Property Loss functionality within the PIEE GFP Module. The Contractor shall support the Government’s process to assign liability and document loss in support of lost, damaged or stolen GFP.

7.5 Excess Property Reporting

Per FAR 52.245-1, the Contractor shall promptly disclose and report Government property in its possession that is excess to contract performance.

7.6 Property Disposition

Government Property Distribution shall be in line with FAR 52.245-1(j) and DFARS 252.245-7005 “Management and Reporting of Government Property". The contractor shall provide a written notice to the Contracting Officer when property held under this contract has not been used in 100 calendar days. All General Equipment/assets provided as GFP shall be returned to the Government for disposition at the completion of its use unless otherwise directed in writing by the Contacting Officer or the Accountable Property Officer (dependent on who is administering the contract). The Contractor shall complete the plant clearance inventory schedule using the plant clearance capability of the GFP module of the PIEE to generate an electronic equivalent of the SF 1428, Inventory Disposal Schedule.

The contractor shall obtain PCO or plant clearance officer approval (dependent on who is administering the contract) prior to disposal of excess GFP/CAP after the contractor completes the plant clearance inventory schedule.

7.6.2 Issuance of the DD 1149 “Requisition and Invoice/Shipping Document” The contractor must obtain a DD1149 before removing any Government Furnished Property, including Plant, Property, and Equipment (PP&E) from NSWCPD premises for general use. For situations where the contractor picks up/replaces NSWCPD property for maintenance purposes, the contractor shall provide an equipment receipt, showing Manufacturer, Model/Part Number, Serial Number and Asset Number/Barcode, on their company letterhead to the COR. Any and all GFP returned to the Government shall include a DD 1149 to document transfer of liability back to the Government.

7.7 Property Closeout. IAW FAR 52.245-1, the Contractor shall promptly perform and report to the PCO or plant clearance officer (dependent on who is administering the contract) contract property closeout to include reporting, investigating and securing closure of all loss of Government property cases; physically inventorying all property upon termination or completion of this Contract/TO; and disposing of items at the time they are determined to be excess to contractual needs.

7.8 Property Tagging:

The contractor can either tag issued equipment or use the provided NSWCPD Plant property barcodes, or NMCI asset tags. If the contractor chooses to use their own tag, it shall not cover the NSWCPD barcode, or NMCI asset tag. The NSWCPD barcode, and or NMCI asset tag number, when provided shall be used on contractor inventory reports.

8.0 PERIOD OF PERFORMANCE

The period of performance of this contract shall be 3 months from the date of award. The actual dates of the repair/replace services shall be determined after the contract is awarded by the technical point of contact listed below.

9.0 GOVERNMENT TECHNICAL POINT OF CONTACT

Joe Salamone: Code 551, joseph.m.salamone3.civ@us.navy.mil, 445-236-8764 Chris Link: Code 551, christopher.a.link6.civ@us.navy.mil, 445-236-8774 Angela Evans: Code 554, angela.g.evans3.civ@us.navy.mil, 267-965-1603 SOW-PWS Template 06 November 2024 version Page 7