We currently have a monthly service contract that the customer did not renew - in May of 2024. They just asked to start the service back up. We have an object of service set up for the monthly PM. If I go through the renewal process, I don’t have an option to skip the past year or have a new start date. I can renew it for 2 years, but then I have 12 months of orders that were not generated. Which is OK.. but not very clean looking. Is there a way to keep the same contract id and skip a year on the renewal?
Best answer by Phil Seifert
Hi Angie,
The renewal process does not have a mechanism to skip a year when it extends a contract when the object of service is renewable. So a single object of service will not have the gap dates in between the two years per your question.
However, there is a way that I think should work for you and hopefully not too many objects of services are defined in your contract. Create different OOS for the same item on the contract.
First, set all the objects of services in the expired contract to Not Renewable. Note this contract and OOS expired on 29 April 2024.
The current PM schedule for this OOS (did not run PM Batch Scheduler for this testing so no orders created).
Note the PM dates are from 29-May 2023 to 29-Apr 2024.
Now, renew the contract with the expiration policy set to Extend Contract and New Duration 2 Years per your request to skip a year.
Run the renewal and you will have a contract valid from 30-April 2023 until 29-April 2026 (3 Years)
You will still only have the single object of service ending 29-April 2024 but now add one for the same item and answer No to the following question:
Set your new object of service valid dates from 30-April 2025 until 29-April 2026 and also set the PM Commencement date to begin at he start of the new coverage period which is 30-April 2025 in this example.
This ‘new’ object service will have its own PM Schedule that only covers the third year.
You will have two objects of service (in this example) where one covers the first year and one covers the third year.
You will not have PM dates scheduled for the item during the third year.
As the second object of service is renewable, future contract extensions will extend that coverage duration and create additional PM Dates going forward.
The key points are not renew the first OOS, run the renewal, create a new OOS covering the time you want the PM’s executed leaving a gap between the first year and the start of the second coverage for the same item.
This way, you will have the same contract ID instead of a new contract.
The renewal process does not have a mechanism to skip a year when it extends a contract when the object of service is renewable. So a single object of service will not have the gap dates in between the two years per your question.
However, there is a way that I think should work for you and hopefully not too many objects of services are defined in your contract. Create different OOS for the same item on the contract.
First, set all the objects of services in the expired contract to Not Renewable. Note this contract and OOS expired on 29 April 2024.
The current PM schedule for this OOS (did not run PM Batch Scheduler for this testing so no orders created).
Note the PM dates are from 29-May 2023 to 29-Apr 2024.
Now, renew the contract with the expiration policy set to Extend Contract and New Duration 2 Years per your request to skip a year.
Run the renewal and you will have a contract valid from 30-April 2023 until 29-April 2026 (3 Years)
You will still only have the single object of service ending 29-April 2024 but now add one for the same item and answer No to the following question:
Set your new object of service valid dates from 30-April 2025 until 29-April 2026 and also set the PM Commencement date to begin at he start of the new coverage period which is 30-April 2025 in this example.
This ‘new’ object service will have its own PM Schedule that only covers the third year.
You will have two objects of service (in this example) where one covers the first year and one covers the third year.
You will not have PM dates scheduled for the item during the third year.
As the second object of service is renewable, future contract extensions will extend that coverage duration and create additional PM Dates going forward.
The key points are not renew the first OOS, run the renewal, create a new OOS covering the time you want the PM’s executed leaving a gap between the first year and the start of the second coverage for the same item.
This way, you will have the same contract ID instead of a new contract.
For information, an object of service can only contain one commencement date thus if you set it the start of the third year for the first object of service, this also would have worked I think provided you did not schedule any service orders based on the extended second year PM’s. It would recalculate the PM schedule from the point of the commencement date.
I did not choose this route as I did not want to give the impression the object service was at all covered during the second year by the contract for either UM or PM linking back to the contract.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.