Module 27 - A306b
A306b: Specifying Requirements for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard v03
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:
(Extended Text Description: Author's relevant description: 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 - Transit" 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 is the logo for the U.S. Department of Transpotation, Office of the Assistant Secretary for Research and Technology.)
Slide 2:
(Extended Text Description: Author's relevant description: This slide, entitled "Welcome" has a photo of Ken Leonard, Director, ITS Joint Program Office, on the left hand side, with his email address, Ken.Leonard@dot.gov. A screen capture snapshot of the home webpage is found on the right hand side - for illustration only - from August 2014. Below this image is a link to the current website: www.its.dot.gov/pcb - this screen capture snapshot shows an example from the Office of the Assistant Secretary for Research and Development - 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 a section labeled Free Training. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb.)
Slide 3:
A306b: Specifying Requirements for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard v03
Slide 4:
Instructor
James J. Frazer
President
Gridaptive Technologies
Pompano Beach, FL, USA
Slide 5:
Learning Objectives
Slide 6:
Learning Objective 1
Slide 7:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Structure of NTCIP 1213 v03
Slide 8:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Capabilities of NTCIP 1213 Systems
Control and monitoring of terminal devices for:
Slide 9:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Capabilities of NTCIP 1213 Systems - System Configurations
(Extended Text Description: Author's relevant description: This slide has a graphic of a Traffic management center on the left, field devices represented by streetlight images on the right and a gateway / embedded computer image in the center. Two arrows show that NTCIP 1213 communications can occur between the TMC and the gateway as well as between the TMC and the streetlights themselves.)
© 2017 Jim Frazer
Slide 10:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Capabilities of NTCIP 1213 Systems - US DOT Framework
(Extended Text Description: Author's relevant description: This slide has a graphic of vehicles and streetlights on the bottom and a traffic management center on the upper left. Arrows describe NTCIP 1213 communications from the TMC to the streetlights as well as communications from the connected vehicles to the streetlights.)
Slide 11:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Capabilities of NTCIP 1213 Systems - U.S. Smart Grid Framework
(Extended Text Description: Author's relevant description: This slide has a graphic of the NIST Smart Grid Framework, multiple arrows show NTCIP 1213 communications between customers, service providers, operation personnel, energy markets and managers of the distribution system.)
Slide 12:
Components of the Standard:
ConOps, Requirements, Dialogs, MIB, PRL, RTM
Structure of the NTCIP 1213 Standard -Missing Components of the Standard
Slide 13:
Focus on Requirements
From User Needs to Functional Requirements
Slide 14:
Relationship to the Previous Step (User Requirements)
User Needs and Functional Requirements
Slide 15:
Review the User Requirements Step, As Needed
User Needs: A Review
Slide 16:
Slide 17:
Question
Which choice is not a capability of the NTCIP 1213 standard?
Answer Choices
Slide 18:
Review of Answers
a) Roadway lighting, including scheduling and zoning
Incorrect. This is a core capability of NTCIP 1213.
b) Safety: electrical leakage anomalies, including power quality and ground fault issues
Incorrect. This is a core capability of NTCIP 1213.
c) Revenue grade power metering
Incorrect. This is a core capability of NTCIP 1213.
d) The physical size of electrical cabinets
Correct! NTCIP 1213 does not support sizing of electrical cabinets.
Slide 19:
Learning Objectives
Slide 20:
Learning Objective 2
Slide 21:
How You Get Off-the-Shelf Interoperability
Use the PRL
Slide 22:
How You Get Off-the-Shelf Interoperability
Use the PRL to Ensure Interoperability
A Section of the PRL Table
Protocol Requirements List (PRL) Table | ||||||
User Need ID | User Need | FR ID | Functional Requirement | Conformance | Support | Additional Specifications |
---|---|---|---|---|---|---|
2.5.2.1.21 | Configure ELMS Device for Adaptive Operation | 0 | Yes / No | |||
3.5.4.23 | Configure ELMS Device for Adaptive Operation | 0 | Yes / No | |||
3.5.4.23.1 | Configure Connected Vehicle Speed Setpoint | 0 | Yes / No | |||
3.5.4.23.2 | Configure Connected Vehicle Direction Setpoint | 0 | Yes / No | |||
3.5.4.23.3 | Configure Connected Vehicle Location Setpoint | 0 | Yes / No | |||
3.5.4.23.4 | Configure Connected Vehicle Ambient Light Level Setpoint | 0 | Yes / No | |||
3.5.4.23.5 | Configure Connected Vehicle Headlight Status Setpoint | 0 | Yes / No | |||
3.5.4.23.6 | Configure Connected Vehicle Road Friction Setpoint | 0 | Yes / No |
Slide 23:
How You Get Off-the-Shelf Interoperability
User Needs in the PRL Table
(Extended Text Description: This slide contains the table shown on Slide 22, with the following column highlighted in red: User Need ID.)
Slide 24:
How You Get Off-the-Shelf Interoperability
User Needs in the PRL Table
(Extended Text Description: This slide contains the table shown on Slide 22, with the following column highlighted in red: User Need.)
Slide 25:
How You Get Off-the-Shelf Interoperability
User Need - Retrieve Luminaire Information
2.5.2.1.21
Configure ELMS Device for Adaptive Operation
A management station may need to configure the ELMS device for adaptive operation. Adaptive operation includes adjusting light levels based on ambient light levels, as well as connected vehicle sensor and status information.
Slide 26:
How You Get Off-the-Shelf Interoperability
Use the PRL to Trace User Needs to Requirements
Functional Requirement Identifier
(Extended Text Description: This slide contains the table shown on Slide 22, with the following column highlighted in red: FR ID.)
Slide 27:
How You Get Off-the-Shelf Interoperability
Use the PRL to Trace User Needs to Requirements
Functional Requirements Column
(Extended Text Description: This slide contains the table shown on Slide 22, with the following column highlighted in red: Functional Requirement.)
Slide 28:
How You Get Off-the-Shelf Interoperability
Requirements for Retrieve Luminaire Information
3.5.4.23.3
Configure Connected Vehicle Location Setpoint
The ELMS device shall allow a management station to configure the connected vehicle location setpoint from within the ELMS device.
Slide 29:
Within a PRL, Selecting a Given Range of a Performance Requirement (Collecting Information)
Examining the PRL's Project Criteria
Supplemental Requirement ID | Supplemental Requirement | Conformance | Project Requirement | Additional Project Requirements |
---|---|---|---|---|
3.5.5 | Supplemental Requirements for Live Data | M | Yes | |
3.5.5.1 | Live Data Response Time | M | Yes | The device shall initiate the transmission of the appropriate response (assuming that the device has permission to transmit) within 125 milliseconds of receiving the last byte of the request, plus 1 millisecond for each byte in the response variable-bindings field |
Slide 30:
Supporting Project Requirements
Completing the PRL
By compiling your project-specific User Needs and examining the dependent functional requirements, you can select which optional features are to be required in your project-specific implementation.
Slide 31:
Conformance to the Standard
Conformance Column in the PRL
(Extended Text Description: This slide contains the following table, with the bottom four rows of the Conformance column highlighted in red:
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 |
)
Slide 32:
Slide 33:
Question
Which of the below is not a reason to use the PRL?
Answer Choices
Slide 34:
Review of Answers
a) To identify User Needs
Incorrect. The PRL does include User Needs.
b) To perform a test for compliance
Correct! Testing is not part of the NTCIP 1213 Standard v03, but must be designed and documented during the project.
c) To identify Functional Requirements
Incorrect. The PRL does include Functional Requirements.
d) To develop a project-specific specification
Incorrect. The PRL is used to develop a project-specific specification.
Slide 35:
Learning Objectives
Slide 36:
Learning Objective 3
Slide 37:
Properly Tracing User Needs to Requirements
User Need/Functional Requirement Relationship
Slide 38:
Slide 39:
Completing the Project-Level PRL
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.
Slide 40:
Completing the Project-Level PRL
Using the PRL to Build a Specification: Washington State DOT Case Study
These User Needs include the ability to:
Slide 41:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
These User Needs do not include the ability to:
Photo: Gridaptive Technologies
Slide 42:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Live Data
User Need ID | User Need | FR ID | Functional Requirement | Conformance | Project Requirement | Additional Project Requirements |
---|---|---|---|---|---|---|
24.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 43:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Off-Line Log Data
(Extended Text Description: This slide contains the following table with the word Yes circled in red on the first row:
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 |
)
Slide 44:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Luminaire Switch State Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 45:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Luminaire Lamp Condition Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 46:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Luminaire Burn Condition Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 47:
Completing the Project-Level PRL
Using the PRL to Build a Specification: Washington State DOT Case Study
Provide Periodic Luminaire Burn Time Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 48:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Periodic Luminaire Temperature Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
2.4.1.2.5 | Provide Luminaire Temperature Logging | 0 | Yes / No | |||
3.3.2.10.6 | Luminaire Temperature Log | 0 | Yes / No |
)
Slide 49:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Periodic Luminaire Pole Condition Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 50:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Relay Switch State Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
2.4.1.27 | Provide Relay Switch State Logging | 0 | Yes / No | |||
3.3.2.10.8 | Relay Switch State Log | 0 | Yes / No |
)
Slide 51:
Completing the Project-Level PRL
Using the PRL to Build a Specification:
Washington State DOT Case Study
Provide Power Meter Switch State Logging
(Extended Text Description: This slide contains the following table with the word No circled in red on the first row:
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 |
)
Slide 52:
Completing the Project-Level PRL
Washington State DOT Case Study - Summary
Slide 53:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Slide 54:
Use of PRL to Communicate Dialogs and Messages With SNMP
Using the Requirements Traceability Matrix (RTM)
Requirement ID Column
(Extended Text Description: This slide contains the following table with the Requirement ID column highlighted in red:
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 |
)
Slide 55:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Requirement Column
(Extended Text Description: This slide contains the following table with the Requirement column highlighted in red:
Requirement ID | Requirement | Dialog ID | Dialog | Object ID | Object |
---|---|---|---|---|---|
3.4.1.3.1 | Configure Luminaire for Light Activated Operations | ||||
4.2.3 | Genenc SNMP Set Interface | ||||
5.4.1.3 | luminaireMode | ||||
5.4.1.15 | luminaireLightThreshold | ||||
5.4.1.16 | lurninaireHoldInterval | ||||
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 | electncalserviceMode | ||||
5.5.1.9 | electricalserviceLightThreshold | ||||
5.5.1.20 | electricalserviceHoldInterval | ||||
5.5.1.21 | electricaberviceLightHysieresis | ||||
5.5.1.22 | electricalserviceDelayInterval |
)
Slide 56:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Dialog ID Column
(Extended Text Description: This slide contains the same table as Slide 55 with the Dialog ID column highlighted in red.)
Slide 57:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Dialog Column
(Extended Text Description: This slide contains the same table as Slide 55 with the Dialog column highlighted in red.)
Slide 58:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Object ID Column
(Extended Text Description: This slide contains the same table as Slide 55 with the Object ID column highlighted in red.)
Slide 59:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Object Column
(Extended Text Description: This slide contains the same table as Slide 55 with the Object ID column highlighted in red.)
Slide 60:
Use of PRL to Communicate Dialogs and Messages with SNMP
Using the Requirements Traceability Matrix (RTM)
Summarizing the RTM:
The RTM
Slide 61:
Use of PRL to Communicate Dialogs and Messages with
SNMP
Using the Requirements Traceability Matrix (RTM)
How to Compare for Interoperability:
Slide 62:
Use of PRL to Communicate Dialogs and Messages with
SNMP
Using the Requirements Traceability Matrix (RTM)
Comparison of PRLs for Interoperability and Interchangeability:
(Extended Text Description: Author's relevant description: This slide includes an image of a data object at the traffic management center and a data object at the field device. An arrow labeled "NTCIP" denotes NTCIP communications between the two objects.)
Slide 63:
Use of PRL to Communicate Dialogs and Messages with
SNMP
Using the Requirements Traceability Matrix (RTM)
Comparison of PRLs for Interoperability:
Slide 64:
Use of PRL to Communicate Dialogs and Messages with
SNMP
Using the Requirements Traceability Matrix (RTM)
Comparison of PRLs for Interchangeability
Slide 65:
Slide 66:
Question
What does the following table mean?
(Extended Text Description: This slide contains the following table:
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 | luminaireHoldlnterval | ||||
5.4.1.17 | luminaireLightHysteresis | ||||
5.4.1.18 | luminaireDelaylnterval |
)
Slide 67:
Review of Answers
a) All of the objects must be supported
Incorrect. They only need to be supported if the requirement has been selected in the PRL.
b) All of the objects must be supported if the requirement is supported
Correct!
c) At least one of the objects must be supported
Incorrect. If the requirement is selected, all of the objects must be supported.
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 68:
Learning Objectives
Slide 69:
Learning Objective 4
Slide 70:
User Needs-Requirements Link
Extending the Standard
Slide 71:
Using Requirements Not Covered by the ELMS Standard
Extending the Standard Complicates Interoperability and Interchangeability
Slide 72:
Using Requirements Not Covered by the ELMS Standard
Extending the Standard Complicates Interoperability and Interchangeability
Extensions should only be considered when:
Slide 73:
Using Requirements Not Covered by the ELMS Standard
Extending the Standard Complicates Interoperability and Interchangeability
Extended equipment should be designed to:
Slide 74:
Slide 75:
Question
Which of the choices below is a reason to extend an ELMS system specification?
Answer Choices
Slide 76:
Review of Answers
a) The existing system uses a nonstandard method
Incorrect. Doing this will prolong the expensive customized approach for another generation.
b) There is an unmet need that justifies the added cost
Correct! Sometimes you just have to accept the added cost.
c) You want to use your specification to favor a specific vendor
Incorrect. This can trap you into a proprietary solution.
d) 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 77:
Module Summary
Slide 78:
We Have Now Completed A306a and A306b in the ELMS Curriculum
Module A306a:
Understanding User Needs for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard v03
Module A306b:
Specifying Requirements for Electrical and Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard v03
Module T306:
Applying Your Test Plan for Electrical and Lighting Management Systems Based on NTCIP 1213 ELMS Standard v03
Slide 79:
Next Course Module
Module T306: Applying Your Test Plan for Electrical and Lighting Management Systems Based on NTCIP 1213 v03 Standard
Concepts taught in next module (Learning Objectives):
Slide 80:
Thank you for completing this module.
Feedback
Please use the Feedback link below to provide us with your thoughts and comments about the value of the training.
Thank you!