My Customer has the following requirement where usage-based PM Actions are linked. This is somewhat similar to Usage-based Replacements
In this example, there are 3 linked PM Actions based on usage.
250 Hour Maintenance
500 Hour Maintenance
1000 Hour Maintenance
These are linked and performed value-based. When PM Action is defined as Performed Value-based, the next occurrence will be adjusted to performed value.
For example, if 250 Hour Mx is completed at 200 Hours. The next Maintenance will be due at 450 Hours (instead of 500). Up to this point, it works ok in IFSAPP Out of the box. However, the customer wants all the link PM Action to be adjusted based on the fact one of the linked PM WO is performed earlier.
After 250 Hour is performed at 200;
500 Hour Maintenance to be due at 450
1000 Hour Maintenance to be due at 950
Then if 500 Hour Maintenance is performed 470 (instead of 450)
Next 250 Hour Maintenance to be due at 720
Next 1000 Hour Maintenance to be due at 970
Have you come across a requirement like this? If so, how did you overcome it (with or without CRIMS)
