Office Soon | free documents download

AMI Use Case:

Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 1 of 30© Copyright 2006, Southern California Edison, All Rights ReservedAMI Use Case: B2 - Utility remotely limits usage and/or connects and disconnects customer February 1, 2006 Author: James McGrath Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 2 of 30© Copyright 2006, Southern California Edison, All Rights ReservedDocument History Revision History Date of this revision: 01-26-06Revision
NumberRevision
DateRevision /
Reviewed
BySummary of ChangesChanges
marked1.0060201JGoacherInserted use case information into templateN1.1060201BLambirdMinor edits to format and contentN1.2060324SGarciaMerge workshop output with Use Case DocY1.3060324SGarciaUse Case updated with workshop output, changes acceptedNApprovals This document requires following approvals.NameTitleJames McGrathMega-Team LeadSyd NagoshiUse Case Team LeadKevin WoodSystem Architecture Team ChairErich GuntherEngineering Team Chair Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 3 of 30© Copyright 2006, Southern California Edison, All Rights ReservedContents 1. Use Case Description............................................................................................. 5 1.1 Use Case Title ................................................................................................................................ 5 1.2 Use Case Summary........................................................................................................................ 5 1.3 Use Case Detailed Narrative .......................................................................................................... 5 1.4 Business Rules and Assumptions .................................................................................................. 6 2. Actors ..................................................................................................................... 7 3. Step by Step analysis of each Scenario ................................................................. 8 3.1 Primary Scenario 1 – Routine Shut Off (Move Out) ....................................................................... 8 3.1.1 Steps for this scenario............................................................................................................. 8 3.2 Primary Scenario 2 – Routine Turn On (Move In) ........................................................................ 10 3.2.1 Steps for this scenario........................................................................................................... 10 3.3 Primary Scenario 3 – Credit and Collection Termination ............................................................. 11 3.3.1 Steps for this scenario........................................................................................................... 11 3.4 Primary Scenario 4 – Credit and Collection Re-Connect ............................................................. 12 3.4.1 Steps for this scenario........................................................................................................... 12 3.5 Alternate Scenario 1 – Local On Site Turn On/Off ....................................................................... 13 3.5.1 Steps for this scenario........................................................................................................... 13 3.6 Alternate Scenario 3 – Credit and Collection Service Limiting ..................................................... 14 3.6.1 Steps for this scenario........................................................................................................... 15 4. Requirements ....................................................................................................... 16 4.1 Functional Requirements.............................................................................................................. 16 4.2 Non-functional Requirements ....................................................................................................... 19 4.3 Business Requirements................................................................................................................ 20 5. Use Case Models (optional) ................................................................................. 21 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 4 of 30© Copyright 2006, Southern California Edison, All Rights Reserved5.1 Information Exchange................................................................................................................... 21 5.2 Diagrams ...................................................................................................................................... 26 6. Use Case Issues .................................................................................................. 27 7. Glossary ............................................................................................................... 28 8. References ........................................................................................................... 29 9. Bibliography (optional).......................................................................................... 30 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 5 of 30© Copyright 2006, Southern California Edison, All Rights Reserved1. Use Case Description 1.1 Use Case Title Utility remotely limits usage and/or connects and disconnects customer.1.2 Use Case Summary The AMI system can be used to control the connectivity of individual customers. This function can be accomplished by controlling a “switch”
between the customer load and the distribution supply system. The utility can base connect/disconnect decisions on a variety of criteria. Examples
include:•Routine move-in/move-out.•Disconnect upon lack of customer payment or via confirmed customer request•Reconnect upon resumption of payment•Disconnect upon load greater than customer allowanceRelated to this scenario is the possibility of the meter autonomously making the disconnect decision based upon criteria such as a load threshold.This scenario excludes the mechanism used by the utility to trigger the connect/disconnect command or mechanism which control the
determination of load set-points.1.3 Use Case Detailed Narrative For most service activation/termination situations the utility has the option of sending a field technician to physically connect/disconnect the service
or to perform what has become known as “soft” turn-on/shut-off. The scheduling of field resources to visit the customer sites is complex and
costly, and occasionally the activity cannot be carried out at the time that the customer wanted. Termination of service in support of credit and
collections activities requires a “physical” interruption of services until appropriate financial arrangements are made to demonstrate that the
customer will honor their obligations. Credit and collection service termination orders inherently carry with them the possibility of physical risk to
the field technicians. The efficiencies provided by remote connect/disconnect include less man hours on site, shorter customer phone call activity, Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 6 of 30© Copyright 2006, Southern California Edison, All Rights Reservedfaster switchover of customers, less opportunities for physical abuse of field reps by non paying customers, and overall improved customer
service.In addition, with the present metering systems deployed for residential and small/medium commercial customers there is no ability to limit load in
response to constrained supply, credit issues, or where the customer desires to set a “maximum” load limit for a site.Utilities are looking to AMI metering to provide capabilities to improve the efficiency of the service initiation/termination processes through remote
turn on/off functions, and to provide a capability to remotely limit usage/load, particularly as a mitigating response to constrained supply and credit
& collections issues. Some of the business transactions that will be investigated in this use case include:•Routine shut-off of service (move out)•Routine turn-on of service (move in)•Credit & Collections termination of service•Credit & Collections reinstatement of service•Local/on site shut-off of service•Local/on site turn-on of service•Credit and Collection Service Limiting1.4 Business Rules and Assumptions Assumptions:• AMI meter is installed.•Meter is self-contained - not instrument rated. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 7 of 30© Copyright 2006, Southern California Edison, All Rights Reserved2. Actors Actor Name Actor Type (person,
device, system etc.) Actor Description AMI MeterDeviceDevice that receives, records, displays and transmits data (e.g. usage,
generation, text messages, event logs, etc.) to authorized systems (e.g.
ADCS) and provides other advanced utility functions.Customer RepresentativePersonCustomer Representatives respond to customer requests to activate, modify
and/or terminate delivery of service. Other credit and collection customer
representatives are responsible for termination of service when customer has
failed to pay their bill in a timely manner.CustomerPersonResidential or small business customers that receive electrical service from
SCE.AMI Back Office SystemSystemThe AMI system is made up of various back office systems that are required
to enable remote two-way communications and control with meters and allow
for data storage and retrieval.Field Service TechnicianPersonManual operations of field devices, repair and construction work. Work on
power system equipment in the field, as instructed by work orders and as
authorized by the distribution operator or other utility personnel Dispatched
by System Operator to fix a fault. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 8 of 30© Copyright 2006, Southern California Edison, All Rights Reserved3. Step by Step analysis of each Scenario 3.1 Primary Scenario 1 - Customer requests routine electric service shut off (Move Out) This scenario describes a voluntary disconnection of service which might lead to the generation of a final energy bill for the service point.Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)Customer requests service
order for shut off.CustomerService is disconnected. Utility
has gathered enough
information to generate a final
energy bill for the customer.3.1.1 Steps for this scenario Step # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column..1CustomerCustomer requests service order with a specific date
and time Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 9 of 30© Copyright 2006, Southern California Edison, All Rights ReservedStep # Actor Description of the Step Additional Notes 2Customer
RepresentativeCustomer Representative enters the date and time in
AMI Back Office system.Representative has the ability to
connect real time, 5-15 minute
desirement, 30-60 minute at
minimum. CCA/ESP notification
required at this step, although this
may not be performed by the AMI
Back Office System; currently
email is the source of the
notification.2.1AMI SystemAMI System sends message to in-Home devices
indicating scheduled turn off, if they exist.3AMI SystemAMI System sends disconnect event to the meter at
the scheduled time, and can be canceled or
updated/rescheduled4AMI MeterMeter provides interval data and read to AMI system5AMI MeterMeter disconnects electric service5.1AMI MeterMeter does not disconnect, data is provided to the AMI
System(Trouble report is created, discussed in Use
Case I2)5.2AMI MeterMeter does not disconnect and data is not provided6AMI MeterMeter sends disconnect acknowledgment, validating
disconnect completed, real time6.1AMI MeterMeter disconnects electric service and does not send
acknowledgement (covered in Use Case I2/B1) Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 10 of 30© Copyright 2006, Southern California Edison, All Rights Reserved3.2 Primary Scenario 2 - Customer requests routine electric service turn on (Move In) This scenario describes a turn-on request sequence which provides enough information to initialize the billing information for a customer.Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)Customer request to establish
service.CustomerService is connected.3.2.1 Steps for this scenario Step # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column.1CustomerCustomer makes request to establish service2Customer
RepresentativeCall Center Representative performs turn on process3Customer
RepresentativeCall Center Representative determines the AMI
meter’s energized status4Customer
RepresentativeCall Center Representative schedules remote connect
in AMI system, and scheduled turn on can be canceled
or Updated/rescheduled5AMI Meter / AMI SystemAMI System sends Turn On/Reconnect event to the
meter at scheduled time6AMI MeterMeter provides interval data and read to AMI System Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 11 of 30© Copyright 2006, Southern California Edison, All Rights ReservedStep # Actor Description of the Step Additional Notes 7AMI MeterMeter executes turn on, if applicable8AMI MeterMeter acknowledges turn on is completed3.3 Primary Scenario 3 - Utility disconnects customer for credit or collection cause This scenario describes an involuntary disconnection sequence which is caused by the failure of the customer to pay or provide credit for electric
service.Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)Customer eligible for
disconnect, credit reasonsCustomerRegulatory requirements are
met, regular credit process
completeMeter sends disconnect
acknowledgement3.3.1 Steps for this scenario Step # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 12 of 30© Copyright 2006, Southern California Edison, All Rights ReservedStep # Actor Description of the Step Additional Notes 1CustomerRegular credit process complete; Customer is eligible
for disconnect due to credit reasons; All regulatory
requirements met2CustomerCustomer receives final notice3AMI SystemAMI System schedules disconnect event4AMI SystemAMI System sends disconnect event to the meter at
scheduled time5AMI MeterMeter provides interval data and read to AMI System6AMI MeterMeter disconnects electric service7AMI MeterMeter sends disconnect acknowledgment, validating
disconnect completed, real time3.4 Primary Scenario 4 - Utility reconnects customer following credit and collection disconnect Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)Customer requests re-connect CustomerCustomer meets re-connect
requirementsCustomer service is restored3.4.1 Steps for this scenario The scenario describes the restoration of service after an involuntary disconnection of the service. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 13 of 30© Copyright 2006, Southern California Edison, All Rights ReservedStep # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column.1CustomerCustomer requests re-connection following
disconnect/limiting for credit reasons2CustomerCustomer meets credit/collection requirements for
reconnection (possibly by remitting overdue
payments)3N/AProceed to Primary Scenario 2 – Customer requests
routine electric service turn on3.5 Primary Scenario 5 - Field Rep performs local electric service connection/disconnection Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)Field Representative is sent to
site to turn on/off electric
serviceField RepresentativeService connection status is
changed and AMI system is
notified of that change.3.5.1 Steps for this scenario This scenario describes a change to service connection status that bypasses the AMI system. The AMI system, however, is informed of the
change after-the-fact. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 14 of 30© Copyright 2006, Southern California Edison, All Rights ReservedStep # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column.1Field RepresentativeField Representative is standing at the meter2Field RepresentativeField Representative can turn on/off electric service
through the meter on siteField Representative, via
common utility practice, will also
download the meter data into
their field device for later
transmission to the AMI back
office system.3MeterMeter logs local electric service on/off occurred and
captures users identification3.6 Primary Scenario 6 - Utility limits customer’s electric service due to credit or collection causes Triggering Event Primary Actor Pre-Condition Post-Condition (Identify the name of the event that startthe scenario)(Identify the actor whose point-of-view isprimarily used to describe the steps)(Identify any pre-conditions or actor statesnecessary for the scenario to start)(Identify the post-conditions or significantresults required to consider the scenariocomplete)For credit reasons, non-
payment, the customer is
eligible for load
limiting/disconnectionCustomerCustomer has met regulatory
requirements for load
limiting/disconnection for credit
reasons Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 15 of 30© Copyright 2006, Southern California Edison, All Rights Reserved3.6.1 Steps for this scenario Step # Actor Description of the Step Additional Notes #What actor, either primary or
secondary is responsible for the
activity in this step?Describe the actions that take place in this step. The step should be
described in active, present tense.Elaborate on any additional description or
value of the step to help support the
descriptions. Short notes on architecture
challenges, etc. may also be noted in this
column.1CustomerRegular credit process is complete, customer is
eligible for disconnect/load limiting for credit reasons:
All regulatory requirements met.2CustomerCustomer receives final notice3AMI SystemPartial electric service limiting event is scheduled4AMI MeterAMI system sends limiting event to the meter at
scheduled time5AMI MeterAMI meter limits electric service and sends
acknowledgement to AMI system5.aCustomerCustomer makes payment . - Go to Scenario P4 (Utility
reconnects customer following credit and collection
disconnect) - Service is restored to 100% level5.bCustomerNo payment after period of time further limiting of
service5.b.2CustomerNo payment longer time period – Go to Scenario P3 -
Utility disconnects customer for credit or collection
cause5.b.3CustomerCustomer makes payment - Go to Scenario P4 (Utility
reconnects customer following credit and collection
disconnect) - Service is restored to 100% level Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 16 of 30© Copyright 2006, Southern California Edison, All Rights Reserved4. Requirements 4.1 Functional Requirements Functional Requirements Associated Scenario # (if applicable) Associated Step # (if applicable) Electric service turn On/Off and electric service limiting commands to the meter shall be
able to be cancelled or updated/rescheduled prior to completion.P1P2P3P63544All self contained meters (including class 320) shall be able to remotely
connect/disconnect/limit electric service to customer premise.P1P2P6575Customer representative shall be able to schedule Date and Time for electric service
turn On/Off and electric service limiting using AMI back office system(s).P1P2P6243Meter shall be able to be turn electric service on/off and limit electric service on demandP1P2P6354Meter shall send acknowledgement of a successfully completed or failed electric service
turn On/Off or electric service limiting event to MDMS and/or AMI back office system(s)P1P2P3P66875 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 17 of 30© Copyright 2006, Southern California Edison, All Rights ReservedFunctional Requirements Associated Scenario # (if applicable) Associated Step # (if applicable) AMI system shall send message to in-home/business device, if it exists, informing
customer of impending/Scheduled electric service turn off or electric service limiting
event including date and time of scheduled event.P1P2P3P62.1544The AMI back office system(s) must allow for electric service disconnects and electric
service limiting events to be prioritized, scheduled, and balanced throughout the day.
(e.g. to avoid large volumes of disconnects occurring at the same time)P1P333Meter shall externally indicate electric service connect/disconnect status so that it is
discernable to a customer or SCE employee on site.P51Authorized SCE Employee on-site shall have the ability to physically toggle electric
service connect/disconnect switch at any time. 24 hours 7 days a week, 365 days a
year.P52Meter shall log date/time and status of attempts to toggle electric service
connect/disconnect switch, including user identity and whether attempt is authorized or
unauthorized.P53Meter shall accept remotely scheduled electric service connect/disconnect/limiting event
while field rep is on site.P52The AMI system shall have the ability to have multiple electric service events
(connect/disconnect/load limiting) scheduled for a single meter.P1P2P3P63434Should a disconnect event and connect event be scheduled to occur for the same meter
on the same day, the meter shall log the events, and automatically provide an “on-
demand type” read to the MDMS without toggling the connect/disconnect switch.P1P257The meter shall have the ability to limit load/service, at multiple configurable steps (e.g.
90% of rated capacity, 75% of rated capacity, etc.)P65 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 18 of 30© Copyright 2006, Southern California Edison, All Rights ReservedFunctional Requirements Associated Scenario # (if applicable) Associated Step # (if applicable) Meter limiter shall reconnect automatically after 2 minutes (to presently configured
limiting level) if meter trips off because configured limit is exceeded.P60Meter limiter shall reconnect automatically no more than once in a 24 hour period.P60Customer shall have the ability to manually reconnect meter limiter at the meter (to
presently configured limiting level) if meter trips off because configured limit is
exceeded.P60By default, meter disconnect switch shall be in the “Closed”/connected position upon
installationP10When the disconnect switch is in the open position the meter shall remain energized
and continue to monitor and record consumption/usage in all channels at the interval for
which the meter is programmed.P1P356Meter shall provide an on-demand read to AMI Back Office system at the time of a
remote electric service turn on/off/load limiting event.P1P2P3P64655The AMI Meter shall be able to accept duplicate electric service
connect/disconnect/limiting commands with no action occurring. (Meter is on, Turn On
message acceptable with no action taken)P1P2P3000Customer Representative shall be able to have access to meter’s current switch position
(on/off/limit level) and energized status from the call center, via AMI back office systemsP23 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 19 of 30© Copyright 2006, Southern California Edison, All Rights Reserved4.2 Non-functional Requirements Non-Functional Requirements Associated Scenario # (if applicable) Associated Step # (if applicable) Electric service turn on message to meter shall be persistent until meter acknowledges
that turn on has been completed successfully.P25Electric service turn off message to the meter shall be persistent until meter
acknowledges that turn off has been completed successfully.P13On demand electric service turn on/off and Limiting commands shall be completed, and
acknowledgement received by requestor, within 1 minute of being requested by AMI
back office system(s).P1P2A3575Remote electric service Turn Off commands shall complete only at the end of a billing
interval.P1P323Meter has an authorization/authentication routine allowing only active/eligible employees
to turn electric service on/off locallyA12Authorized SCE Employee shall have the ability to locally toggle connect/disconnect
switch immediately (regardless of interval) or schedule the connect/disconnect for a
future interval.A12Electric service limiting messages/events sent to the meter shall be persistent until
meter acknowledges limiting has been completed successfully.A34 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 20 of 30© Copyright 2006, Southern California Edison, All Rights Reserved4.3 Business Requirements Business Requirement Associated Scenario # (if applicable) Associated Step # (if applicable) Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 21 of 30© Copyright 2006, Southern California Edison, All Rights Reserved5. Use Case Models (optional) This section is used by the architecture team to detail information exchange, actor interactions and sequence diagrams5.1 Information Exchange For each scenario detail the information exchanged in each stepScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged #Name of the step for this scenario. What actors are primarily
responsible for Producing the
information? What actors are primarily responsible
for Receiving the information? Describe the information being exchanged 11 Customer requests service
order with a specific date and
timeCustomerCustomer RepresentativeCustomer account
information(account #, name,
address)Electric service disconnection
date and time2 Customer Representative
enters the date and time in AMI
system.Customer RepresentativeAMI Back Office SystemCustomer account
information(account #, name,
address)Electric service disconnection
date and time2.1 AMI System sends
message to in-Home devices
indicating scheduled turn off, if
they exist.AMI SystemCustomer Premise
DevicesElectric service disconnection
date and time Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 22 of 30© Copyright 2006, Southern California Edison, All Rights ReservedScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged 3 AMI System sends disconnect
event to the meter at the
scheduled time, and can be
canceled or
updated/rescheduledAMI Back Office SystemAMI MeterElectric service disconnection
event4 Meter provides interval data
and read to AMI systemAMI MeterMDMSInterval usage data5 Meter disconnects electric
serviceAMI MeterElectric service switchDisconnect command5.1 Meter does not disconnect,
data is provided to the AMI
System(Trouble report is
created, continued in I2)AMI MeterAMI SystemDisconnection failure message5.2 Meter does not disconnect
and data is not provided6 Meter sends disconnect
acknowledgment, validating
disconnect completed, real
timeAMI MeterAMI Back Office SystemDisconnection success
message6.1 Meter disconnects electric
service and does not send
acknowledgement (covered in
Use Case I2/B1)21 Customer makes request to
establish serviceCustomerCustomer RepresentativeService connection requestCustomer account information Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 23 of 30© Copyright 2006, Southern California Edison, All Rights ReservedScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged 2 Call Center Representative
performs turn on processCustomer RepresentativeAMI Back Office SystemService connection requestCustomer account information3 Call Center Representative
determines the AMI meter’s
energized statusAMI Meter or AMI System Customer RepresentativeElectric service connection
status4 Call Center Representative
schedules remote connect in
AMI system, and scheduled
turn on can be canceled or
Updated/rescheduledCustomer RepresentativeAMI SystemElectric service connection
event5 AMI System sends Turn
On/Reconnect event to the
meter at scheduled timeAMI SystemAMI MeterElectric service connection
event6 Meter provides interval data
and read to AMI SystemAMI MeterAMI SystemInterval usage data7 Meter executes turn on, if
applicableAMI MeterElectric service switchConnect command8 Meter acknowledges turn on
is completedAMI MeterAMI SystemConnection success message31 Regular credit process
complete; Customer is eligible
for disconnect due to credit
reasons; All regulatory
requirements met Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 24 of 30© Copyright 2006, Southern California Edison, All Rights ReservedScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged 2 Customer receives final
noticeUtilityCustomerFinal notification of electric
service disconnection3 AMI System schedules
disconnect event4 AMI System sends disconnect
event to the meter at scheduled
timeAMI Back Office SystemAMI meterElectric service disconnection
event5 Meter provides interval data
and read to AMI SystemAMI MeterMDMSInterval usage data6 Meter disconnects electric
serviceAMI MeterElectric service switchDisconnect command7 Meter sends disconnect
acknowledgment, validating
disconnect completed, real
timeAMI MeterAMI Back Office SystemDisconnection success
message41 Customer requests re-
connection following
disconnect/limiting for credit
reasonsCustomerCustomer RepresentativeService connection requestCustomer account information2 Customer meets
requirements for reconnection3 Proceed to Primary Scenario
2 – Customer requests routine
electric service turn onSee scenario 2 Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 25 of 30© Copyright 2006, Southern California Edison, All Rights ReservedScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged 51 Field Representative is
standing at the meter2 Field Representative can turn
on/off electric service through
the meter on siteField RepresentativeAMI MeterElectric service
connect/disconnect command3 Meter logs local electric
service on/off occurred and
captures users identificationAMI MeterAMI System (using meter
log)Field Representative identifierDate and Time of electric
service commandType of electric service
command (connect/disconnect)61 Regular credit process is
complete, customer is eligible
for disconnect/load limiting for
credit reasons: All regulatory
requirements met.2 Customer receives final
noticeUtilityCustomerFinal notification of electric
service curtailment3 Partial electric service limiting
event is scheduled4 AMI system sends limiting
event to the meter at scheduled
timeAMI Back Office SystemAMI MeterElectric service limiting event5 AMI meter limits electric
service and sends
acknowledgement to AMI
systemAMI MeterAMI SystemLimit success message Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 26 of 30© Copyright 2006, Southern California Edison, All Rights ReservedScenario # Step #, Step Name Information Producer Information Receiver Name of information exchanged 1 Customer makes payment . -
Go to Scenario P4 (Utility
reconnects customer following
credit and collection disconnect)
- Service is restored to 100%
levelCustomerSee scenario 4UtilityService payment2 No payment after period of
time further limiting of service2.1 No payment longer time
period – Go to Scenario P3 -
Utility disconnects customer for
credit or collection causeSee scenario 32.2 Customer makes payment -
Go to Scenario P4 (Utility
reconnects customer following
credit and collection disconnect)
- Service is restored to 100%
levelCustomerSee scenario 4UtilityService payment5.2 Diagrams The architecture team shall use this section to develop an interaction diagram that graphically describes the step-by-step actor-system
interactions for all scenarios. The diagrams shall use standard UML notation. Additionally, sequence diagrams may be developed to help
describe complex event flows. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 27 of 30© Copyright 2006, Southern California Edison, All Rights Reserved6. Use Case Issues Capture any issues with the use case. Specifically, these are issues that are not resolved and help the use case reader understand the constraints
or unresolved factors that have an impact of the use case scenarios and their realization.Issue Describe the issue as well as any potential impacts to the use case. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 28 of 30© Copyright 2006, Southern California Edison, All Rights Reserved7. Glossary Insert the terms and definitions relevant to this use case. Please ensure that any glossary item added to this list should be included in the global
glossary to ensure consistency between use cases.GlossaryTermDefinitionInstrument-rated MeterA meter is considered instrument rated when there are the presence of various transformers (potential,
voltage, circuit) installed along with the meter. The electricity provided in this type of installation does not
flow through the meter as it will with a non-instrument rated (i.e. self contained) meter. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 29 of 30© Copyright 2006, Southern California Edison, All Rights Reserved8. References Reference any prior work (intellectual property of companies or individuals) used in the preparation of this use case. Advanced Metering Infrastructure (AMI) Program DRAFT B2 - Utility remotely limits usage and/or connects and disconnects customerDocument: ARCH - B2-USE CASE v1.2 050106.docSCE InternalAuthor: James McgrathPage 30 of 30© Copyright 2006, Southern California Edison, All Rights Reserved9. Bibliography (optional) Provide a list of related reading, standards, etc. that the use case reader may find helpful.

refer page:-------http://www.officesoon.com/doc/159202-ami-use-case