Support for ANSI/IES TM-32-19 Lighting Parameters

[dan.stine]

The Illuminating Engineering Society (IES) BIM Standards committee recently created a list of Autodesk Revit enhancement and feature requests based on a membership survey. We have shared a prioritized list with Autodesk and are posting them here, on Revit Ideas, to build community support to benefit the lighting design industry.

Please consider upvoting this Revit Idea.

Description:

Support for ANSI/IES TM-32-19, Lighting Parameters for Building Information Modelling (published in 2019). Automated way to rename parameters for a batch of Lighting Fixture Families in compliance with ANSI/IES TM-32-19. This standard includes parameter naming conventions, broken out by LOD. Perhaps could be accomplished by one or more Shared Parameter files, shipped with the Revit installer?

Revit content should support modern light fixture definitions. That is, Revit geometry in host family, IES files (different file extension). This would enable improved standardization of Lighting Fixture Family parameter names. Such a feature could be used to support other standards as well, beyond ANSI/IES TM-32-19. (To be clear, we still need support for LM-63 as well.) Concerning LOD specifications, affecting ANSI/IES TM-32-19 standard, Revit should comply with the latest updates of Standards and BIM Forum, USA editions. According to BIM Forum USA, recently updated to version 2021, the LOD Specification is organized by CSI Uniformat 2010 and Omniclass, with the subclasses expanded to Level 4 (and in a few cases to Level 5) to provide detail and clarity to the element definitions.

[MichaelWarwick7522]

Whilst generally a good idea, a better developed one is the CIBSE Product Description Templates and the BIM Hawk tool. Rather than yet another North American alternative to international efforts, it would be better if the parameters in TM-32-19 were aligned with the CIBSE PDT parameters and GUIDs. Also the CIBSE effort covers more than just luminaire data and touches on most MEP components.

[Samuel.Arsenault-Brassard]

Perhaps if the IES standards were not paid documents, they would have better luck getting support for their standards. I'd love to review it, but I'm not paying $50 to work for free.

Frankly, at this point, I'm more annoyed that FBX files with IES data exported from Revit lose all the IES data when opened in 3ds Max.

[MichaelWarwick7522]

I'm liking the 2024 verson of the standard much more. It is a shame that all the GUIDs in there are new rather than using the ones from CIBSE, ANZRS, or ISO (so yet another example of "standards are good so lets make one"). At least the NEMA and IES GUIDs are aligned. I'm up-voting this idea, however I would prefer that the EU or ISO GUIDs were used as the basis for anything shipped by AutoDesk. If anyone knows of a tool to convert shared parameters in project and family files from one standard to another, please post here.

[dan.stine]

Great comments, Michael. Revit supports a single format for its shared parameter GUIDs so we had to use new ones. The TM-32-24 comes with an Excel file that maps the GUIDs for multiple standards. I will be participating in a presentation soon, hosted by IES, on some workflows related to the standards and will feature developers working on translation... so please stay tuned for that.