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.)

 

Cover image for A306a: Understanding User Needs for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard. Please see the Extended Text Description below.

(Extended Text Description: Large graphic cover page with dark blue background with the title in white letters “A306a: Understanding User Needs for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard” At the middle left is the “Standards ITS Training” logo with a white box and letters in blue and green. The words “Student Supplement” and “RITA Intelligent Transportation Systems Joint Program Office” in white lettering are directly underneath the logo. Three light blue lines move diagonally across the middle of the blue background.)

A306a:

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

 

Table of Contents

Introduction/Purpose - 2

Basic Overview - 2

History - 3

Compatibility of Versions - 4

Complete ELMS PRL - 5

Glossary - 9

References - 11

Study Questions - 13

 

Module Description

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

Module A306a will provide participants with information on how to identify the appropriate use of the NTCIP 1213 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).

 

1. Introduction/Purpose

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 ELMS systems. This module is to be placed in the context of the SEP as well as in the acquisition curriculum path with I101, A101, A102, and A201. C101 and C201 are the prerequisites and A306b-Specifying Requirements for ELMS Systems Based on NTCIP 1213 Standard follows this module.

This participant supplement provides:

 

2. Basic Overview

NTCIP 1213 v02 defines the generic reference model and conformance requirements for traffic management centers (TMCs) that wish to provide interfaces to field devices. NTCIP 1213 v02 defines requirements that are applicable to all NTCIP TMCs, and contains optional and conditional sections that are applicable to specific environments for which they are intended. NTCIP 1213 v02 defines the ELMS data element objects that are supported by the NTCIP. 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 of 2001 (Report FHWA-PL-01-034, 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 titled 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 v02 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 v02 is an NTCIP Device Data Dictionary Standard. Device Data Dictionaries Standards define management information in terms of objects (data elements, data frames, and messages) for use within NTCIP systems.

 

3. 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 purpose 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 WG 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 MIB object definitions (astronomical clock).

November 2010—incorporated compliable 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.

 

4. Compatibility of Versions

To distinguish NTCIP 1213 v02 (as published) from previous drafts, NTCIP 1213 v02 also includes NTCIP 1213 v02.20 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 to them in any given circumstance. The MIB, the PRL, and the PICS 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 ELMS into one of three major categories:

  1. Power Control and Monitoring - this type of ELMS primarily address 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.

 

5. Complete ELMS PRL

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.4.1

Operational User Needs

M

Yes

 

2.4.1.1

Provide Live Data

M

Yes

 

 

 

3.3 1.1

Retrieve Data

M

Yes

 

 

 

3.3.1.2

Deliver Data

M

Yes

 

 

 

3.3.1.3

Data Retrieval and Data Delivery Action Performance

M

Yes

 

 

 

3.5.5.1

Live Data Response Time

M

Yes

 

2.4.1.2

Provide Off-line Log Data

O

Yes / No

 

 

 

3.3.2.1

Retrieve Configuration of Logging service

M

Yes

 

 

 

3.3.2.2

Configure Logging Service

M

Yes

 

 

 

3.3.2.4

Clear Log

M

Yes

 

 

 

3.3.2.5

Retrieve Capabilities of Event Logging Services

M

Yes

 

 

 

3.3.2.6

Retrieve Number of Events Currently Logged

M

Yes

 

 

 

3.3.2.7

Set Time

M

Yes

 

 

 

3.3.2.8

Retrieve Current Time

M

Yes

 

 

 

3.3.2.9

Set Daylight Saving Time Mode

M

Yes

 

 

 

3.3.2.10

ELMS Pre-defined Event Configurations

M

Yes

 

 

 

3.3.2.10.1

Supported Event Classes

M

Yes

 

 

 

3.5.4

Supplemental Requirements for Event Logs

M

Yes

 

2.4.1.2.1

Provide Luminaire Switch State Logging

O

Yes / No

 

 

 

3.3.2.10.2

Luminaire Switch State Log

O

Yes / No

 

2.4.1.2.2

Provide Luminaire Lamp Condition Logging

O

Yes / No

 

 

 

3.3.2.10.3

Luminaire Lamp Condition Log

O

Yes / No

 

2.4.1.2.3

Provide Luminaire Burn Condition Logging

O

Yes / No

 

 

 

3.3.2.10.4

Luminaire Bum Condition Log

O

Yes / No

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.4.1.2.4

Provide Periodic Luminaire Burn Time Logging

O

Yes / No

 

 

 

3.3.2.10.5

Periodic Luminaire Bum Time Log

O

Yes / No

 

2.4.1.2.5

Provide Luminaire Temperature Logging

O

Yes / No

 

 

 

3.3.2.10.6

Luminaire Temperature Log

O

Yes / No

 

2.4.1.2.6

Provide Luminaire Pole Condition Logging

O

Yes / No

 

 

 

3.32.10.7

Luminaire Pole Condition Log

O

Yes / No

 

2.4.1.2.7

Provide Relay Switch State Logging

O

Yes / No

 

 

 

3.3.2.10.3

Relay Switch State Log

O

Yes / No

 

2.4.1.2.8

Provide Power Meter Switch State Logging

O

Yes / No

 

 

 

3.32.10.9

Power Meter Switch State Log

O

Yes / No

 

2.4.1.2.9

Provide Periodic Power Meter Measurement Logging

O

Yes / No

 

 

 

3.3.2.10.10

Periodic Power Meter Measurement Log

O

Yes / No

 

2.4.1.2.10

Provide Power Meter Condition Logging

O

Yes / No

 

 

 

3.3.2.10.11

Power Meter Condition Log

O

Yes / No

 

2.4.1.2.11

Provide Ground Fault Switch State Logging

O

Yes / No

 

 

 

3.3.2.10.12

Ground Fault Switch State Log

O

Yes / No

 

2.4.1.2.12

Provide Periodic Ground Fault Measurement Logging

O

Yes / No

 

 

 

3.3.2.10.13

Periodic Ground Fault Measurement Log

O

Yes / No

 

2.4.1.2.13

Retrieve Logged Data

M

Yes

 

 

  3.3.2.3 Retrieve Logged Data

M

Yes

 

2.4.1.3

Monitor Exceptional Conditions

O

Yes / No

 

 

 

3.3.3.1

Retrieve Current Configuration of Exception Reporting Service

M

Yes

 

 

 

3.3.3.2

Configure Events

M

Yes

 

 

 

3.3.3.3

Provide Automatic Reporting of Events (SNMP Traps)

M

Yes

 

 

 

3.3.3.4

Manage Exception Reporting

M

Yes

 

 

 

3.3.3.5

Retrieve Capabilities of Exception Reporting Service

M

Yes

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

 

 

3.3.3.6

Retrieve Current Number of Exception Events

M

Yes

 

 

 

3.3.3.7

Record and Timestamp Events

M

Yes

 

2.4.2

Features

M

Yes

 

2.42.1

Configure ELMS Device

M

Yes

 

2.4.2.1.1

Configure Luminaire

M

Yes

 

2.4 2.1.1.1

Retrieve Luminaire Information

M

Yes

 

 

 

3.4 1.1.1.1

Retrieve Luminaire Pole Identifier

O

Yes / No

 

 

 

3.4.1.1.1.2

Retrieve Luminaire Location

M

Yes

 

 

 

3.4.1.1.1.3

Retrieve Luminaire Mode

M

Yes

 

 

 

3.4.1.1.1.4

Retrieve Luminaire Zone

O

Yes / No

 

 

 

3.4.1.1.1.5

Retrieve Luminaire Vendor Information

M

Yes

 

2.4.2.1.1.2

Configure Luminaire Identification Information

M

Yes

 

 

 

3.4.1.1.1.2.1

Specify Location in Longitude/Latitude Coordinates

O

Yes / No

 

 

 

3.4.1.1.1.2.2

Specify Location Information Using Textual Description of a Road/Street/Block Name/Number

M

Yes

The ELMS device shall support a location name of at least _____ (8..255) Characters.

 

 

3.4.1.1.1.2.3

Specify Location in local reference coordinate grid

O

Yes / No

 

 

 

3.4.1.1.2.1

Configure Luminaire Pole Identifier

O

Yes / No

 

 

 

3.4.1.1.2.2

Configure Luminaire Location

M

Yes

 

2.4.2.1.1.3

Configure Luminaire Mode

M

Yes

 

 

 

3.4.1.1.3

Configure Luminaire Mode

M

Yes

 

2.4.2.1 2

Configure Electrical Service

O

Yes

 

2.4.2.1 2.1

Retrieve Electrical Service Information

O

Yes / No

 

 

 

3.4.1.2.1.1

Retrieve Electrical Service Location

M

Yes

 

 

 

3.4.1.2.1.2

Retrieve Electrical Service Zone

O

Yes / No

 

 

 

3.4.1.2.1.3

Retrieve Electrical Service Pole Identifier

O

Yes / No

 

 

 

3.4.1.2.2.1

Configure Electrical Service Location

M

Yes

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

 

 

3.4.1.2.2.2

Configure Electrical Service Pole Identifier

O

Yes / No

 

2.4.2.1.3

Configure for Light-Activated Operation

O

Yes / No

 

 

 

3.4.1.3.1

Configure Luminaire for Light Activated Operations

M

Yes

 

 

 

3.4.1.3.2

Configure Electrical Service for Light Activated Operations

O

Yes / No

 

 

 

3.4.1.3.3

Configure Branch Circuit for Light Activated Operations

O

Yes / No

 

 

 

3.4.1.3.4

Configure Devices in Zone for Light Activated

Operations

O

Yes / No

 

2.4 2.1 4

Configure for Scheduled Operation

O

Yes / No

 

 

 

3.4.1.4.1

Configure Luminaire for Scheduled Operations

O.1 (1..*)

Yes / No

 

 

 

3.4.1.4.2

Configure Electrical Service for Scheduled Operations

O.2 (1..*)

Yes / No

 

 

 

3.4.1.4.3

Configure Branch Circuit for Scheduled

Operations

O.3 (1..*)

Yes / No

 

 

 

3.4.1.4.4.

Configure Devices in Zone for Scheduled

Operations

O.4 (1..*)

Yes / No

 

 

 

3.4.1.4.5

Schedule ELMS Device Event

M

Yes

 

 

 

3.4.1.4.6

Retrieve a Schedule

M

Yes

 

 

 

3.5.1

Supplemental Requirements for Scheduled Operations

M

Yes

 

2.4.2.1.5

Configure Zones

O

Yes / No

 

 

 

3.4.1.5.1

Configure Luminaire Zone

M

Yes

 

 

 

3.4.1.5.2

Configure Electrical Service Zone

O

Yes / No

 

 

 

3.4.1.5.3

Configure Branch Circuit Zone

O

Yes / No

 

 

 

3.4.1.5.4

Define Zones

M

Yes

 

 

 

3.5.2

Supplemental Requirements for Zones

M

Yes

 

2.4.2.1.6

Configure for Manual Operation

M

Yes

 

 

 

3.4.1.8.1

Configure Luminaire for Manual Operation

M

Yes

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

 

 

3.4.1.8.2

Configure Electrical Service for Manual Operations

O

Yes / No

 

 

 

3.4.1.8.3

Configure Branch Circuit far Manual

Operations

O

Yes / No

 

 

 

3.4.1.8.4

Configure Devices in Zone for Manual Operations

O

Yes / No

 

2.4.2.1.7

Configure Stagger Interval

O

Yes / No

 

 

 

3.4.1.6.1

Configure Luminaire Stagger Interval

M

Yes

The ELMS device shall support a stagger interval with a maximum value of _____ (O..255) seconds.

 

 

3.4.1.6.2

Configure Branch Circuit Stagger Interval

O

Yes / No

The ELMS device shall support a stagger interval with a maximum value of _____ (O..255) seconds.

2.4.2.1.8

Configure Dim Levels

O

Yes / No

 

 

 

3.4.1.7.1

Configure Luminaire Dim Level

M

Yes

 

 

 

3.4.1.7.2

Configure Electrical Service Dim Level

O

Yes / No

 

 

 

3.4.1.7.3

Configure Branch Circuit Dim Level

O

Yes / No

 

 

 

3.4.1.7.4

Configure Dim Level for Devices in Zone

O

Yes / No

 

 

 

3.5.3

Supplemental Requirements for Dim Levels

M

Yes

 

2.4 2.1 9

Configure Electrical Service Monitoring and Metering Equipment

O

Yes / No

 

 

 

3.4.1.9.1

Configure Branch Circuit Ground Fault Detector

O

Yes / No

 

 

 

3.4.1.9.2

Configure Branch Circuit Power Meter

O

Yes / No

 

 

 

3.4.1.9.3

Configure Branch Circuit Arc Fault Detector

O

Yes / No

 

2.4.2.1.10

Configure Branch Circuit

O

Yes / No

 

2.4.2.1.10.1

Retrieve Branch Circuit Information

O

Yes / No

 

 

 

3.4.1.10.1.1

Retrieve Branch Circuit Zone

O

Yes / No

 

 

 

3.4.1.10.1.2

Retrieve Branch Circuit Location

O

Yes / No

 

 

 

3.4.1.10.1.3

Retrieve Branch Circuit Pole Identifier

O

Yes / No

 

2.4.2.1.10.2

Configure Branch Circuit

O

Yes / No

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

 

 

3.4.1.10.2.1

Configure Branch Circuit Location

O

Yes / No

 

 

 

3.4.1.10.2.2

Configure Branch Circuit Pole Identifier

O

Yes / No

 

2.4.2.2

Control Device

M

Yes

 

2.4.2.2.1

Control Luminaire

M

Yes

 

 

 

3.4.2.1.1

Control Luminaire by Permanent/Continuous Override

M

Yes

 

 

 

3.4.2.1.2

Control Luminaire by Transitory Override

O

Yes / No

 

 

 

3.4.2.1.3

Control Luminaire by Timed Override

O

Yes / No

 

 

 

3.4.2.1 4

Control Luminaire in Stagger Mode

O

Yes / No

 

2.4.2.2.2

Control Electrical Service

O

Yes / No

 

 

 

3.4.2.2.1

Control Electrical Service by Permanent/Continuous Override

M

Yes

 

 

 

3.4.2.2.2

Control Electrical Service by Transitory Override

O

Yes / No

 

 

 

3.4.2.2.3

Control Electrical Service by Timed Override

O

Yes / No

 

 

 

3.4.2.3.4

Control Electrical Service in Stagger Mode

O

Yes / No

 

2.4.2.2.3

Control Branch Circuit

O

Yes / No

 

 

 

3.4.2.3.1

Control Branch Circuit by Permanent/Continuous Override

M

Yes

 

 

 

3.4.2.3.2

Control Branch Circuit by Transitory Override

O

Yes / No

 

 

 

3.4.2.3.3

Control Branch Circuit by Timed Override

O

Yes / No

 

 

 

3.4.2.3.4

Control Branch Circuit in Stagger Made

O

Yes / No

 

2.4.2.3

Control Devices by Zone

O

Yes / No

 

 

 

3.4.2.4.1

Control Devices in Zone by Permanent/Continuous Override

M

Yes

 

 

 

3.4.2.4.2

Control Devices in Zone by Transitory Override

O

Yes / No

 

 

 

3.4.2.4.3

Control Devices in Zone by Timed Override

O

Yes / No

 

2.4.2.4

Monitor Device Status

M

Yes

 

2.4.2.4.1

Monitor Luminaire

M

Yes

 

 

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

 

 

3.4.3.1.1

Retrieve Luminaire Switch Status

M

Yes

 

 

 

3.4.3.1 2

Retrieve Luminaire Temperature

O

Yes / No

Units are in tenths of degrees Celsius

 

 

3.4.3.1.3

Retrieve Luminaire Burn Time Statistics

O

Yes / No

 

 

 

3.4.3.1.4

Retrieve Luminaire Pole Status

O

Yes / No

 

 

 

3.4.3.1.5

Retrieve Luminaire Dimming Level Output

O

Yes / No

 

 

 

3.4.3.1 6

Retrieve Luminaire Lamp Status

O

Yes / No

 

 

 

3.4.3.1.7

Retrieve Luminaire Power Usage Statistics

O

Yes / No

 

 

 

3.4.3.1.3

Retrieve Luminaire Ballast Status

O

Yes / No

 

 

 

3.4.3.1.8

Retrieve Luminaire Starter Status

O

Yes / No

 

2.4.2.4.2

Monitor Electrical Service

O

Yes / No

 

 

 

3.4.3.2.1

Retrieve Electrical Service Ground Fault Status

O

Yes / No

 

 

 

3.4.3.2.2

Retrieve Electrical Service Hours

O

Yes / No

 

 

 

3.4.3.2.3

Retrieve Electrical Service Operational Status

M

Yes

 

 

 

3.4.3.2.4

Retrieve Electrical Service Power Readings

O

Yes / No

 

 

 

3.4.3.2.5

Retrieve Electrical Service Main Breaker Status

O

Yes / No

 

 

 

3.4.3.2.6

Retrieve Electrical Service Arc Fault Status

O

Yes / No

 

2.4.2.4.3

Monitor Branch Circuit

O

Yes / No

 

 

 

3.4.3.3.1

Retrieve Branch Circuit Power Readings

O

Yes / No

 

 

 

3.4.3.3.2

Retrieve Branch Circuit Arc Fault Status

O

Yes / No

 

 

 

3.4.3.3.3

Retrieve Branch Circuit Breaker Status

O

Yes / No

 

 

 

3.4.3.3.4

Retrieve Branch Circuit Operational Status

M

Yes

 

 

 

3.4.3.3.5

Retrieve Branch Circuit Hours

O

Yes / No

 

 

 

3.4.3.3.6

Retrieve Branch Circuit Ground Fault Status

O

Yes / No

 

 

Supplemental Requirement ID

Supplemental Requirement

Conformance

Project Requirement

Additional Project Requirements

3.5

Supplemental Requirements

M

Yes

 

3.5.1

Supplemental Requirements for Scheduled Operations

M

Yes

 

3.5.1.1

Support a Number of Actions

M

Yes

The ELMS Device shall support at least _____ (1..255) Actions.

3.5.1.2

Support a Number of Day Plans

M

Yes

The ELMS Device shall support at least _____ (1..255) Day Plans.

3.5.1.3

Perform Action at Scheduled Time

M

Yes

 

3.5.2

Supplemental Requirements for Zones

M

Yes

 

3.5.2.1

Define Number of Zones Supported by an ELMS Device

O

Yes / No

The ELMS Device shall support at least _____ (0..65535) Zones.

3.5.2.2

Define Number of ELMS Devices for a Zone

O

Yes / No

At least _____ (0..65535) ELMS devices shall be able to be assigned to a single zone.

3.5.3

Supplemental Requirements for Dim Levels

M

Yes

 

3.5.3.1

Define Dim Levels as a percentage of maximum brightness

O

Yes / No

 

3.5.4

Supplemental Requirements for Event Logs

M

Yes

 

3.5.4.1

Configure Number of Events in Event Log

O

Yes / No

The ELMS device shall support at least _____ (1..255) events.

3.5.4.2

Configure Number of Event Classes

O

Yes / No

The ELMS device shall support at least _____ (1..255) classes.

3.5.4.3

Configure Number of Event Types

O

Yes / No

The ELMS device shall support at least _____ (1..255) event types.

 

Supplemental Requirement ID

Supplemental Requirement

Conformance

Project Requirement

Additional Project Requirements

3.5.5

Supplemental Requirements for Live Data

M

Yes

 

3.5.5.1

Live Data Response Time

M

Yes

The device shall initiate the transmission of the appropriate response (assuming that the device has permission to transmit) within _____ millisecond(s) of receiving the last byte of the request, plus 1 millisecond for each byte in the response variable-bindings field

 

6. Glossary

The following is a Glossary of Terms used throughout the module:

Term

Definition

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.

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.

Dialogs

A sequence of information or message exchanges.

ELMS

Electrical and Lighting Management Systems.

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).

Interchangeability

A condition which 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.

Interoperability

The ability of two or more systems or components to exchange information and use the information that has been exchanged.

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 a MIB compiler.

The database is hierarchical (tree-structured) and entries are addressed through object identifiers. Internet documentation RFCs discusses 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).

Protocol Requirements List (PRL)

A table mapping user needs with its associated requirements. This table allows procurement personnel to specify the desired features of an ELM or can be used by a manufacturer to document the features supported by their implementation.

Requirement

A condition or capability needed by a user to solve a problem or achieve an objective.

Requirements Traceability Matrix (RTM)

A table that links the requirements to the corresponding dialogs and objects.

SNMP/Simple Network Management Protocol

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." 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.

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.

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.

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)

User Needs

The business or operational problem (opportunity) that is to be fulfilled to justify procurement or use.

NOTE—While this is termed a "user need" within the NTCIP community, it reflects needs of all stakeholders.

 

7. References

Building Quality Intelligent Transportation Systems Through Systems Engineering, FHWA-OP-02-046, April 2002. http://ntl.bts.gov/lib/jpodocs/repts te/13620.html

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

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

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. http://www.pcb.its.dot.gov/standardstraining/Modules.aspx

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

"LED Adaptive Lighting and the Smart Grid," Magazine of the International Association of Electrical Inspectors, December 2010. http://iaeimagazine.org/magazine/2010/11/16/led-adaptive-lighting-and-the-smart-grid/

"Maintaining Roadway Lighting and the Environment," IMSA Journal, September 2008. http://www.imsasafety.org/journal/so08/21.pdf

NTCIP Guide, Information Report 9001, Object Definitions for Electrical and Lighting Management Systems, Version 2.20, NTCIP, March 2011. https://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=9001

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

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

"Saving Energy & the Environment with New Street and Area Lighting Technology," IMSA Journal, September 2009. http://www.imsasafety.org/journal/so09/20.pdf

"Saving Time Energy & Lives Using ELMS Technology: How To Better Manage Electrical Infrastructure," IMSA Journal, July 2008. http://www.imsasafety.org/journal/so08/21.pdf

"Smart Cities: Intelligent Transportation and Smart Grid Standards for Electrical and Lighting Management Systems," IMSA Journal, May 2012.

"Smart Cities: Vehicles to Infrastructure and Adaptive Roadway Lighting Communication Standards," IMSA Journal, September 2012.

"Smart Transportation and the Smart Grid," Public Works Magazine, Hanley Wood, ISSN: 0033-3840, April 2010. http://www.pwmag.com/traffic-control/-smart--transportation-and-the-smart-grid.aspx

Systems Engineering for ITS-An Introduction for Transportation Professionals, FHWA. http://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. http://www.fhwa.dot.gov/cadiv/segb/

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

USDOT ITS NTCIP 1213 ELMS V2.20 http://www.ntcip.org/library/documents/pdf/1213v0219d.pdf

USDOT ITS NTCIP 1213 ELMS V2.20 Management Information Base http://www.ntcip.org

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

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

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

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

"Using ITS Standards: An Overview," http://www.pcb.its.dot.gov/

 

8. Study Questions

The presentation for this module includes a sample scenario and several quiz questions, which are presented here for easy reference. The answers to the questions are provided in the online presentation.

Question 1: Which of the following statements is true?

Answer Choices

  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

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

Answer Choices

  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

Question 3: Which of the following user needs cannot be satisfied by an ELMS system? Answer Choices

  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

Question 4: Which of the following is a true statement? Answer Choices

  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.

Question 5: Which of the following descriptions of the PRL is a false statement? Answer Choices

  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.

Question 6: Which of the following is a false statement? Answer Choices

  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.

Question 7: Which of the following is a false statement? Answer Choices

  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. A completed ELMS PRL describes the entire project specification.