Prerequisites

• Products must be created in the Inventory module first (raw materials and finished goods)
• At least one Work Center must be configured
• If using operator tracking, employees must be registered in HR module
• Your user account must have a Manufacturing role assigned (Super User, Manager, Production Planner, or Operator)

First-Time Setup Steps

Technical Setup

Module Dependencies

# __hmx__.py manifest
{
    "name": "Core_Manuf",
    "depends": ["base", "core_product", "core_hr", "webx_widget"],
    "data": [
        "security/manuf_groups.xml",
        "security/base.model.access.csv",
        "data/manuf_order_sequence_data.xml",
        ...
    ]
}

Auto-Sequences

Key Computed Fields

What is a Bill of Materials?

A Bill of Materials (BoM) is like a recipe for making a product. It tells the system: what raw materials are needed, what steps (operations) to follow, which machines (work centers) to use, and what finished products come out at the end.

How to Create a BoM

Production Rules Explained

BoM Technical Reference

Model: bom

Related Models

Cost Summary Engine

The _compute_summary_widget_json method builds a comprehensive cost breakdown as JSON, including:

• Finished goods costs with allocated_cost_percent per output line
• Material costs: quantity × product.standard_price
• WC costs: resolved via _find_workcenter_by_label, then service_cost_ids and labor_cost_ids are iterated with duration/quantity-based calculation
• Byproduct costs deducted from total
• Linked BoM navigation via product_bom_cache

ERD

What is a Work Center?

A Work Center is a machine, production line, or work area where manufacturing operations happen. Each Work Center has its own capacity, costs, and schedule. The system uses this information to plan when and where each operation will be performed.

How to Create a Work Center

WorkCenter Technical Reference

Model: workcenter

Cost Models

Performance Metrics (Read-only)

oee_percentage, lost_percentage, load_percentage, performance_percentage — stored fields for OEE dashboard display.

What is a Manufacturing Order?

A Manufacturing Order (MO) is your instruction to produce a specific quantity of a product. It links to a Bill of Materials and automatically generates the Job Orders (one per operation) needed to complete the production.

How to Create a Manufacturing Order

ManufOrder Technical Reference

Model: manuforder

Key Methods

Priority Access Control

# Roles allowed to change priority on confirmed MOs:
- core_manuf.manuf_group_super_user
- core_manuf.manuf_group_manager
- core_manuf.manuf_group_production_planner
- base.group_system

Material Scaling Logic

# _prepare_material_values()
to_consume_quantity = material.quantity × planned_quantity

# _prepare_workorder_values()
scaled_duration = compute_duration(operation, planned_qty, default_qty)
# where default_qty = sum(bom.output_ids.quantity)

What is a Job Order?

A Job Order (also called Work Order) is a single operation step in the manufacturing process. When you confirm a Manufacturing Order, the system automatically creates one Job Order for each operation defined in the Bill of Materials. Each Job Order is assigned to a specific Work Center.

Executing Job Orders

ManufJobOrder Technical Reference

Model: manufjoborder

Uses active_name = "active" for soft-delete support (voided by split).

Action Methods

action_start()   → status = 'in_progress' (from planned/ready/paused)
action_pause()   → status = 'paused' (from in_progress)
action_done()    → creates ManufRecord, status = 'done', opens record form

Production Record Creation

_create_production_record() creates a ManufRecord with draft status. _is_last_job_order() checks if this is the last active JO in the MO (no other non-done/cancelled/voided active JOs).

What is a Production Record?

When you complete a Job Order (click "Done"), the system automatically creates a Production Record. This is where you enter the actual quantities produced, consumed materials, quality check results, and any notes about the production run.

ManufRecord Technical Reference

Model: manufrecord

action_confirm() sets status to 'confirm' and returns baseactwindowclose to close the dialog.

How Scheduling Works

When you confirm a Manufacturing Order, the system automatically schedules each Job Order on its assigned Work Center. The scheduler respects working hours (8 AM to 4 PM, Monday to Friday) and ensures no two jobs overlap on the same Work Center.

• Sequential Mode: Operations run one after another — the next operation starts only after the previous one finishes.
• Parallel Mode: All operations can start at the same time, each on their assigned Work Center.
• Priority: Higher priority orders (Critical > High > Normal > Low) are scheduled first.
• Duration Calculation: Setup Time + (Operation Duration × Quantity Factor)

Understanding Delay Flags

Scheduling Engine Reference

Models

manufwcschedule — one header per WC per date (UNIQUE constraint on workcenter_id + schedule_date).

manufwcscheduleline — one line per MJO (UNIQUE on mjo_id).

Duration Computation

def compute_duration(operation, planned_qty, default_qty, workcenter=None):
    wc = workcenter or operation.work_center
    setup_time = wc.setup_time or 0
    scaling_factor = planned_qty / default_qty
    op_duration = operation.duration * scaling_factor
    return setup_time + op_duration

Working Calendar

SHIFT_START = time(8, 0)
SHIFT_END = time(16, 0)
WORKING_MINUTES_PER_DAY = 480

# add_working_minutes(): spans across days, skips weekends
# snap_to_working_start(): snaps to next valid work hour
# _is_working_day(): Mon-Fri only

compute_schedule(mo) Flow

1. Get all MJOs sorted by sequence
2. For each MJO: compute scaled duration
3. Determine anchor: sequential mode uses prev_finish; parallel mode uses MO requested start
4. Check WC last finish — if WC is busy, anchor moves forward
5. Snap to working start, compute finish via add_working_minutes
6. Create/get schedule header for the date, create schedule line
7. Sync dates back to MJO

Cascade Operations

When to Split a Job Order

You can split a Job Order when you want to distribute work across multiple Work Centers, or when a single Work Center can't handle the full quantity in time. For example, if you need to produce 1000 units and have 2 machines available, you can split the job into 500 + 500.

How to Split a Job Order

Split Job Order Technical Reference

Business Rules

Execution Flow (action_confirm)

1. Validate via _check_split()
2. Create audit document (ManufSplitJobOrder)
3. Void source MJO: set active=False, status=voided, voided_by_split_id
4. Cancel source schedule line via handle_mjo_void()
5. Create child MJOs from split lines with split_ref_id and parent_mjo_id
6. Schedule each child via schedule_single_mjo()
7. Redistribute MO materials proportionally via _redistribute_materials()
8. Confirm the audit doc (becomes read-only)

Material Redistribution

# _redistribute_materials():
# For each MO material linked to the voided MJO:
#   total_split_qty = sum(child.produce_quantity)
#   for each child MJO:
#     ratio = child.produce_quantity / total_split_qty
#     new_mo_material.to_consume_quantity = original × ratio

Models

manufsplitjoborder — audit document, read-only after confirmation (write raises ValidationError on confirmed state).

manufsplitjoline — split lines with planned_qty, workcenter_id, assigned_mode (auto/manual), duration_planned, resulting_mjo_id.

Assigning Operators

Operators are employees marked as "Manufacturing Labor" in the HR system. You can assign one or more operators to each Job Order with Primary or Secondary roles. The system tracks their availability — an operator currently working on an active job will show as "Busy".

Time Tracking

The system automatically logs work time for each operator through the Labor Time Log. It records actual start and end times, pause durations, and calculates total actual duration. Time logs can be auto-generated from job order actions or entered manually.

Operator Assignment Technical Reference

Model: manufmjooperator

HrEmployee Extension

class HrEmployee(models.Model):
    class Meta:
        inherit = "hremployee"

    is_manufacturing_labor = models.BooleanField(default=False)
    availability_status = computed:
        "Busy" if any active assignment on non-done MJO
        "Available" otherwise

Labor Time Log: manuflabortimelog

Per-operator time tracking with pause sub-lines (manuflabortimelogpause). Source field: auto (system-generated) or manual.

Time Tracking: manuftimetracking

Per-MJO time entries with type (work/pause), start/end times, duration, and optional reason for pauses.

Security Roles

Permission Matrix

C = Create, R = Read, U = Update, D = Delete

Common Issues

Cannot delete a Bill of Materials

Cannot delete a Work Center

Cannot change priority on a Manufacturing Order

Cannot split a Job Order

Scheduling shows "Delayed" status

Operator shows as "Busy"

Technical Troubleshooting

Celery Task Failures

The scheduling task (_run_schedule) is decorated with @use_task(fallback_to_sync=True). If Celery is unavailable, it falls back to synchronous execution. Check Celery worker logs if scheduling seems delayed.

Schedule Integrity

If schedule data becomes inconsistent, you can trigger a full recalculation for a Work Center:

schedule_model = env['manufwcschedule']
schedule_model.recalculate_sequences(wc_id, from_position=1)

Unique Constraint Violations

• workcenter.code — unique across all Work Centers
• manufwcschedule (workcenter_id, schedule_date) — one schedule per WC per date
• manufwcscheduleline.mjo_id — one schedule line per MJO
• material (operation, product) — unique product per operation