Routings
A routing lists the operations that make a product.
Before you start
You need build.engineering.manage.
Operation fields
| Field | Meaning |
|---|
| Sequence | The order of the operation, for example 10, 20. |
| Name | For example "Cut", "Weld", "Assemble". |
| Work centre | Where it runs. |
| Setup (min), Run per unit (min), Move (min) | Standard times. |
| Yield % | Expected good output. |
| Can start when | The previous operation is done, or has started. |
| Reports output | Exactly one operation receives the output. Turning it on turns it off elsewhere. If none is marked, the last one does. |
| Instructions | Text shown at the station. Use Add instruction files for files and drawings. |
| Check form, When, Units between checks | A check at start, every N units, or at finish. |
| Required qualification | Warned or blocked, as set in Build settings. |
| Outside process | A vendor and Lead days. |
Steps
- Open Engineering, then Routings. Create a routing or a new revision.
- Add and fill in each operation.
- Save, then click Release revision.
| Message | Action |
|---|
| Fix the marked operations before saving. | Correct the operations marked in red. |
| Not saved: the server found problems. | Correct and save again. |
| Could not save the routing. | Try again. |