LCS SEC Attachment J-14 LCS Planned Maintenance WI Spec 897-11-001.pdf

04/18/13

Planned Maintenance Work Specification

Ship: LCS Class ITEM NO.897-11-001 COAR: N/A PCN: None

SWT FILE NO: CMP: N/A

REVISED: 18 April 2013 PLANNER: N/A

1. SCOPE:

1.1. Title: Littoral Combat Ship Planned Maintenance System (PMS) Planning and Execution; provide

1.2. Location of Work

1.2.1. Not Applicable

1.3. Identification

1.3.1. Not Applicable

2. REFERENCES

2.1. Current PMS Force Revision

2.2. NAVSEAINST 4790.8B, Ships’ Maintenance and Material Management (3-M)

Manual

2.3. S0400-AD-URM-010, Tag-Out Users’ Manual for Littoral Combat Ship Pilot, dated 30 December 2008

2.4. Contractor Quality Management System (QMS)

2.5. LCS SKED data requirements

3. REQUIREMENTS:

3.1. Provide Planned Maintenance System (PMS) planning and administrative services.

3.1.1. Utilize Reference 2.1., Navy PMS Force Revision, as a baseline to establish maintenance requirements.

3.1.1.1. Where Navy PMS Force Revision lacks coverage submit a PMS Feedback Report (FBR).

3.1.1.1.Implementation schedules for Navy PMS Force Revisions shall be established by SWRMC. Ongoing maintenance efforts should not be disrupted in order to change Force Revisions.

3.1.1.2.Advanced Change Notices (ACN's) and Pen and Ink Changes will be incorporated as soon as practical.

3.1.2. The scope of Contractor responsible planning and execution of the PMS Force Revision will be determined through an adjudication process with the government each time a new Force Revision is released.

3.1.2.1.PMS maintenance planning will include reporting audits validating all equipment requiring maintenance are associated with appropriate maintenance activity.

3.1.2.2. Adjudication results will be documented in both the

contractor-specified planning tool and PMS SKED.

3.1.2.3. Changes to adjudications during the time period between Force Revisions may be requested by either the Government of Contractor and implemented upon approval by both parties.

3.1.3. PMS Planning will be conducted in contractor-specified planning tool utilizing Government Furnished Information (GFI).

3.1.3.1. Align PMS frequency with Navy frequencies, in accordance with Reference 2.2 and the PMS Force Revision.

3.1.3.2. Establish ability for the contractor-specified planning tool to export maintenance scheduling and execution completion data in a format that supports input into PMS SKED.

3.1.4. Schedule situational maintenance requirements (R-checks) utilizing GFI provided to the Industry Team, Ship’s Force, industry team data collection tools, and LCS Squadron.

3.1.5. PMS Feedback Report (FBR) submittal. The industry team shall submit PMS FBR’s directly to the PMS MIS. PMS FBRs shall be submitted, at a minimum, in the following circumstances:

3.1.5.1. PMS MRC on MIP does not apply to any ship of the class.

3.1.5.2. PMS MRC contains administrative error(s).

3.1.5.3. PMS MRC procedure, tools, parts or materials are in error.

3.1.5.4. PMS periodicity change is recommended.

3.1.5.5. PMS coverage is inadequate or unavailable.

3.1.5.6. PMS coverage is excessive.

3.1.5.7. Procedures require improvement to better align them to the LCS class equipment.

3.1.6. PMS reports shall be provided to the SUPERVISOR prior to and at the completion of Availabilities and/or at periodicities agreed upon between the SUPERVISOR and Contractor:

3.1.6.1. PMS work completion.

3.1.6.2. Quarterly PMS forecast.

3.1.6.3. Overdue PMS.

3.1.6.4. Lost Checks.

3.1.6.5. PMS FBR Log.

3.1.6.6. PMS CFR/IDR log.

3.1.6.7. Arrival and Departure Reports containing the following data elements:

3.1.6.7.1. Count of Planned (Base) PMS checks.

3.1.6.7.2. Count and percentage of completed Base PMS

checks.

3.1.6.7.3. Count and percentage of rescheduled PMS checks

that were deferred from previous availability.

3.1.6.7.4. Count and percentage of Cancelled/Deferred PMS

checks.

3.1.6.7.5. Count and Percentage of PMS checks pulled

forward.

3.1.6.7.6. Detail list of Cancelled or Deferred PMS checks

including MIP, Equipment Designation (HSC), Compartment, Reason for cancellation/deferral, impact to ship, and plan for future execution if warranted.

3.1.6.7.7. Detail list of PMS checks pulled forward including MIP, Equipment Designation (HSC), Compartment, and reason for pulling forward.

3.1.6.7.8. Count and percentage of total PMS package, including Base and Pulled Forward PMS.

3.1.6.7.9. Summary of planned man-hours for Base, Pull-

Forward, Cancelled/Deferred, and PMS checks that were deferred from a previous availability.

3.1.6.7.10. Count of Work Authorization Forms (WAFs)

generated.

3.1.6.7.11. Count and percentages of WAFs cancelled or

remaining open at conclusion of availability.

3.1.6.7.12. Count of tag-outs generated.

3.1.6.7.13. Count and percentages of tag-outs remaining in

effect at the conclusion of the availability.

3.1.6.7.14. Count of CFRs submitted.

3.1.6.7.15. CFR details including identification of MIP, MRC, Equipment designation (HSC), Compartment, Description of

Problem Found, Recommended Solution, Government Response, Government Reviewer (ie: PM SBS, CHENG, etc.), Date Opened, Date of Govt Response, Date Closed, and Status.

3.1.6.7.16. Documentation of conditions found that support

identification of Condition Based Maintenance candidates vice periodically scheduled maintenance philosophy.

3.2. Provide PMS production services.

3.2.1. WAF requirements. Each PMS check, conducted by off-ship personnel, requires a WAF. The WAF provides the on-hull crew the notification of what PMS checks the contractor/subcontractor plans to execute, on which systems/equipment, and when the PMS is scheduled to be accomplished. Ship’s Force determines if and when the PMS checks can be performed, authorizes the WAF for the PMS to commence, and provides the final signature on the WAF indicating the work effort has been completed. If the PMS has been deferred or cannot be completed, an appropriate comment will be added to Block 15 of the WAF.

3.2.1.1. WAFs are written at the system/equipment level. They can contain multiple MIPs/MRCs applicable to the particular system/equipment and assigned to a specific contractor/subcontractor.

WAFs are developed, authorized, and tracked utilizing the Navy’s Internet based Electronic Work Authorization Form System (eWAFS).

3.2.1.2. A separate WAF is required in situations where multiple contractors/subcontractors are working on the same system/equipment at the same time. Each unique contactor/subcontractor requires its own WAF.

3.2.1.3. The WAFs for PMS performed by Industry personnel shall be developed by the Industry Team, prior to the start of an availability, to facilitate approval by the on-hull crew. The Industry Team will be provided the following information: Scheduled start and stop dates, point of contact information (name, company/position, and telephone number), MRC number(s), and applicable system/equipment nomenclature.

3.2.2. Equipment Tag-out. Tag-out shall be developed, authorized, and managed in accordance with Reference 2.3 and documented utilizing the Navy’s Electronic Ship Operations Management System (eSOMS).

3.2.3. Tag-out preparation will begin in a sufficient amount of time prior to the maintenance period in order to minimize ramp-up time at the start of the availability. The Industry Team shall accomplish this through use of a portable computer network to develop tag-outs during the planning stages and electronically transferring them to the ship’s LAN or eSOMS computer at the start of the availability.

3.2.4. The Industry Team shall develop the tag-outs for the PMS tasks being accomplished by off-ship personnel. All PMS tag-outs shall be authorized by the on-hull crew.

3.3. Tools, parts and materials for PMS.

3.3.1. Common hand tools will be provided by the contractor or subcontractor without a direct charge to the government. Where special tools are required they shall normally be provided by the industry team. In the event special tools are not available they will be provided by the Government as GFM and maintained as Government Property by the Contractor.

3.3.2. Parts and materials required for PMS will be procured by the Contractor from commercial or government sources. All PMS material will be stored, managed and distributed by the Contractor. Advance procurement and storing of PMS materials is desired, particularly where situational requirements may drive an immediate need for materials with a long lead time.

3.3.3. Contractor shall maintain a portable storage unit sufficient to store miscellaneous parts and other consumable and hardware materials to be used to perform routine repairs not specifically called out on the MRC.

3.4. Performance of PMS will follow sequence and specifications of the written process on the MRC. Where there is a difference between the PMS MRC and other references, the PMS card takes precedence. If the card is in error the PMS FBR process will be followed to resolve the discrepancy. Where it is imperative that the maintenance action be partially completed prior to the scheduled operations, report the discrepancy to the SUPERVISOR via Condition Found Report (CFR) with a recommended solution. Do NOT deviate from the MRC without direction from the

SUPERVISOR.

3.5. Contractor shall, with concurrence of SWRMC, perform repairs to equipment to resolve discrepancies found while performing maintenance. Any activity of this nature will be documented as follow-on work where the maintenance performed and j use of parts will be documented as part of the maintenance history of the equipment.

3.6. Contractor shall record PMS Maintenance Requirements (MR) results as follows:

3.6.1. Contractor will record PMS completion daily via the government approved method.

3.6.2. PMS MR will only be reported as complete when the check is satisfied. Incomplete and/or unsatisfied checks shall never be reported as complete.

3.6.2.1. An MR that is primarily an inspection or assessment of a space, system, or piece of equipment is intended to record results of the inspection or assessment. If the inspection/assessment is properly completed by the maintenance technician, then the contractor shall record the MR as complete provided that any deficiencies identified during the inspection/assessment are reported and documented IAW the MR and the PMS report.

3.6.2.2. If the MR is performed to ensure that a system or piece of equipment is operating properly and that operation is not within tolerances, specifications or requirements, then the contractor shall not record the MR as completed. The contractor shall then report discrepancies via CFR and include them on the PMS report.

3.7. QA Surveillance.

3.7.1. Contractor will maintain the PMS Surveillance Log (PSL), incorporating all PMS checks executed. The PSL shall include all OQE required to validate MR accomplishments.

3.7.1.1. Contractor will notify SWRMC when PMS Surveillance

checks will occur to allow SWRMC to witness contractor QA processes.

3.8. Conditional Based Monitoring

3.8.1.Contractor shall provide documentation of conditions found that support identification of Condition Based Maintenance candidates vice periodically scheduled maintenance philosophy.

3.8.2.Contractor shall develop meters relevant to the equipment and maintenance performed. While performing or overseeing maintenance contractor will ensure that meter data is collected for analysis supporting migration from periodicity based maintenance to condition based maintenance.

3.9.LCS SKED data requirements.

3.9.1.Contractor will provide SWRMC with weekly data files complying with requirements provided in reference 2.5.

4.NOTES:

4.1.None.

5. GOVERNMENT FURNISHED MATERIAL (GFM)

5.1 As Required.