Control cabinet door cut-outs, fit check and bayed suites: configurator rules
The rules a control cabinet configurator needs: size grid, door leaves, cut-outs for fans, windows and cooling units, lock zone and bayed suites.
Short answer: a control cabinet configurator needs rules for three questions: size (which widths, heights and depths does the grid allow per type?), door (does every cut-out for a fan, window or cooling unit fit inside the usable area of one leaf, clear of the lock zone and of other cut-outs?) and suite (how do several bayed cabinets behave together?). Our example configurator shows this with example rules that a manufacturer replaces with their own.
Which inputs does a control cabinet have?
| Input | Values in the example | Depends on / affects |
|---|---|---|
| Type | wall-mounted enclosure, floor-standing cabinet, bayed suite of 2 to 5 cabinets | sets grid, plinth and cooling options |
| Width | wall 300–800 mm, floor 600–1,200 mm, suite 400–1,200 mm per cabinet | per cabinet in a suite; sets the door leaves |
| Height | wall 300–1,200 mm, floor and suite 1,800–2,200 mm | shared by all cabinets in a suite |
| Depth | wall 150–400 mm, floor and suite 400–800 mm | shared; matters for the roof cooling unit |
| Plinth | none, 100 or 200 mm | floor and suite only; the wall enclosure hangs on the wall |
| Door | single (hinged left or right) or double | double only from 1,000 mm width (example rule) |
| Lock | double-bit insert, swing handle with cylinder, comfort handle | no effect on the fit check; the lock zone depends on handle height and the active leaf |
| Cut-outs | filter fan, outlet filter, viewing window, door cooling unit; up to 6 per door | fit check per cut-out |
| Interior and cables | mounting plate with rails, plate only or empty; blank plate, gland plate or brush strip at top and bottom; LED light | notes in the check step |
All values are example values of a fictional product. The demo reads them from tables; a manufacturer replaces those tables with their range.
How does the configurator check door cut-outs?
Each door gets an outside view in the cut-out editor. Cut-outs can be added, dragged with a finger or mouse, or moved with arrow buttons in 25 mm steps. For each cut-out the demo applies four example rules in turn:
- Bigger than the door: the cut-out is wider or taller than the usable area of a leaf.
- Door frame: it is not fully inside the usable area, which is the leaf minus a 60 mm margin. If it straddles both leaves of a double door, the demo reports that it sits across the leaf joint.
- Lock zone: it overlaps a 130 × 260 mm field at the lock edge of the active leaf, centred on the handle height.
- Spacing: it comes closer than 30 mm to another cut-out on the same door.
In the editor a cut-out that fits has a green outline and one that does not has a red one; the reason is shown in the 3D model, in the editor and in the check list. The handle sits at half the cabinet height, on floor-standing cabinets at most 1,100 mm. On a 2,000 mm cabinet the lock zone therefore runs from 870 to 1,130 mm.
Two cases from the demo show how quickly a door fills up. A 600 × 800 mm wall enclosure with a cooling unit on the door turns red: the smallest door cooling unit is 800 mm tall, while the usable door height after the margin is only 680 mm. And on a 1,200 mm double door the medium viewing window (450 mm wide) fits inside one leaf, but the large one (600 mm) does not.
What happens with cooling accessories?
In the demo, cooling is only an accessory with example sizes, not a thermal design. Choosing "filter fan + outlet filter" places a fan low and an outlet filter high on free spots of the door; the size follows the cabinet height (large from 1,200 mm, medium from 600 mm, otherwise small). "Cooling unit on the door" places the largest door unit that fits on the hinge side; if even the small one does not fit, it stays red. Changing the cooling option replaces only fans, filters and cooling units; viewing windows stay where they are.
The roof cooling unit has a 500 × 380 mm footprint and, under the example rule, needs 40 mm more in width and in depth, so at least 540 mm width and 420 mm depth. Wall enclosures do not offer it. On top come notes rather than errors: whether a door can carry a cooling unit is for the manufacturer to decide; a window and a cooling unit on the same door should be reviewed; a note appears when there is no cable entry at top or bottom, and when a light is chosen without a mounting plate. One note is always shown: no statement on protection rating, heat, EMC or standards.
How does the bayed suite work?
A bayed suite has two to five cabinets side by side, starting with three of 800, 800 and 1,200 mm. Each cabinet has its own width, door, cooling option and cut-outs; height, depth, plinth, finish and lock apply to all. You pick a cabinet with chips or by tapping it in 3D, and "apply to all cabinets" copies door and cut-outs to the others. The check step states the total width of the suite with a reminder to check transport and access on site.
In the exploded view the cabinets move apart, showing bay connectors, seals and side panels that only sit at the two ends of the suite. For a single cabinet the same view shows the roof, side panel, door, mounting plate, gland plate and plinth as labelled parts.
What data would you supply?
For your range we need, per type, your size grid and default values, your door and lock variants, the width from which a door becomes a double door, your accessories with outer size and real cut-out size, and your rules for minimum distances, lock zone and allowed positions. Where an accessory has its own conditions, such as one leaf only or a height band, the fit check is extended with those rules. How geometry, data and maintenance are handled for technical enclosures and booths is covered in Implementing configurators for stores, booths and enclosures.
What comes out at the end?
The enquiry lists type, outer dimensions, plinth or wall mounting, finish, lock and, per cabinet, door, cooling option and every cut-out with its size, position in millimetres and check result, plus interior, cable entry at top and bottom and light. Name, company, email, phone, application and quantity are added. Page one of the PDF shows two views of the cabinet and the summary; page two draws each door from outside with its cut-outs and example dimensions in millimetres. Text and PDF are created in the browser only. In a project the door drawing can become a machining sketch or a priced bill of materials.
Example configurator · fictional product
Control cabinet configurator
Plan a control cabinet: wall-mounted, floor-standing or a bayed suite, sizes from a grid, door, lock, fans, windows and cooling unit with a fit check against the door frame – with an opening door, interior, a view of how bays join and a PDF enquiry.
Who such a configurator suits and how it is built for a range is covered in Control cabinet configurator software for enclosure manufacturers. The project process is on 3D configurator development.
Send us your grid and cut-out sizes – we show you what your door rules look like in a configurator.
Frequently asked questions
Can we set our own margins and lock zones?
Yes. Margin, spacing between cut-outs, lock zone size and the double-door width are single values in the demo. In a project your values go in, per type or per lock if needed.
Can the configurator produce machining data for the cut-outs?
The demo produces a door drawing with positions in the PDF, not production data. Because every cut-out is stored with size and position, an output for your production can be connected in a project.
Does it choose the right cooling unit?
No. The demo places fans and cooling units by space and example sizes only. Sizing the cooling stays with the manufacturer and the panel builder.
Sources
- Demo features: "Live in this demo" list on the control cabinet configurator library page, read 15 November 2026: modelwright.de/en/library/control-cabinet-configurator/
- Grid, fit rules, accessory sizes and output: demo source code (data.js: GRID, RULE, CUTS, ROOF_AC; app.js: fitOf, checks, sumRows, PDF) and schema notes; PDF scope: QA log of 15 November 2026, independent round.


