TO 005 SOW_02.06.2025.docx

Statement of Work (SOW) Task Order 005 – Navy / Fincantieri Marine Systems North America (FMSNA) Owners Group & Diesel Working Group Support

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center - Philadelphia Division (NSWCPD) is the 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 Codes 421 and 422 – Diesel Engine Branches, which are responsible for propulsion, ship service and emergency diesel engines within the U.S. Navy Fleet.

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. It does not create employment rights with the U.S. Government whether actual, inherent, or implied. By agreeing to perform the services described in these specifications, the Contractor acknowledges that he/she is not, and shall not become, an employee of the U.S. Government. The Contractor further agrees that he/she shall not bring any cause of action in any forum claiming that he/she has become an employee of the U.S. Government.

1.0.3 The Contractor shall, pursuant to the Government’s right and obligation to inspect, accept, or reject the work, comply with such general direction of the Contracting Officer, or the duly authorized representative of the Contracting Officer as is necessary to ensure accomplishment of the contract objectives.

1.0.4 Government / Contractor Relationship

The services to be delivered under this Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Task Order 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.

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

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

Employee Relationship:

(1) The services to be performed under this Task Order 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.

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

(e) Inapplicability of Employee Benefits: This Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(f) Notice: It is the Contractor's, as well as the Government's, responsibility to monitor Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

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

(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

1.1.1 This task order is in support of an NSWCPD requirement for in person Owners Group meetings and Working Group meetings with FMSNA to discuss and resolve issues pertaining to the FMSNA V1708 engine on the LCS 1 Class application.

1.2 SCOPE OF WORK

1.2.1 The work required in this task order focuses on conducting Navy Owner’s Group (NOG) meetings and Engine Line Working Group meetings to serve as an environment for technical discussion, documentation of action items and continuous improvement with the U.S. Navy’s diesel engine engineering, maintenance and logistics communities.

1.2.2 Action Items typically address the following areas:

· Logistics and provisioning support

· Technical issues seen across the engine line

· Obsolescence adjudication

· Ongoing maintenance issues

1.2.3 Agendas, meeting minutes and an action item register shall be generated and maintained by the Contractor, with input from NSWCPD personnel.

1.2.4 Following Owner’s Group or working group meetings, an update of the action item register shall be provided to NSWCPD by the Contractor, detailing the progress on action items and their status (open/closed).

1.2.5 Working Group meetings shall be coordinated by the Contractor. Action items shall be discussed during the Working Group meetings. The meeting will also discuss issues for all ongoing repair work being accomplished by FMSNA. Meeting agendas, meeting minutes and an action item register shall be generated and maintained by the Contractor, with input from NSWCPD personnel. The agenda action items will remain open until adjudicated, and updates provided at each Working Group meeting.

2.0 APPLICABLE DOCUMENTS

2.1 None.

2.2

3.0 REQUIREMENTS

3.1 Annual Owners Group Meeting

3.1.1 During the task order period of performance, the contractor shall schedule, plan, conduct, administer and otherwise fully execute one (1) FMSNA-Navy Owners Group meeting (NOG). The meeting shall be conducted in the June-September 2025 timeframe in Mayport, FL. The meeting will take place in a conference room on Naval Station Mayport. The conference room will be organized/coordinated by NSWCPD Code 422. The Owners Group meeting shall be planned for a duration of 2 days.

3.1.2 NOG Meeting Preparation

3.1.2.1 In preparation for the NOG meeting, the contractor shall develop and promulgate a meeting announcement, which shall be transmitted via email to an agreed-to distribution list.

3.1.2.2 The meeting announcement shall be distributed no later than 30 days before the scheduled start of the meeting, and shall identify the meeting date and invite participation from the Navy’s LCS 1 Class SSDG diesel engine engineering, maintenance and logistics communities.

3.1.2.3 Following the distribution of the meeting announcement, the contractor shall develop and promulgate a detailed meeting agenda. The agenda shall be distributed via email no later than 15 days before the scheduled start of the meeting.

3.1.3 NOG Meeting Execution

3.1.3.1 The government will host the Owner’s Group meetings at their facilities in Naval Station Mayport.

3.1.3.2 During the meeting, the Contractor shall make available all appropriate technical experts and other applicable personnel (engineering, logistics, parts, field service, etc.) necessary to effectively discuss and address agenda items, topics of concern and other related issues.

3.1.3.3 Action items will be generated based on open discussion from attendees during the meeting.

3.1.3.4 Action items will be assigned to their respective manager or Contractor personnel, as required.

3.1.3.5 Action items which can be addressed and resolved during the meeting will be identified and closed in the action item register.

3.1.3.6 Action items which require further investigation and research from the Contractor, or require updates from Government personnel, will be identified as open in the action item register.

3.1.3.7 Meeting minutes shall be taken by the Contractor, with support of NSWCPD personnel, detailing the progress of the meeting and discussions that occur.

3.1.3.8 At the end of the general meeting proceedings, the contractor shall convene an executive session. The purpose of the executive session is to review meeting notes, review action items (new and existing), and ensure that sufficient information is available to proceed with the development of meeting minutes. Also during the executive session, the action item register shall be updated to reflect the results of the meeting, reviewed and approved during the executive session. The updated post-meeting version of the action item register shall be distributed along with the meeting minutes.

3.1.4 Post-Meeting Support

3.1.4.1 Upon completion of the meeting, the contractor shall work jointly with NSWCPD to finalize and distribute meeting minutes.

3.1.4.2 The Contractor shall distribute meeting minutes via email to all meeting attendees. Final meeting minutes shall be distributed no later than 15 days after the completion of each Owner’s Group meeting.

3.2 Working Group Meetings

3.2.1 To facilitate ongoing communication and technical discussion necessary to effectively adjudicate action items, the contractor shall continue execution of monthly working groups aligned with FMSNA engine and product lines throughout the task order period of performance (12 total).

3.2.2 Meeting Execution

3.2.2.1 Prior to each Working Group meeting, the Contractor shall distribute an agenda via email containing topics to be discussed during the meeting.

3.2.2.2 During the Working Group meetings, the Contractor shall make available all appropriate technical experts and other applicable personnel (logistics, parts, field service, etc.) necessary to effectively discuss and address technical inputs and other related issues.

3.2.2.3 The contractor shall update the action item register to reflect action items closed during Working Group meetings, progress made on in-progress action items during Working Group meetings, and new action items submitted, established and discussed during each Working Group meeting.

3.2.2.4 Meeting minutes shall be taken by the Contractor detailing the progress of the Working Group meetings and discussions that occur.

3.2.3 Post-Meeting Support

3.2.3.1 Upon completion of each Working Group meeting, the contractor shall develop and distribute meeting minutes to all meeting attendees, as well as the task order TPOC and COR. Final meeting minutes shall be distributed no later than 5 days after the completion of each Working Group meeting.

3.2.3.2 Action items submitted for closure shall be in the form of a technical report (CDRL A005). Action item responses shall be written in a clear, concise manner and include the following information:

· Action Item Description

· Background Information

· Discussion of Problem/Issue

· Suggested Solution(s) and/or Resolution(s)

· Recommendation(s), if applicable

4.0 DELIVERABLES

4.1 General

4.1.1 All deliverables submitted during the execution of this task order shall comply with the requirements of applicable Data Item Descriptions (DIDs).

4.1.2 All products, documentation, data files and masters for products/reports etc. developed and submitted in support of the requirements established in this SOW are the property of the Government and shall be turned over to NSWCPD upon request or at the completion of the order. Deliverables shall be developed and submitted in accordance with the Contract Data Requirements Lists (CDRLs) and the specific requirements of each Task Order. Both electronic and hard copy deliverables may be required. Work products shall be submitted in media (e.g., DOC, XLS, PDF, etc.) as mutually agreed upon prior to submission. Unless otherwise specified, deliverable products may be in contractor format.

4.2 Deliverable Acceptance Criteria

4.2.1 Final inspection and acceptance of all work, reports, and other deliverables will be performed by the Government Subject Matter Expert (SME) at the place of delivery. General quality measures, as set forth below, will be applied to each work product delivered under this statement of work:

· Accuracy - Deliverables shall be accurate in presentation, technical content, and adherence to accepted elements of style.

· Clarity – Deliverables shall be clear and concise. Any/all diagrams/text shall be easy to understand and be relevant to the supporting narrative.

· Consistency to Requirements - All deliverables must satisfy the general requirements of this statement of work as well as the specific requirements of each Task Order.

· File Editing - All electronic text and diagrammatic files shall be editable by the Government unless otherwise agreed.

· Timeliness - Deliverables shall be submitted on or before the due date specified by the Government.

4.3 Monthly Progress, Status and Management Reports (CDRL A001)

4.3.1 The contractor shall provide a monthly progress report, which shall detail the work performed during each reporting period together with significant results thereof. This report will describe any problems encountered and propose solutions for their resolution. The report shall further provide the current technical, management and administrative status of the efforts, and contain a brief outline of the work envisioned for the ensuing reporting period. Informal appendices shall be included as necessary or required in the scope of work. At a minimum, an updated version of the Action Item Register shall be submitted as an appendix to each monthly report. Submission of the report shall be done via electronic mail to the Contracting Officer’s Representative (COR) and designated Technical Point of Contact (TPOC).

5.0 SECURITY REQUIREMENTS

5.1 The Contractor shall comply with the security requirements of the Basic Contract.

5.2 In addition to the security requirements called out in the basic contract, the contractor shall comply with the following additional security requirements:

5.2.1 Operations Security (OPSEC)

· The Contractor shall protect critical information associated with this order 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 order requires the Contractor to adhere to OPSEC requirements. The Contractor may not impose OPSEC requirements on its sub-contractors unless NSWCPD approves the OPSEC requirements. During the period of performance of this order, 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).

· Controlled Unclassified Information (CUI) correspondence transmitted internally on the Contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting 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.

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

· 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.1). Questions concerning these requirements shall be directed to the PCO, and the COR who will forward the request to the NSWC PD Security Division (Code 105.1).

5.2.2 Receipt, Storage and Generation of Controlled Unclassified Information (CUI)

· All Controlled Unclassified Information (CUI) associated with this order 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

6.1 The primary place of performance shall be at the Contractor’s facility.

7.0 TRAVEL

7.1 This task order is being awarded on a firm-fixed price basis to support continuation of FMSNA/Navy Owners Group efforts, including execution of Owners Group meetings, execution of working group meetings, and adjudication, response and closure of action items. As result, the contractor shall include in their proposal all costs associated with travel necessary to attend Owners Group meeting in person.

8.0 MATERIAL AND GOVERNMENT FURNISHED MATERIAL/EQUIPMENT

8.1 Not applicable for this task order.

9.0 LEVEL OF EFFORT

9.1 This task order is being awarded on a firm-fixed price basis. As a result, the contractor shall include in their cost proposal the necessary level of effort to complete all elements of this task order within the established period of performance.

10.0 DELIVERY ORDER PERIOD OF PERFORMANCE

10.1 The period of performance for this task order is twelve (12) months from time of award.

11.0 SPECIAL REQUIREMENTS

11.1 Not applicable.

12.0 TECHNICAL POINT OF CONTACT (TPOC)

12.1 The TPOC for this delivery order is Stephen Kovacs, NSWCPD Code 421. Mr. Kovacs can be contacted at Stephen.N.Kovacs.civ@us.navy.mil or (856) 904-2587.

13.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

13.1 The COR for this task order will be Lauren Markey, NSWCPD Code 4021, Philadelphia, PA. Ms. Markey can be contacted at lauren.v.markey.civ@us.navy.mil or (215) 704-8801.