Reopening PPM Work Orders - (REOPENPM Install Parameter)
My current configuration has the REOPENPM install parameter set to "No." What, if any, are the potential negative consequences of changing that install parameter to "Yes" and allowing users to reopen PPMs?
The issue with being able to reopen a PM work order after you have already closed it is data integrity. If you can reopen a closed pm it does not matter how far back you go and it does not control what you can change once it is reopened. So there is a potential for bad data at anytime in the process. This is no different than regular work orders but normally a PM work order is more regulated so it is more controlled.
Wanted to circle back to this and provide some additional information. We are currently migrating a number of assets from one maintenance pattern to another. In the event there are two or more open PM WOs for an asset/MP that does not allow duplicate WOs, you will receive an error when attempting to deactivate the MP. You will also not be able to close the most recent WO until older WOs in the sequence are closed first.
Yes, that is true. Not sure what the question is? The issue that you are describing does not really have anything to do with the Install parameter mentioned above.
There is no question. I was describing an unintended consequence of allowing users to reopen PM WOs. Multiple open PM WOs can create conflict and produce errors. That should be a consideration with respect to the above-referenced install parameter.
The issue with being able to reopen a PM work order after you have already closed it is data integrity. If you can reopen a closed pm it does not matter how far back you go and it does not control what you can change once it is reopened. So there is a potential for bad data at anytime in the process. This is no different than regular work orders but normally a PM work order is more regulated so it is more controlled.
Wanted to circle back to this and provide some additional information. We are currently migrating a number of assets from one maintenance pattern to another. In the event there are two or more open PM WOs for an asset/MP that does not allow duplicate WOs, you will receive an error when attempting to deactivate the MP. You will also not be able to close the most recent WO until older WOs in the sequence are closed first.
Yes, that is true. Not sure what the question is? The issue that you are describing does not really have anything to do with the Install parameter mentioned above.
There is no question. I was describing an unintended consequence of allowing users to reopen PM WOs. Multiple open PM WOs can create conflict and produce errors. That should be a consideration with respect to the above-referenced install parameter.