A street lighting network consuming 12 percent more energy than its rated load on a feeder serving 200 LED luminaires is not a statistical anomaly - it is a diagnostic signal. The rated load for those luminaires at full output is known within two percent. The scheduled dimming profile is programmed into the controller. The expected nightly consumption is therefore calculable within a narrow band. When actual consumption drifts above that band for three consecutive nights and the utility's only response is a monthly bill comparison, the gap between what the data contains and what the operator sees is the difference between a controlled network and one that is degrading without anyone noticing.
Street Lighting Consumption Has a Predictable Signature That Makes Anomalies Visible
A street lighting circuit operates on a fixed schedule with a known load profile. The luminaires switch on at a set illumination threshold, operate at full power for a programmed duration, then dim to a lower level until dawn. The total energy consumed on any given night is the sum of these intervals multiplied by the connected load. For a feeder with identical luminaires, the variation from one night to the next should be less than three percent, driven only by slight differences in dusk-to-dawn duration across seasons.
This predictability is what makes street lighting different from other municipal loads. A water pumping station draws power in response to tank levels and demand patterns that shift daily. A sewage treatment plant runs processes that vary with inflow quality. But a street lighting network has no process variability. Its consumption is deterministic. When the measured energy deviates from the calculated expectation by more than five percent, something physical has changed - a luminaire has failed, a controller has lost its dimming schedule, or the metering itself is incorrect. The operator who treats street lighting as a fixed load misses these signals entirely.
Feeder-Level Monitoring Separates Network-Wide Efficiency from Zone-Specific Anomalies
A single monthly energy bill for an entire ward tells the operator the total consumption but conceals where the excess is occurring. A feeder serving a commercial district may show consistent over-consumption while a residential feeder runs below its rated load, yet the aggregated figure shows a modest increase that triggers no action. The operational question is not whether the network is consuming more than expected - it is which specific feeder, at what time, and for how long.
When a feeder-level energy meter logs consumption at 15-minute intervals, the operator sees the load curve for that zone. A feeder with 150 luminaires rated at 80 watts each, dimmed to 40 watts after midnight, should draw approximately 6 kilowatts during the dimmed period. If the measured draw is 9 kilowatts, the feeder is consuming power equivalent to 75 additional luminaires running at full output. That excess is not a metering error - it is a physical condition that requires investigation. The operator who monitors at feeder level knows which zone to dispatch a crew to before the monthly bill arrives.
Luminaire Performance Degradation and Metering Anomalies Produce Different Signatures
A degraded luminaire does not draw more power - it draws the same power but produces less light. An LED driver that has lost thermal management may still consume its rated wattage while the light output drops by 30 percent. This is a maintenance issue that energy monitoring alone cannot detect. But a luminaire that has failed completely - a driver that has shorted or a surge that has damaged the power supply - may draw zero current or, in the case of a partial failure, draw current without producing light. The feeder load drops by the wattage of the failed unit.
A metering anomaly produces a different pattern. A current transformer that has drifted out of specification, a meter that has lost phase calibration, or a communication module that is reporting corrupted values will show consumption that jumps or drops without any corresponding change in the physical load. The distinguishing feature is the timing. A metering error typically appears as a step change at a specific timestamp and remains consistently high or low thereafter. A real load change - a luminaire failure, a controller reset - appears as a change that correlates with the operational schedule. When the feeder load drops by 400 watts at 2:00 AM and stays low through the morning peak, the operator can rule out a metering fault because the deviation is aligned with the dimming period, not with the full-power interval.
Night-Time Load Curves Reveal Operational Issues That Daytime Inspections Miss Entirely
A daytime inspection of a street lighting network checks for physical damage, pole alignment, and visible luminaire condition. It cannot detect a controller that has lost its dimming schedule and is running luminaires at full power all night. It cannot detect a feeder that is drawing current during the day when the luminaires should be off. It cannot detect a ground fault that is leaking current into the earth without tripping a breaker. These conditions are invisible to a visual patrol but clearly visible in the night-time load curve.
The load curve for a healthy feeder shows a sharp rise at dusk, a flat plateau at full power, a step down at the programmed dimming time, a second flat plateau at reduced power, and a sharp drop at dawn. A feeder with a failed dimming controller shows no step down - the load remains at the full-power level through the entire night. A feeder with a daytime leakage shows a small but nonzero current draw during the hours when the luminaires are switched off. A feeder with a ground fault shows a load curve that is elevated by a constant offset across all periods. These patterns are visible in 15-minute interval data but invisible in a monthly aggregate. The operator who reviews the night-time load curve weekly catches these conditions within days of their onset, not months later.
The Relationship Between Scheduled Dimming and Actual Consumption Diagnoses Control System Health
A programmed dimming schedule is a set of instructions sent to the controller. The actual consumption is the physical response. When the two diverge, the control system is not functioning as programmed. The most common failure is a controller that has lost its schedule due to a power interruption, a firmware fault, or a communication dropout. The controller defaults to full-power operation, and the luminaires run at 100 percent output for the entire night. The operator sees a feeder load that matches the full-power level continuously, with no step down at the programmed dimming time.
A subtler failure occurs when the controller retains its schedule but the dimming command does not reach the luminaire drivers. This can happen when a control cable is damaged, a wireless signal is blocked, or a driver has lost its address. The feeder load shows a partial step down - some luminaires dim while others remain at full power. The result is a load curve that drops by less than the expected amount. For a feeder with 100 luminaires programmed to dim from 80 watts to 40 watts, the expected drop is 4 kilowatts. If the measured drop is only 2 kilowatts, half the luminaires are not dimming. The operator knows that the control system has a zone-level fault, not a global failure, and can dispatch a crew to investigate the specific communication path or driver group.
Consistent Over-Consumption on a Single Feeder Indicates a Different Failure Mode Than Gradual Degradation Across Multiple Feeders
A single feeder that consistently consumes 15 percent more energy than its rated load, night after night, is not suffering from gradual degradation. It is operating with a specific fault - a controller stuck in full-power mode, a set of luminaires that have been rewired to bypass the dimming circuit, or a feeder that is supplying additional load that was never documented in the network inventory. The pattern is constant, repeatable, and zone-specific. The operator can isolate the feeder, verify the connected load against the inventory, and identify the discrepancy within a single site visit.
Gradual degradation across multiple feeders presents a different pattern. The over-consumption is small - two to three percent per feeder - but it appears on several feeders simultaneously and increases slowly over weeks or months. This is consistent with luminaire driver aging, where the internal power supply loses efficiency and draws more current to maintain the same light output. It is also consistent with a gradual increase in supply voltage across the distribution transformer serving the zone. An LED driver draws more current at higher voltage to maintain constant power, but the relationship is not perfectly linear, and the net effect is a small increase in energy consumption that is invisible on a single feeder but measurable across the network. The operator who sees this pattern knows that the root cause is not a localized fault but a systemic condition - aging infrastructure, voltage regulation, or a fleet of luminaires approaching end of life. The response is not a single repair but a programmatic replacement strategy informed by the rate of degradation.
The street lighting network is one of the few municipal assets where the expected consumption can be calculated to within three percent. When the measured consumption diverges from that expectation, the divergence is not noise - it is information. The operator who reads that information at feeder level, at 15-minute intervals, and compares it against the scheduled dimming profile sees failures, faults, and degradation patterns that are invisible to monthly billing data and daytime visual inspections. The gap between what the network is telling them and what they currently measure is the gap between reactive maintenance and informed asset management.