Technology

Implementing a lighting or acoustics configurator: data, estimates and tech

Data preparation, light and reverberation estimates, photometric files, WebGL, mobile, privacy and upkeep for a luminaire or acoustic-panel configurator.

Short answer: a configurator for luminaires or acoustic elements needs three kinds of data: geometry (profiles, connectors, element formats), rules (lengths, spacings, heights, combinations) and performance data (photometry or absorption values). The geometry and rules are usually quick to prepare from drawings. The performance data is where most decisions sit: show a clearly labelled estimate, point planners to your published files, or both. The technical side, 3D in the browser, mobile and privacy, is well understood and should not dominate the project.

This guide is for product managers, technical marketing and digital leads at manufacturers of lighting systems, acoustic baffles, ceiling rafts and wall panels. It uses two of our example configurators with fictional products and example values as evidence, but only for what they actually do.

LUMA LINE linear luminaire – preview of the example configurator
Example configurator · fictional product · example values. Loads only when you click. Open the demo page →

What data does the build need from you?

For a lighting system

  • Profile sections for each optic or housing variant, as a drawing or CAD section. Our LUMA LINE example is built from extrusion sections (40 × 62 mm for the opal version, 40 × 59 mm for the recessed optics), swept along the layout with mitred corners [1].
  • Connectors and accessories: corners, T and cross joints, straight joints, end caps, canopies, suspensions, feeds. In the example each of these is a parts-list line with its own article code.
  • Limits: maximum piece length, maximum span between suspension points, power per driver and per feed. These become rules, not geometry.
  • Finishes and options: anodised colours, RAL colours, colour temperatures, lumen packages, with the article number segment each one adds.

For acoustic elements

  • Element formats: baffle heights and lengths, raft sizes and shapes, thicknesses per material, edge profiles.
  • Suspension and spacing rules: number of cables, spacing ranges, minimum clear heights.
  • The colour card: names and reference values. On a screen these are approximations; our baffle example labels its felt colours as approximate screen colours with fictional names [1].
  • Absorption values, if you want them shown (see below).

Photos, dimensions and drawings usually suffice; CAD is used where it is suitable for the web. How STEP or native CAD exports become a light web model is explained in from CAD to a web 3D configurator.

Generic geometry or your own product?

Both examples are built with Modelwright's own geometry. The baffle demo's elements, rooms, furniture and textures are generated in code, with no manufacturer CAD, drawings or images; the LUMA LINE luminaire is built from its own section drawings [1]. That keeps the demos free of anyone's designs, and it shows the method: in a project, the same approach uses your sections, formats, edge profiles and colour card, so the model matches what you actually sell. A generic stand-in is fine for a pitch; for a buyer who compares your profile with a competitor's, it is not.

Should a configurator calculate light?

Showing light is the reason a lighting configurator is more persuasive than a product image, but it has to be honest about what it is. In the LUMA LINE example, the luminaire is modelled as line emitters with a cosine-power (cos^n) intensity distribution, where the exponent n depends on the optic. Floor, walls, table and ceiling receive their illuminance in small maps that are recalculated whenever the configuration changes; there is no real-time global illumination [1]. The panel shows an average illuminance on the table and is labelled as a simplified light estimate that is not a lighting design.

That is the right level for a sales tool. A formal design is the planner's job, in their own software and against the requirements for indoor workplaces in DIN EN 12464-1 [2]. What the manufacturer can do is make the planner's job easy. The open Global Lighting Data Format (GLDF), maintained by DIAL and RELUX, describes product features and variants and packs photometry and geometry into one file [3]. A configurator can link the matching file for a chosen variant. Producing and validating those files is the manufacturer's responsibility; the configurator only points to them.

ApproachWhat the visitor getsWho is responsible for the numbers
Visual onlyLight colour and glow, no figuresNobody: no figures shown
Labelled estimateCones, false colours, an indicative lux valueThe estimate is illustrative and says so
Link to planning dataYour photometric or GLDF file for the variantThe manufacturer, for its published data

What about absorption values and reverberation?

The baffle example calculates a reverberation time after Sabine, T = 0.161 · V / A, with one example coefficient per surface [1][4]. It shows the full calculation table and labels the result as an example calculation that is not acoustic design. Sabine's formula is a simplification; it is most reliable when absorption is low, and other formulas give better results for typical values [4].

In a project you have two options. Keep the example approach with your own values, clearly labelled. Or show your published, measured absorption values per product and let the planner do the room calculation. In Germany, the acoustic quality of rooms such as classrooms, conference rooms and canteens is planned under DIN 18041 [5]. Which values you publish, and whether a room meets a requirement, is not something a configurator can certify: the manufacturer is responsible for its product data and the planner for the design. We do not invent or adjust performance values.

What runs in the browser?

Both examples use WebGL through three.js, with no app or plugin. Models for a project are delivered as glTF, the royalty-free format of the Khronos Group for transmitting and loading 3D scenes [6]. Three practices matter more than the library:

  • Render on demand. In the builder's test of the baffle example, the page drew 0 frames in 2.5 seconds of idle time, both after loading and after a drag and reset [1]. A configurator that redraws constantly drains phone batteries.
  • Reduced motion. The baffle example lowers its elements into place on their cables in a wave; with the operating system's reduced-motion setting, the elements are placed instantly [1].
  • Recovery. If the browser drops the 3D context, the baffle example recovers and renders again; a red retry box is ready if it stays lost [1].

Page weight is the other budget. The LUMA LINE page with three.js and its room model transferred about 2,419 KB on a local test server [1]. That is a lab measurement, not field data from real visitors, and it is a reason to load 3D only when the visitor opens it, which is how our pages work.

Mobile and accessibility

Specifiers may look at a product on a phone between meetings. The baffle example passed its builder's mobile test harness on emulated devices at 393 × 852, 375 × 667 and 430 × 932, and at 360 × 800 after a landscape overlap was fixed and re-tested [1]. Emulation is not a real phone, and in a project you also review the configurator on your own devices via a private link. Accessibility goes beyond touch targets: every choice should also be readable as text, as in a summary, so the configuration does not depend on seeing the 3D view.

Privacy

A configurator collects room sizes, company names and contact details. In the baffle example nothing typed is sent or stored: the enquiry text and PDF are created in the browser, there are no requests to third parties at runtime, and usage statistics record only the names of the controls used [1]. In a project, the enquiry goes to your sales team by email or webhook, and what is logged is agreed with you and described in your privacy notice.

How do you keep it up to date?

Ranges change: a new colour, a new raft size, a discontinued optic. In the baffle example, everything a manufacturer would replace, from room presets and element sizes to materials, example coefficients, colours and interface text, lives in one data file, separate from the 3D code [1]. That structure is what makes small changes cheap. At Modelwright there is no self-service editor as standard; small changes to products, rules or prices are made by us as part of hosting and care, within the monthly allowance. Scope and prices are covered in what a 3D configurator costs.

Try the examples

The LUMA LINE linear luminaire configurator shows layouts on a ceiling grid, light cones and a labelled light estimate; the acoustic baffle and panel configurator shows elements in a furnished room with a labelled reverberation example. Both are example configurators with fictional products and example values; no manufacturer ordered, reviewed or endorsed them. How their rules work is described in linear lighting configurator rules and the matching guide for baffles; how enquiries leave them is in lighting and acoustics configurator enquiries. The service is described under custom 3D configurator development.

Sources

  1. Demo evidence: source files of the LUMA LINE and acoustic baffle example configurators, the builder's QA notes for the baffle demo and the L1 measurement for LUMA LINE (all read 14 November 2026)
  2. DIN Media: DIN EN 12464-1:2021-11, Light and lighting – Lighting of work places – Part 1: Indoor work places, read 14 November 2026: dinmedia.de
  3. GLDF – Global Lighting Data Format, read 14 November 2026: gldf.io
  4. Wikipedia (German): Nachhallzeit, read 14 November 2026: de.wikipedia.org
  5. DIN Media: DIN 18041:2016-03, Acoustic quality in rooms, read 14 November 2026: dinmedia.de
  6. Khronos Group: glTF, read 14 November 2026: khronos.org

Read next