EIS Alliance Customer Use Cases 1
1
2
Energy Information Standards (EIS) Alliance 3 Customer Domain Energy Services Interface 4
(ESI) Requirements 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
22 EIS Alliance 23
24 25 26
Version: V2.0 27
Created: 04/28/2010 28
Distribution: 2nd Public Review 29
30
EIS Alliance Customer Use Cases 2
Revision History 31
Name Date Reason For Changes Ver./Rev.
John Ruiz 3/04/10 Original 0.1
John Ruiz 3/14/10 Updated per Phoenix Mtg 0.2
John Ruiz 4/1/10 Released Draft 1.0
John Ruiz 4/28/10 Clarification of usage vs demand in ID16 1.11
John Ruiz 5/28/10 Updated for comment resolution 1.9
John Ruiz 6/10/10 Updated per EIS meeting 2.0
32
33
EIS Alliance Customer Use Cases 3
Table of Contents 34 Introduction 4 35 Glossary 5 36 Scope 7 37 Normative References 9 38
Customer Domain Information Requirements 10 39 ID1 Weather ................................................................................................................................ 10 40 ID2 Power Quality ...................................................................................................................... 15 41 ID3 Pricing Information ............................................................................................................. 18 42 ID4 Energy Emissions Profile .................................................................................................... 19 43 ID5 Present Demand-Aggregated Load .................................................................................... 22 44 ID6 Present Demand-Load ........................................................................................................ 23 45 ID7 Available Sheddable Load ................................................................................................... 24 46 ID8 Critical Load ......................................................................................................................... 26 47 ID9 State Change Interval .......................................................................................................... 27 48 ID10 Existing Demand Thresholds ........................................................................................... 28 49 ID11 Onsite Generation Capabilities ........................................................................................ 30 50 ID12 Onsite Energy Storage ...................................................................................................... 32 51 ID13 Onsite Thermal Storage .................................................................................................... 34 52 ID14 Loads to Shed .................................................................................................................... 36 53 ID15 Demand Forecast .............................................................................................................. 37 54 ID16 Historical Interval Usage .................................................................................................. 38 55 ID17 Energy Cost ........................................................................................................................ 41 56 ID18 Energy Emissions per kWh .............................................................................................. 42 57 ID19 Facility Report – Common Data ....................................................................................... 45 58 ID20 Historical Demand (Load) ................................................................................................ 49 59
60
61
EIS Alliance Customer Use Cases 4
Introduction 62
The conceptual model of the smart grid includes a domain called the “Customer” domain. This 63
domain includes the industrial, commercial, and residential buildings and equipment. In order to 64
identify the energy usage information that needs to be shared between the customer domain 65
and other domains within a smart grid, a set of use cases have been defined. These use cases 66
identify the information that passes across a conceptual boundary into or out of the customer 67
domain called the Energy Services Interface (ESI). The physical instantiation of the ESI has, by 68
choice, not been identified. It may be embedded in a meter, utility equipment, or customer 69
premises equipment without changing the use cases. These use cases are contained in a 70
document entitled, “Energy Information Standards (EIS) Alliance Customer Domain Use Cases”, 71
Version 2.0, March 22, 2010. 72
This document identifies the requirements for the information that is passed between the 73
customer domain and the remainder of the smart grid. An effort was made to try to use existing 74
information standards, as applicable. In areas where there are substantial efforts underway to 75
define the definition of the information passed through the ESI, this document defers to that 76
work. The information requirements are identified without relation to the specific protocol used 77
to transfer this information. In this way, market forces can determine the appropriate 78
communications protocols used in any particular domain. 79
80
EIS Alliance Customer Use Cases 5
Glossary 81 Acronym Name Description
CIM Common Information Model
The CIM is an abstract model that represents all the major objects in an electric utility enterprise typically needed to model the operational aspects of a utility. This model includes public classes and attributes for these objects, as well as the relationships between them.
ESI Energy Services Interface
A logical or physical device typically located at the customer facility and used as a communication gateway. The EMS may or may provide the Gateway function. The Energy Services Interface (ESI) permits applications such as remote load control, monitoring and control of distributed generation, in-home display of customer usage, reading of non-energy meters, and integration with building management systems. The ESI may provide auditing/logging functions that record transactions to and from Home Area Networking Devices.
(NAESB Smart Grid Task Force PAP 03 Update, www.naesb.org/pdf4/smart_grid_ssd111809w2.ppt)
IEC International Electrotechnical Commission
The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields.
(IEC 61968-3, IEC-2008)
NOAA National Oceanic and Atmospheric Adminstration
RDF Resource Description Framework
Language recommended by the W3C for expressing metadata that machines can process simply.
UML Universal Modeling Language
Modeling language and methodology for specifying, visualizing, constructing, and documenting the artifacts of a system-intensive process.
W3C World Wide Web Consortium
An international community that develops standards to ensure the long-term growth of the Web.
EIS Alliance Customer Use Cases 6
XML eXtensible Markup Language
Subset of Standard Generalized Markup Language (SGML), ISO 8879, for putting structured data in a text file.
82
EIS Alliance Customer Use Cases 7
Scope 83
This specification builds upon the “Energy Information Standards (EIS) Alliance Customer Domain 84
Use Cases” document by developing the requirements of the information identified as crossing 85
the ESI boundary from the customer domain to the smart grid. This information is identified in 86
the appendix entitled “Information Exchange Table“, and is shown below: 87
ID Name Description
1 Weather Forecast of weather, and related conditions.
2 Power Quality Various attributes of Power Quality on both an instantaneous as well as historical or scheduled (future) perspective
3 Pricing Information
Customer-specific real-time pricing (RTP) data tables and demand interval data (e.g. demand rules, tariffs, previous highest demand etc)
4 Energy Emissions Information used to quantify the environmental burden created during the generation of the power.
5 Present Demand-Aggregated
Instantaneous energy usage of the facility or production site, as an aggregate.
6 Present Demand-Loads
Instantaneous energy usage of the sub loads being monitored.
7 Available Shed-able Load
Individual loads that may be shed to reduce power demand
8 Critical Load Individual loads deemed to be critical, and their aggregate value, which may not be shed
9 State Change Interval
How quickly sub loads can respond to a shed command to reduce power demand.
10 Existing Demand Thresholds
Existing peak demand in current billing period; existing maximum demand during ratchet demand period
11 Onsite generation capabilities (and availability--spinning and non-spinning reserves)
The on-site generation capabilities, current and future status are summarized.
12 Onsite energy storage (and availability)
The on-site energy storage capacity as well as current and future status is summarized.
EIS Alliance Customer Use Cases 8
13 Onsite thermal storage
The capacity and availability of on-site thermal energy storage.
14 Loads to Shed Specific loads the EMS commands to shed.
15 Demand Forecast Forecasted demand (based on production schedule and historical data).
16 Historical interval Usage
Historical information about the energy consumed per block of time (e.g. 15 minute sliding window).
17 Energy Cost Energy cost per unit of time (e.g. minute, hour).
18 Energy Emissions per kW
“Energy Attributes” (ID 4, above) per kilowatt of power used.
19 Facility Report – Common Data
Information related to building energy usage information, including information about consumption, cost, and emissions.
20 Historical Demand (Load)
Historical information about the instantaneous energy demand over a period of time.
This specification addresses requirements for the energy information passed across the ESI in an 88
indusrial, commercial, or residential facility. This specification identifies the required information 89
to be exchanged, and uses type names from the CIM where possible. In an application or 90
standard there may be additional information (e.g. time stamps). 91
This document uses modeling techniques to identify a vendor neutral method of exchanging 92
energy information. It is based upon work performed by IEC technical committee 57: Power 93
systems management and associated information exchange. 94
In developing the information requirements, industry, government, and international standards 95
efforts were analyzed to ensure that the information being transferred was complete. This 96
includes data items defined by the American Society for Heating, Air Conditioning and 97
Refrigeration Engineers (ASHRAE), the Environmental Protection Agency (EPA), the Institute of 98
Electrical and Electronic Engineers (IEEE), the International Electrotechnical Commission (IEC), the 99
LONMark association, the National Oceanic and Atmospheric Administration (NOAA), the Utility 100
Communications Architecture International users group (UCAIug), and the ZigBee Alliance. 101
102
EIS Alliance Customer Use Cases 9
Normative References 103
The following documents are required to understand this document. For undated references, the 104
latest edition of the document applies. 105
Energy Information Standards (EIS) Alliance Customer Domain Use Cases V2.0. 106
IEC 61970-301, Energy Management System Application Program Interface (EMS-API) – Part 301: 107
Common Information Model (CIM) Base. 108
IEC 61970-501, Energy Management System Application Program Interface (EMS-API) – Part 501: 109
Common Information Model Resource Description Framework (CIM RDF) Schema. 110
RDF Semantics, World Wide Web Consortium Recommendation, 10 February 2004 111
RDF/XML Syntax Specification (Revised), World Wide Web Consortium Recommendation, 10 112
February 2004. 113
Resource Description Framework (RDF) Schema Specification 1.0, World Wide Web Consortium, 114
27 March 2000. 115
Extensible Markup Language (XML) 1.0, Second Edition, World Wide Web Consortium, 6 October 116
2000. 117
NOAA National Digital Forecast Database, TIN 06-40, National Oceanography and Atmospheric 118
Administration, 9-May 2006 119
120
EIS Alliance Customer Use Cases 10
Customer Domain Information Requirements 121
ID1 Weather 122
This information represents the forecast weather, and related environmental conditions 123
that can be used to forecast building energy consumption. This information is based 124
primarily upon the NOAA National Digital Forecast Database information. 125
This data item is expected to normally be sourced external to the building by a service 126
provider. 127
The Weather information exchanged across the ESI is defined in Table 1.1. 128
Properties Data Types Units 12-hour Probability of Precipitation (PoP12) PerCent %
Hazards String Maximum Temperature Temperature Degrees C or F
Minimum Temperature Temperature Degrees C or F
Quantitative Precipitation Amount float cm
Relative Humidity PerCent %
Sky Cover PerCent %
Insolation (solar loading) float (W/m^2)
Snow Amount float cm
Temperature Temperature Degrees C or F
Wind Direction AngleDegrees Degrees
Wind Speed float Km/hr
Barometric Pressure float hPa or in of Hg
Start Date/Time AbsoluteDateTimei
End Date/Time AbsoluteDateTimeii
Sunrise Time Timeiii
Sunset Time Timeiv
Geographic Location Degrees Latitude AngleDegrees Degrees
Geographic Location Minutes Latitude Float Geographic Location Degrees Longitude AngleDegrees Degrees
Geographic Location Minutes Longitude Float Geographic Location Elevation Float Meters
Table 1.1 Weather Information 129
The CIM/XML RDF description of this data is shown below. 130
131
132
133
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 134
xmlns:dc=http://purl.org/dc/terms/> 135
136
137
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 11
ESIWeather 138
”Current and forecasted weather related data used in 139 forecasting of energy demand.” 140
141
142
12hourProbabilityofPrecipitation 143 144
”Probably of rain within the next twelve hours from 145 requested time interval.” 146
148
149
150
Hazards 151
”Severe weather warnings over requested time 152 interval.” 153
155
156
157
MaximumTemperature 158
”High Temperature over requested time 159 interval.” 160
162
163
164
MinimumTemperature 165
”Low Temperature over requested time 166 interval.” 167
169
170
171
QuantitativePrecipitationAmount 172 173
”Amount of precipitation over requested time 174 interval.” 175
177
178
179
http://iec.ch/TC57/2003/CIM-schema-cim10#PerCenthttp://iec.ch/TC57/2003/CIM-schema-cim10#PerCenthttp://iec.ch/TC57/2003/CIM-schema-cim10#Sringhttp://iec.ch/TC57/2003/CIM-schema-cim10#Sring
EIS Alliance Customer Use Cases 12
RelativeHumidity 180
”RH over requested time interval.” 181
183
184
185
SkyCover 186
”Amount of cloud cover over requested time 187 interval.” 188
190
191
192
Insolation 193
”Amount of solar loading over requested time 194 interval.” 195
197
198
199
SnowAmount 200
”Amount of snow cover over requested time 201 interval.” 202
204
205
206
Temperature 207
”Current temperature over requested time 208 interval.” 209
211
212
213
WindDirection 214
”Wind direction from true north over requested time 215 interval.” 216
218
219
220
EIS Alliance Customer Use Cases 13
WindSpeed 221
”Wind speed over requested time 222 interval.” 223
225
226
227
BarometricPressure 228
”Barometric pressure over requested time 229 interval.” 230
232
233
234
StartDateTime 235
”Start date and time of weather 236 data.” 237
239
240
241
EndDateTime 242
”End date and time of weather data.” 243
245
246
247
SunriseTime 248
”Date and time of sunrise.” 249
251
252
253
SunsetTime 254
”Date and time of sunset.” 255
257
258
259
GeographicLocationDegreesLatitude 261
EIS Alliance Customer Use Cases 14
”Location in degrees latitude of the weather 262 information.” 263
265
266
267
GeographicLocationMinutesLatitude 269
”Location in minutes latitude of the weather 270 information.” 271
273
274
275
GeographicLocationDegreesLongitude 277
”Location in degrees longitude of the weather 278 information.” 279
281
282
283
GeographicLocationMinutesLongitude 285
”Location in minutes longitude of the weather 286 information.” 287
289
290
291
GeographicLocationMinutesElevation 293
”Location in meters above sea level of the weather 294 information.” 295
297
298
299
300
EIS Alliance Customer Use Cases 15
ID2 Power Quality 301
This information provides various attributes of Power Quality on both an instantaneous 302
as well as historical or scheduled (future) perspective. 303
This information is based upon power quality events defined within IEEE 1159-2009. A 304
Service Level Agreement (SLA) between a and an electrical energy provider should be 305
based on an agreed upon number of transients, sags, voltage fluctuations, voltage dips 306
and interruptions, voltage imbalances, power-frequency variations, induced low 307
frequency voltages, and CD in AC networks events defined in the IEEE 1159 standard. 308
A placeholder was added to this information to indicate Quality of Service (QOS), similar 309
to the Availability found in telephony/data systems. In the future we expect the industry 310
to create a metric that defines--"good power", power availability, or Quality of Service. 311
This data item is expected to normally be sourced external to the building by an energy 312
supplier. It may be validated against internal power quality sources. 313
The Power Quality information exchanged across the ESI is defined in Table 2.1. 314
Properties Data Types Units Transients / Billing Period ULong n/a
Sags / Billing Period ULong n/a
Swells / Billing Period ULong n/a
Interruptions / Billing Period ULong n/a
Voltage Imbalances / Billing Period ULong n/a
power frequency variations / Billing Period ULong n/a
Others (See IEEE-1159) / Billing Period ULong n/a
Quality of Service PerCent %
Table 2.1 Power Quality Information 315
The CIM/XML RDF description of this data is shown below. 316
317
318
319
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 320
xmlns:dc=http://purl.org/dc/terms/> 321
322
323
ESIPowerQuality 324
”Electric power quality characteristics important to 325 an energy consumer.” 326
327
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 16
328
TransientsPerBillingPeriod 329
”Number of transient events allowed during the 330 current billing period.” 331
333
334
335
SagsPerBillingPeriod 336
”Number of sag events allowed during the current 337 billing period.” 338
340
341
342
SwellsPerBillingPeriod 343
”Number of swell events allowed during the current 344 billing period.” 345
347
348
349
InterruptionsPerBillingPeriod 351
”Number of interruption events allowed during the 352 current billing period.” 353
355
356
358
359 VoltageImbalancesPerBillingPeriod 360
”Number of Voltage Imbalance events allowed during 361 the current billing period.” 362
364
365
367
PowerFrequencyVariationsPerBillingPeriod 370
EIS Alliance Customer Use Cases 17
”Number of Power Frequency Variation events allowed 371 during the current billing period.” 372
374
375
376
OthersPerBillingPeriod 377
”Number of other power quality events allowed during 378 the current billing period.” 379
381
382
383
QualityOfService 384
”Indication of the power quality during the current 385 billing period.” 386
388
389
390
391
EIS Alliance Customer Use Cases 18
ID3 Pricing Information 392
This information contains customer-specific real-time pricing (RTP) data tables and 393
demand interval data (e.g. demand rules, tariffs, previous highest demand etc). 394
Development of the requirements for pricing information was considered to be 395
premature by the EIS Alliance. The content of this information is current a topic of 396
discussion within the OASIS EMIX standards body and therefore was deferred. The 397
contents of this information will be addressed as an output of the NIST Priority Action 398
Plan (PAP) 03, entitled “Develop Common Specification for Price and Product 399
Information”. 400
This data item is expected to normally be sourced external to the building by an energy supplier.401
EIS Alliance Customer Use Cases 19
402
ID4 Energy Emissions Profile 403
This Information is used to quantify the environmental burden created during the 404
generation of the power. This could be power received from an energy supplier, drawing 405
down energy storage, or could pertain to energy generated onsite (e.g. Carbon, CO2, SOx, 406
NOx, other by-products of fossil-fuel combustion). Historical and present emissions 407
profiles can be obtained by appropriate use of the start and end dates and times. 408
The content of this information is based upon the identified emissions particulates 409
considered by the EPA to be greenhouse gasses. 410
This data item is expected to normally be sourced external to the building by an energy 411
supplier. There may be cases where this structure cannot be or may not be fully 412
populated.The Energy Emissions information exchanged across the ESI is defined in Table 413
4.1. 414
Properties Data Types Units ARRAY OF: {
Start Date and Time AbsoluteDateTimev
End Date and Time AbsoluteDateTimevi
CO2 ULong Tonnes
NOx ULong Tonnes
Carbon ULong Tonnes
SOx ULong Tonnes
Methane ULong Tonnes
HCH ULong Tonnes
Perfluorocarbons ULong Tonnes
Sulfur Hexafluoride ULong Tonnes
Other contaminants ULong Tonnes
} END ARRAY
Table 4.1 Energy Emissions Information 415
The CIM/XML RDF description of this data is shown below. 416
417
418
419
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 420
xmlns:dc=http://purl.org/dc/terms/> 421
422
423
ESIEnergyEmissionsProfile 424
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 20
” Information used to quantify the environmental 425 burden created during the generation of the electric 426 power.” 427
428
429
CO2 430
”Amount of carbon dioxide produced to generate the 431 power consumed.” 432
434
435
436
NOX 437
”Amount of nitrous oxides produced to generate the 438 power consumed.” 439
441
442
443
Carbon 444
”Amount of carbon produced to generate the power 445 consumed.” 446
448
449
450
SoX 451
”Amount of sulfur oxides produced to generate the 452 power consumed.” 453
455
456
457
Methane 458
”Amount of methane produced to generate the power 459 consumed.” 460
462
463
464
HCH 465
EIS Alliance Customer Use Cases 21
”Amount of Hexachlorocyclohexane produced to generate 466 the power consumed.” 467
469
470
471
Perfluorocarbons 472
”Amount of Perfluorocarbons produced to generate the 473 power consumed.” 474
476
477
478
SulfurHexafluoride 479
”Amount of sulfur hexaflourides produced to generate 480 the power consumed.” 481
483
484
485
OtherContaminants 486
”Amount of other contaminants of emerging concern 487 produced to generate the power consumed.” 488
490
491
492
493
494
EIS Alliance Customer Use Cases 22
ID5 Present Demand-Aggregated Load 495
This information identifies the current energy usage of the facility or production site, as 496
an aggregate. 497
This data item is expected to normally be sourced internal to the building by an energy 498
management system. 499
The Present Demand-Aggregated information exchanged across the ESI is defined in 500
Table 5.1. 501
Properties Data Types Units Present demand aggregated ApparentPower MW or MVA
Table 5.1 Present Demand-Aggregated Information 502
The CIM/XML RDF description of this data is shown below. 503
504
505
506
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 507
xmlns:dc=http://purl.org/dc/terms/> 508
509
510
ESIPresentDemandAggregate 511
” Current electric energy usage of the facility or 512 production site, as an aggregate.” 513
514
516
PresentDemandAggregate 517
”Current energy usage of the facility or production 518 site, as an aggregate.” 519
521
522
523
524
525
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 23
ID6 Present Demand-Load 526
This information identifies the current energy usage of the loads being monitored 527
(conditional on sub metering installed). 528
This data item is expected to normally be sourced internal to the building by an energy 529
management system. 530
The Present Demand-Load information exchanged across the ESI is defined in Table 6.1. 531
Properties Data Types Units ARRAY OF: {
Present Demand Load ApparentPower MW or MVA
} END ARRAY
Table 6.1 Present Demand-Load Information 532
The CIM/XML RDF description of this data is shown below. 533
534
535
536
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 537
xmlns:dc=http://purl.org/dc/terms/> 538
539
540
ESIPresentDemandLoad 541
” Current energy usage of the loads being 542 monitored.” 543
544
546
PresentDemandAggregate 547
”Current energy usage of the loads being 548 monitored.” 549
551
552
553
554
555
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 24
ID7 Available Sheddable Load 556
This information contains Individual loads that may be shed to reduce power demand. 557
There are two methods to indicate the amount of sheddable load; explicit or implicit. 558
Equipment using explicit shedding provide the amount of demand that can be shed (KW 559
or KVA) during an event. Equipment using implicit shedding indicates the percentage of 560
energy demand that can be reduced. The priority of the load gives a relative indication 561
of its criticality within the facility. The Description is intended to be a locally generated, 562
human readable, description of the load. It is intitially entered by the customer. The 563
Identifier is a unique indication of the load within the facility, generated and managed 564
locally by an energy/load management system. 565
This data item is expected to normally be sourced internal to the building by an energy 566
management system. Note that since the “Identifier” in this data structure is locally-567
assigned, a “load” could actually represent a process; for example, a “load” could be the 568
trigger to reset the chilled water setpoint by 1oF or, or activate a demand-limiting a stage 569
in a Rooftop Unit. 570
The Available Sheddable Load information exchanged across the ESI is defined in Table 571
7.1. 572
Properties Data Types Units ARRAY OF: {
Level in kw/kva float KW or KVA
Level in % PerCent %
Priority Priority 0 = High
Shed Delay Seconds seconds
Restore Delay Seconds seconds
Description String n/a
Identifier String } END ARRAY
Table 7.1 Available Sheddable Load Information 573
The CIM/XML RDF description of this data is shown below. 574
575
576
577
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 578
xmlns:dc=http://purl.org/dc/terms/> 579
580
581
ESIAvailableSheddableLoad 582
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 25
”Individual loads and their aggregate value that may 583 be shed to reduce power demand at the customer 584 site.” 585
586
587
588
589
590
EIS Alliance Customer Use Cases 26
ID8 Critical Load 591
This information indicates the individual loads deemed to be critical, and their aggregate 592
value, which may not be shed unless a critical event occurs. Equipment that can be 593
explicitly shed provide the amount of demand that can be shed (KW or KVA) during an 594
event. Equipment that can only be implicitly shed indicates the percentage of energy 595
demand that can be reduced. The priority of the load gives a relative indication of its 596
criticality. 597
This data item is expected to normally be sourced internal to the building by an energy 598
management system. 599
The Critical Load information exchanged across the ESI is defined in Table 8.1. 600
Properties Data Types Units ARRAY OF: {
Level in kw/kva float KW or KVA
Level in % PerCent %
Priority Priority 0 = High
Shed Delay Seconds seconds
Restore Delay Seconds seconds
Description String n/a
Identifier String } END ARRAY
Table 8.1 Critical Load Information 601
The CIM/XML RDF description of this data is shown below. 602
603
604
605
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 606
xmlns:dc=http://purl.org/dc/terms/> 607
608
609
ESICriticalLoad 610
”Individual loads deemed to be critical to the 611 operation of the customer and therefore cannot be 612 shed.” 613
614
615
616
617
618
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 27
ID9 State Change Interval 619
Information on how quickly sub loads can respond to a shed command to reduce power 620
demand. This information can be used by an Energy Supplier to help plan Direct Load 621
Control (DLC) events or model the response of a Demand Response request. Since there 622
was no existing standard on how this is represented, the decision was made to draw 623
from experience within the industry. 624
This data item is expected to normally be sourced internal to the building by intelligent 625
end devices or an energy management system. 626
The State Change Interval information exchanged across the ESI is defined in Table 9.1. 627
Properties Data Types Units ARRAY OF: {
Start delay Seconds seconds
Stop delay Seconds seconds
Description String n/a
Identifier String } END ARRAY
Table 9.1 State Change Interval Information 628
The CIM/XML RDF description of this data is shown below. 629
630
631
632
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 633
xmlns:dc=http://purl.org/dc/terms/> 634
635
636
ESIStateChangeInterval 637
”Indication of how quickly sub-loads can respond to 638 demand response actions.” 639
640
641
642
643
644
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 28
ID10 Existing Demand Thresholds 645
This information indicates the existing peak demand in current billing period and existing 646
maximum demand during the ratchet demand period. 647
This data item is expected to normally be sourced external to the building by an energy 648
supplier. 649
The Existing Demand Thresholds information exchanged across the ESI is defined in Table 650
10.1. 651
Properties Data Types Units Peak Demand Value ApparentPower MW or MVA
Peak demand Date and Time AbsoluteDateTimevii
Ratchet Demand Value ApparentPower MW or MVA
Ratchet Demand Date and Time AbsoluteDateTimeviii
Ratchet Demand Period in Months ULong Table 10.1 Existing Demand Thresholds Information 652
The CIM/XML RDF description of this data is shown below. 653
654
655
656
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 657
xmlns:dc=http://purl.org/dc/terms/> 658
659
660
ESIExistingDemandThresholds 661 662
”Energy information indicating existing peak demand 663 in current billing cycle and maximum demand during ratchet demand 664 period.” 665
666
667
PeakDemandValue 668
”Peak demand threshold of the 669 bulding.” 670
672
673
675
PeakDemandDateAndTime 676
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 29
”Date and time of peak demand of the 677 bulding.” 678
680
681
682
RachetDemandValue 683
”Rachet demand threshold of the 684 bulding.” 685
687
688
690
RachetDemandDateAndTime 691
”Date and time of ratchet demand of the 692 bulding.” 693
695
696
698
RachetDemandPeriodInMonths 699
”Lenght of ratchet demand surcharge for the 700 bulding.” 701
703
704
705
706
707
EIS Alliance Customer Use Cases 30
ID11 Onsite Generation Capabilities 708
This information indicates the on-site generation capabilities, current and future status 709
are summarized. This also includes availability: spinning, and non-spinning reserves. 710
This data item is expected to normally be sourced internal to the building by the 711
generation equipment or an energy management system. 712
Note that Plug-In Electric Hybrids (PHEVs) may be considered an onsite load, generator, 713
or storage device depending upon the capabilities of the PHEV and the onsite energy 714
management system. 715
The Onsite Generation Capabilities information exchanged across the ESI is defined in 716
Table 11.1. 717
Properties Data Types Units Nominal base voltage Voltage kV
Initial Capacity (for generators) ApparentPower MVA
Baseline MVA ApparentPower MVA
Baseline Reactive Capacity ApparentPower MVA
Ramp RatePerSecond PerCent %
Equipment Efficiency Rating PerCent %
Source Type Enumeration 0 = Constant Output 1 = Variable Output
ARRAY OF: {
Start Date and Time AbsoluteDateTimeix
End Date and Time AbsoluteDateTimex
Projected Capacity PerCent
Availability Status Enumeration
0 = Unavailable 1=Available
Reserve Status
Enumeration
0 = Non-Spinning 1=Spinning 2 = Unknown 3. = Not Applicable
Active Status Enumeration
0 = Inactive 1=Active
Charge Status
Enumeration
0 = Discharged 1=Discharging 2 = Charged 3. = Charging
} END ARRAY
Table 11.1 Onsite Generation Capabilities Information 718
The CIM/XML RDF description of this data is shown below. 719
720
721
EIS Alliance Customer Use Cases 31
722
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 723
xmlns:dc=http://purl.org/dc/terms/> 724
725
726
ESIOnsiteGenerationCapabilities 727 728
”On premise electrical generation capabilities and 729 characteristics.” 730
731
732
733
734
735
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 32
ID12 Onsite Energy Storage 736
The onsite energy storage capacity as well as current and future status is summarized. 737
To the outside, on-site energy storage is stored energy that will appear as generation 738
capacity. This also includes availability. 739
This data item can also be used to model other types of energy storage systems. For 740
example, pumped hydro and compressed air storage can be modeled with this structure. 741
This data item is expected to normally be sourced internal to the building by the energy 742
storage equipment or an energy management system. 743
Note that Plug-In Electric Hybrids (PHEVs) may be considered an onsite load, generator, 744
or storage device depending upon the capabilities of the PHEV and the onsite energy 745
management system. 746
The Onsite Energy Storage information exchanged across the ESI is defined in Table 12.1. 747
Properties Data Types Units Available Capacity (storage) EnergyAsMWh MWh
Maximum Power ApparentPower MVA
Equipment Efficiency Rating PerCent %
ARRAY OF: {
Start Date and Time AbsoluteDateTimexi
End Date and Time AbsoluteDateTimexii
Availability Status Enumeration
0 = Unavailable 1=Available
Reserve Status
Enumeration
0 = Non-Spinning 1=Spinning 2 = Unknown 3. = Not Applicable
Active Status Enumeration
0 = Inactive 1=Active
Charge Status
Enumeration
0 = Discharged 1=Discharging 2 = Charged 3. = Charging
} END ARRAY
Table 12.1 Onsite Energy Storage Information 748
The CIM/XML RDF description of this data is shown below. 749
750
751
752
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 753
http://www.w3.org/TR/1999/PR-rdf-schema-19990303
EIS Alliance Customer Use Cases 33
xmlns:dc=http://purl.org/dc/terms/> 754
755
756
ESIOnsiteEnergyStorage 757
”On premise electric energy storage capacity 758 characteristics.” 759
760
761
762
763
764
http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 34
ID13 Onsite Thermal Storage 765
This information indicates the capacity and availability of on-site thermal energy storage. 766
This data item is expected to normally be sourced internal to the building by the storage 767
equipment or an energy management system. 768
The Onsite Thermal Storage information exchanged across the ESI is defined in Table 769
13.1. 770
Properties Data Types Units Available Capacity (storage) float MBTU
Maximum Power float Output Units Enumeration Equipment Efficiency Rating PerCent %
ARRAY OF: {
Start Date and Time AbsoluteDateTimexiii
End Date and Time AbsoluteDateTimexiv
Availability Status Enumeration
0 = Unavailable 1=Available
Reserve Status
Enumeration
0 = Non-Spinning 1=Spinning 2 = Unknown 3. = Not Applicable
Active Status Enumeration
0 = Inactive 1=Active
Charge Status
Enumeration
0 = Discharged 1=Discharging 2 = Charged 3. = Charging
Storage Output Capability
Enumeration
0 = Heating 1=Cooling 2 = Heating and Cooling
} END ARRAY
Table 13.1 Onsite Thermal Storage Information 771
The CIM/XML RDF description of this data is shown below. 772
773
774
775
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 776
xmlns:dc=http://purl.org/dc/terms/> 777
778
779
ESIOnSiteThermalStorage 780
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 35
”Electric capacity and availability of on-premise 781 thermal storage.” 782
783
784
785
786
787
EIS Alliance Customer Use Cases 36
ID14 Loads to Shed 788
This information contains the specific loads the building EMS commands to shed. The 789
Identifier is a unique indication of the load within the facility, generated and managed 790
locally by an energy/load management system. 791
This data item is expected to normally be sourced internal to the building by an energy 792
management system. 793
The Loads To Shed information exchanged across the ESI is defined in Table 14.1. 794
Properties Data Types Units ARRAY OF: {
Description String
Identifier String } END ARRAY
Table 14.1 Loads To Shed Information 795
The CIM/XML RDF description of this data is shown below. 796
797
798
799
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 800
xmlns:dc=http://purl.org/dc/terms/> 801
802
803
ESILoadsToShed 804
”Specific loads that the EMS Commands to 805 shed.” 806
807
808
809
810
811
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 37
ID15 Demand Forecast 812
This information indicates the forecasted demand (based on production schedule and 813
historical data). 814
This data item is expected to normally be sourced internal to the building by an energy 815
management system. 816
The Demand Forecast information exchanged across the ESI is defined in Table 15.1. 817
Properties Data Types Units ARRAY OF: {
Start Date and Time AbsoluteDateTimexv
Interval Timexvi
Forecast Generation Date and Time AbsoluteDateTimexvii
Forecast Origin Enumeration
0 = Internal, 1 = External
Power Factor Float
Forecasted Real Demand ApparentPower KW
Confidence Factor PerCent %
} END ARRAY
Table 15.1 Demand Forecast Information 818
The CIM/XML RDF description of this data is shown below. 819
820
821
822
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 823
xmlns:dc=http://purl.org/dc/terms/> 824
825
826
ESIDemandForecast 827
”Forecasted demand of electric 828 power.” 829
830
831
832
833
834
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 38
ID16 Historical Interval Usage 835
This information indicates the historical information about the energy consumed per 836
block of time (e.g. 15 minute sliding window). 837
This data item is expected to normally be sourced external to the building by an energy 838
supplier or energy information provider. 839
The Historical Interval Usage information exchanged across the ESI is defined in Table 840
16.1. 841
Properties Data Types Units ARRAY OF: {
Start Date and Time AbsoluteDateTimexviii
End Date and Time AbsoluteDateTimexix
Gross Usage EnergyAsMWh MWh
Net Usage EnergyAsMWh MWh
Avoided Usage EnergyAsMWh MWh
Generated Energy EnergyAsMWh MWh
Quality of Reading Enumeration Per IEC61968-9
Source/Greenness
Enumeration
0 = Not Applicable 1 = Zero Emitter 2 = Low Emitter 3 = Low-Medium Emitter 4 = Medium Emitter 5 = Medium-high Emitter 6 = High Emitter 7 = Very High Emitter
Confidence Factor PerCent %
} END ARRAY
Table 16.1 Historical Interval Usage Information 842
The CIM/XML RDF description of this data is shown below. 843
844
845
846
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 847
xmlns:dc=http://purl.org/dc/terms/> 848
849
850
ESIHistoricalIntervalUsage 851 852
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 39
”Historical information about the energy consumed 853 per block of time.” 854
855
856
StartDateTime 857
”Start date and time of interval usage 858 data.” 859
861
862
863
EndDateTime 864
”End date and time of interval usage 865 data.” 866
868
869
870
GrossUsage 871
”Total power consumption over specified time 872 interval.” 873
875
876
877
NetUsage 878
”Net power consumption over specified time 879 interval.” 880
882
883
884
AvoidedUsage 885
”Power consumption avoided (by energy efficiency or 886 other means) over specified time interval.” 887
889
890
891
GeneratedEnergy 892
EIS Alliance Customer Use Cases 40
”Total power generated over specified time 893 interval.” 894
896
897
898
QualityOfReading 899
”Indication of the source of the the demand 900 readings.” 901
903
904
905
Source/Greenness 906
”Indication of the source of the the generated 907 energy.” 908
910
911
912
ConfidenceFactor 913
”Indication of known accuracy of the usage 914 information.” 915
917
918
919
920
921
922
EIS Alliance Customer Use Cases 41
ID17 Energy Cost 923
This information indicates the energy cost per unit of time (e.g. minute, hour). 924
Development of the requirements for pricing and cost information was considered to be 925
premature by the EIS Alliance. The content of this information is current a topic of 926
discussion within the OASIS EMIX standards body and therefore was deferred. The 927
contents of this information will be addressed as an output of the NIST Priority Action 928
Plan (PAP) 03, entitled “Develop Common Specification for Price and Product 929
Information”. 930
This data item is expected to normally be sourced external to the building by an energy 931
supplier. 932
933
EIS Alliance Customer Use Cases 42
ID18 Energy Emissions per kWh 934
This Information is used to quantify the environmental burden created during the 935
generation of the power on a per kilowatt basis. This could be power received from an 936
energy supplier, drawing down energy storage, or could pertain to energy generated 937
onsite (e.g. Carbon, CO2, SOx, NOx, other by-products of fossil-fuel combustion). 938
The content of this information is based upon the identified emissions and particulates as 939
of this writing as listed by the EPA to be greenhouse gasses. This is the complete list 940
identified by the EPA in its Greenhouse Gas Emissions calculator 941
(http://www.epa.gov/cleanenergy/energy-resources/calculator.html). 942
This data item is expected to normally be sourced internal to the building by an energy 943
management system. Some of the information needed by the energy management 944
system to determine this data will be provided by the energy service provider (and was 945
identified in another data item). 946
The Energy Emissions per KWh information exchanged across the ESI is defined in Table 947
18.1. 948
Properties Data Types Units CO2 ULong ppm/Kwh
NOX ULong ppm/Kwh
Carbon ULong ppm/Kwh
SOX ULong ppm/Kwh
Methane ULong ppm/Kwh
HCH ULong ppm/Kwh
Perflurcarbons ULong ppm/Kwh
Sulfur Hexafluoride ULong ppm/Kwh
Other contaminants of emerging concern ULong ppm/Kwh
Table 18.1 Energy Emissions per KWh Information 949
The CIM/XML RDF description of this data is shown below. 950
951
952
953
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 954
xmlns:dc=http://purl.org/dc/terms/> 955
956
957
ESIEnergyEmissionsPerKW 958
”Electric emissions of the blended electric power 959 provided to the building per KW supplied.” 960
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 43
961
962
CO2 963
”Amount of carbon dioxide produced to generate a KW 964 of power consumed.” 965
967
968
EIS Alliance Customer Use Cases 44
1002
1003
1004
Perfluorocarbons 1005
”Amount of Perfluorocarbons produced to generate a 1006 KW of power consumed.” 1007
1009
1010
1011
SulfurHexafluoride 1012
”Amount of sulfur hexaflourides produced to generate 1013 the power consumed.” 1014
1016
1017
1018
OtherContaminants 1019
”Amount of other contaminants of emerging concern 1020 produced to generate a KW of power consumed.” 1021
1023
1024
1025
1026
1027
EIS Alliance Customer Use Cases 45
ID19 Facility Report – Common Data 1028
This information identifies building energy usage information, including information 1029
about consumption, cost, and emissions. 1030
This data item is expected to normally be sourced internal to the building by an energy 1031
management system. 1032
The Facility Report – Common Data information exchanged across the ESI is defined in 1033
Table 19.1. 1034
Properties Data Types Units Current Day Net Consumption EnergyAsMWh MWh
Current Day Overall Consumption EnergyAsMWh MWh
Previous Day Net Consumption EnergyAsMWh MWh
Previous Day Overall Consumption EnergyAsMWh MWh
Present Demand ApparentPower MVA or MW
Current Day Last Year Net Consumption EnergyAsMWh MWh
Previous Day Last Year Overall Consumption EnergyAsMWh MWh
Normalized for weather: Current Day Net Consumption EnergyAsMWh MWh
Normalized for weather: Current Day Overall Consumption EnergyAsMWh MWh
Normalized for weather: Current Day Last Year Net Consumption (same day prior year) EnergyAsMWh MWh
Normalized for weather: Current Day Last Year Overall Consumption (same day prior year) EnergyAsMWh MWh
Current Day Electrical Storage Consumed EnergyAsMWh MWh
Current Day Thermal Storage Consumed Float MBTU
Current Day Electrical Generation EnergyAsMWh MWh
Table 19.1 Facility Report – Common Data Information 1035
The CIM/XML RDF description of this data is shown below. 1036
1037
1038
1039
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 1040
xmlns:dc=http://purl.org/dc/terms/> 1041
1042
1043
ESIFacilityReport-1044 CommonData 1045
”Building energy usage information, including 1046 information about consumption, cost, and 1047 emissions.” 1048
1049
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 46
1051
CurrentDayNetConsumption 1052
”Current day net power consumption.” 1053
1055
1056
1058
1059 CurrentDayOverallConsumption 1060
”Current day total power 1061 consumption.” 1062
1064
1065
1067
PreviousDayNetConsumption 1068
”Previous day net power consumption.” 1069
1071
1072
1074
PreviousDayOverallConsumption 1075 1076
”Previous day total power 1077 consumption.” 1078
1080
1081
1082
PresentDemand 1083
”Current power consumption.” 1084
1086
1087
1089
PreviousDayLastYearNetConsumption 1091
EIS Alliance Customer Use Cases 47
”Previous day last year net power 1092 consumption.” 1093
1095
1096
1098
PreviousDayLastYearOverallConsumption 1099 1100
”Previous day last year total power 1101 consumption.” 1102
1104
1105
1107
CurrentDayNormalizedNetConsumption 1109
”Current day net power consumption normalized for 1110 weather.” 1111
1113
1114
1116
1117 CurrentDayNormalizedOverallConsumption 1118
”Current day total power consumption normalized for 1119 weather.” 1120
1122
1123
1125
CurrentDayLastYearNormalizedNetConsumption 1128
”Current day last year net power consumption 1129 normalized for weather.” 1130
1132
1133
1135
EIS Alliance Customer Use Cases 48
1136 CurrentDayLastYearNormalizedOverallConsumption 1137
”Current day last year total power consumption 1138 normalized for weather.” 1139
1141
1142
1144
CurrentDayElectricalStorageConsumed 1145 1146
”Current day total power consumption from electrical 1147 storage.” 1148
1150
1151
1153
CurrentDayThermalStorageConsumed 1154 1155
”Current day total power consumption from thermal 1156 storage.” 1157
1159
1160
1162
1163 CurrentDayElectricalGeneration 1164
”Current day amount of power generated on-1165 site.” 1166
1168
1169
1170
1171
1172
EIS Alliance Customer Use Cases 49
ID20 Historical Demand (Load) 1173
This data indicates historical information about the highest level of energy usage, or peak 1174
demand consumed over a block of time. 1175
This data item is expected to normally be sourced external to the building by an energy 1176
supplier or an energy information provider. 1177
The Historical Demand information exchanged across the ESI is defined in Table 20.1. 1178
Properties Data Types Units ARRAY OF: {
Start Date and Time AbsoluteDateTimexx
End Date and Time AbsoluteDateTimexxi
Peak Demand EnergyAsMWh MWh
Average Demand EnergyAsMWh MWh
Quality of Reading Enumeration Per IEC61968-9
Source/Greenness
Enumeration
0 = Not Applicable 1 = Zero Emitter 2 = Low Emitter 3 = Low-Medium Emitter 4 = Medium Emitter 5 = Medium-high Emitter 6 = High Emitter 7 = Very High Emitter
Confidence Factor PerCent %
} END ARRAY
Table 20.1 Historical Demand Information 1179
The CIM/XML RDF description of this data is shown below. 1180
1181
1182
1183
xmlns:rdfs=http://www.w3.org/TR/1999/PR-rdf-schema-19990303# 1184
xmlns:dc=http://purl.org/dc/terms/> 1185
1186
1187
ESIHistoricalDemand 1188
”Historical information about the energy consumed 1189 per block of time.” 1190
1191
1192
http://www.w3.org/TR/1999/PR-rdf-schema-19990303http://purl.org/dc/terms/
EIS Alliance Customer Use Cases 50
StartDateTime 1193
”Start date and time of interval demand 1194 data.” 1195
1197
1198
1199
EndDateTime 1200
”End date and time of interval demand 1201 data.” 1202
1204
1205
1206
PeakDemand 1207
”Peak Power demand over specified time 1208 interval.” 1209
1211
1212
1213
AverageDemand 1214
”Average Power demand over specified time 1215 interval.” 1216
1218
1219
1220
QualityOfReading 1221
”Indication of the source of the the demand 1222 readings.” 1223
1225
1226
1227
Source/Greenness 1228
”Indication of the source of the the generated 1229 energy.” 1230
1232
1233
EIS Alliance Customer Use Cases 51
1234
ConfidenceFactor 1235
”Indication of known accuracy of the usage 1236 information.” 1237
1239
1240
1241
1242
1243
1244
i The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
ii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
iii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
iv The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
v The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
vi The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
vii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
viii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
ix The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
x The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xi The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xiii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xiv The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xv The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
EIS Alliance Customer Use Cases 52
xvi
The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xvii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xviii The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xix The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xx The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.
xxi The definition of date and time is currently being developed by the NIST Priority Action Plan #3. This document
will be harmonized with that effort upon the completion of their work.