Configure the Execution Schedule tab on the Pipeline Monitor (PLM) record
- Last UpdatedApr 24, 2025
- 2 minute read
The Execution Schedule tab provides configuration for customized execution schedule of plm records. If this feature is enabled, a custom first execution time and an interval for subsequent executions of plm records can be set for each hour. When this option is disabled, the Pipeline Monitor (PLM) application runs every minute.
Notes: The Execution Schedule can change how often the PLM application runs. By default,
the PLM application runs every minute. Overriding the default schedule may affect
other periodical features of PLM because the new schedule is the shortest interval
at which PLM-related processes can run. These features include the following:
— Collecting term and instantaneous data
— Issuing integration alarms
— Data quality flags
— Deviation filtering
— Plotting
Moreover, when the interval between executions is more than one minute, the calculated
deviation (if any) is divided between the past minutes For more information, see Understand volume inputs to the Pipeline Monitor (PLM) region.
Voting limits for alarming are not supported when the Execution Schedule is configured
for a PLM point.
To configure the Execution Schedule tab
-
Open the plm record, and select the Execution Schedule tab. For more information on how to open the plm record, see Opening the Pipeline Monitoring (PLM) Record.
The Execution Schedule tab appears.

-
To enable the custom execution schedule of the plm record, select the Enable checkbox.
-
In the First Execution field, enter an integer between 0 to 59. This value indicates the minute from the top of the hour to execute the PLM for the first time in that hour. For example, if the First Execution is set to 2, the PLM runs on the second minute of each hour and then periodically after that as defined by the Execution Interval.
-
In the Execution Interval field, enter an integer between 1 to 59. This value indicates the interval in minutes between all subsequent runs of the PLM after the first run. For example, if the First Execution is set to 2, and the Execution Interval is set to 5, the PLM runs for the first time on the second minute of every hour, and then on minutes 7, 12, 17, and so on.