TO 001 SOW_03.03.2021.docx

DOCX document 40 KB Posted

Attached to
US Navy Submarine EDG Global Repair Services
Solicitation number
21-AJP-011
Issued by

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Statement of Work (SOW) SSBN 735 Emergency Diesel Generator (EDG) Repair

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 Branch, which is responsible for diesel engines within the U.S. Navy Fleet, including the SSBN 726 ship class.

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

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.

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.

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.

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.

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.

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:

Confirm the conduct is in violation and when necessary direct the mode of further performance, Countermand any communication regarded as a violation, Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or 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 USS Pennsylvania (SSBN 735) Emergency Diesel Generator (EDG) suffered failure of the number fourteen Lower Main Bearing (LMB).

1.1.2 Following is a summary of findings from the post-casualty Diesel Engine Inspection conducted by Trident Refit Facility-Bangor (TRF-B) DEI:

· Number 14 LMB severely wiped with evidence of heat build-up.

· Number 14 LMB cap distorted with close-in and taper, also heat discoloration.

· Lower crankshaft number 14 main bearing journal scoring and groove that could not be removed by polishing.

· Lower crankshaft number 14 main bearing journal 0.004-0.006 in below new specification and tapered 0.002-0.004 in.

· Lower crankshaft number 14 main bearing journal approximately 0.020 in diametrical clearance to new main bearing.

· Number 13 LMB severely wiped with axial crack on bottom bearing surface and wiping of thrust face and opposite thrust face of bearing.

· Number 13 LMB cap distorted with close-in and taper.

· Number 13 LMB saddle tapered.

· Lower crankshaft number 13 main bearing journal heavy aluminum transfer to journal and thrust surfaces.

· Runout of coupling drive plate 0.0045 in, runout of driven plate 0.003 in, runout of rotor shaft flange 0.0055 in, axial runout of driven plate face 0.007 in.

1.2 SCOPE OF WORK

1.2.1 The scope of work for this Task Order is:

· Complete dimensional, mandrel, and optical alignment inspection of the lower crankline.

· Repair number 11, 12, 13 and 14 LMB saddles.

· Replace number 11, 12, 13 and 14 LMB caps.

· Inspect generator rotor shaft for straightness.

· Assemble new crankshaft and coupling to include machining of crankshaft to vertical drive ring gear, crankshaft to coupling, and coupling to generator rotor.

· Provide technical oversight for engine assembly, crankshaft replacement, generator flexible coupling installation, and generator alignment.

REFERENCE DOCUMENTS

S9312-AH-MMA-010 - EDG Technical Manual

S9233-DP-HBK-010 – Block Repair Handbook

Cylinder Block Bore Salvage Procedure (2963GL)

Model 38 1/8 Corrective Procedures for Main and Rod Bearings

Main Bearing Re-bore Procedure (GL16247A6)

Proprietary OEM engine block weld procedure

Proprietary OEM drawings of crankshaft, engine block, coupling assembly, and generator

REQUIREMENTS

The Contractor shall provide all labor, materials, equipment, special tools and technical expertise necessary to inspect and repair the lower crankline, to install a new lower crankshaft and generator coupling, and to provide technical oversight for reassembly, generator alignment, and retest of the EDG on SSBN 735. The intent of this effort is to return the SSBN 735 to unrestricted service following failure of the number 14 LMB. In support of this effort, the following requirements are established:

3.1 Disassembly

· Remove and install bearing caps to the extent necessary to facilitate crankline inspection using references 2.1 and 2.2 for technical guidance.

3.2 Inspection

· Perform as-found lower crankline dimensional and mandrel inspections using reference 2.2 for technical guidance.

· Perform as-found lower crankline optical alignment inspection using reference 2.2 for technical guidance.

· Inspect generator coupling for concentricity, alignment, and flatness using reference 2.7 for technical guidance.

3.3 Repair

· Replace number 11, 12, 13 and number 14 LMB caps using references 2.2 and 2.7 for technical guidance.

· Repair number 11, 12, 13 and number 14 LMB saddles using references 2.2, 2.5, 2.6, and 2.7 for technical guidance.

· Perform post-repair lower crankline dimensional and mandrel inspections using reference 2.2 for technical guidance.

· Perform post-repair lower crankline optical alignment inspection using reference 2.2 for technical guidance.

· Perform inspection, measurement, and machining services in support of assembly of GFM crankshaft, vertical drive ring gear, and generator coupling using references 2.1 and 2.7 for technical guidance.

· Perform inspection and measurement of generator rotor shaft and shaft coupling flange using reference 2.7 for technical guidance.

3.4 Reassembly

· Provide technical oversight for reassembly of diesel engine using reference 2.1 for technical guidance.

· Provide technical oversight for alignment and coupling of generator to engine to include inspection, measurement, and machining services using references 2.1 and 2.7 for technical guidance. Government will provide rigging and assembly services.

3.5 Material

Below is a list of material that the Contractor will be required provide in order to complete the requirements of this SOW:

Item
Reference 2.1
Quantity
Part Number
Lower main bearing bolt & nut assembly
Fig 7-21, pc 4
4
16702480
Lower main bearing green cap assembly
Fig 7-21, pc 12
6
16701488 (needs main bearing booster fitting)
Lower main thrust bearing green cap assembly
Fig 7-21, pc 13
1
16701494
Coupling ring bolt spacer bushing
Fig 7-27, pc 3
10
NAFB6632A
Bolt, coupling crankshaft to drive plate and rotor shaft to driven plate
Fig 7-27, pc 8
16
16702607or NAFB1638K
Bolt, Ring, coupling drive plate to driven plate
Fig 7-27, pc 5
10
NAFB2404A or NAFB2404F
Nut, coupling crankshaft to drive plate and rotor shaft to driven plate
Fig 7-27, pc 9
16
NAFB1967A
Cotter pin, 3/16 x 2, coupling to rotor and coupling to crankshaft
Fig 7-27, pc 10
16
81309995
Washer, coupling drive plate to coupling driven plate
Fig 7-27, pc 4
10
CAFB2722A (may come with nut, pc 9, PN NAFB1967A)
Nut, coupling drive plate to coupling driven plate
Fig 7-27, pc 6
10
NAFB3596A
Cotter pin, 3/16 x 3, coupling drive plate to coupling driven plate
Fig 7-27, pc 7
10
81309998

Main Thrust Bearing

2
16300373

Main Bearing, Standard

24
16603841

Main Bearing, Booster Pump Application

1
16605609

DELIVERABLES

General

4.1.1 All deliverables submitted during the execution of this Task Order shall comply with the applicable Data Item Descriptions (DIDs) referenced in the individual CDRLs (DD 1423s) included in Exhibit A of the base contract.

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 Status Report (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 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. 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.3.2 For the duration of Task Order execution, the Contractor shall schedule and conduct daily status phone conferences to discuss task status, progress made, problem areas, schedule changes, and other relevant issues related to the execution of this Task Order.

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/ship visited

· Contractor personnel making trip

· Personnel contacted

· Travel dates

· Background

· As-found conditions & observations

· Actions Taken

· OQE data sheets from validation testing

· Conclusions & recommendations

4.4.2 Submission of this report shall be done via electronic mail to the COR and TPOC. Trip reports shall be submitted no later than 10 business days after completion of each trip.

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. 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 provide a daily technical progress report which details the work performed since the previous technical progress report, the work planned or expected to occur over the next 24 hours, and issues or concerns with respect to either time period. The daily technical progress report should be submitted via electronic mail to the designated Technical Point of Contact (TPOC).

4.5.3 The Contractor shall provide a Condition Found Report (CFR) within 24 hours of discovery in the event of a material condition that represents a change in the scope of work of this Task Order as it relates to completion of the overall repair. The CFR should provide a recommended course of action and include estimated labor and material required to address the material condition. Each CFR shall be submitted via electronic mail to the Subject Matter Expert identified in section 12 of this SOW and to the designated TPOC.

4.5.4 Upon completion of all inspections, assessments and analyses, the Contractor shall develop and submit a final report with a cover letter that describes the contents of the report. The final report must detail the results of inspections, assessments, analyses, and repairs, with applicable data that was recorded. Enclosure of CFRs completed in the course of the repair is an acceptable means of including results and data. The report shall provide a recommendation for future use of the equipment (i.e. “suitable for unrestricted operation” or “operation with the following considerations and restrictions”). The report shall include a “lessons learned” section that includes but is not limited to recommended technical and project management improvements based on execution of this Task Order.

SECURITY REQUIREMENTS

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

Operations Security (OPSEC)

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

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

5.2.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.2.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.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.3 Receipt, Storage and Generation of Controlled Unclassified Information (CUI)

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

PLACE OF PERFORMANCE

The primary place of performance for this Task Order shall be shipboard at Trident Refit Facility, Bangor, WA, with technical and program/project management support from the Contractor’s facilities in San Diego, CA and in Beloit, WI.

TRAVEL

The Contractor is required to travel from the primary performance location when supporting this requirement. Contractor is required to travel to the following location in order to perform the services under this SOW:

DESTINATION

Bangor, WA

GOVERNMENT FURNISHED MATERIAL/EQUIPMENT/SERVICES

Trident Refit Facility King’s Bay shop support for assembly, disassembly, rigging, staging, other services and materials not specified in this task order as Contractor-furnished.

NSWCPD will provide a Government-designated representative to support the assessment duration on site for each shipboard visit to provide administrative support, coordinate shipboard efforts, and assist with installation and testing requirements. The Government-designated representative will support contract service personnel during installation and system checks, and will witness all operational testing evolutions.

LEVEL OF EFFORT

The total cost shall include the level of effort necessary to complete all elements of this task order within the established period of performance.

Additionally information related to this SOW:

TASK ORDER PERIOD OF PERFORMANCE

The period of performance for this task order is six (6) months from the time of award.

SUBJECT MATTER EXPERT (SME)

The SME for this delivery order is Stephen Kovacs, NSWCPD Code 421, Philadelphia PA. Mr. Kovacs can be contacted at Stephen.n.kovacs@navy.mil or (856) 904-2587.

CONTRACTING OFFICER’S REPRESENTATIVE (COR)

The COR for this task order is Amy Enever, NSWCPD Code 4021, Philadelphia, PA. Ms. Enever can be contacted at Amy.Enever@navy.mil or (445) 444-5317.

File details come from the government source that posted it. Updated .