TO 007 SOW_12.17.2025.docx

Statement of Work (SOW) Task Order #007 – FMS LCS Working Group #4

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 Code 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

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

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

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

d) 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:

1.1 BACKGROUND

1.1.1 This task order is in support of an NSWCPD requirement for Engine Line Working Group meetings with FMS to discuss and resolve issues pertaining to the Isotta-Fraschini 1708C2ME8 engine line within the Littoral Combat Ship (LCS) Class Freedom Variant.

1.2 SCOPE OF WORK

1.2.1 The work required in this task order focuses on conducting twenty-four (24) total formal LCS Working Group meetings to serve as an environment for technical discussion and documentation of Technical Inputs created by the U.S. Navy’s diesel engine engineering and maintenance communities.

1.2.2 There will be 2 different LCS Working Groups:

1.2.2.1 LCS Technical Working Group

· There will be twelve (12) monthly meetings

· Will include discussion on Technical Inputs as described in Section 2.0

1.2.2.2 LCS Provisioning Working Group

· There will be twelve (12) monthly meetings

1.2.3 Action Items are Technical Inputs which address the following areas:

· Development and upkeep of technical documentation

· Logistics, supply, maintenance, overhauls and provisioning support

· Technical issues seen across the various engine lines

· Projects which are in development or are planned

1.2.4 Meeting minutes, an Action Item Register, and pre-meeting Agenda shall be generated and maintained by the Contractor, with input from NSWCPD personnel.

1.2.4 Working Group meetings shall include discussion on:

· Action Items as described in 1.2.2

· Open Technical Discussion

2.0 APPLICABLE DOCUMENTS

2.1 Enclosure 1 – Technical Input 01 – Engine Exhaust System Maintenance Standard

2.2 Enclosure 2 – Technical Input 02 – Existing Maintenance Standard Revisions

2.3 Enclosure 3 – Technical Input 03 – Seawater and Fuel Oil Flex Hose Upgrade

2.4 Enclosure 4 – Technical Input 04 – Replacement Parts Provisioning Maintenance

2.5 Enclosure 5 – Technical Input 05 - WIF Sensor – Fuel Quality Improvement

2.6 Enclosure 6 – Technical Input 06 – Protype Nova Swiss Fuel Line Condition Analysis

3.0 REQUIREMENTS

3.1 LCS Working Group (WG) Meetings

3.1.1 During the task order period of performance, the contractor shall schedule, plan, host, conduct, administer and otherwise fully execute formal FMS-LCS Working Group meetings (LCS-WGs). The meetings shall be scheduled to occur monthly, and shall be planned for a duration of one (1) hour each. Meetings should be conducted via Microsoft Teams or another agreed upon medium during scheduling of meeting.

3.1.2 LCS WG Meeting Preparation

3.1.2.1 In preparation for each meeting, the contractor shall develop and promulgate meeting announcements, deliverables from previous meeting (updated Action Item Register and Meeting Minutes) and a meeting agenda, which shall be transmitted via email to an agreed-to distribution list. The agenda for each meeting shall be distributed via email no later than one (1) day before the scheduled start of each meeting.

3.1.2.2 Action Item Register shall include all TIs and provide status updates on progress of each TI after each meeting. The Contractor shall clearly identify and label each Action Item with a number in sequential order as submitted by Government (e.g. 2025-001 for the first Technical Input submitted in calendar year 2025).

3.1.3 LCS WG Meeting Execution

3.1.3.1 The Contractor shall conduct the meeting via Microsoft Teams unless an alternate meeting location or medium is bilaterally established.

3.1.3.2 During the meetings, the Contractor shall make available all appropriate engine line technical experts and other applicable personnel (engineering, logistics, parts, field service, etc.) necessary to effectively discuss and address Action Items and other related issues.

3.1.3.3 Items to be discussed during Working Group Meetings will include:

· Contractor progress on Action Items as defined in 1.2.3.

· Ongoing LCS Class IFM 1708C2ME8 technical issues.

· Ongoing LCS Class IFM 1708C2ME8 provisioning issues.

3.1.4 Post-Meeting Support

3.1.4.1 Upon completion of each meeting, the contractor shall review meeting minutes with NSWCPD and distribute finalized 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 one (1) day after the completion of each Working’s Group meeting.

3.2 Technical Inputs

3.2.1 The following Technical Inputs have been attached to this Task Order as Enclosures:

· Technical Input 01 – Engine Exhaust System Maintenance Standard

· Technical Input 02 – Existing Maintenance Standard Revisions

· Technical Input 03 – Fuel Line Routing Upgrade

· Technical Input 04 – Replacement Parts Provisioning Maintenance

· Technical Input 05 - WIF Sensor – Fuel Quality Improvement

· Technical Input 06 – Prototype Nova Swiss Fuel Line Condition Analysis

3.2.2 In between meetings, the contractor shall address and adjudicate all open Technical Inputs in a manner so as to affect their closure as quickly as possible. Technical Inputs submitted for closure shall be in the form of a technical report (CDRL A005) and shall include the following information

· Technical Input Description

· Background Information

· Discussion of Problem/Issue

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

· Recommendation(s), if applicable

3.2.3 Technical Inputs will be assigned to their respective engine line manager or Contractor personnel, as required.

3.3 General

3.3.1 The contractor shall provide services, personnel, facilities, expertise, technical information, special tools, supplies and incidental materials necessary to execute the performance requirements specified in this statement of work and enclosed technical instructions.

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 to support 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 Technical Input Tracker 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).

4.4 Trip Reports (CDRL A002)

4.4.1 The contractor shall develop and submit a trip report for each trip or travel occurrence conducted in support of this task order. Trip reports shall include sufficient information from the trip or travel occurrence as is necessary to effectively communicate the details and results from the travel conducted. At a minimum, each trip report shall include the following information:

· Trip Purpose

· Place(s) visited

· Contractor personnel making trip

· Personnel contacted

· Travel dates

· Background

· As-found conditions & Observations

· Actions Taken

· Conclusions & recommendations

4.5 Technical Reports (CDRL A005)

4.5.1 All other deliverables submitted as part of this task order shall be submitted as technical reports. The format of each technical report deliverable shall be mutually agreed to prior to first submission. Each technical report shall contain a cover letter describing the contents of the deliverable, and shall contain a unique identifier which references the task order number, unique deliverable serial number, date of submission and revision (if applicable).

4.5.2 Technical Input / Action Item responses shall be delivered as technical reports (CDRL A005). Action item responses shall be written in a clear, concise manner and provide detailed descriptions and/or status updates to the following:

· Action Item Description

· Background Information

· Discussion of Problem/Issue

· Suggested Solution(s) with supporting information/documentation

· Recommendation(s), if applicable

· Closure recommendation with rationale

5.0 SECURITY REQUIREMENTS

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

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 the Navy/FMS Working Group process. As result, the contractor shall include in their proposal all costs associated with travel (if any) necessary to complete all elements of this task order within the established period of performance.

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 to support the Navy/FMS Working Group process . 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 delivery 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. Ms. Markey can be contacted at Lauren.V.Markey.civ@us.navy.mil or (215) 704-8801.

Technical Input 1 Engine Exhaust System Maintenance Standard

BACKGROUND:

In support of the Diesel Maintenance Strategy (DMS) program, the LCS 1 Variant Ship Service Diesel Generators (SSDG) require the development of Maintenance Standards (MS) for multiple subsystems of the diesel generators. This technical input requests development of a maintenance standard to explain how to remove, inspect and install the components of the exhaust system, including:

· Exhaust manifolds

· Exhaust duct/flower pot

· Exhaust manifold connection points

· Exhaust turbocharger removal/replacement

· Exhaust system sealing rings and sleeves

· Exhaust system targeting/alignment to shipside exhaust ducting

TECHNICAL ISSUE:

There is no current MS developed for the LCS 1 Variant SSDGs that will provide an industry and government agreed upon standard with detailed procedures and appropriate check points. These maintenance standards will also include the establishment of parts kits that can be provisioned and ordered for the specific maintenance.

REQUESTED DELIVERABLE ACTION BY FMS:

1. Provide a MS for inclusion into a larger MS Handbook that includes procedural steps for the removal, inspection, and installation of the V1708 exhaust system components, piping and software.

2. Procedures shall be developed into a Navy MS Handbook format:

· Shall include both photographs and graphics for exploded views and additional detail.

· May use existing sections of the TM from MCM-class ships if applicable to LCS Class.

· QA Data sheets to be provided for each MS.

3. Develop a complete Replacement Parts Kit (RPK) required to accomplish tasks listed above. These parts may include consumable parts, seals, and parts considered by the Contractor to be standard replacement parts for the overhaul of the assembly.

4. The contractor shall perform technical review prior to each submittal to government.

5. The contractor shall allow three submit/review/revise/resubmit cycles for these maintenance standards.

6. Additional formatting guidance:

· Table of contents: each maintenance standard shall include a table of contents that provides description of each section – each table of contents shall be consistent between maintenance standards.

· Torque Table: A torque table shall be provided for all applicable fasteners. The table is to include tool size, fastener identification and torque specification (noting dry or wet threads). Torques shall be consistent with OEM published documentation.

· Tool List: Standard tools shall be listed out to detail type and size (if applicable) of tool. Special tools shall be listed out separately with a part number that can be used to procure. Request note be added if a non-special alternative tool is available.

· Referencing other procedures: The intent of the maintenance standard is to be a standalone document. References to other external procedures shall be avoided.

NOTE: each maintenance standard may have unique details that may not follow these guidelines. Any issues will be discussed and resolved during our biweekly working group meetings.

· Figure/Table Sequencing: Numbering of figures/tables shall be maintained in sequence. Referenced figures shall be shown on the same page as procedural step(s).

· QA Section 10 formatting: Detailed figures shall be shown where applicable. Section 10 QA figures/tables shall be displayed in sequence with respect to MS procedure.

Technical Input 2 Existing Maintenance Standard Revisions

In support of the Diesel Maintenance Strategy (DMS) program, the LCS 1 Variant Ship Service Diesel Generators (SSDG) require the development of Maintenance Standards (MS) for multiple subsystems of the diesel generators. This technical input requests revision of existing maintenance standards including:

· Fuel Injector

· Intercooler

· Cylinder Head

· Jacket Water Cooler

REFERENCE

Final revisions of Maintenance Standards from Task Order 002, Technical Input 02:

· Fuel Injector

· Intercooler

· Cylinder Head

· Jacket Water Cooler

There are existing MS developed for the LCS 1 Variant SSDGs that provide an industry and government agreed upon standard with detailed procedures and appropriate check points. The existing maintenance standards shown in the background require technical and editorial revision after lessons learned and improved contractor graphics capabilities from maintenance standards developed on Task Order 003, Technical Inputs 02 and 03.

1. Provide revised MS for inclusion into a larger MS Handbook

2. Revised procedures shall be developed into a Navy MS Handbook format:

· Shall include improved photographs and graphics from existing procedures with exploded views and additional detail.

· Update QA Data sheets (if necessary) to be provided for each MS.

3. Revise, as necessary, the existing complete Replacement Parts Kit (RPK) required to accomplish tasks listed above. These parts may include consumable parts, seals, and parts considered by the Contractor to be standard replacement parts for the overhaul of the assembly.

4. The contractor shall perform technical review prior to each submittal to government.

5. The contractor shall allow two submit/review/revise/resubmit cycles for these maintenance standards.

6. Additional formatting guidance:

· Table of contents: each maintenance standard shall include a table of contents that provides description of each section – each table of contents shall be consistent between maintenance standards.

· Torque Table: A torque table shall be provided for all applicable fasteners. The table is to include tool size, fastener identification and torque specification (noting dry or wet threads). Torques shall be consistent with OEM published documentation.

· Tool List: Standard tools shall be listed out to detail type and size (if applicable) of tool. Special tools shall be listed out separately with a part number that can be used to procure. Request note be added if a non-special alternative tool is available.

· Referencing other procedures: The intent of the maintenance standard is to be a standalone document. References to other external procedures shall be avoided.

NOTE: each maintenance standard may have unique details that may not follow these guidelines. Any issues will be discussed and resolved during our biweekly working group meetings.

· Figure/Table Sequencing: Numbering of figures/tables shall be maintained in sequence. Referenced figures shall be shown on the same page as procedural step(s).

· QA Section 10 formatting: Detailed figures shall be shown where applicable. Section 10 QA figures/tables shall be displayed in sequence with respect to MS procedure.

Technical Input 3 Seawater and Fuel Flex Hose Upgrade

There are frequent failures of the flex hoses on both the seawater and fuel systems. These hoses join components on the engine to components on the engine skid. Due to the new rigid mount configuration, flex hoses are no longer required as movement between the engine and the skid is no longer possible.

This technical input (TI) is to evaluate the feasibility of replacing the existing seawater and fuel flex hoses, IFM part numbers identified below, with rigid piping configuration. The existing connection points on the engine and the skid shall not be altered.

SW Hoses: 00I33400A, 00E23600 FO Hoses (x4): 00F14700A

1. Evaluate feasibility of replacing seawater and fuel flex lines with rigid piping.

a) Provide the problem statement

b) Preliminary design (CAD layout)

c) Final design (detailed drawings)

d) Develop Test & Evaluation Plan

e) Procure two sets of components for fitment test

f) Conduct fitment test

g) Provide final report of completed testing

2. Provide official IFM Engineering Change Plan (ECP).

3. Revised pages in spare parts catalog

Technical Input 4 8000-hour Maintenance Replacement Parts & Provisioning

There is a need to update the replacement parts and provisioning data for the SSDGs to meet US Navy Fleet requirements for lifecycle maintenance.

This technical input (TI) is to investigate and resolve provisioning problems that result in unavailability of replacements parts.

1. FMS will provide engineering labor concerning the unavailability of spare parts as follows:

a) Specify provisioning data for parts supersessions

b) Develop all-inclusive parts kits for the following tasks:

i. 8000-hour Top-End Overhaul Kit

1. Overhaul kit shall include all components required to complete all 8000-hour maintenance tasking.

2. Provide “sub-kits” for all tasks required as part of an 8000-hour maintenance (e.g. cylinder heads)

c) Kit and sub-kits shall include drawings and pricing to allow Navy to provision and create NSNs. Deliverables to include:

i. Illustrated parts breakdown drawing on IFM/FMS letterhead or with stamping.

ii. Bill of material/parts list to include kit part number and part numbers & quantities of each individual item in the kit

iii. Quote/cost estimate to include the cost of the kit as well as the cost of each individual item within the kit

2. Update the FMS Spare Parts Manual resulting from changes described above.

Technical Input 5 WIF Sensor – Fuel Quality Improvement

Fuel quality has always been a priority with the US Navy fleet. Water-contaminated fuel has been commonly identified and causes significant degradation to engine components. The current fuel contamination sensor is limited to seawater detection. It cannot detect any non-salinated (fresh) water from the fuel tanks. Such water contamination poses a very high risk to damage the fuel system components. This problem has been most evident by a high rate of fuel metering valve failures observed on the LCS fleet.

This technical input (TI) replaces the existing water in fuel sensor with a different one capable of detecting fresh water. Deliverables to include test and evaluation and to provide NSWCPD an official OEM Engineering Change Proposal (ECP).

Develop a preliminary design to prevent water contamination of the V1708 fuel system components.

1. Analysis of alternatives of WIF Sensors

2. Test and Evaluation Plan of WIF Sensor solution

3. Lifecycle maintenance plan for sensors

4. Two sets of components to be procured for lab testing (contractor furnished)

a) Material to be turned over to Navy after testing

5. Final report of completed testing

6. FMS to provide appendix with all relevant technical documentation with configuration changes (sensor list, sensor technical characteristics to update technical manuals

7. ECP preparation and submission

Technical Input 6 Protype Nova Swiss Fuel Line Condition Analysis

The current design of the high-pressure fuel lines being used on the LCS Freedom class SSDGs has a usable life of three torque cycles. To reduce costs to the navy, NSWCPD has been working with the contractor via Task Order (TO) 002, Technical Input (TI) 005 to develop fuel lines that have an increased number of allowable torque cycles with a minimum of 10 being the target. TO 003, TI 001 tested the prototype fuel lines developed in TO 002, TI 005 on both a test engine and aboard an LCS1VAR ship to prove out the new design.

TECHNICAL ISSUE:

This technical input (TI) provides an analysis of the fuel lines developed in TO 002, TI 005 after being tested onboard USS Minneapolis St Paul (LCS 21) ship via TO 003, TI 001. The analysis will provide data to determine the final condition of the fuel lines after the operational test. The results will aid in the acceptance or redesign of the prototype fuel lines.

REQUESTED DELIVERABLE ACTION BY FMS:

Perform a laboratory analysis of the prototype fuel lines that were operationally tested on board USS Minneapolis/St Paul from TO 003, TI 001:

1. Contractor to mark each single fuel line installed with its associate ship name and number, engine serial number, and cylinder position.

2. Contractor to preserve prototype fuel lines and package them for shipping to ensure fuel line condition is not altered during shipment.

3. Contractor to ship prototype fuel lines to subcontractor Nova Swiss, in Switzerland.

4. Subcontractor Nova Swiss will analyze prototype fuel lines condition along with other information collected from TO 003, TI 001 to verify fuel lines can meet a minimum of 10 torque cycles per usable life as directed in TO 002, TI 005.

5. Subcontractor Nova Swiss to discard fuel lines after testing/analysis.

6. Subcontractor Nova Swiss to release a final report to subcontractor IFM justifying the acceptance of the prototype as the design or provide modification requirements and the justification for the requirements

7. Subcontractor IFM to evaluate the final report.

8. FMS to release official report from Nova Swiss / IFM final to US Navy

9. IFM / Nova Swiss to release production schedule with new fuel line delivery times