Scheduling Work Orders

Schedule a work order forward from a start date or backward from its due date, with its feeder work orders, and follow its planned dates, Late start and schedule history.

Most plants plan the week on paper or in a spreadsheet: which orders start Monday, when the subassemblies come back from the outside wrappers, and whether the order due on the 8th makes it. The plan is out of date the first time a routing changes or someone adds a holiday. In Threaded, you schedule a work order once, and Threaded dates every stop on its route from the routing’s days and the plant calendar. When the routing or the calendar changes, the dates move with it, and the order says so.

#What it is

  • Schedule. A work order is scheduled one of two ways:
    • Start on a date: Threaded dates its stops forward from that day.
    • Finish by a date: Threaded finds the latest start that still finishes on or before that day. It’s the order’s due date unless you pick another.
  • Planned start and Planned finish. The first day of its first stop, and the day it’s done. The planned finish is the day a parent order can use it.
  • Scheduled. A work order with dates that hasn’t started. It waits in its station’s Up next like any not-started order.
  • Feeder work orders. When you schedule an order, its feeder work orders that haven’t started are dated with it, so each one finishes by the day its parent needs it. Their page says Scheduled with wo-1042, linked to the order that dates them.
  • Originally. When an order starts, Threaded keeps the dates it had then. If its planned finish later moves, the header shows the first one beside it, as Originally Tue Dec 8.
  • Late start. A Scheduled order whose planned start has passed in the plant’s time zone, and that still hasn’t started.
  • Dates moved. A routing change or a plant calendar change moved the order’s dates since anyone last scheduled it.

#Rules

  • Owners and Editors schedule work orders, clear a schedule and keep moved dates. Operators and View All members see the dates but not Schedule. Operators can still start orders.
  • Dates count working days on the plant calendar: its workdays and holidays, in its time zone. Until someone saves a calendar, dates use the default (UTC, Monday to Friday, no holidays), and the Schedule dialog says so.
  • Each stop is dated from its routing’s days. A stop runs:
    • on working days only, like most work in the plant;
    • weekends included: on every calendar day, such as curing or an outside service.
  • A stop’s date is the day its work happens. Work that runs overnight, such as an oven cure, is done before the next working day starts, so it shows the day it starts.
  • A routing with no days on its stops is scheduled with dates only: the order gets a start and finish, its stops don’t.
  • Finish by never starts a stretch that includes weekends on a non-working day. If the latest start that fits would, the order starts on the working day before.
  • A date more than 2 years before or after today is refused, and so is a due date more than 2 years away used as the finish date.
  • Scheduling into the past is allowed, for a plan that’s already running. The dialog warns.
  • Move its feeder work orders too is on by default. With it on, every not-started feeder work order is dated with the order, even one you’d scheduled on its own. When off, they keep their dates and are scheduled on their own from then on.
  • Feeder work orders that have started aren’t moved. A later started feeder still holds back an order scheduled with Start on, and an order scheduled with Finish by warns when a started feeder finishes too late.
  • A started order can be rescheduled, but its schedule can’t be cleared. Its original dates stay. Its feeder work orders move only if they haven’t started.
  • Archived orders, and orders whose part may not be in the current plant, can’t be scheduled.
  • When an order starts, Threaded first re-dates it for today’s plant, then keeps those dates as its original dates. If that moved them, the message after Start says so.
  • Undo start puts a scheduled order back to Scheduled, re-dated for the current plant. An order started without a schedule goes back to Not started with no dates.
  • Changing the due date of an order scheduled with Finish by its due date moves it to the new due date, with its feeder work orders. An order scheduled any other way keeps its dates, and the field warns if it now finishes after its due date.
  • A routing change or a plant calendar save re-dates unfinished orders shortly after. Their original dates never move.
  • A schedule that would change nothing changes nothing, so it doesn’t clear Dates moved. Use Keep these dates for that.
  • Printed travelers show the planned dates with the day they were printed. A re-date after that doesn’t change the paper: reprint it.
  • Your organization needs Run turned on. See Feature Access and Billing.

#In the app

#Schedule a work order

  1. Open the work order and click Schedule in the header. It reads Schedule beside Start, which stays the main action before Start.
  2. Under How, choose Start on or Finish by. Finish by starts with the order’s due date filled in.
  3. Pick the date. With Finish by, you can leave it blank to finish by the due date.
  4. Optionally add a Reason. It shows in the order’s schedule history.
  5. If the order has feeder work orders that haven’t started, leave Move its feeder work orders too on to date them with it.
  6. Under What changes, check the dates. Each order it moves has a line, such as wo-1042 · Rod 9ft · Mon Nov 23 – Tue Dec 8 (was Mon Nov 16 – Tue Dec 1), and any warnings follow. Schedule waits until the dates are worked out.
  7. Click Schedule, or Reschedule when the order already has dates.

The warnings say what to look at, such as Finishes Wed Dec 9, after its due date Tue Dec 8., wo-1043 finishes Tue Nov 24, after wo-1042 needs it on Mon Nov 23., or Starts Mon Nov 9, before today. You can schedule anyway.

#Clear a schedule

On a Scheduled order that hasn’t started, open Schedule and click Clear schedule. What changes says what it clears, such as Clears dates on wo-1042 and 3 feeder work orders. Click Clear schedule to confirm. The order goes back to Not started, and so do the feeder work orders it dated, unless you turn off Clear its feeder work orders too. Feeder work orders you scheduled on their own keep their dates.

#Schedule when you create

In Create work order, choose Schedule under When, then Start on or Finish by and a date. Click Create and schedule. Its feeder work orders are created with it and dated with it. Create has no preview: when the new schedule has warnings, the created message lists them, each with a link to the order. See The Floor.

#Read the dates

The work order header shows:

  • Due Tue Dec 8 · Planned finish Wed Dec 9, with 1 day after due beside the planned finish when it’s late for its due date.
  • Originally Tue Dec 8 when the order has started and its planned finish has moved since.
  • Not scheduled when the order has no dates yet.
  • Scheduled with wo-1042 on a feeder work order its parent dates.
  • Late start beside the order’s status.

Needs attention says Should have started Mon Nov 23 for a Late start, and Planned to finish 1 day after its due date when it’s late.

On the Route view, each stop shows its planned dates:

  • Planned Tue Nov 24, or Planned Tue Nov 24 – Wed Nov 25;
  • Planned Thu Nov 26 – Wed Dec 2 · weekends included.

A Scheduled order shows its stops and their dates before it starts, with Planned dates for each stop. Its units are made when it starts. A stop with no days in the routing shows no date. When no stop has days, only the order is dated, and the Route view says No units yet. They’re made when the order starts.

In a station’s Up next, each row shows Planned Mon Nov 23 and Late start when it applies. An order with no dates shows Due Tue Dec 8.

#Dates moved and Keep these dates

When a plant update or a calendar save moves an order’s dates, its header says so, such as Dates moved Mon Nov 16: plant calendar changed. Planned finish Tue Dec 8 → Wed Dec 9, or routing changed for a plant update. The note stays until someone reschedules the order, or an Owner or Editor clicks Keep these dates to accept the new dates as they are. If someone else already kept or rescheduled them, the note just goes away.

#Schedule history

The Route view’s Schedule history lists every change to the order’s schedule, newest first: When, Who, the Change (such as Finish Tue Dec 8 → Wed Dec 9, Due Tue Dec 8 → Thu Dec 10, Started or Start undone), the Cause and the Reason. Changes Threaded made after a plant update or a calendar save show Threaded as who made them. A feeder work order that stopped being dated by its parent reads Now scheduled on its own, with the cause wo-1042 archived or wo-1042 no longer schedules it. The table shows the latest 50 changes to the schedule, and says so when there are more.

#Archive an order that dates feeder work orders

When you archive an order and untick a feeder work order to keep it running, the dialog says it Keeps its dates and is scheduled on its own. The message after Archive names those orders.

#Troubleshooting

“Plant calendar not saved yet.” Dates use the default calendar. Owners and Editors click Set up calendar; everyone else asks one of them. See The Plant Calendar.

“The plant calendar has no working day near these dates.” The calendar has no workday close to the date you picked. Owners and Editors get Open plant calendar to check its workdays and holidays; everyone else is asked to have an Owner or Editor check them.

“wo-1042 has started. Undo Start to clear its schedule.” A started order can’t be cleared. Reschedule it, or undo its start first.

“wo-1042 is archived. Restore it to schedule it.” Restore the order, then schedule it.

“wo-1042’s part may not be in the current plant, so it can’t be scheduled.” Check that its part and first station are in the plant.

“This work order isn’t available.” It was deleted, or it belongs to another organization.

“You can’t schedule work orders. Ask an owner or editor.” Your role changed since the page loaded, for example to View All. Ask an Owner or Editor to schedule it, or to change your role. Start and Undo start say the same for their roles: “You can’t start work orders. Ask an owner, editor or operator.”

“Couldn’t work out the dates.” The dates couldn’t be worked out right now, for example after a dropped connection. Click Try again. If Schedule itself fails the same way, click it again.

“Pick a date within 2 years of today.” Pick a closer date.

#From the CLI or API

From the threaded CLI, threaded task work-order:schedule --work-order WO-1042 (its number or uuid) schedules an order with --forward <date> or --backward <date|due>, clears it with --clear, leaves its feeders with --no-feeders, and shows what would move with --preview. work-order:create --forward <date> or --backward <date|due> creates an order with a schedule, work-order:bulk-create creates many, and work-order:get shows its dates and history. See Work Orders, Units and Records.

With threaded api call:

  • run_format_work_orders_schedule (POST /api/v2/run-format/work-orders/<uuid>/schedule/): mode is forward, backward or none (clear), with anchor (the date; for backward, the due date when left out), reason and include_feeders (default true). It returns the order, moved (each order it moved, with old and new dates) and warnings.
  • run_format_work_orders_schedule_preview (POST …/schedule/preview/): the same body; returns moved and warnings and changes nothing.
  • run_format_work_orders_keep_dates (POST …/keep-dates/): Keep these dates.
  • run_format_work_orders_retrieve: the order’s planned_start, planned_finish, baseline_start and baseline_finish (its original dates), schedule_mode (none, forward, backward, or parent for a feeder its parent dates, named in scheduled_with), late_start, finishes_after_due, dates_moved, and its history: schedule_events holds the latest 50 changes, oldest first, and schedule_events_has_more is true when there are older ones. start_events lists each Start and Undo Start.
  • run_format_work_order_stations_retrieve: each stop’s planned dates (start_date, end_date, schedule_runs).

Warning codes: late_for_due_date, feeder_late, starts_in_past, no_offsets (no stop dates), and from a due-date change, dates_not_moved and no_due_date.

Common errors:

  • 400 on anchor: Pick a start date., Pick a finish date, or set a due date first., Pick a date within 2 years of today., or The plant calendar has no working day near these dates. Check its workdays and holidays.
  • 409 started_clear, archived or part_missing, with the messages under Troubleshooting.
  • 403: scheduling needs an Owner or Editor.
  • 404: the order doesn’t exist, or belongs to another organization.

#Why this matters

A schedule that dates every stop from the routing and the plant calendar is one the floor can trust: Monday’s starts are on Up next, the subassemblies are timed to arrive when the parent needs them, and a late order says so before it’s late. When the routing or the calendar changes, the dates follow, and Dates moved, Originally and the schedule history show what changed and why, so planners spend their time deciding what to do about a late order rather than finding it.