This page describes two sub-modules of src/cluster_erp/modules/production/. work_centers/ holds work centers (WorkCenter), their weekly hours, and the operation types each one can run. capacity/ computes the load on work centers per week against their calendar capacity. The scheduling board that uses the same calendar math is explained on scheduling.
Scope and source¶
- Defined in:
work_centers/models.py,work_centers/services.py,work_centers/routes.py,capacity/services.py, andcapacity/routes.py. - Count: 3 tables; 8 work center routes and 2 capacity routes (
@router.decorators).
Work center fields¶
| Name | Meaning | Source |
|---|---|---|
code, name, description |
Identity | src/cluster_erp/modules/production/work_centers/models.py:28-35 |
cost_center |
Cost center as free text | src/cluster_erp/modules/production/work_centers/models.py:36 |
capacity_per_day |
Daily capacity ceiling, Numeric(10, 2) |
src/cluster_erp/modules/production/work_centers/models.py:37 |
capacity_units |
Parallel resources; N jobs may run at once | src/cluster_erp/modules/production/work_centers/models.py:38-43 |
setup_time_default_min |
Default setup minutes | src/cluster_erp/modules/production/work_centers/models.py:44 |
labor_rate_per_hour, overhead_rate_per_hour |
Rates, Numeric(12, 4) |
src/cluster_erp/modules/production/work_centers/models.py:45-46 |
timezone |
IANA time zone of the working hours; empty means inherited | src/cluster_erp/modules/production/work_centers/models.py:48-54 |
organisation_id |
Owning organisation, resolved through the EventBus | src/cluster_erp/modules/production/work_centers/models.py:55-63 |
is_active |
Active flag | src/cluster_erp/modules/production/work_centers/models.py:47 |
Child rows: WorkCenterHours (production_work_center_hours) with day_of_week, start_time, and end_time, and WorkCenterOperationType (production_work_center_operation_types) with operation_type_code and priority (src/cluster_erp/modules/production/work_centers/models.py:74-151).
Routes¶
| Method and path | Permission | Source |
|---|---|---|
GET, POST /work-centers/; GET, PUT, DELETE /work-centers/{work_center_id}; POST /work-centers/bulk-delete |
work_center.read, .create, .update, .delete, .bulk_delete |
src/cluster_erp/modules/production/work_centers/routes.py:25-132 |
GET, PUT /work-centers/{work_center_id}/operation-types |
work_center.read, work_center.update |
src/cluster_erp/modules/production/work_centers/routes.py:88-101 |
GET /capacity/load (mode crp or rccp), GET /capacity/input-output |
production_order.read |
src/cluster_erp/modules/production/capacity/routes.py:18-34 |
Capacity views¶
- CRP sums the remaining operation minutes of open production orders (released load) and the routing minutes of the planned orders of the latest MRP run (planned load), per work center and week, against calendar capacity. Overloaded rows list the contributing orders and products (
src/cluster_erp/modules/production/capacity/services.py:1-16,src/cluster_erp/modules/production/capacity/services.py:73-332). - RCCP uses only the planned load of master schedule items (
src/cluster_erp/modules/production/capacity/services.py:10-11). - Input-output compares planned input with actual output per work center and week, with the backlog trend (
src/cluster_erp/modules/production/capacity/services.py:12-14,src/cluster_erp/modules/production/capacity/services.py:333). - Open operation statuses are
pending,ready,in_progress, andon_hold; open order statuses areplanned,released,in_progress, andon_hold(src/cluster_erp/modules/production/capacity/services.py:47-48). - Capacity minutes use
day_capacity_minutesof the shared working-time engine (src/cluster_erp/modules/production/capacity/services.py:15-16); see working time.
Constraints and validation¶
PUT .../operation-typesreplaces the work center's capability list with known operation types (src/cluster_erp/modules/production/work_centers/services.py:127-160).- Delete sets
deleted_at(src/cluster_erp/modules/production/work_centers/services.py:102-108). - The scaffold assigns a work center automatically only from the capability table: a single candidate, or the one with the unique lowest
priority(src/cluster_erp/modules/production/routings/scaffold.py:17-21).
Terms introduced¶
| Term | Code identifier | Definition | Turkish term | Source |
|---|---|---|---|---|
| capacity units | capacity_units |
The number of jobs a work center can run at the same time. | Kapasite birimi | src/cluster_erp/modules/production/work_centers/models.py:38-43 |
| capability | WorkCenterOperationType |
An operation type a work center declares it can run, with a priority. | Yetkinlik | src/cluster_erp/modules/production/work_centers/models.py:107 |
| CRP | load (mode crp) |
Capacity requirements planning: load per work center and week against capacity. | Kapasite ihtiyaç planlaması | src/cluster_erp/modules/production/capacity/services.py:73 |
Related pages¶
Verified against commit 92f8051 on 2026-11-13.