Module 27 - A306b

A306b: Specifying Requirements 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 A306b: Specifying Requirements 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 "A306b: Specifying Requirements 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.)

 

A306b: Specifying Requirements for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard

 

Table of Contents

Introduction/Purpose - 2

ELMS Protocol Requirements List - 3

Sample Project Completed ELMS PRL - 7

Specification Text - 11

References to Other Standards - 13

Glossary - 13

References - 16

Study Questions - 19

 

Module Description

This is the final module of the acquisition curriculum path to procure Electrical and Lighting Management Systems with I101, A101, A102, A201, C101, and A306a being the prerequisites. The logical next step for the participant after taking this module is to consider modules in the testing life cycle, which are T101, T201, and T202, which lead up to the potential T306 Applying Your Test Plan to the NTCIP 1213 ELMS Standard.

 

1. Introduction/Purpose

This module provides participants with information on how to identify their user needs for an ELMS. An ELMS is used to control, monitor and manage field deployed electrical and lighting infrastructure.

ELMS user need and requirement identification is based on what the user is seeking to accomplish; this task has been simplified with the introduction of a standardized Concept of Operations as documented in NTCIP 1213, which follows the Systems Engineering Process (SEP). This document provides the user with a Protocol Requirements List (PRL), which provides an easy checklist of all user needs and requirements and can be included in procurement specifications.

 

2. 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 0 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.6.4 Supplemental Requirements for Event Logs M Yes  
2.4.1.2.1 Provide Luminal re Switch State Logging 0 Yes / No  
    3.3.2.10.2 Luminaire Switch State Log 0 Yes / No  
2.4.1.2.2 Provide Luminaire Lamp Condition Logging 0 Yes / No  
    3.3.2.10.3 Luminaire Lamp Condition Log 0 Yes / No  
2.4.1.2.3 Provide Luminaire Burn Condition Logging 0 Yes / No  
    3.3.2.10.4 Luminaire Burn Condition Log 0 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 0 Yes / No  
    3.3.2.10.6 Periodic Luminaire Burn Time Log 0 Yes / No  
2.4.1.2.5 Provide Luminaire Temperature Logging 0 Yes / No  
    3.3.2.10.6 Luminaire Temperature Log 0 Yes / No  
2.4.1.2.6 Provide Luminaire Pole Condition Logging 0 Yes / No  
    3.3.2.10.7 Luminaire Pole Condition Log 0 Yes / No  
2.4.1.2.7 Provide Relay Switch State Logging 0 Yes / No  
    3.3.2.10.8 Relay Switch State Log 0 Yes / No  
2.4.1.2.8 Provide Power Meter Switch State Logging 0 Yes / No  
    3.3.2.10.9 Power Meter Switch State Log 0 Yes / No  
2.4.1.2.9 Provide Periodic Power Meter Measurement Logging 0 Yes / No  
    3.3.2.10.10 Periodic Power Meter Measurement Log 0 Yes / No  
2.4.1.2.10 Provide Power Meter Condition Logging 0 Yes / No  
    3.3.2.10.11 Power Meter Condiion Log 0 Yes / No  
2.4.1.2.11 Provide Ground Fault Switch State Logging 0 Yes / No  
    3.3.2.10.12 Ground Fault Switch State Log 0 Yes / No  
2.4.1.2.12 Provide Periodic Ground Fault Measurement Logging 0 Yes / No  
    3.3.2.10.13 Periodic Ground Fault Measurement Log 0 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 0 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.4.2.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 0 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 0 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 0 Yes / No  
    3.4.1.1.1.2.2 Specify Location Information Using Textual Description of a Road/StreetfBlock 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 0 Yes / No  
    3.4.1.1.2.1 Configure Luminaire Pole Identifier 0 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 Made M Yes  
2.4.2.1.2 Configure Electrical Service 0 Yes  
2.4 2.1 2.1 Retrieve Electrical Service Information 0 Yes / No  
    3.4.1.2.1.1 Retrieve Electrical Service Location M Yes  
    3.4.1.2.1.2 Retrieve Electrical Service Zone 0 Yes / No  
    3.4.1.2.1.3 Retrieve Electrical Service Pole Identifier 0 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 0 Yes / No  
2.4.2.1.3 Configure for Light-Activated Operation 0 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 0 Yes / No  
    3.4.1.3.3 Configure Branch Circuit for Light Activated Operations 0 Yes / No  
    3.4.1.3.4 Configure Devices in Zone for Light Activated Operations 0 Yes / No  
2.4.2.1.4 Configure for Scheduled Operation 0 Yes / No  
    3.4.1.4.1 Configure Luminaire for Scheduled Operations 0.1 (1..*) Yes / No  
    3.4.1.4.2 Configure Electrical Service for Scheduled Operations 0.2 (1..*) Yes / No  
    3.4.1.4.3. Configure Branch Circuit for Scheduled Operations 0.3 (1..*) Yes / No  
    3.4.1.4.4. Configure Devices in Zone for Scheduled Operations 0.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 0 Yes / No  
    3.4.1.5.1 Configure Luminaire Zone M Yes  
    3.4.1.5.2 Configure Electrical Service Zone 0 Yes / No  
    3.4.1.5.3 Configure Branch Circuit Zone 0 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.5.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 0 Yes / No  
    3.4.1.8 3 Configure Branch Circuit for Manual Operations 0 Yes / No  
    3.4.1.8.4 Configure Devices in Zone for Manual Operations 0 Yes / No  
2.4.2.1.7 Configure Stagger Interval 0 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 ___ (0..255) seconds.
    3.4.1.6.2 Configure Branch Circuit Stagger Interval 0 Yes / No The ELMS device shall support a stagger interval with a maximum value of ___ (0..255) seconds.
2.4.2.1.8 Configure Dim Levels 0 Yes / No  
    3.4.1.7.1 Configure Luminaire Dim Level M Yes  
    3.4.1.7 2 Configure Electrical Service Dim Level 0 Yes / No  
    3.4.1.7.3 Configure Branch Circuit Dim Level 0 Yes / No  
    3.4.1.7 4 Conf gure Dim Level for Devices in Zone 0 Yes / No  
    3.5.3 Supplemental Requirements for Dim Levels M Yes  
2.4.2.1.9 Configure Electrical Service Monitoring and Metering Equipment 0 Yes / No  
    3.4.1.9.1 Configure Branch Circuit Ground Fault Detector 0 Yes / No  
    3.4 1.9 2 Configure Branch Circuit Power Meter 0 Yes / No  
    3.4 1.9.3 Configure Branch Circuit Arc Fault Detector 0 Yes / No  
2.4.2.1.10 Configure Branch Circuit 0 Yes / No  
2.4.2.1.10.1 Retrieve Branch Circuit Information 0 Yes / No  
    3.4.1.10.1.1 Retrieve Branch Circuit Zone 0 Yes / No  
    3.4.1.10.1.2 Retrieve Branch Circuit Location 0 Yes / No  
    3.4.1.10.1.3 Retrieve Branch Circuit Pole Identifier 0 Yes / No  
2.4.2.1.10.2 Configure Branch Circuit 0 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 0 Yes / No  
    3.4.1.10.2.2 Configure Branch Circuit Pole Identifier 0 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 0 Yes / No  
    3.4.2.1.3 Control Luminaire by Timed Override 0 Yes / No  
    3.4 2.1.4 Control Luminaire in Stagger Mode 0 Yes / No  
2.4.2.2.2 Control Electrical Service 0 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 0 Yes / No  
    3.4.2.2.3 Control Electrical Service by Timed Override 0 Yes / No  
    3.4.2.3.4 Control Electrical Service in Stagger Mode 0 Yes / No  
2.4.2.2.3 Control Branch Circuit 0 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 0 Yes / No  
    3.4.2.3.3 Control Branch Circuit by Timed Override 0 Yes / No  
    3.4.2.3.4 Control Branch Circuit in Stagger Mode 0 Yes / No  
2.4.2.3 Control Devices by Zone 0 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 0 Yes / No  
    3.4.2.4.3 Control Devices in Zone by Timed Override 0 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 0 Yes / No Units are in tenths of degrees Celsius
    3.4 3.1.3 Retrieve Luminaire Burn Time Statistics 0 Yes / No  
    3.4.3.1.4 Retrieve Luminaire Pole Status 0 Yes / No  
    3.4.3.1.5 Retrieve Luminaire Dimming Level Output 0 Yes / No  
    3.4 3.1.6 Retrieve Luminaire Lamp Status 0 Yes / No  
    3.4.3.1.7 Retrieve Luminaire Power Usage Statistics 0 Yes / No  
    3.4.3.1.8 Retrieve Luminaire Ballast Status 0 Yes / No  
    3.4.3.1.9 Retrieve Luminaire Starter Status 0 Yes / No  
2.4.2.4.2 Monitor Electrical Service 0 Yes / No  
    3.4.3.2.1 Retrieve Electrical Service Ground Fault Status 0 Yes / No  
    3.4.3.2.2 Retrieve Electrical Service Hours 0 Yes / No  
    3.4.3.2.3 Retrieve Electrical Service Operational Status M Yes  
    3.4.3.2.4 Retrieve Electrical Service Power Readings 0 Yes / No  
    3.4.3.2.5 Retrieve Electrical Service Main Breaker Status 0 Yes / No  
    3.4.3.2.6 Retrieve Electrical Service Arc Fault Status 0 Yes / No  
2.4.2.4.3 Monitor Branch Circuit 0 Yes / No  
    3.4.3.3.1 Retrieve Branch Circuit Power Readings 0 Yes / No  
    3.4.3.3.2 Retrieve Branch Circuit Arc Fault Status 0 Yes / No  
    3.4.3.3.3 Retrieve Branch Circuit Breaker Status 0 Yes / No  
    3.4.3.3.4 Retrieve Branch Circuit Operational Status M Yes  
    3.4.3.3.5 Retrieve Branch Circuit Hours 0 Yes / No  
    3.4.3.3.6 Retrieve Branch Circuit Ground Fault Status 0 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 0 Yes / No The ELMS Device shall support at least ___ (0..66536) Zones.
3.5.2.2 Define Number of ELMS Devices for a Zone 0 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 0 Yes / No  
3.5.4 Supplemental Requirements for Event Logs M Yes  
3.5.4.1 Configure Number of Events in Event Log 0 Yes / No The ELMS device shall support at least ___ (1..255) events.
3.5.4.2 Configure Number of Event Classes 0 Yes / No The ELMS device shall support at least ___ (1..255) classes.
3.5.4.3 Configure Number of Event Types 0 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 receivinq the last byte of the request, plus 1 millisecond for each byte in the response variable-bindings field

 

3. Completed ELMS PRL as described in A306b Sample Project

Image of a table. Please see the Extended Text Description below.

(Extended Text Description: This is an excerpt of the ELMS PRL table listed above in section 2. ELMS PRL. The range of rows in this table from the ELMS PRL table starts at 2.4.1 and ends at 3.3.3.5. The only differences between this table and the source ELMS PRL table is that this table is a completed ELMS PRL table as described in A306b Sample Project, with certain elements highlighted as described below. Please see 2. ELMS PRL for the full table data. The table data that is highlighted in this sample project includes the following: The "Yes" in the "Yes / No" cells of rows 2.4.1.2 and 2.4.1.3 are circled. The "No" in the "Yes / No" cells of rows 2.4.1.2.1, 2.4.1.2.2, 2.4.1.2.3, 2.4.1.2.4, 2.4.1.2.5, 2.4.1.2.6, 2.4.1.2.7, 2.4.1.2.8, 2.4.1.2.9, 2.4.1.2.10, 2.4.1.2.11 and 2.4.1.2.12 are circled.)

 

Image of a table. Please see the Extended Text Description below.

(Extended Text Description: This is an excerpt of the ELMS PRL table listed above in section 2. ELMS PRL. The range of rows in this table from the ELMS PRL table starts at 3.3.3.6 and ends at 3.4.1.8.1. The only differences between this table and the source ELMS PRL table is that this table is a completed ELMS PRL table as described in A306b Sample Project, with certain elements highlighted as described below. Please see 2. ELMS PRL for the full table data. The table data that is highlighted in this sample project includes the following: The "Yes" in the "Yes / No" cells of rows 2.4.2.1.2, 2.4.2.1.3, 3.4.1.3.3, 3.4.1.3.4, 2.4.2.1.4, 3.4.1.4.3, 3.4.1.4.4, 2.4.2.1.5 and 3.4.1.5.3 are circled. The "No" in the "Yes / No" cells of rows 3.4.1.1.1.1, 3.4.1.1.1.4, 3.4.1.1.1.2.1, 3.4.1.1.1.2.3, 3.4.1.1.2.1, 2.4 2.1 2.1, 3.4.1.3.2, 3.4.1.4.1, 3.4.1.4.2 and 3.4.1.5.2 are circled. The following number is filled into the blank for the Additional Project Requirements cell of the following row (row: data): 3.4.1.1.1.2.2: 255.)

 

Image of a table. Please see the Extended Text Description below.

(Extended Text Description: This is an excerpt of the ELMS PRL table listed above in section 2. ELMS PRL. The range of rows in this table from the ELMS PRL table starts at 3.4.1.8.2 and ends at 2.4.2.4.1. The only differences between this table and the source ELMS PRL table is that this table is a completed ELMS PRL table as described in A306b Sample Project, with certain elements highlighted as described below. Please see 2. ELMS PRL for the full table data. The table data that is highlighted in this sample project includes the following: The "Yes" in the "Yes / No" cells of rows 3.4.1.8 3, 3.4.1.8 4, 2.4.2.1.10, 2.4.2.1.10.1, 3.4.1.10.1.1, 3.4.1.10.1.2, 3.4.1.10.1.3, 2.4.2.1.10.2, 3.4.1.10.2.1, 3.4.1.10.2.2, 2.4.2.2.3, 3.4.2.3.2, 3.4.2.3.3, 2.4.2.3, 3.4.2.4.2 and 3.4.2.4.3 are circled. The "No" in the "Yes / No" cells of rows 3.4.1.8.2, 2.4.2.1.7, 2.4.2.1.8, 2.4.2.1.9, 3.4.2.1.2, 3.4.2.1.3, 3.4.2.1.4, 2.4.2.2.2 and 3.4.2.3.4 are circled.)

 

Image of a table. Please see the Extended Text Description below.

(Extended Text Description: This is an excerpt of the ELMS PRL table listed above in section 2. ELMS PRL. The range of rows in this table from the ELMS PRL table starts at 3.4.3.1.1 and ends at 3.4.3.3.6. The only differences between this table and the source ELMS PRL table is that this table is a completed ELMS PRL table as described in A306b Sample Project, with certain elements highlighted as described below. Please see 2. ELMS PRL for the full table data. The table data that is highlighted in this sample project includes the following: The "Yes" in the "Yes / No" cells of rows 2.4.2.4.3, 3.4.3.3.3 and 3.4.3.3.5 are circled. The "No" in the "Yes / No" cells of rows 3.4 3.1.2 through 3.4 3.1.9, 2.4.2.4.2, 3.4.3.3.1, 3.4.3.3.2 and 3.4.3.3.6 are circled.)

 

Image of a table. Please see the Extended Text Description below.

(Extended Text Description: This is an excerpt of the ELMS PRL table listed above in section 2. ELMS PRL. The range of rows in this table from the ELMS PRL table starts at 3.5 and ends at 3.5.5.1. The only differences between this table and the source ELMS PRL table is that this table is a completed ELMS PRL table as described in A306b Sample Project, with certain elements highlighted as described below. Please see 2. ELMS PRL for the full table data. The table data that is highlighted in this sample project includes the following: The "Yes" in the "Yes / No" cells of rows 3.5.2, 3.5.2.1, 3.5.2.2, 3.5.4.1, 3.5.4.2 and 3.5.4.3 are circled. The "No" in the "Yes / No" cell of row 3.5.3.1 is circled. The following numbers are filled into the blanks for the Additional Project Requirements cells of the following rows (row: data): 3.5.1.1: 255, 3.5.1.2: 255, 3.5.2.1: 999, 3.5.2.2: 100, 3.5.4.1: 255, 3.5.4.2: 255, 3.5.4.3: 255 and 3.5.5.1: 152.)

 

4. Sample Specification Text

The following text should be considered when inserting NTCIP wording into a procurement specification.

S.1. PRL

The SSM shall conform to NTCIP 1213 and to the items selected in the following Protocol Requirements List (PRL).

<< Insert completed PRL here >>

S.2. Object Ranges

The ELMS shall support all values for all supported NTCIP objects, except as indicated within the PRL and this supplemental.

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

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

S.4. Configure Stagger Interval

a. Configure Luminaire Stagger Interval

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

b. Configure Branch Circuit Stagger Interval

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

S.5. Supplemental Requirements for Scheduled

a. Support a Number of Actions

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

b. Support a Number of Day Plans

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

S.6. Supplemental Requirements for Zones

a. Define Number of Zones Supported by an ELMS

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

b. Define Number of ELMS Devices for a Zone

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

S.7. Supplemental Requirements for Event Logs

a. Configure Number of Events in Event Log

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

b. Configure Number of Event Classes

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

c. Configure Number of Event Types

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

S.8. Supplemental Requirements for Live Data

Live Data Response Time - 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 fieldCommunications Profile

NTCIP communications shall operate over the following communications stack:

See Modules for details

C101: Introduction to the Communications Protocols and Their Uses in ITS Applications

 

5. Reference to Other Standards

Electrical and Lighting Management Systems

Systems Engineering

 

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.
MIB/Management Information Base

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 ELMS 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. An interdisciplinary collaborative approach to derive, evolves, and verify a lifecycle balanced system solution, which satisfies customer expectations and meets public acceptability.
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

 

8. Study Questions

The presentation for this module includes several quiz questions, which are presented here for easy reference. The answers to the questions are provided in the on-line presentation.

Question 1: What tool is used to show the relationship of objects and dialogs within the standard?

  1. Information Profile
  2. Protocol Requirements List (PRL)
  3. Requirements Traceability Matrix (RTM)
  4. Dialogs

Question 2: Which of the following is not a major group of requirements in NTCIP 1213?

  1. Configure ELMS Device
  2. Control Device
  3. Monitor Device Status
  4. Backwards Compatibility Requirements

Question 3: Where should the PRL be included in the specification?

  1. Hardware Specification
  2. In a Standalone Section
  3. Software Specification
  4. Interface Specification

Question 4: What does the following table mean?

Requirement ID Requirement Dialog ID Dialog Object ID Object
3.4.1.3.1 Configure Luminaire for Light Activated Operations
    4.2.3 Generic SNMP Set Interface
        5.4.1.3 luminaireMode
        5.4.1.15 luminaireLightThreshold
        5.4.1.16 luminaireHoldInterval
        5.4.1.17 luminaireLightHysteresis
        5.4.1.18 luminaireDelayInterval
  1. All of the objects must be supported
  2. At least one of the objects must be supported
  3. All of the objects must be supported if the requirement is supported
  4. At least one of the objects must be supported if the requirement is supported

Question 5: Which of the following is the best reason to extend a standard?

  1. There is a unmet need that justifies the added cost
  2. The existing system uses a non-standard method
  3. You want to use your specification to favor a specific vendor
  4. When the standardized solution is overly complex for your simple needs