Lumseq logoLumseq
Lighting Journal

Product knowledge

IES/LDT Files for LED Lighting: Verify the Exact Luminaire Before Using a Calculation

Match IES/LDT files to the exact LED luminaire, optical assembly and output setting, then keep the test evidence and project calculation linked to that configuration.

IES/LDT Files for LED Lighting: Verify the Exact Luminaire Before Using a Calculation

Key takeaways

  • Connect the offered configuration, supporting evidence, photometric file and project calculation in one approval record.
  • A familiar filename or successful import does not establish that the data represents the quoted luminaire.
  • Record optics, length or housing, output setting and CCT or tunable state; ask the supplier to explain which variants the evidence covers.
  • Keep file changes, calculation assumptions and proposed substitutions visible for technical review.

Start with the offered luminaire, then choose the file

Before using an IES or LDT file, confirm that it represents the exact LED luminaire configuration being purchased and that the supplier can explain its supporting evidence. Successful import alone does not establish product identity, test coverage or the result in your installation.

Start from the quotation line and approved drawing. Record the manufacturer, complete model and suffix, revision, optics, housing or length, output setting and colour configuration. Ask the supplier to identify the corresponding file and explain any differences. The decision becomes especially important when a narrow-beam module is replaced with a wider optic, or a strip is installed in a different profile and diffuser.

Separate four pieces of evidence

IES and EULUMDAT/LDT are photometric file formats used in lighting design. DIALux's official FAQ lists LDT and IES among its supported standard formats. Its LDT Editor can open and edit both formats, then save the result as EULUMDAT. This editing and conversion capability is a practical reason to retain the supplier's original file and document later changes.

A test report, a data file and a project calculation answer different questions. DOE's current metrics page identifies ANSI/IES LM-79-24 as Optical and Electrical Measurements of Solid-State Lighting Products. That measurement context should remain distinct from the software file and the assumptions used to model a room. None of these records alone establishes every installation or destination-market requirement.

DOE's March 2012 explanation of LM-79-08 gives a useful report-reading method: identify the tested configuration/version and date, the laboratory and method, and the light source, power supply and optical components. Compare the photographs and details with the specification. This is historical explanatory guidance; it does not establish requirements in the current edition.

RecordWhat to connectQuestion to close
Offered configurationQuotation, exact code, revision and assembly drawingWhat will be supplied?
Supporting test evidenceIdentified configuration, report/date, laboratory, method and conditionsWhat was measured, and what does the supplier say it covers?
Original IES/LDT fileFilename, version or date and supplier's report mappingWhich configuration does this data represent?
Project calculationFile used, layout, orientation and calculation settingsWhat installation has been modelled?

Use an exact-configuration matching table

Ask the supplier to complete a matching table before the file is approved for design. A missing field should stay open until its significance is explained. File headers can help identify a product, but an abbreviated description is not a substitute for a controlled link to the offered configuration.

This does not mean every commercial variant must have a separate test. Ask for the documented basis for any shared coverage, derived data or other representation, and have the responsible technical reviewer decide whether it supports the proposed use. Do not assume a family name makes all optics, output settings and colour options interchangeable.

Match fieldSupplier response needed
IdentityManufacturer, complete model/suffix, revision and drawing reference
Optical assemblyLens or reflector, diffuser, accessories and beam designation
Physical assemblyHousing, finished length and relevant mounting arrangement
Operating stateRated output or drive current, CCT and tunable/dimming state represented
Data basisOriginal file, date/version, report mapping and explanation of covered variants
DifferencesEvery deviation from the quotation, with reviewer disposition

Keep the file basis separate from project settings

Ask whether the supplied data is absolute or relative photometry, what output basis applies and whether any scaling or conversion has already been performed. Obtain the supplier's explanation before adjusting values. Changing a lumen entry or multiplying output is not, by itself, evidence that a different wattage, length or optical assembly has been represented correctly.

DOE's 2012 explanation describes lighting software combining test data, typically IES-format files, with geometry, surface reflectance and all luminaire contributions. In the project record, retain the luminaire positions, mounting heights, aiming and orientation, room geometry, surface reflectances, calculation surfaces and maintenance assumptions. Have the designer check these against the intended installation. A correct product file can still be used in the wrong orientation or with unsuitable room assumptions.

Treat glare and other application targets within their appropriate calculation and assessment scope. A filename or an isolated product claim should not silently replace the project's acceptance criteria. Keep any required site measurements and final installation checks assigned to the responsible party.

Make substitutions reopen the relevant checks

Suppose a quotation identifies a 3000 K spotlight with a narrow optic, but the file description names only its model family. Ask for the exact optic and operating-state mapping before accepting the calculation. If the supplier later proposes a different optic or output option, return that change to the designer rather than carrying over the previous result.

Keep the original file, the version actually used, the calculation report and the approved product schedule together. Record who changed a file or design setting, why it changed and which result was reviewed. A file checksum can help distinguish versions in your archive; it identifies bytes, not their accuracy or suitability. Also check software access separately: DIALux's current FAQ says non-member products may require an appropriate subscription.

An RFQ request buyers can adapt

Please identify the IES/LDT file for the exact quoted luminaire, including model/suffix, revision, optics, diffuser, housing or length, output setting and CCT or tunable state. Return the original file, its version/date, supporting report reference, documented coverage basis and all differences from the offered configuration. Explain any conversion or scaling. Mark unavailable or unverified items explicitly.

Send Lumseq your application, destination market, exact proposed configuration, supply voltage, quantity and layout or calculation requirements. Confirm which photometric files and supporting documents are available for that option before relying on a calculation. Keep product selection, document review and final project acceptance connected to the same identified configuration.

Frequently asked questions

Questions buyers ask

Does an IES or LDT file prove that a luminaire is certified?

No. It is a photometric data input. Request the relevant certification or compliance evidence separately for the exact model, market and intended use.

Can one photometric file cover several luminaire variants?

Ask the supplier to identify the represented configurations and document the coverage basis. Have the technical reviewer assess whether that basis supports the proposed configuration and use.

Can I change the lumen value to model another output option?

Obtain the supplier's data basis and a designer's review first. Record any permitted scaling and its limits; a numerical change alone does not establish the performance of another configuration.

What should I retain with the final lighting calculation?

Keep the approved product schedule, original and used file versions, supporting evidence mapping, design settings, calculation report and the disposition of substitutions or other open items.

Sources and references

DIALux: LDT EditorDIALux: Frequently asked questions — luminaire dataU.S. Department of Energy: Metrics and Test MethodsDOE / PNNL: Understanding LM-79 Reports — March 2012, historical explanation of LM-79-08

Talk to the product team

Planning an OEM or commercial lighting order?

Send your application, specification and destination market. We will help narrow the product and sample options.

Discuss on WhatsApp