Targets

Targets are a way to set production goals and monitor the progress in real time.

Setup

See also Targets Interface.

A target is set on an Article or Article Group and for each target we also specify the number of produced pieces that we aim for.

We then pick out one or more Operations or Operation Groups as checkpoints in the route where we will keep count.

The articles are connected with operations via Routes. If the article has an associated route, that will be pre-selected in the route dropdown, otherwise you will have to select the routes by hand.

If only one route is selected, the checkpoints will be the operations themselves. If multiple routes are selected, you will instead have a choice of operation groups. The list of operation group is retrieved from the operations in the currently selected routes.

If you are only interested in number of completed pieces, then you would put a target on the unloading operation.

Schedules

See also: Schedule Editor Interface.

To know at what amount of production is expected at each point in the day, we connect the checkpoints with a schedule. For example, if we have production between 8 and 16, then we would create a target schedule with 0% expected at 8 and 100% expected at 16. You can also specify the points in-between, to account for the fact that there is no production during breaks. This could look like

Time Percentage
8:00 0%
12:00 50%
12:30 50%
16:00 100%

Here our schedule takes into account that we have a lunch break of 30 minutes where there is no production. Each checkpoint can optionally have a schedule connected with it, otherwise the default schedule of the target will be used.

There are some limitation that apply when creating a schedule

  • First point must start at 0%
  • First point cannot be at or after midnight (24:00).
  • Last point must end at 100%
  • Last point cannot be more than 24 hours after the first point.
  • Each point must have the same or higher target percentage than the previous, it is for example not allowed to go from 50% at 12:00 to 40% at 12:30.

When viewing the history of a target, the target result belongs to the day it started in. For example, if your target starts at 22:00 on the 1st and goes until 06:00 the 2nd, then the result of the target will be associated with the 1st.

Timeline

When a target is set up, there are some things happening at certain times:

Start of the schedule

When the clock hits the first time specified in the schedule, the checkpoint counter will reset to 0 and data from the previous day will be cleared.

Completed operations

Operations that match the checkpoint (operation, article and optionally user group / station group) will increase the checkpoint counter. This value is updated live and is represented by the bar on the Target Status view.

Note that rework operations (repairs) do not contribute to the counter increasing.

Minute-by-minute logs

Every minute, the checkpoint counters will be logged in order to provide a historical value. The system will automatically fill in any missed minutes with the most recent value.

End of the schedule

When clock hits the last time specified in the schedule, the target result will be archived. This result can later be viewed on the target status page by selecting a different date. The checkpoint will not reset until the clock reaches the next specified start time.

Automatic recalculation

When some data that the target depends on is changing, the system will automatically schedule a recalculation of the target data in the next few minutes. If multiple dependency changes are done in short order, the recalculation will be postponed until the depending data stops changing.

Change that will trigger a recalculation are

  • Changing the target configuration such as the operation, article or user/station group filters.
  • Changing a schedule that is used as target default or for a specified checkpoint. Only changes to the schedule start or end time triggers a recalculation.
  • Changes to a user group used as a filter on a target
  • Changes to a station group used as a filter on a target

Trend

The trend shows us if the production pace is speeding up or slowing down.

Example:

The Trend Interval setting is put to 15 minutes. System retrieves the number of pieces produced 15 minutes ago, along with the predicted production quantity 15 minutes ago. System calculates that at that time we had produced 90% of what was predicted.

This value is then compared to the latest value we have, which shows us that we have currently produced 105% of what is predicted right now. The trend is the difference between these two numbers, and gives us +15%.

When the trend is positive, we are catching up to or surpassing the predicted production.
When the trend is negative, we have slowed down the production rate relative to earlier.