Operation Definitions
Operation Definitions are reusable operation templates in ianaiERP. Instead of re-entering the same step — with its work center, timing, and resources — on every routing that uses it, you define it once here and pull it onto any routing with a click.
Overview
- Standardization: Operation Definitions store a standard code, description, default work center, and default resource requirements for a recurring production step (e.g., CNC Machining, Custom Assembly).
- Faster Routing Creation: Once defined, an operation can be dropped onto any routing via Fill from definition instead of being built from scratch each time.
- Consistency at Scale: Changing a definition's defaults doesn't retroactively alter existing routings — each routing keeps its own values unless a field is deliberately left blank to inherit the definition's default.
Where to Access
- Users (admin / common) can access it via Manufacturing → Routing → Operation Definitions tab
- Click Add New to create a new operation definition
Key Attributes
Operation
| Field | Description |
|---|---|
| Code | Unique identifier for the operation (e.g., "CNCMACH"). |
| Operation Type | Classifies the operation (e.g., Manufacturing). |
| Active (toggle) | Controls whether this definition is available for selection on routings. |
| Description | The full name of the operation as shown to operators (e.g., "CNC Machining"). |
| Default Work Center | The work center applied to a routing operation when this definition is selected. |
| Effective From / To | The validity window during which this definition can be used. |
Standards
Applied to a routing operation when this definition is selected. Leave a field empty and the operation keeps its own value instead of inheriting the default.
| Field | Description |
|---|---|
| Setup Time | Default one-time preparation time for this operation, in minutes. |
| Runtime / Unit | Default processing time per individual unit, in minutes. |
| Overlap Quantity | Units to send ahead to the next operation before this one fully completes. |
| Completion Behavior | Manual requires an explicit sign-off to close the step; the alternative closes it automatically once a later operation is recorded — useful for unattended steps. |
| Reporting Basis | Defines what one Start/Complete action counts as — the whole order (Batch) or a single piece (Unit). |
| Default Work Instruction | The document (SOP, traveler, etc.) linked to this operation by default. |
| Recordable (checkbox) | Whether time/quantity reporting is expected at this step. |
| Count point (checkbox) | When enabled, completed quantity is reported and backflushed material is consumed at this operation. |
Simultaneous Resource Requirements
An operation definition isn't limited to a single resource — labor and machines can both be attached and are copied to every routing operation that uses this definition, scheduled together automatically.
| Field | Description |
|---|---|
| Role | The resource category (e.g., Labor, Primary Machine). |
| Target Type | Whether the requirement targets a Pool or a specific Resource. |
| Target | The specific labor pool, machine, or resource required. |
| Units | How many of that resource the step needs. |
| Setup min / Run min per unit | Time contributed by this specific resource, in minutes. |
| Basis | How usage is calculated (e.g., per Item). |
| Posting | Whether usage posts automatically or requires manual entry. |
List View Columns
The Operation Definitions list surfaces the key fields at a glance:
| Column | Description |
|---|---|
| Code | The operation's unique identifier. |
| Description | The operation's full name. |
| Type | The operation type (e.g., Manufacturing). |
| Default Work Center | The work center this operation defaults to. |
| Setup | Default setup time. |
| Run / Unit | Default run time per unit. |
| Resources | Count of simultaneous resource requirements attached. |
| Effective From / To | The definition's validity window. |
Key Functions
| Task | Path | Steps |
|---|---|---|
| Create an operation definition | Manufacturing → Routing → Operation Definitions → Add New | Enter Code, Description, and Operation Type → set Default Work Center → Save |
| Set default standards | On the definition, under Standards | Fill in Setup Time, Runtime/Unit, Completion Behavior, and Reporting Basis as defaults for any routing that uses this definition |
| Attach default resources | On the definition, click Resources | Add one or more Role/Target pairs (labor and/or machines) to be copied onto every routing operation using this definition |
| Use it on a routing | On a routing's operation line | Click Fill from definition to pull in the Code, Description, Work Center, Standards, and Resources in one step |
| Retire a definition | On the definition | Toggle Active off, or set an Effective To date, to stop it from being selectable on new routings |
Related Features
For more detailed information on advanced routing techniques and optimization, please refer to the specific sections in this documentation.