In order to generate requests from the Recurring Service Program, at least one Service Scope must exist and a Program Schedule needs to be generated based on the Service Triggers defined.
The Requests can be generated using the Recurring Service Request Generation assistant which will run as a background job.
Calendar-based Recurring Service Request generation will generate Requests for a chosen date range or a selected schedule horizon (number of days in advance from the current date). The usage/condition-based Recurring Service Request generation picks up program schedule occurrences with a Recorded Value (latest measurement/ reading recorded) that has reached/passed the line Trigger Value for usage triggers (accumulate parameters) and Recorded Value that has met the condition limit or falls outside/inside the given range for condition triggers (limit parameters), and in status Generable to generate Requests. The generation can be limited by specifying which Recurring Service Program, Service Organization, Customer, Contract, Recurring Service Package, Model and Service Object the Recurring Service Program Requests should be generated for.
Request generation can be set up to run as a scheduled background job.
This method of request generation can be run as often as required and Requests can be generated up to a future date (for calendar-based generation). A longer planning window allows you to analyze future resource requirements and plan the Recurrins Service Request along with other service activities.
Requests can also be manually generated from the Recurring Service Program/Schedule tab. This is done by selecting the corresponding program occurrence line and using the Generate Request command.
When you run a recurring program with Floating Schedule set to Yes, only one Request can generated at a time.
It is important to make sure that the program Schedule Occurrences are up-to-date at the time of Request Generation. The Regenerate the Schedule flag will indicate if the schedule requires regeneration.
Requests will only be generated from Active programs and only for Program Occurrences in Generable state. When there is a Request Contract connected to the Recurring Service Program, the Recurring Service Requests will only be generated when the contract is Active. For Recurring Scopes associated with a Contract Line, the SLA Template and Pricing Rule on the Contract Line will be applied on Request Scopes on the generated Recurring Service Requests.
When a Request is generated, information from the Recurring Service Program is included in the generated Request, such as the Description, Service Organization, Customer, Model, Service Object, Service Scopes and all its connections such as Standard Tasks, Resource/Material requirements etc. The Due Next of the respective calendar program occurrence on which the Request was generated will be considered as the SLA Start Date to calculate the SLA Commitment Due Date for SLA Commitment Lines, unless a Triggering Entity and Event has been specified on the SLA Template Line. For usage/condition-based program occurrences on which the Request was generated, the Request creation date would be used.