IES Files and Lighting Simulations: What to Request Before Awarding a Street Light Tender
By
/ November 17, 2026
A street light tender is usually decided twice. The first decision happens in the evaluation room, on paper: does this bidder prove the road will reach the required lighting class? The second happens two years later, on site, when the measured illuminance is compared against the simulation that won the contract. Bidders who cannot produce photometric files fail the first test. Bidders who produce simulations built on optimistic assumptions fail the second one, and the cost lands on the buyer.
This guide covers both sides: what an IES file actually is, how to read the three numbers a Dialux or Relux report is really selling you, and the document set you should demand before award rather than after. It is written for procurement officers, consultants and EPC contractors who have to defend an award decision, not for lighting designers who already own the software.
What an IES File Actually Contains
An IES file is a plain text photometric description of one luminaire: how much light it emits and in which directions. The format is defined by IES LM-63, and files carry the .ies extension. The European equivalent is EULUMDAT, extension .ldt, which carries the same core data in a different layout. Both encode a luminous intensity distribution – candela values on a grid of C-planes and gamma angles – plus the total luminous flux and the physical position of the photometric centre.
That last detail matters more than it sounds. The photometric centre is the point from which the distribution was measured, and simulation software uses it to place the luminaire in space. If a supplier hands you a file whose photometric centre sits below the actual LED array, the software will model the light source lower than it truly is, and the resulting uniformity figures will look better than the road will ever deliver.
The critical limitation: one file describes one luminaire at one drive current. A product family sold as 60W, 90W and 120W from a shared housing needs three files, not one scaled by a factor. A family offered in 3000K, 4000K and 5700K needs a file per CCT if the optics or the LED bin changed. When a bid package contains a single IES file covering an entire range, ask which variant was measured and how the others were derived.
Document
Typical extension
What it proves
What it cannot prove
IES photometry (LM-63)
.ies
Directional intensity distribution and total flux of one measured luminaire
Nothing about lifetime, ingress protection or field consistency
EULUMDAT photometry
.ldt
The same data in the European format used by Relux and Dialux
Nothing beyond what was measured on the sample
LM-79 test report
.pdf
Electrical and photometric performance measured on a sample under lab conditions
Performance of the production line six months later
Simulation project file
.dlx / .evo / .rsn
The actual layout, aiming, maintenance factor and calculation grid used
That the model inputs match what will be installed
Rendered image or PDF sheet
.pdf / .jpg
That someone ran a simulation
Almost everything – renders hide the assumptions that decide the result
The last row is where most tender evaluations go wrong. A glossy isometric render with coloured contours is persuasive and nearly information-free. The project file behind it is what you can audit.
What a Lighting Simulation Can and Cannot Prove
Dialux evo, Relux and AGi32 all solve the same problem: they take photometric files, place them on a defined geometry, and compute illuminance on a grid. The calculation is deterministic. The assumptions feeding it are not. A simulation is only as trustworthy as the input sheet behind it, and that input sheet is the document you should be reading instead of the render.
For solar street lighting the geometry problem is bigger than for mains-fed lighting, because the pole and the luminaire are usually supplied together. A simulation run at 8 m mounting height for a product that ships with a 6 m pole is not a conservative error – it is a different project. Confirm that the mounting height, overhang, tilt angle and spacing in the model match the bill of quantities, item by item.
For grid layout and spacing arithmetic you can sanity-check before any software is involved, our spacing calculator and wattage, pole height and spacing guide cover the manual method. If the simulated spacing implies a spacing-to-height ratio the photometry cannot support, the model is wrong somewhere.
How to Read the Three Numbers That Decide the Award
Almost every road lighting specification, whether it cites EN 13201, CIE 115 or a national standard derived from them, comes down to three families of metrics. Ask for all three per calculation zone, and ask which lighting class the zone was evaluated against – the class is set by the road authority, not by the bidder.
Illuminance: average and maintained
Average maintained illuminance is the headline figure, expressed in lux on the carriageway or on the pedestrian area. The word that carries the risk is maintained: it should already include lumen depreciation, luminaire maintenance and, where relevant, surface soiling. A calculation at initial lumens is a calculation of the first night, not of the maintenance period the contract covers.
Uniformity: U0 and Ud
Uniformity tells you whether the road is evenly lit or striped with bright pools and dark gaps. U0 is minimum divided by average illuminance; Ud is minimum divided by maximum. A design can hit the required average and still fail uniformity, which is exactly the failure mode that produces complaints about dark patches between poles. Report both, and check they were computed on the same grid as the average.
Glare: threshold increment or glare rating
Glare metrics describe how much a driver’s or pedestrian’s vision is degraded by the installation itself. Road lighting schemes typically report threshold increment as a percentage; pedestrian and area schemes often use a glare rating instead. Glare is the metric most often omitted from a tender submission, because it is the one that punishes small, high-intensity luminaires mounted low. If it is missing, the package is incomplete.
Metric
Symbol
What it tells the evaluator
How it gets gamed
Average maintained illuminance
E avg
Overall light level on the defined grid after depreciation
Calculated at initial lumens, with maintenance factor set to 1.0
Overall uniformity
U0
Worst-lit point relative to the average – the dark-gap test
Computed on a coarse grid that skips the gaps between poles
Uniformity (min/max)
Ud
Peak-to-trough spread across the zone
Reported instead of U0 to hide a weak minimum
Threshold increment
TI
Disability glare as a percentage
Omitted entirely, or reported without the observer positions
Glare rating
GR
Glare for pedestrian and area classes
Reported for a viewing direction that flatters the design
Maintenance factor
MF
The allowance for depreciation over the service period
Set close to 1.0, which removes the allowance
Power density indicator
PEC / Dp
Energy used per unit of lit area per year
Quoted from a different dimming schedule than the one specified
One more number deserves a line in the evaluation sheet: the dimming schedule the calculation assumed. Adaptive lighting is legitimate and often required, but a simulation that assumes 50 percent output after midnight must say so, and the controller must be configured to actually deliver it. Our panel and battery sizing covers how photocell, timer and microwave sensor settings translate into real energy savings.
The Document Set to Request Before Award
Treat the photometric submission as a deliverable with its own schedule, not as an attachment someone forwards at the last minute. The list below is what a defensible package contains.
Native photometric files (.ies or .ldt) for every model, wattage and CCT variant offered, not a single file for the range.
The simulation project file (.dlx, .evo or .rsn) as well as the PDF – the project file is auditable, the PDF is not.
An assumptions sheet listing maintenance factor, lamp lumen maintenance, luminaire maintenance, surface reflectance table and the calculation grid spacing.
A pole layout drawing with mounting height, overhang, tilt and aiming angles, matched to the bill of quantities.
An LM-79 test report from an accredited laboratory, with the laboratory name and report number visible.
LM-80 data and TM-21 projection for the LED package, and ISTMT data for the module temperature in the actual housing.
A declaration separating measured lumens from chip or theoretical lumens, and stating whether the photometry is absolute or relative.
The lighting class the design was evaluated against, and the standard edition used for the calculation.
Two of those items are frequently missing even from otherwise strong bids: the ISTMT data and the absolute-versus-relative declaration. Both concern whether the luminaire delivers in the field what it delivered on the measuring bench. A well-run supplier should be able to answer them without going back to the factory.
Red Flags in a Tender Photometric Package
These patterns recur across markets, and each one is cheap to check.
Only renders and PDF contour plots, no native file. The bidder either does not have photometry or does not want it audited.
One IES file reused across three wattages, with the flux in the header unchanged.
Maintenance factor of 1.0, or a calculation explicitly run at initial lumens while the specification asks for maintained values.
Uniformity reported as an average of ratios, or not reported at all.
Glare metrics absent, or reported without stating observer positions and viewing directions.
Mounting height in the model lower than the pole height in the bill of quantities – a lower luminaire always looks better on paper.
Grid spacing coarser than the inter-pole spacing, which flatters uniformity by skipping the dark zones.
Lumen figures quoted “up to”, with no measured value tied to a report number.
Test reports from a laboratory that cannot be identified, or a report number that does not resolve to a scope covering luminaires.
None of these proves bad hardware. Each one proves that the award decision cannot be defended if the installation underperforms, which is the actual risk a procurement officer is carrying.
Sanity-Checking Photometry Without Software
You do not need Dialux to catch a weak submission. Three checks take ten minutes.
Open the .ies file in a text editor. The header contains the total luminous flux. Compare it with the datasheet figure for the same model and wattage; a mismatch means one of the two documents is stale.
Check the file’s C-plane and gamma-angle resolution. Very coarse grids can under-represent a sharp cut-off, and cut-off shape is what determines glare and spill light.
Compare the number of photometric files supplied against the number of SKUs offered. If the ratio is not one to one, ask which variants are interpolated and how.
For the layout arithmetic that sits underneath any simulation – how many fixtures, at what spacing, for a given area – the worked examples in our lux calculation with worked examples apply to open areas and facades, and the solar parking lot lighting layout guide covers car park geometry specifically. Both are useful cross-checks against a submitted design.
Writing the Photometric Requirement Into the RFQ
Most photometric disputes start because the RFQ asked for “IES files and a Dialux study” without defining either. A requirement sentence that closes the gap looks like this:
Bidder to submit native IES LM-63 photometric files for each luminaire model and wattage offered, together with the native simulation project file, the assumptions sheet including maintenance factor and grid spacing, and the lighting class against which the design was evaluated. Submissions containing renders only, or a single photometric file covering multiple wattages, will be treated as non-responsive. Test reports to be identified by laboratory and report number.
That wording is deliberately mechanical. It converts a judgement call into a checklist item, which is what you want when three bids arrive on the same afternoon and one of them is 15 percent cheaper for reasons nobody can articulate. The solar street light tender specification checklist covers the rest of the technical schedule, and the pre-shipment inspection checklist covers what to verify once the goods exist.
Where Qichenshop Stands on Photometric Submittals
Being precise here protects both sides. Our standard configuration for solar street lights includes dusk-to-dawn photocell control, timer control and microwave radar motion sensing. NEMA socket provision, Zhaga Book 18 interfaces, Wi-SUN mesh and smart city platform integration are available as optional or customizable integration, quoted per project and never represented as standard.
On photometry, availability is model-specific rather than universal, so we confirm the photometric file package for your exact model, wattage and CCT in writing at RFQ stage, before you build a submittal around it. We would rather tell you on day one which files exist than have you discover a gap during evaluation. Our current model range, including the A21 all-in-one solar street light and the A01 split solar street light, is documented at model level so the submittal schedule can be built against real configurations.
Commercial term
Standard position
Minimum order quantity
From 50 units
Payment terms
T/T, 30 percent deposit and 70 percent before shipment
Production lead time
Typically 15 days for standard configurations, 15 to 25 days for customized builds
Sample fee
OEM USD 50, ODM USD 300, plus freight collect, refundable against a first order of USD 1,000 or more
Quotation validity
30 days from issue
Warranty
5-Year Limited Warranty
Ingress protection
IP65 for the luminaire housing
Photometric files do not light a road. They are the only part of a bid that lets someone else check whether the road will be lit to the class the authority asked for – which is precisely why they belong in the evaluation, not in an appendix nobody opens.
If you are preparing a tender package and need the photometric documentation scope for a specific model, send the model, wattage, CCT and mounting height with your request: contact Qichenshop.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.