How to group orders by material and thickness without missing due dates ART-133

When grouping orders reduces changeovers without delaying delivery

Group orders by material and thickness only when the repeated preparation work is reduced without endangering an agreed delivery date. The rule is not “cut all identical steel first”: protect fixed-date orders, confirm files and material, then combine compatible sheets inside the available window. That reduces transitions without turning grouping into a cause of delay.

Why this issue arises in practice

Sheet-work queues are often formed by arrival time, a loud reminder, or the nearest sheet. The result is repeated switches of grade, thickness, format and cutting conditions. Some losses are hidden: the technologist reopens a program, the warehouse searches for another material, unfinished bundles remain on the table, and an order with a real deadline is mixed with one that is merely “wanted quickly.” Grouping is useful because it makes the flow predictable, not because a plan looks tidy.

What information must be visible before the decision

How to check your own part mix

Use the planning horizon the cell actually controls: a shift or the next working days. Record factual inputs only: the date promised to the customer, drawing status, material, thickness, format, sheet count, next operation and approval owner. Divide work into “cannot move”, “ready to combine” and “awaiting data”. Do not add work from the third group to a nest merely to improve sheet use: that is how erroneous programs and unnecessary parts are created.

Within the second group, create short families rather than one large list: the same material grade and condition, the same thickness, a compatible sheet format and similar due dates. The technologist then checks whether edge-quality, protective-film, micro-joint, marking or sorting requirements change the logic of the run itself. A production plan is not simply a parts list: it is an agreement about what can be combined without losing identification or quality.

How to turn the check into a decision

Protect the due date first, confirm readiness second, reduce avoidable transitions third, then check that early cutting does not create a later bottleneck. If the same thickness produces a saving but the parts will wait a week before bending, it is not a net saving. Conversely, an extra material change may be justified when it keeps a promised date or prevents the next department from stopping.

Do not substitute an average cutting speed for a planning rule. A thickness change does not always mean a long changeover, and identical thickness does not guarantee the same process. Use actual material cards and programs for the particular equipment, the manufacturer's instructions and a technologist's review. Reserve a controlled run for a new part mix rather than quietly mixing it with a recurring series.

Boundary between transition savings and meeting commitments

The planner must see local saving and the result for the complete order separately. Compatible sheets may reduce material searches, repeated program calls and unexpected queue changes, but the gain disappears if parts then wait for bending, welding or shipment at the agreed time. In that case production has simply moved the loss from the laser department to another point in the route.

To avoid arguing from impressions, record a short reason for each exception: a due date, an incomplete file, a missing sheet, a traceability requirement or the availability of the next operation. This need not be a complex report. It is enough for the next shift to understand why an order ran separately or was not included in the material group. Review these reasons after a suitable period. If most exceptions concern files, laser scheduling itself is not the problem. If they concern missing sheets, material reservation rules need changing. If urgent orders constantly disrupt the queue, agree realistic production windows with sales.

Grouping succeeds not when there are fewer rows on a screen, but when compatible orders pass without unnecessary changes, every part remains identified, and the next operation receives it when needed. Compare planned and actual handover dates, the reason for deviations and the number of unscheduled rearrangements. Do not promise a universal time saving: it depends on the part mix, equipment, programs and organisation of the particular department.

> Contextual action. To compare a part mix, route and equipment constraints before a discussion, prepare a short list of actual parts, materials and requirements. It keeps the discussion tied to a verifiable scenario rather than an abstract model.

Typical mistakes

• Giving every request marked “urgent” the same priority without recording an agreed date.
• Combining only by thickness without grade, surface, film and quality checks.
• Cutting for stock before the route or next operation is agreed.
• Treating a transition saving as more important than order traceability.
• Reordering verbally without a record for technology, stores and the operator.

Checklist before launch or selection

• [ ] Each order has a confirmed due date and file status.
• [ ] Material is checked by full specification, not only by generic name.
• [ ] Work is separated into critical, groupable and data-pending tasks.
• [ ] Sheet availability and next-operation capacity are checked.
• [ ] A mixed sheet has a sorting and identification method.
• [ ] Any due-date deviation is agreed before launch.

What cannot be determined without data

This article gives a planning principle, not a changeover norm, acceptable waiting time or compatibility rule for a particular machine. Those depend on the controller, cutting head, material, contracts, process documentation and production route; the responsible technologist or production manager confirms the final plan.

Decision rule: a due date may break a technical group

Material and thickness are a first filter, not an instruction to wait for an ideal bundle at all costs. They reduce unnecessary changes but do not cancel a confirmed customer date, file readiness or the next operation. Combine an order only when it is technically compatible, completely ready and still inside its agreed production window. If even one condition is missing, it is not “failed grouping”; it is a separate job with a visible reason.

This distinction is useful precisely because it does not conceal the problem. A queue with ten unfinished jobs labelled “almost ready” creates an appearance of workload but does not help the operator. Instead, the actual reason is visible: a sheet, a file, a customer decision or genuine equipment occupancy.

Production window: assembling a bundle without accidental delay

A production window is a short period in which compatible work is processed. It is neither required to be identical in every workshop nor a time standard. It marks the latest moment for adding a ready order; afterwards it moves to the next window or launches separately by date.

Check specification, thickness, dimensions, program status, protective film or special surface protection, marking and next-operation availability—not only a material name. Two items can both be called “2 mm stainless steel” yet not be interchangeable because of grade, surface, a customer requirement or route. The documentation of the particular order, not a queue-level assumption, determines this.

### Minimum production-bundle card

For a small manufacturer, keep one transferable card in a system or spreadsheet with bundle code, confirmed material/thickness group, order numbers, file and sheet status, program owner, identification method, next operation and the cutoff for additions. It does not replace an MES, but it makes the decision transferable between sales, warehouse, technologist and operator.

Example without false economy

There are four orders in the queue. Two have the same confirmed material and thickness, ready files and a deadline at the end of the week. A third looks compatible but is awaiting drawing clarification. A fourth needs the same material, but its parts must reach bending at a specific time for an already agreed assembly. A sound bundle contains the first two orders. Do not add the third “just in case”: it can stop the launch or mix revisions. Give the fourth a separate slot because of its date, or agree its postponement before launch.

There is no universal rule for the number of sheets in a bundle. Judge the outcome by fewer unnecessary changes, preserved traceability and no hidden date shift. If a better nest requires manual part separation, reworking marking or urgently rebuilding the next operation, the local saving may cost more than a separate launch.

What to analyse after a shift

Do not compare only the number of sheets processed. Four questions are useful: how many times the queue had to change; how many jobs left a bundle and why; whether all parts reached the correct order; and whether the next operation received material at the required time. If the same cause recurs—for example, a file arrives after planning or the warehouse cannot see a sheet reservation—that calls for a process change, not punishment of the operator.

It is important to separate a technological fact from a commercial decision. CAM or MES can support nesting, material accounting and queues; Lantek, SigmaNEST, TRUMPF Oseon and Bystronic BySoft describe examples of such functions. But they cannot decide on their own whether a customer date should yield to a material saving. That decision needs company rules and a responsible person.

When identical material is not a reason for one launch

Sometimes parts are technically similar but are better kept out of the same bundle. The first reason is differing traceability rules. If one group has a separate marking, kitting or quality-document requirement, a mixed launch can make handover to the customer harder. The second reason is different edge or surface criticality. The same sheet does not make acceptance criteria the same: one part may accept an ordinary production edge while another goes to a visible panel or a precise assembly.

Parts for bending, welding or external coating can also have different dates and handover methods. Combining them merely because they use the same material can create a semi-finished queue in one place and an urgent stop in another. Small or similar parts without reliable identification should not be mixed until the team has an agreed post-cutting separation method. That is not an argument against mixed nesting generally; it is the condition that makes it controlled.

Passing “not combined” into the plan is as important as passing “combined.” A short visible reason—date, route, file or sorting—lets the next shift continue without guessing. After several weeks, these notes show whether grouping is prevented by the part mix itself or by the process for receiving data. Only then does it make sense to change planning rules or discuss additional software and production capabilities.

Discuss the task