eFactoryPro Wiki

PM Hold process for Planned Shut Down (Site Steps Only)

Updated on

This process outlines the steps that should be followed by the sites when a Planned Shut Down is required.  Although it is possible to apply this process for short time periods, we recommend that you use it for longer periods of time due to the amount of work required by both the site and IT.

Before Shut Down

1. Call the Help Desk and enter a ticket to have your PMs adjusted for the time that the Site is on shutdown.  Be sure to include a name and phone number of a person who will be available if questions arise.

1.1. Include the start date of the shutdown, and end date if known.

1.2. Include the last date that ATS personnel will be on site.

1.3. We also need to know what the customer wants to be done with the PMs that have already generated.

Some examples include:

Cancel:  This will hit the Site's Metrics.

Cancel/Duplicate: This will NOT hit the Site's Metrics.

Leave the following types of PMs open:  Regulatory?  Quarterly?  Semi-Annual?  Annual?  2-Year? etc

Areas/Assets Remaining Active?: If a small crew is remaining for fire watch, are there machines/areas you wish to leave active?

2. Ask that the ticket be escalated to IS Support.

  1. IT will put all future PMs on Hold, changing the Schedule Due Date out to 2030 and the Schedule Rule to 8-Year.
  2. IT will also modify the already generated PMs according to the instructions given in response to 1.3.

THE SITE SHUTS DOWN FOR THE PLANNED OUTAGE.

As soon as you have a FIRM DATE on when the Planned Outage is ending, complete the following steps.

3. Call the Help Desk and have them enter IT Ticket stating the Site's Return to Service Date.  Remember that this must be a firm date of when you are returning to the site.

4. Ask that the ticket be escalated to IS Support.

In response, IT will send the site a modified PM Schedule Forecast Report.

5. Site receives the V-Lookup modified PM Schedule Forecast Excel doc from IT.

6. After meeting with the customer and obtaining agreement, Site modifies the report to show only the next PMs that need to generate.

These are the PMs that will be reactivated, so please be thorough.

7. Site saves a copy and sends back the report on the IT Ticket, asking it to be escalated to IS Support.

IT reloads the appropriate PM Schedule Due Dates and changes the PMs back to the original frequency.

The PMs are then spot checked.

Assuming everything looks right, the IT Ticket is closed.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Next Article How do I stop downtime from accruing while my site is on a Planned Outage?