Technology

Building a configurator for halls, pavilions and modular buildings: data, 3D, floor plans, mobile

How a 3D configurator for steel halls, pavilions, guard booths, restroom blocks and site cabins is built: data files, geometry, floor plans, mobile, care.

Short answer: technically, a configurator for buildings differs from one for small products in three ways. The geometry is generated from dimensions rather than loaded as finished models; a roof-off floor plan is almost always needed; and the object is so large that the camera and controls on a phone need their own rules. Then there is maintenance: grids, prices and room types change, and they belong in a data file, not in program code. Our five example configurators show what that can look like.

Site cabin & welfare unit configurator – preview of the example configurator
Example configurator · fictional product · example values. Loads only when you click. Open the demo page →

What data does a building configurator need?

For halls and modular buildings, the documents your sales team already uses are usually enough. Full engineering data is rarely needed.

DataExampleUsed for
Grids and limitshall spans, pavilion sizes, module lengths, room widthsgeometry and allowed values
Component cataloguedoors, windows, light panels, roof formsoptions and placement rules
Rules in plain words"stacking from 16 ft", "showers need services"blocks, notes, checks
Finishescladding, timbers, RAL coloursmaterials in 3D
Price tablesprice by size and seriesprice guidance, if wanted
Photos and drawingsbrochure, elevations, detailsrecognisable geometry

In the restroom building configurator and the site cabin configurator, everything a manufacturer would replace with its own range sits in a separate data file: room widths, room depth, wall thicknesses, transport limit, module lengths, wall types, colours and texts in both languages. That is the separation we recommend for every building project.

Finished models or generated from dimensions?

A sofa or a lamp is usually loaded as a finished 3D model. A steel building in twelve spans, twenty lengths and eight eaves heights is not: that would be 1,920 models, before doors and colours. Buildings are therefore generated in the browser from dimensions, parametrically. Components such as doors, windows or stairs can still be finished models placed in the right spot.

Our two own demos in this group, the restroom building and the site cabin, are built from procedural geometry and drawn textures, with no photos or brand material. Your route may differ. If you have CAD data, we check before the start whether parts of it are suitable for the web; how that works is covered in CAD to web 3D configurator. For the building itself, parametric geometry from your grids is usually the faster route; your details, such as a particular eaves profile or knee-brace shape, are rebuilt from drawings.

Floor plans, views and states

Buildings need more views than products. In this group's demos they are:

  • Fixed camera views. The steel hall offers 3/4, gable, side and top views and toggles frame, doors and snow.
  • Roof-off floor plan. The restroom building hides roof and ceiling and shows room labels with example areas and door swings. The site cabin shows room zones with furniture blocks with the roof off, plus wall and zone plans.
  • States. Day and night for the restroom building, "close site" with shutters for the site cabin, doors that open when tapped.

The floor plan in particular is prone to mistakes that do not show in the normal view. The independent check of the restroom building found that door frames and fanlights were stacked in the middle of the building instead of sitting in the doorways; it was visible mainly in the floor plan and in the plan in the PDF. The defect was fixed before the demo went live. On the site cabin, overlapping room labels on narrow phones and plan text that was too small were found and fixed; plan text now measures 13.5 px on screen.

Large objects on small screens

Showing a 30 m steel building, or a restroom block with its forecourt, on a phone needs its own camera rules: the whole building must fit, zooming must not end up inside the facade, and the view must return cleanly after rotating. An early test run of the restroom building failed on exactly that: at extreme zoom the building was lost. The fix was a minimum distance of half the fit distance.

In an independent check, both own demos completed the full test journey on seven emulated screen sizes from 360 to 1,440 px wide, with no JavaScript errors, no controls under 44 px and recovery after loss of the WebGL context. Real devices were not tested.

Processing load and battery

A configurator that redraws all the time drains the battery and warms the phone. The two own demos only draw when something changes. For the restroom building, the independent check measured 0 draw calls in 3 seconds at rest, after loading and after rotating and resetting. For the site cabin, the same figure comes from the developer's own check; the independent check did not measure it again. Animations such as the shutters run on elapsed time, not on frames: on a slow device they stutter but finish on time. That was a fix after the first test run.

Languages, units and controls

The demos for the steel hall, the timber pavilion and the guard booth have an English interface, the pavilion and the guard booth with feet and millimetres. The restroom building and the site cabin are in German and English, the site cabin with metres and feet. In the checks of the two own demos, all visible text and the screen-reader labels were reviewed in both languages. For your project: each language and each unit affects interface, enquiry text and PDF and has to match in all three.

Privacy and measurement

In the two own demos, input is not sent or stored; enquiry text and PDF are created in the browser. Only which controls are used is counted, never the content: the developer's check of the restroom building confirmed that typed names and email addresses do not appear in the usage data. In your project we set up sending and analytics events to your requirements.

How is the configurator embedded?

A building configurator runs as its own page or embedded in your website, whatever your CMS, and on dealers' pages if you want. On phones and tablets the 3D can wait until the visitor opens it, with a still image until then. That is how the library works: on desktop the demo starts at once, on phones and tablets after a tap, and if it fails to load, a note with a direct link appears. For buildings this matters, because buyers often open your page on a phone in a farmyard, on a site or in a park, with patchy signal.

In the library, the demos run embedded next to the description; "Full screen" opens the demo on its own. In the restroom building and the site cabin, the in-demo button for your own enquiry leads to the form beside it instead of opening a new tab. That too was found in the independent check and then fixed.

Care after launch

Building ranges change: new lengths, new colours, new prices. If these values sit in a data file, a change is small and testable. At Modelwright, small changes are part of the monthly care; we do not offer a self-service editor as standard. What matters is that after every change, screen, enquiry text and PDF show the same values. In the two own demos, review, enquiry text and PDF use the same list of lines, and the checks compared them line by line.

The five examples

Example configurator · fictional product

Steel hall configurator

Plan a steel hall: machine or riding hall, width, length and wall height with drag handles, snow zone, gates and light panels, colours – with a sample price band and a PDF enquiry.

Halls & large structures · Dimensions and sizes · Colours · Options, modules and accessories

Example configurator · fictional product

Timber pavilion configurator

Put together a timber pavilion: seven series, size by drag handle or input, gable or hip roof, knee braces, privacy slats, wood species and stain – with sample prices and a PDF enquiry.

Halls & large structures · Dimensions and sizes · Colours · Materials and finishes

Example configurator · fictional product

Guard booth configurator

Plan a guard or ticket booth: three styles, length and width, roof, door, cashier window and equipment, colours and glazing – with foundation and shipping checks and a PDF enquiry.

Pods & booths · Dimensions and sizes · Colours · Materials and finishes

Example configurator · fictional product

Prefab restroom building configurator

Plan a prefab restroom building for a park, campsite or trailhead: pick the rooms, set the layout, roof and facade, tap doors to open them – with a roof-off floor plan, a day/night view and a PDF enquiry.

Pods & booths · Dimensions and sizes · Colours · Materials and finishes

Example configurator · fictional product

Site cabin & welfare unit configurator

Plan a site cabin or welfare unit: length from 10 to 32 ft, use, windows and doors on a grid, tap rooms with the roof off, stack two high or make it towable – and close the site with one click: the shutters come down and the doors are barred.

Halls & large structures · Dimensions and sizes · Colours · Materials and finishes

All five are example configurators with fictional products and example values. For how a project runs, see 3D configurator development.

Send us your grids and drawings – we tell you which route to the geometry fits.

Frequently asked questions

Do we need CAD data?

Not necessarily. For buildings, grid lists, drawings and photos are usually enough; we use CAD data when it is suitable for the web.

Does it run on a tablet at a site visit?

Yes, in the browser with no app. For shows or places without signal we settle the offline question in the project.

Who is responsible for the values in the configurator?

You as the manufacturer. The configurator applies your approved grids and rules; values affecting load-bearing capacity or foundations are taken only from your documents.

Sources

  1. Features of the example configurators: "Live in this demo" lists on the linked library pages, read 14 November 2026.

Read next