us dot intelligent transportation systems for and lighting …archive.iamu.org/conference/energy...
TRANSCRIPT
US DOT Intelligent Transportation Systems
Standards for Electrical and Lighting Management Systems
Control & Monitoring of Power & Lighting for Enhanced Safety, Reliability, Resource Allocation
and Energy Savings
Speaker
2
Jim FrazerITS / Smart Grid Consulting Engineer
Chairman ‐ US DOT Intelligent Transportation Systems Electrical Lighting and Management Systems Committee
Chairman ‐ Illuminating Engineering Society’s Roadway Lighting Energy Management Committee
Contributor ‐ IEEE P2030.1 Draft Guide for Electric‐Sourced Transportation Infrastructure
Agenda
• Goals of the US DOT & US DOE• Typical Roadway Lighting System Architecture• Case Studies• What is ITS & ELMS?• ELMS Features & Benefits• How to Specify ITS & ELMS Projects• What’s in the Future?• Resources for Learning More• The Big Picture: Global Competitiveness, Economic
Development
Learning Objective # 1
© US DOT 2012
The USDOT Integrated Framework
4
5
The US Smart Grid Framework
Learning Objective # 1
Subhead (Arial Bold 28 PT Green)
Text (Arial 24 PT Black)
Bullets Bullet 1 Bullet 2 Bullet 2
Sub bullets
NTCIP 1213
Roadway Lighting System Architecture
Management Center
Data Collector
Field Devices
Interoperable System Architecture
Management Center
Data Collector Interface Standards
Field Device Interface Standards
Interoperable Standards Development Focus
8
Definition and Purpose of an ELMS
An ELMS is defined as any system or device capable of sensing
and communicating near real‐time electrical and lighting
parameters using the US DOT’s NTCIP communications
protocol.
9
ELMS Case Study – Anytown, USA You’re the public works manager responsible for:
traffic signals, roadway lighting, and infrastructure.
Users the finance director field staff
You need to: deploy dimmable LED street lighting prepare for adaptive dynamic roadway lighting systems
of the future minimize ground fault injuries
10
ELMS Case Study – Anytown, USAThe User Needs
Energy use must be controllable Power outages must be communicated in near real‐time Dimmable LED lighting must be deployed Adaptive control of lighting based on vehicular and pedestrian traffic must be deployed Ground fault conditions must be communicated in near real‐time
11
ELMS Case Study – Anytown, USA
You’ve reviewed ELMS standards‐based solutions You consider ELMS‐based solutions very promising You then ask yourself
Can an ELMS system satisfy these five wide ranging user needs?
The answer is YES
12
ELMS Case Study – A City in MinnesotaThe User Needs
During a downtown reconstruction project, these user needs were identified:
Lighting system attributes must be monitored
Ground fault conditions must be communicated in near real‐time.
Selected lighting fixtures must be turned off during non‐peak periods
13
ELMS Case Study – A City in MinnesotaThe Results
Roadway lighting system attributes are monitored.
Ground fault conditions are communicated in near real‐time.
Selected lighting fixtures are turned off during non‐peak periods.
14
ELMS Case Study – A County in FloridaThe User Needs
Due to severe and fatal injuries of people and animals, these user needs were recognized:
Ground fault conditions must be communicated in near real‐time
Data must be logged Reports of alarms must be
generated
15
ELMS Case Study – A County in FloridaThe Result
Ground fault conditions are communicated in near real‐time Data is logged Reports of alarms are generated
16
ELMS Case Study – Washington State DOTThe User Needs
During a tunnel and bridge project, these user needs were identified:
Energy use must be controlled Power outages must be
communicated in near real‐time Adaptive control of lighting
based on ambient light levels must be deployed
17
ELMS Case Study – Washington State DOTThe Results
Energy use is controlled Power outages are communicated in near real‐time Adaptive control of lighting based on ambient light levels is deployed
What are Intelligent Transportation Systems?
• The term intelligent transportation system (ITS) describes the process of adding control, monitoring and communications technology to transportation infrastructure and vehicles to improve safety, reduce energy consumption, and to reduce vehicle wear, and transportation time.
• Development and application of ITS technology is also driven by the need for homeland security, and many of the proposed ITS systems also involve surveillance of the roadways.
• Additionally, through coordination with the U.S. Department of Energy, many ITS applications are also supported, enhanced and on occasion, driven by the needs of the Smart Grid electrical distribution technologies.
What is an ELMS?• An ELMS is defined as any system that is able to automatically control and
manage roadside electrical and lighting devices using the National Transportation Communications for Intelligent Transportation Systems (ITS) Protocol (NTCIP). In general, an ELMS is composed of a set of field devices (luminaires, electric circuits, etc.), that are controlled by one or more management stations (computing platforms).
• ELMS allows users to easily and intuitively interact with the wide range of functions and configuration parameters specified in the current Intelligent Transportation Systems (ITS) National Transportation Communications for ITS Protocol (NTCIP) Electrical Lighting and Management Systems (ELMS) standard (NTCIP 1213).
ELMS System Overview• E L M S is the acronym for Electrical Lighting and Management Systems • The effort to develop a standard for Electrical and Lighting Management Systems began with the
formation of an ad‐hoc committee of the Illuminating Engineering Society of North America (IESNA).
• It is now supported by:– ITE, NEMA, AASHTO and the US DOT / Federal Highway Administration
• Technically, the NTCIP Objects for Electrical and Lighting Management Systems defines data elements in ASN.1 using the SNMP Object Type Macro for field devices that monitor and control electrical and lighting systems. These objects define the software interface at the field data logger.
• For more information about NTCIP standards, visit the NTCIP Web Site at http://www.ntcip.org. For a hardcopy summary of NTCIP information, contact the NTCIP Coordinator at the following address.
NTCIP CoordinatorNational Electrical Manufacturers Association
1300 N.17th Street, Suite 1847Rosslyn, Virginia 22209‐3801
fax: (703) 841‐3331 e‐mail:[email protected]
ELMS Terminology• Management Station
– the host computing platform that controls the field Devices. Each station may be installed
– in a local Transportation Management Center (TMC), – or can be field based.
• ELMS Device– A device, module, or piece of equipment which– contains an SNMP Agent,– and is the interface between a component of an illumination system and the NTCIP
communication system. – The device may be integral to a component of the illumination system.
• Simple Network Management Protocol (SNMP) Agent – A logical entity that is hosted on an ELMS device (ex: a Data Logger) that manages the
communications between the management station and other ELMS devices in the system.
• Data Logger– Unit that collects and stores information on the state and operation of ELMS Devices.
ELMS Terminology• Electric Service
– The conductors and equipment for delivering electric energy from the serving utility to the wiring system of the premises served.
• Branch Circuit – Local electrical circuit that provides power to the Luminaires.
• Pole – Roadside light pole. Poles may be categorized by
• their constituent material types • and/or design configurations.
• Luminaire – The light fixture and possibly associated sensors– Luminaires may be organized into control zones– Management functions can be performed on individual Luminaires
or on zones of Luminaires (ex: Scheduling, Dimming)
ELMS System Architecture
Power Meter
NTCIP Supervisory StationManagement Center
NTCIPLocal
Data Logger
Electrical ServiceController
Ground FaultDetector
Electrical Service Controller
Branch CircuitController
Streetlight Controller
Branch CircuitController
StreetlightController
Local CommunicationsAmbient Light
Sensor
NTCIP
Remote Communications Dedicated, Dial‐up, Wireless, BPL, Fiber, Microwave, etc.
ELMS Definitions• MIB – Management Information Base
– A hierarchical data table of system variables• SNMP – Simple Network Management Protocol
– Networking language for computers– The “language” of MIBs
• NTCIP – National Transportation Communication for ITS Protocol – Supported by NEMA, AASHTO and ITE
• Management Station – Management Center– Operator’s User Interface– Data archiving capabilities– Possible data mining capabilities
Management Stations & SNMP Agents
SNMPStandardDynamic Message
SignMIB
Traffic Management
Center 1
SNMPStandardCamera
MIB
SNMPTraffic Flow
SensorsMIB
SNMPStandard
Electrical Lighting &
Management Systems
MIB
Finance Maintenance Emergency Operations
Center
Operations EMS
SNMPMany Other
StandardMIBs
Electric Usage
Hurricane Evacuation Routing
TCP/IP
for FTP
TMC 2
TMC 3UDP for Management Station to SNMP Agent Communications
Pole Knockdown
Homeland Security Event
What’s a “Standardized” MIB?Data table of values, with engineering units, in hierarchical order
System Components• Software for
Management Station• NTCIP 1213
Compliant Data Logger, standalone devices or embedded within streetlight, meter etc.
• Ground Fault Detector
• Streetlight Controller• Ambient Light Sensor• Power Meter• Pole Knockdown
Other Features
• Lat/Lon or GPS• Mapping –
– Google Maps / ESRI / Bing etc.
• Data Mining– When will the fixture fail?– What combination of components
offers the best performance?– Which offers the best payback?– Which lasts the longest?
Controllers: Streetlight, Branch Circuit & Electrical Service
• Reads Current and Voltage
• Switches Lighting Load• Monitors “Run Time”• Reports Status• Reports Power Usage
Revenue Grade Energy Meter• Reads Current and Voltage• Reports Status• Reports Power Usage• Revenue Grade Accuracy• Supports all NTCIP 1213
Parameters• Hard Wired to Current
Transformer
Ground Fault Detector• Reads Dangerous
Current Leakage• Reports Status• Reports Alarms
ELMS Features & Benefits• Low operating costs:
– No continuing subscription fees from telecommunications providers. • Energy Savings
– Through intelligent scheduling of, lighting and elimination of wasteful “dayburners”.
• Control any light, any meter, any ground fault sensor, and circuit: – Any terminal device can be controlled individually and in seconds from an
Internet browser or a mobile phone• Modularity & Flexibility:
– An ELMS system can at any time be expanded to new areas or cities, using existing servers, i.e. with only incremental costs. As the system is based on open standards it can easily be interfaced with other systems, for example GIS and management information systems
• Reports: – The user interface offers fast and easy access to a number of 24‐hour
reports including actual switch on/off times, burn‐hours, and other events
ELMS Features & Benefits• Minimizes errors and the costs of correcting them:
– An efficient replacement program for maximum use of each luminaire can be based on precise burn‐hour data.
– Faults in cabinets, luminaires or electrical circuits are reported automatically, eliminating the need of costly visual inspections
• Complete reporting of system parameters: – generates all the reports needed in control and management,
including reports on streetlight, branch circuit and electrical service settings, including event and fault reports.
• Monitors & control power consumption: – Power meters and ground fault detectors can be deployed anywhere
on the network
ELMS Features & Benefits• Blackout / Brownout protection
– Dimming or switching of individual streetlights can minimize the need for more intrusive actions, such as rolling brownouts
• Compatible with ITS NTCIP 1213– ELMS system is compatible with the NTCIP 1213 software standards
for Electrical Lighting and Management Systems– Federal Highway Grants for ITS NTCIP Applications
• Safety– Reporting of dangerous ground fault conditions– Saving of LIVES
• Real‐time monitoring and logging: – Switch on/off, re‐programming, electricity consumption and faults. All
events are reported and logged.
How Do You Use ELMS NTCIP 1213?• The specification guides:
– Your project’s required user needs
– Your project’s functional requirements
– Your project’s test plan
• Through Use of the Protocol Requirements List
The ELMS Protocol Requirements List
The ELMS Protocol Requirements List1. Select Your User Needs
The ELMS Protocol Requirements List2. Based on Your User Needs, Select the Functional Requirements
The ELMS Protocol Requirements List3. Determine Conformance
The ELMS Protocol Requirements List3. Confirm the Project Requirements
How to Use the ELMS Standard
1. Identify your User Need
2. Select the Dependent Project Requirements
3. Use the Completed Document as your Project Specification
44
Integrating the PRL into an ELMS Specification
ELMS Contract Documents
A completed ELMS PRL is part of the overall specification, in addition to the hardware and software specifications
Importance of the UN / FR Relationship
• User Needs describe what features are required • Functional Requirements refine the user needs into detailed, measurable specifications
• Within the PRL, the relationships between User Needs and Functional Requirements are standardized
• Promotes Interoperability
PRL ‐ User Needs ‐ FR Relationship
• Requirements associated with a User Need are found under that User Need
• Each user need will have at least one requirement associated with it
• Each requirement in the standard is associated with at least 1 user need
• Result: the standard has no unnecessary requirement, and all user needs are satisfied by at least one requirement
Conformance vs. Compliance
• Conformance: – Meets a specified standard– To claim "conformance" to NTCIP 1213, the vendor shall minimally satisfy the mandatory requirements without violating any rules
– Vendors that provide additional features beyond the completed PRL are still conformant
• Compliance – Meets a specification (e.g., for a specific project)
The PRL from an Agency Perspective
• A completed PRL must become part of the overall specification
• Completed PRL indicates the requirements for the communications interface, and, by extension, the user needs (and functional requirements) that the ELMS must support
• If the agency desires to utilize commercial off‐the‐shelf devices, then the agency should compare their list of selected needs and requirements with equipment that is available on the market to ensure that they are not specifying something that does not exist.
The PRL from an Agency Perspective
• Contract Documents:– The completed PRL has to be consistent with the hardware specification.
– The completed PRL shows the intent. – Interested vendors can view the PRL and understand the intent of the requirements.
50
Agency Use of the ELMS PRL
Learning Objective # 3
The ELMS PRL can be used by:
A user or agency specification writer to indicate which requirements are to be implemented in a project specific implementation
The protocol implementer, as a checklist to reduce the risk of failure to conform to NTCIP 1213
51
Supplier and User Use of the PRL
Learning Objective # 3
The ELMS PRL can also be used by:
The supplier (vendor) and user, as a detailed indication of the capabilities of the implementation
The user, as a basis for initially checking potential interoperability with another implementation
What’s Coming In the Version 3.0?
• Vehicle to Infrastructure Communications– Speed, direction, location, road friction, temperature, humidity and ambient light level
– Drives “Adaptive Roadway Lighting”
• Electric Vehicle Charging Support• Better Integration to the Smart Grid
– Energy Services Interface (ESI)
Adaptive Lighting in Version 3.0
• Adaptive Lighting ‐in support of Smart Grid applications in managing power for roadside lighting and is dependent on vehicle and pedestrian locations (V2I)
The ESI in Version 3.0Energy Services
Interface • deals with security,
time base, exchange of dollars for services, basically standardized grid interoperation signals
• buying and selling of energy
• standardized grid interoperation signals
EV Support in Version 3.0• Electric Vehicle
Support– Charging
Management • used to communicate with a charging station to manage the efficient charging of electric vehicles.
– Charging Payment • used to pay for a charge taken at a pay‐by‐the‐charge station.
– Interoperability
SAE J2836 ™
Use casesScope
SAE J2847Detailed Info
Messages
/1 Utility Programs * /1
/2 Off‐Board Charger Communications
/2
/3 Reverse Energy Flow /3
/4 Diagnostics /4
/5 Customer and HAN /5
/6 Wireless Charging /6
US DOT V2I Standards
ambient light level
ITS SAE J2735 SE
Adaptive Roadway Lighting, EV Charging, etc.
Driving The Vision
AASHTO NEMA ITE US DOT US DOE Smart Grid US DOE MSSLC SAE ITSA IES IMSA UN ITU
Integration with the Larger Ecosystem Not a Standalone Solution US DOE
NIST Smart Grid
FHWA Adaptive Lighting Policies
ELMSNTCIP 1213
IES Adaptive Lighting Design Guide
DOE MSSLC Efforts
Roadway Lighting
TechnicianIMSA
ITS NTCIP 1213
Courses
Roadway Lighting SpecialistIMSA
IES RLC Education
Learn More: The ITS PCB Program
I101Using ITS Standards: An Overview
A101Introduction to Acquiring
Standards‐based ITS Systems
A102Introduction to User Needs
Identification
A201Details on Acquiring Standards‐
based ITS Systems
A306aUnderstanding
User Needs for ELMS Based on NTCIP 1213 Standard
A306bSpecifying Requirements
for ELMS Based on NTCIP 1213 Standard
http://www.pcb.its.dot.gov/
Current ITS PCB CoursesDescription Module Title Number Availability
MODULE 1 USING ITS STANDARDS: AN OVERVIEW I101 Available!MODULE 2 INTRODUCTION TO ACQUIRING STANDARDS-BASED ITS SYSTEMS A101 Available!MODULE 3 INTRODUCTION TO USER NEEDS IDENTIFICATION A102 Available!MODULE 4 INTRODUCTION TO ITS STANDARDS REQUIREMENTS DEVELOPMENT A103 Available! MODULE 5 INTRODUCTION TO ITS STANDARDS TESTING T101 Available!MODULE 6 DETAILS ON ACQUIRING STANDARDS-BASED ITS SYSTEMS A201 Available!MODULE 7 IDENTIFYING AND WRITING USER NEEDS WHEN ITS STANDARDS DO NOT HAVE SEP CONTENT A202 Available!MODULE 8 WRITING REQUIREMENTS WHEN ITS STANDARDS DO NOT HAVE SEP CONTENT A203 Available! MODULE 9 HOW TO WRITE A TEST PLAN T201 Available!MODULE 10 UNDERSTANDING USER NEEDS FOR DMS SYSTEMS BASED ON NTCIP 1203 STANDARD A311a Available!MODULE 11 UNDERSTANDING USER NEEDS FOR ESS SYSTEMS BASED ON NTCIP 1204 v03 STANDARD A313a Available!
MODULE 12 UNDERSTANDING USER NEEDS FOR TRAFFIC MANAGEMENT SYSTEMS BASED ON TMDD v3 STANDARD
A321a Available!
MODULE 13 OVERVIEW OF TEST DESIGN SPECIFICATIONS, TEST CASES, AND TEST PROCEDURES T202 Available!MODULE 14 SPECIFYING REQUIREMENTS FOR DMS SYSTEMS BASED ON NTCIP 1203 STANDARD A311b Available!MODULE 15 SPECIFYING REQUIREMENTS FOR ESS SYSTEMS BASED ON NTCIP 1204 v03 STANDARD A313b Available!
MODULE 16 SPECIFYING REQUIREMENTS FOR TRAFFIC MANAGEMENT SYSTEMS BASED ON TMDD v03 STANDARD
A321b Available!
MODULE 17 APPLYING YOUR TEST PLAN TO THE NTCIP 1203 v03 DMS STANDARD T311 Available!MODULE 18 APPLYING YOUR TEST PLAN TO THE NTCIP 1204 v03 ESS STANDARD T313 Available!
http://www.pcb.its.dot.gov/
US DOT ITS NTCIP 1213 ELMSThe US DOT, DOE & Commerce Departments want you to:
Specify and design NTCIP compliant ELMS technology into your roadway infrastructure projects
What’s The Big Picture
• US DOT ELMS is but a small part of a BIG PICTURE• We live in a globally competitive world• Des Moines competes with Davenport
– but also Palo Alto, Shanghai, Tel Aviv & Berlin
• To compete the cities and counties must build the infrastructure that allows competiveness– Historically this was highways, ports and railroads– Today this is Wi‐Fi, fiber, LED, energy management
• Join the US DOT, US DOE, Commerce Department and NIST in this effort
Why? ‐ The Big Picture• To drive STEM jobs
– Science, Technology, Engineering, Mathematics– IT, Biomedical, Research…– High value added jobs
• Tax Ratables• Vibrant Economic Development• Influx of Population / Revitalize Downtown• Creation of an Green, High Tech Ecosystem• Get your EDC involved
Questions
Thank You