Operation
An operation: a step of work that routings put in sequence.
What it is for
A Routing lists operations in sequence, and each routing line carries the resources and hours. The times on this screen (Queue Time Before, Setup Time, Run Time, Transit Time, Overall Time) are recorded on the operation; the routing does not take them over, the hours are entered per resource on the routing.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Operation | The short code. | Cannot be changed once saved. Required |
| Name | The name shown in lookups and on documents. | A clear name. Required |
| Queue Time Before | Recorded only. | Optional |
| Setup Time | Recorded only. | Optional |
| Run Time in (Hour) | Recorded only. | Optional |
| Transit Time | Recorded only. | Optional |
| Overall Time | Recorded only. | Optional |
| Operation Group | Its group. | Pick one |
How to configure it
There is nothing to configure beyond the fields above. Which fields are shown, required or hidden can be changed per company by the consultant in the screen configuration.
Scenarios
- A bakery mixes, bakes and packs. Three operations, then a routing with them in that order.
What it is connected to
- Routing - operations in sequence
- Manufacture Operation Confirmation - confirms one operation at a time
If something looks wrong
- "... already exists" on Save. Another operation already uses this code.