Download presentation
Presentation is loading. Please wait.
1
Street Lighting Controls
City of Seattle Street Lighting Controls Presentation by Ahmed Darrat, PE Seattle Department of Transportation
2
Why Install Controls? Energy Savings Asset Management
Improved Maintenance Security Liability
3
Why Install Controls? Energy Savings HPS
HPS Y axis is power, X axis is time (hours)
4
Why Install Controls? Energy Savings HPS LED
HPS LED Area between two lines is kWh
5
What is Constant Lumen Output?
This is the lamp lumen depreciation of a typical fixture. A street lighting system is typically designed to end of life. If our design is for in this case 50,000, that is 81.5% lumen output. Why waste the extra 19.5% until that 50,000 hours?
6
Why Install Controls? Energy Savings HPS LED LED w/ CLO
HPS LED LED w/ CLO Energy usage will be the inverse of the lamp lumen depreciation
7
Time of Day Controls IESNA RP-8
RP-8 is rigid because it goes by roadway classification which cannot change over time.
8
Time of Day Controls CIE 115:2010 Table 1 Parameter Options
Parameter Options Weighting Factor WF STATIC PARAMETERS Speed Very High 1 High > 35 mph design speed 0.5 Moderate <= 35 mph design speed Full-Width Median or Center Turn Lane No Yes Intersection Density High >= 2 per mile Moderate < 2 per mile Visual Guidance / Traffic Control Poor (Guidance Features: 0; Hazards: 7+) Good (Guidance features: 1; Hazards: 4 – 6) CIE uses roadway parameters rather than classification. More transportation engineering oriented.
9
Time of Day Controls CIE 115:2010 Table 1 CONDITIONAL PARAMETERS
CONDITIONAL PARAMETERS Parameter Options Weighting Factor WF Traffic Volume Very high (> vehicles/day) 1 High (60001 – vehicles/day) 0.5 Moderate (30001 – vehicles/day) Low (10001 – vehicles/day) -0.5 Very low (< vehicles/day) -1 Traffic Composition Mixed with high percentage of non-motorized (non-motorized traffic > 10%) 2 Mixed (non-motorized < 10%) Motorized only Curb Parking Allowed Present Not present Ambient Luminance High (Urban) Moderate (Urban Residential) Low (Suburban and Rural)
10
Time of Day Controls Draft Guideline
Draft Guideline Parameter Options Weighting Factor STATIC PARAMETERS Speed ≥ 35 mph 1 30 mph ≤ 25 mph Full-Width Median or Center Turn Lane Not present Present or One-Way Average Block Length < 500 feet ≥ 500 feet CONDITIONAL PARAMETERS Traffic Volume > 360 veh/lane/hr 1 120 – 360 veh/lane/hr < 120 veh/lane/hr -1 Bicycle Master Plan Distinction Sharrow or Bike Lane 2 Arterial Commonly Used for Biking None Curb Parking Allowed Present Not present Pedestrian Master Plan Priority Tier Tier 5 Tier 4 and 3 Tier 2 and 1 Limited pedestrian access to travel lanes A jurisdiction can develop their own guidelines that best fit them.
11
Time of Day Controls Typical Winter Day Energy Consumption
Typical Winter Day Energy Consumption If you use the guidelines from the previous slide this is an example of what the energy usage would look like throughout the day. This could be real-time (actuated) or pre-timed.
12
Why Install Controls? Energy Savings HPS LED LED w/ CLO
HPS LED LED w/ CLO LED w/ CLO and Time of Day Adjustment Over the life of the fixture the curve would be the same shape as the CLO but with a percentage savings every day.
13
Why Install Controls? Asset Management and Metering
All luminaires will be mapped, information about luminaire, pole, location, power usage, voltage, dim level, operating hours, etc are provided.
14
Why Install Controls? Improved Maintenance Automatic alerts
Automatic alerts Can schedule maintenance because we know burn hours. Race and Social Justice – we won’t rely on residents (some people have better access) to call in lights that aren’t working
15
Why Install Controls? Security
In one of the pilot locations we used the constant lumen output during normal times of day and times when security was a concern we increased the light level to 100%.
16
Why Install Controls? Liability
Can go to the exact time and day and know if the light was on or off, how many hours it had been running, and if dimmed or not.
17
Lessons Learned Luminaire and controller integration
Is controller integrated into fixture? Who is installing the controller? Luminaire and controller integration We found that it is imperative for the luminaire and the controller manufacturer to integrate properly with one another. There is the actual dimming of the lights that is important to consider, but it is also important to consider the physical space within the housing. For the NEEA project, the driver and the LuCo had to be removed to energize the luminaire because there was a very tight connection to the terminal block. Also, which manufacturer do you go to to redeem warranty. Installation procedure Don’t assume anything …In the NEEA project we found that there was some misunderstanding about the single voltage of the LuCos. As you know this caused nearly all of the LuCos being replaced. Additionally, the SeCo was installed after all of the LuCos were installed. Ideally, the SeCo would be installed first and pre-commissioned to receive a signal from the LuCos as they are being installed. This would help in catching early errors in the installation. Commissioning Pilots use a spreadsheet to keep track of everything with stickers. Stickers flew away in the wind, spreadsheet wasn’t always consistent. Required a lot of work before going out into the field. A field scanning device would have been better. Troubleshooting As the LuCos were being replaced by the crew in the field, there was a delay in knowing if the luminaire was working properly. I believe that Vicki mentioned that it would be helpful if the control system could communication immediately to the field installation crew by blinking lights or by some other means to let the crew know that the luminaire has been correctly integrated into the system. Communication to Server Used cellular connection to manufacturer’s server. Not always consistent but using our system would have been costly for a pilot. Future use City’s network and Traffic Management Center over fiber or 4.9 GHz or City wifi.
18
Lessons Learned Installation and commissioning procedure Be prepared!
Luminaire and controller integration We found that it is imperative for the luminaire and the controller manufacturer to integrate properly with one another. There is the actual dimming of the lights that is important to consider, but it is also important to consider the physical space within the housing. For the NEEA project, the driver and the LuCo had to be removed to energize the luminaire because there was a very tight connection to the terminal block. Also, which manufacturer do you go to to redeem warranty. Installation procedure Don’t assume anything …In the NEEA project we found that there was some misunderstanding about the single voltage of the LuCos. As you know this caused nearly all of the LuCos being replaced. Additionally, the SeCo was installed after all of the LuCos were installed. Ideally, the SeCo would be installed first and pre-commissioned to receive a signal from the LuCos as they are being installed. This would help in catching early errors in the installation. Commissioning Pilots use a spreadsheet to keep track of everything with stickers. Stickers flew away in the wind, spreadsheet wasn’t always consistent. Required a lot of work before going out into the field. A field scanning device would have been better. Troubleshooting As the LuCos were being replaced by the crew in the field, there was a delay in knowing if the luminaire was working properly. I believe that Vicki mentioned that it would be helpful if the control system could communication immediately to the field installation crew by blinking lights or by some other means to let the crew know that the luminaire has been correctly integrated into the system. Communication to Server Used cellular connection to manufacturer’s server. Not always consistent but using our system would have been costly for a pilot. Future use City’s network and Traffic Management Center over fiber or 4.9 GHz or City wifi.
19
Lessons Learned Troubleshooting Know your technology
Luminaire and controller integration We found that it is imperative for the luminaire and the controller manufacturer to integrate properly with one another. There is the actual dimming of the lights that is important to consider, but it is also important to consider the physical space within the housing. For the NEEA project, the driver and the LuCo had to be removed to energize the luminaire because there was a very tight connection to the terminal block. Also, which manufacturer do you go to to redeem warranty. Installation procedure Don’t assume anything …In the NEEA project we found that there was some misunderstanding about the single voltage of the LuCos. As you know this caused nearly all of the LuCos being replaced. Additionally, the SeCo was installed after all of the LuCos were installed. Ideally, the SeCo would be installed first and pre-commissioned to receive a signal from the LuCos as they are being installed. This would help in catching early errors in the installation. Commissioning Pilots use a spreadsheet to keep track of everything with stickers. Stickers flew away in the wind, spreadsheet wasn’t always consistent. Required a lot of work before going out into the field. A field scanning device would have been better. Troubleshooting As the LuCos were being replaced by the crew in the field, there was a delay in knowing if the luminaire was working properly. I believe that Vicki mentioned that it would be helpful if the control system could communication immediately to the field installation crew by blinking lights or by some other means to let the crew know that the luminaire has been correctly integrated into the system. Communication to Server Used cellular connection to manufacturer’s server. Not always consistent but using our system would have been costly for a pilot. Future use City’s network and Traffic Management Center over fiber or 4.9 GHz or City wifi.
20
Lessons Learned Communication to Server
Luminaire and controller integration We found that it is imperative for the luminaire and the controller manufacturer to integrate properly with one another. There is the actual dimming of the lights that is important to consider, but it is also important to consider the physical space within the housing. For the NEEA project, the driver and the LuCo had to be removed to energize the luminaire because there was a very tight connection to the terminal block. Also, which manufacturer do you go to to redeem warranty. Installation procedure Don’t assume anything …In the NEEA project we found that there was some misunderstanding about the single voltage of the LuCos. As you know this caused nearly all of the LuCos being replaced. Additionally, the SeCo was installed after all of the LuCos were installed. Ideally, the SeCo would be installed first and pre-commissioned to receive a signal from the LuCos as they are being installed. This would help in catching early errors in the installation. Commissioning Pilots use a spreadsheet to keep track of everything with stickers. Stickers flew away in the wind, spreadsheet wasn’t always consistent. Required a lot of work before going out into the field. A field scanning device would have been better. Troubleshooting As the LuCos were being replaced by the crew in the field, there was a delay in knowing if the luminaire was working properly. I believe that Vicki mentioned that it would be helpful if the control system could communication immediately to the field installation crew by blinking lights or by some other means to let the crew know that the luminaire has been correctly integrated into the system. Communication to Server Used cellular connection to manufacturer’s server. Not always consistent but using our system would have been costly for a pilot. Future use City’s network and Traffic Management Center over fiber or 4.9 GHz or City wifi.
21
QUESTIONS?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.