All Collections
Work Management
Plannes maintenance
What types of triggers can be added to a task?
What types of triggers can be added to a task?
CustomerSuccess Team avatar
Written by CustomerSuccess Team
Updated over a week ago

What types of triggers can be added to a task?

The system allows for 4 types of triggers with which a task can be associated, namely;

  • Date

  • Event

  • Each

  • When.

The operation of each of these will be explained next:

Type 1: Trigger by date

Refers to tasks that have a calendar-based schedule frequency. That is, they are performed routinely after a set period.

When selecting this type of trigger, the following fields must be completed:

  • Make Every: Refers to the time period between each trigger. It is an open field which allows only numerical values.

  • Frequency: Refers to the unit of measurement associated with the “Make Every” value entered in the previous step (e.g. days, weeks, months, etc.)

  • Repeat: An option that allows the user to set whether the task is repeated finitely or will remain active indefinitely.

  • Times: The number of times in which the planned maintenance task cycle is to be repeated (in case it has been established that it is repeated in a finite way).

  • Fixed Schedule: An option that allows the user to set a fixed time period between each trigger regardless of when the last task plan was completed. For example, if we have a task that has a trigger with a frequency of every 30 days and has a fixed schedule, it will not matter if the task is executed as scheduled or delayed since the following activations will be fixed every 30 days. On the other hand, if the fixed schedule option was not selected, the next activation will take place after 30 days, but from the date on which the previous task plan was executed.

Type 2: Trigger by Event

This type of trigger is used for ad-hoc tasks that do not comply with a particular activation frequency and is only activated through the execution of an unplanned task or event (the events are shown through a list previously uploaded to the system).

For example, events can be associated with situations such as some types of failures, requests, or activities that are not necessarily defined with a regular activation frequency, but the procedure to follow in case they occur is known.

Type 3: Trigger by counter/ accumulator meter reading

This trigger is activated by means of accumulator meters or counters (kilometers, hours, etc.). These types of triggers activate each time a certain meter accumulates to the predetermined value required for the execution of a task.

When selecting this type of meter, the following fields must be completed:

  • Frequency: Number of cycles that must be completed before the tasks is triggered.

  • Unit: The unit of measurement associated with the meter reading and task trigger (e.g. each, hours, miles, feet, Litres, etc.).

  • Until: Number of cycles in which the task will be executed (if the activity is executed indefinitely, it is left unlimited).

  • Fixed schedule: In a similar way to triggers by date, this option allows you to set the reading in which the next activation will be executed, which can be fixed (according to what is established) or taken from the last reading recorded at the time of executing the task.

Type 4: Trigger by preset meter reading limit

This type of trigger is activated by non-accumulator meters or non-counters that can fluctuate over time such as temperature, voltage, amperage, etc. These types of triggers activate when a meter reading is recorded that meets the established conditions or outside a certain parameter.

When selecting this type of meter, the following fields must be completed:

  • Unit: The unit of measurement associated with the meter reading and task trigger (e.g. each, hours, miles, feet, Litres, etc.).

  • Is equal to: List the conditions that can be established to define the parameters that the recorded reading must meet to trigger the activation of the task (e.g. equal to, greater than, lower than, etc.).

  • Value: The number that defines the numerical parameter to be considered for the activation of the task.

Did this answer your question?