# Production management

IndustryMax's production module turns a recipe into a run and accounts for what came out of it. A bill of material says what an item is made of; a production order plans a quantity of it; releasing the order snapshots what that run will need; material is issued against the order; job cards record the work done at each work centre; and posting output receives the finished goods into stock alongside what was rejected and what was scrapped. WIP, yield, scrap and the variance between what a run should have consumed and what it did are reported from those same records.

*Last reviewed 2026-09-12. Canonical HTML: https://industrymax.co.in/modules/production*

## The documents it manages

**Bill of material (BOM)**
: The recipe: what an item is made of, in what quantities, for what output quantity, with an expected scrap percentage per component. A BOM can be exploded to see everything underneath it, and asked where-used to see everything it goes into.

**Work centre**
: Where an operation happens — a machine, a bay, a bench.

**Routing**
: The ordered list of operations an item goes through, and which work centre each one belongs to.

**Production order**
: A planned run of a quantity of one item, optionally against a BOM. It moves through draft or planned, released, in progress, and then completed, short-closed or cancelled.

**Job card**
: The work actually done at one operation: quantity good, quantity rejected, quantity scrapped, and downtime in minutes.

**Production output**
: What the run produced, posted into stock. It carries the produced, rejected and scrapped quantities separately.

**Job work received**
: A customer's goods on our floor for work, under their challan. Run by the shop floor rather than the sales office, and deliberately separate from our own production orders.


## How a run works

1. **Plan** — A production order names an item, a quantity, and usually a bill of material.
2. **Release** — Releasing takes a fresh snapshot of what the run needs, calculated from the recipe, the output quantity, the planned quantity and each component's scrap percentage. It is recalculated from scratch each time, so releasing twice cannot double a requirement.
3. **Issue** — Material goes out of the store against the order. Issued and returned quantities are held per component, in the item's stock unit, so the variance report can subtract them honestly.
4. **Work** — Job cards record what each operation produced, rejected, scrapped, and how long it stood idle.
5. **Receive output** — Posting output adds the finished goods to stock at a location, and records the rejected and scrapped quantities against the run.
6. **Close** — A run ends completed, short-closed when the remaining quantity will not be made, or cancelled. Posted output can be reversed, which leaves a visible reversal rather than an edit.


> **Note:** A run can also be raised with no recipe behind it and a hand-entered requirement instead — a repair job is then a real document rather than something kept outside the system.


## Reports

- Production register — every run, with planned, produced, rejected and scrapped quantities.
- WIP — orders released or in progress, with the material sitting in them.
- Yield percentage, calculated in one place so two screens cannot define it differently.
- Scrap, grouped by work centre, by operation or by item, with downtime alongside it.
- Order variance — what the run should have consumed against what it did.


## What it does to stock and to the books

| Step | Stock | Books |
|---|---|---|
| Bill of material | — | — |
| Production order raised | — | — |
| Order released | — (requirement snapshotted only) | — |
| Material issued to the run | reduces component stock | optional |
| Job card | — | — |
| Output posted | adds finished goods | optional |


## What this module does not do

Worth stating plainly, because these are the things buyers assume a production module includes.


- No material requirements planning (MRP) run.
- No finite or capacity scheduling, and no advanced planning and scheduling.
- No machine connectivity or IoT, and no OEE. Job cards record downtime in minutes, which is not the same thing.
- No separate quality-management module. Inspection on the incoming side is part of receiving; on the production side, a job card records good, rejected and scrapped quantities.


## Questions

### Does IndustryMax support bills of material?

Yes. A BOM says what an item is made of, in what quantity, for what output quantity, with an expected scrap percentage per component. It can be exploded downwards and queried where-used upwards, and a production order releases against it.

### Does IndustryMax have production orders and job cards?

Yes. A production order plans a run and snapshots its material requirement when released; job cards record what each operation produced, rejected and scrapped, and the downtime against it.

### How is WIP tracked?

From the orders themselves. Anything released or in progress is work in progress, and the report shows the material issued into it against what it required. A completed or cancelled order is not WIP however its numbers read.

### Does IndustryMax do MRP or production scheduling?

No. There is no MRP run, no finite or capacity scheduling, and no advanced planning. Runs are planned by a person and released by a person.

### Can we take in work from a customer on their own material?

Yes. Job work received records a principal's goods on the shop floor under their challan. It is kept separate from our own production orders because the documents belong to the customer.

## Related

- https://industrymax.co.in/modules/inventory
- https://industrymax.co.in/modules/procurement
- https://industrymax.co.in/modules/accounting
- https://industrymax.co.in/glossary