Production module (production)

The production module in src/cluster_erp/modules/production/ covers manufacturing. It keeps work centers with their capabilities and hours, operation types, routings with operations and prep steps, routing templates, and component allocations that tie BOM items to operations. It creates production orders with components and operations, splits them into work orders, and places work orders on a scheduling board that respects working calendars. This page is the overview; the sub-topics have their own pages.

At a glance¶

What the module does¶

• Keeps work centers with parallel capacity units, working hours, a time zone, an owning organisation, and declared operation-type capabilities (src/cluster_erp/modules/production/work_centers/models.py:25-151).
• Keeps routings per product breakdown, with operations, prep operations, and component allocations, and derives them from the BOM with the scaffold wizard (src/cluster_erp/modules/production/routings/scaffold.py:1-43).
• Creates production orders that explode the BOM into components and copy the routing into operations (src/cluster_erp/modules/production/production_orders/services.py:147-438).
• Splits orders into work orders and executes them (src/cluster_erp/modules/production/work_orders/services.py:39-47).
• Places work orders on a calendar-aware scheduling board and computes capacity load (src/cluster_erp/modules/production/scheduling/services.py:1, src/cluster_erp/modules/production/capacity/services.py:1-16).

Sub-modules¶

Data model¶

Fields are listed on the sub-topic pages. Routings, production orders, components, and production versions carry product_id, product_model_id, and product_version_id (src/cluster_erp/modules/production/routings/models.py:18-34, src/cluster_erp/modules/production/production_orders/models.py:23-40). Labour and overhead rates are Numeric(12, 4) (src/cluster_erp/modules/production/work_centers/models.py:45-46).

Screens and metadata¶

get_metadata declares a sidebar group Production (Turkish Üretim) with Scheduling Board, Production Orders, Work Orders, Routings, Component Allocations, Work Centers, Operation Types, Routing Templates, Cut Technology Rules, Capacity (CRP), and Production Versions, and a home widget Scheduling (src/cluster_erp/modules/production/module.py:2516-2650). The work center card has a capability checklist and a working calendar tab (src/cluster_erp/modules/production/module.py:1356-1366). See gated app bundles and desktop module screens.

Status and actions¶

The module declares no ActionMeta; status changes go through routes such as POST /routings/{routing_id}/status, POST /production-orders/{order_id}/status, and POST /work-orders/{work_order_id}/start (src/cluster_erp/modules/production/routings/routes.py:373, src/cluster_erp/modules/production/production_orders/routes.py:205, src/cluster_erp/modules/production/work_orders/routes.py:112). The status machines are on the sub-topic pages.

Business rules¶

Each sub-topic page lists its rules. Order numbers come from the yearly sequence production_order (src/cluster_erp/modules/production/production_orders/services.py:165).

Events and queries¶

The module consumes 17 contracts and produces 29, counted as on the parties module page. The full list is on the contracts reference.

Permissions¶

The module checks work_center.*, routing.*, routing_template.*, routing_template_op.*, cut_technology_rule.*, production_order.*, and work_order.*. Operation types, component allocations, and production versions use the routing.* keys, and capacity reads use production_order.read (src/cluster_erp/modules/production/operation_types/routes.py:26-121, src/cluster_erp/modules/production/production_versions/routes.py:87-233, src/cluster_erp/modules/production/capacity/routes.py:18-34).

Privacy, retention, and history¶

The module has no privacy_handlers.py. Deletes set deleted_at (src/cluster_erp/modules/production/work_centers/services.py:102-108). Changes are captured by change history.

Analytics facts¶

analytics_facts.py contributes the fact set production_order over production_production_orders with the measures order_count, total_qty_planned, total_qty_produced, and total_qty_scrapped, read with production_order.read (src/cluster_erp/modules/production/analytics_facts.py:20-103). See analytics facts.

Settings and reference data¶

Operation types can be seeded from a list of 41 defaults in code with POST /operation-types/seed-defaults (src/cluster_erp/modules/production/operation_types/services.py:21, src/cluster_erp/modules/production/operation_types/routes.py:121). Working calendars come from the calendars module.

Tests¶

Found by a grep for modules.production in tests/ and for the path /production/ in web-client/_e2e_*.mjs.

Discrepancies¶

Terms introduced¶

Related pages¶

• Modules index
• Work centers and capacity
• Routings and operation types
• Production orders and versions
• Work orders
• Scheduling
• BOM module
• API reference for this module

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