msslc specification for remote monitoring & adaptive lighting … · – networked and...
TRANSCRIPT
MSSLC Specification for Remote Monitoring & Adaptive Lighting Control
Systems—The Next Step in SSL
Southwest Region WorkshopAugust 25-26, 2011
Laura Stuchinsky, Sustainability Officer, City of San Jose DOTTod Rosinbum, Senior Engineer, City of PortlandMichael Poplawski, Senior Lighting Engineer, PNNL
A starting point…
Utility Installations & Field Test
RFP
CityPolicy/Design
Guide
SW Region Workshop August 25-26, 2011 1
First .. no new recurring costs
1) Wireless
2) Utilize city infrastructure
3) City hosts data
SW Region Workshop August 25-26, 2011 2
• Installation• Modify operation in
field• Graphical interface• Integrate with existing
database• More reliable than
photocell
Second … easy to use
SW Region Workshop August 25-26, 2011 3
Utility• Metering accuracy• Data format• Report own energy
consumption
City of San Jose• Minimize energy
consumption
Priorities
SW Region Workshop August 25-26, 2011 4
Taking the long view…
• Capable of serving entire City• Forward compatibility
• Creation of MSSLC Controls Task Force
SW Region Workshop August 25-26, 2011 5
Combining Street Lights with Cycle Tracks and Bio-swales:
Street Lighting Remote Monitoring and Controls:
Luminaire and control system evaluation
Cycle Track
Bio-Swale
Traffic Signal Cabinet Installation
Taking it to the next level …
SW Region Workshop August 25-26, 2011 6
Central Server and Communications Network
Utilities• Metering Accuracy• Standard Billing Interface – that
can be used among customers• Predictability versus Adaptability
– Stand alone and fixed– Networked and changeable
• Performance, Efficiency, etc. • Safety and Liability• Warranties
City of Portland• Performance – Identify outages,
eliminate day-burners, and asset management
• Efficiency – Minimize energy consumption and maintenance
• Product Longevity – Remote monitoring with fewer site visits due to longer life
• Sustainable Projects – e.g. Street lighting combined with cycle tracks and bio swales
• Evaluations – Energy consumption, light output, and temperature effects
Priorities
SW Region Workshop August 25-26, 2011 7
System architecture
SW Region Workshop August 25-26, 2011 8
Graphic user interface
SW Region Workshop August 25-26, 2011 9
Taking a lead task force role
SW Region Workshop August 25-26, 2011 10
• Share experiences with other users• Design a system to utilize the City’s
infrastructure and networks• Promote standardization with Regional
Partners
Enhancing the SJ Specification
• Submittals – Power requirements, MTBF, rated life, and support documentation
• Warranties – Catastrophic failures• Scalability – System expansion and equipment
improvements• User Access – Secure access in the field as well
as by administrator• Sampling Rates and off-line logging – every 60
minutesSW Region Workshop August 25-26, 2011 11
Enhancing the SJ Specification
• Open Protocols and Interoperability –Desirable features
• Evidence of Claims – e.g. maximum number of lights per gateway
• Data Hosting, Ownership, Management and On-going fees
• Users Guide – Advice on how to modify specs to fit local circumstances
SW Region Workshop August 25-26, 2011 12
Ongoing challenges/questions
1. Interoperability: standards and layers2. Dimming: light and power3. Power metering: measurement and storage4. Energy consumption: what and how5. Other
– Transient event (surge) immunity– Lifetime (MTTF)– Reliability (MTBF)
SW Region Workshop August 25-26, 2011 13
• No industry consensus• Existing open protocols
(e.g. NTCIP1213/ELMS) not widely adopted
• Many systems use Zigbeebetween controller and gateway– What level of compliance?– No defined application
layer for streetlights– Can proprietary application
layers be shared?• Gateway to central
management server?
Interoperability
SW Region Workshop August 25-26, 2011 14
• What does 50% dimmed mean?– control signal– power– measured light– perceived light
• Measured light– light meter reading– Illuminance
• Perceived light– visual interpretation– affected by adaptation,
eye dilation
Dimming control
SW Region Workshop August 25-26, 2011 15
Source: IESNA Lighting Handbook, 9th Edition
Dimming: light and power
• Dimming means a reduction in …– Light output (municipality)– Power (utility)
• Typically, control system only provides control signal(e.g. 0-10V, DALI)
• Dimming performance is solely dependent on interpretation of control signal by streetlight– Streetlight make/model, driver dependent– Light output and power have different response
• Control manufacturer ability to provide lower light levels, energy savings dependent on integration with streetlight make/model– Compatible streetlight, driver list?
SW Region Workshop August 25-26, 2011 16
Example: light vs. power
SW Region Workshop August 25-26, 2011 17
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Mea
sure
d Li
ght
Power
Edge 525mA
LEDway 525mA
LEDway 700mA
SW Region Workshop August 25-26, 2011 18
Example: light vs. control
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
0 1 2 3 4 5 6 7 8 9 10
Mea
sure
d Li
ght
0-10V Signal
Edge 525mA
LEDway 525mA
LEDway 700mA
What happens here?
What happens here?
SW Region Workshop August 25-26, 2011 19
Example: power vs. control
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
0 1 2 3 4 5 6 7 8 9 10
Pow
er
0-10V Signal
Edge 525mA
LEDway 525mA
LEDway 700mA
What happens here?
What happens here?
Example: normalized control
SW Region Workshop August 25-26, 2011 20
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Pow
er
Normalized 0-10V Signal
Edge 525mA
LEDway 525mA
LEDway 700mA
System evolution
How do you handle different streetlight make/models on the same control system?• What are the owner input variables?
– Control signal (only)– Light output– Power
• Can/should the control system use the streetlight power measurement as a feedback signal?
• How is lumen depreciation handled?• Does the owner have to program/edit control signal
setting for each luminaire, and manage them over time?
SW Region Workshop August 25-26, 2011 21
Two dimming proposals
1. Standardized streetlight relationships– Light output vs. control – Power vs. control– Tolerances: ± 1%, 10%?
2. Control system streetlight profiles– Look up table(s) with interpolation, and/or
feedback loop (power)– Light output and/or power level input– Translation to streetlight specific control signal
output
SW Region Workshop August 25-26, 2011 22
• Accuracy– What is required? Why?– 0.5% (revenue grade)?– 2.0% (utility grade)?
• Load range– What is required? Why? – Full load down to zero?– Off condition: mechanical
(relay) or electronic?• Temperature range?
– Higher accuracy can be specified over smaller range
– One product for all environments?
• Performance determined by metering IC design
• 2.0% achievable without calibration (in final test)– Over wide load range (3mA to
3A)– Over industrial temp range (-40
to 85C)• Less than 2.0% achievable with
calibration– Added cost for special order– Minimized cost adder if
standard requirement• “Creep threshold”
– Minimum current, under which power is reported as zero
Power metering: measurement
SW Region Workshop August 25-26, 2011 23
• Sampling period– Nominal (all streetlights): 15
minutes?– Detail look (one streetlight):
30 seconds?– Maintained (in case of system
failure): 1 hour (period) for 2 weeks (duration)
• Metrics– Nominal (all streetlights):
time, status, voltage, current, power factor, control signal
– Maintained (in case of system failure): time, active power, power factor?
• 1 sample/15 minutes x 2 weeks x 6 metrics = 8064 data points/streetlight– X 100 poles = 806,400 data
points– X 10000 poles = 80.6M data
points• Can advanced memory
saving techniques be used?– Data compression– Adaptive sampling rate (e.g.
only transmit/save new measurement data when it varies, according to some criteria, from previous measurement)
Power metering: data
SW Region Workshop August 25-26, 2011 24
• What?– Gateway AND controller
• How?– Specified .. and measured
(controller)?– Interpreting abnormalities?– Average during “Normal”
operation– Maximum/Transmit– Minimum/Sleep
• Configuration dependencies?– Pole spacing– Gateway density, number of
hops
• Pro: measure both controller and streetlight
• Con: harder to identify root cause of abnormality
• Pro: knowledge of controller and streetlight functionality, streetlight performance
• Con: no knowledge of controller performance
Energy consumption
SW Region Workshop August 25-26, 2011 25
MSSLC Specification for Remote Monitoring & Adaptive Lighting Control
Systems—The Next Step in SSL
Laura StuchinskySustainability OfficerCity of San Jose DOT
200 E. Santa Clara StreetSan Jose, CA 95113
Tod RosinbumSenior EngineerCity of Portland
1120 SW Fifth AvenuePortland, OR 97204
Michael PoplawskiSenior Lighting Engineer
PNNL
620 SW Fifth Ave Suite 810Portland, OR 97204