Smart Metering Infrastructure (SMI)

Transcription

1 Smart Metering Infrastructure (SMI) Cover Page Customer Service Functions Please note: The following methodology has been utilised to analyse the customer service functions nominated below: Function #7.6: Load management through a controlled load contactor Function #7.7: Supply Contactor operation Functions #7.8: Supply Capacity Control Function #7.9: HAN using Open Standard Function #7.10: Quality of Supply and other Event Recording Function #7.12: Remote Service Checking Each customer service function has been (or will be) analysed individually. As there is no critical mass of historical practices with these functions, the analysis commences with a review of future state activities (that is, an expression of a future scenario based on possible activities). The process maps for these functions will be updated during subsequent BPPWG workshops. Note that this slide pack has been adjusted to accommodated SMI Functional Specification v0.26 BPPWG process maps customer services v03 This version dated 05 July 2010 Slide 1

2 Customer service Principles: The DNSP is allowed to sell load management. How will the legacy from Ripple Control be managed?? A mechanism is required to facilitate: A. Creation and adjustment of meter settings B. Sending commands to the Smart meter C. Retrieving events from the SMI The operation of the mechanism should be made available to nominated parties (based on policy principles and service levels); A Retailer will sell all load management services to customers (other than emergency SCC); A DNSP will offer UFLS and Boost services to customers, either through Retailers via the network tariff or directly to customers; A Retailer can request a customised network tariff for the load management service being offered. A Retailer can request that a customer be moved from the DNSP allocated Network Tariff to a different Network Tariff (Note that some Distributors consider this point to be BAU and hence out of scope, whilst other Distributors doubt whether this principle is BAU) There should be a new NEM Procedure for this CS function (AGL#3.2). Service request should be real time and automated; service level very high (AGL#3.3, 3.4). Service requests should be able to be scheduled as well as queued for action via B2B (AGL#3.5). Performance and service level requirements of this function should be carefully chosen to match the objectives of the smart meter program (AGL#3.8). FRMP requires reason for failure to carry out FRMP request to be provided either immediately or the next business day along with the metering data readings. That is, a FRMP must be notified of a request that has failed to be delivered remotely to a Smart Meter (AGL process map). Need to establish consistency in terminology between MSATS procedures and B2B procedures A single service request must be able to record multiple actions (and their sequence) for execution at a single connection point (AGL). A single service request must be able to record group commands (and their sequence) for execution at multiple connection points (AGL). There needs to be a priority order for different types of messages, with the possibility that 2 or more message types may have the same priority (AGL). The status of a dedicated load contactor or relay must be provided to the FRMP within a reasonable timeframe (after a request to operate that contactor or relay has been initiated by that person) before the FRMP can initiate a second request on that contactor or relay (AGL) Add to principles: The service process must contain NO MANUAL DECISION POINTS (AGL). The commands / processes must allow for group as well as single meter targets (AGL). Separate Group ID ranges must be available for different roles including at least FRMP, DNSP, MDP (AGL). Meter Event log must be published in full to retailers (next day) along with the interval meter data (AGL). Function Load Management through a controlled load contactor #7.6 Other points for further consideration: A DNSP will have the ability to construct network that reflect a range of possible settings for load management services. All load control services being requested will be assigned a logical device number regardless of the physical device properties. PRINCIPLES That is: The FRMP has an interest in: o Default Load Control Schedule o Special Day operation o Priority override operation o Loss of supply load switching o UFLS operation (status only) o Demand limit o Load cycling o Boost mode The DNSP has an interest in: o Emergency Supply Capacity Control o UFLS operation o Boost mode (status only) Add to principles: <<Operation of Boost feature.to be determined>> (AGL). FRMP must be notified if a request could not be fulfilled. The notification is to be from a standard list and conveyed in accordance with an agreed timeline (AGL). A standard process for the reissue of the FRMP request should be available (AGL) Nominated meter settings can only be modified to included restrictions within network tariffs (GRAPL margin comment T2) (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 2 x

3 Customer service Function Load Management through a controlled load contactor #7.6 Principles: PRINCIPLES (realigned to Role Requirements) FRMP: 1. A Retailer will sell all load management services to customers (other than emergency SCC); 2. A Retailer can request a customised network tariff for the load management service being offered. 3. A Retailer can request that a customer be moved from the DNSP allocated Network Tariff to a different Network Tariff (Note that some Distributors consider this point to be BAU and hence out of scope, whilst other Distributors doubt whether this principle is BAU) 4. Service request should be real time and automated; service level very high (AGL#3.3, 3.4). 5. Service requests should be able to be scheduled as well as queued for action via B2B (AGL#3.5). 6. FRMP requires reason for failure to carry out FRMP request to be provided either immediately or the next business day along with the metering data readings (AGL process map). 7. A single service request must be able to record multiple actions (and their sequence) for execution at a single connection point (AGL). 8. A single service request must be able to record group commands (and their sequence) for execution at multiple connection points (AGL). 9. There needs to be a priority order for different types of messages, with the possibility that 2 or more message types may have the same priority (AGL). 10. A FRMP must be notified of a request that has failed to be delivered remotely to a Smart Meter (AGL). 11. The status of a dedicated load contactor or relay must be provided to the FRMP within a reasonable timeframe (after a request to operate that contactor or relay has been initiated by that person) before the FRMP can initiate a second request on that contactor or relay (AGL) 12. The service process must contain NO MANUAL DECISION POINTS (AGL). 13. The commands / processes must allow for group as well as single meter targets (AGL). 14. Separate Group ID ranges must be available for different roles including at least FRMP, DNSP, MDP (AGL). 15. Meter Event log must be published in full to retailers (next day) along with the interval meter data (AGL). 16. <<Operation of Boost feature.to be determined>> (AGL). 17. FRMP must be notified if a request could not be fulfilled. The notification is to be from a standard list and conveyed in accordance with an agreed timeline (AGL). 18. A standard process for the reissue of the FRMP request should be available (AGL). DNSP: 1. The DNSP is allowed to sell load management. How will the legacy from Ripple Control be managed?? 2. A DNSP will offer UFLS and Boost services to customers, either through Retailers via the network tariff or directly to customers; Common: 1. Both the FRMP and DNSP will be able to sell load management services (PE) 2. A mechanism is required to facilitate: A. Creation and adjustment of meter settings B. Sending commands to the Smart meter C. Retrieving events from the SMI 3. The operation of the mechanism should be made available to nominated parties (based on policy principles and service levels); 4. There should be a new NEM Procedure for this CS function (AGL#3.2). 5. Performance and service level requirements of this function should be carefully chosen to match the objectives of the smart meter program (AGL#3.8). 6. Need to establish consistency in terminology between MSATS procedures and B2B procedures 7. Nominated meter settings can only be modified to included restrictions within network tariffs (GRAPL margin comment T2) (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 3 x Same points

4 SPAN comments (1) Function Load Management through a controlled load contactor #7.6 PRINCIPLES Move to a principle in the Role Requirements Paper SPAN suggests (23/4/10) - DNSP offer load management services to the market via Network Tariffs Currently based on: being discussed with NSSC (next * the customers agreed premise metering and load management equipment; meeting 21/4/10) * the agreement between the AER and Retailers regarding specific Network Tariffs that align with Retail product offerings; That is: Principles: and The FRMP has an interest in: Will * UFLS, the DNSP and be emergency allowed to SCC sell can load be management?? used irrespective of which Network Tariff is applied(clc or HAN)?? - The If AER yes, approves how will the all network legacy from tariffs Ripple available Control to DBs be in managed?? accordance with the NEL that requires cost reflectivity, proper price o Default Load Control Schedule signals If no, will how encourage will load customers management to make transition the appropriate to the retailer? decisions with respect to their energy use. o Special Day operation - Network A MECHANISM tariffs are IS REQUIRED developed TO in consultation FACILITATE: with AER; o Priority override operation - DNSP s cannot form Network Tariffs in consultation with individual Retailers, rather Retailers should liaise with the AER; o Loss of supply load switching A. Creation and adjustment of meter settings - Retailers can request a change in Network Tariff where it is linked to physical changes in the connection point configuration o UFLS operation (status only) B. Sending commands to the Smart meter i.e. demand management or embedded generation; and o Demand limit - Smart C. Retrieving Meters will events introduce from the remotely SMI configurable demand management, so the industry will have more network tariff changes o Load cycling and The require operation flexible of network the mechanism tariff arrangements should be made to cater available for remote to nominated configuration parties changes. (based on policy principles and Agreed o to Boost resolve mode in Role service levels); SPAN suggests remove point Requirements The LNSP analysis has an interest in: A Retailer will sell all load management services to customers (other than emergency SCC); o Emergency Agreed Supply to Capacity resolve Control in Role A DNSP will offer UFLS and Boost services to customers, either through Retailers via the network tariff or directly SPAN suggests remove point o UFLS operation Requirements analysis to customers; SPAN suggests remove point o Boost mode (status only) A Retailer can request a customised network tariff for the load management service being offered. Agreed to resolve in Role A Retailer can request that a customer be moved from the DNSP allocated Network Tariff to a different Requirements analysis Network Tariff (Note that some Distributors consider this point to be BAU and hence out of scope, whilst other Distributors doubt whether this principle is BAU) There should be a new NEM Procedure for this CS function (AGL#3.2). SPAN suggests remove point, requirement not principle Agreed to resolve in Role Service request should be real time and automated; service level very high (AGL#3.3, 3.4). Requirements analysis Service requests should be able to be scheduled as well as queued for action via B2B (AGL#3.5). Performance and service level requirements of this function should be carefully chosen to match the objectives of the smart meter program (AGL#3.8). FRMP requires reason for failure to carry out FRMP request to be provided either immediately or the next business day along with the metering data readings (AGL process map). Need to establish consistency in terminology between MSATS procedures and B2B procedures The number of load contractors and relays to be included in a Smart Meter will be at the discretion of the Minister when determining the conditions of the mandatory rollout. Other points for further consideration: A DNSP will have the ability to construct network that reflect a range of possible settings for load management services. All load control services being requested will be assigned a logical device number regardless of the physical device properties. SPAN suggests remove point Agreed to resolve in Role Requirements analysis (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 4 x

5 AGL comments (1) Principles: Will the DNSP be allowed to sell load management?? If yes, how will the legacy from Ripple Control be managed?? If no, how will load management transition to the retailer? A MECHANISM IS REQUIRED TO FACILITATE: A. Creation and adjustment of meter settings B. Sending commands to the Smart meter C. Retrieving events from the SMI The operation of the mechanism should be made available to nominated parties (based on policy principles and service levels); A Retailer will sell all load management services to customers (other than emergency SCC); A DNSP will offer UFLS and Boost services to customers, either through Retailers via the network tariff or directly to customers; A Retailer can request a customised network tariff for the load management service being offered. A Retailer can request that a customer be moved from the DNSP allocated Network Tariff to a different Network Tariff (Note that some Distributors consider this point to be BAU and hence out of scope, whilst other Distributors doubt whether this principle is BAU) There should be a new NEM Procedure for this CS function (AGL#3.2). Service request should be real time and automated; service level very high (AGL#3.3, 3.4). Service requests should be able to be scheduled as well as queued for action via B2B (AGL#3.5). Performance and service level requirements of this function should be carefully chosen to match the objectives of the smart meter program (AGL#3.8). FRMP requires reason for failure to carry out FRMP request to be provided either immediately or the next business day along with the metering data readings (AGL process map). Need to establish consistency in terminology between MSATS procedures and B2B procedures The number of load contractors and relays to be included in a Smart Meter will be at the discretion of the Minister when determining the conditions of the mandatory rollout. A single service request must be able to record multiple actions (and their sequence) for execution at a single connection point (AGL). A single service request must be able to record group commands (and their sequence) for execution at multiple connection points (AGL). There needs to be a priority order for different types of messages, with the possibility that 2 or more message types may have the same priority (AGL). A FRMP must be notified of a request that has failed to be delivered remotely to a Smart Meter (AGL). The status of a dedicated load contactor or relay must be provided to the FRMP within a reasonable timeframe (after a request to operate that contactor or relay has been initiated by that person) before the FRMP can initiate a second request on that contactor or relay (AGL) Function Load Management through a controlled load contactor #7.6 Other points for further consideration: A DNSP will have the ability to construct network that reflect a range of possible settings for load management services. All load control services being requested will be assigned a logical device number regardless of the physical device properties. PRINCIPLES That is: The FRMP has an interest in: o Default Load Control Schedule o Special Day operation o Priority override operation o Loss of supply load switching o UFLS operation (status only) o Demand limit o Load cycling o Boost mode The LNSP has an interest in: o Emergency Supply Capacity Control o UFLS operation o Boost mode (status only) AGL : Has this been decided? It is presumed that DNSP will be able to offer retail services only as an eligible retail participant and not as a regulated DNSP business. NSSC policy principles permit this principle. The principle does not support the assumption. AGL : Continuation of agreed point above. (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 5 Noted x

6 Customer service Function Load Management through a controlled load contactor #7.6 ACTIVITY DIAGRAM - registration Events & sequence (FRMP): Discover attributes of all CLC/R at a connection point Discuss rights to register CLC/R with customer for a nominated appliance o Obtain customer consent Request DNSP to register CLC/R for nominated appliance Request DNSP to configure CLC/R to a specified time schedule Receive notification from DNSP that nominated appliance has been registered Receive notification from DNSP that time schedule has been activated request / receive B2B receive / respond Check current time schedule and if the requested change is within agreed parameters Events & sequence (DNSP): Receive request from FRMP to register CLC/R against a nominated appliance: o Confirm CLC/R is not already in use o Assign FRMP to CLC/R and nominated appliance o Notify FRMP that registration for nominated appliance is complete Receive request from FRMP to configure CLC/R to a specific time schedule o Check nature of request o Issue command to change time schedule o Notify FRMP of that CLC/R time schedule has been changed Notify FRMP of reasons if their request could not be completed: o From an agreed list o Reasons request not actioned for any reason o Reissue of FRMP request as a standard process DNSP updates market systems Point 3 below is in the form of a principle and has been transferred to the principles page. 1. Reasons for not completing the request might be: Comms issues Meter issues Network Issues/emergency override 2. If DNSP process fails, or the request is not actioned for any reason, then this information must be conveyed to the FRMP along with the reasons for not completing the request 3. A standard process for the reissue of the FRMP request should be available x (1) CLC/R means Controlled Load Contactor and/or Relays (2) Green text indicates interface traffic (3) Red text means to be discussed BPPWG process maps customer services v03 (4) Purple text means a change to the slide from last version PE note Slide 6

7 Customer service The times nominated are indicative only but are useful to show that a priority should be available for each request. For example, 1hr means a high priority with execution occurring within 1 hr of the request. 24hr means a low priority with execution occurring within 24 hrs of the request. Function Load Management through a controlled load contactor #7.6 Events & sequence (FRMP): Request DNSP to reconfigure CLC/R to a specified time schedule Request DNSP to over-ride time schedule (disable settings) Request DNSP to shift CLC/R time schedule within a specified period (24h/8h/1h) Receive notification from DNSP of need to trigger override Receive notification from DNSP that override action has been initiated Receive notification of UFLS status ACTIVITY DIAGRAM - reconfigure Reconfigure means a change of meter settings for a CLC/R request / receive This is more like an operational condition rather than a reconfigure condition. It has been left here for the moment B2B receive / respond How should the boost function be included? Treat as a principle. Move to principles page Events & sequence (DNSP): Receive request from FRMP to reconfigure CLC/R to a specific time schedule o Check nature of request. o Issue command to reconfigure the CLC/R time schedule On request of FRMP In accordance with DNSP contractual requirements o Notify FRMP that CLC/R time schedule has been changed On request from FRMP, activate the CLC/R time schedule over-ride o Notify FRMP of that override of time schedule has been effected o Notify FRMP of % of sites operated Notify FRMP of sites not operated DNSP has a need to over-ride CLC/R time schedule: o Notify FRMP of reconfigured CRC/R time schedule after over-ride action initiated Notify FRMP of reasons if their request could not be completed DNSP updates market systems x (1) Green text indicates interface traffic (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version PE note Slide 7

8 Customer service Function Load Management through a controlled load contactor #7.6 ACTIVITY DIAGRAM re-registration Events & sequence (FRMP): Request DNSP to transfer registration of the CLC/R from a current appliance to a new appliance Receive notification from DNSP that the CLC/R has been re-registered to the new appliance Re-register means a change of a nominated appliance against a CLC/R for the current FRMP or DNSP request / receive B2B receive / respond Events & sequence (DNSP): Receive request from FRMP to transfer registration of the CLC/R from a current appliance to a new appliance o Check nature of request. o Issue command to transfer the CLC/R from one appliance to another On request of FRMP In accordance with DNSP contractual requirements o Notify FRMP that registration of the new appliance is complete Notify FRMP of reasons if the request could not be completed DNSP updates market systems x (1) Green text indicates interface traffic (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version PE note Slide 8

9 Customer service Function Load Management through a controlled load contactor #7.6 ACTIVITY DIAGRAM de-registration Events & sequence (FRMP): Request DNSP to deregister nominated appliance from CLC/R Receive notification from DNSP that de-registration is complete De-register means: (a) removing the FRMP associated with a CLC/R; and/or (b) permanently removing the nominated appliance. request / receive B2B receive / respond Events & sequence (DNSP): Receive request from FRMP to deregister nominated appliance from CRC/R o Check nature of request. o Issue command to deregister CLC/R for nominated appliance o Deregister the nominated appliance from the CLC/R in accordance with DNSP contract Notify FRMP of reasons if the request could not be completed DNSP updates market systems x (1) Green text indicates interface traffic (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version PE note Slide 9

10 SPAN comments (2) Function Load Management through a controlled load contactor #7.6 Are these the only activities that the FRMP is interested in? For example, is the FRMP interested in UFLS events? To be reworked once the NSSC policy on which parties operate the load contactor has been resolved To be reworked for: 1. Registration 2. Re-registration 3. De-registration x PE note How should the boost function be included?? Reasons for not completing the request might be: Comms issues Meter issues Network Issues/emergency override Events & sequence (FRMP): Request LNSP to set dedicated load to a specified time profile Request LNSP to over-ride load time profile (ON OFF) Request LNSP to shift load time profile / sub profile within a specified period (24h/8h/1h??) Receive advice from LNSP of need to trigger override Receive advice from LNSP that override action has been initiated Receive advice/status on UFLS request / receive B2B receive / respond 1 or 50,000 over-ride requests per day/lnsp?? 1 or 50,000 over-ride requests / responses per day/lnsp?? 1 or 50,000 over-ride response per day?? Events & sequence (LNSP): Receive request from FRMP to set dedicated load to a specific time profile o Check nature of request. o Acknowledge FRMP request. o Issue command to reconfigure the dedicated load time profile On request of FRMP In accordance with LNSP contract?? o Advise FRMP of configuration status of load time profile for the nominated dedicated load On request of FRMP, activate the load time profile over-ride o Advise FRMP of activation status of load time profile override o Advise FRMP of % of sites operated SPAN clarification Identify sites not operated o Acknowledge FRMP request LNSP has a requirement to over-ride load time profile: o Discuss and agree requirement with FRMP?? capacity. o Advise FRMP of load time profile status after over-ride action initiated o Determine possible scenarios for DNSP action Advise FRMP of reasons if the request could not be completed: (from an agreed list)?? Reasons request not actioned for any reason (reissue of FRMP request as a standard process)?? (1) Green text indicates interface traffic To be clarified ACTIVITY DIAGRAM - registration (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version Slide 10 ON OFF 0 hours 24 Delete in Activity Diagram. Identify in Control Point Records ON OFF 0 hours 24 Mon to Sun 5 x ON & OFF per day What is the LNSP contract to be clarified Agreed to use comment as a test in Role Requirements Paper (23/4/10) - Advise of the percentage of sites operated can be on the basis of what signals the SMMS is able to send out. Receiving all the responses and sending back to the SMMS would flood the infrastructures communications If LNSP process fails, or the request is not actioned for any reason, then this information must be conveyed to the FRMP along with the reasons for not completing the request >>>> a standard process for the reissue of the FRMP request should be available

11 Customer service Function Load Management through a controlled load contactor #7.6 SMI Functional Specification v0.26 #7.6 (page 23) What is the minimum number: This means that if a contactor is provided, there will be no relays. And if one or more relays are provided, there will be no contactor. Load cycling is to be defined in FSv0.25 That is, if the boost primacy mode (priority#3) is selected by a consumer (as part of a retailer offering) the Control Demand Limit (priority#5) will be overridden. However, the boost mode on its own (priority#6) will not override the Control Demand Limit. AGL : Where does the Queue reside? On the meter or on the SMMS? It should be clearly specified that Queuing and Scheduling functionality resides on the meter Queuing in meter: SB to discuss with BRWG. Queuing in SMMS: to be resolved in UR work once indicative Service Levels are available Requirements a) For a meter with a controlled load contactor or relay the controlled load contactor or relay shall be integrated into the meter. (i) The rating of a single phase controlled load contactor that is integrated into the meter shall be 31.5A resistive (AC1 rating) and a nominal voltage rating of 230 Vac. (ii) The rating of a single phase voltage free relay integrated into the meter shall be 2A with a voltage rating of 230 Vac. Up to three voltage free relays shall be supported. (iii) It shall be possible to separately specify the functionality described in Section Error! Reference source not found. to the controlled load contactor and all relays integrated into the meter (iv) In Section Error! Reference source not found. references to the controlled load contactor should be interpreted as the controlled load contactor and/or relay(s) fitted to the meter b) For meters with a controlled load contactor the meter shall support the following basic load control functions: (i) Load Switch Actions (ii) Switch Time Randomisation (iii) Load Cycling c) The meter will use the basic load control functions to separately support the following modes of operation for each controlled load contactor in the meter. (i) (a) Normal Operation Default Load Control Schedule (ii) Alternative Load Control Operation (a) (b) Special Day Load Control Schedule Priority Override (iii) Event Driven Operation (a) (b) (c) Meter Loss of Supply Event Under Frequency Event Demand Limit Event (iv) Customer Driven Operation (a) Boost Mode d) Settings for the controlled load contactor shall be configurable both locally and remotely e) The hierarchy for the modes of operation of the controlled load contactor is governed by the following order: (i) Priority 1 1 Where enabled Meter Loss of Supply Load Switching (ii) Priority 2 (iii) Priority 3 Where enabled: Under Frequency Load Switching Where Boost and Boost Primacy enabled: Boost (iv) Priority 4 When commanded: Priority Override (described in Section Error! Reference source not found.) (v) Priority 5 Where enabled: Direct Load Control Demand Limit 1 Priority 1 is the highest priority Section AGL 24/2/10: What happens when Boost is pressed during a demandlimiting event? 0 contactors & 0 relays; 1 x 31.5A contactors; OR 1, 2 or 3 x 2A relays. AGL 24/2/10: How are we allowed to execute these actions? Is it a role based direct access or is it via B2B service request process? Depends on the prioritisation queue. See clause 7.6.1(e)(iii) and (vi). See also the explanation on primacy in clause Customer Switch Operation Mode (b)(iv). BPPWG process maps customer services v03 Continues on pages 24, 25, 26, 27 and 28 PE note Slide 11 x To be resolved in solution mode

12 Customer service Function Load Management through a controlled load contactor #7.6 AGL 24/2/10: Can multiple actions (sequence) be listed for execution in a single service request? For e.g. a single load management request will actually be executed as: 1. Return status 2. If ON: Commence cycling for 30 mins 3. Stop cycling SMI Functional Specification v0.26 #7.6 (page 24) (i) Priority 6 Where Boost enabled and Boost Primacy disabled: Boost (ii) Priority 7 (iii) Priority Basic Load Control Functions Load Switch Actions When meter date is a special date: Special Load Control Schedule Default Daily Load Control Schedule How should process be developed to accommodate groups of commands? Discussed with SB. Agreed that this should be stated as (1) A single service request must be able to record multiple actions (and their sequence) for execution at a single connection point; (2) A single service request must be able to record group commands (and their sequence) for execution at multiple connection points. It was agreed to move these statements to the principle page. a) The controlled load contactor shall have functionality supporting: (i) Turn On Immediately (ii) Turn Off Immediately (iii) Delayed Turn On (using Switch Time Randomisation, refer to Section ) (iv) Delayed Turn Off (using Switch Time Randomisation) (v) Start Load Cycling (refer to Section ) (vi) Stop Load Cycling Switch Time Randomisation b) In order to avoid synchronised switching of loads throughout the distribution network area the meter shall support the generation of a random delay (i) (a) (b) The meter shall have programmable settings allowing: The minimum time delay to be specified from 0 to 720 minutes (12 hours) in 1 minute increments; The maximum time delay to be specified from 0 to 720 minutes (12 hours) in 1 minute increments; (ii) The delay calculated by the meter shall be a time in seconds from the minimum time delay to the maximum time delay. The algorithm shall use a uniform probability. (a) To ensure that the controlled load contactor is turned on for a defined time when using delayed switching the meter shall either: 1. When the meter is powered on or meter settings affecting Switch Time Randomisation are changed, the meter shall calculate and record a new random time delay. All Delayed Turn On and Delayed Turn Off load switch actions will use this recorded time delay; or 2. On power restore the or when the Delayed Turned On load switch action is used, the meter shall calculate and record a new random time delay. Delayed Turn Off load switch actions shall not calculate a new delay, instead using the recorded time delay Load Cycling of the controlled load contactor c) Load Cycling of the controlled load contactor shall support the following functionality: (i) The meter shall record programmable setting allowing a Random Delay to be specified before load cycling commences. The setting shall allow: (a) The time delay before commencing load cycling to be specified from 0 to 120 minutes in 1 minute increments. x BPPWG process maps customer services v03 PE note Slide 12 Continues on pages 25, 26, 27 and 28

13 Customer service Function Load Management through a controlled load contactor #7.6 SMI Functional Specification v0.26 #7.6 (page 25) (a) The time delay before commencing load cycling calculated by the meter shall be a time in seconds from zero to the maximum time delay. The random delay algorithm shall use a uniform probability distribution. (ii) The meter shall have programmable settings allowing the Cycle Times to be specified. The settings shall allow: (a) (b) The Cycle On Time to be specified in minutes from 1 to 120 minutes in 1 minute increments. The Cycle Off Time to be specified in minutes from 1 to 120 minutes in 1 minute increments. b) When the Load Control Cycling Program starts; (i) If the initial position of the controlled load contactor is in the off position, then after the Random Delay the controlled load contactor will switch to the on position and will commence cycling (off and on) in accordance with the cycle on time and cycle off time. (ii) If the initial position of the controlled load contactor is in the on position then after the Random Delay the controlled load contactor will switch to the off position and will commence cycling (on and off) in accordance with the cycle on time and cycle off time Normal Operation Mode a) The controlled load contactor shall have functionality supporting a programmable sequence of load switch actions. b) The meter shall record a programmable Default Day Load Control Schedule. The Default Day Load Control Schedule shall record ten (10) programmable entries, where each of the ten entries shall specify: (i) The meter time at which the load switch action will occur (in Hours and Minutes) (ii) The required load switch action (from Error! Reference source not found.) c) The meter shall support two Default Day Load Control Schedules referred to as Day Type 1 Default Load Control Schedule and Day Type 2 Default Load Control Schedule (i) For each Day of Week it shall be possible to record a programmable setting specifying which of the two Default Load Control Schedules will operate on that day; Alternative Load Control Operation Mode d) The meter shall support a Special Day Load Control Schedule. (i) To support the Special Day Load Control Schedule the meter shall record a programmable list of up to twelve dates on which the Special Day Load Control Schedule is to be used (ii) The meter shall record a programmable Special Day Load Control Schedule. The Special Day Load Control Schedule shall record ten (10) programmable entries, where each of the ten entries shall specify: (a) (b) The meter time at which the load switch action will occur (in Hours and Minutes) The required load switch action (from Error! Reference source not found.) e) The meter shall support a Priority Override Command (i) (a) (b) (c) The Priority Override Command shall specify. Start Date and Time (in Hours and Minutes) for the override. The Start Time shall also allow: commence immediately. Duration of the Override from 1 to 1440 minutes (24 hours) in 1 minute increments The required load switch action BPPWG process maps customer services v03 Continues on pages 26, 27 and 28 Slide 13

14 Customer service Function Load Management through a controlled load contactor #7.6 SMI Functional Specification v0.26 #7.6 (page 26) (i) After the Duration of the Priority Override, the meter will return to the next highest current load control mode (ii) It shall be possible to locally and remotely clear Priority Override. On clearing the Priority Override the meter will immediately return to the next highest current load control mode. (iii) If during the Priority Override another Priority Override Command is received, it will overwrite the previous settings Event Driven Operation Mode a) The meter shall support Meter Loss of Supply Load Switching. (i) The meter shall record a programmable setting allowing Meter Loss of Supply Load Switching to be enabled or disabled. Enabling and disabling of this setting shall be possible both locally and remotely; (ii) If Meter Loss of Supply Load Switching is enabled: (a) (b) On detection of meter loss of supply, the load contactor shall be switched to the off position On power restore the recorded random delay (specified in Error! Reference source not found.) shall be applied before returning to the next highest current load control mode b) If the meter supports under frequency load switching. (i) The meter shall record programmable settings for under frequency load switching. The settings shall allow: (a) (b) (c) (d) (e) Under frequency load switching to be enabled or disabled The trigger frequency for under frequency load switching from 48Hz to 50Hz in increments of 0.1Hz The measurement period for triggering under frequency load switching from 5 to 60 seconds in increments of 5 seconds The measurement period for triggering the end of under frequency load switching from 1 minute to 60 minutes in increments of 1 minute The under frequency load contactor position for the controlled load contactor during the under frequency, as either turned on or turned off. (ii) If under frequency load switching is enabled (a) (b) When the measured mains frequency drops below the trigger frequency for more than the trigger measurement period the meter shall ensure the controlled load contactor is in the under frequency load contactor position. An event shall be stored in the meter s Quality of Supply Event log to indicate that under frequency mains switching has occurred. When the measured mains frequency increases above the trigger frequency for more than the end of under frequency measurement period the meter shall store an event in the meter s Quality of Supply Event log indicating that the mains frequency has returned to normal. The meter shall use the recorded random time delay (as specified in Error! Reference source not found.) before returning to the next highest current load control mode. c) The meter shall support Demand Limit Load Control Switching. (i) The meter shall record programmable settings for Demand Limit Load Control Switching. The settings shall allow: (a) Demand limit load control switching to be enabled or disabled BPPWG process maps customer services v03 Continues on pages 27 and 28 Slide 14

15 Customer service Function Load Management through a controlled load contactor #7.6 SMI Functional Specification v0.26 #7.6 (page 27) (a) (b) (c) (d) (e) The meter time to terminate Demand Limit Load Control Switching to be specified in hours and minutes Demand limit load control switching exported average active demand trigger value to be specified from 0.5 to 99kW in increments of 0.5kW Demand limit load control switching measurement period to be specified from 1 to 30 minutes in 1 minute increments The Demand Limit Load contactor position for the controlled load contactor during the Demand Limit Event to be specified as turned on or turned off. The Demand Limit Load contactor timeout period to be specified from 1 to 60 minutes in 1 minute increments. (ii) If Demand Limit Load Control Switching is enabled and the meter time indicates that Demand Limit Load Control should be initiated: (a) (b) When the exported average active demand across the specified measurement period exceeds the Demand limit trigger value the controlled load contactor shall be switched to the Demand Limit Load contactor position. An event will be stored in the meter s Quality of Supply Event log indicating that the Demand Limit was exceeded. The controlled load contactor will remain in the Demand Limit Load contactor position for the Demand Limit Load contactor timeout period before control of the load control contactor returns to the next highest current load control mode Customer Drive n Operation Mode a) A meter shall have a configurable Boost option to operate the controlled load contactor. b) The meter shall record a programmable setting allowing Boost operation to be enabled or disabled. Enabling and disabling of this setting shall be possible both locally and remotely. c) If Boost is enabled: (i) A customer can activate boost functionality by pressing a button (Boost Button) on the front of the meter. (ii) When the meter s boost function is activated, (a) (b) (c) The meter shall switch on (close) the controlled load contactor for a preset time, which is programmable from 1 to 6 hours in half hour increments. The boost preset time shall be configurable both locally and remotely; An event will be stored in the meter s Quality of Supply Event Log indicating that boost has been activated. At the end of the boost preset time control of the load control contactor will return to the next highest current load control mode. d) When the Boost Button is disabled, pressing the Boost Button will not switch the controlled load contactor to the on position. e) It shall be possible to change the priority of the Boost Functionality using a Boost Primacy setting. Enabling the Boost Primacy setting shall raise the priority of the Boost above that of Priority Override and Direct Load Control Demand Limit. a) The meter shall support a programmable setting to automatically disable boost functionality when the Emergency Supply Capacity Limit is enabled. BPPWG process maps customer services v03 Continues on page 28 Slide 15

16 Customer service Function Load Management through a controlled load contactor #7.6 SMI Functional Specification v0.26 #7.6 (page 28) Smart Metering Infrastructure Performance Levels a) For Priority Override Commands : b) For transmission to all meters the requested Load control command acknowledged by 90% of meters within 10 minutes 1 c) For commands sent to one or more groups of meters up to four load control commands can be sent to all meters (or groups of meters) in any 24 hour period; d) For commands sent to individual meters requested Load control command acknowledged by 90% of meters within 20 minutes e) The total number of load control commands to individual meters in any 10 minute period can be up to 0.035% of the installed, operational SMI meter population in a distribution network area f) The total number of load control commands to individual meters in any 24 hour period can be up to 2% of the installed, operational SMI meter population in a distribution network area Participant Service Levels g) Standard operation will be turn off and turn on times set within meter, these will operate with sub second Participant Service Level (Indicative) performance h) Alterations to (i.e. remote override) turn off and turn on times will require additional Participant Service Level (Indicative)s. Note this may require additional communication between network and retailer regarding customers existing configuration and tariffs and proposed changes (i) change from Off Peak 1 to Off Peak 2 or vice versa (Participant Service Level (Indicative): performed within 24 hours (ii) load shedding during a controlled load on period (Participant Service Level (Indicative): performed at 98% of meters within 30 mins (iii) temporary override - turn on for set period of time e.g. no hot water so perform short period boost (Participant Service Level (Indicative): performed at individual site within 1 hr of request received 1 Note: Command can also be sent to an individual or group of installed meters BPPWG process maps customer services v03 Slide 16

17 AGL comments (2) NOTE (1): agree to use terms FRMP and DNSP instead of retailer and service provider Function Load Management through a controlled load contactor #7.6 NOTE (2): need to establish consistency in terms between MSATS procedures and B2B procedures >> transfer to principles FRMP LNSP Comments/Queries FRMP Decision Service Provider - SP Comments/Queries 1 Requests SP to set dedicated Load to specified Time Profile Read as network service provider (ie DNSP) for mandate period To be noted Service Levels governed by FS. Further explanation to be provided by SB?? Added to Activity Diagram 2 Request SP to override the above Issues command and advises status to FRMP **Requires a NEW Procedure **Service Levels need to be defined as the action is real-time. **The request needs to be acknowledged to FRMP and the FRMP needs to be advised of the status and WHY the request could not be completed with reasons identified such as: 1. Comms Issues 2. Meter Issues 3. Network Issues/Emergency override. **There should be penalties if the request is NOT ACTIONED and PERFORMANCE INCENTIVES as this has financial impacts on FRMP. **If failed process needs to cover time of re-issuing and information back to FRMP. In case of EMERGENCY, LNSP overrides the Load time profile. It is required to notify FRMP and advise status. 1. emergency This is a matter for the RWG.SB to follow-up with RWG. x Included in the Activity Diagram If DNSP process fails, or the request is not actioned for any reason, then this information must be conveyed to the FRMP along with the reasons for not completing the request >>>> transfer to Activity Diagram. A standard process for the reissue of the FRMP request should be available BPPWG process maps customer services v03 PE note Slide 17

18 AGL comments (3) Function Load Management through a controlled load contactor #7.6 Discussed with SB. Focus is on the relay in the meter, not on the DRED Device at the appliance. Discussed with Martin Gill see MG response Discussed with SB. Discussed with Martin Gill yes MG: 1. SMI F.S. allows up to three 2A relays on two [of the] meter configurations. Depends on rollout determination & DNSP purchase plan 2. SMI F.S. does not assign uses for these relays, the meter simply turns the relays On or Off 3. In AS4755: If nothing is connected to the interface the device runs without restriction Please clarify the following: 1 How many DRED relays are there in the smart meter? Is the minimum number set to 3? 2 Is there a separate relay for each device OR a separate relay for each DRED mode (on/off, 50% and 75%)? 3 Is the default operating mode ON as 100% before the DRED Code is transmitted? 4 In the diagram of Smart Meter, going from top to bottom, The 4th DRED relay does not exist in the meter? How is the DRED code being transmitted to device? 5 In order to execute load control on a device there is a minimum requirement of:??? * Smart Meter with DRED relays and DRED Code Interface. Is the DRED CODE Interface inside the meter? Comment withdrawn * Physical wiring between smart meter and each individual device/appliance * DRED Intelligent device connected to the appliance or an appliance with DRED enabled interface. Having load control facility in the meter is no use if the customer has not additionally installed the DRED enabled appliances. Depends on whether load control need is just ON/OFF or graduated to a performance %. If this is a reference to performance % using the DRED Device, then this comment is correct. Discussed with SB. PE revised diagrams after clarification with Martin Gill. Agreed. Diagrams changed after discussion with Martin Gill x BPPWG process maps customer services v03 PE note Slide 18

19 AGL comments (4) Function Load Management through a controlled load contactor #7.6 Comments transferred from spreadsheet (v09) page CSfn7.6-Procedure#40 for analysis Awaiting NSSC policy decision Transferred to principles The following feedback is based on the scenario that the Load Management function is executed via B2B There should be a new procedure for Service Request for all Customer Service Functions. The service request for executing this function should be real time and automatic Since the action to the Load Management request will be required instantaneously (ideally), hence the service levels need to be very high. Service requests should be able to be scheduled as well as queued with the service provider for action. The initiating party should receive status (success/fail) as Response. If it was a fail, the reason for the fail be clearly communicated to the initiating party. Load Management via dedicated circuit on adhoc basis will always be a high-priority. Performance and service level requirements of this function should be carefully chosen to match the objectives of the smart meter program. Discussed with SB. Agreed to change the statement to There needs to be a priority order for different types of messages, with the possibility that 2 or more message types may have the same priority. Agreed to transfer this statement to the principles page. Transferred to Activity Diagram x BPPWG process maps customer services v03 PE note Slide 19

20 Customer service AEMO switching of the Supply Contactor ON & OFF. Will these states be registered in MSATS? Function Load Management through a controlled load contactor #7.6 No, as Appendix B of FS v0.24 does not list the status of the Supply Contactor as a meter setting. Fn (b)(i) states: the SMI shall be able to remotely determine the status of a Supply Contactor MG has advised that this function has been provided to allow the status of contactors and relays to be determined. This implies that a retailer will need to make a request to the DNSP each time they need to know the status of the Supply Contactor. SCHEMATIC DIAGRAM(1) with minimum functionality (that is, no dedicated controlled load contactor or relays... the actual number depends on the meter configuration presented in Section 6 of the Functional Specification, v0.24) Connection point Main Fuse Supply Contactor Circuit switch Meter o WWW power circuit Hot Water Air Conditioner Measurement element power circuit Smart Meter Management System Smart Meter Communication Network relay operation signals modem Option combinations in some meters: 1. 0 contactor + 0 relays 2. 1 contactor + 0 relays 3. 0 contactor + 1 relay 4. 0 contactor + 2 relay 5. 0 contactor + 3 relay Note that each relay will have its own list of setting to be configured. motor AEMO where are the meter elements and connection points on the diagram? Has the BPPWG defined the hierarchy of all the points? E.g. Changing what component changes the NMI status? Connection point? Supply contactor? This definition will impact how we manage market processes/procedures. Connection point and measurement element added to diagram. Hierarchy of operation of fuse, main switch and supply contactor (and their relationship) has not been considered at the issue phase of the analysis. This discussion will emerge in the solution phase. x (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 20

21 Customer service Function Load Management through a controlled load contactor #7.6 SB: requested that BPPWG discuss who has responsibility to assign # of contactors and relays in a Smart Meter. (The Minister has a choice of none or one dedicated controlled load contactors OR 0, 1, 2 or 3 RELAYS in the mandatory rollout determination) PE: I now understand (14/4/10) that this matter is being considered by the RWG and the BPPWG will be advised in due course of the policy that will be adopted on this matter. Supply Contactor Fn#8 & #14 Dedicated 31.5A load contactor Meter WWW Circuit switch power circuit power circuit SCHEMATIC DIAGRAM(2) with one load contactor and 0 relays (In this example, the Minister has included one dedicated controlled load contactor in the mandatory rollout determination) MG QUESTION: Where does the CURRENT system store that hot water is connected? Hot Water Discussed with MG. Will the type of appliance that is connected to a CLC be recorded by the DNSP, as is the case in the current arrangements? Will such a record be required? Air Conditioner Smart Meter Management System Smart Meter Communication Network relay operation signals modem Normal supply arrangement. That is, in this example the supply is not impacted by the use of the Smart Meter. motor MG 24/2/10: Exception Emergency Override Load Control command BUT this still does not check that the relay has switched For example, a priority override is a special program (see clause 7.6.1(c)(ii) to (iv)). MG 24/2/10: FRMP sends a load management profile through the DNSP to the meter. The meter receives the profile and loads profile successfully. The SMMS records that the event as successfully received and understood via a timeout facility and a series of codes (not in FS)?? DNSP advises FRMP that profile was loaded successfully, or failed to load. NOTE: The 31.5A contactor does not register a change of status in the Event Log whilst the normal program is operational. However, if the normal program is changed to a special program then each operation of the SC will be recorded in the Event Log. MG 24/2/10: The Event Log for the contactor and relay will capture exceptions to any switch command, but not the switching event itself Discussed with SB. Agreed to rework the question as follows: A FRMP must be notified of a request that has failed to be delivered remotely to a Smart Meter. Agreed to transfer this statement to the principles page. MG 24/2/10: Priority appliances are considered to be: Hot water Air conditioner Pool pump Question (SB): how many retries does the SMMS undertake before the FRMP is advised by the DNSP? x (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 21

22 Customer service Function Load Management through a controlled load contactor #7.6 SCHEMATIC DIAGRAM(3) with one load contactor and 3 relays (The Minister has a choice of none or one dedicated controlled load contactors OR 0, 1, 2 or 3 RELAYS in the mandatory rollout determination) Supply Contactor Meter (In this example, the Minister has included 3 RELAYS in the mandatory rollout determination) The status of a dedicated load contactor or relay must be provided to the FRMP within a reasonable timeframe (after a request to operate that contactor or relay has been initiated by that person) before the FRMP can initiate a second request on that contactor or relay (AGL). Circuit switch WWW power circuit Hot Water Smart Meter Management System Smart Meter Communication Network relay operation signals modem power circuit Air Conditioner In this example, the 3 relays are being used by the one air-conditioner The 2A relays can also be assigned to multiple devices (for example, one to an external pool pump contactor, one to an external hot water contactor, and one to the 75% air conditioner control point. MG: Exception Emergency Override Load Control command BUT this still does not check that the relay has switched Discussed with SB. Comment reqorked to The status of a dedicated load contactor or relay must be provided to the FRMP within a reasonable timeframe (after a request to operate that contactor or relay has been initiated by that person) before the FRMP can initiate a second request on that contactor or relay (AGL). Agreed to transfer this point to the principles page. 2A relays On & OFF pulses common common NOTE: The 2A relays do not register a change of status in the Event Log 75% mode 50% mode No acknowledgement signals provided AGL 24/2/10: What registers change? How will the FRMP know that the load management request was successful. Event logs is the only mechanism to validate the date-time and read. The status of relays is determined using Fn#7.12. Does this resolve this question? AGL : AGL requires the status of the load management request to be provided. If this status is not received in time then another B2B request is not going to resolve the issue as it will be a strain on the system to send another 2 way request (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 22 Intelligent Device MG: Correct. This status has to be inferred from the half hourly energy consumption interface motor AS 4755 Interface: Specifies capacity. Does not specify how to use Selects % on receipt of relay operation On & Off 75% MG: 50% AS4755 has on and off as mandatory and 50%, 75% as optional. The intelligent device must cycle an appliance which does not support the 50/75% modes of operation x

23 Customer service Function Load Management through a controlled load contactor #7.6 SCHEMATIC DIAGRAM(4) with one load contactor ON OFF 0 hours 24 ON Mon to Sun 10 x ON & OFF per day OFF 0 hours 24 power circuit power circuit Hot Water Air Conditioner Smart Meter Management System Smart Meter Communication Network modem motor x (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 23

24 Customer service Function Load Management through a controlled load contactor #7.6 Level 1 PROCESS MAP FRMP ACTIVITIES DNSP ACTIVITIES SMMS (INITIATE ACTION) SMART METER OPERATION SMMS (STATUS UPDATE) Request DNSP to register CLC/R for nominated appliance Request DNSP to configure CLC/R to a specified load control schedule Request DNSP to reconfigure CLC/R to a specified load control schedule Request DNSP to over-ride load control schedule (disable settings) Request DNSP to shift CLC/R load control schedule within a specified period (24h/8h/1h) Request DNSP to transfer registration of the CLC/R from a current appliance to a new appliance Request DNSP to deregister nominated appliance from CLC/R Receive notification from DNSP that nominated appliance has been registered Receive notification from DNSP that load control schedule has been activated Receive notification from DNSP of need to trigger override Receive notification from DNSP that override action has been initiated Receive notification from DNSP that the CLC/R has been re-registered to the new appliance Receive notification from DNSP that de-registration is complete Receive request from FRMP to register CLC/R against a nominated appliance o Assign FRMP to CLC/R and nominated appliance o Notify FRMP that registration for nominated appliance is complete Receive request from FRMP to configure CLC/R to a specific load control schedule o Issue instruction to configure the CLC/R load control schedule o Notify FRMP that CLC/R load control schedule has been changed Receive request from FRMP to reconfigure CLC/R to a specific load control schedule Receive request from FRMP to activate the CLC/R load control schedule over-ride o Issue instruction to over-ride load control schedule o Notify FRMP that over-ride of load control schedule has been effected o Notify FRMP of % of sites operated o Notify FRMP of sites not operated Receive request from FRMP to transfer registration of the CLC/R from a current appliance to a new appliance o Issue instruction to transfer the CLC/R from one appliance to another Receive request from FRMP to deregister nominated appliance from CLC/R o Issue instruction to deregister CLC/R for nominated appliance o Notify FRMP that de-registration is complete Notify FRMP of reasons if request could not be completed DNSP has a need to over-ride CLC/R load control schedule: o Notify FRMP of load CLC/R load control schedule after over-ride action initiated o Update market systems Check status of CLC/R : o Logical check in SMMS; o Remote check using Fn#7.12 Validate intended action Initiate intended action for nominated CLC/R SMMS Event Log record Load control schedule activated Load control schedule override activated Access & Security Event Log record Send confirmation of change in settings Send Event Log when prompted SMMS receives Fn#7.12 response information SMMS receives Event Log status confirmation SMMS Event Log record (1) SMMS means Smart Meter Management System BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 24 x

25 AGL comments (5) Function Load Management through a controlled load contactor #7.6 AGL 24/2/10: The words Business Decisions should be removed from all similar diagrams/processes. Customer service functions will be role-based and requests will be validated through the security protocol. With the desire of real-time like performance levels, there is hardly any leverage for manual decision validation. OK. Changed from Business Decisions to Activities Level 1 PROCESS MAP FRMP ACTIVITIES DNSP ACTIVITIES INITIATE ACTION SMART METER OPERATION STATUS UPDATE Request DNSP to set dedicated load to a specified time profile Request DNSP to activate load time profile Request DNSP to over-ride load time profile (ON OFF) Request DNSP to shift load time profile / sub profile within a specified period (24h/8h/1h??) Receive advice from DNSP of need to trigger override o Acknowledge advice?? Receive advice from DNSP that override action has been initiated Receive request from FRMP to set dedicated load to a specific time profile o Acknowledge FRMP request o Issue command to configure the dedicated load time profile o Advise FRMP of status of load time profile or reasons for not completing the request Receive request from FRMP to activate the load time profile o Acknowledge FRMP request o Activate the load profile over-ride o Provide FRMP with activation status report of load time profile o Advise FRMP of % of sites operated o Identify sites not operated Provide reason for failure to carryout FRMP request Receive request from FRMP to shift the load time profile o Acknowledge FRMP request o Shift the load profile o Provide FRMP with shift report DNSP has a need to over-ride load time profile: o Discuss/agree need with FRMP o Advise FRMP of load time profile status after over-ride action initiated o LSNP updates market systems (eg. MSATS Check status of load circuit: o Logical check in SMMS; o Remote physical check using Fn#7.12 Validate intended action Initiate operation of nominated circuit SMMS Event Log record Load profile activated Load profile override activated Access & Security Event Log record Send confirmation of change in program Send Event Log when prompted AGL 24/2/10: How will this be provided? FRMP requires access to that data either immediately or the next business day along with the reads. SMMS receives Event Log status confirmation SMMS Event Log record Use to inform service level discussion transfer to principles (1) SMMS means Smart Meter Management System BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 25 x

26 SPAN comments (3) Point of clarification (23/4/10) SPAN acknowledges that for an override event the DNSP should provide advice that the request is accepted and processed. The single response is on basis of the logic applied by the Smart Metering Infrastructure. The DNSP should not be obligated to send additional advice that to indicate the physical fulfilment at the meter. FRMP BUSINESS DECISIONS Point clarified. No further action required Request LNSP to set dedicated load to a specified time profile Request LNSP to activate load time profile Request LNSP to over-ride load time profile (ON OFF) Request LNSP to shift load time profile / sub profile within a specified period (24h/8h/1h??) Receive advice from LNSP of need to trigger override o Acknowledge advice?? Receive advice from LNSP that override action has been initiated SPAN 24/2/10: What is the point of checking the status of a load circuit if closed it does not mean there was any load reduction LNSP BUSINESS DECISIONS Receive request from FRMP to set dedicated load to a specific time profile o Acknowledge FRMP request o Issue command to configure the dedicated load time profile o Advise FRMP of status of load time profile or reasons for not completing the request Receive request from FRMP to activate the load time profile o Acknowledge FRMP request o Activate the load profile over-ride o Provide FRMP with activation status report of load time profile o Advise FRMP of % of sites operated o Identify sites not operated Provide reason for failure to carryout FRMP request Receive request from FRMP to shift the load time profile o Acknowledge FRMP request o Shift the load profile o Provide FRMP with shift report LNSP has a need to over-ride load time profile: o Discuss/agree need with FRMP o Advise FRMP of load time profile status after over-ride action initiated LSNP updates MSATS Change comment to read: What is the point of advising the retailer twice of a trigger event. The DNSP does not want to be obligated to check if their action has been completed at the meter for every decision to initiate an override. Function Load Management through a controlled load contactor #7.6 INITIATE ACTION SMART METER OPERATION Check status of load circuit Validate intended action Initiate operation of nominated circuit SMMS Event Log record Comments requested from retailers please Point of clarification (23/4/10) SPAN acknowledges that the process of initiating an action requires the status checking prior to fulfilment. However, this status is information that could stored in the SM Management System. Our interpretation of this check status is a logical check will suffice. Point clarified. No further action required SPAN 24/2/10: Load profile activated Load profile override activated Access & Security Event Log record Send confirmation of change Send status report when prompted What is the point of checking the status of a load circuit? If closed it does not mean there was any load reduction. Also it does not relate to changing, shif ting or over-riding the load profile Change activities to logical check and remote physical check on Level 1 process map slide SPAN 24/2/10: STATUS UPDATE SMMS receives status confirmation SMMS Event Log record Point of clarification Status reporting should refer to the event log. Status reporting on the Load circuit is not required Status report should indicate the current profile being applied whether it is changed, shifted or over-ridden The status report refers to the Event Log. There will be entries in this Log when special programs are enabled (see Note in Schematic Diagram(2) and (3)). Activity modified in process map to improve clarity (change status report to Event Log ). BPPWG process maps customer services v03 PE note Slide 26 x Agreed. Change made

27 Customer service Function Load Management through a controlled load contactor #7.6 INTERFACE TRAFFIC DIAGRAM Customer Market Systems Also deregister appliance MSATS Also transfer registration to new appliance Also reconfiguration of CLC/R schedule CP#16 FRMP ACTIVITIES Request registration of CLC/R for appliance Request configuration of CLC/R to schedule Request override of schedule Request shift of schedule CP#1 CP#2 CP#3 CP#4 CP#5 CP#6 CP#7 CP#8 CP#11 CP#12 CP#15 DNSP ACTIVITIES Notify that registration completed Notify that schedule has changed Notify of override to CLC/R schedule Notify that schedule shift completed Notify of override action taken Notify reasons request not completed Notify that deregistration completed Update Also % sites & site locations not operated Remote CP#13 CP#14 SMART METER Configure schedule Reconfigure schedule Over-ride schedule Shift schedule Fn#7.12 settings check of settings A&S Event Log record (1) CP means Control Point Send confirmation that settings have changed Two way acknowledgement (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version main area of interest PE note Slide 27 x

28 AGL comments (6) Function Load Management through a controlled load contactor #7.6 INTERFACE TRAFFIC DIAGRAM Market Systems No further action required AGL 24/2/10: What does this mean? MSATS CP#16 FRMP ACTIVITIES Request dedicated load set to specified time profile Request load profile be activated Request override of profile Request shift of profile CP#1 CP#2 CP#3 CP#4 CP#5 CP#6 CP#7 CP#8 CP#11 CP#12 CP#15 DNSP ACTIVITIES Provide status of profile Provide activation status report Provide confirmation of override activated Provide profile shift report Advise of need to trigger override Send override advice Send confirmation of operation Update MSATS Remote CP#13 CP#14 SMART METER Load time profile set Load time profile activated Load time profile override activated Load time profile shifted A&S Event Log record Send status confirmation x NOTES: BPPWG process maps customer services v03(1) CP means Control Point Two way acknowledgement main area of interest PE note Slide 28

29 SPAN comments (4) Function Load Management through a controlled load contactor #7.6 Market Systems MSATS CP#16 FRMP BUSINESS DECISION Request dedicated load set to specified time profile Request load profile be activated Request override of profile Request shift of profile CP#1 CP#2 CP#3 CP#4 CP#5 CP#6 CP#7 CP#8 CP#11 CP#12 CP#15 LNSP BUSINESS DECISION SMART METER Provide status of profile Provide activation status report Provide confirmation of override activated Load time profile set Load time profile activated Load time profile override activated Load time profile shifted A&S Event Log record Remote CP#13 Provide profile shift report CP#14 Advise of need to trigger override Send status confirmation Send override status report SPAN 24/2/10: Send confirmation of operation Status reporting on the Load circuit is not required Status report should indicate the current profile being applied whether it is changed, shifted or over-ridden Update MSATS Agreed to change status report to advice x BPPWG process maps customer services v03 PE note Slide 29

30 Customer service Function Supply Contactor operation OFF #7.7 PRINCIPLES Principles: 1. Don t disconnect in future?? 2. Retailers can switch-off a connection point faster using remote operation of the Supply Contactor?? 3. Retailers require knowledge of Supply Contactor status. 4. The ARM command will be initiated only by the DNSP; the FRMP is to be advised when the ARM status is set. 5. The auto-off function will be set with reference to the DNSP only. The FRMP does not require knowledge of this event 6. The FRMP requires notification is a loss of supply event has occurred. 7. The retailer is the only person who can request the ARM function be enabled?? (from slide 53 of v093) 8. The service process must contain NO MANUAL DECISION POINTS (AGL). 9. The commands / processes must allow for group as well as single meter targets (AGL). 10. Separate Group ID ranges must be available for different roles including at least FRMP, DNSP, MDP (AGL). 11. Meter Event log must be published in full to retailers (next day) along with the interval meter data (AGL). 12. Safety precautions are likely to be specified on a jurisdictional by jurisdictional basis (GRAPL) 13. Safety can be strengthened through standardisation of requests and response types between Market Participants and also between Retailers and customers (GRAPL) 14. DNSP should make status of supply contactor at the connection point available to eligible participants on request in accordance with agreed service levels (GRAPL) x (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 30

31 SPAN comments (1) Function Supply Contactor operation OFF #7.7 PRINCIPLES This point to be discussed by the BPPWG Principles: 1. Don t disconnect in future?? 2. Retailers can switch-off a connection point faster using remote operation of the Supply Contactor?? 3. Retailers require knowledge of Supply Contactor status. 4. The ARM command will be initiated only by the LNSP; the FRMP is to be advised when the ARM status is set. 5. The auto-off function will be set with reference to the LNSP only. The FRMP does not require knowledge of this event 6. The FRMP requires advice is a loss of supply event has occurred. 7. The FRMP is the only person who can request the ARM function be enabled?? (from slide 53 of v093) 23/4/10: SPAN disagrees that the FRMP is the only person who can request the ARM function. If ARM is used any Retailer or depending on safety risk assessment the DNSP may control the ARM function Agreed that term FRMP was too narrow and should be changed to retailer. Agreed that lst sentence can be deleted. x (1) Red text means to be discussed BPPWG process maps customer services v03 (2) Purple text means a change to the slide from last version PE note Slide 31

32 Customer service Events & sequence (FRMP): FRMP conversation with customer o Accommodation status: Non-payment: Check customer conditions (eg. life support) Move-out + transfer to another FRMP o Clarification of site requirements o Safety related information from customer: Additional information required to be satisfied that remote operation of Supply Contactor can be requested Understand connection point status (from MSATS or other database) o NMI status o Metering installation classification o Meter type (SM, AMI or other) o Meter attributes: Meter configuration details Energy measurement channels that have been configured Customer Service function settings o Meter contactor status o Fuse status Decision options for type of Service required: o Fuse REMOVE o Supply Contactor OFF Open remotely or locally Request supplementary information from DNSP: o Generally for exceptional circumstances Receive published service information from DNSP: Assess annual cost and service timing publication Conditions applicable to each Service Order type FRMP preference: o Advice to customer: Arrangements needed to vary connection point status Actions to be undertaken Time that supply will be connected o Customer agreement with arrangements FRMP decision to request DNSP: o To operate Supply Contactor or main fuse Type of B2B Service Order to be submitted?? o What if status information is incorrect MSATS has to be updated. IF the status information is incorrect, as soon as the CR is raised, the relevant participants should ensure the CATS tables are up to date in real time B2B Events & sequence (DNSP): Receive request from FRMP for connection point status o Validate B2B Service Order o Acknowledge request o Provide relevant information to FRMP Receive request from FRMP for supplementary information o Validate B2B Service Order o Acknowledge request o Provide relevant information to FRMP Receive request from FRMP to turn Supply Contactor OFF o Check pre-conditions o Acknowledge request o Activate by remote command o Activate by local action Receive request from FRMP to remove main fuse Publish cost of service (annually) o Include certainty of service (likelihood of success) o Guaranteed time of service Update standing data in MSATS: o Existing standing data o New standing data o If request by FRMP is found to be based on wrong information Examine Access and Security Event Log Function Supply Contactor operation OFF #7.7 AEMO ( 25/3/10) raised a limitation with the bilateral agreement and its application to the SMI. This comment raises a question of whether the bilateral agreement provision in clause 2.3(a) of the B2B Service Orders procedure applies to SMI?? For discussion. request / receive receive / respond Events & sequence (pending-frmp): nil Real-time (clarify??) report on connection point status (needs to be available) MSATS environment: Real-time information flows?? (1) Green text indicates interface traffic Update report on connection point status ACTIVITY DIAGRAM (2) Red text means to be discussed BPPWG process maps customer services v03 (3) Purple text means a change to the slide from last version PE note Slide 32 MSATS What is the "Guarantee"? It is as per the rules? Or the agreed "Service and performance" levels OR agreed by NSSC? But they are common and not NMI specific?? Are there any penalties? Is there a performance level around the updating of MSATS. Will it be in the rules? Or the agreed "Service and performance" levels OR agreed by NSSC? But they are common and not NMI specific?? Are there any penalties? x

33 Customer service PE discussed with MG. The meter receives commands in the sequence sent and reacts to those commands independently. For example, if an ARM command is received with the SC open, the meter will react to that command. During the ARM timeout period, if a close command is received by the meter then the meter will react to that command (and hence close the SC). The FS is silent on the reaction of the meter to sequential commands and this will be clarified in v027 of the FS. AGL 24/2/10: Has there been a decision on this by NSSC? DNSP only FRMP only? PE: MG confirmed that this matter has not been discussed at the NSSC. The decision will either be made in the RWG or be left to the BPPWG to resolve. As a prompt, this point has been noted on the principles slide. Note: on a better understanding of the use of this function, PE has changed the focus from the DNSP (who operates the SMMS) to the FRMP (who will initiate the request). SMI Functional Specification v0.26 #7.7 (page 29) Requirements a) Meters other than a Three Phase CT connected meter without an external supply contactor, shall support functionality to control a supply of the contactor customer. enable the interruption and restoration of supply to customer premises; (i) For all whole current meters the supply contactor shall be integrated into the meter; (ii) For CT connected meters supporting an external supply contactor, a voltage free 2A relay with a rating of 230Vac shall be integrated into the meter. b) In Section Error! Reference source not found. references to the supply contactor shall also apply to the control relay integrated into the Three Phase CT connected meter supporting external supply contactor c) For whole current meters when the supply contactor in the meter is in the Open position all outgoing (customer side) active circuits for the meter shall remain de-energised; d) Supply contactor operation shall be possible both locally and remotely; e) For meters with a supply contactor it shall be possible to display the status of the supply contactor on the visible display (refer Error! Reference source not found.). The possible supply contactor status is: (i) On (supply contactor in the closed position) (ii) Monitor Supply (supply contactor in the closed position) (iii) Armed (supply contactor in the open position) (iv) Off (supply contactor in the open position) (v) Supply Capacity Exceeded (supply contactor in the open position, visible display shows the remaining time before the supply contactor is automatically switched to the On state) f) The SMI shall support separate commands for switching the supply contactor 1. The four supply contactor switch commands are: (i) Close command (ii) Monitor Supply command (refer ) (iii) Arm command (refer Error! Reference source not found.) (iv) Open command Monitor Supply g) The meter shall support a Monitor Supply (auto-off) function such that if the measured exported active power is above a programmable level after receiving the Monitor Supply command, the supply contactor will automatically switch to the Off state (open position). h) When the Monitor Supply Load command is used: (i) The meter shall automatically switch the supply contactor to the off state (open position) if more than X Watts of active power is measured by the meter for more than Y seconds during the measurement period of Z seconds after the meter receives the command, where: (a) (b) (c) X range: 20 W 25 kw programmable in 20 W increments; Y range: 1- Z seconds programmable in 1 second increments; Function Supply Contactor operation ON/OFF #7.7 AGL : This is for a default ARM. AGL s comments refers to timing out ARM before its usual time setting on the request Z range: 1-3,600 seconds programmable in 1 second increments; Discussed with MG. Start with the meter in the open state. There are two actions to this function. First, the SMMS Operator (DNSP) sends a ARM command to the meter. The meter primes the Supply Contactor in the ARM state in readiness for a further command (the close command). The second command is initiated from a button on the meter enclosure that can be operated by a person in the local vicinity of the meter. In addition, a meter setting would be configured to enable the priming action to time out so that the ARM command becomes inactive after an elapsed period. AGL : in addition to ARM timeout, there should also be an ARM override so that the FRMP can override ARM or Arm timeout and close the supply contactor from the retailer back end systems on the request of the customer (where the meter box is not easily locatable / accessible). Section x 1 Refer Error! Reference source not found. for switching matrixes and configurations BPPWG process maps customer services v03 Continues on pages 30 and 31 PE note Slide 33

34 Customer service Function Supply Contactor operation ON/OFF #7.7 SMI Functional Specification v0.26 #7.7 (page 30) (a) For CT connected meters (with 2A relay) the measurement of X shall be the value measured by the meter, the meter does not need to know the CT ratio and is not required to calculate the customer load; (ii) The meter shall report to the SMMS when the supply contactor has been automatically switched to the off state (open position) due to the measured load exceeding the Monitor Supply settings; (iii) The meter shall store a Quality of Supply event when the supply contactor has been automatically switched to the Off state (open position) due to exceeding the Monitor Supply settings Arm a) When the meter receives an Arm command, the meter shall ensure that the supply contactor is in the open position. The meter shall have a clear visible indication that the supply contactor is now in the Armed state. b) When the meter is in the Armed state it shall be possible for a customer to change the meter from the Armed state to the On state (supply contactor in the closed position). A meter event will be stored in the Quality of Supply Event log to indicate that the customer has moved the supply contactor to the On state. c) The meter shall support a configurable arming time out period. If during the arming time out period the customer does not turn the supply contactor to the On state the meter shall automatically return to the Off state. A meter event will be stored in the Quality of Supply Event log to indicate that a time out has occurred. The arming time out period shall be programmable from 1 hour to 48 hours in 1 hour increments Supply Contactor Functionality for Meter Loss of Supply d) The meter shall support an option to switch the supply contactor to the open position when meter loss of supply is detected. If this option is enabled the meter shall ensure the supply contactor is in the open position during meter loss of supply. Upon supply restoration the meter shall restore the supply contactor to the state before meter loss of supply. It shall be possible to locally and remotely enable and disable this option Smart Metering Infrastructure Performance Levels e) For individual meters, the supply contactor switch command will be acknowledged by 90% of meters within 10 minutes; f) The total number of turn on/turn off commands to individual meters in any 10 minute period shall be no greater than 0.015% of the installed, operational SMI meter population in a distribution network area; g) The SMMS shall report exceeding the Monitor Supply settings within 10 minutes of the supply contactor being switched for 99% of meters; h) The total number of supply contactor switch commands in any 24 hour period can be up to 0.5% of the installed, operational SMI meter population in a distribution network area Participant Service Levels i) For individual meters: (i) Command performed and supply contactor operated at 90% of meters within 1 hour (ii) Command performed and supply contactor operated performed at 99% of meters within 3 hours BPPWG process maps customer services v03 Continues on page 31 Slide 34

35 Customer service Function Supply Contactor operation ON/OFF #7.7 SMI Functional Specification v0.26 #7.7 (page 31) The total number of supply contactor commands to individual meters in any 24 hour period can be up to 2% of the installed, operational SMI meter population in a distribution network area. BPPWG process maps customer services v03 Slide 35

36 ERGON comments Function Supply Contactor operation OFF #7.7 ACTIVITY DIAGRAM REVIEW AS 29/06/10: agreed that all matters had been attended resolved x BPPWG process maps customer services v03 PE note Slide 36

37 ENERGEX comments Discuss Function Supply Contactor operation OFF #7.7 ACTIVITY DIAGRAM REVIEW Who will manage and ensure that the customer impacts of a smart meter function are in the best interests of the end use customers? Are there other ways to achieve the same end goal e.g. turning off of discretionary appliances via the HAN, Improved business intelligence provided by smart meters. The standing data that will be recorded in the MSATS environment and it's timeliness will be critical in the decision making processes. How to ensure that Life Support details are up to date for the retailers? Checks will still need to be performed by the DNSP's to address Life Support and disconnection requests for community power (safety). How to advise that a variation of the certainty of service has occurred e.g. comms issues or comms may be available but just doesn't turn the contactor off. Guarantee service times must take into consideration the communication issues as the DNSP might be able to complete with 2 hours of receipt or within 2 hours of comms becoming available or within 5 days if a physical site visit is required. New completion responses will be required to keep the retailer appraised of any variation to the expected response times. The DNSP will provide a SO completion response which will confirm the work was completed and the relevant product code/s associated with the requested work. BPPWG process maps customer services v03 Slide 37

38 AGL comments (1) Slide 30 New principle: Retailers can switch-off a connection point faster using remote operation of the Supply Contactor. Transferred to Principles slide Function Supply Contactor operation OFF #7.7 ACTIVITY DIAGRAM REVIEW Discussed with SB. A suitable replacement principle might be: Retailers can switch-off a connection point faster using remote This is not an approved concept. Remote allows for us to perform faster operation and more of the Supply efficiently NOT do it at all as liability is with the FRMP for illegal use and Contactor. vacant sites? Is the context of "Fuse removal"? Or Does it mean the site is never de-energised? Customer Site details notification for Life Support, should be reviewed for this aspect. Is this ad hoc information? Activity Diagram modified to include Life Support as one activity at the nominated point. Replace LNSP by SERVICE PROVIDER As discussed in CSFn7.6. Agreed to retain DNSP as reference entity in Events & sequence line. 1. The 3rd party is the FRMP Yes, as discussed in CSFn7.6. 3rd Party changed to generic reference. x Add here: existing and new standing data information PE confirmed that the send response was part of the B2B process arrangement. SB agreed that this comment should be assigned to the update MSATS standing data activity. PE to record comment on Activity Diagram What is the "Guarantee"? It is as per the rules? Or the agreed "Service and performance" levels OR agreed by NSSC? But they are common and not NMI specific?? Are there any penalties? SB to raise with BRWG. PE to add as note to Activity Diagram. SB would also like this comment to apply to update MSATS standing data BPPWG process maps customer services v03 PE note Slide 38

39 AEMO comments (1) Function Supply Contactor operation OFF #7.7 ACTIVITY DIAGRAM REVIEW Methodology Step Step - 1 Step - 2 Step - 3 Step - 4 Step Description Identify Applicable SMI Function/Topic Identify Business Trigger that applyto this function Identify if business triggers fit within existing market processes, if yes, list. If no new process may be required) List sub process steps of the market processes ~ both current and potential new ones (if applicable) Findings Function # 7 Switching Supply Contactor ON/OFF Changing the status of a site by switching the Supply Contactor ON or OFF 1. De-Energisation (OFF) 2. Re-Energisation (ON) 3. NMI Data Update 1. De-Energisation (Retailer and DNSP initiated) ~ Prevent Consumption (Non Payment, Unauthorised, No access etc) ~ Move Out ~outage ~Defect ~Saftey ~No Access ~Load Management 2. Re-Energisation (Retailer and DNSP initiated) ~Post Prevent Consumption Recovery (Non Payment, Unauthorised, No access etc) ~ Move in ~ NSW New conneciton ~Post outage ~Post Defect ~Post Saftey ~Post No Access ~Post Load Management x These should be broken down into more detailed activities see CSFn7.7 pages in spreadsheet BPPWG process maps customer services v03 PE note Slide 39

40 AEMO comments (2) Function Supply Contactor operation OFF #7.7 ACTIVITY DIAGRAM REVIEW Step - 5 Step - 6 Step - 7 Step - 8 Step - 9 Identify exising NEM Procedures that will be impacted by the new function. Observations/Assumptions Identify clauses in each identified procedure that will most likely need to change. E.g. Where in the procedure does contactor status or interval meter definately impacts the procedure? Identify clauses in each identified procedure that may need to change. E.g. Where in the procedure does contactor status or interval meter may possibly impact the procedure? Touch points external to this Function that may be impacted 1. MSATS Procedures - CATS Procedure 2. B2B Procedure - Service Order Process 3. Standing Data for MSATS 1. MSATS - CATS Procedure 2.4 (j), (l) 2. B2B Service Order Process 2.1 (a) 2.3 (a) (a) ii 2.9 (a) (b) (a) (d) 1, Standing Data for MSATS 6 1. MSATS - CATS Procedure 2.3(b) (a), (c), (f), (u), (o) 11.4 (c) B2B Service Order Process (b), (e) (a), (d), (e) 3. Standing Data for MSATS N/A 1. Changes to the procedures are dependant on solution used to apply function. 2. B2B Technical delivery and Techincal Guidelines may need to be addressed. 1. Customer Transfers (if customer is changing retailer) 2. B2B Build Pack 3. BDPIP Processes Transferred to relevant procedure pages for CSFn7.7 in spreadsheet. Matched to appropriate activities arising from process map (Activity Diagram analysis) x BPPWG process maps customer services v03 PE note Slide 40

41 Customer service Events & sequence (FRMP): FRMP conversation with customer o Accommodation status: Move-in Move-in + no power at site o Clarification of site requirements o Safety related information from customer: Additional information required to be satisfied that remote operation of Supply Contactor can be requested Understand connection point status (from MSATS or other database) o NMI status o Metering installation classification o Meter type (SM, AMI or other) o Meter attributes: Meter configuration details Energy measurement channels that have been configured Customer Service function settings o Meter contactor status o Fuse status o Period of disconnection Decision options for type of Service required: Fuse REPLACE Supply Contactor ON Close remotely or locally Customer ON Fuse REPLACE + Supply Contactor ON Request supplementary information from DNSP: o Generally for exceptional circumstances Receive published service information from DNSP: Assess annual cost and service timing publication Conditions applicable to each Service Order type FRMP preference: o Advice to customer: Arrangements needed to vary connection point status Actions to be undertaken Time that supply will be connected: Expand?? o Customer agreement with arrangements FRMP decision to request DNSP : o To operate Supply Contactor or main fuse Type of B2B Service Order to be submitted?? o What if status information is incorrect?? MSATS has to be updated. IF the status information is incorrect, as soon as the CR is raised, the relevant participants should ensure the CATS tables are up to date in real time Meter attributes and capabilities should be available at NMI discovery and the other SM details like HAN details etc can be a part of the CATS CR. request / receive B2B receive / respond Events & sequence (DNSP): Receive request from FRMP for connection point status o Validate B2B Service Order o Acknowledge request o Provide relevant information to FRMP Receive request from FRMP for supplementary information o Validate B2B Service Order o Acknowledge request o Provide relevant information to FRMP Receive request from FRMP to turn Supply Contactor ON o Check pre-conditions o Acknowledge request o Activate by remote command (what if comms fails??) o Activate by Local action Receive request from FRMP to replace main fuse Respond to auto disconnection when SC switched ON Clarify site connectivity (site statistics discovery) Publish cost of service (annually) o Include certainty of service (likelihood of success) o Guaranteed time of service Update standing data in MSATS : o Existing standing data o New standing data o If request by FRMP is found to be based on wrong information Function Supply Contactor operation ON #7.7 (3) Red text means to be discussed BPPWG process maps customer services v03 (4) Purple text means a change to the slide from last version Slide 41 Examine Access and Security Event Log Events & sequence (pending-frmp): FRMP conversation with customer o Accommodation status o Clarification of site requirements o Safety related information from customer: Understand connection point status (from MSATS or other database) Decision options for type of Service required: Request information from DNSP: Receive published service information from DNSP: FRMP preference: o Advice to customer: o Customer agreement with arrangements FRMP decision to request DNSP: o To operate Supply Contactor or main fuse Type of B2B Service Order to be submitted?? o What if status information is incorrect?? Real-time (clarify??) report on connection point status (needs to be available) MSATS environment: Real-time information flows?? Update report on connection point status (note jurisdictional differences) (1) SC means Supply Contactor (2) Green text indicates interface traffic ACTIVITY DIAGRAM Include New CATS tables for New SMART METER Function attributes, capabilities at the site, HAN etc Real time service checking should be available to New FRMP. MSATS has to be updated. IF the status information is incorrect, as soon as the CR is raised, the relevant participants should ensure the CATS tables are up to date in real time MSATS AEMO ( 25/3/10) raised a limitation with the bilateral agreement and its application to the SMI. This comment raises a question of whether the bilateral agreement provision in clause 2.3(a) of the B2B Service Orders procedure applies to SMI?? For discussion.

42 ERGON comments Function Supply Contactor operation ON #7.7 ACTIVITY DIAGRAM REVIEW AS 29/06/10: agreed that all matters had been attended resolved x BPPWG process maps customer services v03 PE note Slide 42