Appearance
Multipanel Groups
Multipanel Groups let you combine multiple wall panels into a single unit that is processed together through the machine. This is a production-level decision — you create groups inside a batch to tell the machine to feed several panels consecutively as one run.
When a group is valid, the report system treats the whole group as a single logical panel: Bill of Materials reports use the combined rail length, and machine files (MOB2) are generated as one file for the whole group.
Feature flag
Multipanel Groups must be enabled on your company by a Produuz.it administrator. Once enabled, a Multipanel Groups entry appears in each project's menu, and admins get a Multipanel Configurations table in Projects Settings.
Configuration
The constraints for groups are kept in multipanel configurations, shared by the whole company. An admin manages them in Projects Settings → Multipanel Configurations: click New to add one, or the pencil to edit it. A company can have several, for example one per machine.
| Setting | Description |
|---|---|
| Name | Name of the configuration. |
| Default for new projects | New projects use this configuration. |
| Min. height (mm) | Minimum panel height allowed in a group. |
| Min. / Max. element width (mm) | Allowed width range for individual panels. |
| Max. transport width (mm) | The combined width of all panels plus gaps must not exceed this value. This is typically the physical limit of the machine or transport system. |
| Min. / Max. elements per group | Minimum and maximum number of panels per group. |
| Default gap (mm) | Default gap between elements when creating a new group. |
Each project picks the configuration it uses in its project form, in the Multipanel Config field.
Creating a Group
Open Multipanel Groups in the project menu, choose a Batch, and click the Multipanel button in the table toolbar. The dialog has two sides:
- Select panels (left) — tick two or more assemblies of the batch. Once a panel is selected, incompatible panels (different height or rail profile) are disabled; hover one to see why.
- Gaps between panels (right) — set the gap between each pair of adjacent panels, in mm.
- Validation — the checks run on their own every time the selection or a gap changes. Each requirement shows a pass or fail icon with a detail message.
- Group name — give the group a name and click Create.
Create is only enabled when every check passes, so a new group is always saved as valid. Use the pencil on a row to edit a group, and Update to save it.
Validation Requirements
All 7 requirements must pass before a group can be created.
| # | Requirement | What is checked |
|---|---|---|
| 1 | Height equality | All panels must have the same height; each must meet the configured minimum. |
| 2 | Element width & transport width | Each panel's width must be within the configured [min, max] range, and the total width must not exceed the maximum transport width. |
| 3 | Element count | The number of panels must be within the configured minimum and maximum. |
| 4 | Top/bottom rail framing | Top and bottom rail profiles must be identical across all panels. |
| 5 | Same batch | All panels must belong to the same batch. |
| 6 | Identical zones | The zones checked by the configuration must be present in all panels or in none, with the same branches in each. |
| 7 | Gap & total transport width | Total combined width (sum of panel widths + all gaps) must not exceed the configured maximum. |
Saw and milling operations on the panel layer must also be equal across all panels. produuz.it does not check this: make sure of it before you group the panels.
Group Status
| Status | Meaning |
|---|---|
draft | Not validated yet. |
valid | All validation checks passed. Reports and machine files treat the group as a single panel. |
invalid | One or more validation checks failed. |
The Valid column of the table shows the result of the last validation; hover it for the details of each check. Click the refresh icon on a row to run the validation again, for example after a design change.
Report Form — Assembly Selector
When building a report (BoM, machine files, etc.), the assembly selector is aware of multipanel groups:
- Each assembly that belongs to a group shows a chip with the group name and the panel count (e.g.
Group A ×3). This makes it easy to spot which assemblies are part of a combined unit. - A Force multipanel selection switch, on by default, sits above the selector. When it is on, selecting any assembly in a group automatically selects all the other assemblies of the same group. This prevents accidentally generating a report for only part of a group.
A group is only treated as one panel when all of its panels are in the selection. If only some are selected, each of them is handled as an individual panel.
Bill of Materials Impact
When generating a BoM report (Wood BoM, Plates BoM, etc.) that includes all the assemblies of a valid Multipanel Group:
- The top rail and bottom rail parts are replaced by a single virtual part spanning the full group width.
- The rail length in the cut list equals
sum of all panel widths + sum of all gaps between panels. - All other part properties (material, profile, finish, etc.) are taken from the first panel's rail.
- Non-rail parts from each panel appear individually in the list, as usual.
- Only one row appears per rail category (one top rail, one bottom rail) for the entire group — not one per panel.
This ensures the cut list reflects the actual piece that goes through the machine, rather than individual per-panel lengths that would be incorrect.
Example
Two panels: 1200 mm and 900 mm wide, with a 10 mm gap between them. Combined rail length = 1200 + 900 + 10 = 2110 mm. The BoM shows one top rail and one bottom rail, each 2110 mm long.
Machine File Impact (MOB2)
When generating a MOB2 machine file for a selection that includes all the assemblies of a valid Multipanel Group:
- A single
.mob2file is generated for the entire group, named after the group. - The file is placed in the batch folder as
<phase>/<batch>/<group_name>.mob2. - Part positions within the combined file are offset correctly: parts from panel 2 are placed after panel 1, with the configured gap applied — so the machine sees the full combined run in the correct order.
- The revision field is left blank for group files (since a group has no single design revision).
- The operation drawings go to
<phase>/<batch>/pics/<group_name>/, and they are added to every panel of the group in the viewer. - Groups are applied by the MOB v1 and MOB v2 Machine File reports only. Action triggers and the Mobfile Generator make one file per design.
- The Frame Station Invert Y axis settings and Treat extra woods as normal frame woods have no effect on group files.
See: MOB v2 Machine File
Tracking Production Progress
Both the left-menu list (in the 3D viewer) and the Multipanel Groups management table show a row of small station chips for each group. Each chip represents one station of the batch's production line and shows how many panels of the group are ready at that station, in the form ready/total:
- An outlined chip means no panel has started the station yet.
- A filled orange chip means some panels are working there or are already ready there.
- A filled green chip means every panel of the group has been marked ready at that station.
- When every station of every panel is ready, a single Ready chip replaces the row.
Stations that none of the panels pass through are left out. Hover any chip to see the full breakdown — number of panels that are ready, currently working, and still waiting at that station.
In the viewer, open the group row to work on all its panels at once with the Multiwall Checklist.
Clearing Proofs in Bulk
In the Multipanel Groups management table, ticking the checkbox of one or more rows reveals a Proof Options menu in the toolbar. The Clear proof action wipes all production proofs for every panel of the selected groups in one operation — useful when a group needs to be reworked from the start. The same menu also offers Set Ready and Merge checklist, mirroring the actions available on individual constructibles. Next to it, Launch action generates the drawings of the selected groups.