Field | Description | ||
---|---|---|---|
General PPM profile fields | |||
Code | Enter a unique code for the PPM profile. | ||
Name | Enter a relevant name for the PPM profile. | ||
Type | Displays the type of PPM profile that was added: a PPM scheduling profile with clustering or without clustering. | ||
Language | Select the language in which the descriptions of generated PPM orders, order lines and order costs, from this profile should be shown. The generated PPM orders and related order costs and order lines will take their descriptions from the related 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.
| ||
Maintenance 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 | In this field, 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 | In this field you can 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.
| ||
Criteria type | The purpose of this mandatory field is to prevent duplicate orders being generated from the PPM profile. Select the criteria by which activity definitions should be filtered and picked up for order generation: Property-based or Contract-based. • Property-based type: only picks up activity definitions that at least have a link to the selected properties and no link to a contract-based maintenance plan. With this type, no links can be made to contracts on the PPM profile. • Contract-based type: only picks up activity definitions that at least have a link to the selected contracts via their service plan (with a contract-based maintenance plan reference). With this type, you can link both properties and contracts to the PPM profile. See Criteria type and PPM profile for more information. | ||
Links - perform at least one of the three Link actions on a PPM profile: | |||
Linked contracts | This field displays the contracts that are linked to the PPM profile via the Links action on the action panel. | ||
Linked properties | • If the criteria type of your PPM profile is property-based, this field enables you to select the properties that are linked to the maintenance plan. • If the criteria type of your PPM profile is contract-based, this field enables you to select the properties that are linked to the contracts and properties from a contract-based maintenance plan. | ||
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. | ||
Additional fields for PPM profiles with clustering: | |||
Cluster group | Select the cluster group that applies to the PPM profile. This cluster group defines the criteria for clustering the maintenance orders during the scheduled run. | ||
Timespan for clustering | Select the timespan that should apply to the clustering: day, week, month or year. | ||
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. |