Setting-up and Configuring PM Process
PM Process Setup allows for configuration of the following:
• Creation behavior of Work Order(s) and Work Detail record(s) – where applicable
◦ WO generation determined by the rules and mappings defined in PM Process.
◦ WO assignment set to Primary Technician, or specific Team, Dispatcher, Technician, or Queue.
◦ Calculation of Preferred Start and End Date Time where applicable.
◦ Auto-population of relevant fields, such as “Work Order Type,” “Is PM Work Order,” and “Preventive Maintenance Plan”.
• Creation behavior of Case record(s) – optional
◦ Case Creation per the mapping defined in PM Process.
◦ Case assignment to specific User or Queue.
If the PM Plan’s PM Schedule Definitions are utilizing “Task Templates/Work Order Purpose” functionality, then the PM Process setup determines the following:
• If
SET001 (Module: Preventive Maintenance, Submodule: PM Actions) is True (default), then Tasks from the Task Template are created per the target object and Mapping defined in the PM Process.
◦ OOTB SVMX Mapping for PM Process directs Task Templates to map to the ‘Task’ related object on the Work Order.
◦ SET001 (Create Task on Work Order) and
SET002 (Default priority value) are both global settings under Module: Preventive Maintenance, Submodule: PM Actions.
◦ SET002 is used as default task priority, if there is no mapping from Task Template to Task’s Priority field.
• If required parts have been defined in the Task Template, then Work Detail line records are created on the WO related list as per Required Parts Map configured in PM Process.
◦ These Work Detail Lines will default to a line type of “Requires Part”.