Module 27 - A306b

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

Welcome

Head shot photo of Ken Leonard, Director - ITS Joint Program Office

Ken Leonard, Director
ITS Joint Program Office

Ken.Leonard@dot.gov

Screen capture snapshot of RITA website - for illustration only - see the extended text description below.

(Extended Text Description: Intro Slide: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: http://www.pcb.its.dot.gov - this screen capture snapshot shows an example from the RITA website from April 2013. At the top of the page it shows the RITA logo with the text U.S. Department of Transportation Research and Innovative Technology Administration - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and sections entitled Available E-Training (free), Free ITS Training and T3 Webinars. Again, this image serves for illustration only. The current website link is: http://www.pcb.its.dot.gov)

www.pcb.its.dot.gov

(Note: There is additional text attached to this slide that includes the following introductory information from Ken Leonard):

"ITS Standards can make your life easier. Your procurements will go more smoothly and you'll encourage competition, but only if you know how to write them into your specifications and test them. This module is one in a series that covers practical applications for acquiring and testing standards-based ITS systems.

I am Ken Leonard, director of the ITS Joint Program Office for USDOT and I want to welcome you to our newly redesigned ITS standards training program of which this module is a part. We are pleased to be working with our partner, the Institute of Transportation Engineers, to deliver this new approach to training that combines web based modules with instructor interaction to bring the latest in ITS learning to busy professionals like yourself.

This combined approach allows interested professionals to schedule training at your convenience, without the need to travel. After you complete this training, we hope that you will tell colleagues and customers about the latest ITS standards and encourage them to take advantage of the archived version of the webinars.

ITS Standards training is one of the first offerings of our updated Professional Capacity Training Program. Through the PCB program we prepare professionals to adopt proven and emerging ITS technologies that will make surface transportation safer, smarter and greener which improves livability for us all. You can find information on additional modules and training programs on our web site www.pcb.its.dot.gov

Please help us make even more improvements to our training modules through the evaluation process. We look forward to hearing your comments. Thank you again for participating and we hope you find this module helpful."

 

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:

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

 

Slide 5:

Instructor

Head shot photo of James J. Frazer - President - Gridaptive Technologies - Pompano Beach, Florida, USA

James J. Frazer
President
Gridaptive Technologies
Pompano Beach, Florida, USA

 

Slide 6:

Target Audience

 

Slide 7:

Recommended Prerequisite(s)

 

Slide 8:

Curriculum Path (SEP)

A graphic diagram is depicted that describes the seven current sequential courses in this series. Please see the Extended Text Description below.

(Extended Text Description: A graphic diagram is depicted that describes the seven current sequential courses in this series, starting with blue boxes containing the text: 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, A306a: Understanding User Needs for Electrical and Lighting Management Systems based on the NTCIP 1213 Standard, and finally A306b: Specifying Requirements for Electrical and Lighting Management Systems based on the NTCIP 1213 Standard - which is highlighted in purple.)

 

Slide 9:

Learning Objectives

  1. Review the structure of the NTCIP 1213 v02 Standard
  2. Use the Protocol Requirements List (PRL) to specify the standardized structure of requirements
  3. Include the requirements from the PRL in the specification
  4. Explain how interoperability is achieved through the Requirements Traceability Matrix
  5. Examine the benefits of the SEP approach regarding verification and validation in the ELMS testing process
  6. Explain conditions and context for extending the standard including specifying requirements not covered by standard

 

Slide 10:

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

 

Slide 11:

Learning Objective # 1

Capabilities of NTCIP 1213 Systems

Control and monitoring of terminal devices for:

 

Slide 12:

Learning Objective # 1

Capabilities of NTCIP 1213 Systems

Integration with other systems including:

 

Slide 13:

Learning Objective # 1

NTCIP 1213 System Configurations

This slide graphically represents a management center, an intermediary gateway and a number of field devices. Please see the Extended Text Description below.

(Extended Text Description: Author's relevant descriptive notes: Key message: This slide defines the environment in which the ELMS operates and where the interfaces are addressed by the standard. Field devices include meters, roadway lights, and safety equipment such as ground fault sensors. Notice that the NTCIP 1213 interface can be located at a gateway data collector or at a terminal device. This slide graphically represents a management center, an intermediary gateway and a number of field devices. One bidirectional arrow representing NTCIP 1213 communications connects the management center to the gateway. The second bidirectional arrow representing NTCIP 1213 communications connects the management center to the field devices.)

Graphics: Gridaptive Technologies

 

Slide 14:

Learning Objective # 1

The USDOT Framework

This slide describes the larger transportation ecosystem in which the ELMS operates and where the interfaces addressed by the standard. Please see the Extended Text Description below.

(Extended Text Description: Author's relevant descriptive notes: Key message: This slide describes the larger transportation ecosystem in which the ELMS operates and where the interfaces addressed by the standard. Notice NTCIP 1213 is a center to field communications standard, and that it is part of the larger ITS ecosystem. This slide graphically represents a management center and a number of field devices. A bidirectional arrow representing NTCIP 1213 communications connects the management center to the field devices. A "vehicle to infrastructure" block is represented as well.)

 

Slide 15:

Learning Objective # 1

The US Smart Grid Framework

This slide describes the larger electrical distribution ecosystem in which the ELMS operates and where the interfaces addressed by the standard. Please see the Extended Text Description below.

(Extended Text Description: Author's relevant descriptive notes: Key message: This slide describes the larger electrical distribution ecosystem in which the ELMS operates and where the interfaces addressed by the standard. The National Institute of Standards and Technology (NIST) Smart Grid Conceptual Model provides a high-level framework for the smart grid that defines seven important domains: Bulk Generation, Transmission, Distribution, Customers, Operations, Markets and Service Providers. It shows all the communications and energy/electricity flows connecting each domain and how they are interrelated. Each individual domain is itself comprised of important smart grid elements that are connected to each other through two-way communications and energy/electricity paths. These connections are the basis of the future, intelligent and dynamic power electricity grid. The NIST Smart Grid Conceptual Model helps stakeholders understand the building blocks of an end-to-end smart grid system, from Generation to (and from) Customers, and explores the interrelation between these smart grid segments.)

 

Slide 16:

Learning Objective # 1

Structure of the NTCIP 1213 Standard

Components of the Standard

 

Slide 17:

Learning Objective # 1

Structure of the NTCIP 1213 Standard (Cont.)

Components of the Standard

 

Slide 18:

Learning Objective # 1

Missing Components of NTCIP 1213

Test Cases

 

Slide 19:

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

 

Slide 20:

Learning Objective # 1

Which choice is not a capability of the NTCIP 1213 standard?

Answer Choices

  1. Roadway lighting, including scheduling and zoning
  2. Safety: electrical leakage anomalies, including power quality and ground fault issues
  3. Revenue grade power metering
  4. Wiring specifics

 

Slide 21:

Learning Objective # 1

Review of answers

A small graphical red and yellow X representing incorrect.a) Roadway lighting, including scheduling and zoning
Incorrect. This is a core capability of NTCIP 1213.

A small graphical red and yellow X representing incorrect.b) Safety: electrical leakage anomalies, including power quality and ground fault issues
Incorrect. This is a core capability of NTCIP 1213.

A small graphical red and yellow X representing incorrect.c) Revenue grade power metering
Incorrect. This is a core capability of NTCIP 1213.

A small graphical green and yellow check mark representing correct.d) Wiring specifics
Correct. NTCIP 1213 does not support wiring specifics.

 

Slide 22:

Summary of Learning Objective # 1

Review the Structure of the NTCIP 1213 Standard

 

Slide 23:

Learning Objective # 2 - Use the Protocol Requirements List (PRL) to specify the standardized structure of requirements

 

Slide 24:

Learning Objective # 2

Use the PRL to Trace User Needs to Requirements

A Subset of the PRL Table

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

(Extended Text Description: Table data below:

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  

)

Source: NTCIP 1213

 

Slide 25:

Learning Objective # 2

Use the PRL to Trace User Needs to Requirements

User Need IDs in the PRL Table

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the User Need ID column data. Please see Slide 24 for the table data.)

 

Slide 26:

Learning Objective # 2

Use the PRL to Trace User Needs to Requirements

User Needs in the PRL Table

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the User Need column data. Please see Slide 24 for the table data.)

 

Slide 27:

Learning Objective # 2

An Example User Need -Retrieve Luminaire Information

Examining User Need 2.4.2.1.1.1

2.4.2.1.1.1 Retrieve Luminaire Information

The system manager needs to be able to determine the capabilities of the ELMS. This manager may need to configure the ELMS luminaire to retrieve pole identifiers, locations, modes, zones, and vendor information for each luminaire.

 

Slide 28:

Learning Objective # 2

Use the PRL to Trace User Needs to Requirements

The Functional Requirement Identifier

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the FR ID column data. Please see Slide 24 for the table data.)

 

Slide 29:

Learning Objective # 2

Use the PRL to Trace User Needs to Requirements

The Functional Requirements Column

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the Functional Requirement column data. Please see Slide 24 for the table data.)

 

Slide 30:

Learning Objective # 2

Requirements for Retrieve Luminaire Information

Examining 3.4.1.1.1.1

3.4.1.1.1.1 Retrieve Luminaire Pole Identifier

A management station shall able to retrieve from the ELMS device the pole identifier to which a luminaire is attached.

 

Slide 31:

Learning Objective # 2

Requirements for Retrieve Luminaire Information

3.4.1.1.1.2 Retrieve Luminaire Location - A management station shall be able to retrieve the location of the luminaire from the ELMS device. The location information shall be in one of the following forms:

3.4.1.1.1.2.1 Specify Location in Longitude/Latitude

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

3.4.1.1.1.2.3 Specify Location in Local Reference Coordinate Grid

 

Slide 32:

Learning Objective # 2

Requirements for Retrieve Luminaire Information

3.4.1.1.1.3 Retrieve Luminaire Mode - A management station shall be able to retrieve the current operating mode of the luminaire from the ELMS device.

3.4.1.1.1.4 Retrieve Luminaire Zone - A management station shall be able to retrieve the zone identifier(s) for a luminaire from the ELMS device.

3.4.1.1.1.5 Retrieve Luminaire Vendor Information - A management station shall be able to retrieve the information on the version, make, and model of the luminaire from the ELMS device.

 

Slide 33:

Learning Objective # 2

ELMS Requirements are "Well-formed"

[Actor] [Action] [Target] [Constraint] [Localization]

Actor - Identifies who or what does the action

Action - Identifies what is to happen

Target - Identifies who or what receives the action

Constraint - Identifies how to measure success or failure of the requirement

Localization - Identifies the circumstances under which the requirement applies

Localization and constraint portions are important, but not all requirements will have both.

 

Slide 34:

Learning Objective # 2

Example of an ELMS Requirement

A management station shall be able to retrieve the location of the luminaire from the ELMS device

Actor - management station

Action - be able to retrieve

Target - the ELMS device

Constraint - location of the luminaire

 

Slide 35:

Learning Objective # 2

Section 3 Functional Requirements

3.1 Tutorial [Informative]

3.2 Protocol Requirements List (PRL)

3.3 Operational Environment Requirements

3.4 Functional Requirements

3.5 Supplemental Requirements

 

Slide 36:

Learning Objective # 2

Section 3.3 Operational Environment Requirements

3.3.1 Provide Live Data

3.3.2 Provide Off-Line Log Data

3.3.3 Monitor Exceptional Conditions

 

Slide 37:

Learning Objective # 2

Section 3.4 Functional Requirements

3.4.1 Configure ELMS Device

3.4.2 Control Device

3.4.3 Monitor Device Status

 

Slide 38:

Learning Objective # 2

Section 3.5 Supplemental Requirements

3.5.1 Supplemental Requirements for Scheduled Operations

3.5.2 Supplemental Requirements for Zones

3.5.3 Supplemental Requirements for Dim Levels

3.5.4 Supplemental Requirements for Event Logs

3.5.5 Supplemental Requirements for Live Data

 

Slide 39:

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

 

Slide 40:

Learning Objective # 2

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

Answer Choices

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

 

Slide 41:

Learning Objective # 2

Review of answers

A small graphical red and yellow X representing incorrect.a) Configure ELMS Device
Incorrect. These requirements provide for configuring ELMS field devices.

A small graphical red and yellow X representing incorrect.b) Control Device
Incorrect. These requirements provide for controlling the ELMS field device.

A small graphical red and yellow X representing incorrect.c) Monitor Device Status
Incorrect. These requirements provide for monitoring alarms and device status.

A small graphical green and yellow check mark representing correct.d) Backwards Compatibility Requirements
Correct. As the first published version of the standard, it does not have any backwards compatibility issues with which to deal.

 

Slide 42:

Learning Objective # 2

Including PRL Requirements in the ELMS Specification:

Conformance

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the Conformance column data. Please see Slide 24 for the table data.)

 

Slide 43:

Learning Objective # 2

Including PRL Requirements in the ELMS Specification:

Conformance

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

(Extended Text Description: Table data below:

User Need ID User Need FR ID Functional Requirement Conformance Project Requirement Additional Project Requirements
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  

Note: Four rows in the Conformance column are highlighted, starting with 0.1 (1..*) through 0.4 (1..*).)

 

Slide 44:

Learning Objective # 2

Including PRL Requirements in the ELMS Specification:

Project Requirements

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

(Extended Text Description: This is the same table as Slide 24, but highlighting the Project Requirement column data. Please see Slide 24 for the table data.)

 

Slide 45:

Learning Objective # 2

Including PRL Requirements in the ELMS Specification:

Project Requirements

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

(Extended Text Description: Table data below:

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  

Note: The last column, Additional Project Requirements, is highlighted.)

 

Slide 46:

Learning Objective # 2

Examining the PRL's Additional Project Requirements:

Performance Criteria

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

(Extended Text Description: Table data below:

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 las permission to transmit) within 125 millisecond(s) of receiving the last byte of the request, plus 1 millisecond for each byte in the response variable-bindings field

)

 

Slide 47:

Summary of Learning Objective #2

Use the Protocol Requirements List (PRL) to specify the standardized structure of requirements.

 

Slide 48:

Learning Objective # 3 - How to Include the

Requirements from the PRL in the Specification

 

Slide 49:

Learning Objective # 3

Using the PRL to Build a Specification: Washington State DOT Case Study

In preparing the communications interface specification for a large bridge and tunnel project, many user needs were identified.

Author notes: A photo of a highway at night with time lapse photopgrahy is presented as background information.

 

Slide 50:

Learning Objective # 3

Using the PRL to Build a Specification:

Washington State DOT Case Study

These Needs Included the Ability to:

 

Slide 51:

Learning Objective # 3

Using the PRL to Build a Specification:

Washington State DOT Case Study

These Needs Do Not Include the Ability to:

An image of an electrical cabinet used in the Washington State DOT project is pictured.

Photo: Gridaptive Technologies

 

Slide 52:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Live Data

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

(Extended Text Description: Table data below:

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  

)

 

Slide 53:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Off-Line Log Data

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

(Extended Text Description: Table data below:

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.5.4 Supplemental Requirements for Event Logs M Yes  

Note: The "Yes" in the column header of the "Yes / No" column is circled.)

 

Slide 54:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Luminaire Switch State Logging

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

(Extended Text Description: Table data below:

2.4.1.2.1 Provide Luminaire Switch State Logging 0 Yes / No  
    3.3.2.10.2 Luminaire Switch State Log 0 Yes / No  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.1 is circled.)

 

Slide 55:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Luminaire Lamp Condition Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.2 is circled.)

 

Slide 56:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Luminaire Burn Condition Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.3 is circled.)

 

Slide 57:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Periodic Luminaire Burn Time Logging

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

(Extended Text Description: Table data below:

2.4.1.2.4 Provide Periodic Luminaire Burn Time Logging 0 Yes / No  
    3.3.2.10.5 Periodic Luminaire Burn Time Log 0 Yes / No  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.4 is circled.)

 

Slide 58:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Periodic Luminaire Temperature Logging

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

(Extended Text Description: Table data below:

2.4.1.2.5 Provide Luminaire Temperature Logging 0 Yes / No  
    3.3.2.10.6 Luminaire Temperature Log 0 Yes / No  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.5 is circled.)

 

Slide 59:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Periodic Luminaire Pole Condition

Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.6 is circled.)

 

Slide 60:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Relay Switch State Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.7 is circled.)

 

Slide 61:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Power Meter Switch State Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.8 is circled.)

 

Slide 62:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Periodic Power Meter Measurement

Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.9 is circled.)

 

Slide 63:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Power Meter Condition Logging

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

(Extended Text Description: Table data below:

2.4.1.2.10 Provide Power Meter Condition Logging 0 Yes / No  
    3.3.2.10.11 Power Meter Condition Log 0 Yes / No  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.10 is circled.)

 

Slide 64:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Ground Fault Switch State Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.11 is circled.)

 

Slide 65:

Learning Objective # 3

Building Project Specifications

Using the PRL

Provide Periodic Ground Fault Measurement

Logging

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.1.2.12 is circled.)

 

Slide 66:

Learning Objective # 3

Building Project Specifications

Using the PRL

Retrieve Logged Data

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

(Extended Text Description: Table data below:

2.4.1.2.13 Retrieve Logged Data M Yes  
    3.3.2.3 Retrieve Logged Data M Yes  

)

 

Slide 67:

Learning Objective # 3

Building Project Specifications

Using the PRL

Monitor Exceptional Conditions

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

(Extended Text Description: Table data below:

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  
    3.3.3.6 Retrieve Current Number of Exception Events M Yes  
    3.3.3.7 Record and Timestamp Events M Yes  

Note: The "Yes" in the "Yes / No" cell of row 2.4.1.3 is circled.)

 

Slide 68:

Learning Objective # 3

Building Project Specifications

Using the PRL

Features

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

(Extended Text Description: Table data below:

2.4.2 Features M Yes  

)

 

Slide 69:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure ELMS Device

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

(Extended Text Description: Table data below:

2.4.2.1 Configure ELMS Device M Yes  

)

 

Slide 70:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Luminaire

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

(Extended Text Description: Table data below:

2.4.2.1.1 Configure Luminaire M Yes  

)

 

Slide 71:

Learning Objective # 3

Building Project Specifications Using the PRL

Retrieve Luminaire Information

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

(Extended Text Description: Table data below:

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

Note: The "No" in the "Yes / No" cells of rows 3.4.1.1.1.1 and 3.4.1.1.1.4 are circled.)

 

Slide 72:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Luminaire Identification Information

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

(Extended Text Description: Table data below:

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/Street/Block Name/Number M Yes Thp ELMS device shall support a location name of at least 255 (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  

Note: The "No" in the "Yes / No" cells of rows 3.4.1.1.1.2.1, 3.4.1.1.1.2.3 and 3.4.1.1.2.1 are circled.)

 

Slide 73:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Luminaire Mode

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

(Extended Text Description: Table data below:

2.4.2.1.1.3 Configure Luminaire Mode M Yes  
    3.4.1.1.3 Configure Luminaire Mode M Yes  

)

 

Slide 74:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Electrical Service

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

(Extended Text Description: Table data below:

2.4.2.1.2 Configure Electrical Service 0 Yes / No  

Note: The "Yes" in the "Yes / No" cell is circled.)

 

Slide 75:

Learning Objective # 3

Building Project Specifications

Using the PRL

Retrieve Electrical Service Information

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

(Extended Text Description: Table data below:

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  
    3.4.1.2.2.2 Configure Electrical Service Pole Identifier 0 Yes / No  

Note: The "No" in the "Yes / No" cell of row 2.4.2.1.2.1 is circled.)

 

Slide 76:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure for Light-Activated Operation

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" in the "Yes / No" cells of rows 2.4.2.1.3, 3.4.1.3.3 and 3.4.1.3.4 are circled. The "No" in the "Yes / No" cell of row 3.4.1.3.2 is circled.)

 

Slide 77:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure for Scheduled Operation

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" in the "Yes / No" cells of rows 2.4.2.1.4, 3.4.1.4.3 and 3.4.1.4.4 are circled. The "No" in the "Yes / No" cells of rows 3.4.1.4.1 and 3.4.1.4.2 are circled.)

 

Slide 78:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Zones

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" in the "Yes / No" cells of rows 2.4.2.1.5 and 3.4.1.5.3 are circled. The "No" in the "Yes / No" cell of row 3.4.1.5.2 is circled.)

 

Slide 79:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure for Manual Operation

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

(Extended Text Description: Table data below:

2.4.2.1.6 Configure for Manual Operation M Yes  
    3.4.1.8.1 Configure Luminaire for Manual Operation M Yes  
    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  

Note: The "No" in the "Yes / No" cell of row 3.4.1.8.2 is circled. The "Yes" in the "Yes / No" cells of rows 3.4.1.8.3 and 3.4.1.8.4 are circled.)

 

Slide 80:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Stagger Interval

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

(Extended Text Description: Table data below:

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.

Note: The "No" in the "Yes / No" cell of row 2.4.2.1.7 is circled.)

 

Slide 81:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Dim Levels

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

(Extended Text Description: Table data below:

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 Configure Dim Level for Devices in Zone 0 Yes / No  
    3.5.3 Supplemental Requirements for Dim Levels M Yes  

Note: The "No" in the "Yes / No" cell of row 2.4.2.1.8 is circled.)

 

Slide 82:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Electrical Service Monitoring and Metering Equipment

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.2.1.9 is circled.)

 

Slide 83:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Branch Circuit

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

(Extended Text Description: Table data below:

2.4.2.1.10 Configure Branch Circuit 0 Yes / No  

Note: The "Yes" in the "Yes / No" cell is circled.)

 

Slide 84:

Learning Objective # 3

Building Project Specifications

Using the PRL

Retrieve Branch Circuit Information

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" of all the "Yes / No" cells are circled.)

 

Slide 85:

Learning Objective # 3

Building Project Specifications

Using the PRL

Configure Branch Circuit

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

(Extended Text Description: Table data below:

2.4.2.1.10.2 Configure Branch Circuit 0 Yes / No  
    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  

Note: The "Yes" of all the "Yes / No" cells are circled.)

 

Slide 86:

Learning Objective # 3

Building Project Specifications

Using the PRL

Control Device

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

(Extended Text Description: Table data below:

2.4.2.2 Control Device M Yes  

)

 

Slide 87:

Learning Objective # 3

Building Project Specifications

Using the PRL

Control Luminaire

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cells of rows 3.4.2.1.2 through 3.4.2.1.4 are circled.)

 

Slide 88:

Learning Objective # 3

Building Project Specifications

Using the PRL

Control Electrical Service

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.2.2.2 is circled.)

 

Slide 89:

Learning Objective # 3

Building Project Specifications

Using the PRL

Control Branch Circuit

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" in the "Yes / No" cells of rows 2.4.2.2.3, 3.4.2.3.2 and 3.4.2.3.3 are circled. The "No" in the "Yes / No" cell of row 3.4.2.3.4 is circled.)

 

Slide 90:

Learning Objective # 3

Building Project Specifications

Using the PRL

Control Devices By Zone

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

(Extended Text Description: Table data below:

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  

Note: The "Yes" in the "Yes / No" cells of rows 2.4.2.3, 3.4.2.4.2 and 3.4.2.4.3 are circled.)

 

Slide 91:

Learning Objective # 3

Building Project Specifications

Using the PRL

Monitor Device Status

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

(Extended Text Description: Table data below:

2.4.2.4 Monitor Device Status M Yes  

)

 

Slide 92:

Learning Objective # 3

Building Project Specifications

Using the PRL

Monitor Luminaire

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

(Extended Text Description: Table data below:

2.4.2.4.1 Monitor Luminaire M Yes  
    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 Retreve Luminaire Lamp Status 0 Yes / No  
    3.4.3.1.7 Retreve Luminaire Power Usage Statistics 0 Yes / No  
    3.4.3.1.8 Retreve Luminaire Ballast Status 0 Yes / No  
    3.4.3.1.9 Retr eve Luminaire Starter Status 0 Yes / No  

Note: The "No" in the "Yes / No" cells of rows 3.4.3.1.2 through 3.4.3.1.9 are circled.)

 

Slide 93:

Learning Objective # 3

Building Project Specifications

Using the PRL

Monitor Electrical Service

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 2.4.2.4.2 is circled.)

 

Slide 94:

Learning Objective # 3

Building Project Specifications

Using the PRL

Monitor Branch Circuit

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

(Extended Text Description: Table data below:

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  

Note: 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.3.1, 3.4.3.3.2 and 3.4.3.3.6 are circled.)

 

Slide 95:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements

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

(Extended Text Description: Table data below:

Supplemental Requirement ID Supplemental Requirement Conformance Project Requirement Additional Project Requirements
3.5 Supplemental Requirements M Yes  

)

 

Slide 96:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements for Scheduled Operations

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

(Extended Text Description: Table data below:

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 255 (1..255) Actions.
3.5.1.2 Support a Number of Day Plans M Yes The ELMS Device shall support at least 255 (1..255) Day Plans.
3.5.1.3 Perform Action at Scheduled Time M Yes  

)

 

Slide 97:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements for Zones

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

(Extended Text Description: Table data below:

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 999 (0..65535) Zones.
3.5.2.2 Define Number of ELMS Devices for a Zone 0 Yes / No At least 100 (0..65535) ELMS devices shal be able to be assigned to a single zone.

Note: The "Yes" in the "Yes / No" cells of rows 3.5.2.1 and 3.5.2.2 are circled.)

 

Slide 98:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements for Dim Levels

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

(Extended Text Description: Table data below:

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  

Note: The "No" in the "Yes / No" cell of row 3.5.3.1 is circled.)

 

Slide 99:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements for Event Logs

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

(Extended Text Description: Table data below:

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 255 (1..255) events.
3.5.4.2 Configure Number of Event Classes 0 Yes / No The ELMS device shall support at least 255 (1..255) classes.
3.5.4.3 Configure Number of Event Types 0 Yes / No The ELMS device shall support at least 255 (1..255) event types.

Note: The "Yes" in the "Yes / No" cells of rows 3.5.4.1, 3.5.4.2 and 3.5.4.3 are circled.)

 

Slide 100:

Learning Objective # 3

Building Project Specifications

Using the PRL

Supplemental Requirements for Live Data

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

(Extended Text Description: Table data below:

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 152 millisecond(s) of receiving the last byte of the request, plus 1 millisecond for each byte in the response variable-bindings field

)

 

Slide 101:

Learning Objective # 3

Using the PRL in a Specification

As Part of the Interface Specification

 

Slide 102:

Learning Objective # 3

Using the PRL in a Specification

Compare and contrast vendor PRLs for off-the-shelf interoperability analysis

 

Slide 103:

Learning Objective # 3

Using the PRL in a Specification

Consistency

Three overlapping circles are represented. They are titled: Hardware Specification, Interface Specification, and Software Specification

 

Slide 104:

Learning Objective # 3

Using the PRL in a Specification

Sample Text for Use in a Specification

 

Slide 105:

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

 

Slide 106:

Learning Objective # 3

Which choice is not a functional requirement contained in the NTCIP 1213 PRL?

Answer Choices

  1. Retrieve luminaire location
  2. Configure luminaire mode
  3. Configure branch circuit zone
  4. Retrieve wiring particulars

 

Slide 107:

Learning Objective # 3

Review of answers

A small graphical red and yellow X representing incorrect.a) Retrieve luminaire location
Incorrect. This is a functional requirement of NTCIP 1213.

A small graphical red and yellow X representing incorrect.b) Configure luminaire mode
Incorrect. This is a functional requirement of NTCIP 1213.

A small graphical red and yellow X representing incorrect.c) Configure branch circuit zone
Incorrect. This is a functional requirement of NTCIP 1213.

A small graphical green and yellow check mark representing correct.d) Retrieve wiring particulars
Correct NTCIP 1213 does not support retrieval of wiring particulars.

 

Slide 108:

Summary of Learning Objective # 3

How to include the requirements from the PRL in the specification

 

Slide 109:

Learning Objective # 4 - Explain How

Interoperability is Achieved through the Requirements Traceability Matrix

 

Slide 110:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

Achieving Interoperability and Interchangeability

 

Slide 111:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Requirement ID Column

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

(Extended Text Description: Table data below:

Requirement ID Requirement Dialog ID Dialog Object ID Object
3.3 Operational Environment Requirements
3.3.1 Provide Live Data
3.3.1.1 Retrieve Data
    4.2.1 Generic SNMP Get Interface
3.3.1.2 Deliver Data
    4.2.3 Generic SNMP Set Interface
3.3.1.3 Data Retrieval and Data Delivery Action Performance
    4.2.1 Generic SNMP Get Interface
    4.2.2 Generic SNMP Get-Next Interface
    4.2.3 Generic SNMP Set Interface
3.3.2 Provide Off-line Log Data
3.3.2.1 Retrieve Configuration of Logging service
    4.2.1 Generic SNMP Get Interface

Note: The first column, Requirement ID, is highlighted.)

 

Slide 112:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Requirement Column

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

(Extended Text Description: Table data below:

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
3.4.1.3.2 Configure Electrical Service for Light Activated Operations
    4.2.3 Generic SNMP Set Interface
        5.5.1.6 electricalserviceMode
        5.5.1.19 electricalserviceLightThreshold
        5.5.1.20 electricalserviceHoldInterval
        5.5.1.21 electricalserviceLightHysteresis
        5.5.1.22 electricalserviceDelayInterval

Note: In this slide, the second column, Requirement, is highlighted.)

 

Slide 113:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Dialog ID Column

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

(Extended Text Description: This is the same table as Slide 112, but highlighting the Dialog ID column data instead of the Requirement column data. Please see Slide 112 for the table data.)

 

Slide 114:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Dialog Column

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

(Extended Text Description: This is the same table as Slide 112, but highlighting the Dialog column data instead of the Requirement column data. Please see Slide 112 for the table data.)

 

Slide 115:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Object ID Column

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

(Extended Text Description: This is the same table as Slide 112, but highlighting the Object ID column data instead of the Requirement column data. Please see Slide 112 for the table data.)

 

Slide 116:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

The Object Column

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

(Extended Text Description: This is the same table as Slide 112, but highlighting the Object column data instead of the Requirement column data. Please see Slide 112 for the table data.)

 

Slide 117:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

Summarizing the RTM

The RTM

 

Slide 118:

Learning Objective # 4

Using the Requirements Traceability Matrix (RTM)

How to Compare for Interoperability

 

Slide 119:

Learning Objective # 4

Comparison of PRLs

For Interoperability and Interchangeability

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

(Extended Text Description: Author's relevant descriptive notes: Key message: This slide introduces interoperability and interchangeability. Two boxes are pictured. The first represents the data object within the management center. The second represents the data object within the NTCIP 1213 device. A bidirectional arrow representing NTCIP communications connects the two boxes.)

 

Slide 120:

Learning Objective # 4

Comparison of PRLs

For Interoperability

 

Slide 121:

Learning Objective # 4

Comparison of PRLs

For Interchangeability

 

Slide 122:

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

 

Slide 123:

Learning Objective # 4

What does the following table mean?

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

(Extended Text Description: Table data below:

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

)

 

Answer Choices

  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

 

Slide 124:

Learning Objective # 4

Review of answers

A small graphical red and yellow X representing incorrect.a) All of the objects must be supported
Incorrect. They only need to be supported if the requirement has been selected in the PRL.

A small graphical red and yellow X representing incorrect.b) At least one of the objects must be supported
Incorrect. If the requirement is selected, all of the objects must be supported.

A small graphical green and yellow check mark representing correct.c) All of the objects must be supported if the requirement is supported
Correct.

A small graphical red and yellow X representing incorrect.d) At least one of the objects must be supported if the requirement is supported
Incorrect. If the requirement is supported, all of the objects must be supported.

 

Slide 125:

Learning Objective # 4

NTCIP 1213 Dialogs

A Basic Dialog between the TMS and the ELMS

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

(Extended Text Description: Author's relevant descriptive notes: Key message: Emphasize that many dialogs are a simple "Get" or "Set" command coupled with the response. The image above describes a simple GET request. Notice the management station is "getting" a "variable binding list." Two boxes representing a management station and an ELMS device are pictured. Two arrows representing a data request and a data response connect the two boxes.)

 

Slide 126:

Learning Objective # 4

NTCIP 1213 Dialogs

Dialog Example: Configuring a Schedule

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

(Extended Text Description: Author's relevant descriptive notes: Key message: This slide describes the "Set" commands used in configuring a schedule. To configure a schedule, Schedule Actions, Schedule Day Plans, and Time-Base Schedules need to be defined in the ELMS device. This is accomplished through use of the Set command that writes data to the ELMS device from the Management Station. In the first example of the three, the Management Station is Configuring Schedule Actions through a "Set" command. In the second example, the Management Station is Configuring Day Plans through a "Set" command. In the final example, the Management Station is configuring a Time-Base Schedule through a "Set" command. Two boxes representing a management station and an ELMS device are pictured at the top of the graphic. Three boxes representing three example dialogs are represented on the right of the screen. These are titled: "configure schedule", "configure day plans" and "configure time-base scheduile." Two arrows representing a data request and a data response connect the management station and ELMS device boxes for each of the three examples.)

Source: NTICP 1213

 

Slide 127:

Learning Objective # 4

NTCIP 1213 Dialogs

All Dialog Objects Are Listed in the RTM

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

(Extended Text Description: Table data below:

3.4.1.4 Configure for Scheduled Operation
3.4.1.4.1 Configure Luminaire for Scheduled Operations
    4.3.1 Configure Luminaire for Scheduled Operations
        5.4.1.4 luminaireSwitchMode
3.4.1.4.2 Configure Electrical Service for Scheduled Operations
    4.3.2 Configure Electrical Service for Scheduled Operations
        5.5.1.7 electricalserviceSwitchMode
3.4.1.4.3 Configure Branch Circuit for Scheduled Operations
    4.3.3 Configure Branch Circuit for Scheduled Operations
        5.6.1.7 branchcircuitSwitchMode
3.4.1.4.4 Configure Devices in Zone for Scheduled Operations
    4.3.4 Configure Devices in Zone for Scheduled Operations
        5.7.1.6 zoneSwitchMode
3.4.1.4.5 Schedule ELMS Device Event
    4.3.5 Schedule ELMS Device Event
        5.3.4.1 scheduleActionIndex
        5.3.4.2 scheduleAction
        5.3.4.3 scheduleActionType
        5.3.4.4 scheduleActionNumber
        5.3.4.5 scheduleActionParameter

)

 

Slide 128:

Summary of Learning Objective #4

Explaining Interoperability and the RTM

 

Slide 129:

Learning Objective # 5 - Examine the benefits of the SEP approach

 

Slide 130:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits in Developing a Test Plan

 

Slide 131:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits of Testing Using SEP

 

Slide 132:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits of Testing Using SEP

 

Slide 133:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits of Testing Using SEP

 

Slide 134:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits of Testing Using SEP

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

(Extended Text Description: Testing and the Systems Engineering Process. A graphic of the systems engineering process (SEP). The main graphic of the SEP is a V-shaped diagram in gradated blue with some additional horizontal extensions on the left and right side of the top of the V shape. Each section is separated with dark blue lines. There is a key at the lower right showing the blue separator lines, and designating them as "Decision Gate." The left horizontal extension is labeled as "Lifecycle Processes" and include the sections "Regional Architecture" (separated by a white space) to the second section labeled "Needs Assessment," then "Concept Selection," (blue line) "Project Planning," and "Systems Engineering Management Planning" (blue line). At this point the sections begin to descend the left side of the V with "Concept of Operations," (blue line) "System Requirements," (blue line) "High-level Design," "Subsystem Requirements," (blue line) "Detailed Design," (blue line) and "Software Coding / Hardware Fabrication" (blue line) at the bottom juncture of the V shape. Underneath the bottom point of the V shape is a long thin horizontal arrow pointing to the right labeled "Time Line." There is a long thin diagonal arrow pointing down along the left side of the V labeled "Decomposition and Definition." From the bottom point of the V, the sections begin to ascend up the right side of the V with "Unit Testing," (blue line) "Subsystem Integration," (blue line) "Subsystem Verification," (blue line) "System Integration," (blue line) "System Verification," (blue line) "Initial Deployment," (blue line) "System Validation," and (blue line) "Operations and Maintenance." There is a long thin arrow pointing up along the right side of the V shaped labeled "Integration and Recomposition." At this point the sections on the right "wing" of the V are labeled with "Changes and Upgrades" and (white space) "Retirement/Replacement." Between the V shape there are a series of gray dashed arrows connecting the related sections on each left/right side of the V shape. The first arrow (top) is labeled "System Validation Plan" and connects "Concept of Operations" on the left and "System Validation" on the right. The second arrow is labeled "System Verification Plan (System Acceptance)" and connects "System Requirements" on the left and "System Verification and Deployment" on the right. The third arrow is labeled "Subsystem Verification Plan (Subsystem Acceptance)" and connects "High-Level Design" on the left and "Subsystem Verification" on the right. The last arrow (at the bottom) is labeled "Unit/Device Test Plan" and connects "Detailed Design" on the left and "Unit/Device Testing" on the right. The empty space in the middle of the V is highlighted in light blue. The right side V diagonal from "Unit Testing," through "Subsystem Verification Subsystem Integration," "System Verification System Integration," to "System Validation Initial Deployment." There is a large word "Traceability" at the top of the graphic with a curved arrow pointing downward to the highlighted space between the V shape. There is another large word "Testing" on the right side of the diagram with a curved arrow pointing into the sections of the right side of the V diagram.)

 

Slide 135:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits of Testing Using SEP

 

Slide 136:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits to Agencies

 

Slide 137:

Learning Objective # 5

Examine the benefits of the SEP approach

The Benefits to Vendors

 

Slide 138:

Summary of Learning Objective #5

Benefits of the SEP Approach

 

Slide 139:

Learning Objective #6 - Extending the

Standard

 

Slide 140:

Learning Objective #6

Extending the Standard

Complicates interoperability and interchangeability

 

Slide 141:

Learning Objective #6

Extending the Standard

Extensions should only be considered when:

 

Slide 142:

Learning Objective #6

Extending the Standard

Extended equipment should be designed to:

 

Slide 143:

Learning Objective #6

Extending the Standard Using a Custom User Need

X.1 Custom Needs

X.1.1 Plan Selection Based on Astronomical Clock (Annex C)

A TMS operator needs the ELMS to switch luminaires, circuits and electrical services based on the sunrise and sunset time as calculated by day of year, and latitude / longitude.

This feature allows ELMS to ensure these conditions are managed daily.

 

Slide 144:

Learning Objective #6

Extending the Standard Using a Custom User Need

X.2 Requirements

X.2.1 Configure Astronomical Control

The ELMS shall allow the TMS to configure schedule mode to enable astronomical control

X.2.2 Monitor Astronomical Control

The ELMS shall allow the TMS to monitor astronomical control.

 

Slide 145:

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

 

Slide 146:

Learning Objective #6

Which of the following is the best reason to extend the NTCIP 1213 standard?

Answer Choices

  1. There is an 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

 

Slide 147:

Learning Objective #6

Review of answers

A small graphical green and yellow check mark representing correct.a) There is an unmet need that justifies the added cost
Correct. Sometimes you just have to accept the added cost.

A small graphical red and yellow X representing incorrect.b) The existing system uses a non-standard method
Incorrect. Doing this will prolong the expensive customized approach for another generation.

A small graphical red and yellow X representing incorrect.c) You want to use your specification to favor a specific vendor
Incorrect. This can trap you into a proprietary solution.

A small graphical red and yellow X representing incorrect.d) When the standardized solution is overly complex
Incorrect. Some NTCIP features are complex to allow flexibility, but costs of custom solutions far outweigh any costs due to added complexity.

 

Slide 148:

Summary of Learning Objective #6

Explain conditions and context for extending the Standard

 

Slide 149:

What We Have Learned

  1. Components of the standards: User Needs Requirements, Dialogs, the PRL and the RTM.
  2. Dialogs_ and messages in the RT/Ware communicated to the field device using SNMP.
  3. The protocol implementer can use testing results to confirm conformance to NTCIP 1213 as a benefit to agencies.
  4. The RTM traces requirement to a single design solution, thereby providing interoperability

 

Slide 150:

Resources

 

Slide 151:

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