OUTDOOR LIGHTING CONTROL

SYSTEM FUNDAMENTALS
9:00am Sunday 5/3/2015
Mark Wilbur, GE Lighting Solutions
Michael Poplawski, Pacific Northwest National Laboratory
ATTENDEE SURVEY: BACKGROUND 3

 Manufacturer
 Municipal user
 Utility user
 Contractor, Consultant
 Market Analyst
 Investment, Finance
 Other
ATTENDEE SURVEY: BACKGROUND 4

Manufacturer experience User experience

 Lighting control system  Installed system

 Lighting control sub-system  Pilot project
 Lighting control component  Demonstration project
 Luminaire  Mock-up
 Other  Technical review
 None
ATTENDEE SURVEY: EXPECTATIONS 5

 General education
 Features and options of commercially available
products
 Value propositions
 Barriers to adoption
 Planning a project
 Specific questions
 Market analysis
WHO IS THIS COURSE DESIGNED FOR? 6

• Specifiers, owners, and operators of outdoor lighting systems

• System integrators, start-up and commissioning agents
• Manufacturers of non-lighting equipment that could get
integrated into networked outdoor lighting systems
A (NETWORKED) OUTDOOR LIGHTING CONTROL SYSTEM 7
NETWORKED CONTROL SYSTEMS 8

• Network (from IES TM-23-11): A group of systems that function

cooperatively and/or interdependently to provide a chain of
command for lighting control
• Field Device Network: typically a Local Area Network (LAN)
that connects and enables communication between
(exclusively) Field Devices
• Backhaul Network: typically a Wide Area Network (WAN) that
connects and facilitates communication between (at a
minimum) one or more Field Device networks with a Central
Management System.
NETWORKED CONTROL SYSTEMS 9

• Field devices: the entire set of networked Components

(hardware and embedded software, consisting of Controllers
and possibly Gateways) installed in the field that, following,
installation, start-up and commissioning, function together to
adaptively control and remotely monitor Luminaires.
• Central Management System: a computer environment that
functions as the core of the System by providing all shared
System services, and consolidating and storing (or managing
the storage of) all System data
SYSTEM CONFIGURATION 10

Installation Start-up Commissioning

Devices have basic necessities Devices are operating as System functions and
for operating as intended intended, all system functions capabilities are configured
and capabilities are available according to user desires
to the user

Physical configurations Logical configurations Functional configurations

Mechanical mounting Evaluation of and Grouping, associations
Electrical connection configuration for Monitoring, reporting
environmental conditions (i.e.
Default values compatibility) Control strategies
Provisioning Configuration for and Schedules
verification of data exchanges
(i.e. interoperability)
LEARNING OBJECTIVES 11

1. Understand the full capabilities and underlying technology

building blocks of market‐available outdoor lighting control
systems.
2. Understand the value propositions offered by outdoor lighting
control systems, current real‐ world barriers to adoption, and
the status of relevant research, standards and regulations.
3. Understand how to align value propositions with the needs of
relevant stakeholder groups, create strategies for overcoming
barriers to adoption, and draft specifications that meet user
needs.
4. Understand how outdoor lighting control systems can form
the backbone of future Machine‐To‐ Machine and Internet of
Things ecosystems that make tomorrow’s urban
environments safer and more livable.
AGENDA 12

1) Introduction, Assessment & Adoption

2) Technology Fundamentals
3) Basic System Capabilities & Value Propositions
4) Demonstration Part 1
5) Lunch (90 minutes)
6) Demonstration Part 2
7) Market Adoption Status
8) Future Possibilities
9) Interoperability, Standards & Specifications
10) Q&A
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Assessment and adoption
Michael Poplawski
 Cities account
for…
70% of energy
consumption

Lighting 20% of electricity

consumption

14
OUTDOOR LIGHTING APPLICATIONS 15

Roadway Urban Streets

Residential Site & Area

LED ADOPTION 16

• Driven by economic circumstances

– Reduced municipal revenues
– Higher energy costs
– Increasing energy efficiency regulations
• Driven by falling prices and shortened payback
• Driven by successful retrofit pilot projects
• Clear transition path from traditional lighting to LED technology
LED RETROFIT PILOTS 17

Los Angeles Before and After LED retrofit

• LED luminaires have proven energy efficiency and reliability
while providing high-quality lighting
• LA (142K), Seattle (42K), Boston (32K), Las Vegas (40K), NYC
(250K)
LED LIGHTING MARKET IS GROWING FAST 18

6% 45% 70% LED market share in outdoor

http://www.mckinsey.com/~/media/mckinsey/dotcom/client_service/automotive and
assembly/lighting_the_way_perspectives_on_global_lighting_market_2012.ashx
STRONG GROWTH EXPECTED FOR LIGHTING CONTROLS 19

http://www.mckinsey.com/~/media/mckinsey/dotcom/client_service/automotive and
assembly/lighting_the_way_perspectives_on_global_lighting_market_2012.ashx
NEW TECHNOLOGY ADOPTION 20
HOW SHOULD ONE GO ABOUT
CONSIDERING AND PLANNING FOR THE
ADOPTION OF AN OUTDOOR LIGHTING
CONTROL SYSTEM?
A RECOMMENDED END-TO-END ADOPTION PROCESS 22

Solution
Infrastructure Requirements Operation and
Design & Deployment
Assessment Specification Management
Selection

• Needs & goals • Priorities • Technology/sol • Installation • Measurement

• Data acquisition • Requirements ution • Start-Up and verification
• Scoping & • Evaluation • Performance • Commissioning • Operational
ideation criteria modeling • System optimization
• Audit • Business and • Scenario integration • Maintenance
partnership analysis services
models
INFRASTRUCTURE ASSESSMENT 25

Identify assets Verify/Visualize Evaluate

IDENTIFY ASSETS 26

• Review existing information

– Typical data formats: Excel, GIS files
• Asset Verification
– Validate existing assets (visualization can help)
LIGHTING ASSET DATA ACQUISITION 27

• Depending on the quality and/or ownership of the data, a new

asset data collection step may be required
• Asset data collection methods
– Field data collection of pole location (GPS) and asset
information
– Done prior-installation (e.g. using mobile tools) or enabled
by control system (post installation)
ASSET DATA 28

Typical data points per pole location:

• ID: Unique identifier
• Location (Latitude, Longitude)
• Lamp Type: HPS, LED, Metal Halide, Mercury Vapor, …
• Lamp Wattage: 100 W, 75 W, 50 W, …
• Volts: 120-277V
• Style: cobra head, decorative, architectural, …
• Additional information (e.g. pole condition, photocell, arm
length)
LIGHTING ENERGY AND COST EVALUATION 29

• Energy & Sustainability Impact

– KWh/year consumed
– CO2 impact: Emission factor
• 6.89551 × 10-4 metric tons CO2 / kWh
• Operational Costs
– Energy cost
• Estimates: Operating hours x power x energy price
– Maintenance costs
• Re-lamping: components + labor
LIGHTING QUALITY EVALUATION 30

• Lighting measurements
– Typically at sample locations
• Refer to standard practices
– IES RP-8-XX
REQUIREMENTS SPECIFICATION 31

Goals and Evaluation/

Requirements
priorities Business models
GOALS AND PRIORITIES 32

• Identify stakeholders and document main goals and priorities

– Energy savings, sustainability
– Maintenance savings
– Lead technology deployment
– Others???
• Understand the value of technology
– LED and controls
DIFFERENT VIEWS AND INTERACTIONS 33

• Mayor
• Finance
• Building owner
• City maintenance team
• Public works department
• Site manager
• Electrician
• IT
DIFFERENT NEEDS AND BENEFITS 34

• Energy savings
• Cost savings ($)
• Control
• Monitoring
• Maintenance optimization
• CO2 carbon reduction
• Light pollution reduction
• Safety
DOCUMENT REQUIREMENTS 35

• Use cases and application requirements

• Example:
– Users want to define the time intervals and levels to be
applied.
– The system shall support dimming and it shall be possible
to specify a target dimming level and times for the dimming
actions.
• Important to set mandatory and optional features
• Supporting resources
– DOE Model Specification
EVALUATION METRICS 36

• ROI (Return On Investment): measures the rate of return on

money invested
– Considers economic factors only and focuses mainly on
initial costs
• Shift to new metrics that take into account other factors and
long term view
– TCO (Total Cost of Ownership)
– TVO (Total Value of Ownership)
BUSINESS MODELS 37

Model What Advantage Disadvantage

Supplier-to- Municipality purchases the Complete transparency of costs Municipality responsible for the
customer products/services directly from involved capital investment
direct manufacturers/ suppliers.
Direct line of communication with Municipality takes on project risk
system experts

Public energy Utilities team up with municipalities. All parties strongly incentivized to Applicability depends on ownership
service deal achieve energy savings models (areas under local vs.
Often the utility sub-contracts the
(PES) federal/state control)
lighting (installation and maintenance) Municipalities deal with one company
to servicing companies. and utilities can create economies of
scale

Energy Municipality outsources lighting No capital investment required from Long contract period required to pay
performance project completely in exchange for municipalities: ESCO provides off the capital investment
contract (EPC) guaranteed energy savings. financing and takes on the risk
Mostly deployed between private
Most commonly a partnership with an Guaranteed energy savings and parties
energy servicing company (ESCO). maintenance

Public-private Similar to an EPC, but municipalities Municipality maintains equity share in Municipalities also take on some of
partnership retain a stake in the project. the project the risk
(PPP)
Municipalities partner with a major Performance and energy/maintenance Most often used for projects broader
PPP, or tender for large PPP projects savings guaranteed by private than just outdoor lighting
that comprise a significant lighting partners
element (such as city street lighting)

Source: The LED Future – outdoor Lighting for sustainable and

livable cities, White paper
SOLUTION DESIGN & SELECTION 38

Technology/
Performance Scenario
System modeling Analysis
Capabilities
DEFINE SYSTEM CAPABILITIES 39

• Map use cases and application requirements to technical

requirements and system capabilities
– Example: adaptive lighting requires a system that supports
dimming.
• Understand options/capabilities available and value
propositions
PERFORMANCE ANALYSIS 40

• Technical
– Energy consumption and expected savings compared to
baseline
– System reliability (up time)
– Response time
• Economic/financial
– Evaluate ROI, TCO/TVO metrics
• Regulatory and Standards
– System meet minimal lighting requirements (e.g. as defined
in IES RP-8-XX)
– Interoperability standards
NEW SERVICES 41

• Financial Services
– private vs. public financing
• Maintenance Services
– performance contracts
– Lighting as a Service
• Technical Solutions Services
– System operation and optimization services (e.g. network
management, troubleshooting, re-commissioning)
DEPLOYMENT 42

• Project management
• Installation, start-up, and commissioning
• System integration
OPERATION & MANAGEMENT 43

• Monitoring
– Measurements
– Performance verification
• Maintenance
• System optimization (re-commissioning)
Q&A

Assessment and adoption

Michael Poplawski
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Technology Fundamentals
Mark Wilbur
OUTDOOR LIGHTING FIELD DEVICES 46

• Basic
– Photocontrols, photoelectric cells, photocells, Astronomical
clocks
– On/off only
• Advanced (but non-networked)
– On/off and dimming
• Networked
– One-way or two-way communication
– Remote control
– Remote monitoring
PHOTOCELLS 47

• On at dusk and off at dawn

• Dominant deployed outdoor lighting control
ASTRONOMICAL CLOCKS 48

• Devices that determine (typically from a database) the

expected time of sunrise and sunset for a given calendar date
(i.e. day, month, year) and geographical location
• On/off based on expected sunset and sunrise times, without
the use of a photocell
• Typically allows programming of offsets around sunset and
sunrise times and shifts due to daylight saving time
• Do not compensate for cloudy days, or other variables that
affect light levels around sunrise and sunset
ADVANCED NON-NETWORKED CONTROLS 49

• Sunrise/sunset trimming (or offset)

– Modified on/off times
– Shorter on duration
• Part-night dimming
– Typically pre-determined, scheduled time, configured at or
prior to installation
– Typically pre-determined, fixed dimmed light level,
configured at or prior to installation
PART-NIGHT DIMMING EXAMPLE 50

Example: 50% savings

Energy savings depends on chosen

dimming periods and levels
NETWORKED FIELD DEVICES 51

Networked devices (hardware

and embedded software,
consisting of Controllers and
possibly Gateways) installed in
the field that, following
purchase, installation, start-up
and commissioning, function
together to adaptively control
and remotely monitor
Luminaires.
FIELD DEVICES 52

Controller - the device that originates a command to execute a lighting change.

Most commonly associated with a lighting control station or control console, a
controller may also be a sensor or other automatic device operating without human
interaction.
– Physically monitors and controls Luminaires installed at Control Points
– Reacts and responds to logical and physical inputs
– Makes control decisions using internal algorithmic and logic functions
– Communicates via a network protocol
Gateway - a device designed for interfacing between two communication networks
that use different protocols, such as BACnet to DALI, or DMX512 to 0-10VDC. A
Gateway may contain devices such as protocol translators, impedance matching
devices, rate converters, fault isolators, or signal translators as necessary to
provide system interoperability.
– Serves (at a minimum) as the interface between one or more Field
Devices and a Central Management System
– Typically translating from a wireless Field Device protocol to a
standardized Wide Area Network (WAN) protocol, such as WiFi (i.e. IEEE
802.11xx), Ethernet (i.e. IEEE 802.3), or LTE Cellular (i.e. 3GPP
Releases)
NETWORKED FIELD DEVICES 53
CONNECTIVITY 54

• Technologies
– Wireless
– Wired (Power Line Carrier)
• Network Topology
– Star Lighting
Cabinet
Power Line Carrier
– Mesh

Gateway

Gateway

Wireless Mesh Wireless

Star
WIRELESS CONNECTIVITY PROTOCOLS 56

• Application + (Mesh) network layers

– Typically proprietary implementations

Lighting Control Lighting Control

Application Application + Application
Transport/Network Networking Layers Transport/Network
(Mesh) (Mesh)
802.15.4 802.15.4
(radio) (radio)

• Radio (Physical + MAC) Layers

• Typical standard implementations
– IEEE 802.15.4 (used in ZigBee), IEEE 802.11 (WiFi)
– Some modified, proprietary versions
EXISTING AND EMERGING 57
WIRELESS STANDARDS

IEEE 802.15.4 IEEE 802.11 Cellular (3G)

family family
Data rates 20, 40, 100, 250 Kbps Depends on standard version: 2, DL: 2-28 Mbps
5, 11, 54, 72, 150, and up Mbps UL: 384 Kbps -11Mbps
…

Spectrum 868-870 MHz (EU) 2.45 GHz Various

902-928 MHz (US) 5 GHz
2.4 GHz (Worldwide)

Range/ 100 m – 1.5 Km 10 – 250 m Growing coverage (depends

Depends on frequency band on deployment)
Coverage
Primary Applications Building/home automation, Wireless broadband/Internet Mobile broadband, M2M
sensor/actuator networks, access applications in the future
healthcare, games, etc
(usually low data rates and
low power devices)

Standard 15.4 (most used in existing 802.11a/b/g/n and others… Evolving (3G, LTE, LTE
products) New sub-GHz spec under advanced, …)
Development 15.4g new extension for development (11ah), expected
smart utility networks (high 2015
data rates and range for
outdoor applications)
MESSAGE (PACKET) ROUTING 62

Border Router (Gateway):

aggregates packets and connects
to external networks i.e. internet

Router (Controller): generates and

forwards (repeats) adjacent node’s
packets

Leaf (Controller):
transmits/receives messages
MESSAGE (PACKET) FORWARDING MODELS 63
MESH NETWORK FORMATION 64
WIRELESS MESH CONNECTIVITY 65

CMS

WAN
(IP Network)

• Mesh networks use packet forwarding to increase range and

robustness
• Performance factors to consider in the network deployment
– communication range of nodes
– interference robustness
– scalability
– security
BACKHAUL COMMUNICATION NETWORKS 67

Cellular
Network
Internet (GPRS, 3G, 4G)
Access
Point

Central Management
System
Field Devices

Operator
BACKHAUL COMMUNICATION OPTIONS 68

• Cellular
– GRPS, 3G, LTE/4G
– Wide availability and coverage
– Must consider propagation conditions at gateway locations
to avoid coverage holes
• Wired (Fiber)
– IEEE 802.3 (Ethernet)
– Limited availability and (pole) coverage in outdoor
environments
– Fastest and most reliable
NETWORK SECURITY 69

Secure deployment • To prevent the connection of malicious

and commissioning devices to the system

• To prevent eavesdropping on the

Encryption of data communications in the system

• To prevent unauthorized people or

Authentication devices from controlling or disrupting
the system

• To prevent hackers from uploading non-

Secure software
functional or malicious software to the
updates system
CENTRAL MANAGEMENT SYSTEMS 70

Computer environments that function as the core of a System by

providing all shared System services, and consolidating and
storing (or managing the storage of) all System data
CLOUD-BASED HOSTING 71

Internet

(Hosted by Vendor)
User remote access

• Complexity (application management, software upgrades, security

management) handled by Vendor
• Access through encrypted user sessions (https) – technology similar to
online banking
• Reliable infrastructure with multitenant software and automated backups
• Cost effective (leverage the cloud scale)
• Typically involves a service fee (per-light-point-per-year fee)
USER SITE BASED HOSTING 72

1 2

(Hosted by User) User remote access Standalone desktop

application

• End user and vendor coordinates application management and

software upgrades
• All data stays within the user’s premises
• End user responsible for data backup and security management
• Typically, one time software cost + support services
(helpdesk/upgrades)
CENTRAL MANAGEMENT SYSTEM CORE CAPABILITIES 73

• Graphic User Interface (GUI)

• Commissioning
– Control strategies
– Fault thresholds
• Asset management
• Reporting
– Remote monitoring
– Energy consumption
– Fault detection, tracking, alarm generation
• Diagnostics and manual control
Q&A

Technology Fundamentals
Mark Wilbur
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Basic System Capabilities & Value Propositions
Michael Poplawski
 BASIC SYSTEM CAPABILITIES 78

High performance sources Connected

Wireless, scalability, security

Remote monitoring & control

metering, status, energy reports

Adaptive
schedules, presence, weather, traffic Sensing
cars, pedestrians, bicycles,
environment…
LOCAL START-UP 79

• Upload light plan (if available)

• Scan barcodes
• Collect GPS coordinates (with handheld GPS)
• Send handheld data file to PC or directly to CMS
• Configure devices from CMS

GPRS/3G
REMOTE START-UP 80

• Plug in twist-lock module

• Watch Indicator lights
• Input Fixture information (Lamp, Driver, etc.) -
Proceed to next Fixture
• Behind the scenes
– GPS Coordinates acquisition & storage
– Sync clock with GPS time
– Auto Join mesh network & register
– Sync schedule and settings info from CMS
– Run initial diagnostics
– Register collected information with CMS
– Blink indicator lights for success/fail code
ASSET TYPES 81

• Street light
– Pole
– Controller
– Luminaire
• Cabinets
– Gateway
– Traffic management
equipment
ASSET MANAGEMENT 82
ASSET LOCATION 83
COORDINATED ASSETS 84

Pole

Controller
Luminaire
POLE ASSET FIELDS 85
CONTROLLER ASSET FIELDS 86
LUMINAIRE ASSET FIELDS 87
IMPORTING LEGACY OR EXISTING ASSET DATA 88

Operator

AMS Lighting CMS

Login Login

Data Exchange
Data
3rd Party Connector
(via standard Web Street Lighting
Asset Services) Management System
Management System
USER MANAGEMENT 89

• Configure user roles and access rights

• Use roles
• Administrator (full access)
• User (standard/normal operational access)
• Report (view only access)
DEVICE CONFIGURATION 90
OVER-THE-AIR FIRMWARE UPDATES 91
GROUPING 92
TIME AND CALENDAR SCHEDULING 94
ENERGY CONSUMPTION 96
ELECTRICAL PARAMETERS 97
CONFIGURING FAULTS AND NOTIFICATIONS 98
ADAPTIVE CONTROL STRATEGIES 99

• Time based
– Scheduled by time (and possibly calendar date)
– Fixed, finite number of switching times and light levels
• Event based
– Triggered by data from one or more sources
• Sensors, networked data sources
• Traffic, ambient light, motion, environmental conditions)
– Dynamically varying switching times and light levels in
response to event triggers
TIME AND EVENT-BASED CONTROL 100
(E.G. TRAFFIC SENSOR)

Traffic increase Traffic decrease

100%
90%
80%

70%
60%

50%
Photocell Photocell
40% “off” “on”
30%

20%
10%

0%
09:00

16:00
06:00
07:00
08:00

10:00
11:00
12:00
13:00
14:00
15:00

17:00
18:00
19:00
20:00
21:00
22:00
23:00
24:00
00:00
01:00

03:00
04:00
05:00
02:00
TIME AND EVENT-BASED CONTROL 101
(E.G. MOTION SENSOR)

100% 100%

20% 20% 20%

off off
FAULT REPORTING 103
SYSTEM STATUS 105
DIAGNOSTICS 107
MANUAL CONTROL 108

Luminaire or group selection

Overriding automatic control

Q&A

Basic System Capabilities & Value Propositions

Michael Poplawski
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Demonstration Part 1
Mark Wilbur
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Lunch (90 minutes)
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Demonstration Part 2
Mark Wilbur
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Market Adoption Status
Michael Poplawski
KEY MARKET ADOPTION ISSUES 115

• Market and user maturity

• Upfront cost and/or payback time
• Quantifiable value propositions
• Game changers
– Managing modularity vs. integration
– Interoperability
– Future city visions, interdepartmental or municipal-utility
collaboration models, business models
– New value propositions, revenue opportunities
USER AND MARKET MATURITY 116

• Utilities and municipalities • Young market

and have different vested – Mature core technology
interests – Start-up and
• Different commissioning
utilities/municipalities see processes viewed as
value propositions differently complex and time-
• Size matters consuming
• User learning curve – Rapid product evolution
– Networks, • One size does not fit all
communication – Match desirable feature
– New/additional devices set(s) to user type(s)
to maintain – MSSLC Model
Specification
UPFRONT COST AND PAYBACK TIME 117

• Controls cost on par with LED luminaire

• Focus on simple value propositions may not lead to acceptable
payback
– Maintenance and energy cost savings from remote
monitoring are straightforward, but vary by user
– Energy savings from adaptive lighting are difficult to
monetize due to lack of metered tariffs and regulatory
guidance
MONETIZING ENERGY SAVINGS 118

• Requires new utility tariff(s)

• Existing utility infrastructure does not support accepting
metering data
• Existing metering standards not (directly) applicable
– ANSI C12.1, 12.20
– Meter accuracy
– Data security for billing purposes
• New ANSI C136.50 “revenue grade energy measurement
device” standard (specific for lighting) under development
ALTERNATIVES TO ENERGY METERING 119

Adaptive lighting tariff 1 Average or bin-center reduction

100%
Average or bin-
75%
center duration
50%
25%
0%

2:00 AM

4:00 AM

6:00 AM

8:00 AM
12:00 AM

10:00 AM
12:00 PM

8:00 PM

10:00 PM
2:00 PM

4:00 PM

6:00 PM

Adaptive lighting tariff 2 Average or bin-center reduction

100%
75%
50%
Average or bin-
25% center duration
0%
2:00 AM

4:00 AM

6:00 AM

8:00 AM
12:00 PM

8:00 PM

10:00 PM

12:00 AM

10:00 AM
2:00 PM

4:00 PM

6:00 PM
MUNICIPALITIES VS. UTILITIES 120

• New fixed tariff vs. metered tariff

• Responsibility, liability
– Meter ownership, accuracy requirements
– Network infrastructure ownership
– Data security
• Future opportunities
– Integration with other systems
– Revenue stream
ADAPTIVE LIGHTING IMPLEMENTATION STRUGGLES 121

• Adjust light levels according to what? How? Based on what

data?
– Pedestrian traffic
– Automobile traffic
– Mass transit schedules
– Lighting zones, condition
– Weather
• Liability concerns
• IES RP-8-14
– Some adaptable recommended light levels
– Limited specific guidance
MODULARITY 122

• Easy incorporation of new or exchange of existing component,

typically facilitated by plug/receptacle or some other connector
• May better facilitate gradual adoption of new/upgraded
component
• Separation of components with different expected
lifetime/reliability may lead to lower life-cycle cost
• Typically leads to higher up-front (material) cost
• Modularity + standardization (leading to high volume) may limit
increase in up-front cost
INTEGRATION 123

• Co-design of single system previously comprised of two or

more sub-systems, typically resulting in fewer components,
circuit boards, connectors, manufacturing steps
• Typically leads to lower up-front (material) cost, and higher
reliability
• Need to get the feature set right
– Compromised ability to incorporate new or exchange
existing component later
– Typically driven by clear feature demand, standards
TERMINOLOGY 124

• Compatibility: The capability of two or more devices,

applications, networks, or systems to coexist in the same
physical environment – that is, operate without corrupting,
interfering with, or hindering the operation of the other entity.
• Interoperability: The capability of two or more devices,
applications, networks, or systems to reliably and securely
exchange and readily use data with a commonly shared
meaning.
• Interchangeability: The capability of two or more devices,
applications, networks, or systems to be physically exchanged
for each other and provide a defined level of identical operation
without additional configuration.
THE IMPACT OF GREATER INTEROPERABILITY 125

• Facilitates the incorporation of best-of-breed devices,

deployment of an energy-saving platform (i.e. multi-phase, not
limited to initial install choices)
• Reduces incremental cost of system enhancement (e.g.
software vs. hardware)
• Facilitates crowd-sourced development (software, use cases)
• Reduces user risk (e.g. device, manufacturer obsolescence),
increase user satisfaction and adoption
• Facilitates greater data exchange
– Use data from, share data with non-lighting systems
– Improved performance of lighting and non-lighting systems
– Non-energy benefits
– Communicate measured performance (hours-of-use,
energy)
INTEROPERABILITY QUESTIONS 126

• Where?
– Physical/MAC layers?
– Network stack?
– Application layer?
• When?
– Market adoption bottleneck
– Mature feature definition, technology
• How?
– Requires understanding of industry standards and
specifications
– Careful, comprehensive specification, certification and
compliance testing
CITY VISIONS 127

http://ca-sanjose.civicplus.com/DocumentCenter/Home/View/242
http://www.nyc.gov/html/dot/downloads/pdf/2013-dot-sustainable-streets.pdf
COLLABORATIVE EFFORTS 128

http://www.cleantechsandiego.org/streetlight-working-group.html
SERVICE-BASED BUSINESS MODELS 129

• Many implementations http://www.wmata.com/about_metro/news/PressReleaseDetail.cfm?ReleaseID=5613

http://greatergreaterwashington.org/post/21636/wmata-gets-turned-on-to-public-private-partnerships/
– Energy service contract
(ESCO)
– Lease-to-own
– Pay for performance
• Many financing benefits
– Capital vs. Operating
cost flexibility,
optimization
– Reduced risk
• Many owner and operator
benefits
– Reduced or eliminated
system management, re-
commissioning
– Improved system
optimization,
performance
LEGISLATED MANDATES AND 130
FUNDING SUPPORT?

http://www.its.dot.gov/
http://www.fhwa.dot.gov/everydaycounts/technology/adsc/intro.cfm
http://www.fhwa.dot.gov/federalaid/projects.pdf#its
 Q&A

Market Adoption Status

Michael Poplawski

131
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Future Possibilities
Mark Wilbur
133
FUTURE OPPORTUNITIES 134

FOR THE LIGHTING INFRASTRUCTURE

• Mini-Cell Tower Deployments: ATT / Verizon Leases

• Parking Availability: Parking Location Provider Fees
• Parking Metering: Parking Fines
• Interactive LCD Billboards: Retail Advertising Fees
• Weather Reporting: Weather Service Fees
• Air Quality Reporting: Industrial Offender Fines
• Illegal Dumping Detection: Dumping Fines
 MICRO CELL TOWERS 135

Small Cells
are low-powered radio access
nodes that operate in licensed
and unlicensed spectrum that
have a range of 10 meters to 1
or 2 kilometers.
ARCchart estimates that by
2017 a total of 5 million small
cells will ship annually
 AUTOMATED PARKING SPACES 136

Smart phone application

developers charge a small
fee to guide users to the
nearest available parking
space

The same communications network can interact with the local

parking meters to notify the parking enforcement team of
violations
INTERACTIVE 137

RETAIL / INFORMATIONAL DISPLAYS

• Interactive Directions
• Local Retailer Advertisements
• Tourist Information
• Interactive Sightseeing Challenges
WEATHER MONITORING 138

• Temperature
• Barometric Pressure
• Wind Speed and Directions
• Humidity
• Rain Fall
• Snow Accumulations
• Roadway Surface Temperatures
OCCUPANCY DETECTION 139

3 Primary sensor technologies used in motion/occupancy detectors

Passive Infrared
Radiation IR wavelength detection ideal indoors away from direct sunlight lowest cost and complexity
Doppler
Audio Frequency Shift Ideal for outdoor applications Many manufactures offer hybrid PIR/Doppler sensors
Microwave
RF pulse reflection strength delay Ideal for applications that report velocity and direct detection

Lighting Network Uses:

• Adaptive lighting during of peak activity

• Security Lighting
• Energy Conservation
MAGNETOMETERS 140

The outstanding performance of in-roadway sensors such as

inductive loops, magnetic detectors, and magnetometers is due
partly to their close proximity to the vehicles passing over them.
Another advantage is that they are insensitive to inclement
weather such as rain, fog, and snow.

Lighting Networks Uses:

Vehicle Detection
Vehicle Velocity
Vehicle Direction
Parking Availability
VIDEO CAMERAS 141

Video cameras are the fastest growing sensor technology with an

estimated 10,000 new cameras being deployed every day

Lighting Networks Uses:

Pole Mounted Imaging opportunities including…

Pedestrian Congestion
Vehicle Congestion
Parking Availability
Parking Violations
Illegal Dumping Detection
Vandalism Detection

Real progress being made with distributed pattern

matching VS real time video transmission and
external image evaluations
DRONES ARE ON THEIR WAY TO A COMMUNITY 142

NEAR YOU

Light fixtures are the ideal charging and staging locations

Life saving opportunities include:

Police: Saving lives by providing advance

video surveillance of active crime scenes
Fire: Saving lives by advanced surveillance
of active fires and rescues, optimization of
asset deployments to minimize risks
Home Land Security: Video Surveillance of
reported national security treats
Emergency Medical: Delivery of portable
defibrillators and other self administered
aid prior to the arrival of EMS personnel
DATA COLLECTION GROWTH CONTINUES TO 143

EXCEED ALL PREDICTIONS

THE MACHINES HAVE TAKEN OVER 144

MACHINES HAVE SILENTLY TAKEN OVER THE

INTERNET GENERATING MORE TRAFFIC THAN ALL
OF THE PEOPLE ON THE PLANET COMBINED
DATA ANALYTICS 145

APPLICATIONS USE AVAILABLE SENSOR DATA TO

PROVIDE REAL WORLD ACTIONABLE DATA YOU
AND YOUR CUSTOMERS CAN USE

• Where has increased lighting levels reduced crime ?

• Where has additional lighting levels increased retail sales ?
• Where has increased lighting levels increased property values ?
• Where has roadway temperature reporting reduced salt usage and slow plow cost ?
• Where has reducing time looking for a parking space increase retail sales ?
Q&A

Future Possibilities,
Mark Wilbur
OUTDOOR LIGHTING CONTROL
SYSTEM FUNDAMENTALS
Interoperability, Standards & Specifications
Michael Poplawski
THERE ARE MANY POSSIBLE LEVELS OF 151
INTEROPERABILITY

Application
7 Data Network Process to
Application

Presentation
6 Data Data Representation and
Encryption
Application

Session
5 Data Interhost Communication

Transport
4 Segments End-to-End Connections and
Reliability
Transport &
Network Network
3 Packets Path Determination and IP
(Logical Addressing)

Data Link
2 Frames MAC and LLC
(Physical addressing)
Physical &
Physical Data Link
1 Bits Media, Signal, and
Binary Transmission

http://en.wikipedia.org/wiki/OSI_model
THERE ARE MANY POSSIBLE LEVELS OF 152
INTEROPERABILITY

OSI Model “Internet” Model

Application DHCP
7 Data Network Process to
Application FTP
Presentation HTTP
Application
6 Data Data Representation and
Encryption
SMTP
SNMP
SSH
Session
5 Data Interhost Communication

Transport Transport TCP

4 Segments End-to-End Connections and
Reliability
UDP

Network Internet IPv4

3 Packets Path Determination and IP
(Logical Addressing)
IPv6
DSL
Data Link DOCSIS
2 Frames MAC and LLC
(Physical addressing)
Link Ethernet
Physical ISDN
1 Bits Media, Signal, and
Binary Transmission
PPP
THERE ARE MANY POSSIBLE LEVELS OF 153
INTEROPERABILITY

OSI Model “Human” Model

Application
Application Specific • Jargon
7 Data Network Process to
Application • Lingo
• Colloquialisms
Presentation
6 Data Data Representation and
Encryption Language
• English, French
Session • Dialect
5 Data Interhost Communication

Transport
Transport • Horse, Vehicle, Airplane
4 Segments End-to-End Connections and
Reliability
• Wired
• Wireless
Network
3 Packets Path Determination and IP
(Logical Addressing)
Format • Face-to-face
• Letter, Email
Data Link • Telephone
2 Frames MAC and LLC
(Physical addressing)
Physical
Physical • Verbal
1 Bits Media, Signal, and
Binary Transmission
• Written
THERE ARE MANY POSSIBLE LEVELS OF 154
INTEROPERABILITY

ISDN Ethernet
Cable Ethernet
DSL
Ethernet

Mouse
Mouse
Generic
Driver
Driver
MouseA USB
Driver
Printer
Driver USB

Mouse
Mouse
Driver
Mouse
Driver B USB
Driver B
ANSI C136.10-2010 155

“Locking-Type Photocontrol Devices and Mating Receptacles—

Physical and Electrical Interchangeability and Testing”
ANSI C136.41-2013 156

“Dimming Control Between an External Locking Type Photocontrol and

Ballast or Driver”

https://www.nema.org/Standards/Pages/For-Roadway-and-Area-Lighting-Equipment-
Dimming-Control-Between-an-External-Locking-Type-Photocontrol-and-Ballast-or-
Driver.aspx
ANSI C136.41-2013 COMPLIANT COMPONENTS 157
ANSI C136.41-2013 COMPLIANT PRODUCTS 158
“CONTROL-READY” LUMINAIRES 159

• What?
– Dimmable LED driver
– Low additional up-front material cost
– Low future upgrade labor cost
• Why?
– Growing adoption of controllable (e.g. LED) luminaires
– Minimize cost to add control later
• How?
– Exterior plug/receptacle
– Power-door replacement
– LED driver replacement
– Interior plug/receptacle
– Firmware upgrade
ANSI C136 STANDARDS IN DEVELOPMENT 160

• ANSI C136.48 – “Remote Monitoring and Control for Roadway

and Area Lighting Equipment”
– Defines the minimal requirements for remote control and
monitoring systems used for roadway and area lighting
• ANSI C136.50 – “Revenue Grade Energy Measurement”
– Defines the minimal requirements for energy metering
devices in a roadway and area lighting control system
LONMARK INTERNATIONAL 161

• Industry consortium
– Many applications
– 15 street lighting members
• Based on the ISO/IEC 14908 series of standards for networked
control
• Full interoperability (including application layer), primarily for
wired physical implementations
• Design specification(s) + compliance testing and certification

http://www.lonmark.org/connection/solutions/lighting/streetlighting
THE TALQ CONSORTIUM 162

• Industry consortium
– 13 regular members
– 15 associate members
• Defines a standardized interface (including application layers)
between central management systems and outdoor lighting
networks
• Does not specify Physical or Data Link layers
• Design specification(s) + compliance testing and certification

http://www.talq-consortium.org/
WI-SUN ALLIANCE 163

• Industry Consortium
– 9 Promoter Members
– 49 Contributor Members
– 5 Observer Members
• IEEE 802.15.4g Physical and Data Link
• IPv6, 6loWPAN Network and Transport protocols
• Does not specify Application layer
• Design specification(s) + compliance testing and certification

http://www.wi-sun.org
WI-SUN ALLIANCE 164

• Primarily focused on Physical & Data Link Layers, with

Network layers as required
• Does not specify Application layer

http://www.wi-sun.org
ZIGBEE NEIGHBORHOOD AREA NETWORK 167

• Industry consortium
– Many applications
– NAN members currently not specified
• Intended to be the last-mile, outdoor access network that
connects smart meters and distribution automation devices to
Wide Area Network (WAN) gateways
• IEEE 802.15.4g Physical and Data Link
• IETF Network and Transport protocols, including IPv6, RPL,
UDP and TCP
• Does not specify Application layer
• Design specification(s) + compliance testing and certification

http://www.zigbee.org/what-is-zigbee/utility-industry/
LIGHTING STANDARDS AND RECOMMENDED PRACTICES 170

• Have focused on
illumination requirements to
meet visual task
requirements and ensure
safety
• Based on legacy
technology; largely do not
take into account newer
technologies, connected
lighting, and adaptive
strategies
• Need to evolve in sync with
LED source and networked
lighting control adoption
IES RP-8-14 – ROADWAY LIGHTING 171

• Includes adaptive lighting

recommendations
• Light levels based on road
classification
• Suggests that road
classification may be
adapted based on actual
traffic conditions
• Refers to emerging
international guidelines on
adaptive lighting (CIE – 115-
2010)
CIE 115:2010 – LIGHTING OF ROADS FOR MOTOR AND 172
PEDESTRIAN TRAFFIC

• Takes improved performance of luminaires and lamps and

introduction of controls into account
• Provides a structured model for the selection of the appropriate
lighting classifications, taking into account parameters relevant
to visual tasks requirements
• By taking into account time dependent variables like traffic
volume or weather conditions, the model offers the possibility
to use adaptive lighting systems
CIE 115:2010 – LIGHTING OF ROADS FOR MOTOR
AND PEDESTRIAN TRAFFIC
Parameter Weighting Values
• Six Illuminance Classes (Vw)
Speed 1, 0.5, 0
• M = 6 – Vws
• Vws = Sum of Vw Traffic Volume 1, 0.5, 0, -0.5, -1

• Higher Speed, Higher Traffic Composition 2, 1, 0

Volume, Higher Density,
Separation of 1, 0
More Parked Vehicles Carriageways
–  Lower M Intersection Density 1, 0
–  Higher illuminance
Parked Vehicles 0.5, 0

Class M1 M2 M3 M4 M5 M6 Ambient Luminance 1 ,0,-1

Avg. Luminance 2.0 1.5 1.0 0.75 0.5 0.3 Visual Guidance, 0.5, 0
Avg. Illuminance 50 30 20 15 10 7.5 Traffic Control
FHWA GUIDELINES 174

Criteria for Luminance Selection

• Speed
• Traffic Volume
• Median
• Intersection/Interchange Density
• Ambient Luminance
• Guidance
• Pedestrians and Bicycles
• Parked Vehicles
• Facial Recognition

http://www.fhwa.dot.gov/publications/research/safety/14050/14050.pdf
DOE MODEL SPECIFICATION FOR NETWORKED 175

OUTDOOR LIGHTING CONTROL SYSTEMS

• A tool designed to help cities, utilities, and other local agencies

accelerate their adoption of systems that can further reduce the
energy and maintenance costs of operating their streetlights.
• A major update to the original “Model Specification for Adaptive
Control and Remote Monitoring of LED Roadway Luminaires”
– Renamed to better reflect its evolving scope
– A work-in-progress, a living document that reflects user
experiences and the changing commercial market

http://www1.eere.energy.gov/buildings/ssl/control-specification.html
VERSION 2.0 176

• Released April, 2014

• Introduction of a Backhaul Communication Network section
with associated requirements
• Separation of the Start-Up and Commissioning sections with
updated or enhanced requirements for both
• Further refinement focused on facilitating independent bids for
Central Management System(s), Backhaul Communication
Network(s), and Field Devices.
• More user notes, new and updated references to industry
standards activities, and continued clarification of specifications
recommended for all users vs. those deemed optional and
likely to be only required by some users.
INTENDED USE 177

• Intended to serve as a modular reference for drafting Requests

for Qualifications (RFQ’s), Requests for Information (RFI’s),
Requests for Proposals (RFP’s) or similar documents
• Not intended to serve as a standard specification, and
therefore should not (and in unedited form, can not) be used to
create a list of qualified products
• Intended to be customized as needed to meet the needs of a
specific User
CONTENT 178

• A template for translating unique user needs into clear and

consistent specification language
• Some suggested content is considered suitable for all Users,
and therefore presented as mandatory requirements.
• Other suggested content is considered suitable for only some
Users, and is therefore presented as Optional requirements.
ORGANIZED TO SUPPORT TYPICAL 179
PROJECT STAGES
ORGANIZATION 180

• PART 1 – INTRODUCTION
– Lists of normative and informative standardized references
– A structure for incorporating user-specific references
– A set of definitions
• PART 2 – SUBMITTED MATERIALS
– Suggested non-technical content that might be included in
a RFQ, presented at the announcement of an RFP,
included in a RFP, presented prior to signing a Contract, or
included in Contract terms
• PART 3 – SYSTEM DESCRIPTION
– Suggested content for describing the scope of a new
project in terms of what Components are being procured as
well as what Components comprise an existing System
ORGANIZATION 181

• Parts 4-7 focused on Component types and warranty terms

– PART 4 – CENTRAL MANAGEMENT SYSTEM
– PART 5 – BACKHAUL COMMUNICATION NETWORK
– PART 6 – FIELD DEVICES
– PART 7 – COMPONENT WARRANTY
ORGANIZATION 182

• Parts 8-11 focused on post-procurement project stages and

maintenance terms
• PART 8 – COMPONENT INSTALLATION
• PART 9 – SYSTEM START-UP
• PART 10 – SYSTEM COMMISSIONING
• PART 11 – SYSTEM MAINTENANCE
ORGANIZATION 183

• Appendices A-G contain suggested structure and examples for

describing existing equipment that comprise an existing
System, or will be integrated separately into the System
– Appendix A: Existing Central Management System
– Appendix B: Existing Backhaul Communication Network(s)
– Appendix C: Existing Field Devices
– Appendix D: Existing Luminaires
– Appendix E: Existing Sensor(s)
– Appendix F: Existing Asset Management System(s)
– Appendix G: Existing Intelligent Traffic System(s)
SPECIFYING INTEROPERABILITY 184
Q&A

Interoperability, Standards & Specifications

Michael Poplawski
Q&A

[email protected]
[email protected]
PLEASE REMEMBER TO COMPLETE THE
COURSE EVALUATIONS.
Thank you!