TO 006 SOW_12.05.2025.docx

Statement of Work (SOW) Task Order 006 – Exhaust System Piping Structural Analysis & Improvement Engineering Plan

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 a NSWCPD requirement for the development of a detailed engineering plan for the improvement of the exhaust piping and below configuration, which was initially explored under Task Order 001, Technical Input 004, “Exhaust Duct Leak Solution”.

1.2 SCOPE OF WORK

1.2.1 Using Systems Engineering processes and principles, defined in Reference Document 2.1, the contractor will design, develop and model the improvement to exhaust piping and bellow configuration as previously outlined in the Task Order 001, Technical Input 004 deliverable. The existing model shall also be reviewed to include modeling and analysis to use as baseline comparison for improved design.

1.2.2 In doing so, the contractor will apply the Systems Engineering Process (SEP) model (requirements analysis, functional analysis & allocation, design synthesis and verification) in a spiral manner across the stages of the SEP to produce documents, diagrams, models and products of increasing detail as the process flows from concept development to engineering development.

1.2.3 The goal of this task order is to complete Phase I of the SEP, and to validate that the developed components have achieved Technical Readiness Level (TRL) 5 – technology validated in a relevant environment.

1.2.4 The following system requirements have been established:

· The new engine exhaust system design/configuration shall provide quantifiable and verifiable improvements in reducing documented ship class exhaust leaks

· Any engine exhaust piping design improvements shall maintain existing configuration properties including:

· Temperature and pressure requirements

· Material selection

· Deflection requirements

· Shock and vibration requirements IAW MIL-S-901D

· Utilize, to the maximum-extent possible, the existing exhaust system components, piping and bellows configuration.

· Analysis shall be accomplished with engine rigid mount configuration.

1.2.5 The development and validation of this upgrade has been broken into the following phases:

· Phase I: Design, Analysis, Testing & Evaluation

· Phase II: Pilot Deployment

· Phase III: Engineering Release

This task order focuses on Phase I – Design, Analysis, Testing & Evaluation.

1.2.6 In the Concept Development stage, the contractor will:

· Focus on building a concept to satisfy operational needs

· Establish the system need(s)

· Leverage existing designs from other engine exhaust piping bellows configurations

· Translate operational needs into a feasible concept

· Translate customer system requirements into system operational requirements

· Translate system operational requirements into performance requirements

· Translate system performance requirements into system functional specification(s)

· Identify failure points and/or exhaust leaks on current exhaust engine configuration

· Develop a defined system concept and functional baseline

· Conduct a system design review (SDR) to validate the defined system concept and established functional baseline

1.2.7 In the Engineering Development stage, the contractor will:

· Engineer the system to perform the designated functions

· Translate system functional specification(s) into system design specifications

· Translate the defined system concept into an engineered prototype

· Integrate components, sub-assemblies and sub-systems into a functional system of systems

· Conduct preliminary design efforts to develop system architecture, define interface requirements and establish the allocated baseline of the system

a) Any design improvements shall also be compared to Gibbs & Cox design study of current configuration (Reference Document 2.2).

· Conduct a preliminary design review (PDR) to ensure the preliminary design and system architecture are complete, and there is technical confidence the capability need can be satisfied within cost and schedule goals. The PDR also validates the system’s allocated baseline.

· Develop system test & evaluation master plan (TEMP).

· Conduct detailed system design to further develop the system and establish the product baseline.

1.2.8 In the Testing & Evaluation stage, the contractor will:

· Conduct system testing & analysis via computer-aided design and FEA modeling.

· Evaluate thermal growth from expansion and contraction and accounted for in the installation process and final design.

· Evaluate the weight and forces of the exhaust piping and bellows and isolate ship side exhaust piping from engine-mounted exhaust trunk.

· Evaluate the engine exhaust system sealing ring and gasket effectiveness.

· Validate fitment of exhaust piping design improvements and bellows configuration analytically for each SSDG configuration.

· Assessment of space constraints for each engine position (e.g. NR1 SSDG, NR2 SSDG, etc).

· Conduct a critical design review (CDR) to ensure the system, as designed, modeled, and tested, meets all established and derived system requirements and is ready to proceed into Phase II – Pilot Deployment.

1.2.9 Key Milestones:

· Concept development, establishment of functional system baseline & SDR

· Preliminary design, establishment of allocated system baseline & PDR

· Detailed design

· FEA analysis & validation

· General Fitment validation analysis of exhaust piping design improvements and bellows configuration.

· Establishment of the product baseline & CDR

1.2.10 Expected Key Benefits:

· Minimized frequency of engine exhaust system leaks

· Reduced stress and wear on exhaust components and sealing surfaces

1.2.11 Systems Engineering Definitions:

· Functional baseline – describes the system functional specifications as they are derived from system performance requirements during the concept development stage. The functional baseline is sometimes referred to as the system specification, and is established during the concept development stage.

· Allocated baseline – describes the functional and interface characteristics for all system elements and the verification required to demonstrate achievement of those specified characteristics. The allocated baseline is sometimes referred to as the end item design-to specification, and is established during the preliminary design phase of the engineering development stage.

· Product baseline – describes the physical system and consists of the documentation describing all of the necessary functional and physical characteristics of the system, the selected functional and physical characteristics designated for the prototype build, and the tests necessary to validate that the system meets all established and derived requirements. The product baseline is sometimes referred to as the end item build-to specification, and is established during the detailed design phase of the engineering development stage.

2.0 REFERENCE DOCUMENTS

2.1 DoD Systems Engineering Guidebook, February 2022

2.2 LMM Gibbs & Cox Document # 15102304 “Ship Service Diesel Generator Exhaust Gas Joint Shock Data Package”.

3.0 REQUIREMENTS

3.1 The contractor shall develop, maintain, and submit a project plan that demonstrates the contractor’s understanding of the task order requirements and establishes critical and measurable task milestones. The project plan shall also include the requisite tasks and sub-tasks that connect the project milestones, and the predecessor/successor relationship of each task and sub-task, such that a clear path to task completion is represented. The contractor shall attach a completion percentage to each task and sub-task, and the percentage complete for each task shall roll up to the milestone and overall project levels, such that a clear and supportable completion percentage is reflected at the task order, milestone and task/sub-task levels. First submittal of the project plan shall be no later than two weeks after task order award, and subsequent submittals shall be made in conjunction with each monthly status meeting.

3.2 In support of these efforts, the contractor shall schedule and conduct monthly status meetings. During these status meetings, the contractor shall discuss progress made since the previous meeting, work anticipated to be completed in the ensuing period, problem areas encountered and other topics relevant to the execution of this task order. The contractor shall submit via email the monthly status report and an updated project plan at least one day prior to each meeting and shall develop and submit meeting minutes (via email) upon completion of each meeting. Meeting minutes shall be submitted no later than three business days after each monthly meeting.

3.3 Concept Development Stage:

3.3.1 Using systems engineering processes, principles and methods described in Reference Document 2.1, the contractor shall develop a defined system concept and functional baseline for the updated engine exhaust piping and bellows configuration. The customer requirements indicated in Section 1.2.4 of this SOW shall govern the contractor’s system definition and functional baseline establishment efforts. In doing so, the contractor shall:

· Translate operational needs into a feasible system concept

· Translate customer system requirements into system operational requirements

· Translate system operational requirements into performance requirements

· Translate system performance requirements into system functional specification(s)

3.3.2 Once the system concept has been defined, the contractor shall conduct a system design review (SDR) to evaluate the manner in which the system’s requirements have been allocated to configuration items and the engineering process that produced the allocation(s). For the SDR, the contractor shall establish entry criteria based on the documents, drawings, diagrams, analyses, and other artifacts developed during the concept development stage. Additionally, the contractor shall establish exit criteria based on validating the system’s functional baseline.

3.4 Engineering Development Stage:

3.4.1 Using systems engineering processes, principles and methods described in Reference Document 2.1, the contractor shall conduct preliminary system design efforts to develop system architecture, identify system components, sub-assemblies and sub-systems, define interface requirements and establish the allocated baseline of the system. In doing so, the contractor shall:

· Engineer the system to perform the designated functions

· Translate system functional specification(s) into system design specifications

· Translate the defined system concept into a validated development model

· Translate the system’s functional baseline into the allocated baseline

· Develop a test & evaluation plan

· Develop the necessary drawings, diagrams, documents and other artifacts that demonstrate the system’s allocated baseline has been developed

3.4.2 Once the contractor has developed a validated system development model and has developed the system’s allocated baseline, the contractor shall conduct a system preliminary design review (PDR) to:

· Ensure that all system requirements have been validated, allocated, the requirements are complete and the flow-down is adequate to verify system performance

· Show that the proposed design is expected to meet the functional and performance requirements

· Demonstrate sufficient design maturity in the proposed design approach to proceed to the detailed design phase

· Demonstrate that the design is verifiable

3.4.3 For the PDR, the contractor shall establish entry criteria based on the documents, drawings, diagrams, analyses and other artifacts developed during the preliminary design phase of the engineering development stage. Additionally, the contractor shall establish exit criteria based on validating the system’s allocated baseline.

3.4.4 Following completion of the PDR and successful achievement of the established exit criteria, the contractor shall proceed to the detailed design phase of the project, wherein the following will be accomplished:

· Design synthesis to translate the system design specifications into system build specifications

· Design synthesis to translate the allocated baseline into the product baseline

· Design synthesis to transform the validated development model into an engineered prototype system

· Develop computer-aided design/finite element analysis (CAD/FEA) models of the improved SSDG engine exhaust piping and bellow configuration.

· Conduct CAD/FEA evaluation of system components to validate system/customer requirements, including shock/vibration specification compliance.

· Develop the necessary drawings, diagrams, documents and other artifacts that demonstrate the system’s product baseline has been developed

3.5 Testing & Evaluation Stage

3.5.1 For the purposes of this task order, testing & evaluation shall consist of the fitment validation analytically based on identified space constraints for each engine configuration.

3.5.2 The contractor shall ensure the updated piping and bellows configuration:

· Do not have any significant shipboard interference that would require major ship system modifications

· Is structurally feasible given layout of space and appropriate support for added mounting points

3.5.3 Following successful completion of all system T&E, the contractor shall conduct a critical design review (CDR) to ensure that the system has met all established system requirements via testing and validation, and can proceed to Phase II of the project – Pilot Deployment. The objectives of the CDR are to:

· Ensure that the system product baseline has been established

· Demonstrate that the proposed design can and has met all established system requirements

· Demonstrate sufficient design and configuration maturity to allow the system to proceed to pilot deployment, i.e. TRL 6.

3.5.4 For the CDR, the contractor shall establish entry criteria based on the documents, drawings, diagrams, analyses and other artifacts developed during the engineering development and T&E stages. Additionally, the contractor shall establish exit criteria based on validating the system’s product baseline.

3.6 Phase I Final Report

3.6.1 Upon completion of the above Phase I efforts, the contractor shall develop and submit a Phase I Final Report, which shall include the following:

· Evaluation, analysis, and conclusion of detailed design & analysis data

· Full system Bill of Material

· Shock & Vibration qualification assessment

· Installation Procedure to include proper bellows/exhaust piping targeting requirements

· Official Engineering Change Proposal issued by the OEM

3.7 Material Turn Over

3.7.1 N/A

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 prepare and 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 and financial status of the efforts and contain a brief outline of the work envisioned for the ensuing reporting period. The contractor shall also include in the monthly status report an updated version of the task order project plan. Informal appendices may be included as necessary to enhance status reporting. Submission of the report shall be done via electronic mail to the Contracting Officer’s Representative (COR) and designated Technical Point of Contact (TPOC). This deliverable shall be submitted at least one business day prior to each regularly scheduled monthly status meeting.

4.4 Project Planning Chart (CDRL A004)

4.4.1 The contractor shall develop and submit a project plan as detailed in Section 3.1 of this SOW. First submittal of the project plan shall be no later than two weeks after task order award, and subsequent submittals shall be made in conjunction with each monthly status meeting.

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 The contractor shall develop and deliver SDR entry/exit criteria as described in Section 3.3.2 of this SOW.

4.5.3 The contractor shall develop and deliver PDR entry/exit criteria as described in Section 3.4.2 of this SOW.

4.5.4 The contractor shall develop and deliver CDR entry/exit criteria as described in Section 3.5.2 of this SOW.

4.5.5 The contractor shall develop and deliver the Phase I Final Report as described in Section 3.6.1 of this SOW. The contractor shall allow for up to three submit/review/adjudicate/resubmit cycles for the final acceptance of the Phase I final report.

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

7.0 TRAVEL

7.1 This task order is being awarded on a firm-fixed price basis to support the development of design improvements to the LCS 1 Class SSDG exhaust system. As a result, the contractor shall include in their proposal all costs associated with travel 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.

9.0 LEVEL OF EFFORT

9.1 This task order is being awarded on a firm-fixed price basis to support the development of design improvements to the LCS 1 Class SSDG exhaust system . 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 Frank Tiesi, NSWCPD Code 422. Mr. Tiesi can be reached at Frank.V.Tiesi.civ@us.navy.mil or (445) 232-1261.

13.0 SUBJECT MATTER EXPERT (SME)

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

14.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

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