IMSA Roadway Lighting II common mistakes
IMSA Roadway Lighting II · Understand the traps and how to avoid them.
Computing average illuminance by averaging the maintained illuminance values of a few sample points taken near the poles, then declaring the design compliant without checking uniformity ratios.
Candidates treat roadway lighting design as a single-number problem because average illuminance is the most familiar metric, and they under-sample the layout so the dark mid-span and curb zones never enter the calculation. Uniformity (max/min or avg/min) is a separate pass/fail criterion that is easy to forget when the average already looks acceptable.
What to do instead
For every design or review problem, state both the average illuminance (or luminance) target and the uniformity criterion before evaluating any numbers. When a grid is given, compute max/min and average/min explicitly and check each against the standard separately. If the prompt gives only a few points, say that the grid is insufficient to demonstrate uniformity rather than concluding compliance.
Treating RP-8 and the MUTCD as interchangeable authorities, citing the MUTCD for illuminance levels or RP-8 for sign retroreflectivity and traffic control device requirements.
Both documents are routinely referenced on roadway projects, and candidates memorize document names without internalizing their scope. The MUTCD governs traffic control devices and includes lighting provisions for specific situations; RP-8 is the roadway lighting design practice standard covering illuminance, luminance, veiling luminance, and uniformity. Mixing them produces citations that are technically wrong even when the underlying number is right.
What to do instead
Build a one-page scope map: RP-8 for design metrics and levels, MUTCD for traffic control devices and warrants, NESC for supply and pole clearances, NEC for the premises wiring and service, local DOT/AASHTO for structural and geometric requirements. Before answering, ask which question the cited document actually answers, and name the governing document explicitly in the response.
Selecting luminaires by lumen output and wattage alone, ignoring the distribution type (Type I through Type V), backlight/uplight classifications, and the resulting spacing-to-mounting-height ratio.
Catalog lumen and wattage numbers are the easiest specifications to compare, so candidates default to them. Distribution determines where the light lands; a Type III and a Type V at the same lumen output produce very different roadway coverage, glare, and spill. BUG ratings and cutoff classifications add another layer that is often skipped.
What to do instead
When evaluating a luminaire, list four attributes before any photometric number: distribution type matched to the geometry (median, one-side, interchange), BUG rating versus the applicable zone, CCT and color rendering needs, and optical efficiency or luminaire efficacy. Then check that the spacing-to-mounting-height ratio implied by the layout is consistent with the chosen distribution.
Designing pole and foundation loads using only the luminaire weight and ignoring wind area, EPA, ice loading, and the second-order effect of arm length on bending moment at the base.
Weights are printed on the fixture spec sheet and feel like the load; wind pressure and projected area require looking up exposure categories and drag coefficients. Candidates also forget that a longer mast arm multiplies the wind force by its lever arm, so bending moment at the base grows faster than the luminaire weight suggests.
What to do instead
For every structural question, write the load path explicitly: luminaire and arm EPA times design wind pressure, times height to the point of application, plus ice load where applicable, plus pole self-weight and any attached equipment. Compare the resulting base moment and shear to the pole and foundation capacities rather than to weight ratings, and state the design code and exposure category used.
Sizing conductors and overcurrent protection from the luminaire wattage without accounting for driver inrush, continuous-load derating, voltage drop over long runs, and the difference between service and branch-circuit requirements.
Candidates apply a simple watts-over-volts calculation and stop. LED drivers draw high short-duration inrush current that affects breaker selection, lighting is a continuous load requiring conductors and protection at 125 percent, and long circuits on a 480 V or 240 V system can still exceed allowable voltage drop even when ampacity is fine.
What to do instead
Use a fixed four-step routine: compute load current including driver losses and any power-factor correction, apply the continuous-load multiplier, check voltage drop at the farthest luminaire against the project limit, then verify overcurrent device coordination with driver inrush. Keep service, feeder, and branch-circuit calculations separate and label which article of the NEC governs each step.
Answering maintenance and inspection questions with generic advice such as 'inspect regularly and replace failed lamps' instead of specifying the maintenance factor components, relamping group policy, and the inspection items that actually matter.
Maintenance content is perceived as soft and low-yield, so candidates skim it. Exam items on this domain typically test whether the candidate can decompose the maintenance factor into lamp lumen depreciation, luminaire dirt depreciation, and survival factor, and whether they know what to check on a pole and foundation after an impact.
What to do instead
Memorize the maintenance factor as a product of named components and be ready to compute or critique it. For inspection items, prepare a checklist covering luminaire aim and condition, lens cleanliness, pole plumb and corrosion, anchor bolt and handhole condition, grounding and bonding continuity, and photo-control operation. Answer with the specific item and its acceptance criterion.
Confusing luminance with illuminance and using the terms interchangeably when explaining veiling luminance, disability glare, or the reason a wet pavement reads brighter than a dry one.
Both are photometric quantities tied to roadway lighting standards, and many study sources use them loosely. Luminance is reflected light leaving the pavement toward the observer and depends on pavement reflectance class; illuminance is light arriving at the surface. Veiling luminance and glare calculations are luminance-based, so the mix-up corrupts the reasoning.
What to do instead
Anchor each term to its unit and observer: illuminance in lux or footcandles measured at the road surface, luminance in candelas per square meter measured from the driver's viewpoint. When a question mentions pavement reflectance class, wet conditions, or glare, assume luminance-based analysis and say so explicitly before computing.
Applying a single illuminance or luminance level to every roadway class instead of matching the level to the functional classification, pedestrian volume, intersection or interchange context, and design speed.
Candidates memorize one familiar number and reuse it. Standards define levels by roadway classification and context, with separate criteria for intersections, crosswalks, and conflict areas, and higher design speed generally raises the requirement. A single-number answer signals memorization without application.
What to do instead
Before quoting any level, state the classification, context, and design speed from the prompt, then select the corresponding criterion. For intersections and crosswalks, note that vertical illuminance and glare control are evaluated in addition to pavement illuminance. If the prompt omits the classification, say what additional information is needed rather than assuming.
Specifying an LED luminaire replacement without verifying driver compatibility with the existing control system, dimming protocol, and photocell or network interface, then treating the retrofit as a pure lamp swap.
LED retrofits look electrically simple compared with legacy HID systems, so candidates skip the control interface. Legacy photocells, timers, and adaptive controls may use voltage-based or proprietary signaling that a new 0-10 V or networked driver cannot interpret, and dimming curves and minimum output differ.
What to do instead
For any retrofit question, enumerate the interface chain: supply voltage and phase configuration, driver input and dimming protocol, control device output, and network or central management system compatibility. State whether the existing control must be replaced or reprogrammed, and confirm the driver's dimming range and standby behavior before declaring the retrofit feasible.
Answering safety questions about work on energized roadway lighting circuits with general lockout/tagout language while omitting the specific hazards of series circuits, multiple supply points, and photoelectric control feedback.
Roadway lighting circuits can be series-fed with high voltage, can be supplied from more than one point, and can be re-energized by photocell or time-clock action after the local switch is opened. Candidates who treat the circuit like a simple branch circuit miss these sources of backfeed and stored energy.
What to do instead
For every safety scenario, identify all sources of supply and control, including photocells, time clocks, and network commands, and state that the circuit must be opened at a verified disconnecting means, tested for absence of voltage, and grounded or isolated per the applicable rules. Name the specific hazard present in the scenario rather than reciting generic lockout steps.