Module 26 - A306a

A306a: Understanding User Needs for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard

HTML of the Student Supplement

(Note: This document has been converted from the Student Supplement to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

Table of Contents

Module Description - 2

Introduction/Purpose - 2

Samples/Examples - 5

Reference to Other Standards - 30

Glossary - 31

References - 38

Study Questions - 40

Icon Guide - 42

 

1. Module Description

This participant supplement provides additional information for the Professional Capacity Building (PCB) Module A306a, Understanding User Needs for ELMS Systems Based on NTCIP 1213 Standard v03.

Module A306a will provide participants with information on how to identify the appropriate use of the NTCIP 1213 v03 standard and acquire an ELMS system based on what the user is seeking to accomplish with support from tools and resources such as a Protocol Requirements List (PRL) in following a systems engineering process (SEP).

This module helps the user understand the scope of the ELMS standard and its versions. It also assists in identifying the uses and associated needs of ELS systems. This module is to be placed in the context of SEP as well as in the acquisition curriculum path, with I101, A101, A102, A201, C101, and C201 being the prerequisites, and with A306b - Specifying Requirements for ELMS Systems Based on NTCIP 1213 v03 Standard following this module.

This participant supplement provides:

 

2. Introduction/Purpose

The purpose of this updated module is to incorporate necessary changes resulting from new user needs and capabilities such as connected vehicles, SMART Grid, and others included in the updated NTCIP 1213 standard v03 (from v02). NTCIP 1213 v03 defines the generic reference model and conformance requirements for traffic management centers (TMCs) that wish to provide interfaces to ELMS field devices. An ELMS is defined as any system capable of monitoring, controlling, and communicating certain electrical and lighting system parameters using NTCIP.

The effort to develop an NTCIP ELMS standard began with the International Technology Exchange Program's European Road Lighting Technologies scan tour in April 2001 (Report FHWA-PL-01-034 dated September 2001). This technology and implementation plan was further developed by the American Association of State Highway and Transportation Officials (AASHTO) Task Force for Highway Lighting and is being implemented as the Master Lighting Plan in the AASHTO publication entitled Roadway Lighting Design Guide. The Task Force's original desire was to define the features, functionality, and point of interoperability for ELMS equipment.

NTCIP 1213 v03 defines data elements in ASN.1 using the SNMP Object Type Macro for field devices that monitor and control electrical and lighting systems.

NTCIP 1213 v03 is an NTCIP Device Data Dictionary Standard. Device Data Dictionary Standards define management information in terms of objects (data elements, data frames, and messages) for use within NTCIP systems.

History

In 1992, the National Electrical Manufacturers Association (NEMA) 3-TS Transportation Management Systems and Associated Control Devices Section began development of the NTCIP. The Transportation Section's work was in response to user needs to include standardized systems communication in the NEMA TS 2 standard, Traffic Controller Assemblies. Under the guidance of the Federal Highway Administration's NTCIP Steering Group, the NEMA effort was expanded to include the development of communications standards for all transportation field devices that could be used in an Intelligent Transportation Systems (ITS) network.

In September 1996, an agreement was executed among AASHTO, ITE, and NEMA to jointly develop, approve, and maintain the NTCIP standards. In 2002, the Joint Committee on the NTCIP accepted the invitation from Karl Burkett (Texas DOT) to transfer the initial work of an ad hoc committee of the Illuminating Engineering Society of North America (IESNA), and formed the NTCIP ELMS Working Group to further develop the control objects based on NTCIP. The NTCIP ELMS Working Group's first meeting was in April 2003.

NTCIP 1213 v02 development started in 2002 under funding provided by the FHWA. NTCIP 1213 v01.03.

February 2004—Accepted as a User Comment Draft by the Joint Committee on the NTCIP.

March 2004—NTCIP Standards Bulletin B0090 distributed for user comment.

NTCIP 1213 v02. The ELMS Working Group incremented the major version number to indicate the substantial reorganization of content. Version v01 never advanced beyond the User Comment Draft stage.

NTCIP 1213 v02.19. December 2005—Accepted v02.19b as a Recommended Standard by the Joint Committee on the NTCIP.

December 2006—NTCIP Standards Bulletin B0111 referred v02.19d for balloting. Approved by AASHTO in July 2008, approved by ITE in March 2008, and approved by NEMA in June 2007.

NTCIP 1213 v02.20. June 2010—Began editing publication. July 2010—discussed proposals for alternative Management Information Base (MIB) object definitions (astronomical clock);

November 2010—incorporated compilable alternative MIB object definitions and polled the NTCIP ELMS Working Group for approval.

NTCIP 1213 v02.20. December 2010—removed direct references to NTCIP 1103 v02 for trap support-addressed astronomical clock feature in supplied MIB modifications in Annex B. February 2011— completed editing and publication.

NTCIP 1213 v03. February 2017—maintains backwards compatibility with v02, adds support for connected vehicles, electric vehicle charging, and Smart Grid automated demand response.

Compatibility of Versions

To distinguish NTCIP 1213 v03 (as published) from previous drafts, the NTCIP 1213 v03 standard includes "NTCIP 1213 v03" on each page header. All NTCIP Standards Publications have a major and minor version number for configuration management. The version number syntax is 'v00.00a,' with the major version number before the period, and the minor version number and edition letter (if any) after the period.

NTCIP 1213 v02 is designated, and should be cited as, NTCIP 1213 v02. Anyone using NTCIP 1213 v02 should seek information about the version number that is of interest in any given circumstance. The MIB and, the PRL should all reference the version number of the standards publication that was the source of the excerpted material.

Compliant systems based on later, or higher, version numbers MAY NOT be compatible with compliant systems based on earlier, or lower, version numbers. Anyone using NTCIP 1213 v02 should also consult NTCIP 8004 v02 for specific guidelines on compatibility.

ELMS Types

There are many types of ELMS and they can be characterized in many ways. One way is by the capabilities the ELMS offers for terminal device support. This characterization places an ELMS into one of following major categories:

  1. Power Control and Monitoring - this type of ELMS primarily addresses energy metering and power quality
  2. Control and Monitoring of Roadway Lighting - this type of ELMS focuses upon control and monitoring of street and roadway lighting fixtures
  3. Ground Fault Control and Monitoring - this type of ELMS is one in which the features deployed support detection and interruption of transient electrical currents commonly known as ground faults
  4. Electric Vehicle Charging Management
  5. Smart Grid Automated Demand Response
  6. Connected Vehicle and Connected Pedestrian Support - for true adaptive roadway lighting

 

3. Samples/Examples

For a comprehensive perspective on the broad capabilities of an NTCIP 1213 v03 compliant ELMS, please review the complete PRL listed below:

User Need ID User Need FR ID Functional Requirement Conformance Support Additional Specifications
2.5.1 Operational User Needs M Yes  
2.5.1.1 Provide Live Data M Yes  
    3.5.1.1 Retrieve Data M Yes  
    3.5.1.2 Deliver Data M Yes  
    3.5.1.3 Data Retrieval and Data Delivery Action Performance M Yes  
    3.5.1.4 Live Data Response Time M Yes  
2.5.1.2 Provide Off-Line Log Data O Yes / No  
    3.5.2.1 Retrieve Configuration of Logging Service M Yes  
    3.5.2.2 Configure Logging Service M Yes  
    3.5.2.2.1 Configure Number of Events in Event Log M Yes / No The ELMS device shall support at least _____ (1..255) events.
    3.5.2.2.2 Configure Number of Event Classes M Yes / No The ELMS device shall support at least _____ (1..255) classes.
    3.5.2.2.3 Configure Number of Event Types M Yes / No The ELMS device shall support at least _____ (1..255) event types.
    3.5.2.3 Retrieve Logged Data      
    3.5.2.4 Clear Log M Yes  
    3.5.2.5 Retrieve Capabilities of Event Logging Services M Yes  
    3.5.2.6 Retrieve Number of Events Currently Logged M Yes  
    3.5.2.7 Set Time M Yes  
    3.5.2.8 Retrieve Current Time M Yes  
    3.5.2.9 Set Daylight Saving Time Mode M Yes  
    3.5.2.10 ELMS Pre-Defined Event Configurations M Yes  
    3.5.2.10.1 Supported Event Classes M Yes  
             
2.5.1.2.1 Provide Luminaire Switch State Logging O Yes / No  
    3.5.2.10.2 Luminaire Switch State Log O Yes / No  
2.5.1.2.2 Provide Luminaire Condition Logging O Yes / No  
    3.5.2.10.3 Luminaire Condition Log O Yes / No  
2.5.1.2.3 Provide Luminaire Operating Hours Condition Logging O Yes / No  
    3.5.2.10.4 Luminaire Operating Hours Condition Log O Yes / No  
2.5.1.2.4 Provide Periodic Luminaire Operating Hours Time Logging O Yes / No  
    3.5.2.10.5 Periodic Luminaire Operating Hours Time Log O Yes / No  
2.5.1.2.5 Provide Luminaire Temperature Logging O Yes / No  
    3.5.2.10.6 Luminaire Temperature Log O Yes / No  
2.5.1.2.6 Provide Luminaire Pole Condition Logging O Yes / No  
    3.5.2.10.7 Luminaire Pole Condition Log O Yes / No  
2.5.1.2.7 Provide Relay Switch State Logging O Yes / No  
    3.5.2.10.8 Relay Switch State Log O Yes / No  
2.5.1.2.8 Provide Energy Meter Switch State Logging O Yes / No  
    3.5.2.10.9 Energy Meter Switch State Log O Yes / No  
2.5.1.2.9 Provide Periodic Energy Meter Measurement Logging O Yes / No  
    3.5.2.10.10 Periodic Energy Meter Measurement Log O Yes / No  
2.5.1.2.10 Provide Energy Meter Condition Logging O Yes / No  
    3.5.2.10.11 Energy Meter Condition Log O Yes / No  
2.5.1.2.11 Provide Ground Fault Switch State Logging O Yes / No  
    3.5.2.10.12 Ground Fault Switch State Log O Yes / No  
2.5.1.2.12 Provide Periodic Ground Fault Measurement Logging O Yes / No  
    3.5.2.10.13 Periodic Ground Fault Measurement Log O Yes / No  
2.5.1.2.13 Retrieve Logged Data M Yes  
    3.5.2.3 Retrieve Logged Data M Yes  
2.5.1.3 Monitor Exception Conditions O Yes / No  
    3.5.3.1 Retrieve Current Configuration of Exception Reporting Service M Yes  
    3.5.3.2 Configure Events M Yes  
    3.5.3.3 Provide Automatic Reporting of Events (NTCIP Traps) M Yes  
    3.5.3.4 Manage Exception Reporting M Yes  
    3.5.3.5 Retrieve Capabilities of Exception Reporting Service M Yes  
    3.5.3.6 Retrieve Current Number of Exception Events M Yes  
    3.5.3.7 Record and Timestamp Events M Yes  
2.5.2 Functional User Needs M Yes  
2.5.2.1 Configure ELMS Device M Yes  
2.5.2.1.1 Configure Luminaire O Yes / No  
2.5.2.1.1 Retrieve Luminaire Information O Yes / No  
    3.5.4.1.1.1 Retrieve Luminaire Pole Identifier O Yes / No  
    3.5.4.1.1.2 Retrieve Luminaire Location M Yes  
    3.5.4.1.1.3 Retrieve Luminaire Mode M Yes  
    3.5.4.1.1.4 Retrieve Luminaire Zone O Yes / No  
    3.5.4.1.1.5 Retrieve Luminaire Vendor Information M Yes  
    3.5.4.1.1.6 Retrieve Luminaire Light Source Type O Yes / No  
    3.5.4.1.1.7 Retrieve Luminaire Wattage O Yes / No  
    3.5.4.1.1.8 Retrieve Luminaire Voltage O Yes / No  
    3.5.4.1.1.9 Retrieve Luminaire Ballast / Driver Description O Yes / No  
    3.5.4.1.1.10 Retrieve Luminaire Communications Protocol O Yes / No  
2.5.2.1.1.2 Configure Luminaire Identification Information O Yes / No  
    3.5.4.1.1.2. 1 Specify Location in Longitude/Latitude O Yes / No  
    Coordinates    
    3.5.4.1.1.2. 2 Specify Location Information Using Textual Description of a Road / Street / Block Name / Number O Yes / No The ELMS device shall support a location name of at least _____ (8..255) Characters.
    3.5.4.1.1.2. 3 Specify Location in Local Reference Coordinate Grid O Yes / No  
    3.5.4.1.2.1 Configure Luminaire Pole Identifier O Yes / No  
    3.5.4.1.2.2 Configure Luminaire Location M Yes  
2.5.2.1.1.3 Configure Luminaire Mode O Yes  
    3.5.4.1.3 Configure Luminaire Mode M Yes  
2.5.2.1.1.4 Manage Luminaire Color Temperature O    
    3.5.4.1.4 Manage Luminaire Color Temperature O Yes / No  
             
2.5.2.1.2 Configure Electrical Service O Yes  
2.5.2.1.2.1 Retrieve Electrical Service Information O Yes / No  
    3.5.4.2.1.1 Retrieve Electrical Service Location M Yes  
    3.5.4.2.1.2 Retrieve Electrical Service Zone O Yes / No  
    3.5.4.2.1.3 Retrieve Electrical Service Pole Identifier O Yes / No  
    3.5.4.3.1 Configure Electrical Service Location M Yes  
    3.5.4.3.2 Configure Electrical Service Pole Identifier O Yes / No  
2.5.2.1.3 Configure for Light-Activated Operation O Yes / No  
    3.5.4.4.1 Configure Luminaire for Light Activated Operations M Yes  
    3.5.4.4.2 Configure Electrical Service for Light Activated Operations O Yes / No  
    3.5.4.4.3 Configure Branch Circuit for Light Activated Operations O Yes / No  
    3.5.4.4.4 Configure Devices in Zone for Light Activated Operations O Yes / No  
2.5.2.1.4 Configure for Scheduled Operation O Yes / No  
    3.5.4.5.1 Configure Luminaire for Scheduled Operations O.1 (1..*) Yes / No  
    3.5.4.5.2 Configure Electrical Service for Scheduled Operations O.2 (1..*) Yes / No  
    3.5.4.5.3 Configure Branch Circuit for Scheduled Operations O.3 (1..*) Yes / No  
    3.5.4.5.4 Configure Devices in Zone for Scheduled Operations O.4 (1..*) Yes / No  
    3.5.4.5.5 Schedule ELMS Device Event M Yes  
    3.5.4.5.6 Retrieve a Schedule M Yes  
             
    3.5.4.5.7 Support a Number of Actions M Yes The ELMS Device shall support at least _____ (1..255) Actions.
    3.5.4.5.8 Support a Number of Day Plans M Yes The ELMS Device shall support at least _____ (1..255) Day Plans.
    3.5.4.5.9 Perform Action at a Scheduled Time M Yes  
2.5.2.1.5 Configure Zones O Yes / No  
    3.5.4.6.1 Configure Luminaire Zone M Yes  
    3.5.4.6.2 Configure Electrical Service Zone O Yes / No  
    3.5.4.6.3 Configure Branch Circuit Zone O Yes / No  
    3.5.4.6.4 Configure Electric Vehicle Charger Zone O Yes / No  
    3.5.4.6.5 Define Zones M Yes  
             
    3.5.4.6.6 Define Number of Zones Supported by an ELMS Device M Yes / No The ELMS Device shall support at least _____ (0..65535) Zones.
    3.5.4.6.7 Define Number of ELMS Devices for a Zone M Yes / No At least _____ (0..65535) ELMS devices shall be able to be assigned to a single zone.
2.5.2.1.6 Configure for Manual Operation M Yes  
    3.5.4.9.1 Configure Luminaire for Manual Operation O Yes  
    3.5.4.9.2 Configure Electrical Service for Manual Operations O Yes / No  
    3.5.4.9.3 Configure Branch Circuit for Manual Operations O Yes / No  
    3.5.4.9.4 Configure Devices in Zone for Manual Operations O Yes / No  
2.5.2.1.7 Configure Stagger Interval O Yes / No  
    3.5.4.7.1 Configure Luminaire Stagger Interval O Yes The ELMS device shall support a stagger interval with a maximum value of _____ (0..255) seconds.
    3.5.4.7.2 Configure Branch Circuit Stagger Interval O Yes / No The ELMS device shall support a stagger interval with a maximum value of _____ (0..255) seconds.
    3.5.4.7.3 Configure Electrical Service Stagger Interval O Yes / No The ELMS device shall support a stagger interval with a maximum value of _____ (0..255) seconds.
2.5.2.1.8 Configure Light Levels O Yes / No  
    3.5.4.8.1 Configure Luminaire Light Level O Yes  
    3.5.4.8.2 Configure Electrical Service Light Level O Yes / No  
    3.5.4.8.3 Configure Branch Circuit Light Level O Yes / No  
    3.5.4.8.4 Configure Light Level for Devices in Zone O Yes / No  
2.5.2.1.9 Configure Electrical Service Monitoring and Metering Equipment O Yes / No  
    3.5.4.10.1 Configure Branch Circuit Ground Fault Detector O Yes / No  
    3.5.4.10.2 Configure Branch Circuit Power Meter O Yes / No  
    3.5.4.10.3 Configure Branch Circuit Arc Fault Detector O Yes / No  
2.5.2.1.10 Configure Branch Circuit O Yes / No  
2.5.2.1.10. 1 Retrieve Branch Circuit Information O Yes / No  
    3.5.4.11.1.1 Retrieve Branch Circuit Zone O Yes / No  
    3.5.4.11.1.2 Retrieve Branch Circuit Location O Yes / No  
    3.5.4.11.1.3 Retrieve Branch Circuit Pole Identifier O Yes / No  
    3.5.4.11.1.4 Retrieve Branch Circuit Electrical Parameters O Yes / No  
2.5.2.1.10. 2 Configure Branch Circuit O Yes / No  
    3.5.4.11.2.1 Configure Branch Circuit Location O Yes / No  
    3.5.4.11.2.2 Configure Branch Circuit Pole Identifier O    
2.5.2.1.11 Manage Configuration of Astronomical Clock O Yes / No  
2.5.2.1.11. 1 Configure Astronomical Clock O Yes / No  
    3.5.4.12.1 Configure Latitude of Installation O Yes / No  
    3.5.4.12.2 Configure Longitude of Installation O Yes / No  
    3.5.4.12.3 Configure Date O Yes / No D
2.5.2.1.11. 2 Retrieve Astronomical Clock Information O Yes / No  
    3.5.4.13.1 Retrieve Latitude of Installation O Yes / No  
    3.5.4.13.2 Retrieve Longitude of Installation O Yes / No  
    3.5.4.13.3 Retrieve Date O Yes / No  
    3.5.4.13.4 Retrieve Sunrise Time O    
    3.5.4.13.5 Retrieve Sunset Time O    
2.5.2.1.12 Manage Configuration of Photocells O Yes / No  
2.5.2.1.12. 1 Configure Photocells O Yes / No  
    3.5.4.14.1 Configure Photocell for Analog, Digital or Reverse Operations O Yes / No  
2.5.2.1.12. 2 Retrieve Photocell Configuration O Yes / No  
    3.5.4.14.2 Retrieve Configuration of Photocell O Yes / No  
2.5.2.1.13 Configure Energy Meter O Yes / No  
2.5.2.1.13. 1 Configure Energy Meter Accuracy O Yes / No  
    3.5.4.15.1 Configure Accuracy of Energy Meter M Yes / No  
2.5.2.1.13. 2 Retrieve Energy Meter Accuracy O Yes / No  
    3.5.4.15.2 Retrieve Accuracy of Energy Meter M Yes / No  
2.5.2.1.14 Retrieve Connected Vehicle Sensor Information O Yes / No  
    3.5.4.16.1 Retrieve Connected Vehicle Speed O Yes / No  
    3.5.4.16.2 Retrieve Connected Vehicle Direction O Yes / No  
    3.5.4.16.3 Retrieve Connected Vehicle Location O Yes / No  
    3.5.4.16.4 Retrieve Connected Vehicle Ambient Light Level O Yes / No  
    3.5.4.16.5 Retrieve Connected Vehicle Headlight Status O Yes / No  
    3.5.4.16.6 Retrieve Connected Vehicle Road Friction O Yes / No  
2.5.2.1.15 Retrieve Electric Vehicle Charger Information O Yes / No  
    3.5.4.17.1 Retrieve Electric Vehicle Charger Manufacturer NameLocation M Yes / No  
    3.5.4.17.1 Retrieve Electric Vehicle Charger Manufacturer Name O Yes / No  
    3.5.4.17.2 Retrieve Electric Vehicle Charger Model Number O Yes / No  
    3.5.4.17.3 Retrieve Electric Vehicle Charger Serial Number O Yes / No  
    3.5.4.17.4 Retrieve Electric Vehicle Charger Ground Fault Current Status O Yes / No  
    3.5.4.17.5 Retrieve Electric Vehicle Charger Charge Current O Yes / No  
    3.5.4.17.6 Retrieve Electric Vehicle Charger Proximity Resistance O Yes / No  
    3.5.4.17.7 Retrieve Electric Vehicle Charger Temperature O Yes / No  
    3.5.4.17.8 Retrieve Electric Vehicle Charger Activation O Yes / No  
    3.5.4.17.9 Retrieve Electric Vehicle Charger Operational Status O Yes / No  
    3.5.4.17.10 Retrieve Electric Vehicle Charger Total Energy Consumed O Yes / No  
    3.5.4.17.11 Retrieve Electric Vehicle Charger Energy Delivered for Current Charging Session O Yes / No  
    3.5.4.17.12 Retrieve Electric Vehicle Charger Energy Delivered for Previous Charging Session O Yes / No  
    3.5.4.17.13 Retrieve Electric Vehicle Charger Energy Loss O Yes / No  
             
2.5.2.1.16 Retrieve Energy Automatic Demand Response Information O Yes / No  
    3.5.4.18.1 Retrieve Electricity Price O Yes / No  
    3.5.4.18.2 Retrieve Energy Price O Yes / No  
    3.5.4.18.3 Retrieve Demand Charge O Yes / No  
    3.5.4.18.4 Retrieve Bid Price O Yes / No  
    3.5.4.18.5 Retrieve Bid Load O Yes / No  
    3.5.4.18.6 Retrieve Bid Energy O Yes / No  
    3.5.4.18.7 Retrieve Load Dispatch O Yes / No  
    3.5.4.18.8 Retrieve Load Control Capacity O Yes / No  
    3.5.4.18.9 Retrieve Load Control Offset O Yes / No  
    3.5.4.18.10 Retrieve Load Control Setpoints O Yes / No  
    3.5.4.18.11 Retrieve Load Control Percent Offset O Yes / No  
             
2.5.2.1.17 Configure Ground Fault Interrupter Setpoint O Yes / No  
    3.5.4.19 Configure Ground Fault Setpoint O Yes / No  
2.5.2.1.18 Retrieve Ground Fault Setpoint O Yes / No  
    3.5.4.20 Retrieve Ground Fault Setpoint O Yes / No  
2.5.2.1.19 Retrieve Ground Fault Status O Yes / No  
    3.5.4.21 Retrieve Ground Fault Status O Yes / No  
2.5.2.1.20 Configure Power Outage Message O Yes / No  
    3.5.4.22 Configure Power Outage Message O Yes / No  
2.5.2.1.21 Configure ELMS Device for Adaptive Operation O Yes / No  
    3.5.4.23 Configure ELMS Device for Adaptive Operation O Yes / No  
    3.5.4.23.1 Configure Connected Vehicle Speed Setpoint O    
    3.5.4.23.2 Configure Connected Vehicle Direction Setpoint O    
    3.5.4.23.3 Configure Connected Vehicle Location Setpoint O    
    3.5.4.23.4 Configure Connected Vehicle Ambient Light Level Setpoint O    
    3.5.4.23.5 Configure Connected Vehicle Headlight Status Setpoint O    
    3.5.4.23.6 Configure Connected Vehicle Road Friction Setpoint O    
2.5.2.1.22 Retrieve ELMS Device Adaptive Operation Configuration O Yes / No  
    3.5.4.24 Retrieve ELMS Device Adaptive Operation Configuration O Yes / No  
    3.5.4.24.1 Retrieve Connected Vehicle Speed Setpoint O    
    3.5.4.24.2 Retrieve Connected Vehicle Direction Setpoint O    
    3.5.4.24.3 Retrieve Connected Vehicle Location Setpoint O    
    3.5.4.24.4 Retrieve Connected Vehicle Ambient Light Level Setpoint O    
    3.5.4.24.5 Retrieve Connected Vehicle Headlight Status Setpoint O    
    3.5.4.24.6 Retrieve Connected Vehicle Road Friction Setpoint O    
2.5.2.2 Control Device M Yes  
2.5.2.2.1 Control Luminaire O Yes / No  
    3.5.5.1.1 Control Luminaire by Permanent/Continuou s Override M Yes  
    3.5.5.1.2 Control Luminaire by Transitory Override O Yes / No  
    3.5.5.1.3 Control Luminaire by Timed Override O Yes / No  
    3.5.5.1.4 Control Luminaire in Stagger Mode O Yes / No  
    3.5.5.1.5 Control Luminaire by Photocell O Yes / No  
    3.5.5.1.6 Control Luminaire by Adaptive Means O Yes / No  
2.5.2.2.2 Control Electrical Service O Yes / No  
    3.5.5.2.1 Control Electrical Service by Permanent/Continuou s Override M Yes  
    3.5.5.2.2 Control Electrical Service by Transitory Override O Yes / No  
    3.5.5.2.3 Control Electrical Service by Timed Override O Yes / No  
    3.5.5.2.4 Control Electrical Service in Stagger Mode O Yes / No  
    3.5.5.2.5 Control Electrical Service by Photocell O Yes / No  
    3.5.5.2.6 Control Electrical Service by Adaptive Means O Yes / No  
2.5.2.2.3 Control Branch Circuit O Yes / No  
    3.5.5.3.1 Control Branch Circuit by Permanent/Continuou s Override M Yes  
    3.5.5.3.2 Control Branch Circuit by Transitory Override O Yes / No  
    3.5.5.3.3 Control Branch Circuit by Timed Override O Yes / No  
    3.5.5.3.4 Control Branch Circuit in Stagger Mode O Yes / No  
    3.5.5.3.5 Control Branch Circuit by Photocell O Yes / No  
    3.5.5.3.6 Control Branch Circuit by Adaptive Means O Yes / No  
2.5.2.2.4 Control Electric Vehicle Charger O Yes / No  
    3.5.5.4.1 Control Soft Start O Yes / No  
    3.5.5.4.2 Control Automatic Reclosure on Fault Time O Yes / No  
    3.5.5.4.3 Control Power-up Delay Minimum Time O Yes / No  
    3.5.5.4.4 Control Power-up Delay Maximum Time O Yes / No  
    3.5.5.4.5 Control Electric Vehicle Charger Activation O Yes / No  
             
2.5.2.3 Control Devices by Zone O Yes / No  
    3.5.5.5.1 Control Devices in Zone by Permanent/Continuou s Override O Yes  
    3.5.5.5.2 Control Devices in Zone by Transitory Override O Yes / No  
    3.5.5.5.3 Control Devices in Zone by Timed Override O Yes / No  
    3.5.5.5.4 Control Devices in Zone by Photocell O Yes / No  
    3.5.5.5.5 Control Devices in Zone by Adaptive Means O Yes / No  
2.5.2.4 Monitor Device Status M Yes  
2.5.2.4.1 Monitor Luminaire O Yes / No  
    3.5.6.1.1 Retrieve Luminaire Switch Status M Yes / No  
    3.5.6.1.2 Retrieve Luminaire Temperature O Yes / No Units are in tenths of degrees Celsius
    3.5.6.1.3 Retrieve Luminaire Operating Time Statistics O Yes / No  
    3.5.6.1.4 Retrieve Luminaire Pole Status O Yes / No  
    3.5.6.1.5 Retrieve Luminaire Light Level Output O Yes / No  
    3.5.6.1.6 Retrieve Luminaire Status O Yes / No  
    3.5.6.1.7 Retrieve Luminaire Power Usage Statistics O Yes / No  
    3.5.6.1.9 Retrieve Luminaire Ballast/Driver Status O Yes / No  
    3.5.6.1.9 Retrieve Luminaire Starter Status O Yes / No  
2.5.2.4.2 Monitor Electrical Service O Yes / No  
    3.5.6.2.1 Retrieve Electrical Service Ground Fault Status O Yes / No  
    3.5.6.2.2 Retrieve Electrical Service Hours O Yes / No  
    3.5.6.2.3 Retrieve Electrical Service Operational Status M Yes  
    3.5.6.2.4 Retrieve Electrical Service Energy Readings O Yes / No  
    3.5.6.2.5 Retrieve Electrical Service Main Breaker Status O Yes / No  
    3.5.6.2.6 Retrieve Electrical Service Arc Fault Status O Yes / No  
2.5.2.4.3 Monitor Branch Circuit O Yes / No  
    3.5.6.3.1 Retrieve Branch Circuit Energy Readings O Yes / No  
    3.5.6.3.2 Retrieve Branch Circuit Arc Fault Status O Yes / No  
    3.5.6.3.3 Retrieve Branch Circuit Breaker Status O Yes / No  
    3.5.6.3.4 Retrieve Branch Circuit Operational Status M Yes  
    3.5.6.3.5 Retrieve Branch Circuit Hours O Yes / No  
    3.5.6.3.6 Retrieve Branch Circuit Ground Fault Status O Yes / No  
             
             

 

4. Reference to Other Standards

 

5. Glossary

action An element of a day plan schedule.
adaptive Allow control by inputs of schedule, astronomical clock, ambient light, and connected vehicle information.
Agency specification A document that has been prepared by an agency to define requirements for a subject item or process when procured by the agency.
ambient light level The amount of light surrounding the luminaire location.
Astronomical clock Allow control by sunrise and sunset time as calculated by latitude, longitude, and day of year.
Automated Demand Response (ADR) System functions that monitor and control the ELMS device in response to load and cost signals from the electric utility provider.
branch circuit A local electrical circuit that provides power to the luminaires.
candela An SI unit of measure for luminous intensity, abbreviated cd.
compatibility The ability of two or more systems or components to exchange information. Note: See IEEE Standards Dictionary, Glossary of Terms and Definitions, October 2008.
Compliance A condition that exists when an item meets all of the requirements of an agency specification.
Concept of Operations A document that describes the purpose for a system project, including a description of the current and proposed system, as well as key user needs that the new system is required to address.
Conformance A condition that exists when an item meets all of the mandatory requirements as defined by a standard. It can be measured on the standard as a whole, which means that it meets all mandatory (and applicable conditional) requirements of the standard or on a feature level (i.e., it conforms to feature X as defined in section X.X.X), which means that it meets all mandatory (and applicable conditional) requirements of the feature.
"connected vehicle" sensor and status information Includes vehicle, bicycle and pedestrian data objects.
consistent The ability of two or more systems or components to exchange information and use the supported information that has been exchanged and gracefully reject any unsupported information according to defined rules.
Configure The process of setting parameters within the ELMS device during installation. Note: These are typically set at time of installation and system commissioning.
Control The process of setting or resetting parameters within the ELMS device, during operation. Note: These are typically set as needed either manually or through external inputs, for example, electricity price information received automatically from the electric utility on a periodic basis.
data Elements of information exchanged between a management station and an ELMS device used to configure, control, or monitor the operation of the ELMS device.
data logger A unit that collects and stores information on the state and operation of ELMS devices.
day plan A standard device schedule element that contains a set of at least one or more actions to be performed for a device on a given day.
determine To read information from a device.
dialogs A sequence of information or message exchanges.
dim levels The setting for the intensity of the light generated by the luminaire.
download To transfer information from the central computer into the referenced field device.
electrical service The conductors and equipment for delivering electric energy from the serving utility to the wiring system of the premises served. NOTE: See National Electrical Code (NEC).
Electrical and Lighting Management Systems (ELMS) Any system capable of monitoring and controlling electrical and lighting systems using the National Transportation Communications for ITS Protocol (NTCIP).
ELMS device A device, module, or piece of equipment that 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.
ELMS management station One or more host computing platforms that controls the field devices.

Note: Management station(s) may be installed in a local Transportation Management Center (TMC), or can be field based.
feature A behavior of an ELMS device.
Informative Information that identifies a document, introduces its content, and explains its background, its development and its relationship with other documents; or information that provides additional information intended to assist the understanding or use of the document (see normative).
interchangeable A condition that exists when two or more items possess such functional and physical characteristics as to be equivalent in performance and durability, and are capable of being exchanged one for the other without alteration of the items themselves, or adjoining items, except for adjustment, and without selection for fit and performance. Note: See National Telecommunications and Information Administration, U.S. Department of Commerce
interface A named set of operations that characterizes the behavior of an element.

Note: See Unified Modeling Language specification
interoperability The ability of two or more systems or components to exchange information and use the information that has been exchanged. Note: See IEEE Standards Dictionary, Glossary of Terms and Definitions, October 2008.
live data A specific operational network configuration between a management station and the ELMS device whereby the information exchange can be performed without the need for initiating and terminating a physical network connection between a management station and ELMS device.

Note: From a network perspective, this configuration is an "always on" connection, where a management station has access to the "current" information available in the ELMS device.
location referencing message specification (LRMS) Location referencing as specified in SAE J2735 SE standard.
logged data A specific operational network configuration between a management station and the ELMS device, whereby a management station is required to execute a procedure for establishing a physical connection between a management station and the ELMS device prior to being able to exchange data with the ELMS device. Note: In this configuration, information generated by the ELMS device, which is expected to be retrieved by a management station, is stored external to a management station until such time as a management station initiates the network connection to access the stored (logged) data from the ELMS device.
lumen The unit of luminous flux emitted in a solid angle of one steradian by a uniform point source that has an intensity of one candela.
luminaire The light fixture and possibly associated sensors. Note: Luminaires may be organized into zones. Management functions can be performed on individual luminaires or on zones of luminaires (e.g., dimming).
luminance The intensity of light per unit area at its source. Usually measured in candela per square foot or candela per square meter.
lux A measurement of light. A unit of luminance produced on a surface area of one square meter by a luminous flux of one lumen uniformly distributed over the surface (1 lux = 1 lumen per square meter).
Management Information Base (MIB) A management information base (MIB) is a virtual database used for managing the entities in a communications network. Most often associated with the Simple Network Management Protocol (SNMP), the term is also used more generically in contexts such as in OSI /ISO Network management model. While intended to refer to the complete collection of management information available on an entity, it is often used to refer to a particular subset, more correctly referred to as MIB-module.

Objects in the MIB are defined using a subset of Abstract Syntax Notation One (ASN.1) called "Structure of Management Information Version 2 (SMIv2)" RFC 2578. The software that performs the parsing is an MIB compiler.

The database is hierarchical (tree-structured) and entries are addressed through object identifiers. Internet documentation RFCs discuss MIBs, notably RFC 1155, "Structure and Identification of Management Information for TCP/IP based Internets," and its two companions, RFC 1213,"Management Information Base for Network Management of TCP/IP-based internets."
Normative Information that describes the scope of the document and that sets out provisions (ISO). Normative elements are considered to be a prescriptive part of the standard (see informative).
object A data structure used to monitor or control one feature, attribute, or controllable aspect of a manageable device.
operator An individual who needs to interact with the device by either controlling or monitoring its operations.
photo sensor A light-measuring device used to quantify the ambient light conditions at the luminaire. Also referred to as photo cell or photoelectric cell.
point-to-multipoint A communications architecture that supports communications between a central system and many devices. Also called multi-drop communication.
point-to-point A communications architecture that supports dedicated communications exclusively between two devices.
pole Pole supporting a luminaire, electrical service, or branch circuit.

Note: Poles may be categorized by their constituent material types and/or design configurations.
protocol A specific set of rules, procedures, and conventions defining the format and timing of data transmissions between devices that are required to be accepted and used to understand each other.
Protocol Requirements List (PRL) A table mapping user needs with their associated requirements. This table allows procurement personnel to specify the desired features of an ELMS or can be used by a manufacturer to document the features supported by their implementation.
requirement A description of a condition or capability to which a system is obligated to conform; either derived directly from user needs, or stated in a contract, standard, specification, or other imposed document. A desired feature, property, or behavior of a system.
requirements traceability The ability to follow or study the logical progression among the needs, requirements, and design details in a step-by-step fashion.
Requirements Traceability Matrix (RTM) The table that graphically represents the logical progression among the needs, requirements, and design details.
return Data sent to the requester (in the context of device requirements for providing data requested by an external system).
schedule A mechanism by which an operator can define times in the future at which the luminaire performs actions.

Note: Refer to NTCIP 1103 v02 for information on global objects that support scheduling operations.
Simple Network Management Protocol (SNMP) Simple Network Management Protocol (SNMP) is an "Internet-standard protocol for managing devices on IP networks." Devices that typically support SNMP include routers, switches, servers, workstations, printers, modem racks, and more. [1] It is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention. SNMP is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects.[2]

SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (and sometimes set) by managing applications.
Simple Transportation Management Framework (STMF) Describes the organization of the information within devices and the methods of retrieving or modifying any information within the device. STMF also explains how to generate and use computer readable information organization descriptions.
Smart Grid device A terminal device which provides electrical load information to the utility.
SNMP agent This is a logical entity that is hosted on an ELMS device (e.g., a data logger) that manages the communications between a management station and other ELMS devices in the system.
Specification A document that specifies in a complete, precise, and verifiable manner the requirements, design, behavior, or other characteristics of a system or component, and often the procedures for determining whether these provisions have been satisfied.
stagger interval The amount of time, in seconds, between switching individual luminaires, electrical services, or branches assigned to a given branch circuit.

Note: The intent of the stagger interval is to minimize peak demand.
subfeature A specialization of a more generic feature.
Systems Engineering An interdisciplinary approach and means to enable the realization of successful systems. (INCOSE).

An interdisciplinary collaborative approach to derive, evolve, and verify a lifecycle balanced system solution, which satisfies customer expectations and meets public acceptability. (IEEE)
Traffic Management Center (TMC) The location of the central computer and equipment that allows operations staff to monitor and manage roadside lighting through field devices.
upload To transfer information from the referenced field device to the central computer, or an attached portable computer.
user A person who uses the system that is developed.
user needs The business or operational problem (opportunity) to be fulfilled to justify procurement or use.

Note: "User need," as understood within the NTCIP community, reflects needs of all stakeholders.
validate To ensure that an item of interest is as intended. For example, to ensure that the data associated with a set operation have been stored in a device without any errors.
zone A logical grouping of luminaires and/or circuits; used for control and reporting purposes.

 

6. References

Technical

Building Quality Intelligent Transportation Systems Through Systems Engineering
FHWA-OP-02-046, April 2002.
https://ntl.bts.gov/lib/jpodocs/repts_te/13620.html
Accessed March 23, 2016

Details On Acquiring Standards-Based ITS Systems, ITE PCB Module A201, 2011
https://www.pcb.its.dot.gov/standardstraining/Modules.aspx

IEEE Std 1362-1998, IEEE Guide for Information Technology - System Definition
Concept of Operations (ConOps) Document, IEEE, 1998.

Introduction to Acquiring Standards-Based ITS Systems, ITE PCB Module A101, 2011
https://www.pcb.its.dot.gov/standardstraining/Modules.aspx

Introduction to User Needs Identification, ITE PCB Module A102, 2011
https://www.pcb.its.dot.gov/standardstraining/Modules.aspx

NTCIP Guide, Information Report 9001
https://www.ntcip.org/

The NTCIP Guide, Version 04, NTCIP 9001, 2009

Object Definitions for Electrical and Lighting Management Systems, Version 2.20, NTCIP March 2011.

Recommended Practice for Software Requirements Specifications, IEEE 830, 1998.

Systems Engineering for ITS-An Introduction for Transportation Professionals, FHWA
https://ops.fhwa.dot.gov/publications/seitsguide/seguide.pdf

Systems Engineering Guidebook for Intelligent Transportation Systems, Version 3.0,
United States Department of Transportation, November 2009
https://www.fhwa.dot.gov/cadiv/segb/

Systems Engineering Guidebook, Caltrans and FHWA, February 200
http://www.dot.ca.gov/newtech/docs/se_guidebook_ver1-12_14_05.pdf

Systems Engineering Handbook, International Council on Systems Engineering (INCOSE), v3.2, 2010
http://www.incose.org/ProductsPublications/sehandbook

Systems Engineering Handbook, Version 3.2,
International Council on Systems Engineering, January 2010

The NTCIP Guide, Version 04, NTCIP 9001, 2009

US DOT ITS NTCIP 1213 ELMS V2.20
https://www.ntcip.org/library/documents/pdf/1213v0219d.pdf

US DOT ITS NTCIP 1213 ELMS V2.20 Management Information Base
https://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=1213

USDOT Standards Program
https://www.standards.its.dot.gov/

USDOT, FHWA, Freeway Operations and Management
https://ops.fhwa.dot.gov/freewaymgmt/frwy_ops.htm

USDOT, FHWA, Operations
https://ops.fhwa.dot.gov/

USDOT, RITA, ITS-JPO
https://www.its.dot.gov/index.htm (Fact sheets)

Using ITS Standards: An Overview, ITE PCB Module I101, 2011
https://www.pcb.its.dot.gov/standardstraining/Modules.aspx

Application

LED Adaptive Lighting & The Smart Grid
http://www.iaei.org/magazine/2010/11/led-adaptive-lighting-and-the-smart-grid/
The Magazine of the International Association of Electrical Inspectors
December 2010

Smart Transportation and The Smart Grid
http://www.pwmag.com/industry-news.asp?sectionID=760&articleID=1250011
Public Works Magazine, published by Hanley Wood, ISSN: 0033-3840
April 2010

Saving Energy & The Environment with New Street and Area Lighting Technology
http://www.imsasafety.org/journal/so09/20.pdf
International Municipal Signal Association Journal
September 2009

Electrical Lighting & Management Systems, Intelligent Transportation Systems & Interagency Communications
http://www.imsasafety.org/journal/nd08/7.pdf
International Municipal Signal Association Journal
November 2008

Maintaining Roadway Lighting and The Environment
http://www.imsasafety.org/journal/so08/21.pdf
International Municipal Signal Association Journal
September 2008

Saving Time, Energy & Lives Using ELMS Technology: How to Better Manage Electrical Infrastructure
http://www.imsasafety.org/journal/ja08/ja08.pdf
International Municipal Signal Association Journal
July 2008

Smart Cities: Intelligent Transportation and Smart Grid Standards for Electrical and Lighting Management Systems
http://www.imsasafety.org/
International Municipal Signal Association Journal
May 1, 2012

Smart Cities: Vehicle to Infrastructure and Adaptive Roadway Lighting Communication Standards
http://www.imsasafety.org/
International Municipal Signal Association Journal
September 1, 2012

 

7. Study Questions

These quiz/poll questions and answer choices as presented in the PowerPoint slide allow students to follow along with the recording. Three additional quiz questions are also provided to reinforce learning. See the webinar archive for answers.

1. Which of the following statement is true?

  1. NTCIP 1213 is an Information Content standard
  2. NTCIP 1213 is an Application Level standard
  3. NTCIP 1213 is a Transport Level standard
  4. NTCIP 1213 is a Plant Level Standard

2. Which of the following is not an advantage of using the systems engineering process for the ELMS NTCIP 1213 standard?

  1. Supports interoperability
  2. It allows multiple designs for each requirement
  3. Allows clear development of test procedures based on the requirements selected
  4. Determines what user needs are supported

3. Which of the following user needs cannot be satisfied by an ELMS system?

  1. Need to inform TMC manager of electrical leakage
  2. Need to control traffic flow at an intersection
  3. Need to inform TMC manager of energy usage
  4. Need to control lighting levels by dimming

4. Which of the following is a true statement?

  1. ELMS User Needs do not describe what features the device needs to support and why
  2. ELMS Functional Requirements are not specifications
  3. Within the ELMS PRL, the relationships between User Needs and Functional Requirements are not standardized
  4. The ELMS PRL promotes Interoperability

5. Which of the following descriptions of the PRL is a false statement?

  1. Options for Conformance are Mandatory or Optional
  2. Options for Project Requirements are Yes or No
  3. Optional User Needs are dependent on Project Requirements
  4. Optional Functional Requirements are not dependent on Project Requirements

6. Which of the following is a false statement?

  1. User Needs describe what features the device needs to support.
  2. Functional Requirements refine the user needs into specifications.
  3. Relationships between User Needs and Functional Requirements are standardized.
  4. The ELMS PRL does not promote interoperability.

7. Which of the following is a false statement?

  1. Vendors can provide an ELMS PRL for their standard products to show what user needs they support
  2. A completed ELMS PRL must become part of the overall specification
  3. A completed ELMS PRL indicates the requirements for the communications interface
  4. d) A completed ELMS PRL describes the entire project specification

8. Who and what can generate User Needs?

  1. People but not systems
  2. Systems but not people
  3. People and systems
  4. Neither people nor systems

Answer: C - people, including travelers, TMC operators, as well as systems can generate User Needs.

9. Which of the following organizations can integrate the PRL into a specification?

  1. Vendors
  2. Agencies
  3. Both
  4. Neither

Answer: C - Both Vendors and Agencies can use the PRL in specifications and contract documents

10. Which of the following describes the relationship between User Needs and Functional Requirements within the PRL?

  1. User Needs describe what features are required
  2. Functional Requirements refine the user needs into detailed, measurable specifications
  3. Within the PRL, the relationships between User Needs and Functional Requirements are standardized
  4. All of the above Answer: C - Within the PRL

 

8. Icon Guide

The following icons are used throughout the module to visually indicate the corresponding learning concept listed below, and/or to highlight a specific point in the training material.

1) Background information: General knowledge that is available elsewhere and is outside the module being presented. This will be used primarily in the beginning of the slide set when reviewing information readers are expected to already know.

Background information icon indicates general knowledge that is available elsewhere and is outside the module being presented.

2) Tools/Applications: An industry-specific item a person would use to accomplish a specific task, and application of that tool to fit the need.

Tools/Applications icon. An industry-specific item a person would use to accomplish a specific task, and applying that tool to fit your need.

3) Remember: Used when referencing something already discussed in the module that is necessary to recount.

Remember icon. Used when referencing something already discussed in the module that is necessary to recount.

4) Refer to Student Supplement: Items or information that are further explained/detailed in the Student Supplement.

Supplement icon indicating items or information that are further explained/detailed in the Student Supplement.

5) Example: Can be real-world (case study), hypothetical, a sample of a table, etc.

Example icon. Can be real-world (case study), hypothetical, a sample of a table, etc.

6) Checklist: Used to indicate a process that is being laid out sequentially.

Checklist icon used to indicate a process that is being laid out sequentially.