12.07.2015 Views

Maintenance Planning Process - Marine Corps Systems Command

Maintenance Planning Process - Marine Corps Systems Command

Maintenance Planning Process - Marine Corps Systems Command

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Maintenance</strong> <strong>Planning</strong> <strong>Process</strong> NarrativesOperations & Support Subsystem PhaseTitle: Inputs to SLEPBlock Reference Number: OS-20Objective: The objective of updating the Service Life Extension Program (SLEP)is to ensure that weapon systems and their associated support subsystems thatare targeted for life extension programs can continue to be supported to the endof the desired extended life of the system.Risks: Failure to update SLEP may lead to support subsystems includingmanufacturing capabilities and spares, being no longer available for the entireextended service life. This will leave the existing system experiencing longerrepair cycles than expected, may require LOGCOM to take over supporting thesystems without having the facilities or budgets to do so, higher than desirablefailures of the systems, lower availability, and significantly higher ownershipcosts. This in turn will increase POM requirements, logistics and fleet demands.Responsibility: It is the responsibility of MCSC Log; LOGCOM Log; to ensurethat each SLEP is updated in a timely manner anytime a SLEP is beingconsidered.Involvement of Others: OEM/ContractorMechanisms: RCM2Inputs: Updated MEA, Level of Repair Analysis and Analysis of <strong>Maintenance</strong>AlternativesOutputs: SLEP recommendationsTiming: Immediately after a SLEP has been announced and all aspects of the<strong>Maintenance</strong> Engineering Analyses have been updatedDistribution: MCSC Log, LOGCOM Log, OPFORRES, OEM/ContractorPreparation: See SLEP procedures3/15/2006 Page 22 of 24 Flowchart Control MPP V2.1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!