Instruction tasks

An instruction task comes from an instruction. For example: According to an instruction a measurement must be executed after every series of 100 produced units. After every series of 100 produced units, the instruction generates an task to execute the measurement.

You can add a trigger, which will trigger this instruction (sheet) during job execution, for all instructions and instruction sheets. An exception to this is the document instruction, which is always visible by default.

The triggers can be based on:

  • Time: Several time-based combinations are possible, ranging from x minutes after start to interval based, every hour or shift based.
  • Quantity: Responds to the quantity of produced or rejected items during production. This can be job or run (if the job is executed in several steps) based.

    For example: After 100 rejected units a setup instruction is triggered for the operator to reset the machine.

  • Tag: Using a signal or a counter tag. A signal tag responds to the HIGH or LOW signal, a counter tag responds to reaching a certain value or a multitude of it.

    For example: A counter tag will keep track of the number of secondary outputs. Once the counter tag reaches the value 50, the trigger can generate the instruction.

  • Alarm: At activation and/or deactivation of an alarm.

    To add an alarm trigger based on an instruction, you must configure an alert ID to the alarm.

    For example: you can draw up an instruction that explains what to do if the oil level is too low. You configure this alarm with Alarm ID: Alarm OIL. The instruction is triggered when the alarm is active.

  • LPN: You can add a instruction that pilots what to do if a new LPN is created or an LPN is closed. You can also configure how many LPNs need to be triggered in the instruction.
  • Serial Number: You can add an instruction that pilots what to do if a new serial number is created, intermediately registered or when a serial number is completed. You can also configure how many serial numbers need to be triggered in the instruction.

If these tasks will overlap, overlap settings are available to avoid the generation of new tasks until the previous one is finished, to suppress tasks for a certain time span or to just allow the overlap without restrictions.