Work Orders¶
A Work Order is a concrete unit of scheduled, trackable work — either production work for one Manufacturing Order item, or maintenance work on an asset. Work Order Templates standardize how a recurring Work Order type is set up, and Job Cards record shop-floor checks and sign-offs against a Work Order.
Accessing Work Orders¶
Open the Planning sidebar and select Work Orders for the order list, or Work Order Templates to manage templates.
Work Order Templates¶
Click New Template and fill in:
| Field | Description |
|---|---|
| Name | Required |
| Default Routing | Optional — a Workflow Template (must apply to Work Orders) that Work Orders created from this template will follow by default |
The template list shows each template's name and its default routing (or "—"). Use the row's Delete action to remove a template.
Creating a Work Order¶
From the Work Orders list, click New Work Order, choose a Type, and fill in the rest:
Manufacturing (the default):
| Field | Description |
|---|---|
| WO Number | Required — a unique identifier (e.g. WO-0001) |
| Manufacturing Order | Required — pick the MO this Work Order fulfils |
| Item | Required — pick which item on that MO this Work Order is for. Options populate once an MO is selected |
| Work Order Template | Optional |
The selected item's SKU is shown for confirmation before saving.
Maintenance:
| Field | Description |
|---|---|
| WO Number | Required — a unique identifier |
| Asset | Required — the machine this maintenance work is for |
| Maintenance Plan | Optional — link this Work Order to one of the asset's Maintenance Plans so completing it also logs the maintenance |
| Work Order Template | Optional |
You can also raise a Maintenance Work Order directly from an asset's own Maintenance Plans card, or from the fleet-wide Maintenance page — see Maintenance — or report an unplanned issue straight from the asset's page, see Reporting an unplanned issue.
The order list shows each Work Order's number (click to open its detail page), linked MO or Asset, SKU, status, Priority, and routing progress. Use the search box to filter by WO number, MO number, SKU, or asset name.
Description & Priority¶
Every Work Order can carry a free-text Description and a Priority (Low / Medium / High / Critical) — both shown on the detail page and editable there alongside its other details. Reported issues fill these in automatically; you can add or adjust them on any Work Order.
Status values¶
| Status | Meaning |
|---|---|
| Planned | Created, not yet started |
| In Progress | Actively being worked |
| Completed | Finished |
| Cancelled | No longer being produced |
How routing gets attached¶
Creating a Manufacturing Work Order by hand automatically attaches a routing (a sequence of steps from a Workflow Template) if one can be resolved, in this order of preference:
- A routing set directly on the Manufacturing Order item.
- The Manufacturing Order's own Workflow Template, if it has one (see MO Templates) — a legacy fallback kept for existing organisations; new setups should prefer setting the routing directly on the item instead, since that same MO-level template is also now used for the MO's own lifecycle (see Routing).
- The default routing on the Work Order Template you chose when creating the Work Order.
Work Orders auto-generated by a Manufacturing Order's own routing (a Generate Work Orders step, see Workflow Templates) only ever pick up a routing from the item's own Routing field — never from the Manufacturing Order's own template, since that column means something different for MO-level routing now.
A Maintenance Work Order only picks up a routing from its Work Order Template's default routing, if one was chosen — there's no Manufacturing Order to inherit from.
If none of these apply, the Work Order is created successfully with no routing — this is a normal state, not an error, and shows as No routing configured on the detail page.
Completing a Maintenance Work Order¶
Marking a Maintenance Work Order Completed — either by finishing the last step of its routing, or by setting its Status directly if it has no routing — automatically records the maintenance against its linked Maintenance Plan (the same effect as clicking Log Performed on the plan) and clears any related overdue alert. A Maintenance Work Order with no Maintenance Plan attached simply closes, with nothing further to record.
Tracking routing progress¶
Open a Work Order to see its details (SKU or Asset/Maintenance Plan depending on its type, planned quantity, scheduled dates) and, if it has a routing attached, its progress through that routing's steps.
Each step shows its position, name, type, and status (Pending, Active, or Completed). The one active step is highlighted:
- If it's a Task step, a Complete Step button lets you mark it done and move the routing on to the next step.
- Every other step type (Decision, Parallel Split, Parallel Join, Rework Loop) resolves itself automatically the instant the routing reaches it — see Workflow Templates for what each one does.
If the routing has finished every step, its status shows as Completed. A Routing Blocked badge appears next to the Work Order's own status if the routing genuinely gets stuck (for example, a Decision step whose condition can't be evaluated) — this is uncommon; most routings run straight through without ever showing Blocked.
Users with edit access can also update the Work Order's Planned Line, Planned Machine, and Status directly from the detail page.
Scheduling a Work Order¶
Users with edit access can set a Work Order's Scheduled Start and Scheduled End from its detail page, alongside Planned Line/Machine/Status. Both dates are shown on the detail page once set, and together they're what place the Work Order on the Gantt Chart — a Work Order missing either date won't appear there.
Actual dates & Linked Runs¶
Once shopfloor production starts, a Work Order's Actual Start and Actual End are derived automatically from the line runs linked to it — they're not set by hand. A run is linked to a Work Order from the run's own edit dialog on its production line; once linked, it shows up in the Linked Runs table on the Work Order's detail page (line, start, end, batch ID, status), and the Work Order's Actual Start/End update to reflect the earliest linked run's start and the latest one's end. Use a row's Unlink action to remove a run that was linked in error.
Dependencies¶
A Work Order can declare that it Depends on another Work Order, or that it Blocks another — these relationships are what draw the arrows between bars on the Gantt Chart.
From a Work Order's detail page, click Add Dependency and choose:
| Field | Description |
|---|---|
| Relationship | Depends on (this Work Order can't start until the other one reaches the chosen point) or Blocks (the other Work Order depends on this one) |
| Work Order | The other Work Order in the relationship |
| Dependency Type | Finish to Start, Start to Start, Finish to Finish, or Start to Finish — how the two Work Orders' schedules relate |
The Dependencies card lists everything this Work Order depends on and everything it blocks, each with the other Work Order's number and status. Use a row's Unlink action to remove a dependency that's no longer needed.
Job Cards¶
Job Cards are shop-floor checklists attached to a Work Order — use them to record checks, measurements, or sign-offs for a specific step of production.
From a Work Order's detail page, click New Job Card and fill in:
| Field | Description |
|---|---|
| Name | Required |
| Checklist Template | Required — the checklist structure this job card will follow |
| Maker | Required — the user group responsible for filling in the checklist |
| Checker | Optional — a user group that reviews the filled checklist |
| Approver | Optional — a user group that gives final sign-off |
Each Job Card in the list shows its name (a link to open and fill it in), current stage (Maker, Checker, Approver, or Issuer), and status. Job cards awaiting input take you to the fill screen when clicked; completed ones open in a read-only view. Use the row's Delete action to remove a job card that's no longer needed.
If the Work Order has a Planned Line or Machine set, opening a Job Card first prompts a QR scan to confirm you're at the right equipment — see QR-Scan Reconciliation.
Tip
Job Cards use the same checklist system as the rest of Enture — see the Checklist reference for how filling in, checking, and approving a checklist works once you open one from a Work Order.
Rejections and rework¶
If a Job Card is rejected (by its Checker or Approver) and it's tied to a routing step that has a Rework Target Seq configured (see Workflow Templates), the Work Order's routing automatically loops back to that step for another pass — no separate action needed. Once the configured number of attempts is used up, the routing continues on as normal instead of looping again. Rejecting a Job Card with no rework configured on its step is a plain rejection with no effect on the routing.
Attachments¶
Every Work Order has its own Attachments section for uploading drawings, GTPs, and other documents — see Attachments for how to use it.