Routings and operation types

This page describes the sub-modules of src/cluster_erp/modules/production/ that define how a product is made: routings/ (with the scaffold in routings/scaffold.py), operation_types/, routing_templates/ (with cut technology rules), and component_allocations/. A routing (Routing) is the operation sequence of one product breakdown. Its component allocations tie BOM items and other inputs to operations; together they form the operation BOM (eBOM). The BOM side is on the BOM module.

Scope and source¶

• Defined in: the models.py, schemas.py, services.py, and routes.py of the four sub-modules, routings/scaffold.py (RoutingScaffolder), and routing_templates/metadata.py.
• Count: 9 tables; 28 routing routes, 8 operation type routes, 16 routing template and rule routes, and 6 allocation routes (@router. and @rules_router. decorators).

Routing fields¶

Routing statuses¶

A routing moves from draft to active to obsolete (src/cluster_erp/modules/production/routings/services.py:44-48). Activation is refused while blockers remain: an operation without a work center, without an operation type, or with zero run time per unit, or a prep operation without an operation type (src/cluster_erp/modules/production/routings/services.py:541-599, src/cluster_erp/modules/production/routings/services.py:610-649). GET /routings/{routing_id}/readiness returns these blockers (src/cluster_erp/modules/production/routings/routes.py:319). When a new BOM version becomes active, live routings of the same breakdown are marked stale (src/cluster_erp/modules/production/module.py:195-224).

eBOM scaffold¶

The scaffold derives a routing from the BOM of one product breakdown. The diagram shows the plan and apply path.

flowchart TD
 P["POST /routings/scaffold-plan with product, model, version"] --> T["load_tree: GetBomScaffoldTree"]
 T --> F["flatten_inputs: phantom children lifted, qty multiplied"]
 F --> J["final joining operation with material inputs"]
 F --> C["cut prep for make_from_stock items"]
 J --> TP["resolve_template: RoutingTemplate by category and material type"]
 C --> CR["cut_rules: CutTechnologyRule by material and stock form"]
 TP --> WC["wc_candidates from work center capabilities"]
 CR --> WC
 WC --> Q["plan with questions and plan_hash"]
 Q --> A["POST /routings/scaffold-apply with answers"]
 A --> H["plan_hash recomputed from current BOM"]
 H --> M["Routing, RoutingOperation, PrepOperation, ComponentAllocation rows"]
 M --> I["CreateScaffoldIntermediate for operation outputs"]

In prose: scaffold-plan is a dry run that needs the full product breakdown (src/cluster_erp/modules/production/routings/routes.py:155-206). The scaffolder reads the BOM tree with GetBomScaffoldTree (src/cluster_erp/modules/production/routings/scaffold.py:177-217). Non-phantom items become material inputs of one final joining operation; phantom items are never inputs, and their children are lifted with the phantom's quantity multiplied (src/cluster_erp/modules/production/routings/scaffold.py:8-12, src/cluster_erp/modules/production/routings/scaffold.py:247-335). A make-from-stock item with length stock and a cut length gets a mandatory cut prep step; sheet stock gets a 2D cut candidate (src/cluster_erp/modules/production/routings/scaffold.py:13-15, src/cluster_erp/modules/production/routings/scaffold.py:336-348). A routing template that matches the product's category and material type supplies the operation sequence; two equally specific templates are refused (src/cluster_erp/modules/production/routings/scaffold.py:22-28, src/cluster_erp/modules/production/routings/scaffold.py:470-540). A cut technology rule answers the cut question (src/cluster_erp/modules/production/routings/scaffold.py:29-31, src/cluster_erp/modules/production/routings/scaffold.py:589-622). Work centers come only from declared capabilities (src/cluster_erp/modules/production/routings/scaffold.py:16-21, src/cluster_erp/modules/production/routings/scaffold.py:388-469). Process operations are never created automatically unless a template declares them (src/cluster_erp/modules/production/routings/scaffold.py:22-24). The plan carries a plan_hash over the breakdown, BOM version, and item quantities (src/cluster_erp/modules/production/routings/scaffold.py:41-43, src/cluster_erp/modules/production/routings/scaffold.py:218-246).

scaffold-apply writes the plan in one transaction. A changed BOM gives a 409, a missing required answer a 422, and an existing live routing on the breakdown a 409 (src/cluster_erp/modules/production/routings/routes.py:207-262, src/cluster_erp/modules/production/routings/scaffold.py:1038-1354). When an operation has an output, the scaffolder asks products_and_services to create or reuse an intermediate product with CreateScaffoldIntermediate (src/cluster_erp/modules/production/routings/scaffold.py:2234). Tree mode plans and applies sub-assemblies all or nothing (src/cluster_erp/modules/production/routings/scaffold.py:962-1037, src/cluster_erp/modules/production/routings/scaffold.py:1355-1425). copy-to deep-copies a routing onto another breakdown and re-binds allocations to the target's active BOM; unmatched rows are reported (src/cluster_erp/modules/production/routings/scaffold.py:35-39, src/cluster_erp/modules/production/routings/scaffold.py:2077-2460).

Routes¶

Constraints and validation¶

• A component allocation is unique per BOM item and operation, per operation and source operation, and per operation and product, among live rows (src/cluster_erp/modules/production/component_allocations/models.py:27-56).
• The bom module reads allocations through GetComponentAllocations to fill operation type and work center in its explosion (src/cluster_erp/modules/production/module.py:145-147).

Discrepancies¶

Terms introduced¶

Related pages¶

• Production module
• BOM module
• Work centers and capacity
• Production orders and versions

Verified against commit 92f8051 on 2026-11-13.