# Actors

Descriptor:
Recloser (Team) Server to Remote Interactions


Descriptor:
Intelligent Fault detector (with Oscillography)


# AlternativePathConnections

Requirements:
DMS shall be able to send sensor data request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send sensor data reply to DMS


Requirements:
Feeder Sensor shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 hr for each Sensor


Requirements:
CIS - Utility shall be able to send on-demand meter read request to the Smart Meter via the Head-End

Implication:
May need to estimate or manually read, 
Not system critical


Requirements:
AMI Head-End shall be able to report & send "AMI Head-End to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS


Requirements:
DAP shall be able to report & send "DAP to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS

HowOften:
1 trans per PrePay meter per x on-demand cmds per time period

Implication:
Broken cash register, 
Not system critical


Requirements:
Smart Meter (Electric or Gas, Residential or Commercial/Industrial) shall be able to send on-demand meter read data to CIS - Utility

HowOften:
1 trans per PrePay meter per on demand request


Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing - Utility and/or MDMS and/or NMS


Requirements:
IHD shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per PrePay customer with IHD

Implication:
Customer Frustration, 
Not system critical


Requirements:
Feeder VR shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder VR


Requirements:
Feeder VR shall be able to send sensor data reply to DMS


Requirements:
Feeder VR shall be able to send status change info to DMS


Requirements:
Feeder VR shall be able to send deviation alert to DMS


Requirements:
Feeder VR shall be able to send alarm condition to DMS


Requirements:
Feeder VR shall be able to send failure to operate alert to DMS


Requirements:
DMS shall be able to send status request to Feeder CBC


Requirements:
Feeder CBC shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder CBC


Requirements:
Feeder CBC shall be able to send sensor data reply to DMS


Requirements:
Feeder CBC shall be able to send status change info to DMS

HowOften:
Average 1 alert every 12 hr for each CBC


Requirements:
Feeder CBC shall be able to send deviation alert to DMS


Requirements:
Feeder CBC shall be able to send alarm condition to DMS


Requirements:
Feeder CBC shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each CBC


Requirements:
DMS shall be able to send status request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send status reply to DMS


Requirements:
Smart Meter (Gas Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas C/I meter.  May have 15min vs 1hr interval data

Reliability:
90% success every 4-6 hours, 
98% success over a day, 
> 99.5% over two days

Implication:
Need to retry, 
Potential broken cash register, 
Not system critical


Requirements:
Smart Meter (Gas Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas resdnt meter, with 4hr -24h interval data


Requirements:
Smart Meter (Electric Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
12-24 trans per day per electric C/I meter, Intervals of 15min to 1hr, 4-20 data points per interval

Reliability:
>98% success every 3 hours, 
>99.5% success over 2 days, 
> 99.5% over two days


Requirements:
Smart Meter (Electric Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
4-6 trans per day per electric resdnt meter, Intervals of 15min to 1hr, 4-8 data points per interval


Requirements:
MDMS may be able to send multiple interval meter reading request to Smart Meter


Requirements:
Smart Meter may be able to process & send/forward multiple interval meter reading data (per specific meter request from MDMS) to MDMS


HowOften:
1 trans per meter per x on-demand cmds per time period


Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing and/or MDMS and/or NMS


HowOften:
1-10 trans per day per customer with IHD


Requirements:
LMS shall be able to send charging price rates to PHEV

Implication:
May need to retry, system critical in scale, PHEV could charge at minimum rate


Requirements:
non-Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-non-SMtr per day


Requirements:
Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-SMtr per day


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from PHEV) to LMS" communication failure to PHEV & NMS


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from LMS) to PHEV" communication failure to LMS


Requirements:
LMS shall be able to negotiate Power Charging Rate with PHEV

HowOften:
150 trans per 1000 mtrs 2-4 times per day

Implication:
Customer Service issue, PHEV battery does not get re-charged.  Potential system impact in scale


Requirements:
PHEV shall be able to send negotiate Power Charging Rate messages to LMS

HowOften:
1 thread, 2-4 trans per PHEV connected meter per day


Requirements:
AMI Head-End shall be able to process & send "PHEV VIN information request to MDMS (from PHEV)" communications failure to PHEV


Requirements:
PHEV shall be able to process & send charging status of the PHEV to LMS

HowOften:
2-4 trans per PHEV charging event per day


Requirements:
PHEV shall be able to publish PHEV VIN information request to MDMS


Requirements:
CIS - Utility shall be able to send a scheduled cancel service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch state request to Smart Meter


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS, or MDMS) communications failure" with Smart Meter, to CIS/Billing - Utility and/or MDMS and NMS


ActorB:
CIS/Billing - Utility, 
MDMS, 
LMS, 
DSM

Requirements:
Smart Meter shall be able to send service switch state data to CIS - Utility, MDMS, LMS, DSM


Requirements:
Smart Meter shall be able to send service switch operate acknowledgment to CIS - Utility, MDMS


Requirements:
Smart Meter shall be able to send service switch operate faillure to CIS - Utility, MDMS

HowOften:
1 trans per 1000 SW-oper per mtr per day


Requirements:
Smart Meter shall be able to report & send metrology information after a successful service switch operate to CIS - Utility, MDMS


Requirements:
CIS - Utility shall be able to send a meter config for prepay capability request to Smart Meter

HowOften:
1 trans per prepay enrollment per premise meter

Implication:
Need to retry, 
Potential broken PrePay meter config, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay unenroll per premise meter


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to IHD

HowOften:
25 trans per PrePay mtr with IHD per month


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS


Requirements:
CIS - Utility shall be able to send a cancel of scheduled service switch operate request to Smart Meter


Requirements:
AMI Head-End shall be able to process & send "service switch operate request (from CIS - Utility) communications failure" with Smart Meter, to CIS - Utility

HowOften:
1-4 trans per 1000 PrePay mtrs-SW-oper per day


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS - Utility, or MDMS) communications failure" with Smart Meter, to AMI Head-End and/or MDMS and/or NMS


HowOften:
1 trans per 1000 SW-oper per PrePay mtrper day


Requirements:
Feeder Sensor shall be able to send deviation alert to DMS


Requirements:
Feeder Sensor shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every day for each Sensor


Requirements:
DMS shall be able to send status request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send sensor data reply to DMS


Requirements:
Feeder Recloser shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Recloser


Requirements:
Feeder Recloser shall be able to send deviation alert to DMS


Requirements:
Feeder Recloser shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Recloser


Requirements:
Feeder Recloser shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Recloser


Requirements:
DMS shall be able to send status request to Feeder Switch


Requirements:
Feeder Switch shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Switch


Requirements:
Feeder Switch shall be able to send sensor data reply to DMS


Requirements:
Feeder Switch shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Switch


Requirements:
Feeder Switch shall be able to send deviation alert to DMS


Requirements:
Feeder Switch shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Switch


Requirements:
Feeder Switch shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Switch


Requirements:
DMS shall be able to send status request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send sensor data reply to DMS


Requirements:
Feeder Fault_Detector shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 week for each Fault Detector


Requirements:
Feeder Fault_Detector shall be able to send deviation alert to DMS


Requirements:
Feeder Fault_Detector shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Fault Detector


Requirements:
DMS shall be able to send step up command to Feeder VR

HowOften:
Average 1 cmd every 2 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send step up command ACK to DMS


Requirements:
DMS shall be able to send step down command to Feeder VR


Requirements:
Feeder VR shall be able to send step down command ACK to DMS

HowOften:
Average 1 ack every 2 hr for each Feeder VR


Requirements:
DMS shall be able to send new config to Feeder VR

HowOften:
Average 1 cmd every 12 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder VR


Requirements:
DMS shall be able to send open command to Feeder CBC

HowOften:
Average 1 cmd every 12 hr for each Feeder CBC


Requirements:
Feeder CBC shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder CBC


Requirements:
Feeder CBC shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder CBC

HowOften:
Average 1 cmd every 1 week for each Feeder CBC


Requirements:
Feeder CBC shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder Sensor

HowOften:
Average 1 cmd every 1 week for each Feeder Sensor


Requirements:
Feeder Sensor shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Sensor


Requirements:
DMS shall be able to send new config to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send new config ACK to DMS


Requirements:
DMS shall be able to send open command to Feeder Switch

HowOften:
Average 1 cmd every 1 week for each Feeder Switch


Requirements:
Feeder Switch shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder Switch


Requirements:
Feeder Switch shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Switch


DailyClockPeriods:
From 1-6 hr duration, from 4-8 times a year


HowOften:
Average 1 cmd every 5 min for each Feeder VR


HowOften:
Average 1 ack every 5 min for each Feeder VR


HowOften:
Average 1 cmd every 1 hr for each Feeder VR


HowOften:
Average 1 ack every 1 hr for each Feeder VR


HowOften:
Average 1 cmd every 5 min for each Feeder CBC


HowOften:
Average 1 ack every 5 min for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder CBC


HowOften:
Average 1 ack every 1 hr for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder Sensor


HowOften:
Average 1 ack every 1 hr for each Feeder Sensor


HowOften:
Average 1 cmd every 12 hr for each Feeder Switch


HowOften:
Average 1 ack every 12 hr for each Feeder Switch


Requirements:
Smart Meter shall be able to send outage notification to OMS

HowOften:
100 percent of meters that lose power per day

Implication:
Not Critical due to broadcast nature of transmission


Requirements:
Smart Meter shall be able to send power restoration notification to OMS

HowOften:
100 percent of meters that returned to power per day


Requirements:
DAP shall be able to send a notification when DAP running on battery power to OMS

HowOften:
20 per 1000 DAP per system power outage event per day


# Application2ApplicationConnections

DataFlowRef:
[(1Ca + 4DRC) or (4Ba + 4ERU + 4E + 4ERC) or (4F + 4FRC) or 4GRC] + 4A

Requirements:
Feeder Recloser shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder CBC


DataFlowRef:
4A +
[(1Ca + 4DSW) or (4Ba + 4ERU + 4E + 4ESW) or (4F + 4FSW) or 4GSW]

Requirements:
DMS shall be able to send open command to Feeder Switch

HowOften:
Average 1 cmd every 1 week for each Feeder Switch


DataFlowRef:
[(1Ca + 4DSW) or (4Ba + 4ERU + 4E + 4ESW) or (4F + 4FSW) or 4GSW] + 4A

Requirements:
Feeder Switch shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder Switch


Requirements:
Feeder Switch shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Switch


DataFlowRef:
4A +
[(1Ca + 4DRG) or (4Ba + 4ERU + 4E + 4ERG) or (4F + 4FRG) or 4GRG]

Requirements:
DMS shall be able to send sensor data request to Feeder VR

DailyClockPeriods:
From 1-6 hr duration, from 4-8 times a year


DataFlowRef:
[(1Ca + 4DRG) or (4Ba + 4ERU + 4E + 4ERG) or (4F + 4FRG) or 4GRG] + 4A

Requirements:
Feeder VR shall be able to send sensor data reply to DMS


Requirements:
DMS shall be able to send step up command to Feeder VR

HowOften:
Average 1 cmd every 5 min for each Feeder VR


Requirements:
Feeder VR shall be able to send step up command ACK to DMS


Requirements:
DMS shall be able to send step down command to Feeder VR


Requirements:
Feeder VR shall be able to send step down command ACK to DMS

HowOften:
Average 1 ack every 5 min for each Feeder VR


Requirements:
DMS shall be able to send new config to Feeder VR

HowOften:
Average 1 cmd every 1 hr for each Feeder VR


Requirements:
CIS - Utility shall be able to send bulk meter read information requests to MDMS

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


Requirements:
MDMS shall be able to send bulk meter read information requests to Head End


Requirements:
MDMS shall be able to process & send bulk meter read information data to CIS - Utility


Requirements:
AMI Head-End shall be able to process & forward on-demand meter read data to MDMS


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]

Requirements:
Smart Meter (Gas Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas C/I meter.  May have 15min vs 1hr interval data

Reliability:
90% success every 4-6 hours, 
98% success over a day, 
> 99.5% over two days

Implication:
Need to retry, 
Potential broken cash register, 
Not system critical


Requirements:
Smart Meter (Gas Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas resdnt meter, with 4hr -24h interval data


Requirements:
Smart Meter (Electric Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
12-24 trans per day per electric C/I meter, Intervals of 15min to 1hr, 4-20 data points per interval

Reliability:
>98% success every 3 hours, 
>99.5% success over 2 days, 
> 99.5% over two days


Requirements:
Smart Meter (Electric Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
4-6 trans per day per electric resdnt meter, Intervals of 15min to 1hr, 4-8 data points per interval


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP

HowOften:
5-15 trans per 1000 REP prepay mtrs per day

Implication:
Customer Frustration, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal

HowOften:
5-15 trans per 1000 Common Web Portal prepay mtrs per day


Requirements:
Customer Browser - Mobile shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Premise

HowOften:
5-15 trans per 1000 utility prepay mtrs per day


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
CIS/Billing - Utility shall be able to process, extract, send bulk Customers subset of Account information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


DataFlowRef:
1B +
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] +
1D

Requirements:
MDMS may be able to send multiple interval meter reading request to Smart Meter


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
1B

Requirements:
Smart Meter may be able to process & send/forward multiple interval meter reading data (per specific meter request from MDMS) to MDMS

Implication:
May need to estimate or manually read, 
Not system critical


DataFlowRef:
[(1Aa + 1B) or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
1D

Requirements:
CIS - Utility shall be able to send on-demand meter read request to the Smart Meter via the Head-End


DataFlowRef:
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  +
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
DAP shall be able to report & send "DAP to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS

HowOften:
1 trans per meter per x on-demand cmds per time period

Implication:
Broken cash register, 
Not system critical


Requirements:
IHD shall be able to report & send "IHD to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from IHD to meter when re-established OR alternate dataflow to NMS and/or MDMS


Requirements:
Cust. EMS shall be able to report & send "Cust. EMS to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from Cust. EMS to meter when re-established OR alternate dataflow to NMS and/or MDMS


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing and/or MDMS and/or NMS


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to IHD via Smart Meter ESI


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS via Smart Meter ESI


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS - Utility via non-Smart Meter ESI

HowOften:
1 trans per Cust. EMS - Utility per x on-demand cmds per time period


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to IHD via non-Smart Meter ESI

HowOften:
1 trans per IHD per x on-demand cmds per time period


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
[(1B + 1Aa) or 1Ab]

Requirements:
Smart Meter (Electric or Gas, Residential or Commercial/Industrial) shall be able to send on-demand meter read data to CIS - Utility


Requirements:
Smart Meter ESI shall be able to send on-demand meter reading request to IHD via Smart Meter ESI


Requirements:
Smart Meter shall be able to send on-demand meter reading request to Cust. EMS via Smart Meter ESI

HowOften:
1 trans per Cust. EMS per on demand request


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to Cust. EMS - Utility via non Smart Meter ESI

HowOften:
1 trans per Cust. EMS - Utility per on demand request


Requirements:
IHD shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per customer with IHD


Requirements:
Customer EMS shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per customer with Cust. EMS


Requirements:
LMS shall be able to send charging price rates to PHEV

Implication:
May need to retry, system critical in scale, PHEV could charge at minimum rate


DataFlowRef:
5Bb+ 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
9

Requirements:
non-Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-non-SMtr per day


DataFlowRef:
5Ba+ 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
9

Requirements:
Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-SMtr per day


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from PHEV) to LMS" communication failure to PHEV & NMS


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from LMS) to PHEV" communication failure to LMS


Requirements:
LMS shall be able to negotiate Power Charging Rate with PHEV

HowOften:
150 trans per 1000 mtrs 2-4 times per day

Implication:
Customer Service issue, PHEV battery does not get re-charged.  Potential system impact in scale


Requirements:
PHEV shall be able to send negotiate Power Charging Rate messages to LMS

HowOften:
1 thread, 2-4 trans per PHEV connected meter per day


Requirements:
AMI Head-End shall be able to process & send "PHEV VIN information request to MDMS (from PHEV)" communications failure to PHEV


Requirements:
PHEV shall be able to process & send charging status of the PHEV to LMS

HowOften:
2-4 trans per PHEV charging event per day


Requirements:
PHEV shall be able to publish PHEV VIN information request to MDMS


DataFlowRef:
[(1Aa + 1B)  or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
1D

Requirements:
CIS - Utility shall be able to send a scheduled cancel service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch state request to Smart Meter


DataFlowRef:
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
DAP shall be able to process & send "service switch operate request (from CIS, or MDMS) communications failure" with Smart Meter, to CIS/Billing - Utility and/or MDMS and NMS


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[8 or 9 or (1B or (1B + 1Aa) or 1Ab)]

TargetActor:
CIS/Billing - Utility, 
MDMS, 
LMS, 
DSM

Requirements:
Smart Meter shall be able to send service switch state data to CIS - Utility, MDMS, LMS, DSM


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[1B or ((1B + 1Aa) or 1Ab)]

Requirements:
Smart Meter shall be able to send service switch operate acknowledgment to CIS - Utility, MDMS


Requirements:
Smart Meter shall be able to send service switch operate faillure to CIS - Utility, MDMS

HowOften:
1 trans per 1000 SW-oper per mtr per day


Requirements:
Smart Meter shall be able to report & send metrology information after a successful service switch operate to CIS - Utility, MDMS


DataFlowRef:
[(1Aa + 1B)  or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] +
1D

Requirements:
CIS - Utility shall be able to send a meter config for prepay capability request to Smart Meter

HowOften:
1 trans per prepay enrollment per premise meter

Implication:
Need to retry, 
Potential broken PrePay meter config, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay unenroll per premise meter


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to IHD

HowOften:
25 trans per PrePay mtr with IHD per month


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to IHD via [Common Web Portal - Utility or ESI - non-Smart Meter)


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS via [Common Web Portal - Utility or ESI - non-Smart Meter)

HowOften:
25 trans per PrePay mtr with Cust. EMS per month


Requirements:
CIS - Utility shall be able to send a cancel of scheduled service switch operate request to Smart Meter


Requirements:
AMI Head-End shall be able to process & send "service switch operate request (from CIS - Utility) communications failure" with Smart Meter, to CIS - Utility

HowOften:
1-4 trans per 1000 PrePay mtrs-SW-oper per day


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS - Utility, or MDMS) communications failure" with Smart Meter, to AMI Head-End and/or MDMS and/or NMS


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[8 or 9 or (1B or (1AA or 1Ab)]


HowOften:
1 trans per 1000 SW-oper per PrePay mtrper day


Requirements:
AMI Head-End shall be able to report & send "AMI Head-End to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS


HowOften:
1 trans per PrePay meter per x on-demand cmds per time period


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] + 
[(1B + 1Aa) or 1Ab]

HowOften:
1 trans per PrePay meter per on demand request


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI - Utility

HowOften:
1 trans per PrePay Customer per demand with IHD


HowOften:
1 trans per PrePay Customer per demand with Cust. EMS - Utility


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] + 
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing - Utility and/or MDMS and/or NMS


HowOften:
1 trans per PrePay customer with Cust. EMS per x on-demand cmds per time period


HowOften:
1 trans per PrePay customer with IHD per x on-demand cmds per time period


HowOften:
1-10 trans per day per PrePay customer with IHD


HowOften:
1-10 trans per day per PrePay customer with Cust. EMS


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility


Requirements:
Feeder VR shall be able to send status reply to DMS


Requirements:
Feeder VR shall be able to send status change info to DMS


Requirements:
Feeder VR shall be able to send deviation alert to DMS


Requirements:
Feeder VR shall be able to send alarm condition to DMS


Requirements:
Feeder VR shall be able to send failure to operate alert to DMS


DataFlowRef:
4A +
[(1Ca + 4DCB) or (4Ba + 4ERU + 4E + 4ECB) or (4F + 4FCB) or 4GCB]

Requirements:
DMS shall be able to send status request to Feeder CBC


DataFlowRef:
[(1Ca + 4DCB) or (4Ba + 4ERU + 4E + 4ECB) or (4F + 4FCB) or 4GCB] + 4A

Requirements:
Feeder CBC shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder CBC


Requirements:
Feeder CBC shall be able to send sensor data reply to DMS


Requirements:
Feeder CBC shall be able to send status change info to DMS

HowOften:
Average 1 alert every 12 hr for each CBC


Requirements:
Feeder CBC shall be able to send deviation alert to DMS


Requirements:
Feeder CBC shall be able to send alarm condition to DMS


Requirements:
Feeder CBC shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each CBC


DataFlowRef:
4A +
[(1Ca + 4DS) or (4Ba + 4ERU + 4E + 4ES) or (4F + 4FS) or 4GS]

Requirements:
DMS shall be able to send status request to Feeder Sensor


DataFlowRef:
[(1Ca + 4DS) or (4Ba + 4ERU + 4E + 4ES) or (4F + 4FS) or 4GS] + 4A

Requirements:
Feeder Sensor shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send sensor data reply to DMS


Requirements:
Feeder Sensor shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 hr for each Sensor


Requirements:
Feeder Sensor shall be able to send deviation alert to DMS


Requirements:
Feeder Sensor shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every day for each Sensor


DataFlowRef:
4A +
[(1Ca + 4DRC) or (4Ba + 4ERU + 4E + 4ERC) or (4F + 4FRC) or 4GRC]

Requirements:
DMS shall be able to send status request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send sensor data reply to DMS


Requirements:
Feeder Recloser shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Recloser


Requirements:
Feeder Recloser shall be able to send deviation alert to DMS


Requirements:
Feeder Recloser shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Recloser


Requirements:
Feeder Recloser shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Recloser


Requirements:
DMS shall be able to send status request to Feeder Switch


Requirements:
Feeder Switch shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Switch


Requirements:
Feeder Switch shall be able to send sensor data reply to DMS


Requirements:
Feeder Switch shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Switch


Requirements:
Feeder Switch shall be able to send deviation alert to DMS


Requirements:
Feeder Switch shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Switch


Requirements:
Feeder Switch shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Switch


Requirements:
DMS shall be able to send status request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send sensor data reply to DMS


Requirements:
Feeder Fault_Detector shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 week for each Fault Detector


Requirements:
Feeder Fault_Detector shall be able to send deviation alert to DMS


Requirements:
Feeder Fault_Detector shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Fault Detector


HowOften:
Average 1 cmd every 2 hr for each Feeder VR


HowOften:
Average 1 ack every 2 hr for each Feeder VR


HowOften:
Average 1 cmd every 12 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder VR


Requirements:
DMS shall be able to send open command to Feeder CBC

HowOften:
Average 1 cmd every 12 hr for each Feeder CBC


Requirements:
Feeder CBC shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder CBC


Requirements:
Feeder CBC shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder CBC

HowOften:
Average 1 cmd every 1 week for each Feeder CBC


Requirements:
Feeder CBC shall be able to send new config ACK to DMS


Requirements:
DMS shall be able to send new config to Feeder Sensor

HowOften:
Average 1 cmd every 1 week for each Feeder Sensor


Requirements:
Feeder Sensor shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Sensor


Requirements:
DMS shall be able to send new config to Feeder Recloser


HowOften:
Average 1 ack every 1 hr for each Feeder VR


HowOften:
Average 1 cmd every 5 min for each Feeder CBC


HowOften:
Average 1 ack every 5 min for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder CBC


HowOften:
Average 1 ack every 1 hr for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder Sensor


HowOften:
Average 1 ack every 1 hr for each Feeder Sensor


HowOften:
Average 1 cmd every 12 hr for each Feeder Switch


HowOften:
Average 1 ack every 12 hr for each Feeder Switch


Requirements:
Smart Meter shall be able to send outage notification to OMS

HowOften:
100 percent of meters that lose power per day

Implication:
Not Critical due to broadcast nature of transmission


Requirements:
Smart Meter shall be able to send power restoration notification to OMS

HowOften:
100 percent of meters that returned to power per day


Requirements:
DAP shall be able to send a notification when DAP running on battery power to OMS

HowOften:
20 per 1000 DAP per system power outage event per day


Requirements:
OMS shall be able to process, extract, send bulk Customers subset of service outage information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day


Requirements:
MDMS shall be able to process, extract, send bulk Customers subset of meter information to ODW - Utility


Requirements:
AMI Head-End shall be able to process, extract, send bulk Customers subset of meter communication information to ODW - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
CIS/Billing - REP shall be able to process, extract, send bulk Customers subset of Account information to ODW - REP

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
DMS shall be able to send status request to Feeder VR


# Application2ApplicationWithBracketHierarchy

Requirements:
CIS - Utility shall be able to send on-demand meter read request to the Smart Meter via the Head-End

Implication:
May need to estimate or manually read, 
Not system critical


Requirements:
AMI Head-End shall be able to report & send "AMI Head-End to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS


DataFlowRef:
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}] +
[{(1B + 1Aa) or 1Ab} or 1B or 7] #|

Requirements:
DAP shall be able to report & send "DAP to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS

HowOften:
1 trans per PrePay meter per x on-demand cmds per time period

Implication:
Broken cash register, 
Not system critical


Requirements:
IHD shall be able to report & send "IHD to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from IHD to meter when re-established OR alternate dataflow to NMS and/or MDMS


Requirements:
Cust. EMS shall be able to report & send "Cust. EMS to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from Cust. EMS to meter when re-established OR alternate dataflow to NMS and/or MDMS


Requirements:
Smart Meter (Electric or Gas, Residential or Commercial/Industrial) shall be able to send on-demand meter read data to CIS - Utility

HowOften:
1 trans per PrePay meter per on demand request


Requirements:
Smart Meter ESI shall be able to send on-demand meter reading request to IHD via Smart Meter ESI


Requirements:
Smart Meter shall be able to send on-demand meter reading request to Cust. EMS via Smart Meter ESI


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI - Utility

HowOften:
1 trans per PrePay Customer per demand with IHD


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to Cust. EMS - Utility via non Smart Meter ESI

HowOften:
1 trans per PrePay Customer per demand with Cust. EMS - Utility


Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing - Utility and/or MDMS and/or NMS


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS via Smart Meter ESI


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to IHD via Smart Meter ESI


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS - Utility via non-Smart Meter ESI

HowOften:
1 trans per PrePay customer with Cust. EMS per x on-demand cmds per time period


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to IHD via non-Smart Meter ESI

HowOften:
1 trans per PrePay customer with IHD per x on-demand cmds per time period


Requirements:
IHD shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per PrePay customer with IHD

Implication:
Customer Frustration, 
Not system critical


Requirements:
Customer EMS shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per PrePay customer with Cust. EMS


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility

HowOften:
5-15 trans per 1000 utility prepay mtrs per day


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP

HowOften:
5-15 trans per 1000 REP prepay mtrs per day


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility


Requirements:
Feeder VR shall be able to send status reply to DMS


DataFlowRef:
4A +
[{1Ca + 4DRG} or {4Ba + 4ERU + 4E + 4ERG} or {4F + 4FRG} or 4GRG] #|

Requirements:
DMS shall be able to send sensor data request to Feeder VR


DataFlowRef:
[{1Ca + 4DRG} or {4Ba + 4ERU + 4E + 4ERG} or {4F + 4FRG} or 4GRG] + 4A #|

Requirements:
Feeder VR shall be able to send sensor data reply to DMS


Requirements:
Feeder VR shall be able to send status change info to DMS


Requirements:
Feeder VR shall be able to send deviation alert to DMS


Requirements:
Feeder VR shall be able to send alarm condition to DMS


Requirements:
Feeder VR shall be able to send failure to operate alert to DMS


DataFlowRef:
4A +
[{1Ca + 4DCB} or {4Ba + 4ERU + 4E + 4ECB} or {4F + 4FCB} or 4GCB] #|

Requirements:
DMS shall be able to send status request to Feeder CBC


DataFlowRef:
[{1Ca + 4DCB} or {4Ba + 4ERU + 4E + 4ECB} or {4F + 4FCB} or 4GCB] + 4A #|

Requirements:
Feeder CBC shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder CBC


Requirements:
Feeder CBC shall be able to send sensor data reply to DMS


Requirements:
Feeder CBC shall be able to send status change info to DMS

HowOften:
Average 1 alert every 12 hr for each CBC


Requirements:
Feeder CBC shall be able to send deviation alert to DMS


Requirements:
Feeder CBC shall be able to send alarm condition to DMS


Requirements:
Feeder CBC shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each CBC


Requirements:
DMS shall be able to send status request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send status reply to DMS


Requirements:
CIS - Utility shall be able to send bulk meter read information requests to MDMS

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


Requirements:
MDMS shall be able to send bulk meter read information requests to Head End


Requirements:
MDMS shall be able to process & send bulk meter read information data to CIS - Utility


Requirements:
AMI Head-End shall be able to process & forward on-demand meter read data to MDMS


DataFlowRef:
1D + 
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}]  #|

Requirements:
Smart Meter (Gas Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas C/I meter.  May have 15min vs 1hr interval data

Reliability:
90% success every 4-6 hours, 
98% success over a day, 
> 99.5% over two days

Implication:
Need to retry, 
Potential broken cash register, 
Not system critical


DataFlowRef:
1D + 
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}]   #|

Requirements:
Smart Meter (Gas Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas resdnt meter, with 4hr -24h interval data


Requirements:
Smart Meter (Electric Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
12-24 trans per day per electric C/I meter, Intervals of 15min to 1hr, 4-20 data points per interval

Reliability:
>98% success every 3 hours, 
>99.5% success over 2 days, 
> 99.5% over two days


Requirements:
Smart Meter (Electric Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
4-6 trans per day per electric resdnt meter, Intervals of 15min to 1hr, 4-8 data points per interval


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP


Requirements:
Customer Browser - Premise shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal

HowOften:
5-15 trans per 1000 Common Web Portal prepay mtrs per day


Requirements:
Customer Browser - Mobile shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
CIS/Billing - Utility shall be able to process, extract, send bulk Customers subset of Account information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


Requirements:
MDMS may be able to send multiple interval meter reading request to Smart Meter


Requirements:
Smart Meter may be able to process & send/forward multiple interval meter reading data (per specific meter request from MDMS) to MDMS


DataFlowRef:
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}]  +
[{(1B + 1Aa) or 1Ab} or 1B or 7] #|

HowOften:
1 trans per meter per x on-demand cmds per time period


Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing and/or MDMS and/or NMS


HowOften:
1 trans per Cust. EMS - Utility per x on-demand cmds per time period


HowOften:
1 trans per IHD per x on-demand cmds per time period


HowOften:
1 trans per Cust. EMS per on demand request


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI


HowOften:
1 trans per Cust. EMS - Utility per on demand request


HowOften:
1-10 trans per day per customer with IHD


HowOften:
1-10 trans per day per customer with Cust. EMS


Requirements:
LMS shall be able to send charging price rates to PHEV

Implication:
May need to retry, system critical in scale, PHEV could charge at minimum rate


Requirements:
non-Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-non-SMtr per day


Requirements:
Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-SMtr per day


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from PHEV) to LMS" communication failure to PHEV & NMS


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from LMS) to PHEV" communication failure to LMS


Requirements:
LMS shall be able to negotiate Power Charging Rate with PHEV

HowOften:
150 trans per 1000 mtrs 2-4 times per day

Implication:
Customer Service issue, PHEV battery does not get re-charged.  Potential system impact in scale


Requirements:
PHEV shall be able to send negotiate Power Charging Rate messages to LMS

HowOften:
1 thread, 2-4 trans per PHEV connected meter per day


Requirements:
AMI Head-End shall be able to process & send "PHEV VIN information request to MDMS (from PHEV)" communications failure to PHEV


Requirements:
PHEV shall be able to process & send charging status of the PHEV to LMS

HowOften:
2-4 trans per PHEV charging event per day


Requirements:
PHEV shall be able to publish PHEV VIN information request to MDMS


Requirements:
CIS - Utility shall be able to send a scheduled cancel service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch state request to Smart Meter


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS, or MDMS) communications failure" with Smart Meter, to CIS/Billing - Utility and/or MDMS and NMS


DataFlowRef:
1D +
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}] +
[8 or 9 or {1B or (1B + 1Aa) or 1Ab}] #|

TargetActor:
CIS/Billing - Utility, 
MDMS, 
LMS, 
DSM

Requirements:
Smart Meter shall be able to send service switch state data to CIS - Utility, MDMS, LMS, DSM


Requirements:
Smart Meter shall be able to send service switch operate acknowledgment to CIS - Utility, MDMS


Requirements:
Smart Meter shall be able to send service switch operate faillure to CIS - Utility, MDMS

HowOften:
1 trans per 1000 SW-oper per mtr per day


Requirements:
Smart Meter shall be able to report & send metrology information after a successful service switch operate to CIS - Utility, MDMS


Requirements:
CIS - Utility shall be able to send a meter config for prepay capability request to Smart Meter

HowOften:
1 trans per prepay enrollment per premise meter

Implication:
Need to retry, 
Potential broken PrePay meter config, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay unenroll per premise meter


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to IHD

HowOften:
25 trans per PrePay mtr with IHD per month


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to IHD via [Common Web Portal - Utility or ESI - non-Smart Meter)


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS via [Common Web Portal - Utility or ESI - non-Smart Meter)

HowOften:
25 trans per PrePay mtr with Cust. EMS per month


Requirements:
CIS - Utility shall be able to send a cancel of scheduled service switch operate request to Smart Meter


Requirements:
AMI Head-End shall be able to process & send "service switch operate request (from CIS - Utility) communications failure" with Smart Meter, to CIS - Utility

HowOften:
1-4 trans per 1000 PrePay mtrs-SW-oper per day


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS - Utility, or MDMS) communications failure" with Smart Meter, to AMI Head-End and/or MDMS and/or NMS


DataFlowRef:
1D +
[1Ca or {1Cb + 1Cba} or {1Cc + 1Cba}] +
[8 or 9 or {1B or (1AA or 1Ab)} #|


HowOften:
1 trans per 1000 SW-oper per PrePay mtrper day


Requirements:
DMS shall be able to send sensor data request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send sensor data reply to DMS


Requirements:
Feeder Sensor shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 hr for each Sensor


Requirements:
Feeder Sensor shall be able to send deviation alert to DMS


Requirements:
Feeder Sensor shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every day for each Sensor


DataFlowRef:
4A +
[{1Ca + 4DRC} or {4Ba + 4ERU + 4E + 4ERC} or {4F + 4FRC} or 4GRC] #|

Requirements:
DMS shall be able to send status request to Feeder Recloser


DataFlowRef:
[{1Ca + 4DRC} or {4Ba + 4ERU + 4E + 4ERC} or {4F + 4FRC} or 4GRC] + 4A #|

Requirements:
Feeder Recloser shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send sensor data reply to DMS


Requirements:
Feeder Recloser shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Recloser


Requirements:
Feeder Recloser shall be able to send deviation alert to DMS


Requirements:
Feeder Recloser shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Recloser


Requirements:
Feeder Recloser shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Recloser


DataFlowRef:
4A +
[{1Ca + 4DSW} or {4Ba + 4ERU + 4E + 4ESW} or {4F + 4FSW} or 4GSW] #|

Requirements:
DMS shall be able to send status request to Feeder Switch


DataFlowRef:
[{1Ca + 4DSW} or {4Ba + 4ERU + 4E + 4ESW} or {4F + 4FSW} or 4GSW] + 4A #|

Requirements:
Feeder Switch shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Switch


Requirements:
Feeder Switch shall be able to send sensor data reply to DMS


Requirements:
Feeder Switch shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Switch


Requirements:
Feeder Switch shall be able to send deviation alert to DMS


Requirements:
Feeder Switch shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Switch


Requirements:
Feeder Switch shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Switch


Requirements:
DMS shall be able to send status request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send sensor data reply to DMS


Requirements:
Feeder Fault_Detector shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 week for each Fault Detector


Requirements:
Feeder Fault_Detector shall be able to send deviation alert to DMS


Requirements:
Feeder Fault_Detector shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Fault Detector


Requirements:
DMS shall be able to send step up command to Feeder VR

HowOften:
Average 1 cmd every 2 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send step up command ACK to DMS


Requirements:
DMS shall be able to send step down command to Feeder VR


Requirements:
Feeder VR shall be able to send step down command ACK to DMS

HowOften:
Average 1 ack every 2 hr for each Feeder VR


Requirements:
DMS shall be able to send new config to Feeder VR

HowOften:
Average 1 cmd every 12 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder VR


Requirements:
DMS shall be able to send open command to Feeder CBC

HowOften:
Average 1 cmd every 12 hr for each Feeder CBC


Requirements:
Feeder CBC shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder CBC


Requirements:
Feeder CBC shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder CBC

HowOften:
Average 1 cmd every 1 week for each Feeder CBC


Requirements:
Feeder CBC shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder Sensor

HowOften:
Average 1 cmd every 1 week for each Feeder Sensor


Requirements:
Feeder Sensor shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Sensor


Requirements:
DMS shall be able to send new config to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send new config ACK to DMS


Requirements:
DMS shall be able to send open command to Feeder Switch

HowOften:
Average 1 cmd every 1 week for each Feeder Switch


Requirements:
Feeder Switch shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder Switch


Requirements:
Feeder Switch shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Switch


DailyClockPeriods:
From 1-6 hr duration, from 4-8 times a year


HowOften:
Average 1 cmd every 5 min for each Feeder VR


HowOften:
Average 1 ack every 5 min for each Feeder VR


HowOften:
Average 1 cmd every 1 hr for each Feeder VR


HowOften:
Average 1 ack every 1 hr for each Feeder VR


HowOften:
Average 1 cmd every 5 min for each Feeder CBC


HowOften:
Average 1 ack every 5 min for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder CBC


HowOften:
Average 1 ack every 1 hr for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder Sensor


HowOften:
Average 1 ack every 1 hr for each Feeder Sensor


HowOften:
Average 1 cmd every 12 hr for each Feeder Switch


HowOften:
Average 1 ack every 12 hr for each Feeder Switch


Requirements:
Smart Meter shall be able to send outage notification to OMS

HowOften:
100 percent of meters that lose power per day

Implication:
Not Critical due to broadcast nature of transmission


Requirements:
Smart Meter shall be able to send power restoration notification to OMS

HowOften:
100 percent of meters that returned to power per day


Requirements:
DAP shall be able to send a notification when DAP running on battery power to OMS

HowOften:
20 per 1000 DAP per system power outage event per day


Requirements:
OMS shall be able to process, extract, send bulk Customers subset of service outage information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day


Requirements:
MDMS shall be able to process, extract, send bulk Customers subset of meter information to ODW - Utility


Requirements:
AMI Head-End shall be able to process, extract, send bulk Customers subset of meter communication information to ODW - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
CIS/Billing - REP shall be able to process, extract, send bulk Customers subset of Account information to ODW - REP

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
DMS shall be able to send status request to Feeder VR


# ExcelAppConnectionsImport

Requirements:
CIS - Utility shall be able to send bulk meter read information requests to MDMS

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


Requirements:
MDMS shall be able to send bulk meter read information requests to Head End


Requirements:
MDMS shall be able to process & send bulk meter read information data to CIS - Utility


Requirements:
AMI Head-End shall be able to process & forward on-demand meter read data to MDMS


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]

Requirements:
Smart Meter (Gas Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas C/I meter.  May have 15min vs 1hr interval data

Reliability:
90% success every 4-6 hours, 
98% success over a day, 
> 99.5% over two days

Implication:
Need to retry, 
Potential broken cash register, 
Not system critical


Requirements:
Smart Meter (Gas Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
1-6 trans per day per gas resdnt meter, with 4hr -24h interval data


Requirements:
Smart Meter (Electric Commercial/Industrial) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
12-24 trans per day per electric C/I meter, Intervals of 15min to 1hr, 4-20 data points per interval

Reliability:
>98% success every 3 hours, 
>99.5% success over 2 days, 
> 99.5% over two days


Requirements:
Smart Meter (Electric Residential) shall be able to send multi interval-data meter reads data to AMI Head-End

HowOften:
4-6 trans per day per electric resdnt meter, Intervals of 15min to 1hr, 4-8 data points per interval


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP

HowOften:
5-15 trans per 1000 REP prepay mtrs per day

Implication:
Customer Frustration, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal

HowOften:
5-15 trans per 1000 Common Web Portal prepay mtrs per day


Requirements:
Customer Browser - Mobile shall be able to process & send Customer account information requests from authenticated Customer to Common Web Portal


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Premise

HowOften:
5-15 trans per 1000 utility prepay mtrs per day


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Web Portal - Utility shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Web Portal - REP shall be able to send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Premise


Requirements:
Common Web Portal shall be able to process & send Customer account information response data to authenticated Customer Browser - Mobile


Requirements:
CIS/Billing - Utility shall be able to process, extract, send bulk Customers subset of Account information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day
(x) * (y) = total Smart Meters deployed  per named utility


DataFlowRef:
1B +
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] +
1D

Requirements:
MDMS may be able to send multiple interval meter reading request to Smart Meter


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
1B

Requirements:
Smart Meter may be able to process & send/forward multiple interval meter reading data (per specific meter request from MDMS) to MDMS

Implication:
May need to estimate or manually read, 
Not system critical


DataFlowRef:
[(1Aa + 1B) or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
1D

Requirements:
CIS - Utility shall be able to send on-demand meter read request to the Smart Meter via the Head-End


DataFlowRef:
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  +
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
DAP shall be able to report & send "DAP to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS

HowOften:
1 trans per meter per x on-demand cmds per time period

Implication:
Broken cash register, 
Not system critical


Requirements:
IHD shall be able to report & send "IHD to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from IHD to meter when re-established OR alternate dataflow to NMS and/or MDMS


Requirements:
Cust. EMS shall be able to report & send "Cust. EMS to Meter on-demand meter read request communications errors", to MDMS and/or NMS via comm path from Cust. EMS to meter when re-established OR alternate dataflow to NMS and/or MDMS


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing and/or MDMS and/or NMS


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to IHD via Smart Meter ESI


Requirements:
Smart Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS via Smart Meter ESI


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to Cust. EMS - Utility via non-Smart Meter ESI

HowOften:
1 trans per Cust. EMS - Utility per x on-demand cmds per time period


Requirements:
2-Way Meter shall be able to report & send Meter on-demand read request app errors to IHD via non-Smart Meter ESI

HowOften:
1 trans per IHD per x on-demand cmds per time period


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)]  + 
[(1B + 1Aa) or 1Ab]

Requirements:
Smart Meter (Electric or Gas, Residential or Commercial/Industrial) shall be able to send on-demand meter read data to CIS - Utility


Requirements:
Smart Meter ESI shall be able to send on-demand meter reading request to IHD via Smart Meter ESI


Requirements:
Smart Meter shall be able to send on-demand meter reading request to Cust. EMS via Smart Meter ESI

HowOften:
1 trans per Cust. EMS per on demand request


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to Cust. EMS - Utility via non Smart Meter ESI

HowOften:
1 trans per Cust. EMS - Utility per on demand request


Requirements:
IHD shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per customer with IHD


Requirements:
Customer EMS shall be able to send on-demand meter reading request to Smart Meter

HowOften:
1-10 trans per day per customer with Cust. EMS


Requirements:
LMS shall be able to send charging price rates to PHEV

Implication:
May need to retry, system critical in scale, PHEV could charge at minimum rate


DataFlowRef:
5Bb+ 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
9

Requirements:
non-Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-non-SMtr per day


DataFlowRef:
5Ba+ 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
9

Requirements:
Smart Meter ESI shall be able to process & send "Send of Price Rate (from LM) to PHEV" communication failure to LMS

HowOften:
1 trans per 1000 PHEV-mtrs-ESI-SMtr per day


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from PHEV) to LMS" communication failure to PHEV & NMS


Requirements:
AMI Head-End shall be able to process & send "negotiate Power Charging Rate messages (from LMS) to PHEV" communication failure to LMS


Requirements:
LMS shall be able to negotiate Power Charging Rate with PHEV

HowOften:
150 trans per 1000 mtrs 2-4 times per day

Implication:
Customer Service issue, PHEV battery does not get re-charged.  Potential system impact in scale


Requirements:
PHEV shall be able to send negotiate Power Charging Rate messages to LMS

HowOften:
1 thread, 2-4 trans per PHEV connected meter per day


Requirements:
AMI Head-End shall be able to process & send "PHEV VIN information request to MDMS (from PHEV)" communications failure to PHEV


Requirements:
PHEV shall be able to process & send charging status of the PHEV to LMS

HowOften:
2-4 trans per PHEV charging event per day


Requirements:
PHEV shall be able to publish PHEV VIN information request to MDMS


DataFlowRef:
[(1Aa + 1B)  or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] + 
1D

Requirements:
CIS - Utility shall be able to send a scheduled cancel service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch operate request to Smart Meter


Requirements:
CIS - Utility shall be able to send a service switch state request to Smart Meter


DataFlowRef:
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
DAP shall be able to process & send "service switch operate request (from CIS, or MDMS) communications failure" with Smart Meter, to CIS/Billing - Utility and/or MDMS and NMS


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[8 or 9 or (1B or (1B + 1Aa) or 1Ab)]

TargetActor:
CIS/Billing - Utility, 
MDMS, 
LMS, 
DSM

Requirements:
Smart Meter shall be able to send service switch state data to CIS - Utility, MDMS, LMS, DSM


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[1B or ((1B + 1Aa) or 1Ab)]

Requirements:
Smart Meter shall be able to send service switch operate acknowledgment to CIS - Utility, MDMS


Requirements:
Smart Meter shall be able to send service switch operate faillure to CIS - Utility, MDMS

HowOften:
1 trans per 1000 SW-oper per mtr per day


Requirements:
Smart Meter shall be able to report & send metrology information after a successful service switch operate to CIS - Utility, MDMS


DataFlowRef:
[(1Aa + 1B)  or 1Ab] + 
[1Ca or (1Cba + 1Cb) or (1Cba + 1Cc)] +
1D

Requirements:
CIS - Utility shall be able to send a meter config for prepay capability request to Smart Meter

HowOften:
1 trans per prepay enrollment per premise meter

Implication:
Need to retry, 
Potential broken PrePay meter config, 
Not system critical


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay enrollment requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay enrollment per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Premise shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust premise browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - Utility

HowOften:
1 trans per Utility Cust mobile browser users prepay unenroll per premise meter


Requirements:
Customer Browser - Mobile shall be able to send Customer prepay unenroll requests from authenticated Customer to CIS / Billing - REP

HowOften:
1 trans per REP Cust mobile browser users prepay unenroll per premise meter


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to IHD

HowOften:
25 trans per PrePay mtr with IHD per month


Requirements:
CIS - Utility shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to IHD via [Common Web Portal - Utility or ESI - non-Smart Meter)


Requirements:
CIS - REP shall be able to send any of the PrePay messages (~10 different types) to Cust. EMS via [Common Web Portal - Utility or ESI - non-Smart Meter)

HowOften:
25 trans per PrePay mtr with Cust. EMS per month


Requirements:
CIS - Utility shall be able to send a cancel of scheduled service switch operate request to Smart Meter


Requirements:
AMI Head-End shall be able to process & send "service switch operate request (from CIS - Utility) communications failure" with Smart Meter, to CIS - Utility

HowOften:
1-4 trans per 1000 PrePay mtrs-SW-oper per day


Requirements:
DAP shall be able to process & send "service switch operate request (from CIS - Utility, or MDMS) communications failure" with Smart Meter, to AMI Head-End and/or MDMS and/or NMS


DataFlowRef:
1D +
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] +
[8 or 9 or (1B or (1AA or 1Ab)]


HowOften:
1 trans per 1000 SW-oper per PrePay mtrper day


Requirements:
AMI Head-End shall be able to report & send "AMI Head-End to Smart Meter on-demand meter read request communications errors", to CIS/Billing - Utility and/or MDMS and/or NMS


HowOften:
1 trans per PrePay meter per x on-demand cmds per time period


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] + 
[(1B + 1Aa) or 1Ab]

HowOften:
1 trans per PrePay meter per on demand request


Requirements:
2-Way Meter shall be able to send on-demand meter reading request to IHD via non Smart Meter ESI - Utility

HowOften:
1 trans per PrePay Customer per demand with IHD


HowOften:
1 trans per PrePay Customer per demand with Cust. EMS - Utility


DataFlowRef:
1D + 
[1Ca or (1Cb + 1Cba) or (1Cc + 1Cba)] + 
[((1B + 1Aa) or 1Ab) or 1B or 7]

Requirements:
Smart Meter shall be able to report & forward Meter on-demand read request app errors to CIS/Billing - Utility and/or MDMS and/or NMS


HowOften:
1 trans per PrePay customer with Cust. EMS per x on-demand cmds per time period


HowOften:
1 trans per PrePay customer with IHD per x on-demand cmds per time period


HowOften:
1-10 trans per day per PrePay customer with IHD


HowOften:
1-10 trans per day per PrePay customer with Cust. EMS


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility


Requirements:
Customer Browser - Premise shall be able to send Customer account information requests from authenticated Customer to Web Portal - REP


Requirements:
Customer Browser - Mobile shall be able to send Customer account information requests from authenticated Customer to Web Portal - Utility


Requirements:
Feeder VR shall be able to send status reply to DMS


DataFlowRef:
4A +
[(1Ca + 4DRG) or (4Ba + 4ERU + 4E + 4ERG) or (4F + 4FRG) or 4GRG]

Requirements:
DMS shall be able to send sensor data request to Feeder VR


DataFlowRef:
[(1Ca + 4DRG) or (4Ba + 4ERU + 4E + 4ERG) or (4F + 4FRG) or 4GRG] + 4A

Requirements:
Feeder VR shall be able to send sensor data reply to DMS


Requirements:
Feeder VR shall be able to send status change info to DMS


Requirements:
Feeder VR shall be able to send deviation alert to DMS


Requirements:
Feeder VR shall be able to send alarm condition to DMS


Requirements:
Feeder VR shall be able to send failure to operate alert to DMS


DataFlowRef:
4A +
[(1Ca + 4DCB) or (4Ba + 4ERU + 4E + 4ECB) or (4F + 4FCB) or 4GCB]

Requirements:
DMS shall be able to send status request to Feeder CBC


DataFlowRef:
[(1Ca + 4DCB) or (4Ba + 4ERU + 4E + 4ECB) or (4F + 4FCB) or 4GCB] + 4A

Requirements:
Feeder CBC shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder CBC


Requirements:
Feeder CBC shall be able to send sensor data reply to DMS


Requirements:
Feeder CBC shall be able to send status change info to DMS

HowOften:
Average 1 alert every 12 hr for each CBC


Requirements:
Feeder CBC shall be able to send deviation alert to DMS


Requirements:
Feeder CBC shall be able to send alarm condition to DMS


Requirements:
Feeder CBC shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each CBC


DataFlowRef:
4A +
[(1Ca + 4DS) or (4Ba + 4ERU + 4E + 4ES) or (4F + 4FS) or 4GS]

Requirements:
DMS shall be able to send status request to Feeder Sensor


DataFlowRef:
[(1Ca + 4DS) or (4Ba + 4ERU + 4E + 4ES) or (4F + 4FS) or 4GS] + 4A

Requirements:
Feeder Sensor shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Sensor


Requirements:
Feeder Sensor shall be able to send sensor data reply to DMS


Requirements:
Feeder Sensor shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 hr for each Sensor


Requirements:
Feeder Sensor shall be able to send deviation alert to DMS


Requirements:
Feeder Sensor shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every day for each Sensor


DataFlowRef:
4A +
[(1Ca + 4DRC) or (4Ba + 4ERU + 4E + 4ERC) or (4F + 4FRC) or 4GRC]

Requirements:
DMS shall be able to send status request to Feeder Recloser


DataFlowRef:
[(1Ca + 4DRC) or (4Ba + 4ERU + 4E + 4ERC) or (4F + 4FRC) or 4GRC] + 4A

Requirements:
Feeder Recloser shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send sensor data reply to DMS


Requirements:
Feeder Recloser shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Recloser


Requirements:
Feeder Recloser shall be able to send deviation alert to DMS


Requirements:
Feeder Recloser shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Recloser


Requirements:
Feeder Recloser shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Recloser


DataFlowRef:
4A +
[(1Ca + 4DSW) or (4Ba + 4ERU + 4E + 4ESW) or (4F + 4FSW) or 4GSW]

Requirements:
DMS shall be able to send status request to Feeder Switch


DataFlowRef:
[(1Ca + 4DSW) or (4Ba + 4ERU + 4E + 4ESW) or (4F + 4FSW) or 4GSW] + 4A

Requirements:
Feeder Switch shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Switch


Requirements:
Feeder Switch shall be able to send sensor data reply to DMS


Requirements:
Feeder Switch shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 day for each Switch


Requirements:
Feeder Switch shall be able to send deviation alert to DMS


Requirements:
Feeder Switch shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Switch


Requirements:
Feeder Switch shall be able to send failure to operate alert to DMS

HowOften:
Average 1 alarm every month for each Switch


Requirements:
DMS shall be able to send status request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send status reply to DMS


Requirements:
DMS shall be able to send sensor data request to Feeder Fault_Detector


Requirements:
Feeder Fault_Detector shall be able to send sensor data reply to DMS


Requirements:
Feeder Fault_Detector shall be able to send status change info to DMS

HowOften:
Average 1 alert every 1 week for each Fault Detector


Requirements:
Feeder Fault_Detector shall be able to send deviation alert to DMS


Requirements:
Feeder Fault_Detector shall be able to send alarm condition to DMS

HowOften:
Average 1 alarm every week for each Fault Detector


Requirements:
DMS shall be able to send step up command to Feeder VR

HowOften:
Average 1 cmd every 2 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send step up command ACK to DMS


Requirements:
DMS shall be able to send step down command to Feeder VR


Requirements:
Feeder VR shall be able to send step down command ACK to DMS

HowOften:
Average 1 ack every 2 hr for each Feeder VR


Requirements:
DMS shall be able to send new config to Feeder VR

HowOften:
Average 1 cmd every 12 hr for each Feeder VR


Requirements:
Feeder VR shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder VR


Requirements:
DMS shall be able to send open command to Feeder CBC

HowOften:
Average 1 cmd every 12 hr for each Feeder CBC


Requirements:
Feeder CBC shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder CBC


Requirements:
Feeder CBC shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 12 hr for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder CBC

HowOften:
Average 1 cmd every 1 week for each Feeder CBC


Requirements:
Feeder CBC shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder CBC


Requirements:
DMS shall be able to send new config to Feeder Sensor

HowOften:
Average 1 cmd every 1 week for each Feeder Sensor


Requirements:
Feeder Sensor shall be able to send new config ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Sensor


Requirements:
DMS shall be able to send new config to Feeder Recloser


Requirements:
Feeder Recloser shall be able to send new config ACK to DMS


Requirements:
DMS shall be able to send open command to Feeder Switch

HowOften:
Average 1 cmd every 1 week for each Feeder Switch


Requirements:
Feeder Switch shall be able to send open command ACK to DMS


Requirements:
DMS shall be able to send close command to Feeder Switch


Requirements:
Feeder Switch shall be able to send close command ACK to DMS

HowOften:
Average 1 ack every 1 week for each Feeder Switch


DailyClockPeriods:
From 1-6 hr duration, from 4-8 times a year


HowOften:
Average 1 cmd every 5 min for each Feeder VR


HowOften:
Average 1 ack every 5 min for each Feeder VR


HowOften:
Average 1 cmd every 1 hr for each Feeder VR


HowOften:
Average 1 ack every 1 hr for each Feeder VR


HowOften:
Average 1 cmd every 5 min for each Feeder CBC


HowOften:
Average 1 ack every 5 min for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder CBC


HowOften:
Average 1 ack every 1 hr for each Feeder CBC


HowOften:
Average 1 cmd every 1 hr for each Feeder Sensor


HowOften:
Average 1 ack every 1 hr for each Feeder Sensor


HowOften:
Average 1 cmd every 12 hr for each Feeder Switch


HowOften:
Average 1 ack every 12 hr for each Feeder Switch


Requirements:
Smart Meter shall be able to send outage notification to OMS

HowOften:
100 percent of meters that lose power per day

Implication:
Not Critical due to broadcast nature of transmission


Requirements:
Smart Meter shall be able to send power restoration notification to OMS

HowOften:
100 percent of meters that returned to power per day


Requirements:
DAP shall be able to send a notification when DAP running on battery power to OMS

HowOften:
20 per 1000 DAP per system power outage event per day


Requirements:
OMS shall be able to process, extract, send bulk Customers subset of service outage information to ODW - Utility

HowOften:
typically performed in x batches of y meters once per day


Requirements:
MDMS shall be able to process, extract, send bulk Customers subset of meter information to ODW - Utility


Requirements:
AMI Head-End shall be able to process, extract, send bulk Customers subset of meter communication information to ODW - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - Utility


Requirements:
ODW - Utility shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
CIS/Billing - REP shall be able to process, extract, send bulk Customers subset of Account information to ODW - REP

HowOften:
typically performed in x batches of y number meters once per day
(x) * (y) = total Smart Meters deployed  per named REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Web Portal - REP


Requirements:
ODW - REP shall be able to process & send bulk Customers subset of Acct/Premise information to Common Web Portal


Requirements:
DMS shall be able to send status request to Feeder VR


