After filling out the initial configurations of a Plan, it’s time to set up how Work Orders will be created from that Plan.
Important note: If you want to learn more about creating Plans, access this article.
Opening Mode
The opening of WOs from a plan can be automatic or manual:
Automatic: The WO is generated as soon as the execution is triggered.
Manual: A notification is sent to those responsible for the plan. A user with permission must click "Generate" to create the WO.
Schedule New Work Orders
By selecting this option, a new WO will only be generated after all Work Orders from the previous cycle have been completed.
Eligible Days of the Week
Here, you select the days of the week on which the Plan execution can occur.
An execution only happens on days you have marked as active. If it is scheduled for an inactive day, it will automatically be rescheduled for the next active day, without affecting the delay rate.
Eligible Day of the Month
Sets a fixed day of the month to generate the WO. If necessary, the WO will be generated afterward, respecting this date, without counting as a delay.
Important note: This option is only available for Plans that have cycles with calendar conditionals where the minimum recurrence is more than 30 days.
Allowed Month
In annual plans, you can set a fixed month for execution. It follows the same rules as the allowed days of the month.
Creation Date
If a Plan has two recurrences (calendar and metric), it will always follow the rule of the recurrence that triggered it.
If triggered by calendar, it will follow the time rules.
If triggered by metric, it will follow the metric values.
When Triggered by Calendar
The Creation Date defines how far in advance the WO will be generated before the cycle’s scheduled execution date.
0 days → The WO will be generated on the same day as the execution.
3 days → The WO will be generated 3 days before the execution.
Example: If a cycle occurs every 30 days and the Creation Date is 3 days, the WO will be created 3 days before the execution.
By default, the initial value will always be 0 (the WO is generated on the exact day of the recurrence).
When Triggered by Metric
The Creation Value by Metric defines how many units before the metric reaches the trigger value the WO will be generated.
If the cycle occurs every 500 hours and the Creation Value is 50 hours, the WO will be generated when the metric reaches 450h.
The plan does not require exact precision: if the metric surpasses 450h (for example: 460h, 500h, or even 1000h), the WO will be generated as soon as there is a reading above that value.
Important notes:
The WO will only be generated when there is a reading above the defined value.
If the metric does not have frequent readings, triggering the Work Order can be compromised. We recommend using plans only with metrics that have a high frequency of readings.
Due Date
The Due Date defines until when the WO can be completed.
If a Plan has two recurrences, it will follow whichever recurrence triggered it (calendar or metric).
When Triggered by Calendar
The Due Date determines the final deadline for completing the WO, counted from the triggering date.
0 → The WO is due on the same day it is triggered.
5 days → The WO is due 5 days after the trigger date.
This date will automatically populate the Due Date field of the generated WO.
When Triggered by Metric
The Metric Due Value defines how long the WO can be completed, based on the metric’s progression.
If a cycle occurs every 500 hours and the Due Value is 100 hours, the WO must be completed before the metric reaches 600h.
If the WO is not finished by this limit, the tolerance rules (if any) will be applied.
Within this field, you can also add an automatic due date. Automatic Due Date automatically fills the Due Date field of the generated WO.
If the plan is triggered by metric, only metric values affect tolerances, not the automatic Due Date.
Tolerances
Delay Tolerance
Defines the maximum time a WO can be late for completion, considering:
Plans triggered by calendar: The deadline is based on the WO’s Due Date, defined at the time of creation.
Plans triggered by metric: The deadline is based on the Metric Due Value, meaning the WO must be completed before the metric reaches a specific value. If the WO is not finished within the set timeframe, tolerance rules will apply, which can affect the plan’s next executions.
Early Completion Tolerance
Defines the maximum time a WO can be completed before the planned date, always considering the due date of the generated WO.
Rate After Delay Tolerance
If the WO exceeds the defined tolerance, the next executions will be postponed according to the stipulated rate.
Rate After Early Completion Tolerance
If the WO is completed before the early completion tolerance limit, the next executions will be brought forward according to the stipulated rate.