Preventative Maintenance Scheduling Changes
If there is a change to a Preventative Maintenance Schedule, the only problem-free way to do this is to unassign the PM Procedure from the Equipment or Location, Reassign and setup a new schedule. When this is done the historical data on the old 'pms' record is lost although the WRs still exist in the system.
If the change to the schedule is made by changing the Date of First PM or updating the frequency/recurrence pattern, it leads to the PM WR not getting generated.
I would suggest a few changes to make the PM Planning a more error free process for the end user:
If there is a change in the schedule, allow the user to make the change by updating the date of first PM but add some validations/checks to ensure that this will not result in any problems when the PM WR needs to be generated.
Allow the user to make updates to multiple pms records from the PM Planner and generate the PM Dates for multiple PM schedules from this view.
Anything else that can be done to ensure that the user is only allowed to make changes to the pms record which will not cause it to not generate a WR as per the changed schedule. eg. restriction on the Date for first PM that can be selected.

-
Steve commented
This is a crucial upgrade, we have approx 44,000 assets in our system and am now in the process of forecasting dates for 2025 and am now discovering that for quire a few of these assets I cannot gett he dates to generate due to changes having being made. I now need filter for assets with no 2025 dates and unassign and reassign the PM procedure to get the dates to forecast, incredibly inefficient and potentially missed PM WR generations.
-
Ashley Nuttall commented
A lot of Comments about pausing a PM, i find setting the filter up in the console and grouping to the required group will allow you to cancel all the dates that are forecasted. This only works if the PM's have been forecasted and would be better if it was just an active/in active value in the PMS
-
Stephen commented
have an option to do extended forecasts push forecast out to a parametise duration. We forecast 5 years in advance. Also ensure pmsd forward records with no WO are deleted into the future (from today) when the forecast is currently done there are duplicates that skew cost estimates
-
Ashley Nuttall commented
I believe the changing of the Date first works to set the forward generation dates, however, a recent change to the generation function does mean the user needs to delete the forecasted PMSD data. The planner seems to cover this but only for the range set. Would be best maybe to monitor this field and have an action that removes all forecasted dates so that duplicates are not created. An inactive function would be good to be able to set a PMS to stop it from generating without changing any of the settings. There are ways to paulse a PMS for a time period already setting the manual date next to do will stop anything generating until the set date.
There is definitely a requirement to actively check the current eq status so that work is not generated, equally, there needs to be a report that shows all PMS records that will be affected by the equipment status. This will help if there are any expected PMS not generated because the eq has the wrong status.
-
Dan commented
remove the group by option that's ticked by default, as i can't really understand why anyone would use this when generating PPMs. our business partner recommended we always untick it
-
Stephen commented
Allow a manual out of cycle PM to be generated from the define schedules screen and give the option to choose the date. the date should be able to be retrospective. Example Tech has to do a repair and at the same time should do a PM for best practice, but does not want to re-schedule the cycle PM. Another example where this can be useful is when the auto create process goes down or there is an outage of IT. PM can be readily generated at the PMS screen allowing detailed view of relevant data on that screen to make decisions.
-
Stephen commented
Should also consider the ability to Purge forecast in the PMSD into the future when PMS is not active or not used or PM has been removed. we use this for 30 year forecast but when a building is demolished it would be good to have the ability to purge that data.
-
Heidi Sia-Ho Hoang commented
Definitely a must. I would suggest not to play with the Date of first PM, but rather use a specific field for adjusted date. "Adjusted date" field can be one-time thing or permanent change.
As of disposing of an equipment, I would suggest to add a pop-up window that ask if related tickets and PM should be cancelled as well (PMS to be INACTIVED or PAUSED).
Also agree for having the possibility to pause PMS manually. -
Stephen commented
While looking at this please review the layout of the Manage Work Order Generation Rules - Recurring Pattern Layout. It is difficult to understand if you are not very familiar with it.
Also have the ability to turn PMS of and on active/inactive
-
Tom Wilson - JLL commented
Another concept relative to pausing PM WR generation is to link PM generation to the status of Equipment. In theory there is no need to generate PM WRs for an equipment item that is flagged as anything other than "In Service", and has the added benefit of not being required to alter all the actual schedules associated to equipment that is not "In Service" but has not been disposed of.
The same principal applies to equipment flagged as "disposed". Although best practice would be to remove all PM schedules associated to equipment that has been flagged as disposed, this functionality would stop the needless generation of PM WRs for equipment that technically no longer exists in the asset inventory. -
Alisse Wasser commented
I agree with this, especially the idea of having some sort of verification that the work request will properly generate when changes are made or even when new schedules are created. I have found that I have to actively review all PVMs that generated on their generation date just to catch schedules that are not working properly. This would be huge time saver and it would make the PvM scheduling more reliable/robust.
-
Dan commented
Yes this is a MUST for me.
We also have requirement to be able to pause PPMs, i know you can set the frequency to 0 but this is a dirty solution and you need to remember to put it back to what it was. There should be the option to pause for a defined time, for example if you have a monthly PPM but due to reason such as lack of access (Covid...) or refurbishment you may not be carrying out the task for 3 months. You should be able to pause the PM schedule for x period, so pause for 3 of the next x (what ever the frequency is) then restart automatically.