Enabling and Configuring Advanced PM Engine Settings
The Advanced PM engine provides the capability to efficiently process large volumes of data, which reduces the scalability issues and overcome Salesforce limitations. The Advanced PM engine leverages a queueable job on top of a batch class, enabling organizations to overcome Salesforce limitations and improve overall performance.
The SCON Scheduler job initiates the batch class and hands over data to the queueable job. This queueable job operates as a two-level asynchronous process that reduces data volume and addresses other Salesforce limits.
 |
The Advanced PM engine is supported only for Time-Based PM Plans and not supported for Condition-Based PM Plans.
|
To enable the Advanced PM Engine in your org, you must enable the Global Setting, GBL046. By default, this setting is set to False, where the org leverages the pre-existing time-based PM Engine for PM Processing.
Configuring Advanced PM Engine Settings
With Advanced PM Engine enabled, you can define the Batch Size to control PM Schedules and Sub-Batch/Chunk Size to control PM Coverages using the following settings:
|
Setting
|
Description
|
|---|---|
|
SET001 (Module: Preventive Maintenance; Submodule: PM Processor)
|
This setting defines the number of PM Schedules to be processed per batch transaction by the Advanced PM Engine. By default, this value is set to 100.
|
|
SET002 (Module: Preventive Maintenance; Submodule: PM Processor)
|
This setting defines the number of PM Coverages to be processed in Queueable job by the Advanced PM Engine. The Queueable Processor uses this to segment the records to process and iterate via self- chaining. By default, this value is set to 100.
|
|
|
• These settings are applied only when the Advanced PM Engine settings is enabled in your org.
• The Notification Manager sends an email with processed plan details that includes an attachment for failure and attaches log details to the PM Plan.
|
Use Case
An MRI machine is installed at a hospital. A PM Plan is required to anticipate the service needs of the device and is scheduled at predefined intervals. The machine is set to be serviced every two months over the next 20 months. Based on these requirements, the end user creates a PM Plan by defining all necessary parameters. The admin configures the PM Process by defining criteria using the expression builder to qualify PM Plan records for generating PM work orders.
Once the PM Plan and PM Process are established, the SCON scheduler picks up the PM Process and qualified PM Plans to create PM Work Orders, as shown in the following table:
|
Total Number of Qualified PM Plans
|
Schedules per Plan
|
PM Coverage Per Plan
|
Number of Tasks in Task Template
|
Number of Parts in Task Template
|
Total Work Orders created
|
Total Work Details created
|
Total Cases Created
|
Total Tasks Created
|
Time taken for Execution
|
|---|---|---|---|---|---|---|---|---|---|
|
10000
|
10
|
1
|
15
|
3
|
100000
|
300000
|
100000
|
151000
|
46 mins
|
|
|
The runtime observed in a standard sandbox environment may vary in a customer’s actual environment.
|
As per this use case, the total number of qualified plans is 10,000 based on the matching criteria, resulting in a large volume of work orders. The existing time-based PM engine might take longer to process these large volumes of data or could reach Salesforce governance limits.
To address scalability issues and limitations, you can configure the new Advanced PM engine settings, SET001 and SET002 to process large volumes of data more efficiently and reduce the time required for execution.
|
Setting
|
Value
|
|---|---|
|
SET001 (Module: Preventive Maintenance; Submodule: PM Processor)
|
100
|
|
SET002 (Module: Preventive Maintenance; Submodule: PM Processor)
|
100
|
It is recommended to adjust these settings within the range of 1–200, to bypass any governor limit that may occur in specific org environment or to further optimize runtime performance.