When mixed nesting is genuinely worthwhile
Mixed nesting is useful when several orders ready for launch use the same material and technologically compatible requirements, and the business can unambiguously separate every part after cutting. The saving does not come from mixing by itself: it comes from filling a sheet better and leaving fewer remnants. Without a sheet map, marking rules, sorting control points and a person responsible for completeness, material savings can quickly become shipment errors.
Traceability starts before the program is created
The common mixed-sheet problem often begins before the machine, when positions with different statuses enter one task. Before creating a program, record the revision of every part, ordered quantity, marking requirement, next route and responsible person. When a contour changes after the sheet map was made, the update needs a controlled procedure. Otherwise a correctly cut part can enter the wrong kit simply because a paper or digital map is stale.
A launch number, sheet map and separate containers are required. The record may live in ERP, MES, a label or a control sheet, but it must be usable on the shop floor.
Start a trial mixed launch with orders that have no conflicting requirements. Its purpose is to reveal real sorting time and error points, not to declare the entire system ready after one convenient sheet.
Calculate the economic effect transparently. When assessing the benefit of a smaller remnant, account for the extra minutes required to prepare the map and labels and sort the parts, as well as the cost of an error if one occurs. A high sheet-fill percentage is not a success when it mixes a kit or delays shipment. A sound process leaves not only parts, but evidence of the order, program and material from which each part came.
### Checking a sheet map before the first mixed launch
Check the route of a particular part, not an abstract CAM capability. Take one sheet with two orders and answer four questions: where is the contour in the program, who removes the part, which container receives it, and who confirms handover? If every answer exists without an oral explanation from the program author, the process has basic control. If it depends on one employee's memory, mixed nesting is not ready to scale.
For parts going to a next operation, show route status as well as order number: bending, welding, inspection or direct shipment. The map need not duplicate the whole production system; it only needs to show the next point so that a part is not left between areas without a clear owner.
### Roles on a mixed sheet
The planner decides which ready orders may be considered together by date and material. The programmer or technologist checks whether the nest is realistic to unload and does not create unacceptable process risk. The operator runs the approved program; the person sorting checks parts against map and container. The shift leader must see an incomplete kit before it becomes a customer problem. In a small company one person may hold several roles, but the control actions must remain.
### What a sufficient result looks like
A sufficient mixed-launch result is not merely “the sheet was used better.” It includes a sheet with a controlled program revision, a map tied to positions, physical separation, and a record of missing or damaged parts. Only then can material gain be compared with extra work. If remanufacture is needed, the map must show whether the cause was the program, unloading, container or input data.
Admission matrix: what to combine and what to keep separate
Mixed nesting is not mandatory optimisation. A short admission matrix does not replace a technologist, but resolves obvious disputes. One group may include orders with the same complete sheet specification, approved files and close dates. A second group needs a separate decision: similar material but different surface requirements, a special route or small similar parts. A third group is not mixed: customer-owned material, special batch requirements, confidential or critical kits, incompatible dates or unconfirmed files.
| Decision | Minimum basis | Control action |
|---|---|---|
| May combine | One material specification, approved revisions, compatible dates | Create one sheet map and separate handover points |
| Consider separately | Surface, route or container type differs | Technologist and planner approve an exception before programming |
| Do not combine | Customer material, critical kit, unconfirmed file or incompatible date | Plan a separate launch; do not conceal risk with sheet savings |
Build this matrix from actual error causes. If left and right parts were confused several times, a blanket ban on mixed sheets is not the answer: add a rule for similar geometry or separate containers. If delay arose because labels were missing, change when containers are prepared. Rules should result from evidence, not incidental bureaucracy.
What to do with an incomplete kit
Do not quietly move an incomplete kit to the next operation. The map or production record must retain the position, actual quantity, cause and next action: relaunch, search in the sorting area, technical check or date agreement. This protects planning and customer communication from a shortage discovered only during packing.
Do not use a mixed launch to hide an urgent position inside a large sheet. Where one part has a critical date, its unloading, checking and handover priority must be set before launch. Otherwise a sheet saving can create a larger service or shipment loss.
What to check before regular use
After several controlled sheets, review the records: number of clarifications, whether the map worked without its author, sorting time, unexplained remnants, and whether every part reached the next route. No problem in one simple case is not proof of universal readiness. Repeated launches with a clear record justify broadening the allowed scenarios.
A small example without invented metrics
Imagine two orders using the same confirmed material. One contains several large brackets that go to bending after cutting. The other contains flat plates for direct shipment. Nesting may save sheet area, but the routes then diverge. To retain control, the map shows not only contour numbers but separate destinations: “container for bending” and “container for inspection before shipment.” The first container does not move onward until quantities are checked; the second is not packed with parts from another order.
This example does not define which particular parts may be combined. It asks whether a part's ownership remains obvious once it is separated from the sheet. If the answer relies on marker colour, oral memory or accidental position on a table, use a different scenario. If map, container and handover mark confirm it, mixed nesting can be assessed by actual results.
Data worth providing for a practical assessment
For consultation or internal review, controlled revisions of several DXF files, material specification, quantities, dates, surface requirements and a short description of next operations are enough. There is no need to send the entire production plan or disclose customer-confidential data. Without these minimum facts, however, it is not possible to assess honestly whether a mixed sheet suits a particular part mix.
Before regular use, also check that the map file is stored with the program revision, not in the author's personal folder. When a part revision changes, review the map before launch. This simple rule reduces the risk of correctly sorting a part that is already obsolete and makes an internal investigation of a deviation easier. For critical kits, separately define the moment of final reconciliation before handover to the next area.
Sheet map: which data must live together
A sheet map is not a pretty nesting screenshot; it is a short controlled record. It combines launch identifier, program revision, material, order list, position numbers, quantities, container logic and next-operation status. Not every field must be printed large near the machine. The person removing and handing over a part must have the version that matches the running program.
When one position changes after the sheet has been prepared, simply replacing a DXF in a folder is insufficient. Decide whether the nest, quantity, containers, sorting order or route changes. If it does, withdraw the old map from use and record a new revision. This does not require complex document management, but removes the hazardous situation where the technologist works with the current file while the warehouse or shift uses the previous parts list.
For recurring part families, use consistent rules for naming the position and revision. Designations such as “left/right”, “top/bottom” and internal codes must not be replaced with a similar description on a label. If two parts are geometrically similar but belong to different kits, the map must make that distinction visible before they are removed from the sheet.
From unloading to the next operation
A successful mixed launch does not end when contours leave the sheet. The vulnerable point is often unloading: small parts can remain on the table, similar parts can enter a neighbouring container, and large panels can hide the rest of a kit. Plan the sorting method before launch: removal order, intermediate area, marked containers and quantity-reconciliation point.
For different routes, show handover point as well as order number: bending, welding, inspection, coating or packing. The operator need not control all production; they need only see where a checked position belongs. The recipient accepts a kit through a clear status, not an assumption that the sheet was ready.
Give an urgent part a separate control point. It may be cut in a mixed sheet, but need not wait until all other orders are sorted. Design the map so that its checking and handover path is visible and separate.
How to review a deviation without seeking a culprit
When a kit is short, separate four causes: input-quantity error, stale map revision, unloading failure, or physical damage/loss. They require different actions. A relaunch does not cure an unchanged map, and new marking does not cure a wrong order quantity.
A short deviation record includes launch number, position, actual quantity, discovery point, checked map revision and next action. It is not for punishing a worker; it makes mixing rules more precise. Repeated causes become process changes: another container, separate marking, another reconciliation point or a prohibition on combining a defined part class.
When to stop mixing rather than force it through
Cancel mixed nesting before launch when any critical condition is unconfirmed: no current revision, separately traceable material, an unagreed urgent route, or a sorting method based on assumption. Declining one mixed sheet is not an optimisation failure; it shows that existing data cannot safely preserve kit completeness.
Be especially careful with similarly shaped positions that have different marking, coating or acceptance requirements. Visual similarity does not prove interchangeability. If a distinction requires an oral explanation from the program author, first make it visible on the map and at handover, then assess material savings.
Typical mistakes
- Mixing positions only because they physically fit on one sheet.
- Keeping the sheet map apart from the program revision or failing to update it after a drawing change.
- Unloading all parts to one intermediate area without container rules or a reconciliation owner.
- Passing positions to the next operation before quantity or route is confirmed.
- Treating one successful launch as proof that every mixed-order scenario is ready.
Checklist before a mixed launch
- [ ] Material, quantity and controlled file revision are confirmed for every position.
- [ ] The sheet map is tied to a particular program revision and launch number.
- [ ] Each order has a container, next operation and reconciliation point.
- [ ] Similar or critical parts have visible distinction before unloading.
- [ ] Urgent positions have a separate checking and handover path.
- [ ] A shortage has a named recorder and next action.
What cannot be determined without data
This article does not set ERP/MES rules, certificate requirements or a marking method. They depend on the contract, equipment, product and internal procedure.