Preparing Area Lighting for Photometric File Availability: A Step-by-Step Release Workflow

Area lighting — parking-lot poles, roadway arms, canopy and high-mast luminaires — is specified, modeled and rebated almost entirely from photometric data files. When a specifier asks for "the IES file," they are asking for a machine-readable description of how one specific luminaire distributes light, and the lighting design, glare review and utility paperwork all stop until that file exists and can be trusted.

This guide describes the release workflow in the order it actually runs: what must be true before a test request goes out, who owns each step, where the checkpoints sit, and how to decide whether a file is finished or merely generated.

What "file availability" actually means

A photometric file is available in the operational sense only when three things line up:

• A traceable test exists. The file is derived from an accredited measurement of a production-representative sample, and the report ID can be produced on request.
• The file describes an orderable configuration. Its header and photometry match the exact ordering code a specifier will put in a schedule, not a near neighbour in the family.
• The file is consumable. It imports cleanly into lighting design software, integrates back to the tested lumen output, and covers the angle range needed for glare and uplight analysis.

A PDF datasheet, a marketing lumen figure, or a file copied from a sister product satisfies none of these. The rest of this article is the process for getting all three.

Prerequisites: what must be settled before a sample ships

If any row is unresolved, the correct move is to hold the request rather than to test and re-test. Repeat testing costs more than a day of configuration discipline.

Step 1 — Build the test matrix from the orderable options

Start from the option list a customer can actually select, and create one test per combination that changes the light output or its distribution:

• Optic or distribution (Type II, III, IV, V, asymmetric forward-throw variants), including any field-interchangeable optics
• Correlated colour temperature and CRI option
• Lumen package or wattage setting, including each position of a field-selectable switch
• Accessories that sit in the optical path or alter output — visors, house-side shields, louvers, lenses, diffusers
• Voltage variant when the driver is not constant across the range

Two decisions belong here. First, whether a multi-position field-selectable product is measured at every position or restricted in the catalog to the positions with data; the second option is legitimate but must be reflected in the ordering code. Second, which configurations are priority for the first release — normally the highest-volume CCT and the distributions named in the largest open projects.

Output: a controlled test matrix with internal request IDs, each mapped to one ordering code and one intended file name.

Step 2 — Qualify the laboratory before the sample arrives

A photometric file is only as good as the measurement behind it, so qualify the lab on paper first:

• Accreditation scope covers luminaire photometry to ANSI/IES LM-79 under ISO/IEC 17025, and the report will be issued under that accreditation
• Goniophotometer type and darkroom capacity suit the largest luminaire in the family — a high-mast or long area arm must fit the rig at the required measurement geometry without truncating the distribution
• Calibration traceability and stated measurement uncertainty are documented in the report
• Deliverables include the LM-79 report, an ANSI/IES LM-63 file, and where the workflow requires it, an ANSI/IES TM-33 XML/JSON file
• Queue and re-test policy are known before you commit a launch date to sales

An in-house lab is acceptable on the same terms: accreditation must cover the test, and the report must be issued under it. Unaccredited internal data can support development, but it should not be the evidence behind a published file.

Step 3 — Condition and stabilize the sample under LM-79 conditions

LM-79 testing of solid-state luminaires is absolute photometry: the luminaire is measured as a complete system, because there is no lamp lumen rating to normalize against. That makes the physical setup part of the result.

• Ambient: 25 °C ± 1 °C at the device under test, in still air, with the temperature sensed close to the sample at the sample's height
• Orientation: mounted as installed — an arm-mounted area luminaire measured in the wrong plane produces a distribution that does not match the field
• Stabilization: per LM-79-19, light output and electrical power are considered stable when at least three readings taken at no more than 10-minute intervals across a 20-minute period vary by less than 0.5 %, measured as (maximum − minimum) divided by the last reading
• Recorded electricals: input voltage and frequency, input power, power factor, and current harmonic distortion as reported by the lab

Interrupting the run — changing an accessory, repositioning the sample, re-seating a driver — restarts stabilization. Note the restart in the test record so the report timeline is explainable.

Step 4 — Review the report before anyone generates a file

Files are generated quickly and reviewed rarely, so the report review is the last cheap place to catch a mismatch. Check, in this order:

1. Sample ID, build and date code match the frozen configuration and the bill of materials
2. Test voltage and frequency match the marketing claim you intend to make
3. Ambient temperature record and stabilization evidence are present
4. Mounting orientation and accessory configuration are described explicitly
5. Total luminous flux, input watts, efficacy, CCT, CRI (with R9 if the program asks for it) and chromaticity data are reported
6. The distribution is described in words and the measured angle set is complete

If the report lists a different lens, a different driver revision, or a nominal voltage you do not sell, stop. Generating a file from it simply distributes the error to every designer who imports it.

Step 5 — Generate and validate the photometric file

The North American interchange format is defined by ANSI/IES LM-63-19 (reaffirmed in 2025): a plain-text header of bracketed keywords such as [TEST], [TESTLAB], [MANUFAC], [LUMCAT], [LUMINAIRE], [LAMP], [BALLAST] and [OTHER], followed by a TILT=NONE line, the lamp and photometric parameters, and then the vertical and horizontal angle arrays with their candela values.

Four settings decide whether design software reads the file correctly:

• Absolute vs. relative photometry: for LED luminaires the lumens-per-lamp field is written as -1, with a ballast factor of 1.0. This tells downstream software that the candela values are measured luminaire output and must not be scaled by a lamp lumen value. Omit it and a designer's calculation silently inflates or deflates every result.
• Photometric type: Type C for architectural and area luminaires, with units and luminaire dimensions entered consistently in feet or metres.
• Angle coverage: a vertical range of 0–180° is what allows backlight, uplight and glare (BUG) evaluation; horizontally, either 0–180° or a symmetric 0–90° set is workable, but the choice must match what the analysis will ask for. A file truncated at 90° vertical cannot support an uplight or glare review.
• Header traceability: the test lab, test date, report number and the exact product code belong in the header, not only in an email.

Then validate. Import the file into two independent lighting programs, integrate the candela distribution back to total flux, and compare that figure with the LM-79 report. Any difference beyond the lab's stated measurement uncertainty is a blocker, not a rounding note. A second sanity check is the shape of the distribution: peak intensity and the 50 % beam angle should match the description in the report.

Step 6 — Name, version and publish as one package

Photometric files outlive the people who created them, so the name has to carry the identity. Use a fixed convention — manufacturer, family, CCT, optic, lumen package or wattage, voltage, revision — with no spaces and no informal suffixes such as "final" or "new." Keep a register that pairs each file with its report ID, release date and the file it supersedes.

Publish the file and the report together, and retire the previous version from every library it reached: the website download page, the submittal generator, the sales drive, and any distributor who has been quoting from it. A superseded file that stays downloadable is a defect report waiting to happen.

Step 7 — Handoffs and change control

Treat the file as configuration-controlled data. Re-test and re-issue when the LED board or bin changes, the driver changes, the optic or lens changes, an accessory is added inside the optical path, or the thermal design is revised. A finish change is usually photometrically neutral; a finish change inside the optical cavity is not.

Release gate checklist

• Configuration frozen and documented; sample is production-representative
• Lab accreditation, scope and calibration confirmed; report issued under accreditation
• Ambient, orientation and stabilization documented per LM-79-19
• Report reviewed against bill of materials, voltage claim and accessory set
• File written with absolute photometry (-1 lumens per lamp, ballast factor 1.0), Type C geometry, full angle coverage and traceable header
• Integrated flux reconciles with the report; distribution shape verified in two programs
• File named and versioned to convention, registered with its report ID, old version withdrawn
• Handoffs complete, with the change-control trigger list recorded

Common failure modes

• Relative photometry data published for an LED luminaire
• One file reused across CCTs, wattages or optics to save test slots
• File generated from an engineering sample that never matched the shipped build
• Test voltage that does not match the market where the product is sold
• Accessory configuration omitted, so a shielded luminaire is modeled as unshielded
• Angle range truncated at 90° vertical, blocking glare and uplight analysis
• Header fields left blank, making the file untraceable to any report
• Superseded files still live on the download page after a re-test

When to escalate instead of releasing

Stop the release and escalate to product management and quality when: tested flux or wattage misses the catalogued target; measured CCT or chromaticity falls outside the declared bin; the file cannot be reconciled to the report; the sample's build record differs from the current bill of materials; or a project has already been modeled with an earlier file that is now superseded. In each case the cost of a late, honest correction is smaller than the cost of a design that has to be rebuilt after submittal.

Expected outputs

A completed workflow yields: one controlled test matrix mapped to ordering codes; accredited LM-79 reports per configuration; LM-63 photometric files (and TM-33 XML where required) that reconcile to those reports; a versioned file register with supersession history; and handoffs that let a designer model the product, a utility review it, and a sustaining engineer know exactly what would invalidate the data. That package — not the file alone — is what "photometric file availability" means for an area lighting product.