Recurring Service Program Schedule

Recurring Service Program Schedule consists of Program Occurrences that can be generated for a Recurring Service Program based on regular calendar/ usage intervals inside the Program's Valid From and Valid To dates. For calendar-based programs, the program's Interval Type can be set to either Day, Week, Month or Year. And for usage-based programs, the Testpoint, cumulative Parameter (defined for the Program Main Object), Start Value and Interval must be set. The Service Scopes will be related to the Program Occurrences following the recurrence pattern defined for each Service Scope.

E.g.: Calendar-based Recurring Service Program Schedule Trigger - Weekly
Service scope X - recur every 1 Week
Service scope Y - recur every 2 Weeks

E.g.: Usage-based Recurring Service Program Schedule Trigger - Every 5000km (starting from 5000km)
Service scope X - recur every 5000km
Service scope Y - recur every 10000km

For calendar-based programs, once the service trigger is defined and a calendar option (Main Object Calendar/ Location Calendar/ Service Organization Calendar/ All Year/ Calendar) is selected, user can generate the schedule using Generate Schedule command in the Recurring Service Program/Schedule tab. If not, the schedule will be generated upon activating the Recurring Service Program. As a result, program occurrences can be generated into Recurring Service Requests.

For usage-based programs, a service occurrence is triggered based on the actual condition of a service object. To determine the condition of an object, the object parameter's measurements must be reported. Once the usage-based trigger is added to the program (i.e.: enter values for Testpoint, Parameter (defined for the Program's Main Object), Start Value and Interval) and there is at least one measurement registered, a program schedule occurrence will be created with a Trigger Value and a Recorded Value. If the Recorded Value (latest measurement/ reading recorded) has reached/passed the Trigger Value and in status Generable a Request can be generated on the corresponding program occurrence. However, if the Request is not generated for such program occurrences until a new measurement/ reading is recorded that reach/pass the next Trigger Value (based on the meter Interval), the program schedule occurrence status will be set to Not needed and a new program occurrence will be created in status Generable.

In situations where the program occurrence that is set to Not needed needs to be generated into a request, it is possible to create a Request manually by setting the line status to Generable.

When the Request is processed, the Request Status on respective program occurrence will be updated accordingly and Request Completed will be updated only when the Request is set to status Completed.

The length of the recurring service program schedule, i.e., the number of program occurrences generated in the schedule, depends on the life span of the Recurring Service Program, denoted by either the Valid To date or the PM_PLAN_HORIZON.

Manual changes done (e.g.: setting a scope to Generable = No) on program occurrences will be reset at regeneration of the Recurring Service Program schedule.

Status handling of schedule lines

There are different statuses on program occurrence.

Schedule Status	Description
Generable	Ready to generate Requests.
Request Generated	Request is generated.
Not in Current Schedule	When the user changes the recurring service program validity, it will be required to regenerate the schedule. If there are Request generated line which falls outside the new program validity, then such lines are preserved and will be assigned this status. Such requests should be handled manually.
Not needed	When the Request is not generated for a program occurrence where the Trigger Value has reached/passed the Recorded Value (latest measurement/ reading recorded) and a new measurement/ reading is recorded that reach/pass the next Trigger Value (based on the usage Interval), the program schedule occurrence status will be set to Not Needed.
On Hold	The program occurrence is temporarily not being pursued (e.g.: due to dispute with the customer, work slowdown, etc.). When the schedule line is applicable for request generation, the status can be changed back to Generable.
Cancelled	Program occurrence is no longer applicable. When a program occurrence has been cancelled, no further changes will be allowed. However, it will not be allowed to cancel a program occurrence with a Request generated. Cancelling a request to be handled on the Request.

Note: It is not allowed to set Request Generated, Not needed, and Not in Current Schedule statuses on program occurrences manually.