Along with the maintenance plan processing batch size, the number of maintenance assets in each maintenance plan also impacts the process run performance. The number of work orders generated for each process run depends on the total number of maintenance assets in the maintenance plans, as work orders are generated for the assets.

To avoid Salesforce governor limits, refer to the specific recommendations in the Salesforce Governor Limit Recommendations section.

For example, 10 maintenance plans containing 10 assets each are considered for the maintenance plan process run, and all the maintenance assets' work rules are qualified. In this case, 100 work orders are generated for the process run.

Each maintenance plan process supports a maximum of 10,000 maintenance plans. When the total number of plans across multiple PM processes is fewer than 10,000, the system automatically combines them into a single Apex batch job to optimize execution efficiency. No single batch job will exceed this threshold.

The threshold limit is configurable and can be adjusted to accommodate specific customer requirements and deployment scenarios.

Batch size should be set in inverse proportion to the number of assets associated with each maintenance plan. Higher asset counts per plan require a smaller batch size to prevent heap size errors and reduce CPU consumption, while lower asset counts allow for a larger batch size to improve throughput.

The number of batch workers created for a single Apex batch job depends on the combination of the batch size set and the Maintenance Plan assignment threshold limit. The following table shows a couple of examples.

Work order creation during maintenance plan execution depends on work rules and asset conditions. If conditions are not met, no work order is generated. The number of work rules and asset conditions configured per plan directly impacts heap consumption during batch processing.

The following table summarizes examples of tested scenarios. Use these results as guidelines when configuring work rules and asset conditions for your maintenance plan processes.

To avoid Salesforce Governor Limit, distribute Maintenance Plans across multiple processes based on the following table combinations.

Asset 360 maintenance plan processing runs as Apex batch jobs on the Salesforce platform. The following platform constraints apply and should be considered when planning large-scale maintenance plan processing.

A maximum of five Apex batch jobs can run concurrently on the Salesforce platform. Any additional jobs are automatically queued by Salesforce until resources become available. Job sequencing and queue management are controlled by Salesforce and are not configurable by users. These constraints affect overall execution time and resource availability, particularly for organizations with large numbers of maintenance plans or multiple simultaneous maintenance plan processes.

Rather than specifying a fixed number of concurrent processes, it is recommended to organize maintenance plan processes using logical separation, grouping plans by function, asset type, or business unit. This approach prevents any single process from being overloaded, reduces the risk of hitting platform limits during batch execution, and maintains predictable and efficient execution across all processes.

Avoid consolidating all maintenance plans into a single process, as this increases the likelihood of exceeding batch size and heap size thresholds.

A new threshold limit setting is introduced during Asset 360 package upgrades. After upgrading, you must review and update your maintenance plan process configurations to ensure they comply with the recommended limits described on this page.