Consumer Services - Brief Use Cases

The Purpose of Automatic meter reading (AMR) function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.6	1.3	2.7	1.4	1.6	1.7

COMMENTS:
The following comments were collected during the peer review:

0 - for multicast / broadcast messages, that recipient can be permitted to miss

How does this rating for "AMR" differ or relate to MDMA and others below?

-- Joe Hughes - 28 Apr 2003

While the architecture for AMR is fairly straightforward for fulfilling the meter functions, the architecture for tying AMR-enhanced meter information to other functions of electricity markets is largely unspecified, especially for competitive electricity markets. This especially true where multiple members of the electricity value chain (generator to end use) simultaneously need access to the information in real time. There are also PID control theory applications to restoring electricity markets (e.g., reliability crisis) to the desired "set point." These applications not only need real-time data, they also need speedy access and analysis of the meter data history. So configuration, quality of service, and data management all should be 2.5 or higher.

-- William Smith - 27 Jun 2003

C-1.1 Meter Data Management Agent (MDMA) reads meters with handheld/mobile technologies

The Purpose of Meter Data Management Agent (MDMA) reads meters with handheld/mobile technologies function
is to

permit company to improve the billing process, make it more cost effective, faster, more comfortable to the clients, reduce probability of error in the reading process and the estimations in the billing

To eliminate problems related to reading meters in difficult or dangerous locations (or in most locations) and can also help to reduce utility company operating costs

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators

Etc)

Customers

Meters

performing

Retrieve meter data traveling around meters locations

with key interfaces between

MDMAs and meters

MDMAs and Settlement System

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability (can be read later)

Data accuracy high (billing purposes)

Data frequency is low

with security requirements of

High security level and confidentiality to keep safe this data (that have financial implications)

To keep private individual energy consumption

And also to avoid tampering and other acts, that put in risk the financial process

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
0.0	1.0	3.0	1.0	2.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Security=3 this it cash register data

Constraints=2 large legacy interface

Data Mgmt=1 smaller volume of data and existing system if functioning

The following comments were collected during the peer review:

1 - guaranteed delivery

No timeliness requirements

0 looks too low for configuration here since the vision includes migration to fixed.

-- Joe Hughes - 28 Apr 2003

Agree with the comments here, and think this item is ancillary. CEIDS is trying to address the Digital Society, isn't it? This item is for basic customers as they now exist.

-- William Smith - 27 Jun 2003

C-1.2 MDMA reads industrial and/or commercial meters with fixed AMR technology

The Purpose of MDMA reads industrial and/or commercial meters with fixed AMR technology function
is to

permit company to improve the billing process, make it more cost effective, more comfortable to the clients, reduce probability of error in the reading

To reduce utility company operating

It also permits to stream line the settlement system, making it faster and more transparent

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators

Etc)

Customers

Meters

performing

Retrieve meter data

with key interfaces between

MDMAs and meters

MDMAs and Settlement System

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high (billing purposes)

Data frequency is low

with security requirements of

High security level and confidentiality to keep safe this data (that have financial implications)

To keep private individual energy consumption

And also to avoid tampering and other acts, that put in risk the financial process

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	2.0	3.0	2.0	3.0	2.6

COMMENTS:
The following comments were collected during the team rating review:

Config=3 still large but not as large as residential but dispersed locations

QoS = 2 because need for timeliness and accuracy of cost-sensitive data Data Mgmt=2 high volume of data Constraint=3 high cost of some media/interfaces/transports Security=3 this is the cash

Non repudiation of meter configration changes

The following comments were collected during the peer review:

2 - higher performance -- sub second delays

I'm surprised that the time dimension isn't stressed here. Just like Fedex, speedier availability of the data and the settlement process has tremendous value that the digital society will be able to tap into. In particular, add "deliver" and "provide access to" under Performing; change "medium" to "high" regarding availability, and "low" to "high" regarding data frequency, under Quality of Service. Also change "infrequent" to "frequent" under Data Management. Quality of Service & Data Management should be ranked at least 2.5. Otherwise it will be a slow, garbage-in/garbage out middleman at best. The lightspeed interactions of the Digital Society will need trustworty data available on a moment's notice.

-- William Smith - 27 Jun 2003

C-1.3 MDMA reads residential meters with fixed AMR technology

The Purpose of MDMA reads residential meters with fixed AMR technology function
is to

permit company to improve the billing process, make it more cost effective, more comfortable to the clients, reduce probability of error in the reading

To reduce utility company operating

It also permits to stream line the settlement system, making it faster and more transparent

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators

Etc)

Customers

Meters

performing

Retrieve meter data

with key interfaces between

MDMAs and meters

MDMAs and Settlement System

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high (billing purposes)

Data frequency is low

with security requirements of

High security level and confidentiality to keep safe data with financial implications

To keep private individual energy consumption

And also to avoid tampering and other acts, that put in risk the financial process

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	3.0	2.0	3.0	2.4

COMMENTS:
The following comments were collected during the team rating review:

Config=3 large quantity of connections;

QoS=1 need for "last gasp" communications from meter on loss of power Data Mgmt=2 high volume of data Constraint=3 high cost of some media/interfaces/transports Security=3 this is the cash

Non repudiation of meter configration changes

The following comments were collected during the peer review:

3 - Ultra high performance -- guaranteed bandwidth determinacy

Similar comments to those in 1.2. This portrayal completely overlooks the opportunity for AMR to interoperate with digitally-enhanced residences (e.g., home automation). Add "data presentment" to Purpose, change things to reflect needs for High Data Availability, High Frequency Data/Updates.

-- William Smith - 27 Jun 2003

C-1.4 MDMA provides individual and aggregated meter readings to market settlements, DisCos, and/or TransCos

The Purpose of MDMA provides individual and aggregated meter readings to market settlements, DisCos, and/or TransCos function
is to

permit to stream line the settlement system, making it faster and more

It permit customers to know accurately their load profile, helping then to select the most suited tariff

It permit DisCos and TransCos to perform energy and power balances to use for billing purposes, planning

To reduce risk when signing settlements to both parties (now the load profile is more certain)

directly involving

MDMAs (DisCos, Energy Services Provider-ESPs, GenCos, Scheduling Coordinators (if they exist), etc), Customers

ISO/RTOs, TransCos, Settlement System, Historical Records, , Meters, Billing System, Accounting System, ESP-SCADA/EMS

performing

Provide final energy data and reporting to support billing and settlement processes

with key interfaces between

MDMAs and Settlement System

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One* to one between MDMAs and Settlement system over WAN

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability, data accuracy high (billing purposes), data frequency is

High volume of data between MDMA and settlement system

with security requirements of

Confidentiality (normal) and high security level to allow proper settlement and market processes

with data management requirements of

Large metering database with infrequent updates

Data is exchanged with other units inside and outside of the organization

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Security=3 this it cash register data

Data Mgmt= 1 additional use of existing data, which is alread acquired

If this is not AMR supported, then it probably doesn't need changing, because it will be inadequate to meet Digital Society needs. The aggregation function is critical to freeing the bounds of current metering/settlement approaches so customers can take advantage of new services and relationships with their energy providers. The more automated (and the more the feedback timescale shrinks), the better.

-- William Smith - 27 Jun 2003

C-1.5 MDMA or DisCo provides individual energy usage and billing to customers

The Purpose of MDMA or DisCo provides individual energy usage and billing to customers function
is to

permit to make more transparent the billing

It permit customers to know accurately their load profile, helping then to select the most suited tariff

In market where small customer chose Energy provider it helps to reduce risk when signing settlements (now the load profile is more certain)

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators (if they exist)

Etc)

Customers

Meters

Settlement System

Historical Records

Meters

Billing System

Accounting System

ESP-SCADA/EMS

Web page

performing

Provide final energy data and reporting to support billing processes

with key interfaces between

MDMAs and Settlement System

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One* to one between MDMAs and Settlement system over WAN

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high (billing purposes)

Data frequency is low

with security requirements of

Confidentiality (normal) and high security level to allow proper billing process

with data management requirements of

Large metering and billing databases with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:
This function has similar interfaces (and ratings) to function (C-1.4) MDMA provides individual and aggregated meter readings to market settlements, DisCos, and/or TransCos above.

Ditto (see C1.4). Also there are a number of missing word/odd wordings/typos in C1.4 and C1.5.

-- William Smith - 27 Jun 2003

C-1.6 Prepay metering

The Purpose of Prepay metering function
is to

Allow clients a better control of their energy costs

Eliminate the reading process and its costs

And reduce working capital of the energy provider

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators (if they exist)

Etc)

Customers

Meters

Settlement System

Historical Records

Meters

Billing System

Accounting System

ESP-SCADA/EMS

performing

meters provide energy already paid (through cards for example), MDMA compute energy

* Here I assuming a prepaid scheme that require connection with MDMA or ESP

with key interfaces between

ESP SCADA/EMS and Settlement System

with communication configuration requirements of

One to one between ESP SCADA/EMS and Settlement System over WAN

with quality of service requirements of

Medium availability

Data accuracy high

Low data frequency

with security requirements of

High security level and confidentiality to keep private individual energy consumption and also to avoid tampering u other source of error

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

Low value item. May be good for electricity provider for managing customers whose accounts tend to be delinquent regarding payment.

-- William Smith - 27 Jun 2003

C-1.7 Non-electric metering -- subcontracted submetering for non-electric utilities -- Note: focus on aspects of shared infrastructure and not the actual metering

The Purpose of Non-electric metering -- subcontracted submetering for non-electric utilities -- Note: focus on aspects of shared infrastructure and not the actual metering function
is to

use the economies and cost reductions that bring the common (or shared) use of one metering system with other services (water

telephone, etc)

directly involving

MDMAs (DisCos, Energy Services Provider-ESPs, GenCos, Scheduling Coordinators (if they exist), etc), Customers, Meters, Gas Companies, Water Companies, Billing System, Accounting System, Other services

In a aggregate way it involves also ISO/RTOs, TransCos, Settlement System, Historical Records, ESP-SCADA/EMS

performing

Retrieve meter data from different services (electricity

Gas

Etc)

with key interfaces between

Electric meters and gas meters

Electric meters and water meters

MDMAs and meters

MDMAs and Electric Billing/Accounting/Settlement Systems

MDMAs and Gas Companies

MDMAs and Water Companies

with communication configuration requirements of

One to one between different types of meters

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high

Data frequency is low because it is not frequently read

with security requirements of

High security level and confidentiality to keep safe this data (that have financial implications)

To keep private individual energy/gas/water consumption

And also to avoid tampering and other acts, that put in risk the financial process

with data management requirements of

Large metering database with infrequent updates

Exchange of information across organizational boundaries

with constraints of

Interfaces between electric

Gas

And water meters are media-constrained

Compute-constrained

And power-constrained

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	2.0	3.0	2.0	3.0	2.6

COMMENTS:
The following comments were collected during the team rating review:

Config =3 due to communications of gas and water meters to electric meter-reading system

QoS = 2 due to need by some (larger) customers for high availability of information in real-time

Security =3 different issues where different clients have rights to subsets of information from a single device

Data Mgmt =2 due to cross-organizational data flows and large amounts of data

Constraints = 3 due to media-constrained

Compute-constrained

And power-constrained interfaces between electric

Gas

And water meters to the meter-reading system

Agree with the ratings. Not sure why this hasn't caught on; we've talked about it for 20 years that I know of. Might be facilitated in areas where the metering function is outsourced by all utilities; then a 3rd party can invest in the multifunction metering interface.

-- William Smith - 27 Jun 2003

C-1.8 Sub-metering -- customer bill disaggregation and rental space allocations

The Purpose of Sub-metering -- customer bill disaggregation and rental space allocations function
is to provide customers options of disaggregation of their bills allowing them to distribute the energy cost properly among their users
directly involving

MDMAs

Customers

Meters

Billing System

performing

Provide final energy data and reporting to support disaggregated billing process

with key interfaces between

MDMAs and meters

ESP-Billing system

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One to one between ESP and Billing system

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy medium

Low data frequency

with security requirements of

High security level and confidentiality

with data management requirements of

Large metering database (each consumer could be consider with more fields) with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

This will probably be most helpful to the customer for controlling energy costs at the end use level, and to energy companies looking to promote end-use oriented programs and services.

-- William Smith - 27 Jun 2003

C-1.9 Non-intrusive load monitoring -- deducing load contributions by monitoring aggregate consumption changes

The Purpose of Non-intrusive load monitoring -- deducing load contributions by monitoring aggregate consumption changes function
is to

Prevent customer emergencies, faults, etc by notifying them when they face no-normal raises in their loads (possible fail)

Estimate load profile of unknown loads by aggregate estimation

directly involving

MDMAs

Customers

Meters

Load Monitoring Software and Equipment

performing

Monitor load

Diagnostic faults and estimate unknown loads

with key interfaces between

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

High availability

Data accuracy medium

High data frequency

with security requirements of

Medium security level and confidentiality

with data management requirements of

Large metering database with more frequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	2.0	1.0	1.2

COMMENTS:
This function has similar interfaces (and ratings) to function (C-9.4) Improve power quality through data acquistion and supervisory control above.

The following comments were collected during the team rating review:

Data Mgmt=2 implementation needs to be tuned to the customer installation

EPRI has a long history (we were a pioneer) with this technology. It has potential cost advantages over "wired" approaches. What's the tradeoff against today's wireless configurations? Quality of Service and Data Management seem low, and their interaction with Configuration seems understated/underrated. Config 1.5 to 2.0 seems more reasonable, as does Quality of Service 2.0.

-- William Smith - 27 Jun 2003

C-1.10 Outage detection

The Purpose of Outage detection function
is to Narrow down location of broken/misoperating power system infrastructure
directly involving

MDMAs

Customers

Meters

Historical Records

ESP-SCADA/EMS

performing

Identify meters without power or non-responsive to infer affected equipment location

with key interfaces between

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

High availability

Data accuracy medium

High data frequency

with security requirements of

Medium security level

with data management requirements of

Large metering database with frequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	1.0	0.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Config=2 coordination with dist sys protection

QoS=2 performance

Security=2 reaches into home

The following comments were collected during the peer review:

Essentially same, as item 15B

This can be a high value item for both the energy company and the customer. I'd suggest trying to piggyback some of the AMR-enabled items above to provide higher value based on the higher requirements for Quality of Service and Data Management. Data Management should be rated 2.0.

-- William Smith - 27 Jun 2003

C-2 Customer Management

The Purpose of Customer Management function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.3	1.0	1.7	1.5	1.0	1.3

COMMENTS:

See comments below. Given the number of involved parties these activities try to connect, the ratings should be substantially higher. This issue is a fundamental impediment to functioning competitive electricity markets. Also, I wonder if some of the myriad involved parties noted below shouldn't also be included in items 1.1 to 1.10.

-- William Smith - 27 Jun 2003

C-2.1 ESP interfaces with customers to provide tamper detection, load profiles, etc. services to DisCos

The Purpose of ESP interfaces with customers to provide tamper detection, load profiles, etc. services to DisCos function
is to

Provide ESP/DisCo with necessary tamper protection

Load profile

And other basic customer management services

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators (if they exist)

Etc)

Customers

Meters

Settlement System

Historical Records

Meters

Billing System

Accounting System

ESP-SCADA/EMS

Web page

performing

Basic management of customer meter

Connection point

with key interfaces between

MDMAs and meters

MDMAs and Settlement System

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high

Data frequency is low because it is not frequently read

with security requirements of

High security level and confidentiality to keep private individual energy consumption and also to avoid tampering u other source of error

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Config=2 large number of devices

Data Mgmt=2 5 minute profile data to manage

Please add definitions for acronyms like ESP, EMS, etc

-- Philip Jacobs - 17 Apr 2003

I see that these in particular are listed at first use but others are not, Dis Co. Maybe link each acronym to a definition in a glossary?

-- Philip Jacobs - 17 Apr 2003

This function would be a prime candidate for AMR enabling. That would up the rating for Quality of Service.

-- William Smith - 27 Jun 2003

C-2.2 ESP provides connect, disconnect, energy usage and billing information, etc. to customers

The Purpose of ESP provides connect, disconnect, energy usage and billing information, etc. to customers function
is to

Provide ESP/DisCo with necessary tamper protection

Load profile

And other basic customer management services

directly involving

MDMAs (DisCos

Energy Services Provider-ESPs

GenCos

Scheduling Coordinators (if they exist)

Etc)

Customers

Meters

Settlement System

Historical Records

Meters

Billing System

Accounting System

ESP-SCADA/EMS

Web page

performing

Basic management of customer meter

Connection point

with key interfaces between

MDMAs and meters

MDMAs and Settlement System

with communication configuration requirements of

One* to many between MDMAs and meters over WAN

One* to one between MDMAs and Settlement system over WAN

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability

Data accuracy high

Data frequency is low because it is not frequently read

with security requirements of

High security level and confidentiality to keep private individual energy consumption and also to avoid tampering u other source of

Higher security due to connect/disconnect capability - life safety issue

with data management requirements of

Large metering database with infrequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	3.0	2.0	1.0	1.8

COMMENTS:
The following comments were collected during the team rating review:

Config=2 large number of devices

Data Mgmt=2 5 minute profile data to manage

Security=3 control

This function would be a prime candidate for AMR enabling. That would up the rating for Quality of Service.

-- William Smith - 27 Jun 2003

C-2.3 ESP provides DisCo with information for updating relevant databases

The Purpose of ESP provides DisCo with information for updating relevant databases function
is to

permit to stream line the settlement system, making it faster and more

It permit customers to know accurately their load profile, helping then to select the most suited tariff

It permit DisCos and TransCos to perform energy and power balances to use for billing purposes, planning

To reduce risk when signing settlements to both parties (now the load profile is more certain)

directly involving

MDMAs (DisCos, Energy Services Provider-ESPs, GenCos, Scheduling Coordinators (if they exist), etc), Customers

ISO/RTOs, TransCos, Settlement System, Historical Records, , Meters, Billing System, Accounting System, ESP-SCADA/EMS

performing

Provide final energy data and reporting to support billing and settlement processes

with key interfaces between

MDMAs and Settlement System

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One* to one between MDMAs and Settlement system over WAN

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

Medium availability, data accuracy high (billing purposes), data frequency is

High volume of data between MDMA and settlement system

with security requirements of

Confidentiality (normal) and high security level to allow proper settlement and market processes

with data management requirements of

Large metering database with infrequent updates

Data is exchanged with other units inside and outside of the organization

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	2.0	2.0	1.0	1.4

The following comments were collected during the peer review:

ESP to DisCo Link

I'm surprised that the ratings are so low. We're talking about interoperability between multiple parties of an extremely high value item. That's pretty complex. I'd up the Configuration and Quality of Service items to at least 2.0. I'd also change the bullets above to reflect the need for high availability and frequent updates. Also, a major constraint is the potential incompatibility of between the involved parties' data management systems and data requirements. I'd up constraints to 2.0.

-- William Smith - 27 Jun 2003

C-3 Customer trouble call management

The Purpose of Customer trouble call management function
is to

Permit to shorten the out time due to faults in the distribution networks

Allowing the distribution companies to better use their repair crews and minimize the down time for customers (without increasing the level of redundancy of the distribution systems)

directly involving

Energy Services Providers ESPs

Customers

Distribution Operations and Distributed Resources

Historical Records

performing

ESPs / DisCos

Receive trouble calls

ESPs / DisCos generate trouble ticket

ESPs / DisCos check SCADA-EMS

ESPs send a crew*

Crew communicate via radio (internet-notebook-handheld also)

Crew perform manual or request switching operations*

ESPs / DisCos update statistics

* if necessary

with key interfaces between

Customer and ESPs / DisCos

ESPs / DisCos and Quality of Service Management Program

with communication configuration requirements of

One* to many between ESPs/DisCos and Customers over Phone, Internet u other

One to one between ESPs/DisCos and Quality of Service Management

*One in case on one ESPs/DisCos

with quality of service requirements of

High availability

Rapid respond

Specially during emergencies or contingencies

Data accuracy high

A rapid response is required to minimize a possible out of standard service

with security requirements of

Medium security requirement

with data management requirements of

Large databases randomly updated with

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	1.0	1.0	1.0

COMMENTS:

Some of the requirements here could underwrite some of the improvements noted in earlier comments above. However, I'm unfamiliar with this function. I also wonder if cell phones, etc. won't suffice for the extracompany activities.

-- William Smith - 27 Jun 2003

C-3.1 Customer reports trouble and trouble ticket is generated (see Call Center Management and Support under Information Management Domain)

The Purpose of Customer reports trouble and trouble ticket is generated (see Call Center Management and Support under Information Management Domain) function
is to permit to inform the company about a trouble with a customer in order to start working on solve that
directly involving

Energy Services Providers ESPs

Customers

Distribution Operations

Historical Records

performing

Customers notify ESPs / DisCos

ESPs / DisCos generate trouble ticket

with key interfaces between

Customer and ESPs / DisCos

ESPs / DisCos and Quality of Service Management Program

with communication configuration requirements of

One* to many between ESPs/DisCos and Customers over Phone, Internet u other

One to one between ESPs/DisCos and Quality of Service Management

*One in case on one ESPs/DisCos

with quality of service requirements of

High availability

Rapid respond

Specially during emergencies or contingencies

Data accuracy high

A rapid response is required to minimize a possible out of standard service

with security requirements of

Medium security requirement

with data management requirements of

Large databases randomly updated with

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	1.0	1.0	1.0

COMMENTS:

C-3.2 Trouble ticket is used by outage management function (see Distribution Operations)

The Purpose of Trouble ticket is used by outage management function (see Distribution Operations) function
is to obtain all the data about the fault to solve it as fast as possible
directly involving

ESPs

Customers

Distribution Operations

Historical Records

performing

ESPs / DisCos check SCADA-EMS

ESPs send a crew*

Crew communicate via radio (internet-notebook-handheld also)

Crew perform manual or request switching operations*

* if necessary

with key interfaces between

ESPs / DisCos and Quality of Service Management Program

with communication configuration requirements of

One* to many between ESPs/DisCos and Customers over Phone, Internet u other

*One in case on one ESPs/

One to many between ESPs/DisCos and crew

with quality of service requirements of

High availability

Rapid respond

Specially during emergencies or contingencies

Data accuracy high

A rapid response is required to minimize a possible out of standard service

with security requirements of

High security requirement to keep a clean Quality of service management program

with data management requirements of

Large databases randomly updated with

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	1.0	1.0	1.0

COMMENTS:

C-3.3 Trouble ticket is used for statistical analysis (see Distribution Operations)

The Purpose of Trouble ticket is used for statistical analysis (see Distribution Operations) function
is to keep updated the outage statistics to compute quality indexes, pay fines or compensate (if the regulatory scheme consider that)., plan network improvements
directly involving

ESPs

Customers

Distribution Operations

Historical Records

performing

ESPs / DisCos update statistics

with key interfaces between

ESPs / DisCos and Quality of Service Management Program

ESPs / DisCos and Historical Records

with communication configuration requirements of

One to one between ESPs/DisCos and Quality of Service Management Program

One to one between ESPs/DisCos and Historical Records

with quality of service requirements of

High availability to keep an accurate record of outages

Failures

Etc

with security requirements of

High security requirement to keep an accurate record of outages

Failures

Etc

with data management requirements of

Large databases randomly updated with

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	1.0	1.0	1.0

COMMENTS:

C-4 Real-time Pricing (RTP)

The Purpose of Real-time Pricing (RTP) function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.5	2.5	3.0	2.0	2.0	2.4

COMMENTS:

This is certainly one of the defining horizons for CEIDS, with stringent requirements on all fronts, including regulatory policy.

-- William Smith - 27 Jun 2003

C-4.1 ESP issues updated RTP schedules for subscribing customers

The Purpose of ESP issues updated RTP schedules for subscribing customers function
is to

To create a two-way communication channel that sends information to the customers

to allow them to plan and modify their load and generation in response to price signals in "real-time" (operational timeframe which can range from seconds to days ahead), and to provide real-time information about the behavior of the customer in response to the price

This service shall not be limited to

energy

Other services such as voltage regulation (reactive power),

contributions to frequency regulation, and contribution to reserves can also be part of this protocol, once again both for purposes of conveying to the customer what is desired and at what price, and to measure and record what the customer is providing to the system
directly involving

Market Operations

Energy Services Providers

Customers

Distribution Operations

Transmission Operations

And Distributed Resources

performing

The computation of base RTP by Market operations, calculation of specific RTPs by

ESPs, posting and/or multicasting of RTPs to specific and/or to all customers, determination and recording of customer generation and load and its correlation to the RTP signals, scheduling of loads and DR based on RTP, management of loads and DR in real-

This includes scheduling and metering not only energy but of

ancillary services as well

with key interfaces between

ESPs and Market Operations (DisCo

RTO

TransCo)

ESPs and Customer Building Automation systems

with communication configuration requirements of

Multicast of RTP data to large numbers of customers

Within contractual timeframes

With contractual availability

And collection and transmittal of customer

Information back to a collection site for purposes of settlement and payments based

On both RTP and quantities of various items for, which a contract has been

Established

with quality of service requirements of

High availability of RTP data

Timeliness of RTP data

with security requirements of

authentication of RTP data,

non-repudiation of RTP data, accurate audit logs, and sufficient redundancy to ensure that information from the user about its production and/or consumption of energy and other ancillary services is not only sent back but also archived and reasonably secure from failures in the real time communications

See Energy

Scheduling and DR Management for additional requirements

with data management requirements of

Large numbers of customers

with constraints of

New applications

Many different types of systems

Unvalidated cost-benefit

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	3.0	2.0	1.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

Config=2 large number of customer sites

QoS = 2 due to need for highly accurate financial information

Security=3 controlling load; financial consequence of tampering

Data Mgmt=2 volume

The Configuration issues for this function have a significant impact on the IECSA architecture, because the ESPs will need to have multi-cast communications links with a large number of dispersed customers, ranging from large industrial and commercial customers to small residential customers. These communication links will also need to have high overall availability and rapid response times (probably on the order of a few minutes) so that the customers are provided with pricing information in a timely manner that meets the market tariff requirements. The security of these communication links will need to be very high, both because there could be significant market operations financial consequences to eavesdropping, modification of data, or denial of service, but also because the information could be used for controlling loads, which could impact customer operations, and therefore have direct impacts on customer finances. Finally, the ESP will need to manage a large amount of data from the different customers that it serves, and may have significant and on-going changes in customers, customer tariffs, and value-added services with those customers, making data management a significant issue.

-- Frances Cleveland - 01 May 2003

I concur with Frances' comments. I'm a little confused about the terms "base RTP" and "specific RTP" -- are you assuming a 2 part price structure with baselines? Adding in responsiveness to reserve issues and ancillary services (1 minute, 4 sec in CA) will greatly add to the time-sensitive information transfer and physical action requirements.

-- William Smith - 27 Jun 2003

C-4.1.1 ESP receives base RTP schedule from Market Operations

The Purpose of ESP receives base RTP schedule from Market Operations function
is similar to function (C-4.1) ESP issues updated RTP schedules for subscribing customers above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	3.0	2.0	1.0	2.0

COMMENTS:

C-4.1.2 ESP calculates customer-specific RTP schedules

The Purpose of ESP calculates customer-specific RTP schedules function
is similar to function (C-4.1) ESP issues updated RTP schedules for subscribing customers above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	3.0	2.0	1.0	2.0

COMMENTS:

C-4.1.3 ESP multicasts RTP schedules to customers

The Purpose of ESP multicasts RTP schedules to customers function
is similar to function (C-4.1) ESP issues updated RTP schedules for subscribing customers above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	3.0	2.0	1.0	2.0

COMMENTS:

C-4.2 Customer EMS manages energy usage based on RTP

The Purpose of Customer EMS manages energy usage based on RTP function
is to Manage energy usage based on pricing signals
directly involving

ESP RTP calculation engine/database

Customer user interface

Customer EMS

performing

Load control

Process

And staff scheduling

with key interfaces between

Customer Building Automation systems to End Devices

with communication configuration requirements of

Multicast of load and generation control commands within buildings

Campuses

And wider areas

with quality of service requirements of

High availability of control commands and monitored information

with security requirements of

High security due to control of end devices

with data management requirements of

Large numbers of a large variety of end devices

with constraints of

New applications

Many different types of systems

Unvalidated cost-benefit

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	3.0	3.0	2.0	3.0	2.8

COMMENTS:
The following comments were collected during the team rating review:

Config=3 large quantity of end devices in different areas

QoS = 3 due to need for highly accurate financial information

Security=3 controlling loads

Financial consequence of tampering

Data Mgmt=2 due to many different types of end devices and their needs

Constraints = 3 due to diversity of end devices

Compute-constrained nature of end devices

The configuration rating reflects the issue that customers could have a very large variety of end devices that they would like to control, possibly dispersed over large buildings or campuses. This means that there would be an architectural challenge for each customer on how best to handle a possible mix of media, end-device monitoring and control requirements, and possibly different protocols. Since controlling loads and/or DER devices could have significant financial impacts on a customer's business, the communications would need high availability and appropriately reliable response timing. For the same reasons, security will need to be very high to avoid financial consequences from tampering, including ensuring the security and accuracy of the audit records. Data management of the monitoring and control of the customer's end devices could provide challenges due to the large variety and varying characteristics of these end devices. In addition, the media to the end devices could be limited in bandwidth, and the end device controllers could be constrained in compute capabilities.

-- Frances Cleveland - 01 May 2003

I again agree with Frances' comments. Please change the term "end devices" to "end-use technologies" Clark won't like the first one.

-- William Smith - 27 Jun 2003

C-4.2.1 Customer EMS determines optimal mix of current load, deferred load, and DR generation, based on RTP schedule

The Purpose of Customer EMS determines optimal mix of current load, deferred load, and DR generation, based on RTP schedule function
is similar to function (C-4.2) Customer EMS manages energy usage based on RTP above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	3.0	3.0	2.0	3.0	2.8

COMMENTS:

C-4.2.2 Customer EMS implements load and DR management

The Purpose of Customer EMS implements load and DR management function
is similar to function (C-4.2) Customer EMS manages energy usage based on RTP above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	3.0	3.0	2.0	3.0	2.8

COMMENTS:

C-5 Load management

The Purpose of Load management function
is to

Permit companies make a better use of their installed capacity by reducing the system peak

Make the system more secure and more responsive to contingencies

directly involving

Energy Services Providers

Customers

Distribution Operations and Distributed Resources

performing

Managing controllable loads (Ex: radio controled A/C system

Heaters

Etc) and applying curtailment/interruptions/load shedding schemes

ESPs send a crew (if not remote control is available)

Crew communicate via radio and mobile phone (internet-notebook-handheld also)

Crew perform manual operations

with key interfaces between

Energy Services Providers / DisCos to Customer Controllable Load/Equipment

Energy Services Providers to Distribution Operation (crew)

with communication configuration requirements of

One to many between ESPs/DisCos and distributed Customer Controllable Load/Equipment

One to one between ESPs/DisCos and Distribution Operation (crew communication through radio

Mobile phone lines)

with quality of service requirements of

High availability

Rapid response

Data accuracy high

A rapid response is required to keep load/generation equilibrium and to minimize a possible out of standard service

with security requirements of

High security requirements to avoid undesirable disconnections in customers loads

with data management requirements of

Large databases randomly updated with events (mainly during contingencies and peak demand)

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	2.5	2.1

COMMENTS:

I find this one somewhat archaic. The prevailing term nowadays is Demand Response (e.g., Program 90). The discussion above focuses only on the response to reliability constraints, and seems to mix rotating outages in with curtailment programs. It completely misses the economic motivations (spot prices) that have led to sophisticated demand bidding programs. The low Quality of Service rating is quite astounding. Suggest complete rewrite, as this function has critical needs akin to those of RTP. See EPRI Reports 1006015 (New Principles for Demand Response Planning) and 1006017 (Demand Trading) for insights into how to proceed.

-- William Smith - 27 Jun 2003

C-5.1 ESP applies direct load control measures - residential

The Purpose of ESP applies direct load control measures - residential function
is to Allow company to reduce load and in that way the installed capacity required making the system safer under contingencies
directly involving

Energy Services Providers

Customers

Customer Controllable Load/Equipment

Distribution Operations and Distributed Resources

performing

Managing controllable loads (Ex: radio controlled A/C system

Heaters

Etc) and applying curtailment/interruptions/load shedding schemes

with key interfaces between

Energy Services Providers / DisCos to Customer Controllable Load/Equipment

Energy Services Providers to Distribution Operation (crew)

with communication configuration requirements of

One to many between ESPs/DisCos and distributed Customer Controllable Load/Equipment

One to one between ESPs/DisCos and Distribution Operation (crew communication through radio

Mobile phone lines)

with quality of service requirements of

High availability

Rapid response

Data accuracy high

A rapid response is required to keep load/generation equilibrium and to minimize a possible out of standard service

with security requirements of

High security requirements to avoid undesirable disconnections in customers loads

with data management requirements of

Large databases randomly updated with events (mainly during contingencies and peak demand)

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	3.0	2.2

COMMENTS:
The following comments were collected during the team rating review:

Config=3 links to large numbers of customers

Security=2 authentication of user/class

Data Mgmt=2 large numbers of customer groups

Constraints=3 compute-constrained

Media constrained

This is pretty basic stuff. The only new twist here is that we can now piggyback on existing digitial backbones (e.g., cell, pager). The fundamental flaws with remote devices (cycling switches, smart thermostats) remain; the remote technologies and strategies employed lead to customer overkill and free riders.

-- William Smith - 27 Jun 2003

C-5.1.1 Applies/requests direct load control (cycle water heaters, air conditioners, and other loads)

The Purpose of Applies/requests direct load control (cycle water heaters, air conditioners, and other loads) function
is similar to function (C-5.1) ESP applies direct load control measures - residential above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	3.0	2.2

COMMENTS:

Should address "rebound" effects at the end of the control period. Need pretty sophisticated strategy to avoid adverse infrastructure impacts.

-- William Smith - 27 Jun 2003

C-5.1.2 Curtails customer loads

The Purpose of Curtails customer loads function
is similar to function (C-5.1) ESP applies direct load control measures - residential above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	3.0	2.2

COMMENTS:

I'm totally confused about the difference between direct load control as used here, and "curtailing [residential] customers." Is this rotating outages in subdivisions? Please clarify.

-- William Smith - 27 Jun 2003

C-5.1.3 Interrupts customer loads

The Purpose of Interrupts customer loads function
is similar to function (C-5.1) ESP applies direct load control measures - residential above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	3.0	2.2

COMMENTS:

Same issues -- I don't understand what differentiation you are getting at among these terms with respect to the residential sector.

-- William Smith - 27 Jun 2003

C-5.1.4 Sheds customer loads (under frequency / under voltage)

The Purpose of Sheds customer loads (under frequency / under voltage) function
is similar to function (C-5.1) ESP applies direct load control measures - residential above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	2.0	3.0	1.0	1.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

Config=3 will involve comm to home and comm in house

QoS=2 sub-second (100ms) performance in the home

Security=3 don't want undesired remote access

This one's pretty clear. Would the actuation be done by a device in the customer's home?

-- William Smith - 27 Jun 2003

C-5.1.5 Requests load-reducing volt/var control

The Purpose of Requests load-reducing volt/var control function
is similar to function (C-5.1) ESP applies direct load control measures - residential above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	3.0	2.2

COMMENTS:

Has anyone estimated the relative value of this control to the standard demand reduction approaches? Also, per extensive conversations with the Cal-ISO, voltage reductions aren't quite CA's cup of tea. Seems more applicable back east. Don't know what the story is with VARs in this context (other than their relation to voltage support).

-- William Smith - 27 Jun 2003

C-5.2 Permissive power provision -- devices can request a limit of power. This would allow an emegency device to use power while other loads might not. Scheduled and load limited. Authenticated level control

The Purpose of Permissive power provision -- devices can request a limit of power. This would allow an emegency device to use power while other loads might not. Scheduled and load limited. Authenticated level control function
is to permit devices to request limited amout of power for emergency/housekeeping functionality without fee or billing agreement in place
directly involving

ESP

Customers

Individual load equipment

performing

Load control based on equipment type

Load requirements

Customer class and location

with key interfaces between

ESP

Customer databases

Billing systems

Payment history

Individual load equipment

with communication configuration requirements of

One to many between ESPs/DisCos and distributed Customer Controllable Load/Equipment

with security requirements of

High security requirements to avoid undesirable disconnections in customers loads

with data management requirements of

Large databases, large numbers of

Data exchanges with other units of the company

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	2.0	2.0	2.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

Config=3 potential national identity issue - recognizing the user anywhere in the contry/world

Security=2 authentication of user/class

Data Mgmt=2 point of sale issues

Constraints=2 unknown application

This is quite clever. I'd like to hear more. Might be applicable beyond the residential sector. We tried a variant of it in our response to the 2001 CA Power Crisis.

-- William Smith - 27 Jun 2003

C-6 Building/Home Energy Management Services

The Purpose of Building/Home Energy Management Services function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.8	1.0	2.0	1.2	1.0	1.4

COMMENTS:

This activity has traditionally a hard sell to residential end-use customers. Most home automation firms have tried to get electric/telecommunications utilities to play a marketing/business partner role, to no avail. While the benefits from energy cost reductions usually outclasses the security and medical alarm capabilities, these benefits still don't seem to meet threshold requirements for achieving high market penetration of home automation. What architectural changes are being proposed that would help?

-- William Smith - 29 Jun 2003

C-6.1 ESP monitors building security systems (illegal entry, environmental alarms, health care signals, etc.) - no remote control

The Purpose of ESP monitors building security systems (illegal entry, environmental alarms, health care signals, etc.) - no remote control function
is to see item 14 below

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.7	1.2	2.2	1.6	1.2	1.6

COMMENTS:
The following comments were collected during the peer review:

See #14 below

See comment on 6.0. Retrofit installations do come with some constraints. Depending on the interoperability desired with outside parties, Quality of Servie and Data Management might be revalued to the 2.0 range.

-- William Smith - 29 Jun 2003

C-6.2 Customer EMS manages building environment, based on preset parameters (security settings, temperature, appliances, lighting management, etc.)

The Purpose of Customer EMS manages building environment, based on preset parameters (security settings, temperature, appliances, lighting management, etc.) function
is to provide energy management expertise and supervision to customer purchased energy management equipment
directly involving

Service provider

Contractor

Customer

Customer facility

Tenant

performing

Load survey

Analysis

Equipment advice and planning

Installation contracting assistance

Monitoring of alarms

Dispatching

Customer gui gateway

with key interfaces between

Service provider

Contractor

Customer

Customer facility

Tenant

with communication configuration requirements of

Sensor configuration information

Setpoints for alarms / alerts

Subsystem control algorithm selection

with quality of service requirements of

Limits of communications to user interface and supervisory control and monitoring (not direct control)

Medium-high availability

Multiparty simultaneous access

with security requirements of

Privacy

Confidentiality

Authentication

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

with constraints of

large library of analytical tools and control algorithms and equipment

High level of control domain expertise for engineering and support required

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because of a large number of devices, significant setup information that must be communicated and varied low level communication protocols to these

Security=2 because building security management (alarm systems) may be controlled

Given that this section seems to advocate the real-time interaction with ESPs depending on the ESPs operations, availability should probably be high. Data frequency (under Data Management) should be added as a high. I'm suprised to see Constraints and Data Management rated only a 1, given what's under that category; I'd add the need for real time access and operations (with ESP) under Constraints, too.

-- William Smith - 29 Jun 2003

C-6.3 Customer status/control of building environment locally and/or remotely by modifying parameters

The Purpose of Customer status/control of building environment locally and/or remotely by modifying parameters function
is to provide secure access to customer site through managed network
directly involving

Service provider

Customer

Service providers gateway

Installation/service personnel

performing

Gateway services between data access protocols and "web browser"

Management of security relationship with customer site

with key interfaces between

Service provider

Customer

Service providers gateway

with communication configuration requirements of

Customer premise layout and sensor network

Supervisory control over ems and security system

Reporting options

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable remote user interface (less than 1 sec?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

Non-repudiation of customer intiated actions

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	3.0	1.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because of a large number of devices, significant setup information that must be communicated and varied low level communication protocols to these

Security=3 remote control -most likely through the Internet

I find it odd that as more items are added to the Constraints category, the rating never moves up. My comments on 6.2 apply here, too.

-- William Smith - 29 Jun 2003

C-6.4 Customer EMS bids into power market for dynamic load profile

The Purpose of Customer EMS bids into power market for dynamic load profile function
is to provide dynamic optimization of customer energy cost through interaction with power markets
directly involving

Service provider

Customer

Customer facility management system

Power market

Customer meter

performing

Machine bidding for power consumption based on load profile offered and accepted

Power quality needs and exposures

Aggregation of customer loads to form bid pool

with key interfaces between

Service provider

Customer

Customer facility management system

Power exchange

Customer meter

with communication configuration requirements of

Bid pool mutual agreements

Contract with market participants

Association with revenue meter

with quality of service requirements of

reliable delivery of messages, can tolerate relatively large propagation delays (

hours?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Participation in external security regime

Non-repudiation of customer intiated actions

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	3.0	2.0	2.0	2.2

COMMENTS:
The following comments were collected during the team rating review:

Config=3 large number

Bi-directional

Security=3 audit trails

Contract information

Non-repudiation

Data Mgmt=2 many contracts & relationship must be in place for this function to operate

Contraints=2 regulatory issues

Parallelism to stock market automated trading where it is regulated to avoid positive feedback loops

The following comments were collected during the peer review:

Like e-bay for energy

This is more like it. Now Constraints are a 2, and contain fewer and less onerous items that previously. Quality of Service seems underrated (2.0?).

-- William Smith - 29 Jun 2003

C-6.4.1 machine bidding for power consumption

The Purpose of machine bidding for power consumption function
is similar to function (C-6.4) Customer EMS bids into power market for dynamic load profile above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	3.0	2.0	2.0	2.2

COMMENTS:

C-6.4.2 buildings of same owner collaborate on load profile

The Purpose of buildings of same owner collaborate on load profile function
is similar to function (C-6.4) Customer EMS bids into power market for dynamic load profile above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	3.0	2.0	2.0	2.2

COMMENTS:

This a key benefit to customers, ranging from bill consolidation to facilitate enegy cost control, to participating actively in competitive electricity markets.

-- William Smith - 29 Jun 2003

C-6.4.3 negotiate for poor power quality events

The Purpose of negotiate for poor power quality events function
is similar to function (C-6.4) Customer EMS bids into power market for dynamic load profile above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
3.0	1.0	3.0	2.0	2.0	2.2

COMMENTS:

I'm not quite clear regarding how power quality fits here, although it's intriguing conceptually. If an aggregate of remote actions can contribute to a PQ problem higher up in the system, then there might be quite a bit of value. However, the real-time and coordination requirements would be high (I see that Configuration is rated 3.0). I'd think that Data Management and Constraints might be >2.5, and Qof S a 2.0).

-- William Smith - 29 Jun 2003

C-6.5 Customer EMS tracks billing

The Purpose of Customer EMS tracks billing function
is to provide dynamic access to premise revenue meter to guide facility management
directly involving

Service provider

Customer

Customer facility management system

Power market

Customer meter

performing

Retrieval of current consumption

Bill to date

Pricing forecasts

Historic performance data

Power quality events

with key interfaces between

Service provider

Customer

Customer facility management system

Power market

Customer meter

with communication configuration requirements of

Meter access information

Customer identification information

Access rights / limitations for customer access

with quality of service requirements of

Reliable delivery of messages

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

Role based access control to isolate user permisions to view/read / change information

with data management requirements of

Access to customer information base for retrieval of historic data (not currently in meter)

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because of a large number of devices and multiple user applications that may need to take advantage of billing

Security=2 because of dealing with billing information to make

Data management=2 because of need to maintain data for each customer and make it available on demand

This is fine, unless you are interacting with real-time pricing or demand-bidding programs. Then things should be rated higher.

-- William Smith - 29 Jun 2003

C-6.5.1 EMS receives bill to date

The Purpose of EMS receives bill to date function
is similar to function (C-6.5) Customer EMS tracks billing above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

{Description??}

C-6.5.2 EMS receives pricing forecasts

The Purpose of EMS receives pricing forecasts function
is similar to function (C-6.5) Customer EMS tracks billing above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

{Description??}

C-6.5.3 EMS receives history data - minute by minute and events

The Purpose of EMS receives history data - minute by minute and events function
is similar to function (C-6.5) Customer EMS tracks billing above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

{Description??}

C-6.6 Offsite premise management

The Purpose of Offsite premise management function
is to provide remote access and monitoring to remote sites
directly involving

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Installation/service

performing

Data verification and validation

Gateway services between data access protocols and notification recipients

Management of security relationship with customer site

with key interfaces between

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Installation/service

with communication configuration requirements of

Customer premise layout and sensor network

Reporting options

Sensor confirmation tree

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable notification delay (~20 sec?)

Relatively infrequent access (ie mostly idle)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

For some sites with minimal requirements

POTS modem access may be most cost effective network connection

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	3.0	1.0	1.0	1.6

COMMENTS:
This function has similar interfaces (and ratings) to function (C-6.3) Customer status/control of building environment locally and/or remotely by modifying parameters above.

The following comments were collected during the team rating review:

Config=2 because of potential for large number of devices to control over varied lower level protocols and physical

Security=3 because Internet likey to be used and risk of unauthorized remote control of systems

Given the entries in the categories above, these seem quite underrated, except for Security. This where some of the trickier (but potentially higher value) capabilities come into play.

-- William Smith - 29 Jun 2003

C-6.6.1 Provide analysis and control of homes / businesses /vacation property

The Purpose of Provide analysis and control of homes / businesses /vacation property function
is similar to function (C-6.6) Offsite premise management above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	3.0	1.0	1.0	1.6

COMMENTS:

C-6.7 Occupancy based heating and lighting controls

The Purpose of Occupancy based heating and lighting controls function
is similar to function (C-6) Building/Home Energy Management Services above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
0.0	0.0	0.0	0.0	0.0	0.0

COMMENTS:
The following comments were collected during the peer review:

Local contol only

See comments above. Market is not sufficiently conducive that these systems can penetrate to a high degree in isolation.

-- William Smith - 29 Jun 2003

C-6.8 Building VAR Control

The Purpose of Building VAR Control function
is to dynamically adjust the power factor of the load in a building
directly involving

The building pf controller and the capacitor bank controller the supplier who set the pf penalty rates and the building energy management contractor and other local var controllers

performing

On/off control or linear control of power factor compensation in a facility

with key interfaces between

Pf controller and the compensation device

The utility and the controller

The energy management contractor and the controller

The pf controller and other pf controllers in the area

with communication configuration requirements of

One to one and many to many

with quality of service requirements of

Relatively high-speed data communications (sub-second) and high accuracy

with security requirements of

Authentication and access control for interface between various energy control systems

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	1.0	1.0	1.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

QoS=2 special case when closed loop control is implemented

This item has modest bottom line benefits to the system and the customer. It would seem to be a case where an aggregate of buildings can contribute to votage support.

-- William Smith - 29 Jun 2003

C-7 Weather

The Purpose of Weather function
is to provide access to real-time and historical weather data
directly involving

National weather service

Third party providers

Automated weather stations

Customer equipment

Automated warning systems

performing

On-line analysis

Event correlation

Storm track prediction

Impact prediction

with key interfaces between

Customer service

Crew dispatch

Operations

with communication configuration requirements of

Sensor connectivity over disparate networks

Internet

Serial interface

Satellite

Publish/subscribe model

Event triggers

Warning levels

with quality of service requirements of

Reliable delivery of messages

Real time data

Propogation delays of seconds OK

with security requirements of

Data from third parties subject to licensing restrictions so data must be secured to prevent unauthorized use

Anti-spoofing

with data management requirements of

Large databases of data may need to be maintained with fast retrieval

Large number of entities - similar to classic SCADA

with constraints of

Many legacy systems in place using proprietery protocols and data formats

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.7	1.0	1.0	1.3	1.0

COMMENTS:

C-7.1 Lightening and severe weather alert notification

The Purpose of Lightening and severe weather alert notification function
is to provide access to real-time and historical weather data
directly involving

National weather service

Third party providers

Automated weather stations

Customer equipment

Automated warning systems

performing

On-line analysis

Event correlation

Storm track prediction

Impact prediction

with key interfaces between

Customer service

Crew dispatch

Operations

with communication configuration requirements of

Sensor connectivity over disparate networks

Internet

Serial interface

Satellite

Publish/subscribe model

Event triggers

Warning levels

with quality of service requirements of

Reliable delivery of messages

Real time data

Propogation delays of seconds OK

with security requirements of

Data from third parties subject to licensing restrictions so data must be secured to prevent unauthorized use

Anti-spoofing

with data management requirements of

Large databases of data may need to be maintained with fast retrieval

Large number of entities - similar to classic SCADA

with constraints of

Many legacy systems in place using proprietery protocols and data formats

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	1.0	1.0	1.0	1.2

COMMENTS:
The following comments were collected during the team rating review:

Qos=2 because of need for timely warning information which may be used for notifying exposed personnel that may be exposed to danger - life safety

Mainly an issue for lightning notification which requires quick action by personnel working outside in an affected area

The following comments were collected during the peer review:

Erich to review - lowered security and data mgmt to 1 - OK - EWG

C-7.1.1 Notification of emergency transient conditions

The Purpose of Notification of emergency transient conditions function
is similar to function (C-7.1) Lightening and severe weather alert notification above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	1.0	1.0	1.0	1.2

COMMENTS:

C-7.2 Weather to consumer

The Purpose of Weather to consumer function
is to provide access to real-time and historical weather data
directly involving

National weather service

Third party providers

Automated weather stations

Customer equipment

Automated warning systems

performing

On-line analysis

Event correlation

Storm track prediction

Impact prediction

with key interfaces between

Customer service

Crew dispatch

Operations

with communication configuration requirements of

Sensor connectivity over disparate networks

Internet

Serial interface

Satellite

Publish/subscribe model

Event triggers

Warning levels

with quality of service requirements of

Reliable delivery of messages

Real time data

Propogation delays of seconds OK

with security requirements of

Data from third parties subject to licensing restrictions so data must be secured to prevent unauthorized use

Anti-spoofing

with data management requirements of

Large databases of data may need to be maintained with fast retrieval

Large number of entities - similar to classic SCADA

with constraints of

Many legacy systems in place using proprietery protocols and data formats

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.0	1.0	0.0	1.0	0.6

COMMENTS:
The following comments were collected during the peer review:

EMS can use this input to make decistion, as to how to optimize decisions for the day such, as pre-heating and pre-cooling

I'm amazed at the low ratings here, given all the items in the discussion above. This gets amplified when tying an aggregate of customers to a system or market condition. What am I missing?

-- William Smith - 29 Jun 2003

C-7.2.1 Provide day or multiday ahead weather forecasts, alerts

The Purpose of Provide day or multiday ahead weather forecasts, alerts function
is similar to function (C-7.2) Weather to consumer above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.0	1.0	0.0	1.0	0.6

COMMENTS:

C-7.2.2 Provide dynamic/periodic wind/solar/thermal/precipitation status for optimal control

The Purpose of Provide dynamic/periodic wind/solar/thermal/precipitation status for optimal control function
is similar to function (C-7.2) Weather to consumer above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.0	1.0	0.0	1.0	0.6

COMMENTS:

Same comment as for 7.2

-- William Smith - 29 Jun 2003

C-7.3 Weather from consumer

The Purpose of Weather from consumer function
is to gather weather information from customer owned sensors
directly involving

National weather service

Third party providers

Automated weather stations

Customer equipment

Automated warning systems

performing

On-line analysis

Event correlation

Storm track prediction

Impact prediction

with key interfaces between

Customer service

Crew dispatch

Operations

with communication configuration requirements of

Sensor connectivity over disparate networks

Internet

Serial interface

Satellite

Publish/subscribe model

Event triggers

Warning levels

with quality of service requirements of

Reliable delivery of messages

Real time data

Propogation delays of seconds OK

with security requirements of

Data from third parties subject to licensing restrictions so data must be secured to prevent unauthorized use

Anti-spoofing

with data management requirements of

Large databases of data may need to be maintained with fast retrieval

Large number of entities - similar to classic SCADA

with constraints of

Many legacy systems in place using proprietery protocols and data formats

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.0	1.0	2.0	2.0	1.2

COMMENTS:
The following comments were collected during the team rating review:

Data Mgmt=2 data from large volume of users

Constraints=2 analysis of micro-climate information does not exist today

The following comments were collected during the peer review:

Micro-climate analysis - information could be used to predict load from windmills and solar

Agree with the comments above, but am surprised at the low Configuration and Quality of Service ratings.

-- William Smith - 29 Jun 2003

C-7.3.1 Retrieve microclimate data from consumer controls -- outside air, solar, precipitation

The Purpose of Retrieve microclimate data from consumer controls -- outside air, solar, precipitation function
is similar to function (C-7.3) Weather from consumer above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	0.0	1.0	2.0	2.0	1.2

COMMENTS:

C-8 Third party services

The Purpose of Third party services function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	2.0	2.0	2.0	1.6

COMMENTS:

C-8.1 Contractor use of utility gateway and communications

The Purpose of Contractor use of utility gateway and communications function
is to provide managed access to customer premise network for third party contracting organizations
directly involving

Service provider

Contractor

Customer

Customer facility

Tenant

performing

Gateway between gui applications at contractor site and customer sited equipment

Persistant logging and retrieval of notification events

with key interfaces between

Service provider

Contractor

Customer

Customer facility

Tenant

with communication configuration requirements of

Sensor configuration information

Setpoints for alarms / alerts

Subsystem content models

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable remote user interface (less than 1 sec?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

Role based access control to isolate independent contractors from each others authorized accesses

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	2.0	2.0	2.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Security=2 privacy issues

Data Mgmt=2 large quantity of data

Constraints=2 hugh interoperability problem due to the large diversity of products and interfaces

C-8.1.1 Remote servicing of HVAC control

The Purpose of Remote servicing of HVAC control function
is similar to function (C-8.1) Contractor use of utility gateway and communications above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	2.0	2.0	2.0	1.6

COMMENTS:

C-9 Power Quality

The Purpose of Power Quality function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.8	2.0	2.2	2.0	1.0	1.8

COMMENTS:

C-9.1 Notify customer of current PQ information

The Purpose of Notify customer of current PQ information function
is to notify customer of supply system power quality conditions in real time and provide information for coordination with facility equipment
directly involving

Distribution operations

Customers

Marketing

performing

Power quality performance monitoring and reporting in real time

with key interfaces between

Distribution operations and customer facility managers; distribution power quality reporting system and customer system equipment

with communication configuration requirements of

Distribution system power quality monitoring system and interfaces to customer systems

with quality of service requirements of

Accurate

Fast reporting of power quality conditions cor coordination with customer systems

with security requirements of

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Large pq monitoring database describing both historical and real time system conditions

Database of customer system characteristics for coordination

with constraints of

Ability of customer to use the power quality information effectively

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	3.0	2.0	2.0	1.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because power quality monitors have a lot of settings that need to be input and maintained and numberous communication protocols and user interfaces are

QoS=3 because decisions are made by many entities based on the information and it's timliness and the potential of some applications requiring high-accuracy time

The information is needed within minutes of capture and it is large (megabyte).

Security= 2 because of spoofing concern and concern for information getting into competitor hands regarding quality of

Data Management=2 because of large database requirements

The following comments were collected during the peer review:

Lot's of legacy protocols and user interfaces

C-9.1.1 Current harmonic content

The Purpose of Current harmonic content function
is similar to function (C-9.1) Notify customer of current PQ information above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	3.0	2.0	2.0	1.0	2.0

COMMENTS:

C-9.1.2 PQ events

The Purpose of PQ events function
is similar to function (C-9.1) Notify customer of current PQ information above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	3.0	2.0	2.0	1.0	2.0

COMMENTS:

C-9.2 Implement power quality contracts

The Purpose of Implement power quality contracts function
is to

Improve customer process performance and productivity through coordination with and knowledge of the power supply conditions

Coordinate with DA systems to achieve maximum power quality levels possible within system constraintsprovide reporting

Evaluation

And billing functions for power quality and custom power contracts

directly involving

Marketing

Customers

performing

Coordination functions to help optimize the performance of customer equipment and facilities based on the power supply system conditions

Including notification of power quality conditions, that can be a concern to equipment operation

Coordination with equipment controls to improve performance

And automatic identification of system changes and equipment modifications, that can improve performance

Reporting and billing functions for PQ contracts

with key interfaces between

Marketing and customers

with communication configuration requirements of

Report formats for PQ contracts

with quality of service requirements of

Accurate reports based on contract conditions

with security requirements of

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Pq database information for generation of appropriate reports

with constraints of

Contract terms and conditions

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	3.0	2.0	1.0	1.8

COMMENTS:
The following comments were collected during the team rating review:

QoS=2 because some contracts require immediate notification of

Security-3 because contracts and serious money are

Data Mgmt=2 because of large databases for PQ data, the need for frequent backups, and off-ste storage

C-9.3 Coordinate with power conditioning equipment and process equipment to improve performance

The Purpose of Coordinate with power conditioning equipment and process equipment to improve performance function
is to coordinate the operation of power conditioning equipment and critical loads with actual system power quality conditions
directly involving

Distribution operations

Customers

Marketing

performing

Direct coordination with customer equipment to facilitate optimum response to actual power quality conditions

with key interfaces between

System pq reporting system

Customer power conditioning and critical equipment

with communication configuration requirements of

Control functions available in customer equipment in response to power quality conditions

with quality of service requirements of

Reliable communication between the distribution pq system and actual customer equipment controls

with security requirements of

Security management protocols

with data management requirements of

System power quality data for coordination with equipment; equipment databases to know equipment response alternatives

with constraints of

Ability of equipment to respond to real-time PQ conditions

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because power quality monitors have a lot of settings that need to be input and maintained and numberous communication protocols and user interfaces are

QoS=2 because decisions are made by many entities based on the information and it's

The information is needed within minutes of capture and it is large (megabyte).

Security= 2 because of spoofing concern and concern for information getting into competitor hands regarding quality of

Data Management=2 because of large database requirements

C-9.3.1 power factor correction and harmonic filters

The Purpose of power factor correction and harmonic filters function
is similar to function (C-9.3) Coordinate with power conditioning equipment and process equipment to improve performance above.
performing

Background harmonic distortion, system voltage profiles, and billing systems can influence the optimum configuration and switching of power factor correction

Automatic overload detection and switching to avoid resonance problems

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:

C-9.3.2 UPS and power conditioning equipment

The Purpose of UPS and power conditioning equipment function
is similar to function (C-9.3) Coordinate with power conditioning equipment and process equipment to improve performance above.
performing

Status of the supply system can influence optimum operation of power conditioning

Coordination during switching operations can prevent equipment outages

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:

C-9.3.3 Process equipment and machine controls

The Purpose of Process equipment and machine controls function
is similar to function (C-9.3) Coordinate with power conditioning equipment and process equipment to improve performance above.
performing

Monitoring of equipment response to disturbances can lead to real time adjustments and power conditioning

Response to capacitor switching transients, voltage sags, momentary interruptions, harmonic distortion levels can all be critical

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:

C-9.4 Improve power quality through data acquistion and supervisory control

The Purpose of Improve power quality through data acquistion and supervisory control function
is to

coordinate with customer systems to improve power quality being supplied in real time (

capacitor switching to reduce harmonics, system reconfiguration to improve voltage control

)

directly involving

Distribution operations

Industrial control and automation systems

Capacitor bank controllers

Tap changer controllers

performing

System control functions to improve power quality

with key interfaces between

Power quality reporting system and distribution automation system

with communication configuration requirements of

Parameters of power quality, that require improvement and alternatives available in the system control to improve PQ

Access to on-line impact assessment calculation engine

with quality of service requirements of

Reliable reporting of PQ conditions

Equipment configuration status

And interface to DA system for implementation of PQ improvement actions

with security requirements of

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Large database of real time power quality information

System configuration information

Alternatives for improving power quality

Logging system

Priority system

Models of power system for on-line simulation and assessment of configuration changes

with constraints of

System configuration alternatives for improving power quality

Availability of controls for changing the system configuration

Priorities for the power quality levels

Legacy PQ equipment with a myriad of protocols and file formats

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because power quality monitors have a lot of settings that need to be input and maintained and numberous communication protocols and user interfaces are

QoS=2 because decisions are made by many entities based on the information and it's

The information is needed within minutes of capture (sometimes seconds) and it is large (megabyte).

Security= 2 because of spoofing concern and concern for information getting into competitor hands regarding quality of

Data Management=2 because of large database requirements

C-9.5 Prioritize system improvements based on reliability and PQ levels being supplied to customers

The Purpose of Prioritize system improvements based on reliability and PQ levels being supplied to customers function
is to prioritize future maintenance and capital improvements based on power quality and reliability levels
directly involving

Distribution planning

performing

Prioritizing of system improvements

with key interfaces between

Power quality reporting system and distribution system design options

with communication configuration requirements of

Report specification and delivery

with quality of service requirements of

Reliable availability of reports (web-based) per specifications

with security requirements of

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Historical pq database management for assessment of pq performance and potential improvement through system improvements

Impacts of pq levels of customer operation for the prioritizing process

Report formats for prioritizing

with constraints of

System alternatives for improving performance

Needs of customers for pq improvement

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Config=2 because power quality monitors have a lot of settings that need to be input and maintained and numberous communication protocols and user interfaces are

Security= 2 because of spoofing concern and concern for information getting into competitor hands regarding quality of

Data Management=2 because of large database requirements

C-10 Electric Vehicle / home co-gen

The Purpose of Electric Vehicle / home co-gen function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.5	1.0	2.5	1.5	1.0	1.5

COMMENTS:

C-10.1 Billing a "consumption event" when consumer charges up at another customers "pump" (charging station)

The Purpose of Billing a "consumption event" when consumer charges up at another customers "pump" (charging station) function
is to

Provide a means for a consumer

Eg owner of electric vehicle

To be billed for a "fill up" regardless of where in the electric grid he "plugs in" for power

directly involving

Service provider

EStation

Customer

performing

Enable consumer access from eStation based on some authentication method

Measure the consumption event during filling

Provide billing event associated with consumption event

Provide receipt mechanism for those fillups, that occur in a non-retail location

with key interfaces between

Service provider

EStation

Customer

with communication configuration requirements of

Customer account

eStation account

Customer authentication means

with quality of service requirements of

Reliable delivery of messages

Propagation delays of several seconds is tolerable

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

Non-repudiation of customer intiated actions

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

with constraints of

need to be able to support both retail establishments, as well as, consumers "home" outlets as viable eStations for this

Retail establishments can have obligations for fancy user interfaces and receipt printing, customer premise can not

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	2.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

Security=3 multi-home access

Data Mgmt=2 many nodes

C-10.1.1 When consumer charges up at another customers "pump" (charging station)

The Purpose of When consumer charges up at another customers "pump" (charging station) function
is similar to function (C-10.1) Billing a "consumption event" when consumer charges up at another customers "pump" (charging station) above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	2.0	1.0	1.6

COMMENTS:

C-10.2 EV as generator: permit EV generator to emit power into power grid

The Purpose of EV as generator: permit EV generator to emit power into power grid function
is to

support the occasional use of an EV as an emergency generator or power

Fuel cells could be a source of energy

It also could help to reduce peak power (an in this way reduce the energy/power bills)

directly involving

Service provider

EStation

Customer

performing

Ability to tolerate the attachment to an eStation at any location and source power into it

The ability to account for net power flowing back from this source into the power grid

with key interfaces between

Service provider

EStation

Customer

with communication configuration requirements of

Customer account

eStation account

Customer authentication means

with quality of service requirements of

Reliable delivery of messages

Propagation delays of several seconds is tolerable

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

Non-repudiation of customer intiated actions

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

with constraints of

need to be able to support both retail establishments, as well as, consumers "home" outlets as viable eStations for this

Retail establishments can have obligations for fancy user interfaces and receipt printing, customer premise can not

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	2.0	1.0	1.6

COMMENTS:
This function has similar interfaces (and ratings) to function (C-10.1) Billing a "consumption event" when consumer charges up at another customers "pump" (charging station) above.

C-10.2.1 Permit EV generator to emit power into power grid

The Purpose of Permit EV generator to emit power into power grid function
is similar to function (C-10.2) EV as generator: permit EV generator to emit power into power grid above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	2.0	1.0	1.6

COMMENTS:

C-11 Energy efficiency monitoring

The Purpose of Energy efficiency monitoring function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Config=2 large base

Security=2 privacy issues

C-11.1 Appliance performance monitoring

The Purpose of Appliance performance monitoring function
is to provide advanced analysis to customer sited sensor data to achieve proactive maintenance and performance analysis
directly involving

Service provider

Customer

Customer facility

Tenant

performing

Data acquisition

Appliance signature analysis (non-intrusive appliance load monitoring) simulated operation modeling

Predictive maintenance algorithmic analysis

Historical trend logging and event recording

with key interfaces between

Service provider

Customer

Customer facility

Tenant

with communication configuration requirements of

Sensor configuration information

Setpoints for alarms / alerts

Algorithm selection

with quality of service requirements of

Reliable delivery of messages

Minimal demands on performance

with security requirements of

Privacy

Confidentiality

Authentication

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

with constraints of

Potentially large computation requirements for continuous analysis of customer sited data

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:

C-11.1.1 Monitor and compute energy efficiency for applicances and subsystems

The Purpose of Monitor and compute energy efficiency for applicances and subsystems function
is similar to function (C-11.1) Appliance performance monitoring above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:

C-11.2 Fault detection and diagnostics

The Purpose of Fault detection and diagnostics function
is to

Not unique use case

Part of above

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:

C-11.2.1 Detect specific appliance signature and analyze for drift or fault

The Purpose of Detect specific appliance signature and analyze for drift or fault function
is similar to function (C-11.2) Fault detection and diagnostics above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	1.0	2.0	1.0	1.0	1.4

COMMENTS:

C-12 Indoor Air Quality

The Purpose of Indoor Air Quality function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:

C-12.1 Monitoring of sensors

The Purpose of Monitoring of sensors function
is to support performance requirements for indoor air quality and facilitate conflict resolution in disputes related to air quality in buildings
directly involving

Service provider

Customer

Customer facility

Tenant

performing

Monitoring of sensors

Sending signals for local environmental conditions (outside air quality)

Journalling of IAQ measurements

with key interfaces between

Service provider

Customer

Customer facility

Tenant

with communication configuration requirements of

Sensor configuration information

Setpoints for alarms / alerts

with quality of service requirements of

Reliable delivery of messages

Minimal demands on performance

with security requirements of

Privacy

Confidentiality

Non-repudiation

Authentication

with data management requirements of

Persistant and reliable storage and retrieval of records

Potentially large number of records / customer sites

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:
The following comments were collected during the team rating review:

Security=3 possibility of use of data in litigation

C-12.1.1 regulatory support / documentation of compliance

The Purpose of regulatory support / documentation of compliance function
is similar to function (C-12.1) Monitoring of sensors above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:

C-12.1.2 remote monitoring and alarming of measurements

The Purpose of remote monitoring and alarming of measurements function
is similar to function (C-12.1) Monitoring of sensors above.

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	3.0	1.0	1.0	1.4

COMMENTS:

C-13 ISP services to customer

The Purpose of ISP services to customer function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	2.0	2.0

COMMENTS:

C-13.1 Reselling of bandwidth to conventional communication service providers (including telephone, TV, and ISP)

The Purpose of Reselling of bandwidth to conventional communication service providers (including telephone, TV, and ISP) function
is to sell excess communications capacity/dark fiber of DisCo to third parties
directly involving

ESP

DisCo

Customer

Telephone company

ISP's

Other third parties

performing

Ancillary communications and data services directy to customers through previously established communications media

with key interfaces between

ESP

DisCo

Customer

Telephone company

ISP's

Other third parties

with communication configuration requirements of

Many and varied - internet

Telephony

Complex addresing issues

with quality of service requirements of

Wide range of requirements depending on particular ancillary services provided

with security requirements of

Wide range of requirements depending on particular ancillary services provided

with data management requirements of

Wide range of requirements depending on particular ancillary services provided

with constraints of

Wide range of requirements depending on particular ancillary services provided

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	2.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

All items 2 or 3 because specific use of bandwidth is by definition unknown

C-14 Third party Service Support

The Purpose of Third party Service Support function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.4	2.2	2.6	1.2	1.0	1.7

COMMENTS:

C-14.1 Homes security services - owner managed

The Purpose of Homes security services - owner managed function
is to provide secure access to customer site through managed network
directly involving

Service provider

Customer

Service providers gateway

Installation/service personnel

performing

Data verification and validation

Gateway services between data access protocols and "web browser"

Management of security relationship with customer site

with key interfaces between

Service provider

Customer

Service providers gateway

with communication configuration requirements of

Customer premise layout and sensor network

Supervisory control over security system

Reporting options

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable remote user interface (less than 1 sec?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	3.0	1.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

QoS=2 timely delivery of alarms

Security=3 remote control through the utility network

C-14.2 Home health (patient monitoring / health emergency alarm)

The Purpose of Home health (patient monitoring / health emergency alarm) function
is to provide reliable monitoring services for home health care emergencies
directly involving

Service provider

Customer

Service providers gateway

Physician

Emergency personnel

Installer/service personnel

performing

Data verification and validation

Gateway services between data access protocols and "web browser"

Management of security relationship with customer site

Dispatching of emergency personnel

with key interfaces between

Gateway

Service provider

Installer/service

Personnel

Customer

Customers information distribution list

with communication configuration requirements of

Customer information

Sensor list

Reporting options

Performance requirements

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable minimal impact ot injured persons (seconds?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

High availability of service due to life or death nature of message contents

Transaction processing needs confirmed acknowledgement of delivery to key parties

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	3.0	3.0	1.0	1.0	2.0

COMMENTS:
The following comments were collected during the team rating review:

Config=2 more parameter involved; may include health record access

QoS=3 health care issues

Security=3 sensitive information

C-14.3 Alarm qualification

The Purpose of Alarm qualification function
is to provide false alarm filtering and data validation of customer alarm system
directly involving

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Installation/service

performing

Data verification and validation

Gateway services between data access protocols and notification recipients

Management of security relationship with customer site

with key interfaces between

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Installation/service

with communication configuration requirements of

Customer premise layout and sensor network

Reporting options

Sensor confirmation tree

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable notification delay (~20 sec?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	3.0	1.0	1.0	1.6

COMMENTS:
The following comments were collected during the team rating review:

QoS=2 timely delivery of alarms

Security=3 remote control through the utility network

C-14.4 Remote video surveillance -- monitoring of home "web cams"

The Purpose of Remote video surveillance -- monitoring of home "web cams" function
is to provide video gateway services for customer sited web cams
directly involving

Service provider

Customer

Service providers gateway

Customer camera

Installation/service

performing

Access control of video stream

Optional encryption of images

Storage and retrieval of recordings

with key interfaces between

Service provider

Customer

Service providers gateway

Customer camera(s)

Installation/service

with communication configuration requirements of

Customer premise layout and camera locations

Reporting options

Storage options

with quality of service requirements of

Video buffering to provide customer contiguous viewing

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

Potentially huge data sets

with constraints of

Possible law enforcement / privacy issues

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	2.0	1.0	1.8

COMMENTS:
The following comments were collected during the team rating review:

Config=2 high bandwidth

QoS=2 alarm system

Security=2 privacy

Data Mgmt=2 high volume of video data

C-14.5 home alarms -e.g. -water in basement

The Purpose of home alarms -e.g. -water in basement function
is to provide for the annunciation and routing of alarm messages
directly involving

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Installation/service

performing

Annunciation of emergency conditions

Validation and verification of alarm data and sensor quality

Dispatch of emergency personnel

with key interfaces between

Service provider

Customer

Service providers gateway

Customer security system

Police

Fire

Emergency personnel

Plumber

Electrician

Cable guy

Installation/service

with communication configuration requirements of

Customer premise layout and sensor network

Reporting options

Sensor confirmation tree

with quality of service requirements of

Reliable delivery of messages

Propagation delays of acceptable notification delay (~20 sec?)

with security requirements of

Privacy

Confidentiality

Authentication of user

Security management protocols

with data management requirements of

Persistant and reliable storage and retrieval of archival records

Large number of entities

with constraints of

Communications to the customer site may include media costrained lines

High cost per kilobyte of data (dollars per KB)

Impacted by sheer number of customers

May be third party relationships with installing/service companies

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	2.0	2.0	1.0	1.0	1.4

COMMENTS:
This function has similar interfaces (and ratings) to function (C-14.1) Homes security services - owner managed above.

C-15 Transmission and Distribution Operations Support

The Purpose of Transmission and Distribution Operations Support function
is described below...

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.5	1.8	2.4	1.8	1.8	2.0

COMMENTS:

C-15.1 Detecting light outages in street lights

The Purpose of Detecting light outages in street lights function
is to Detect street light outages
directly involving

Street lights

ESP

DisCo

performing

Street light asset management

with key interfaces between

Street lights

ESP

DisCo

with communication configuration requirements of

Low cost

Low bandwidth

High point count

Power line carrier

with quality of service requirements of

Eventual delivery of messages with no significant time contrain

with security requirements of

Little or none

with data management requirements of

Database to track assets

Low volume data but lots of points

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
1.0	1.0	1.0	1.0	0.0	0.8

COMMENTS:

C-15.2 Downed Conductor / Power Outage region detection

The Purpose of Downed Conductor / Power Outage region detection function
is to Narrow down location of broken/misoperating power system infrastructure
directly involving

MDMAs

Customers

Meters

Historical Records

ESP-SCADA/EMS

performing

Identify meters without power or non-responsive to infer affected equipment location

with key interfaces between

ESP SCADA/EMS and Settlement System

ESP SCADA/EMS and Historical Records

with communication configuration requirements of

One to one between ESP SCADA/EMS and Settlement System over WAN

One to one between ESP SCADA/EMS and Historical Records System

*One in case on one MDMA

Many in case of many MDMAs

with quality of service requirements of

High availability

Data accuracy medium

High data frequency

with security requirements of

Medium security level

with data management requirements of

Large metering database with frequent updates

with constraints of

No special constrains

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
2.0	2.0	2.0	1.0	0.0	1.4

COMMENTS:
This function has similar interfaces (and ratings) to function (C-1.10) Outage detection above.

The following comments were collected during the team rating review:

Config=2 coordination with dist sys protection

QoS=2 performance

Security=2 reaches into home

C-16 Calculation of home R factor

The Purpose of Calculation of home R factor function
is to Dynamically calculate the heating "R" factor of a home
directly involving

Home energy controller

Interior temperature sensors

External temperature sensors

Solar sensors

And wind sensors

performing

Calculation of a homes heat loss given the input values from the sensors

with key interfaces between

All sensors and the home energy controller and the home energy controller and third party service providers

with communication configuration requirements of

Many to one

On a scale of 0 (does not involve significant architectural challenges) to 3 (highly likely to involve architectural challenges) this function was rated as follows:

Configuration	Quality of Service	Security	Data Management	Constraints	Average
0.0	0.0	1.0	1.0	0.0	0.4

COMMENTS: