Manufacturingdata

Production Records

What records does a production run leave behind — documents, waste figures, and confirmations?

Production leaves a record at every level: documents on the BOM, documents on the run, waste entries against the planned figure, and confirmation records of what was actually produced. The batch is identified by the lot number assigned at planning.

Referenced across3 other parts of continON

How it works

Two document layers exist. Files attached to the bill of materials describe the product — specifications and instructions that apply to every run. Files attached during the run’s documentation step belong to that specific batch, saved against the manufacturing process itself.

Waste is recorded per phase with the planned figure from the BOM, the actual amount, and an other-waste field that requires a written justification — so deviation is data, not a shrug. The confirmation record completes the trail: produced quantity, confirmation date, note, and the warehouse the output was recorded against, all under the plan’s lot number. Produced articles can also carry a dedicated manufacture barcode identifier on the item master.

What the register holds

5 on the record
Product-level and batch-level documents
BOM attachments describe the product; run attachments belong to the specific batch that produced them.
Waste with justification
Planned waste, actual waste, and justified other waste are stored per phase and per run.
Confirmation as the closing record
Produced quantity, date, note, and receiving warehouse are captured on a confirmation record per phase and process.
Lot-identified output
The lot number assigned at planning identifies the batch across stock, sales, and traceability lookups.
Manufacture barcode on the item master
A dedicated barcode field on the produced article supports labeling of manufactured items.

See production records running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.