AMI Requirements Report Prototype - We are down for …€¦ · XLS file · Web view ·...

Advanced Metering Infrastructure Program Preliminary Requirements

Document: document.xls

© Copyright 2006, Southern California Edison, All Rights Reserved of 30

Instructions

The Preliminary Requirements on the next worksheet represent the consolidated output of a series of 41 workshops covering 18 AMI Use Cases and involving more than 140 internal subject matter experts from across SCE’s Customer Service, Transmission & Distribution, and Power Procurement Business Units. The 18 Use Cases were scoped to include all areas of SCE’s operations where various anticipated features of advanced meters might be “put to use” to help reduce costs, promote improved customer service, or to improve overall operating efficiency. Each requirement included in the list is associated with a Component, Functional Area, and Priority.

Component links the requirement to the AMI architecture component that represents the most desired location to satisfy the function(s) described by the requirement. SCE understands that specific technical solutions may satisfy a requirement with other components and will use feedback from the vendor community to evolve our conceptual architecture. A diagram depicting SCE’s conceptual component architecture for AMI is also included in the “Diagrams” section of this document for reference.

Functional Area is an organizing construct which groups requirements related to a common metering or communications function.

Priority provides an indication of the relative importance of these requirements to SCE as driven by anticipated business value, regulatory requirements, and/or completeness of an overall AMI solution. Priority codes have the following meaning:

1 = Core Requirements2 = Desirable for 2007 product selection3 = Future functionality of particular interest to SCE




# Component Functional Area FR/ NFR Requirement Priority

** Please review the "Instructions" worksheet for an explanation of columns and priority scale

1 Meter General FR 12 Meter Metrology FR Meter shall record self reads at midnight for each register or channel every day 13 Meter Metrology FR Meter shall support interval data collection for energy consumption 14 Meter Metrology FR Meter shall support a minimum of 4 channels of interval data 1

5 Meter Metrology FR 26 Meter Metrology FR Meter shall support measurement of peak demand 17 Meter Metrology FR Meter shall support measurement of time-of-use kWH and kW demand 18 Meter Metrology FR Meter shall support interval data of 1, 5, 10, 15, 20, 30, or 60 minutes or 24 hours in length 19 Meter Metrology FR Meter's recording interval length shall be remotely configurable 1

10 Meter Metrology FR 111 Meter Metrology FR Meter shall support bi-directional metering to support distributed generation measurement 112 Meter Metrology FR Meter shall distinguish between a missing interval and zero consumption 113 Meter Metrology FR Meter shall distinguish between a power outage and zero consumption 1

14 Meter Metrology FR 3

15 Meter Metrology FR 116 Meter Metrology FR Non-residential meter shall additionally support multi-voltage 117 Meter Metrology FR Non-residential meter shall additionally support interval data collection for VAR and PF 118 Meter Memory/Storage NFR 1

19 Meter Memory/Storage NFR 1



All meters shall comply with SCE Specification E-100 SSM for Induction and Solid State Watthour Meters, Revision 5.1.2, (dated 6/29/06)

Meter shall support measurement of voltage data (line-to-line). This data shall be the maximum, minimum, and average over a programmable interval of 15, 30, or 60 minutes with timestamp.

Meter's recording interval length shall only be able to be adjusted at an appropriate time to ensure that the conversion to the "target" interval length meets billing system requirements (e.g. conversion from 15 min to 60 min occurs at the top of the hour)

Meter shall support measurement of two or more services in a single meter ("multi-service") for residential configurations (e.g. Form 2S). This is needed for distributed generation applications where we need to measure both the gross generator output as well as the net receive/sent to/from the utilityNon-residential meter shall additionally have pulse output capabilities (for backwards compatibility with existing energy management systems or other users of pulse output)

Meter shall store 5 minute interval data for a minimum of 45 days for two channelsMeter shall store at least the last 100 diagnostic events/errors in a log with a timestamp indicating the occurrence of the event/errorMeter shall store at least the last 100 informational messages in a log with a timestamp indicating the receipt of the messageMeter shall store at least the last 512 communications events in a log with a timestamp indicating the occurrence of the event.





22 Meter Meter Communications FRMeters shall be enabled for two-way secure communications with authorized systems and devices

1

23 Meter Meter Communications FR 1

24 Meter Meter Communications FR 3

25 Meter Meter Communications NFR 126 Meter Meter Communications FR Meter shall continue to record data during a communications failure/outage. 1

27 Meter Meter Communications FR 128 Meter Meter Communications FR Meter shall separately identify communications event data from metering data 129 Meter Internal Clock FR Meter's internal clock shall be validated with an external time source at least once per day. 1

30 Meter Internal Clock FR 1

31 Meter Internal Clock FR 232 Meter Internal Clock FR Meter shall log all successful and failed internal clock time corrections or adjustments. 2

33 Meter Internal Clock FR 134 Meter Default Read Schedule FR Meter shall store its own default read schedule 135 Meter Default Read Schedule FR Meter's default read time shall be remotely programmable/ updateable. 136 Meter Default Read Schedule FR Meter shall store, log, and acknowledge any changes to the default read schedule. 237 Meter Default Read Schedule FR Meter shall acknowledge receipt and setup of a read schedule 138 Meter Default Read Schedule FR Meter shall send all interval read data at least once per day 1

39 Meter Default Read Schedule FR 140 Meter Default Read Schedule FR Meter shall have the ability to recognize and log when it cannot send a scheduled read 2

41 Meter Default Read Schedule FR 142 Meter Non-Default Read Schedule FR Meter shall be able to store multiple read schedules (minimum of 4 schedules) 1

Meter shall have a unique internal and external identity to enable targeted messaging and communications (i.e. individually addressable meters) SCE prefers a standards-based physical communications link between the meter and the communications module. If the communications link used is not standards-based, the Vendor shall identify and specify the limitations of the physical link.If Meter's internal communication component utilizes wireless technology, Meter communication component shall have appropriate FCC approvals

Meter shall keep an on-board log of communications events:1. link fail2. link switch3. link up4. link quality

Meter's internal clock shall be automatically reset during the daily time validation if meter time is greater than 20 seconds but less than 120 seconds out of synch with the external time source

Meter's internal clock shall be synchronized/reset within a recording interval, but not at an interval boundary

Meter's internal clock shall keep time even if there is no communication with the network and shall maintain holdover accuracy to ANSI C12.1 specifications.

Meter shall be capable of sending all read data according to its stored read schedule (without being prompted by any external command or communication)

Following a failed scheduled read, at the next scheduled read time the meter shall send all interval read data since the last successful scheduled read transmission





43 Meter Non-Default Read Schedule FR 1



46 Meter Non-Default Read Schedule FR 147 Meter On Demand Reads FR Meter shall be able to respond to requests for on-demand access to meter and log data. 1

48 Meter On Demand Reads NFR 1

49 Meter On Demand Reads NFR 2

50 Meter On Demand Reads FR 251 Meter Remote Disconnect/Reconnect FR Meter shall be able to be remotely disconnected/ reconnected 1

52 Meter Remote Disconnect/Reconnect FR 153 Meter Remote Disconnect/Reconnect FR Meter shall be able to accept scheduled service disconnect/ reconnect 154 Meter Remote Disconnect/Reconnect FR 1

55 Meter Remote Disconnect/Reconnect FR 1





60 Meter Remote Disconnect/Reconnect NFR 1

Meter shall be capable of sending all read data according to multiple stored, alternate read schedules (without being prompted by any external command or communication)Meter shall be capable of sending all read data for stored read schedules at a frequency configurable down to the meter's interval data recording length.For the first occurrence of a non-default scheduled read (i.e. a read that occurs more frequently than once per day), the AMI meter shall send data beginning at midnight that morning through current time.For second and later occurrences of a non default scheduled read, the AMI meter shall send data beginning at the previous read time through current time.

Meter shall be able to receive, log, and return requests for on-demand meter data (up to 24 hours of data) within 60 seconds of the meter receipt Meter shall be able to receive, log, and return requests for on-demand meter data (up to 7 days of data) within 60 seconds of the meter receipt Meter shall be able to log failed on demand reads (meter unable to respond to on demand request) in the communications log along with all information available to define the cause of the failure.

Meter shall remain energized and continue to monitor and record consumption (i.e. zero consumption for each interval) when disconnect switch is the open/disconnected position

Meter shall be able to be remotely disconnected/ reconnected on demandMeter shall be able to be remotely disconnected/reconnected according to utility pre-configured rulesMeter shall be able to detect duplicate service disconnect/ reconnect events and ignore the duplicate events (e.g. Meter is already on -- reconnect event accepted with no action taken)Meter shall be able to cancel or update/reschedule scheduled disconnect/ reconnect events prior to their completionMeter shall send a meter read and acknowledgement to Data Center Aggregator upon a successfully completed or failed electric service disconnect/ reconnect eventMeter shall enable an SCE Employee working on-site at the customer premise to be able to physically operate its service disconnect/ reconnect switch at any time. 24 hours, 7 days a week, 365 days a yearMeter shall support an external authorization/ authentication routine (i.e. by remote systems or field tool) to enable only active and eligible SCE employees to operate its service disconnect/reconnect switch on-site at the customer premise










66 Meter Service Limiting FR 1




70 Meter Service Limiting NFR 171 Meter Service Limiting FR Meter shall be able to have service limited at multiple configurable steps 1




75 Meter Tariff/Rate Configuration FR 1

Meter shall allow authorized SCE employee (while on-site at the customer premise) to operate the service disconnect/reconnect switch immediately (regardless of interval) or to schedule a connect/ disconnect for a future interval Meter shall log date/time and status of attempts to operate the service disconnect/reconnect switch remotely or on-site at the customer premise. Log entries will include requestiong user or system identity and authorization statusMeter shall be able to be remotely disconnected/reconnected on demand and have acknowledgement received by requesting system within 1 minute of request being initiatedMeter shall allow a reconnect event to occur following a disconnect event only after a configurable amount of time (e.g. at least 1 to 2 minutes) has elapsed since the disconnect event.

Should a disconnect event and reconnect event be scheduled to occur for the same meter on the same day, Meter shall log the events and automatically provide an on-demand read to the Data Center Aggregator without operating the disconnect/reconnect switchMeter shall have the ability to limit service to customers upon a remote utility request (on-demand, scheduled, or via pre-configured rules)Meter shall be able to detect duplicate service limiting events and ensure the duplicate event is ignored (e.g. Meter is already limited -- identical limit event accepted with no action taken)Meter shall be able to cancel or update/reschedule scheduled service limiting events prior to their completionMeter shall send a meter read and acknowledgement to Data Center Aggregator upon a successfully completed or failed electric service limiting eventMeter shall be able to be remotely limited on demand and have acknowledgement received by requesting system within 1 minute of request being initiated

Meter shall disconnect (i.e. open disconnect switch) if customer load is above agreed configured limiting levelMeter shall reconnect automatically after a configurable amount of time (e.g. 2 minutes) to its presently configured limiting level if meter disconnects because the configured limit is exceeded

Meter shall attempt automatic reconnection a configurable number of times (e.g. only once) after a configurable duration (e.g. 2 minutes) per 24 hour period if meter disconnects because configured limit is exceeded. Meter shall be able to receive, log, and update tariff and rate information received from the Data Center Aggregator.





76 Meter Tariff/Rate Configuration NFR 1

77 Meter Demand Response FR 1



80 Meter Load Control FR 1



83 Meter Load Control NFR 2




87 Meter Load Control FR 188 Meter Load Control FR Meter shall be able to monitor and log customer curtailment override requests 2



Meter shall be able to receive, log, and update tariff and rate information received from the Data Center Aggregator at midnight on the day it is received, and send an acknowledgement to the Data Center Aggregator within 5 minutes of completed processing.Meter shall be able to automatically launch and terminate demand response events, once it has received the event message from the Data Center AggregatorMeter shall be able to receive and process demand response event cancellations or reschedule messagesMeter shall be able to log demand response events and send acknowledgement of successful processing to Data Center AggregatorMeter shall be able to receive, log, and execute secure load control/curtailment requests, via AMI communications systemLoad Control/Curtailment requests supported by the meter shall include curtailment type, curtailment start and planned end dates/times, and date/time of requestMeter shall be able to receive load control/curtailment event messages (to be sent to meter display or local display device) that differentiate between predicted (override available) and emergency (no override) energy shortage curtailment requestsMeter shall enable a grace period allowing the customer to reduce load after receiving a curtailment event. Grace period shall be configurable based on event type (predicted or emergency).

Meter shall be capable of receiving and simultaneously storing at least two separate scheduled curtailment requests.Meter shall be able to receive, log, and process secure load control/curtailment END messages, so that the curtailment can be ended (with full restoration of service) earlier than specified in the original request.Meter shall allow curtailment events to expire (with full restoration of service), if no load restoration message is received before the curtailment end time specified in the curtailment initiation message

Meter shall support a curtailment override option at the customer site for non-emergency events. This override function could be implemented directly through the use of a button/ data link to the meter or indirectly via communications equipment and back office systems

Meter shall be able to monitor and log customer non-compliance with curtailment requests (load level above curtailment threshold)Meter shall be able to provide (available) load data and response time on demand to the Data Center Aggregator for purposes of determining amount of load available for curtailment








94 Meter Distributed Generation Support FR 195 Meter Distributed Generation Support FR Meter shall be capable of detecting distributed generation 3

96 Meter Prepaid Metering FR 1




100 Meter Prepaid Metering FR 3101 Meter Outage Detection/Management FR Meter shall be able to communicate its energized status (i.e. has voltage) 1

102 Meter Outage Detection/Management FR 2103 Meter Outage Detection/Management FR Meter shall report restoration information (voltage quality and quantity) 2

104 Meter Outage Detection/Management FR 2



Meter shall support from 10 to 100 curtailment requests during 1 year. This would be the equivalent of 150 to 1500 curtailment requests during its life cycle. Meter shall send log of curtailment requests (and corresponding compliance/non-compliance) to Data Center Aggregator within 24 hours for compliance evaluation and at least once per week for system auditingMeter shall support on demand request for log of curtailment requests/events (and corresponding compliance/non-compliance)Meter shall be able to be re-programmed remotely to support bi-directional metering. This reprogramming event will be logged in the meter and sent back with the next regular meter read.

Meter shall be able to support both prepayment services and regular billing and payment services (i.e. no special prepayment meter required) Meter shall be able to be converted to/from a prepayment program at the end of a recording interval without disruption to service. Meter shall be able to receive and process informational and transactional prepayment messages from the Data Center AggregatorMeter shall send an acknowledgement message to the Data Center Aggregator whenever informational and transactional prepayment messages are received and processed.Meter shall be able to store multiple, scheduled prepayment events for the same service location and send an alert when a overlapping prepayment schedules exist

The meter shall be able to detect and communicate a power outage at the premise prior to communications loss.

Meter disconnect/reconnect switch shall be able to be configured to open during an outage when certain set thresholds are reached. Configuration thresholds should include minimum voltage and duration of that voltage to trigger disconnects. For overvoltage, maximum voltage and duration will also be supported.

Meter shall be able to reconnect automatically (i.e. close disconnect/reconnect switch) after voltage has returned to and remained within configurable voltage thresholds for a configurable amount of time (e.g. voltage is within limits and remained above 90% of nominal voltage for at least 3 sec.)

Meter shall be able to reconnect automatically (i.e. close disconnect/ reconnect switch) within a remotely configurable random interval (e.g. 0-30 sec) upon restoration of voltage





107 Meter Tamper Detection FR 1

108 Meter Tamper Detection FR 1109 Meter Tamper Detection FR Meter shall detect physical inversion and generate a tamper event 1



112 Meter Tamper Detection FR 1113 Meter Tamper Detection NFR Meter tamper events shall be sent with a higher priority than normal status messages 1




117 Meter Power Quality FR 2





122 Meter Power Quality NFR 3


Meter shall be able to detect removal from its socket and generate a tamper event before it loses ability to communicate with the communications networkMeter shall be able to detect voltage at the load side when the disconnect switch in the meter is open (for the purpose of detecting meter bypass) and generate a tamper event

Meter shall detect physical tampering, such as, seal tampering, meter ring removal, case / cover removal etc and generate a tamper event For each tamper event, the meter shall, at a minimum, transmit and locally log the following information: 1. Event Timestamp 2. Tamper status (event type) 3. Meter ID

Meter shall communicate tamper events to the Data Center Aggregator as soon as they occur (when possible)

If the meter is unable to communicate at the time the tamper event is detected, meter shall store tamper events and transmit them when meter communications are re-establishedMeter shall distinguish initial installation events and re-energize events (i.e. after an outage) from meter removal and reinstallation (potential tampering) to avoid transmission of non tamper related events. Meter shall store tamper events until they are flagged for deletion once they have been successfully transferred to the Data Center Aggregator and 45 days have passed. Meter shall monitor voltage in order to detect an RMS variation according to IEC 61000-4-30 and IEEE 1159 standardsMeter shall be able to measure RMS variation at the customer site in order to detect the origin of an RMS variation (Customer side or Network side). Meter shall detect and log RMS variation based on magnitude, duration, and direction. (per phase, aggregate) Meter shall make RMS variation event data available for retrieval from the meter even if there is a communications outage before, during, and after the event.Meter shall allow authorized SCE employees to retrieve detailed RMS Variation information both locally and remotely (on demand). Local communication has priority over remote Meter shall measure harmonics data according to IEC 61000-4-7 and IEEE 519 for voltage and current.Meter shall store harmonics data for a period ranging from 1 - 7 days after the data is captured, depending on the frequency of retrieval.








127 Meter Meter Display - Energy FR 2








135 Meter Meter Display - Info FR 1



Meter shall allow authorized SCE employees to retrieve detailed harmonics information both locally and remotely (on demand). Local communication has priority over remote Meter shall be capable of storing and returning event based power quality information on demand for a minimum of 60 days after the data is captured, even if there is no communications with the meter over the 60 day period. Meter shall be able to clear power quality data (event data and harmonics) from its memory once the data has been retrieved from the meterMeter shall be remotely configurable to record the amount of gross and/or net energy consumed and generated (kWH) within the current bill cycle so that it can be displayed on a premise device and/or meter displayMeter shall be remotely configurable to record the peak demand in kW (consumed and generated) recorded to date in the current bill cycle with the date/time it occurred so that it can be displayed on a premise device and/or meter display Meter shall be remotely configurable to record the energy consumed and generated in kWH, in time-of-use periods, for energy consumed and generated within the current bill cycle so that it can be displayed on a premise device and/or meter displayMeter shall be remotely configurable to record the peak demand (consumed and generated) in kW, in time-of-use-periods, recorded to date in the current bill cycle with the date/time it occurred so that it can be displayed on a premise device and/or meter display

Meter shall be remotely configurable to record consumption (e.g. WH or kWH) for the last completed recording interval so that it can be displayed on a premise device and/or meter displayMeter shall be remotely configurable to record gross and/or net energy consumed and generated (WH or kWH) for the last completed recording interval so that it can be displayed on a premise device and/or meter display

Meter shall be remotely configurable to record customer's instantaneous demand (e.g. W or kW) so that it can be displayed on a premise device and/or meter display (and updated as frequently as every 3 seconds)Meter shall be remotely configurable to record the customer's instantaneous volts, Amps and VARs so that they can be displayed on a premise device and/or meter display Meter shall be able to send all meter display information and messages to the customer's premise display device (the device must meet SCE standards)Meter display shall provide date and time in "local time", displaying the time in Pacific Daylight Time or Pacific Standard Time as appropriateMeter shall externally indicate electric service connect/disconnect status so that it is visible to customer or SCE employee on site.














147 Meter Meter Display - Messages FR 3

148 Meter Meter Display - Messages FR 3

149 Meter Meter Display - Messages NFR 2

150 Meter Meter Display - Config FR 2

151 Meter Meter Display - Config FR 2

Meter shall be remotely configurable to record the customer's current bill cycle schedule (start/end date and number of days) so that it can be displayed on a premise device and/or meter display

Meter shall be remotely configurable to record the customer's current rate schedule (e.g. TOU-GS1, etc.) so that it can be displayed on a premise device and/or meter displayMeter shall be able to remotely receive and store rate information (one rate at a time) that is needed to calculate the customer's estimated energy costs (kWh, time-of-use, baseline, etc.) to enable display of this informationEstimated energy cost data that is presented on the meter display shall be accompanied by an "estimate only" message. Meter shall be remotely configurable to record the estimated energy cost for consumed and generated energy for the current billing cycle so that it can be displayed on a premise device and/or meter display Meter shall be remotely configurable to record the estimated energy cost for consumed and generated energy, in time-of-use periods, for the current billing cycle so that it can be displayed on a premise device and/or meter displayMeter shall be remotely configurable to record the estimated energy cost for consumed and generated energy for the last completed recording interval so that it can be displayed on a premise device and/or meter displayMeter shall record the customer's prepayment balance in dollars, kWh, and estimated time remaining (days/hrs/mins) based on historical consumption and date/time of last update so that it can be displayed on a premise device and/or meter displayWhen the estimated prepay time remaining reaches a configurable threshold (i.e. 48 hrs), meter shall be able to refresh customer's prepayment balance, kWh, and estimated time remaining (hrs/mins) at the same frequency as the meter's billing intervals for the purpose of displaying it on a premise device and/or meter display

Meter shall be able to display pending, active and ended event messages to include the event type, event schedule date/time (start and end), hourly/time-of-use pricing and customer cost Meter shall be able to display the date and time (local time) when the meter event information was last received/updated (e.g. CPP event notification received mm/dd/yy, 10:00 am) Meter shall transmit utility messages and/or energy information to a display device and/or load control equipment within 10 seconds of being received or recorded by the meterMeter shall be able to execute and log remote meter display provisioning and configuration requests. Meter display shall be remotely configurable to customize individual information attributes as available or not available for display





152 Meter Meter Display - Config NFR 2

153 Meter Testing & Diagnostics FR 1

154 Meter Testing & Diagnostics FRMeter shall support a remotely or locally initiated meter test for communications connection status

1155 Meter Testing & Diagnostics FR Meter shall support a remotely or locally initiated meter test for HAN operation 1156 Meter Testing & Diagnostics FR Meter shall support a remotely or locally initiated meter test for energized status 1157 Meter Testing & Diagnostics FR Meter shall support a remotely or locally initiated meter test for load side voltage 1158 Meter Testing & Diagnostics FR Meter shall support a remotely or locally initiated meter test for disconnect switch status 1159 Meter Testing & Diagnostics FR Meter shall support a remotely or locally initiated meter test for internal clock time accuracy 1160 Meter Testing & Diagnostics NFR Meter shall return results for all remote or local meter tests within 60 seconds 2

161 Meter Self-Monitoring & Alarms FR 1




165 Meter Self-Monitoring & Alarms NFR 1166 Meter Self-Monitoring & Alarms FR Meter shall be able to detect, log, and report program or memory failure 1





Meter shall be able to complete remotely initiated meter display configuration requests within 60 seconds of being receivedMeter shall support on demand or scheduled meter tests issued remotely via the Data Center Aggregator or locally on-site (e.g. via a field tool) through both wireless and optical port communications.

Meter shall be able to initiate meter tests automatically based on a schedule stored within the meter, based on a schedule stored within a neighborhood aggregator, or based upon the detection of certain events by the meterMeter shall be able to send non-usage messages and alarms to the Data Center Aggregator that contain date/time from internal meter clock, message code/type, and meter identifierMeter shall be able to diagnose a variety of self-test results and determine if failures are critical or non-critical to determine what kind of notification should be provided (e.g. immediate, nightly, only upon request, etc.)Meter shall be able to test / check that it is recording data correctly and consistently. Detected failures shall be logged and generate an event specific to that measurement to report to the Data Center Aggregator.Meter shall perform self check at least once per month and as often as once per day and results logged and sent in with next scheduled read.

Meter shall be able to detect and log communications link failures upon failed communications initiated from the meterMeter shall be able to send an alarm/event to the Data Center Aggregator when a configurable number of consecutive communications link failures are detected (e.g. three consecutive link failures)Meter shall be able to periodically record the communication signal strength and report it back to the Data Center AggregatorMeter shall be able to self diagnose/detect a meter display failure and log the failure. (E.g. No display, illegible text)




# Component Functional Area FR/ NFR Requirement Priority171 Meter Self-Monitoring & Alarms FR Meter shall prioritize failures by safety /service versus other failure types 1172 Meter Self-Monitoring & Alarms NFR Meter shall send safety / service failure events within 15 minutes of detection 1


174 Meter Event/Message Management & Logs FR 1





179 Meter Event/Message Management & Logs NFR 1180 Meter Event/Message Management & Logs FR Meter shall log all messages sent to and received from the Data Center Aggregator 1


182 Meter Installation FR 1

183 Meter Installation FR 1184 Meter Installation FR Meter shall accept installed service point information from the installer's field tool. 1



187 Meter Installation FRBy default, meter disconnect switch shall be in the "closed"/connected position upon installation

1


Meter shall make diagnostic log information available either on-demand or by regularly sending to the Data Center AggregatorMeter shall be able to receive and send, store, log, and process many types of event and informational messages including Disconnect, Reconnect, Prepayment, Meter Read Schedule maintenance, demand response curtailment start/end, customer override, etc.Meter shall authenticate message/request sources (systems or devices) prior to processing or displaying such information. Meter shall reject and log messages/requests that are received from unauthorized systems or devicesMeter shall have the ability to prioritize messages (event and informational) received from the Data Center Aggregator (e.g. connect/disconnect, load control, etc) based on message attributes (type, source, explicit priority, etc.)Meter shall send an acknowledgement of receipt of event and informational messages to the Data Center Aggregator. Meter shall send an acknowledgement of receipt of event and informational messages to the Data Center Aggregator within a configurable length of time (as quickly as 60 seconds)

Meter's message logs shall include the following information at a minimum: message type, process status, system/device source, date/time received or sent (internal meter clock), event schedule (start and end) date/time (if applicable), hourly and/or time-of-use price information (if applicable for the event type)

Meter shall be preprogrammed with default SCE configuration prior to shipment from the manufacturer.Meter shall be configured with appropriate tariff/rate program at installation time (updated from default configuration)

Meter shall accept old meter ID from installer field tool and communicate it to Data Center Aggregator Meter shall accept old meter final reading from installer field tool and communicate it to the Data Center Aggregator

Upon installation, the meter shall recognize it is in the wrong socket. (configuration, i.e. number of clips)










194 Meter Installation NFR 1

195 Meter Meter Management FR 1



Upon installation, meter shall self-register on the AMI Communications Network. Self-registration data shall include:

1.New meter ID2.New meter installation read3.Comms address4.Meter log information5.Removed meter ID6.Removed meter read7.Security credentials8.Customer devices present within HAN (may not use this information until customer enrolls)9.Current program identification

If not self-registered on install, meter shall self-register on the AMI Communications Network the first time that communication is established in that location. Pre-condition: DCA shall have a unique identifier stored for the meter before the meter can authenticate and join the network.

In the case of self-registration failure, Meter shall be able to automatically reattempt self-registration after a configurable period of timeUpon installation, meter shall perform a self diagnostic and detect and log all failures. SCE defined critical failures shall be reported to Data Center Aggregator immediately (at a minimum: check sum error, meter failure from firmware upgrade, metrology failure, program or memory failure, time synch failure)

Upon installation, meter shall communicate to Installer:1.Meter health check/diagnostic results2.Communications network check results (WAN & HAN) Meter shall complete installation self-registration and self-diagnostic processes in less than 2 minutes combined. This is driven by the fact that total meter installation time shall be less than 15 minutes. Meter shall be physically assigned a utility meter number (before it arrives at utility) which identifies manufacturer, meter form, voltage, communications type, etc.Individual meters shall be identifiable within shipping containers and packaging (can be RFID or bar code)Meter packing labels shall include: Class, voltage, wire, cycles, test amps, KW, catalog number, Purchase Order number and release, quantity, meter form, born-on date, Lot number, Utility meter numbers in box, manf. Serial number (RFID or bar codes)






199 Meter Meter Reliability NFR 1

200 Meter Software/Firmware Upgrades FR 1



203 Meter Software/Firmware Upgrades FRMeter shall permit remotely or locally initiated reversion of software/firmware to a previous version

1

204 Meter Software/Firmware Upgrades FR 1205 Meter Software/Firmware Upgrades FR Meter's current software/firmware version shall be remotely and locally readable 1206 Meter Software/Firmware Upgrades FR Meter shall be configurable to retain stored register reads over a software/firmware upgrade 1207 Meter Software/Firmware Upgrades FR Meter shall be configurable to reset stored register reads over a software/firmware upgrade 1







214 Meter Local Connectivity FR 2

Meter identification mechanism shall require minimal manual interaction, and should be usable by various actors enterprise (warehouse tech, meter shop tech, meter installer). Could be RFID or bar codesMeter shall have a projected minimum service life of 20 years, with a failure rate of less than 0.5% per yearMeter shall be able to accept and install software/firmware upgrades provided remotely via the AMI communications networkMeter shall be able to accept and install software/firmware upgrades provided locally on site either through both wireless and optical port communicationsMeter shall continue normal operation while downloading software/firmware upgrades until instructed to change to the new version

Meter shall automatically revert to a previous version of software/firmware if a critical failure is detected on start-up following upgrade. Reversion shall not happen repeatedly.

Meter shall be able to retain all meter configuration settings, statuses, customer information, and event logs over a software/firmware upgradeMeter shall be designed with failsafe logic to minimize mis-operation of the disconnect switch and load control/distributed generation during software/firmware upgrades Meter shall log firmware download and upgrade attempts, failures, successes, reversions, etc. with timestampMeter shall report important or critical failures following a software/firmware upgrade within 15 minutes after start-up of new program. Critical failures could include billing information loss or loss of electric service. Ability to program what failures report immediately needs to be configurable.

Meter shall report non-critical failures following a software/firmware upgrade with the next regularly scheduled meter read.When upgrading large number of meters, meter shall report software/ firmware upgrade failures (where reversion is required) at the next meter readUpon completion of proper authorization by the meter of a field tool, meter shall be able to identify itself to field tool and provide access to its data and configuration settings at installation time, and later in support of ongoing operations & maintenance activities







217 Meter Local Connectivity NFR 1

218 Meter Local Connectivity FR 1219 Meter Local Connectivity FR Meter shall log all local meter data download attempts. 1

220 Meter Distribution Functions FRMeter shall be capable of responding to a request from an authorized source for present voltage

2

221 Meter Distribution Functions FR 2

222 Meter Distribution Functions NFR 3223 Premise Gateway Meter Communications NFR Premise Gateway shall be physically located under the cover of the meter 1

224 Premise Gateway Internal Clock FR Premise Gateway shall be time-synchronized with an external time source at least once per day. 1

225 Premise Gateway HAN NFR 1

226 Premise Gateway HAN FR 1




230 Premise Gateway 3rd Party Messaging FR 2


Meter shall be able to communicate locally to a field tool independently of the normal AMI communications mechanismMeter shall support local download to a field tool of all meter and communications data and logs stored in meter memory through both wireless and optical port communicationsMeter shall support local download to a field tool of all meter and communications data and logs stored in meter memory within 1 minute or lessMeter shall provide security/ authentication for local meter data download attempts to ensure downloads can only be executed by authorized utility or third party personnel

When the meter replies to a request for voltage from a Distribution Automation Node, it shall report 1 - timestamp and 2 - VoltageMeter shall provide Fault report to Distribution Control Management System in less than 5 sec (time of fault to annunciation)

Premise Gateway shall use ZigBee v1.1 or later in the 2400 MHz ISM band as the Home Area Network (HAN). The ZigBee HAN controller (aka coordinator) shall be located under the cover of the meter. The HAN shall maintain the entire ZigBee open protocol stack including ZigBee profiles.Premise Gateway shall be able to securely route messages between the Communications Network and the customer's HAN for the purpose of monitoring customer devices.

Premise Gateway shall be able to securely route messages between the Communications Network and the customer's HAN for the purpose of controlling/programming customer devices.Premise Gateway shall be able to receive event messages from HAN devices (e.g. customer's local display device) and securely route them through the AMI Communications NetworkPremise Gateway shall detect failures in communicating with subscribed HAN devices and report exceptions to the Data Center AggregatorPremise Gateway shall be able to communicate with authorized third parties directly or via the AMI Communications NetworkPremise Gateway shall be remotely configurable to communicate with zero, one, or many third parties.







234 Premise Gateway 3rd Party Messaging NFR 3


236 Premise Gateway Load Control FR 1

237 Premise Gateway Load Control NFR 1



240 Premise Gateway Gas/Water Utility Meters FR 2






Premise Gateway shall log unauthorized third party message attempts (inbound or outbound) to/from customer HAN devices

Premise Gateway shall generate an alarm/real-time event to Data Center Aggregator when unauthorized third party messaging attempts (to/from HAN devices) exceeds the rate of 10 per hourOnce received, the Premise Gateway shall deliver inbound messages to HAN devices and outbound messages back to the 3rd Party (directly or via AMI Communications Network) in 60 seconds or less, subject to message prioritizationPremise Gateway shall be able to prioritize event messages received from SCE and 3rd parties. The prioritization shall be configurable by the utility. Premise Gateway shall route event messages between the AMI Communications Network and customer load control equipment. (customer devices must meet SCE standards) Premise Gateway shall route event messages between the AMI Communications Network and customer load control equipment within 60 seconds of being received (at P.G.) or sent (from load control device)Premise Gateway shall log all attempts (with success/failure status) to deliver curtailment requests to load control devicesPremise Gateway shall support conveying load control information (including compliance status and time remaining to comply) to local display device.Premise Gateway shall support communications between any SCE approved AMI compatible water/gas meters and the AMI Communications NetworkPremise Gateway shall be compatible with existing Gas/Water Encoder-Receiver-Transmitter (ERT) devices (Itron or other)Premise Gateway shall support polling of gas/water meters as well as accepting information originated directly from gas/water metersPremise Gateway shall support receipt of any data messaging from water/gas meters so long as it is formatted according to SCE AMI defined standardsPremise Gateway shall add date/time stamp to water/gas meter reads (if not already provided by water/gas meter)Premise Gateway shall add its device identifier (i.e. SCE device identifier) to water/gas meter reads as the entry point into the AMI communications network





246 Premise Gateway Distributed Generation Support FR 3

247 Premise Gateway Distributed Generation Support FR 3

248 Premise Gateway Event/Message Management & Logs FR 2



251 Internal Clock FR 1

252 Event/Message Management & Logs FR Neighborhood Aggregator shall support prioritized message processing 1

253 Outage Detection/Management FR 2

254 Testing & Diagnostics FR 1

255 Network Management NFR 1

256 Comms Performance/Reliability NFR 1

257 Data Center Aggregator Metrology FR 1

258 Data Center Aggregator Metrology FR 1

Premise Gateway shall be able to securely route messages between the utility to and from customer Generation Control Equipment which is part of the customer's Building Management System (BMS) including:1. increase/decrease demand2. increase/decrease generation3. increase/decrease VARs Any of these requests may specify a time period for which to perform the operation, or an "undo" command. This is the "generation dispatch" functionality.Premise Gateway shall be able to differentiate between multiple individual generators at a customer site Premise Gateway shall be able to log messages sent between the AMI communications network and the meter or HAN connected devicesPremise Gateway shall be able to send its message log information to the Data Center Aggregator according to a regular schedule (configurable frequency) or on demand

Premise Gateway log shall be configurable to immediately report certain messages/events (based on message/event type) to the Data Center Aggregator in real-time upon being recorded

Neighborhood Aggregator

Neighborhood Aggregator shall be time-synchronized with an external time source at least once per day.

Neighborhood AggregatorNeighborhood Aggregator

Neighborhood Aggregator shall monitor and log the duration of power outages of all meters associated with the neighborhood aggregator (for later statistical analysis)


Neighborhood Aggregator shall permit remote:1. status report (up / down)2. diagnostics3. link status report4. communications event log retrieval


Neighborhood Aggregator shall be modular to permit change of network communications technology.


Neighborhood Aggregator shall be able to operate for extended periods in the absence of grid power (at least 8 hours)Data Center Aggregator shall be able to remotely configure the meter's recording interval length (to all interval lengths supported by the meter)Data Center Aggregator shall have access to channel multipliers, meter multipliers, unit of measure per channel, and other basic meter info





259 Data Center Aggregator Internal Clock FR 1

260 Data Center Aggregator Internal Clock FR 1

261 Data Center Aggregator Default Read Schedule FR 1


263 Data Center Aggregator Default Read Schedule FR 1264 Data Center Aggregator Default Read Schedule FR Data Center Aggregator shall have the ability to place meters into read schedule groups 1



267 Data Center Aggregator Default Read Schedule NFR 2






Data Center Aggregator shall validate the internal clock time for meters and all other field communications components at least once per day and synchronize it with system time if the difference exceeds a configurable tolerance. Data Center Aggregator shall log an event message for each meter if the daily time validation detects meter time that is greater than 120 seconds out of synch with system time source.Data Center Aggregator will collect all interval data and logs from field and premise Communications Network components (incl Premise Gateways) and all meters at a configurable frequency, but at least once per dayData Center Aggregator shall have the ability to remotely configure (set/update/cancel) meter's default read schedule for a specified or on-going duration. (for all AMI meters)Data Center Aggregator shall receive and log the meter's acknowledgement of successful default read schedule setup

Data Center Aggregator shall have the ability to identify read groups that (1) consistently fail to meet targeted schedule read times and (2) consistently retrieve all reads within scheduled time parameters

Data Center Aggregator shall be able to automatically rebalance default meter read schedules on a periodic basis in order to balance/optimize the overall meter read schedule performance. Rebalancing shall be accomplished by automatically selecting meters from "over" committed groups and reallocating them to one or more "under" committed groups for maximum default read efficiency Data Center Aggregator shall receive acknowledgement of a read schedule setup from the meter within 15 minutes of the setup event being sent.Data Center Aggregator shall record the results of read group analysis and the resulting actions takenData Center Aggregator shall successfully collect interval and all log data for previous day (midnight to midnight) from at least 99% of meters, each day by 6 a.m.

Data Center Aggregator scheduled read data shall be able to be transmitted directly to recipients with real-time requirements within 60 seconds of the read being sent from the meter.

Data Center Aggregator shall be able to issue a re-read request for all meters that have failed to report their default read (i.e. mass on demand read - up to 10% of total AMI meter population). Data Center Aggregator shall be able to optimize a mass on demand read to minimize the impact on system performance






274 Data Center Aggregator Non-Default Read Schedule FR 1

275 Data Center Aggregator Non-Default Read Schedule FR 2

276 Data Center Aggregator Non-Default Read Schedule NFR 1




280 Data Center Aggregator On Demand Reads FR 1



283 Data Center Aggregator On Demand Reads NFR 1

284 Data Center Aggregator On Demand Reads NFR 2

285 Data Center Aggregator Remote Disconnect/Reconnect FR 1



Data Center Aggregator shall be able to request and receive results for an automatically initiated mass on demand read within 2 hoursData Center Aggregator shall have the ability to remotely set a non-default meter read schedule(s) at a configurable frequency of greater than once per day but not more frequently than the meter's recording interval.Data Center Aggregator shall log details of all non-default meter read schedules including the source (system/party) of each non-default schedule. Data Center Aggregator shall support collection of interval data from meters at a frequency as often as the meter's configured interval length Data Center Aggregator shall collect interval data from AMI meters according to its configured non-default read schedule within 1 minute of schedule 98% of the time and within 2 minutes 2% of the time

Data Center Aggregator shall be able to support the following expected non-default read schedule levels: 20% of the meters will have a collection frequency of 1 hour (35 times per year for 6 hour durations) and 6% of the meters will have a collection frequency of 15 min. (35 times per year for 6 hour durations)For reads more frequent than daily reads, Data Center Aggregator shall identify missing data within 2 read intervals (elapsed time) Data Center Aggregator shall be able to issue an on-demand read request initiated from authorized SCE systemsData Center Aggregator shall be able to retrieve logs on demand from meters and all communications network componentsData Center Aggregator shall be able to automatically issue a remote meter test upon on-demand read request failure.Data Center Aggregator shall be able to issue and receive results for on-demand read requests from the meter within 30 seconds 80% of the time and within 60 seconds 99% of the time.

Data Center Aggregator shall be able to retrieve logs on demand from meters and all communications network components (incl Premise Gateways) within 60 seconds of the requestData Center Aggregator shall be able to schedule, reschedule and cancel remote disconnect/reconnect/service limiting events for future dates/times.Data Center Aggregator shall enable remote disconnect/reconnect/limiting events to be sent and executed on demandData Center Aggregator shall support automatic disconnect/reconnect/limiting events based on configurable rules (e.g. scheduling, customer class, extreme weather, tariff)







290 Data Center Aggregator Remote Disconnect/Reconnect NFR 1




294 Data Center Aggregator HAN FR 1

295 Data Center Aggregator HAN FR 1

296 Data Center Aggregator HAN NFR 2

297 Data Center Aggregator Load Control FR 1

298 Data Center Aggregator Distributed Generation Support FR 3

299 Data Center Aggregator Prepayment Service FR 1


Data Center Aggregator shall support sending notification messages to an in-home/business device informing customer of impending/scheduled disconnect or service limiting event (including date and time of scheduled event)Data Center Aggregator shall 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)Data Center Aggregator shall support delivery of Disconnect/Reconnect event messages to the meter that are persistent until the meter acknowledges event status or the event is ended.

Data Center Aggregator shall support transmitting remote disconnect/ reconnect/ limiting commands to the meter and the command be executed within 60 seconds of the request being sent.

Data Center Aggregator shall automatically retry transmitting disconnect/reconnect events to the meter if it does not receive an acknowledgement within 60 seconds of the original transmission. Data Center Aggregator shall allow a reconnect event to occur following a disconnect event only after a configurable amount of time (e.g. at least 1 to 2 minutes) has elapsed since the disconnect event.

Data Center Aggregator shall require unique IDs for HAN-connected customer equipment to enable remote communications between the utility or third parties and specific customer equipment Data Center Aggregator shall be able to remotely request self-test of customer equipment (If supported by customer equip)Data Center Aggregator shall enable customer notification of communication status with HAN devices within 30 minutes of enrolling them. Expected value is 2 minutes 90% of the time. Data Center Aggregator shall support Advanced Load Control functionality and the communication of load control events which originate from a Load Control SystemData Center Aggregator shall support dispatching signals to control certain types of customer generation and collect data from the customer at the next regular reading interval (as opposed to immediately)Data Center Aggregator shall support sending scheduled prepayment events to the meter at least 24 hrs prior to the start of the event, if the event schedule start time is more than 24hrs into the future, and immediately if the event start time is in less than 24 hrs

When the customer's estimated remaining prepay time reaches a configurable threshold (e.g. 48 hrs) remaining until the account reaches zero, Data Center Aggregator shall be able to automatically begin collecting interval data from the meter at the same frequency as the meter's recording interval length








304 Data Center Aggregator Outage Detection/Management FR 1305 Data Center Aggregator Outage Detection/Management NFR Data Center Aggregator shall report outage/restoration information to OMS within 1-5 min. 2

306 Data Center Aggregator Tamper Detection FR 1

307 Data Center Aggregator Power Quality FR 2

308 Data Center Aggregator Power Quality NFR 3

309 Data Center Aggregator Power Quality NFR 3

310 Data Center Aggregator Gas/Water Utility Meters FR 2311 Data Center Aggregator Gas/Water Utility Meters FR Data Center Aggregator shall be able to request water/gas meter reads on demand 2

312 Data Center Aggregator Gas/Water Utility Meters FR 3

313 Data Center Aggregator Gas/Water Utility Meters FR 2314 Data Center Aggregator Gas/Water Utility Meters FR Data Center Aggregator shall identify water/gas meters that did not send requested read data 2




When the customer's estimated remaining prepay time reaches a configurable threshold (e.g. 48 hrs) remaining until the account reaches zero, Data Center Aggregator shall be able to transmit calculated prepayment balance information to the Premise Gateway at the same frequency as the meter's recording interval lengthData Center Aggregator shall be able to schedule multiple prepayment event schedules for the same service location Data Center Aggregator shall not allow prepayment schedules to co-exist that overlap or duplicate schedules for the same service locationData Center Aggregator will interface with the OMS to provide outage/ restoration information from the AMI system for many meters over a short period of time. System shall be 99% accurate in reporting outages so that repair crews can be dispatched to the correct locations

Data Center Aggregator shall collect and log all tamper detection events sent by meters (logged with event timestamp, tamper event type, and meter ID)Data Center Aggregator shall retrieve Power Quality data at a greater frequency than the history available in the meter (i.e. to ensure no lost data)Data Center Aggregator shall enable harmonics data collection that follows IEC 61000-4-30 (Class B and IEEE 519) standardsData Center Aggregator shall enable harmonics level to be measured and stored; shall range up to the 9th or 15th. Data Center Aggregator shall have the ability to collect reads from gas/water meters at least once per day.

Data Center Aggregator shall support collection of interval read data from gas/water meters (if the water/gas meter is setup for interval reads)Data Center Aggregator shall be able to receive two reads (corrected and uncorrected) from Gas Meters.

Data Center Aggregator shall be able to collect non-usage data (i.e. battery level, temp, pressure, etc.) along with usage data from gas/water meters if available.Data Center Aggregator shall be able to send commands to gas/water meters for remote disconnect/reconnect (for those gas/water meters equipped to handle such commands)Data Center Aggregator shall support all AMI scheduling, diagnostic, logging, reporting and prioritization functionality for Gas/Water meters to the extent that the gas/water meter supports those functions.







320 Data Center Aggregator 3rd Party Messaging FR 3








328 Data Center Aggregator 3rd Party Messaging NFR 3




Data Center Aggregator shall be able to interface with gas/water meters via the Premise Gateway at the gas/water meter's premise location or via any other Premise GatewayData Center Aggregator shall accommodate self registering and non-self registering water/gas metersData Center Aggregator shall support routing authorized/authenticated third party messages between external third parties and the Premise Gateway for the purpose of monitoring or controlling customer devices connected to a HAN

Data Center Aggregator shall support the ability to remotely provision the Premise Gateway to accept third party messages from specific, contractual, HAN devices. (i.e. for security purposes)Data Center Aggregator shall generate an alarm message when unauthorized third party messaging attempts exceed the rate of 10 per hour.Data Center Aggregator shall allow for third party messages for monitoring or control to be able to be prioritized by the third partyData Center Aggregator shall be able to prioritize between third party messages and utility messages, dependent on their urgency (configurable)Data Center Aggregator shall send and receive third party messages with a response time that is configurable based on contract tier levels agreed to by SCE, customers, and third parties.

Data Center Aggregator shall allow for multiple configuration levels (by customer) for the number/frequency of messages third parties are permitted to send to and receive to/from Premise Gateways (based on availability of multiple third party messaging contract tier levels to govern)If the third party exceeds the configured number of messages allowed, Data Center Aggregator shall reject further third party messages and send third party a warning message advising that the limit has been exceededData Center Aggregator will support third party messaging 24 hours per day 7 days a week with an allowance for down time for maintenance

Data Center Aggregator shall log receipt of all third party messages received with the message ID, destination ID and date/time received (including those from the customer devices) and shall log all transmissions sent back to the third party. This includes logging of authorized and unauthorized message attempts.Data Center Aggregator shall notify the third party when a third party message is undeliverable to the customer's Premise Gateway (Possible failure reasons include:exceeded limit of messages, system congestion, etc.)Data Center Aggregator shall notify the third party within 15 minutes when a third party message is undeliverable to the customer's Premise Gateway






333 Data Center Aggregator Meter Display - Config FR 2334 Data Center Aggregator Meter Display - Config FR Data Center Aggregator shall log the meter display reset request results. 2

335 Data Center Aggregator Local Display NFR 1



338 Data Center Aggregator Testing & Diagnostics FR 1




342 Data Center Aggregator Testing & Diagnostics FR Data Center Aggregator shall be able to remotely test communications with external third parties. 3




Once received, the Data Center Aggregator shall deliver inbound 3rd Party messages to the Premise Gateway and outbound messages back to the 3rd Party in 60 seconds or less, subject to message prioritizationData Center Aggregator shall be able to send remote meter display configuration requests (individual display attributes) to the AMI meter, on demand, based on customer configuration choices

Data Center Aggregator shall be able to routinely (e.g. daily, hourly) transmit energy related information to premise display device within 1 minute of sending 99% of the time and within 30 minutes of sending 1% of the timeData Center Aggregator shall be able to routinely (e.g. daily, hourly) transmit energy related information to other customer devices (e.g. cell phone, pager, satellite/cable stations, etc.) within 1 minute of sending 99% of the time and within 30 minutes of sending 1% of the time Data Center Aggregator shall be able to receive and process requests from other utility systems (e.g. CSS) to send text messages to customer devices (e.g. cell phone, satellite/cable stations, etc.) within 60 seconds of the original request.

Data Center Aggregator shall provide comprehensive remote testing and diagnostic capabilities for each system component (communications and meters) based on a (periodic) schedule or on demand. Remote testing and diagnostic alarm messages are to be considered high priority. Data Center Aggregator shall be able to remotely test meters for communications status, energized status, load side voltage and switch status on-demand. Data Center Aggregator shall be able to remotely detect network communications problems including loss of redundant communications pathways, diminishing signal strength, repeated delays in reporting etc.Data Center Aggregator shall be able to remotely test communications with customer devices attached to a HAN.

Data Center Aggregator shall have the ability to identify the probable cause of a communications failure within the AMI communications network.

Data Center Aggregator shall provide mechanisms for remotely correcting system/component problems, which at a minimum shall include the ability to remotely recycle (or restart) a component.Data Center Aggregator shall log the results of all remote testing and diagnostics activities and any automatic actions taken based on those results








349 Data Center Aggregator Testing & Diagnostics NFR 1

350 Data Center Aggregator Testing & Diagnostics NFR 1

351 Data Center Aggregator Event/Message Management & Logs FR 1

352 Data Center Aggregator Event/Message Management & Logs FR 1353 Data Center Aggregator Event/Message Management & Logs FR Data Center Aggregator shall support a cancellation capability for scheduled events 1354 Data Center Aggregator Event/Message Management & Logs FR Data Center Aggregator shall not allow scheduling of conflicting events 1




Data Center Aggregator shall make the results of all received alerts and remote testing and diagnostic results available to authorized IT systems (e.g. MDMS, CSS, Work Order Tracking, etc.)Data Center Aggregator shall have configurable alert levels and notifications based on the severity of a problem detected and the number of endpoints affected.

Data Center Aggregator shall be able to classify specific testing/diagnostic results to either require or not require human intervention (configurable) in the determination of issuing trouble reports

Data Center Aggregator shall detect if any network components are not responding within the following intervals based on the number of meters affected. (Estimate only - Different network topologies will result in different values.)A) < 200 meters - next read.B) 200 - 1000 meters - within 6 hoursC) 1000 - 5000 meters - within 1 hourD) 5k - 20k meters - within 15 minutes.E) 20k - 50k meters - within 1 minute. Data Center Aggregator shall be able to remotely perform a meter, communications device, or HAN test (testing parameters shall be configurable) and receive results within 60 seconds

Data Center Aggregator shall be able to send and receive various types of event messages (e.g. demand response, load control, disconnect/reconnect, prepayment, etc.) to and from all AMI components (e.g. meters, communications devices, & HAN-connected devices) either directly or indirectly.Data Center Aggregator shall be able to send event messages to AMI components that contain the current (at a minimum) date/time, event type/code, event schedule date/time (start and end), priority, and hourly or time-of-use pricing (if applicable)

Data Center Aggregator shall be able to send alert messages to AMI meter and/or display device at a configurable frequency (e.g. each hour prior to disconnect)

All event messages sent by the Data Center Aggregator shall be able to be acknowledged. For synchronous requests, the target component will respond with the result of the request. For asynchronous requests, the target component will acknowledge receipt of request and will asynchronously notify Data Center Aggregator of results.Data Center Aggregator shall be able to communicate alpha/numeric informational messages to the meter and/or other customer display devices















368 Data Center Aggregator Installation FR 1369 Data Center Aggregator Installation FR Data Center Aggregator shall synchronize the meter's internal clock upon installation. 1

370 Data Center Aggregator Installation FR 1

Data Center Aggregator shall be able to communicate informational messages in English or Spanish language, configurable by customer preference

Data Center Aggregator shall be able to prioritize all messages (event and informational) that are sent to the meter, customer's HAN devices (display, load control, etc.), and other customer designations such as e-mail, cell phones, etc. (customer display devices must meet SCE standards)

Data Center Aggregator will support multiple message prioritization schemes. Each scheme will support prioritizing and limiting messages (event and informational) by end device, message type, source and destination. The priority and limits by class, source and destination shall be configurable by the utility.

Data Center Aggregator shall enable alerting when configured messaging limitations are exceeded. Data Center Aggregator shall ensure that utility messages always take priority over third party communicationsData Center Aggregator shall log all messages (event and informational) sent to and received from all AMI components (meters, communications devices, & HAN-connected devices) with the message date/time, event/message type identifier, and source/target(s) identifierData Center Aggregator shall log each instance when a event message has been sent to an AMI component, but no (anticipated) receipt is received within the configured time frame.In the event that an event message is not acknowledged (if expected), Data Center Aggregator shall be able to automatically retry the operation. This frequency and timing of this functionality shall be configurable, dependent on the event message type and device target.

For bulk operations (e.g. daily non pay disconnect events), Data Center Aggregator shall support leveling of event messages so as to minimize impacts to the system and support personnel. For curtailments, emergency or otherwise, this may include the capability for broadcast messages keyed by rate class, geography, tariff etc.

Data Center Aggregator shall be able to schedule event messages to be delivered to the meter, display device or control equipment to ensure the utility meets regulatory requirements (e.g. day ahead event by 3:00 pm of the previous day, day of event by 10am of day and real-time events on-demand) Data Center Aggregator shall be able to detect installation of new meters onto the Communications network, and shall also detect when existing AMI meters have been removed

As meters self-register, Data Center Aggregator shall initially place them into an unscheduled read group





371 Data Center Aggregator Network Management FR 1

372 Data Center Aggregator Network Management FR 1

373 Data Center Aggregator Secure Communications FR 1




377 Data Center Aggregator Comms Performance/Reliability NFR 1



380 Data Center Aggregator Comms Performance/Reliability FR Data Center Aggregator shall automatically select from redundant communications paths if available 1

381 Data Center Aggregator Comms Performance/Reliability FR 1



Data Center Aggregator shall be able to provide updated reports available at least once a day as well as on demand that contain key diagnostics and statistics from all AMI meters, devices, and field communication network elements. Reports shall include (at a minimum) meter read status reports, event/transaction status reports, trouble reports, and meter additions/removalsData Center Aggregator shall be modular to permit change of network communications technology. Data Center Aggregator shall provide a secure communication mechanism and configurable authentication capabilities to protect against Spoofing, Man in the Middle, replay attacks, etc.

Data Center Aggregator shall include an intrusion prevention system that monitors communications, infers when an attack is occurring and notifies components of the AMI system to take action. It may also take direct action to block malicious traffic and malformed messages.

Data Center Aggregator shall authorize and authenticate all communications on the AMI network (utility and 3rd party messaging) and shall reject and log messages received from unauthorized systems/devices. This includes messages being transported on: a. WAN - Wide area network b. HAN - Home area network c. NAN - Neighborhood area network Data Center Aggregator shall correlate meter read failures with output of an intrusion prevention system Data Center Aggregator shall provide full high availability and backup/recovery for all of the head end system hardware. 99.995% availabilityData Center Aggregator shall be able to communicate event messages to 500,000 AMI meters within 3 seconds for 99.95% of the meters, and within 10 seconds for 1% of the meters.Data Center Aggregator shall be able to process 50,000 (or 1% of the AMI meter population) on-demand requests per day for interval data (not including the pre-scheduled meter data collection schedules) at the customer's request/initiation via the utility website

Data Center Aggregator shall perform data flow control after a communication or power outage to prevent resources from being overloaded. Critical messages exchanged between the Data Center Aggregator and premise and/or field devices will be delivered in 10 seconds 80 percent of the timeHigh priority messages exchanged between the Data Center Aggregator and premise and/or field devices will be delivered in one minute 80 percent of the time







386 Data Center Aggregator Systems Integration NFR 1

387 Data Center Aggregator Systems Integration FR 1


389 Data Center Aggregator Systems Integration NFR 1





394 Gas/Water Utility Meters FR 2

Medium priority messages exchanged between the Data Center Aggregator and premise and/or field devices will be delivered in five minutes 80 percent of the timeLow priority messages exchanged between the Data Center Aggregator and premise and/or field devices will be delivered in fifteen minutes 80 percent of the timeData Center Aggregator shall be able to support common information model (CIM) structures, commercial EAI interfaces, and/or service oriented integration patterns for IT systems integration with Meter Data Management System (MDMS) and other enterprise IT systemsData Center Aggregator shall be able to receive, log and process requests (e.g., prepayment schedules, connect, disconnect, demand limit request, meter tests) from other utility systems (e.g., CSS)Data Center Aggregator shall be able to transmit all data received from the meters, communications devices, and customer/HAN devices (incl. load control devices) to the MDMS (e.g. usage, logs, alerts, receipts, prepayment balances, etc.)Data Center Aggregator shall be able to transmit specific event and account information to authorized systems (e.g. Customer Service Database) within 60 seconds of receipt from the meter, display device or control equipment Data Center Aggregator shall provide a means to interface with utility network management and outage management systems to correlate detected system issues to reduce the generation of extraneous trouble reports. Data Center Aggregator shall be able to provide meter's energized status and disconnect switch status (on/off/limit level) to Call Center (and other) IT SystemsData Center Aggregator shall be able to provide to Call Center (and other) IT Systems the same information that the customer can see on the meter / in home display

Data Center Aggregator shall be able to notify other enterprise systems or organizations which subscribe to meter data when a configurable percentage of meters cannot be read after a recovery attempt. Examples of enterprise subscribers to meter data include, but are not limited to:1. GCC2. Tariffs, Programs and Services3. Customer Call Center4. Energy Supply and Marketing5. Revenue Services Organization6. Telecomm Control Center

System Management Console

System Management Console shall manage water/gas meter population including a unique, configurable read schedule







397 Software/Firmware Upgrades FR 1


399 Software/Firmware Upgrades FR System Management Console will prevent incompatible hardware/software (firmware) combinations 2




403 Tariff/Rate Configuration FR 1

404 Outage Detection/Management NFR 2


406 Distributed Generation Support NFR 2

407 Event/Message Management & Logs FR Communications Network will support a secure, routable, utility extensible message format 1

408 Memory/Storage NFR 1

409 Power Supply NFR 1

410 Distributed Generation Support NFR 3


System Management Console shall maintain a meter reading schedule for multiple service types at one premise


System Management Console shall manage read frequency of water/gas meters to enable maximum battery life.


System Management Console will provide a mechanism for remote upgrades of meter software/firmware. Local, on-site upgrades will also be possible.


System Management Console shall co-ordinate software/firmware upgrade scheduling, including identifying which meters need to be upgraded.

System Management ConsoleSystem Management Console

System Management Console shall schedule upgrades to new software/firmware versions to minimize the number of intervals affected by an upgrade


System Management Console shall have the option of requiring immediate acknowledgement of the status of firmware upgrade from the meter. If immediate acknowledgement is not requested from the meter, the status is sent with the next scheduled read.


System Management Console shall compare pre-software/firmware upgrade meter data and status with post-upgrade status to ensure that upgrades are successful


System Management Console shall be able to transmit customer specific rate information (e.g. kWh pricing, TOU period time frames) to the AMI meter


System Management Console shall be capable of communicating outage/restoration information of 200 meters simultaneously and instantaneously (5 sec).


System Management Console shall be 99% accurate in reporting outages so that repair crews can be dispatched to the correct locations


System Management Console shall be able to remotely program the meter for net energy metering and receive acknowledgement within 5 minutes or request

Communications Network


Communications Network components storing payload data shall utilize non-volatile memory for storing and retaining this information. Data storage durations must be sufficient to meet durations for the class of data being stored.


Communications Network components, located outside of a substation, shall be capable of connecting to a main voltage ranging from 120V to 240V. Equipment located on street secondary must be capable of operating on 120/240 volt service.


Communications Network shall support at least 500,000 distributed generation customers. (i.e. via additional meters)





411 Distribution Functions NFR Communications Network shall support 50,000 Distribution Automation Nodes 3







418 Field Tool Installation FR 1

419 Field Tool Local Connectivity FR 1

420 Field Tool Meter Management FR 1





Communications NetworkCommunications Network

For outage notification to be useful, Communications Network shall be at least as reliable as the power system it is monitoring and reporting on.


Communications Network components shall comply with FCC regulations (indicated by appropriate documentation)


Communications Network shall be hardened to operate in a noisy electrical environment. Vendor shall provide their certifications for Electromagnetic Compatibility (e.g. ANSI C12.20, IEC 61000-4-2, etc.)


Communications Network components shall have a failure rate of less than 0.5% per annum over the required operating life of the system (15 years) and less than 1.00% per annum during the extended operating life of the system (years 16-20)


Communications Network and all features shall be available 24 hours per day 7 days a week with an allowance for down time for maintenance and will support a reliability of 99.99%


The overall reliability of the Communications Network shall be greater than 99% (This is based on the current performance of SCE's existing communication systems and number of enrolled customers in demand response programs) Wireless Field Tool shall be able to communicate directly with the meter to load meter programs and set meter configurations through both wireless and optical port communications

Wireless Field Tool shall support secure local download of all meter and communications data and logs stored in meter memory (e.g. register read, demand, interval data, logs, voltage, PF, etc.)Wireless Field Tool shall provide work order functionality to allow for investigation, resolution, and initiation (for as-found problems identified in field) of trouble reportsWireless Field Tool shall be capable of testing the AMI communications interface on the meter as well as the HAN interface on the meter

Wireless Field Tool (or other mechanism) shall be able to uniquely identify meters by their physical location (i.e. LAT/LONG) and provide this information to a meter management system. Must be able to specify unique location identifier for each meter when multiple meters are at the same LAT/LONG

Wireless Field Tool shall be able to support multiple applications (e.g. work order management, meter management/configuration, communications network testing/management, etc.) Wireless Field Tool shall allow its user to seamlessly move back and forth between multiple applications running simultaneously, without exiting the applications





425 Field Tool Network Management FR 2


427 Distribution Functions FR 2

428 Distribution Functions FR 2

429 Distribution Functions NFR Distribution Automation Nodes shall be able to operate off of voltages between 110 and 480 volts. 2

430 Distribution Functions NFR 2

Wireless Field Tool shall be able to report results of the AMI communication network connectivity and strength to its user and relevant back office systemsUpon completion of trouble reports, Wireless Field tool shall automatically upload all relevant information to the appropriate IT system(s)

Distribution Automation Nodes

Distribution Automation Nodes shall provide an interface between the AMI communications network and distribution automation equipment such as, but not limited to: Remote Fault Indicators, Remote Controlled Switches, Capacitor Bank Controllers, Reclosers, etc

Distribution Automation Nodes

Distribution Automation Nodes shall be able to exchange information and commands with other elements of the AMI system including other distribution automation nodes, neighborhood aggregators, meters, premise gateways, load control devices and enterprise systems (via the Data Center Aggregator)

Distribution Automation NodesDistribution Automation Nodes

Some Distribution Automation Nodes shall be able to operate for extended periods in the absence of grid power (at least 8 hours)

AMI Requirements Report Prototype - We are down for …€¦ · XLS file · Web view ·...

Documents

Transcript of AMI Requirements Report Prototype - We are down for …€¦ · XLS file · Web view ·...