Every job on the board knows when it will finish and how that compares with its due date. The Schedule tells you when a job slips, when an operator reports a problem and when a machine goes down, and the alerts clear themselves once the reason is gone.
On time, at risk or late#
A job's spare time is the working time between its planned finish and its due date, less the finish buffer. From it:
| Risk | When |
|---|---|
| On time | At least the at-risk threshold to spare (4 working hours unless you change it). |
| At risk | Some time to spare, but less than the threshold. |
| Late | Planned to finish after its due date. |
| Unknown | The job has no due date, or one of its steps has only an approximate time on the way to the finish. |
Spare time and lateness are counted in working hours, and shown in clock time too ("2.5 working h late · 18 h"), so a weekend doesn't make a job look later than it is. Risk is worked out again after every change to the plan and every report from the floor.
Where due dates come from#
A job's due date is the earliest due date of its items (an item's Due property), else the imposition job's due date from its Order card; see Item properties. A date without a time means the end of the working day (see Schedule settings), in your team's time zone. The Schedule never changes due dates: change them in Imposition.
Alerts#
| Alert | When | Where you see it |
|---|---|---|
| At risk | A job's spare time drops below the at-risk threshold. | Bell, team home |
| Late | A job is planned to finish after its due date. | Bell, message, team home |
| Ready check cleared | A ready check passes, for example a proof is approved. | Bell, message |
| Ready check failed | A proof is rejected or preflight fails. | Bell, message |
| Problem reported | An operator reports a problem. | Bell, message, the machine's station |
| Machine down | An operator reports a machine down. | Bell, message, team home |
| Overrun | A step runs well over its estimate. | Bell, the machine's station |
| Queue changed | A planner changes what a station runs next. | The machine's station |
| Layout changed | A job's layout changed or was removed after production started. | Bell, the job's panel |
| Proposal | A suggestion to move steps is ready, for example after a machine goes down. | Bell |
An alert appears once per job or machine and clears itself when its reason is gone: a late job that is on time again, a machine back up, a problem resolved.
Where you see them#
- The board: the late and at-risk chips in the header, and each job's risk in its panel.
- Team home: Needs attention shows Late jobs, Jobs at risk, a machine that is down ("Press 2 is down", or Machines down when there are several) and Ready to schedule, each with its count and a link to the board.
- Your own systems: the API lists open alerts and acknowledges them (see Schedule API).
- Stations: a machine's station shows the alerts about that machine, such as a queue a planner changed or a step running over.
Email and proposals#
Planned: Bell, email and proposals
A bell on the board lists the open alerts, where you can acknowledge them. Machine down and Late alerts will also be emailed, a late job at most once a day, to the people chosen in Schedule settings. When a machine goes down, a re-route proposal such as "Press 2 down (ETA 13:00): move 4 steps to Press 1 → 2 fewer late" comes with Preview and Dismiss. It is never applied by itself.