Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Line-level state is mainly reflecting the state of the main machine. However, there are some line-wide activities which should impact reporting and in some sense ‘Ignore’ what’s happening on the main machine

...

You can incorporate this statuses in any rules you like, but the simplest configuration assigns a line-level ‘changeover' downtime, when the value of the signal is > 0, or separate states for 1 and 2:

...

Future improvements:
You will be able to set a changeover type, and take into account the type of the changeover in the line-level rule

...

You can incorporate this statuses in any rules you like, but the simplest configuration assigns a line-level ‘cleaning' downtime, when the value of the signal is > 0, or separate states for 1 = 1, like in the example below:

...

Info

Coming in 2023

Similarly to the changeover described above, activitiey ‘Maintenance’ will trigger a tag value which can be used to influence line state

We plan to improve user experience for configuring line state. vs schedule behaviour and create a single view in line settings which with just a single checkbox will allow you to:
- Enable / Disable “NoPlan” state
- Enable / Disable “NoWorkHours” state
- Enable “NoWorkHours” enforcement (regardless of orders)
- Enable / Disable “Changeover”
- Enable / Disable “Cleaning”

...