Module 26 - A306a

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

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation 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.)

 

Slide 1:

Welcome - Graphic image of introductory slide. Please see the Extended Text Description below.

(Extended Text Description: Slide 1: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words “Standards ITS Training” in green and blue on the middle left side. The word “Welcome” in white is to the right of the logo. Under the logo box are the words “RITA Intelligent Transportation Systems Joint Program Office.”)

 

Slide 2:

A306a:

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

 

Slide 3:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 4:

Instructor

Portrait image of James J. Frazer, President, Gridaptive Technologies Pompano Beach, FL, USA

James J. Frazer

President

Gridaptive Technologies Pompano Beach, FL, USA

 

Slide 5:

Target Audience

 

Slide 6:

Recommended Prerequisite(s)

 

Slide 7:

Curriculum Path (SEP)

Curriculum Path (SEP) diagram. Please see the Extended Text Description below.

(Extended Text Description: A graphic is depicted that describes the seven current sequential courses in this series: They are I101 Using ITS Standards: An Overview A101: Introduction to Acquiring Standards based ITS Systems A102: Introduction to User Needs Identification A201: Details on Acquiring Standards-based ITS Systems C101: Introduction to Communications Protocols and their use in ITS Applications C201: Introduction to the SNMP and its Applications in the NTCIP Standards A306a: Understanding User Needs for Electrical and Lighting Management Systems based on the NTCIP 1213 Standard A306b: Specifying Requirements for Electrical and Lighting Management Systems based on the NTCIP 1213 Standard. The first six courses listed - I101 through C201 - are highlighted in blue boxes and the last two courses listed - A306a and A306b - are highlighted in darker purple boxes.)

 

Slide 8:

Learning Objectives

  1. Review the structure of the NTCIP 1213 v02 Standard for Electrical and Lighting Management Systems (ELMS)
  2. Identify ELMS-specific user needs
  3. Use the Protocol Requirements List (PRL) to select the user needs and link to requirements
  4. Explain how the ELMS PRL table of the NTCIP 1213 Standard fits into the development of ELMS project specifications and contract documents

 

Slide 9:

Value of an ELMS Module Sequence

The ELMS NTCIP 1213 Group of Modules consists of:

 

Slide 10:

Learning Objective #1 - Review the Structure of the NTCIP 1213 v02 Standard

 

Slide 11:

Learning Objective #1

Definition and Purpose of an ELMS

An ELMS is defined as a system or device that:

 

Slide 12:

Learning Objective #1

What Defines a System as an ELMS?

To be an ELMS system, a system needs to:

 

Slide 13:

Case Study. A placeholder graphic of a traffic operations center indicating a case study. The image shows a large room with a series of computer work stations in six visible rows leading into the distance. People are seated and working at several workstations. There is a blue rectangle at the top of the image of the traffic operations center with the title “Case Study.” DOT and RITA logo in lower left corner and Standards ITS Training logo in lower right corner.

 

Slide 14:

Learning Objective #1

ELMS Case Study - Anytown, USA

 

Slide 15:

Learning Objective #1

ELMS Case Study - Anytown, USA

The User Needs

 

Slide 16:

Learning Objective #1

ELMS Case Study - Anytown, USA

Can an ELMS system satisfy these five wide ranging user needs?

The answer is YES.

This course will provide the domain knowledge to achieve those goals.

 

Slide 17:

Learning Objective #1

The NTCIP 1213 ELMS Standard

 

Slide 18:

Learning Objective #1

Structure of the ELMS NTCIP 1213 Standard

NTCIP 1213 Table of Contents

 

Slide 19:

Learning Objective #1

Benefits of the ELMS NTCIP 1213 Standard

Follows the Systems Engineering Process (SEP) and provides the following benefits:

 

Slide 20:

Learning Objective #1

Review of the ELMS Standard NTCIP 1213

National Transportation Communications for ITS Protocols (NTCIP): a family of standards for the ITS industry

 

Slide 21:

Learning Objective #1

The NTCIP Family of ITS Standards

A family of standards for the ITS industry (cont.)

 

Slide 22:

Learning Objective #1

The NTCIP Family of ITS Standards

A graphic of the communication levels of the NTCIP standards. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: A graphic of the communication levels of the NTCIP standards. The bottom level is the Plant Level and includes boxes for Dial-up, Fiber, Coax, Wireless, Twisted Pair, and Leased Line. The next higher level is called the Subnetwork Level and includes PPP, Ethernet, and PMPP. The next level is called the Transport Level and includes TCP/IP, UDP/IP, and T2/NULL. The next level is called the Application Level and includes C2C XML, DATEX, FTP, TFTP, SNMP, and STMP. The next level is called the Information Level and includes C2C Messages, Files, Data Objects, and Dynamic Objects. These boxes are connected to an overarching box also in the Information Level is highlighted with a red square indicating that it is the subject of ELMS NTCIP 1213 standard. This area is labeled Functional Area Data Dictionaries with the left hand side identifying C2C Data Dictionaries and the right hand side labeled NTCIP Data Dictionaries.)

Source: NTCIP 9001, Exhibit 3.3: NTCIP Standards Framework

 

Slide 23:

Learning Objective #1

Review of the ELMS NTCIP 1213 Standard

What is NTCIP 1213?

A graphic is depicted that describes the hierarchical relationship between the ELMS Management station, the ELMS Device and the Field Devices. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: A graphic is depicted that describes the hierarchical relationship between the ELMS Management station, the ELMS Device and the Field Devices. At the top of the image is a text block that states "ELMS Management Station". In the middle of the image is a text black that states "ELMS Device". At the bottom of the image is a text block that describes field devices. It describes these as “Branch Circuits, Power metering, Ground fault, Roadway Lighting, Power Quality and Electrical Services. In the image a bidirectional arrow connects the ELMS Management Station and the ELMS Device. It is labeled NTCIP - as it describes native NTCIP communications between these devices. In the image a bidirectional arrow connects the ELMS Device and the Field Devices. It is labeled Non- NTCIP - as it describes non- NTCIP communications between these devices. )

Figure 1, Page 9, NTCIP 1213 Standard

 

Slide 24:

Learning Objective #1

History of the ELMS NTCIP 1213 Standard

 

Slide 25:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 26:

Learning Objective #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.

 

Slide 27:

Learning Objective #1

Review of Answers

A small graphical green and yellow check mark representing correct.a) NTCIP 1213 is an information content standard.
Correct because NTCIP 1213 addresses the information level of interoperability.

 

A small graphical red and yellow X representing incorrect.b) NTCIP 1213 is an application level standard.
Incorrect because NTCIP 1213 does not address the application level.

 

A small graphical red and yellow X representing incorrect.c) NTCIP 1213 is a transport level standard.
Incorrect because NTCIP 1213 does not address the transport level.

 

A small graphical red and yellow X representing incorrect.d) NTCIP 1213 is a plant level standard.
Incorrect because NTCIP 1213 does not address the plant level.

 

Slide 28:

Learning Objective #1

Major Benefits of ELMS NTCIP 1213

 

Slide 29:

Learning Objective #1

Advantages of ELMS NTCIP 1213

Enables Solutions that are:

 

Slide 30:

Learning Objective #1

Advantages of SEP and ELMS NTCIP 1213

 

Slide 31:

Learning Objective #1

ELMS NTCIP 1213 and the Systems Engineering Process Life Cycle

The SEP "V" Model

An image that describes the V model of the Systems Engineering Process Life Cycle. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: Includes an image that describes the V model of the Systems Engineering Process Life Cycle. The left side of the V represents concept development and the decomposition of requirements into function and physical entities that can be architected, designed, and developed. The right side of the V represents integration of these entities (including appropriate testing to verify that they satisfy the requirements) and their ultimate transition into the field, where they are operated and maintained. An obvious place to start developing system requirements is with the user requirements—high-level expressions of user needs that the system is expected to satisfy. Subsequently, system technical requirements are developed after user requirements are defined. System requirements should be tracked or traced to the user requirements. Tracing a requirement means to cross-reference the source (in this case user) requirement on which a system-level requirement is based, and also to reverse reference which system requirement(s) implement the source requirements. Tracing user to system-level requirements helps ensure that all requirements have some user basis and that all user requirements are included in the system requirements for development. )

 

Slide 32:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 33:

Learning Objective #1

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

 

Slide 34:

Learning Objective #1

Review of Answers

A small graphical red and yellow X representing incorrect.a) Supports interoperability
True, the NTCIP 1213 SEP process supports the information level of interoperability.

 

A small graphical green and yellow check mark representing correct.b) It allows multiple designs for each requirement
False, the NTCIP 1213 does define a unique design for each requirement.

 

A small graphical red and yellow X representing incorrect.c) Allows clear development of test procedures based on the requirements selected
True, the NTCIP 1213 describes clear test procedures.

 

A small graphical red and yellow X representing incorrect.d) Determines what user needs are supported
True, the NTCIP 1213 determines the user needs to be supported.

 

Slide 35:

Summary of Learning Objective #1

Review the structure of the NTCIP 1213 v02 Standard

 

Slide 36:

Learning Objective #2 - Identify SpecificELMS User Needs

 

Slide 37:

Case Study. A placeholder graphic of a traffic operations center indicating a case study. The image shows a large room with a series of computer work stations in six visible rows leading into the distance. People are seated and working at several workstations. There is a blue rectangle at the top of the image of the traffic operations center with the title “Case Study.” DOT and RITA logo in lower left corner and Standards ITS Training logo in lower right corner.

 

Slide 38:

Learning Objective #2

ELMS Case Study - A City in Minnesota

The User Needs

During a downtown reconstruction project, these user needs were identified :

Includes a general background image of ITS technology including DMS signage.

Image © 2012 Gridaptive Technologies

 

Slide 39:

Learning Objective #2

ELMS Case Study - A City in Minnesota

The Results

Includes a general background image of ITS technology describing a map based graphical user interface.

Image © 2012 Gridaptive Technologies

 

Slide 40:

Learning Objective #2

ELMS Case Study - A County in Florida

The User Needs

Due to severe and fatal injuries of people and animals, these user needs were recognized:

Includes an image of a child actuating a crosswalk signal button.

Image © 2012 Gridaptive Technologies

 

Slide 41:

Learning Objective #2

ELMS Case Study - A County in Florida

The Result

Includes an image of a lighting technician working on a pole mounted ELMS installation.

Image © 2012 Gridaptive Technologies

 

Slide 42:

Learning Objective #2

ELMS Case Study - Washington State DOT

The User Needs

During a tunnel and bridge project, these user needs were identified:

Includes an general image of roadway lighting at night with a city in the background.

Image © 2012 Gridaptive Technologies

 

Slide 43:

Learning Objective #2

ELMS Case Study - Washington State DOT

The Results

Includes an image of large electrical service cabinets used in this application.

Image © 2012 Gridaptive Technologies

 

Slide 44:

Learning Objective #2

ELMS NTCIP 1213 Concept of Operations

What is the Concept of Operations?

 

Slide 45:

Learning Objective #2

Primary Uses of ELMS NTCIP 1213 Systems

ELMS is used for control and monitoring of:

 

Slide 46:

Learning Objective #2

What is a User Need?

Describes the major capability provided by a system to satisfy an operational need

 

Slide 47:

Learning Objective #2

Who and What Can Generate User Needs?

User needs describe the major capability provided by a system to satisfy an operationalneed.

 

Slide 48:

Learning Objective #2

ELMS NTCIP 1213 User Needs

The ELMS Problem Statement

 

Slide 49:

Learning Objective #2

Scope of the ELMS NTCIP 1213 Standard

Simple Architecture

This graphic includes an image of an ELMS Management Station to the left, and ELMS Device in the center, and terminal devices to the right. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: This graphic includes an image of an ELMS Management Station to the left, and ELMS Device in the center, and terminal devices to the right. This graphic describes an ELMS that supports only proprietary terminal devices. Notice that the luminaire, electrical service, and branch circuit do not communicate using NTCIP. In this case the ELMS device translates proprietary protocols into standardized ELMS objects.

)

 

Slide 50:

Learning Objective #2

Scope of the ELMS NTCIP 1213 Standard

Alternate Architecture: ELMS within a Luminaire

This graphic includes an image of an ELMS Management Station to the left, and ELMS Device to the right. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: This graphic includes an image of an ELMS Management Station to the left, and ELMS Device to the right. The graphic of an alternate ELMS architecture depicts the connections among various ELMS components. It describes an ELMS device resident within a roadway luminaire, as well as native NTCIP communications directly to the luminaire. This graphic depicts the connections among various ELMS components. The management station is connected to the data aggregator ELMS device, and this connection is the subject of the NTCIP standards.)

Source Figure 1 , Page 9 NTCIP 1213 Standard

 

Slide 51:

Learning Objective #2

Scope of the ELMS NTCIP 1213 Standard

Alternate Architectures - Logical Zoning

This graphic includes an image of an ELMS Management Station to the left, and ELMS Device in the center, and terminal devices to the right. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: This graphic includes an image of an ELMS Management Station to the left, and ELMS Device in the center, and terminal devices to the right. Within the ELMS devices Zones are depicted.
This graphic describes logical zones resident within an ELMS device.

This graphic depicts the connections among various ELMS components. The management station is connected to the data aggregator ELMS device, and this connection is the subject of the NTCIP standards. The ELMS itself communicates with multiple terminal components which may include various sensors, including lighting controllers, ground fault interrupters, and revenue grade electric meters. )

 

Slide 52:

Learning Objective #2

ELMS NTCIP 1213 User Needs in Detail

 

Slide 53:

Learning Objective #2

ELMS NTCIP 1213 User Needs in Detail

The user needs are organized as follows:

 

Slide 54:

Learning Objective #2

ELMS NTCIP 1213 Operational User Needs

Provide Live Data (mandatory)

2.4.1.1 Provide Live Data

One operational environment allows the management system to monitor and control the device by issuing requests (e.g., requests to access information, alter information, or control the device). In this environment, the device responds to requests from the management station immediately (e.g., through the provision of live data, success/failure notice of information alteration, or success/failure of the command).

 

Slide 55:

Learning Objective #2

ELMS NTCIP 1213 Operational User Needs

Provide Off-line Logged Data

2.4.1.2 Provide Off-Line Log Data

Some operational environments do not have always-on connections (e.g., dial-up links). In such environments, a transportation system operator may wish to define conditions under which data is placed into a log, which can then be uploaded at a later time. For example, the operator may wish to manage the ELMS device so that it autonomously maintains a log of whenever a specific luminaire is turned on or off.

 

Slide 56:

Learning Objective #2

ELMS NTCIP 1213 Features

Relate to the informational needs of the users

Divided into three major functional categories

  1. Control, monitor, and manage roadway lighting
  2. Control, monitor, and manage electrical power
  3. Control, monitor, and manage electrical safety

 

Slide 57:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Roadway Lighting

Managing Roadway Lighting includes several sub-needs:

 

Slide 58:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Roadway Lighting

Managing Roadway Lighting includes several sub-needs:

 

Slide 59:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Roadway Lighting

Managing Roadway Lighting also includes luminaire sub-needs:

 

Slide 60:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Roadway Lighting

Managing Roadway Lighting also includes Luminaire sub-needs:

 

Slide 61:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Electrical Power

Managing Electrical Power includes several sub-needs:

 

Slide 62:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Electrical Safety

Managing Electrical Safety includes several sub-needs:

 

Slide 63:

Learning Objective #2

ELMS NTCIP 1213 Features: Manage Electrical Safety

Managing Electrical Safety includes several additional sub-needs:

 

Slide 64:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 65:

Learning Objective #2

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

 

Slide 66:

Learning Objective #2

Review of Answers

A small graphical red and yellow X representing incorrect.a) Need to inform TMC manager of electrical leakage
Incorrect, NTCIP 1213 supports the communications of electrical leakage information.

 

A small graphical green and yellow check mark representing correct.b) Need to control traffic flow at an intersection
Correct, NTCIP 1213 does not support traffic flow.

 

A small graphical red and yellow X representing incorrect.c) Need to inform TMC manager of energy usage
Incorrect, NTCIP 1213 supports the communications of energy usage information.

 

A small graphical red and yellow X representing incorrect.d) Need to control lighting levels by dimming
Incorrect, NTCIP 1213 supports the communications of dimming information.

 

Slide 67:

Summary of Learning Objective #2

 

Slide 68:

Learning Objective #3 - Use the Protocol Requirements List (PRL) to Select User Needs and Link to Requirements

 

Slide 69:

Learning Objective #3

ELMS NTCIP 1213 Functional Requirements

Section 3 of the ELMS standard defines the requirements based on the user needs identified in Section 2, and the interrelationship of user needs and functional requirements.

 

Slide 70:

Learning Objective #3

The Purpose of the ELMS Protocol Requirements List

The PRL's purpose is to:

 

Slide 71:

Learning Objective #3

The ELMS Protocol Requirements List

3.2.5 Protocol Requirements List (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 Lagging 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

 

 

Slide 72:

Learning Objective #3

ELMS User Needs in the PRL

3.2.5 Protocol Requirements List (PRL). Please see the Extended Text Description below.

(Extended Text Description: This slide depicts the table in Slide 71 (repeated below) with the following changes: The columns User Need ID and User Need are highlighted with a red box.

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 Lagging 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

 

)

 

Slide 73:

Learning Objective #3

ELMS Functional Requirements in the PRL

3.2.5 Protocol Requirements List (PRL). Please see the Extended Text Description below.

(Extended Text Description: This slide depicts the table in Slide 71 (repeated below) with the following changes: The columns FR ID and Funcational Requirement are highlighted with a red box.

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 Lagging 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

 

)

 

Slide 74:

Learning Objective #3

ELMS Conformance in the PRL

3.2.5 Protocol Requirements List (PRL). Please see the Extended Text Description below.

(Extended Text Description: This slide depicts the table in Slide 71 (repeated below) with the following changes: The column Conformance is highlighted with a red box.

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 Lagging 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

 

)

 

Slide 75:

Learning Objective #3

ELMS Project Requirements in the PRL

3.2.5 Protocol Requirements List (PRL). Please see the Extended Text Description below.

(Extended Text Description: This slide depicts the table in Slide 71 (repeated below) with the following changes: The column Project Requirement is highlighted with a red box.

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 Lagging 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

 

)

 

Slide 76:

Learning Objective #3

ELMS Supplemental Requirements

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 o Number of Actions

M

Yes

The ELMS Device snail support at least _____ (1..255) Aclions.

3.5.1.2

Support a Number of Day Plans

M

Yes

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

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

Suppfemental 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 Requirement for Event LOtjS

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.

 

Slide 77:

Learning Objective #3

Other User Needs Not in the PRL

Other Operational Needs:

User Needs Not Supported by NTCIP 1213

 

Slide 78:

Learning Objective #3

Summarizing the ELMS PRL

3.2.5 Protocol Requirements List (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 Lagging 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

 

 

Slide 79:

Learning Objective #3

Agency Use of the ELMS PRL The ELMS PRL can be used by:

 

Slide 80:

Learning Objective #3

Supplier and User Use of the ELMS PRL The ELMS PRL can also be used by:

 

Slide 81:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 82:

Learning Objective #3

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.

 

Slide 83:

Learning Objective #3

Review of Answers

A small graphical red and yellow X representing incorrect.a) User needs do not describe what features the device needs to support and why.
Incorrect, user needs do describe supported features.

 

A small graphical red and yellow X representing incorrect.b) Functional requirements are not specifications.
Incorrect, functional requirements do not support specifications.

 

A small graphical red and yellow X representing incorrect.c) Within the PRL, the relationships between user needs and functional requirements are not standardized.
Incorrect, relationships between user needs and functional requirements are standardized.

 

A small graphical green and yellow check mark representing correct.d) The PRL promotes interoperability.
Correct, the PRL does support interoperability.

 

Slide 84:

Learning Objective #3

Selecting User Needs through the PRL

Using the ELMS User Need ID number 2.4.2.2.2, the corresponding text allows determination if the user need "Control Electrical Service" is desired in your system.

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

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

 

Slide 85:

Learning Objective #3

Selecting User Needs through the PRL

ELMS User Need 2.4.2.2.2 "Control Electrical Service" is defined on page 14 of the ELMS Standard as:

A management station may need to control an electrical service directly or by enabling/disabling the stagger mode for branch circuits served by the electrical service. A management station may need to control the electrical service to allow or disallow the schedule control by one of three states:

  1. Continuous controlónot allowing the schedule to control current settings for electrical service
  2. Transitory control ónot allowing the schedule to control the electrical service until the next event in the schedule
  3. Timed controlónot allowing the schedule to control the electrical service until after a period of time specified in the timed control dialog for the electrical service

 

Slide 86:

Learning Objective #3

The ELMS PRL and Conformance

Conformance Mandatory vs. Optional

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

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

 

Slide 87:

Learning Objective #3

The ELMS PRL and Conformance

Conformance Mandatory vs. Optional

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

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

 

 

Slide 88:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 89:

Learning Objective #3

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.

 

Slide 90:

Learning Objective #3

Review of answers

A small graphical red and yellow X representing incorrect.a) Options for conformance are mandatory or optional.
True statement; the only valid entries for Conformance are mandatory and optional.

 

A small graphical red and yellow X representing incorrect.b) Options for project requirements are yes or no.
True statement; the only valid entries for project requirements are yes and no.

 

A small graphical red and yellow X representing incorrect.c) Optional user needs are dependent on project requirements.
True statement; selection of project requirements drives the inclusion/exclusion of optional UN.

 

A small graphical green and yellow check mark representing correct.d) Optional functional requirements are not dependent on project requirements.
False; selection of project requirements drives the inclusion/exclusion of optional FRs.

 

Slide 91:

Learning Objective #3

ELMS User Needs Hierarchical Relationship

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

 

 

Slide 92:

Learning Objective #3

The ELMS PRL User Needs - Project Requirements Relationship

Supported Project Requirements

Agency/Specifier to circle Yes or No to indicate the agency's user needs for the proposed implementation.

User Need ID

User Need

FRID

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

 

 

Slide 93:

Learning Objective #3

Importance of the ELMS PRL's User Needs and Functional Requirements Relationship

 

Slide 94:

Learning Objective #3

The ELMS PRL's User Needs/Functional Requirements Relationship in Detail

Functional Requirement Identifier (FR ID) - Section Number of the Functional Requirement

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

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

 

 

Slide 95:

Learning Objective #3

The ELMS PRL's User Needs/Functional Requirements Relationship in Detail

 

Slide 96:

Learning Objective #3

The ELMS PRL's User Needs/FunctionalRequirements Relationship in Detail

Mandatory vs. Optional

 

Slide 97:

Learning Objective #3

The ELMS PRL's User Needs/FunctionalRequirements Relationship in Detail

Additional Project Requirements Column

 

Slide 98:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 99:

Learning Objective #3

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.

 

Slide 100:

Learning Objective #3

Review of Answers

A small graphical red and yellow X representing incorrect.a) User Needs describe what features the device needs to support.
True statement, user needs describe what features are required.

 

A small graphical red and yellow X representing incorrect.b) Functional Requirements refine the user needs into specifications.
True statement, Functional Requirements do refine user needs into detailed, measurable specifications.

 

A small graphical red and yellow X representing incorrect.c) Relationships between User Needs and Functional Requirements are standardized.
True statement, the PRL defines standardized relationships.

 

A small graphical green and yellow check mark representing correct.d) The PRL does not promote interoperability.
False, the PRL does promote interoperability.

 

Slide 101:

Learning Objective #3

Using the ELMS PRL to Check Interoperability

Use of the ELMS PRL supports interoperability of selected attributes with:

 

Slide 102:

Summary of Learning Objective #3

Use the ELMS PRL to select the user needs and link them to requirements to:

 

Slide 103:

Learning Objective #4

Explain how the ELMS PRL table of the NTCIP 1213 Standard fits into the development of ELMS project specifications and contract documents

 

Slide 104:

Learning Objective #4

Integrating the ELMS PRL into an ELMS Specification

From a vendor's perspective

 

Slide 105:

Learning Objective #4

Integrating the ELMS PRL into an ELMS Specification

From an agency's perspective

 

Slide 106:

Learning Objective #4

Integrating the ELMS PRL into an ELMS Specification

ELMS Contract Documents

A completed ELMS PRL is part of the overall project specification, in addition to the hardware and software specifications

Contract Documents diagram. Please see the Extended Text Description below.

(Extended Text Description: The graphic table depicts the following information that includes a table, shown below. A box labled Contract Documents surrounds a table with three columns, the last column entitled Communications Interface Specifications is highlighted in red:

Product Specifications
Hardware Specifications Software Specifications Communications Interface Specifications
Functional Requirements Functional Requirements Functional Requirements
Performance Requirements Performance Requirements Performance Requirements
Structural Requirements   Protocol Requirements
Mechanical Requirements    
Electrical Requirements    
Environmental Requirements    

Additional author's notes for Slide 106: Includes an images that describes Contract Documents as being comprised of Hardware Specifications, Software Specifications and Communications Interface Specifications

)

 

Slide 107:

Learning Objective #4

Integrating the ELMS PRL into an ELMS

Specification - Conformance vs. Compliance

 

Slide 108:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 109:

Learning Objective #4

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

 

Slide 110:

Learning Objective #3

Review of Answers

A small graphical red and yellow X representing incorrect.a) Vendors can provide an ELMS PRL for their standard products to show what user needs they support.
True statement, products can be evaluated for standardization

 

A small graphical red and yellow X representing incorrect.b) A completed ELMS PRL must become part of the overall specification.
True statement, project specifications includes communications, hardware, and software specifications

 

A small graphical red and yellow X representing incorrect.c) A completed ELMS PRL indicates the requirements for the communications interface.
True statement, the PRL defines the communications interface

 

A small graphical green and yellow check mark representing correct.d) A completed ELMS PRL describes the entire project specification.
False, it only describes the communications interface

 

Slide 111:

Summary of Learning Objective #4

 

Slide 112:

What We Have Learned

  1. NTCIP 1213 defines the concept of operations and user needs for Electricaland Lighting Management Systems.
  2. NTCIP 1213 follows the SEP approach.
  3. ELMS has three major categories of functionalities.
    1. Control RoadwayLighting
    2. Monitor Ground Fault Conditions
    3. Monitor Electrical Power Usage
  4. A Protocol Requirements List is used to link user needs to functional requirements.
  5. PRL table of the ELMS standard fits into an ELMS project specification.

 

Slide 113:

Resources

 

Slide 114:

Questions? A placeholder graphic image with word Questions? at the top, and an image of a lit light bulb on the lower right side.

 

Slide 115:

Next Course Module

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