Code

Enter a unique code for the PPM profile.

Name

Enter a relevant name for the PPM profile.

Cluster group (PPM profiles with clustering)

Select the relevant cluster group for the PPM profile. This cluster group sets the criteria for clustering maintenance orders during the scheduled run.

Criteria type (non-clustered)

This mandatory field prevents duplicate orders from being generated by the PPM profile. Select the filtering criteria for activity definitions to be included in order generation: Property-based or Contract-based.

Language

Select the language in which the descriptions of generated PPM orders, order lines and order costs should be displayed for this profile.

The descriptions for generated PPM orders, order lines, and related order costs will be derived from the Translated name field in the selected language.

If you do not select a language in this field, the language from the SCHEDULERENGINEADMIN user account is used for PPM order generation.

Plan

Select the maintenance plan to which the PPM profile applies.

System status

Displays the selected status of the PPM profile: Active or Inactive.

Start date of schedule

Enter a start date for running the scheduled PPM profile.

End date of schedule

Enter an end date for running the scheduled PPM profile.

Schedule

Define the frequency and number of intervals at which the schedule should be run. You can also select specific dates for running the schedule.

Future period

Select a period in the future for which to generate PPM orders, starting on the next scheduled run date. Example: if you select 1 month, each scheduled run generates PPM orders for the next monthly period.

Past period

Select a period in the past until the next scheduled run date. This period is used to generate orders for activities that were 'missed' in a previous scheduled run. Typically, these are activities that were added to the schedule after the previous run date. With this setting, you can include the 'missed' activities from a past period in the next run. This setting is especially useful for Condition-based or Predictive-based activities that have dynamic scheduling behavior. Example: if you select 1 Month, the PPM profile will include activities from the previous month in the order generation, upon each scheduled run.

Next run date-time of schedule

Initially: enter the first date-time on which the schedule should be run to generate PPM orders. After the first run, this field will display the next calculated run date-time according to the schedule.

Linked contracts

This field displays the contracts that are linked to the PPM profile via the Links action on the action panel.

Linking a contract is optional. If no contract is linked, Activity definitions linked to any contract are applicable.

Linked properties

This field displays the properties that are linked to the PPM profile via the Links action on the action panel.

Linking a property is optional. If no property is linked, Activity Definitions of any property are selected.

Linked activity definition groups

This field displays the activity definition groups that are linked to the PPM profile via the Links action on the action panel.

Linking a activity definition group is optional. If no activity definition group is linked, Activity Definitions linked to any activity definition group are applicable.

Timespan for clustering

Select the timespan that should apply to the clustering: By day, By week, By month, by year or By generation period.

Intermediate logging?

Specify whether you want to activate intermediate logging on the background action, during the order generation. By default, this field is set to No, to prevent the system from slowing down. This means that log results are only stored when the background action for order generation has ended. If you want to monitor the background action's progress more closely, set intermediate logging to Yes, but bear in mind that this may affect the system's performance.