Family data guide
Parameters in a Revit lighting family made from IES
BIMMER uses the IES file for photometric distribution and available measured metadata, combines that with manufacturer-entered product identity and electrical fields, and writes the resulting data into the Revit lighting family. IES is not a complete product datasheet, so fields it does not authoritatively contain remain editable rather than being guessed.
Direct support status
| Input | Directly accepted? | Required action |
|---|---|---|
| IES photometric web and declared values | Yes | Parsed and validated where present in the file. |
| Manufacturer identity/product code | With preparation | Review or enter it before generation. |
| CAD geometry dimensions | With preparation | Derived from/imported geometry and checked against the product. |
| Unstated IP, finish, cut-out or warranty data | No | Enter authoritative catalogue values; BIMMER does not invent them. |
The BIMMER workflow
- Validate the IES and identify which photometric/electrical values are actually declared for the tested luminaire.
- Review BIMMER’s extracted values, then enter authoritative manufacturer fields such as product code, description and other catalogue data.
- Generate the RFA and inspect Type Properties plus the photometric web in Revit.
- Schedule/tag the fields needed by specifiers, edit permitted values and re-issue when the source data changes.
What IES can authoritatively provide
An LM-63 file primarily provides the luminous-intensity distribution and supporting test metadata. Depending on the file, values such as lamp count, lumens and electrical information may be available. The exact content varies, so a robust workflow parses what is present and flags inconsistencies rather than assuming every laboratory writes the same optional fields.
What must come from the manufacturer
Product code, marketing description, finish, ingress protection, cut-out, mounting, warranty and other catalogue attributes are not reliably encoded in the photometric web. They should be entered from controlled product data. BIMMER keeps relevant fields editable so the family can reflect the authoritative catalogue without pretending the IES contains it.
Type data should remain usable
After generation, open Type Properties and confirm names, units and values. Test the fields in a schedule and tag. A family with many populated strings is not useful if the values are unverifiable, duplicated or impossible to maintain.
Common failures and what to change
IES values disagree with the latest datasheet.
Confirm the photometric file revision and product variant; replace the IES or correct the controlled source before re-issue.
Optional IES metadata is blank.
Do not fabricate it. Enter only manufacturer-authoritative product fields in the editable parameter step.
Units or parameter names confuse Revit schedules.
Review the generated Type Properties and schedule/tag behavior as part of the release checklist.
Questions manufacturers ask
Does IES contain the luminaire’s full product data?
No. It primarily contains photometry and related test metadata. Product identity, finish, IP rating and other catalogue fields must come from authoritative manufacturer data.
Can parameters be changed after conversion?
Relevant family/type fields remain editable. For a controlled catalogue, make the change in BIMMER’s source record and re-issue so the next RFA version stays traceable.
Primary references
- Specify an IES file for a light source in Revit — Autodesk
- IES lighting standards library, including LM-63 — Illuminating Engineering Society
- About importing ACIS objects into Revit — Autodesk