Post on 15-Apr-2017
Welcome
Ken Leonard, DirectorITS Joint Program OfficeK L d@d tKen.Leonard@dot.gov
www.pcb.its.dot.gov
A306b: Specifying Requirements for Electrical and
Lighting Management Systems (ELMS) Based on NTCIP 1213 Standard
4
Instructorst ucto
James J. FrazerPresidentGridaptive TechnologiesPompano Beach Florida USAPompano Beach, Florida, USA
5
Target Audiencea get ud e ce
E i i t ff Engineering staff Street lighting maintenance staff TMC/Operations staff System developers Private and public sectors users including manufacturers
6
Recommended Prerequisite(s)eco e ded e equ s te(s) I101: Using ITS Standards: An Overview
A101: Introduction to Acquiring Standards-based ITS q gSystems
A102: Introduction to User Needs Identification
A201: Details On Acquiring Standards-based ITS Systems
C101: Introduction to the Communications Protocols and Their Uses in ITS Applications
A306a: Understanding User Needs for Electrical and Li hti M t S t (ELMS) B d NTCIPLighting Management Systems (ELMS) Based on NTCIP 1213 Standard
7
Curriculum Path (SEP)I101
Using ITS Standards: An Overview
A101Introduction to
Acquiring Standards ‐based
ITS Systems
A102Introduction to User Needs IdentificationITS Systems
A201 C101A201Details on Acquiring Standards‐based ITS
Systems
Intro. to Comm. Protocols
and Their Use in ITSApplications
A306aUnderstanding User Needs for
El i l d Li h i
A306bSpecifying Requirements for
El i l d Li h iElectrical and LightingManagement Systems(ELMS) Based on NTCIP
1213 Standard
Electrical and LightingManagement Systems(ELMS) Based on NTCIP
1213 Standard
8
Learning Objectivesea g Object es
1. Review the structure of the NTCIP 1213 v02 Standard2. Use the Protocol Requirements List (PRL) to specify
the standardized structure of requirements 3. Include the requirements from the PRL in the3. Include the requirements from the PRL in the
specification4. Explain how interoperability is achieved through the
Requirements Traceability MatrixRequirements Traceability Matrix5. Examine the benefits of the SEP approach regarding
verification and validation in the ELMS testing process6. Explain conditions and context for extending the
standard including specifying requirements not covered by standard
9
covered by standard
Learning Objective # 1 – Review the ea g Object e # e e t eStructure of the NTCIP 1213 Standard
Summarize NTCIP 1213 Capabilities Identify components of the standard, ConOps, y p , p ,Requirements, Dialogs, MIB, PRL, RTM Focus on Requirements State what this standard does not have (e.g., test cases)
10
Capabilities of NTCIP 1213 Systems
Learning Objective # 1
Capab t es o C 3 Syste sControl and monitoring of terminal devices for:
Roadway lighting, including scheduling and zoning Safety: electrical leakage anomalies, including power
lit d d f lt iquality and ground fault issues Revenue grade power metering
11
Capabilities of NTCIP 1213 Systems
Learning Objective # 1
Capab t es o C 3 Syste s
Integration ith other s stems incl dingIntegration with other systems including:
Vehicle to Grid Infrastructure Vehicle to Grid Infrastructure The electrical distribution network (The Smart Grid) Electric vehicle charging infrastructureg g
12
NTCIP 1213 System Configurations
Learning Objective # 1
C 3 Syste Co gu at o s
13
Graphics: Gridaptive Technologies
The US Smart Grid Framework
Learning Objective # 1
e US S a t G d a e o
S bhead (Arial Bold 28 PT GreenSubhead (Arial Bold 28 PT Green)
Text (Arial 24 PT Black)
Bullets Bullet 1
NTC Bullet 1
Bullet 2 Bullet 2
CIP 1213
Sub bullets
15
Structure of the NTCIP 1213 Standard
Learning Objective # 1
St uctu e o t e C 3 Sta da dComponents of the Standard
Section 1: General Section 2: Concept of Operations
S ti 3 F ti l R i t Section 3: Functional Requirements Section 4: Dialog Specifications Section 5: Electrical and Lighting Management System Section 5: Electrical and Lighting Management System Master Object Definitions
16
Structure of the NTCIP 1213 Standard (Cont.)
Learning Objective # 1
St uctu e o t e C 3 Sta da d (Co t )Components of the Standard
Annex A: Requirements Traceability Matrix (RTM) Annex B: Object Tree
A C R i d Obj t D fi iti f A t i l Annex C: Revised Object Definitions for Astronomical Clock
17
Missing Components of NTCIP 1213
Learning Objective # 1
ss g Co po e ts o C 3Test Cases
Does not include Test Cases Need to be produced for each project
F t ti l i For more on testing, please examine: T101: Introduction to ITS Standards Testing T201: How to Write a Test Plan T201: How to Write a Test Plan T202 Overview of Test Design Specifications, Test Cases, and Test Procedures
18
Learning Objective # 1
Which choice is not a capability of the NTCIP 1213 standard?
Answer Choices
a) Roadway lighting, including scheduling and zoning b) S f l i l l k li i l dib) Safety: electrical leakage anomalies, including power
quality and ground fault issues c) Revenue grade power meteringc) Revenue grade power metering d) Wiring specifics
20
Learning Objective # 1
Review of answersa) Roadway lighting, including scheduling and zoning
Incorrect This is a core capability of NTCIP 1213Incorrect. This is a core capability of NTCIP 1213.
b) Safety: electrical leakage anomalies, including power quality and ground fault issuespower 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) Wiring specificsCorrect. NTCIP 1213 does not support wiring
21
specifics.
Summary of Learning Objective # 1Su a y o ea g Object e #Review the Structure of the NTCIP 1213 Standard
We summarized the capabilities of the NTCIP 1213 standard1213 standard We identified the components of the standard We focused on requirementsWe focused on requirements We stated what this standard does not have
22
Learning Objective # 2 – Use the Protocol g jRequirements List (PRL) to specify the standardized structure of requirements q
The PRL is a table that is a tool included in the fstandard for use by the system developers, agency
specifiers, and producers of ELMS equipment
Properly trace user needs to requirements
Within a PRL, select a given range of a f i t
23
performance requirement
Use the PRL to Trace User Needs to
Learning Objective # 2
Use t e to ace Use eeds toRequirementsA S bset of the PRL TableA Subset of the PRL Table
24
Source: NTCIP 1213
Use the PRL to Trace User Needs to
Learning Objective # 2
Use t e to ace Use eeds toRequirementsUser Need IDs in the PRL TableUser Need IDs in the PRL Table
25
Use the PRL to Trace User Needs to
Learning Objective # 2
Use t e to ace Use eeds toRequirementsUser Needs in the PRL TableUser Needs in the PRL Table
26
An Example User Need –
Learning Objective # 2
a p e Use eedRetrieve Luminaire InformationE amining User Need 2 4 2 1 1 1Examining User Need 2.4.2.1.1.1
2.4.2.1.1.1 Retrieve Luminaire InformationTh t d t b bl t d t i thThe 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, g p ,locations, modes, zones, and vendor information for each luminaire.
27
Use the PRL to Trace User Needs to
Learning Objective # 2
Use t e to ace Use eeds toRequirementsThe F nctional Req irement IdentifierThe Functional Requirement Identifier
28
Use the PRL to Trace User Needs to
Learning Objective # 2
Use t e to ace Use eeds toRequirementsThe F nctional Req irements Col mnThe Functional Requirements Column
29
Requirements for Retrieve Luminaire
Learning Objective # 2
equ e e ts o et e e u a eInformationE amining 3 4 1 1 1 1Examining 3.4.1.1.1.1
3.4.1.1.1.1 Retrieve Luminaire Pole Identifier3.4.1.1.1.1 Retrieve Luminaire Pole IdentifierA management station shall able to retrieve from the ELMS device the pole identifier to which a luminaire is attachedattached.
30
Requirements for Retrieve Luminaire
Learning Objective # 2
equ e e ts o et e e u a eInformation3 4 1 1 1 2 Retrieve Luminaire Location A management3.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/Latitude3.4.1.1.1.2.1 Specify Location in Longitude/Latitude3.4.1.1.1.2.2 Specify Location Information Using Textual Description of a Road / Street / Block Name / Number3 4 1 1 1 2 3 Specify Location in Local Reference3.4.1.1.1.2.3 Specify Location in Local Reference Coordinate Grid
31
Requirements for Retrieve Luminaire
Learning Objective # 2
equ e e ts o et e e u a eInformation3 4 1 1 1 3 Retrieve Luminaire Mode A management3.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 astation 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 A3.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
32
luminaire from the ELMS device.
ELMS Requirements are “Well-formed”
Learning Objective # 2
S equ e e ts a e e o ed
[Actor] [Action] [Target] [Constraint] [Localization]
Actor – Identifies who or what does the actionAction – Identifies what is to happenT t Id tifi h h t i th tiTarget – Identifies who or what receives the actionConstraint – Identifies how to measure success or failure of the requirementqLocalization – Identifies the circumstances under which the requirement appliesLocalization and constraint portions are important but not allLocalization and constraint portions are important, but not all requirements will have both.
33
Example of an ELMS Requirement
Learning Objective # 2
a p e o a S equ e e tA management station shall be able to retrieve the location of the luminaire from the ELMSthe location of the luminaire from the ELMS device
Actor management stationActor - management station Action - be able to retrieveTarget - the ELMS deviceConstraint - location of the luminaire
34
Section 3 Functional Requirements
Learning Objective # 2
Sect o 3 u ct o a equ e e ts
3.1 Tutorial [Informative]3 2 P t l R i t Li t (PRL)3.2 Protocol Requirements List (PRL)3.3 Operational Environment Requirements3.4 Functional Requirements3.5 Supplemental Requirements
35
Section 3.3 Operational Environment
Learning Objective # 2
Sect o 3 3 Ope at o a o e tRequirements
3.3.1 Provide Live Data3 3 2 Provide Off-Line Log Data3.3.2 Provide Off Line Log Data3.3.3 Monitor Exceptional Conditions
36
Section 3.4 Functional Requirements
Learning Objective # 2
Sect o 3 u ct o a equ e e ts
3.4.1 Configure ELMS Device3 4 2 C t l D i3.4.2 Control Device3.4.3 Monitor Device Status
37
Section 3.5 Supplemental Requirements
Learning Objective # 2
Sect o 3 5 Supp e e ta equ e e ts
3.5.1 Supplemental Requirements for Scheduled Operations3 pp q p3.5.2 Supplemental Requirements for Zones3.5.3 Supplemental Requirements for Dim Levels3 5 4 Supplemental Requirements for Event Logs3.5.4 Supplemental Requirements for Event Logs3.5.5 Supplemental Requirements for Live Data
38
Learning Objective # 2
Which of the following is not a major group of requirements in NTCIP 1213?
Answer Choices
a) Configure ELMS Device b) C l D ib) Control Device c) Monitor Device Status d) Backwards Compatibility Requirementsd) Backwards Compatibility Requirements
40
Learning Objective # 2
Review of answersa) Configure ELMS Device
Incorrect. These requirements provide for fi i ELMS fi ld d iconfiguring ELMS field devices.
b) Control Device Incorrect These requirements provide forIncorrect. These requirements provide for controlling the ELMS field device.
c) Monitor Device Status Incorrect. These requirements provide for monitoring alarms and device status.
d) B k d C tibilit R i td) Backwards Compatibility Requirements Correct. As the first published version of the standard, it does not have any backwards
41
, ycompatibility issues with which to deal.
Including PRL Requirements in the
Learning Objective # 2
c ud g equ e e ts t eELMS Specification:ConformanceConformance
42
Including PRL Requirements in the
Learning Objective # 2
c ud g equ e e ts t eELMS Specification:ConformanceConformance
43
Including PRL Requirements in the ELMS
Learning Objective # 2
c ud g equ e e ts t e SSpecification:Project Req irementsProject Requirements
44
Including PRL Requirements in the ELMS
Learning Objective # 2
c ud g equ e e ts t e SSpecification:Project Req irementsProject Requirements
45
Examining the PRL's Additional Project
Learning Objective # 2
a g t e s dd t o a ojectRequirements:Performance CriteriaPerformance Criteria
125
46
Summary of Learning Objective #2 Su a y o ea g Object e #Use the Protocol Requirements List (PRL) to specify the standardized structure of p yrequirements.
To properly trace user needs to requirementWithin a PRL, to select a given range of a performance
47
Learning Objective # 3 – How to Include the g jRequirements from the PRL in the Specification
How to compare and contrast vendor PRLs for off-the-shelf interoperability analysis
Explain how it fits into the big picture
E plain ho ELMS fits in the smart grid infrastr ct re Explain how ELMS fits in the smart grid infrastructure
Properly tracing User Needs to Requirements
Creating a Specification, Overview, Contents, and Considerations
48
Considerations
Using the PRL to Build a Specification:
Learning Objective # 3
Us g t e to u d a Spec cat oWashington State DOT Case Study
In preparing the communications interface specification for a large p gbridge and tunnel project, many user needs were identified.
49
Using the PRL to Build a Specification:
Learning Objective # 3
Us g t e to u d a Spec cat oWashington State DOT Case StudyThese Needs Included the Ability to:
Control lighting system lumen output by current ambient light level (adaptive lighting)
y
light level (adaptive lighting) Control lighting fixtures by zones of branch circuits Configure branch circuits into alternate zonesConfigure branch circuits into alternate zones Configure, control, and monitor branch circuits Configure schedules for branch circuit zones Report exceptional conditions in a near real-time basis Override schedules as required
50
Using the PRL to Build a Specification:
Learning Objective # 3
Us g t e to u d a Spec cat oWashington State DOT Case StudyThese Needs Do Not Incl de the Abilit to
Configure, control, or monitor
These Needs Do Not Include the Ability to:
Luminaires Electrical services Ground fault equipment Arc fault equipment
Provide Smart Grid information Provide Smart Grid information to the local electric utility
G
51
Photo: Gridaptive Technologies
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Li e DataProvide Live Data
52
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Off Line Log DataProvide Off-Line Log Data
53
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide L minaire S itch State LoggingProvide Luminaire Switch State Logging
54
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide L minaire Lamp Condition LoggingProvide Luminaire Lamp Condition Logging
55
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide L minaire B rn Condition LoggingProvide Luminaire Burn Condition Logging
56
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Periodic L minaire B rn Time LoggingProvide Periodic Luminaire Burn Time Logging
57
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Periodic L minaire Temperat re LoggingProvide Periodic Luminaire Temperature Logging
58
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Periodic L minaire Pole ConditionProvide Periodic Luminaire Pole Condition Logging
59
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Rela S itch State LoggingProvide Relay Switch State Logging
60
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Po er Meter S itch State LoggingProvide Power Meter Switch State Logging
61
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Periodic Po er Meter Meas rementProvide Periodic Power Meter Measurement Logging
62
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Po er Meter Condition LoggingProvide Power Meter Condition Logging
63
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Gro nd Fa lt S itch State LoggingProvide Ground Fault Switch State Logging
64
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLPro ide Periodic Gro nd Fa lt Meas rementProvide Periodic Ground Fault Measurement Logging
65
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLRetrie e Logged DataRetrieve Logged Data
66
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLMonitor E ceptional ConditionsMonitor Exceptional Conditions
67
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLFeat resFeatures
68
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re ELMS De iceConfigure ELMS Device
69
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re L minaireConfigure Luminaire
70
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLRetrie e L minaire InformationRetrieve Luminaire Information
71
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re L minaire Identification InformationConfigure Luminaire Identification Information
255
72
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re L minaire ModeConfigure Luminaire Mode
73
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Electrical Ser iceConfigure Electrical Service
/ No
74
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLRetrie e Electrical Ser ice InformationRetrieve Electrical Service Information
75
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re for Light Acti ated OperationConfigure for Light-Activated Operation
76
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re for Sched led OperationConfigure for Scheduled Operation
77
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re ZonesConfigure Zones
78
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re for Man al OperationConfigure for Manual Operation
79
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Stagger Inter alConfigure Stagger Interval
80
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Dim Le elsConfigure Dim Levels
81
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Electrical Ser ice Monitoring andConfigure Electrical Service Monitoring and Metering Equipment
82
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Branch Circ itConfigure Branch Circuit
83
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLRetrie e Branch Circ it InformationRetrieve Branch Circuit Information
84
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLConfig re Branch Circ itConfigure Branch Circuit
85
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLControl De iceControl Device
86
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLControl L minaireControl Luminaire
87
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLControl Electrical Ser iceControl Electrical Service
88
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLControl Branch Circ itControl Branch Circuit
89
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLControl De ices B ZoneControl Devices By Zone
90
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLMonitor De ice Stat sMonitor Device Status
91
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLMonitor L minaireMonitor Luminaire
92
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLMonitor Electrical Ser iceMonitor Electrical Service
93
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLMonitor Branch Circ itMonitor Branch Circuit
94
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irementsSupplemental Requirements
95
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irements for Sched ledSupplemental Requirements for Scheduled Operations
255
255
96
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irements for ZonesSupplemental Requirements for Zones
100999
97
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irements for Dim Le elsSupplemental Requirements for Dim Levels
98
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irements for E ent LogsSupplemental Requirements for Event Logs
255
255
255
99
Building Project Specifications
Learning Objective # 3
u d g oject Spec cat o sUsing the PRLS pplemental Req irements for Li e DataSupplemental Requirements for Live Data
152
100
Using the PRL in a Specification
Learning Objective # 3
Us g t e a Spec cat oAs Part of the Interface Specification
A completed PRL defines the requirements for the NTCIP interface
A deployment may need multiple interface specificationso Management systems that support multiple deviceso Management systems that support multiple deviceso May need support for legacy protocol
101
Using the PRL in a Specification
Learning Objective # 3
Us g t e a Spec cat oCompare and contrast vendor PRLs for off-the-shelf interoperability analysisy y
Once your project specific PRL is complete, you can use it to determine:it to determine:
If off-the-shelf solutions are available Which vendor’s product fits your application bestp y pp Whether custom development is required Which vendor’s products are interoperable, and exactly which features are interoperable
102
Using the PRL in a Specification
Learning Objective # 3
Us g t e a Spec cat o
Consistency
The interface specificationThe interface specification must be consistent with the remainder of the specification
103
Using the PRL in a Specification
Learning Objective # 3
Us g t e a Spec cat oSample Text for Use in a Specification
The PRL should be properly introduced within the specification.
A copyright disclaimer should appear with the PRL.
Refer to the student supplement for guidance on wording used to introduce the PRL.
104
Learning Objective # 3
Which choice is not a functional requirement contained in the NTCIP 1213 PRL?
Answer Choices
a) Retrieve luminaire locationb) C fi l i i db) Configure luminaire modec) Configure branch circuit zoned) Retrieve wiring particularsd) Retrieve wiring particulars
106
Learning Objective # 3
Review of answersa) Retrieve luminaire location
Incorrect. This is a functional requirement of NTCIP 1213NTCIP 1213.
b) Configure luminaire modeIncorrect This is a functional requirement ofIncorrect. This is a functional requirement of NTCIP 1213.
c) Configure branch circuit zoneIncorrect. This is a functional requirement of NTCIP 1213.
d) R t i i i ti ld) Retrieve wiring particularsCorrect. NTCIP 1213 does not support retrieval of wiring particulars.
107
g p
Summary of Learning Objective # 3 Su a y o ea g Object e # 3How to include the requirements from the PRL in the specification
We demonstrated how to compare and contrast vendor PRLs for off-the-shelf interoperability analysis.PRLs for off the shelf interoperability analysis. We explained how ELMS fits in the smart grid infrastructure architecture.We properly traced user needs to requirements.We created a specification, overview, contents, and considerationsconsiderations.
108
Learning Objective # 4 – Explain How Interoperability is Achieved through the Requirements Traceability Matrix
Explain source requirement and how it is selected in RTM Explain source requirement and how it is selected in RTM
Explain link to dialogs, objects, and block objects
Learn how dialogs and messages in RTM are communicated to the field device using SNMP
Provide complete description of how a specification is to be created to support the complete end-to-end example
Provide example of how monitoring of ELMSs work
109
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)Achie ing Interoperabilit andAchieving Interoperability and Interchangeability
How the RTM traces to a single design Annex A contains the RTM The RTM maps requirements to a specific design
How to compare for interoperability How to compare for interchangeability How to compare for interchangeability
110
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Req irement ID Col mnThe Requirement ID Column
111
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Req irement Col mnThe Requirement Column
112
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Dialog ID Col mnThe Dialog ID Column
113
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Dialog Col mnThe Dialog Column
114
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Object ID Col mnThe Object ID Column
115
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)The Object Col mnThe Object Column
116
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)S mmari ing the RTMSummarizing the RTM
The RTMThe RTM Maps each requirement to one specific design Is a precise dialogp g Is a precise list of objects All of the objects must be supported if the requirement is supported
117
Using the Requirements Traceability
Learning Objective # 4
Us g t e equ e e ts aceab tyMatrix (RTM)Ho to Compare for InteroperabilitHow to Compare for Interoperability
Th RTM id i t bilit f i t The RTM provides interoperability of requirements
The PRL indicates which requirements are supported The PRL indicates which requirements are supported
Comparison of PRLs allow quick determination of p qinteroperability
118
Learning Objective # 4
Comparison of PRLsCo pa so o sFor Interoperability and Interchangeability
119
Comparison of PRLs
Learning Objective # 4
Co pa so o sFor Interoperability
If both the TMS and the ELMS support a feature Interoperability is provided
If th TMS t b t ELMS d t If the TMS supports, but ELMS does not TMS can still use other features (typically) TMS can still interoperate with feature with other pdevices
If ELMS supports, but TMS does notF t ld b d b th /f t TMS Feature could be used by other/future TMS
Feature can potentially be used manually
120
Comparison of PRLs
Learning Objective # 4
Co pa so o sFor Interchangeability
Both support a feature Equipment is interchangeable for feature
N i t t ld d t New equipment supports; old one does not New equipment is interchangeable (meets or exceeds))
Old equipment supports; new ones do not Feature will not be supported
I f t d d? Is feature needed?
121
Learning Objective # 4
What does the following table mean?
a) All of the objects m st be s pportedAnswer Choicesa) All of the objects must be supportedb) At least one of the objects must be supportedc) All of the objects must be supported if the requirement isc) All of the objects must be supported if the requirement is
supportedd) At least one of the objects must be supported if the
123
requirement is supported
Learning Objective # 4
Review of answersa) All of the objects must be supported
Incorrect. They only need to be supported if the i t h b l t d i th PRLrequirement has been selected in the PRL.
b) At least one of the objects must be supportedIncorrect If the requirement is selected all of theIncorrect. If the requirement is selected, all of the objects must be supported.
c) All of the objects must be supported if the requirement is supportedCorrect.
d) At l t f th bj t t b t d if thd) At least one of the objects must be supported if the requirement is supportedIncorrect. If the requirement is supported, all of
124
q pp ,the objects must be supported.
NTCIP 1213 Dialogs
Learning Objective # 4
C 3 a ogsA Basic Dialog between the TMS and the ELMS
Request
Response
125
NTCIP 1213 Dialogs
Learning Objective # 4
C 3 a ogsDialog Example: Configuring a Schedule
Action
Day Plan
Time Base ScheduleTime Base Schedule
126
Source: NTICP 1213
Summary of Learning Objective #4 Su a y o ea g Object e #Explaining Interoperability and the RTM
W l i d i t d h th We explained source requirements and how they are selected in the RTM. We examined links to dialogs, objects, and block objects.e e a ed s to d a ogs, objects, a d b oc objects We described how a specification is created to support the complete end-to-end example, from user need to dialog on th ithe wire.We discussed how monitoring of ELMS is accomplished.
128
Learning Objective # 5 – Examine the ea g Object e # 5 a e t ebenefits of the SEP approach
Benefits in developing a test plan Benefits of testing using SEP
Benefits to agencies Benefits to agencies Benefits to vendors
129
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oac
The Benefits in Developing a Test Planp g
Verify that requirements are fulfilled Reduce the risk of misinterpretation between agency and manufacturers
R d th i k f fi i l i t Reduce the risk of financial mismanagement Reduce the risk of perceived lack of oversight Ensure interoperability to allow system expansion Ensure interoperability to allow system expansion
130
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits of Testing Using SEP
Validation: Making sure a system, when placed in operation, will support agency needs
Verification: Making sure a design complies with requirements and that the systems (as proposed and delivered) comply with both design and requirementsdelivered) comply with both design and requirements
Traceability: A tool to help determine if the agency’s requirements are fulfilled by the design and thatrequirements are fulfilled by the design and that implementation was done correctly
Used for unit, subsystem, and system testing
131
Used for unit, subsystem, and system testing
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits of Testing Using SEP
U it/D i T ti Unit/Device Testing Focuses on comparing an implementation against the standards and specified options p p May be performed by inspecting the code to use “proven” software to send test messages to the device
Subsystem Testing Consists of connecting two or more devices together
d h i d tand exchanging data Assumes devices and components have passed a designed unit test plan
132
g
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits of Testing Using SEP
S t T ti System Testing Highest level of testing Performed after all lower level testing is successfully g ycompleted Performed in an operational environment Includes acceptance testing Includes acceptance testing
133
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits of Testing Using SEP
134
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits of Testing Using SEP
Provides the framework and process to verify that the system meets the user needs Improves stakeholder participation Improves stakeholder participation Results in more adaptable, resilient systems Verifies functionality and fewer defectsVerifies functionality and fewer defects Results in higher level of reuse in future projects Results in better documentation
135
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits to Agencies
Users including transportation and electric utility specification developers can use testing results to confirm which requirements have been delivered in a project specificwhich requirements have been delivered in a project specific implementation
The protocol implementer can use testing results to confirm The protocol implementer can use testing results to confirm conformance to NTCIP 1213
136
Examine the benefits of the SEP approach
Learning Objective # 5
a e t e be e ts o t e S app oacThe Benefits to Vendors
The supplier can supply testing data as a detailed indication of the capabilities of the implementation
The user can use this vendor supplied test data, as a basis for checking interoperability with another implementation
137
Summary of Learning Objective #5 Su a y o ea g Object e #5Benefits of the SEP Approach
We discussed the importance of the SEP.
W i d th b fit i d l i t t lWe examined the benefits in developing a test plan.
We reviewed the benefits to agencies including Transportation and electricity specification developers.
We reviewed the benefits to vendors.
138
Learning Objective # 6 – Extending the g j gStandard
Conditions and context for extending the standard Conditions and context for extending the standard Specify requirements not covered by the standard
Adding missing requirements identified through best practices Emphasize user needs-requirements link
139
Extending the Standard
Learning Objective # 6
Extending the StandardComplicates interoperability and interchangeabilityinterchangeability
Not achievable unless all design details are known Extensions are relatively custom solutions, resulting in:
Increased specification costsIncreased development costs Increased development costs
Increased testing costs Increased integration costs Increased integration costs Longer deployment timeframe Increased maintenance costs
140
Extending the Standard
Learning Objective # 6
te d g t e Sta da dExtensions should only be considered when:
NTCIP features are inadequate to meet need Benefits of extension outweigh added costs
141
Extending the Standard
Learning Objective # 6
te d g t e Sta da dExtended equipment should be designed to:
Appropriately integrate with NTCIP-only deployments Minimize added complexity
142
Extending the Standard Using a Custom
Learning Objective # 6
te d g t e Sta da d Us g a CustoUser Need
X.1 Custom NeedsX.1.1 Plan Selection Based on Astronomical Clock (Annex C)(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.longitude.This feature allows ELMS to ensure these conditions are managed daily.
143
Extending the Standard Using a Custom
Learning Objective # 6
te d g t e Sta da d Us g a CustoUser Need
X.2 RequirementsX.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.
144
Learning Objective # 6
Which of the following is the best reason to extend the NTCIP 1213 standard?
Answer Choices
a) There is an unmet need that justifies the added costb) Th i i d d h db) The existing system uses a non-standard methodc) You want to use your specification to favor a specific
vendorvendord) When the standardized solution is overly complex for
your simple needs
146
Learning Objective # 6
Review of answersa) There is an unmet need that justifies the added cost
Correct. Sometimes you just have to accept the dd d tadded cost.
b) The existing system uses a non-standard methodIncorrect Doing this will prolong the expensiveIncorrect. Doing this will prolong the expensive customized approach for another generation.
c) You want to use your specification to favor a specific vendor Incorrect. This can trap you into a proprietary solution.
d) Wh th t d di d l ti i l ld) When the standardized solution is overly complexIncorrect. Some NTCIP features are complex to allow flexibility, but costs of custom solutions far outweigh any
147
y, g ycosts due to added complexity.
Summary of Learning Objective #6 Su a y o ea g Object e #6Explain conditions and context for extending the Standard
We discussed specifying requirements that areth t t i l d d i th t d dthat are not included in the standard: By adding missing requirements identified through best practicesbest practices By emphasizing the user need/requirements link
148
What We Have Learned1) Components of the standards: User Needs,____________,
Dialogs, the _____and the RTM.Requirements
PRL
2) _______ and messages in the _____are communicated to the field device using ________.Dialogs RTM
SNMP
3) The protocol implementer can use testing results to confirm to NTCIP 1213 as a benefit to agenciesconformance___________to NTCIP 1213 as a benefit to agencies.
4) The RTM traces requirement to a _______design solution, thereby providing
single
conformance
interoperabilitythereby providing _____________interoperability
149
Resourcesesou ces Systems Engineering Handbook, Version 3.2, International Council on Systems Engineering, January 2010 Systems Engineering Guidebook for Intelligent Transportation Systems Version 3 0 United StatesTransportation Systems, Version 3.0, United States Department of Transportation, November 2009 The NTCIP Guide, Version 04, NTCIP 9001, 2009The NTCIP Guide, Version 04, NTCIP 9001, 2009 Object Definitions for Electrical and Lighting Management Systems, Version 2.20b, NTCIP March 2011 A306b Participant Student Supplement
150