Business Process and Procedures Workstream Role ... Smart Metering Program Business Process and...

National Smart Metering ProgramNational Smart Metering Program

Business Process and Procedures Workstream

Role Requirements Paper SMI De-en process Version Number: Version 0.5

Status: Draft

Author: P Egger

Date Published: 27 June 2010

File Name: bppwg workshop 14 outcome - bp01 - role requirements de_en v0.5 (marked).docx

Deleted: business

Comment [PE1]: Deleted to align with ‘short title’

Deleted: 4

Deleted: 21

ROLE REQUIREMENTS PAPER (SMI De-en process)

File Name: BPPWG workshop 14 outcome - BP01 - role requirements De_en v0.5 (marked).docx Security Classification: Unrestricted of 41


[Table of Contents] Version History: Version Date Description of change Amended by v0.1 27 May 2010 Initial version prepared from workshop#12 P Egger v0.2 07 Jun 2010 Reworked for workshop#13 P Egger v0.3 18 Jun 2010 Reworked from workshop#13. Flowchart moved to

Attachment A, Control Point Records incorporated into document at Attachment B, Process step descriptions introduced in initial form at Attachment C. Table of Contents and hyperlinks added.

P Egger

v04 21 June 2010 Revised in conjunction with Stakeholder Feedback comments arising from workshop#13.

P Egger

05 27 June 2010 Revised to accommodate Stakeholder Feedback received up to COB 25 June. Released to enable discussion at workshop#14

P Egger

General Suggestions Table: FR#(1) Suggestions (2)(3) Supported by (4) Count

A.5 Cover Page –certain sections require modification or clarification as per the suggesting wording: Introduction - This Cover Page has been prepared to represent the following Proposed NEM business processes that have been used for the development of User Requirements: 3. Objective - The objective of the Role Requirements analysis is to determine the requirements of each Role that will use the nominated business process when SMI capability is available to that process. 4. Scope - The Role Requirements analysis for all Proposed NEM business processes has been restricted to the mandate period. 6. Common Role Related Principles – please clarify principle.

AEMO 1

A.6 Replace all references of ‘needs’ to ‘requirements’ as this is a requirements paper

AEMO 1

A.7 ATTACHMENT 3 - Control point records – This information is useful however the records take up too much space in the document and contain solutions. Suggest using the ‘what’ the ‘when’ and the ‘who’ and use that in the main section to identify the requirements. And remove the ‘Where’ and ‘how’ as they are solution based and should not be documented in a requirements paper. Suggest using them in the ‘solutions paper’.

AEMO 1

5.0 The term “NEM Business Process” needs to be defined. Service Order or Meter Data is a NEM business process, ‘de-energisation’, ‘re-energisation’ etc are not.

AEMO 1

8.0 The word “De-en” is an abbreviation and does not describe the process effectively. SMI De-Energisation process. This should be consistently used throughout the document.

AGL 1

8.1 AEMO suggests that the objective of the de-energisation process is reworded as per suggested wording. The objective of the SMI De-en service Process is to prevent unauthorised consumption of customers consuming electricity without authorisation by the FRMP when electrical safety isolation is not required.

AEMO 1

9.0 d) SMI De-en covers remote opening of the Supply Contactor only. AGL 1

Deleted: 27

Deleted: Revised to accommodate Stakeholder Feedback received up to COB 25 June. Released to enable discussion at workshop#14




FR#(1) Suggestions (2)(3) Supported by (4) Count ADD: This process also covers local opening of the supply contactor for exception purposes.

9.1 Uncertain of the scope of the scope. Are the items within the scope defined for the process or the solution? Scope item (d) appears to be the only scope item that is an accurate scope statement. Should the document contain what is ‘out of scope’? i.e. Re-energisation process. 9. (d) SMI De-en process covers remote operation opening of the supply Contactor only.

AEMO 1

9.a.1 ‘An SMI De-en service request can only be initiated by the FRMP’

Suggest adding the word ‘current’ before FRMP to remove any ambiguity around connection/disconnection requests from multiple retailers. ‘An SMI De-energisation service request can only be initiated by the current FRMP’. This should be consistently used throughout the document

AGL 1

9.a.2 ‘An SMI De-en service request can only be initiated by the FRMP’. The group should consider the situation where the current retailer sends a de-enegisation request where a re-energisation has been requested within a specified timeframe, whether this is from the same or prospective retailer.

AEMO 1

9.b & c b. The SMI De-en service request can only seek to stop supply at a premise for the purpose of (a) move out, (b) non-payment, and (c) satisfying a customer request’ c. The SMI De-en service request must not be used to request electrical safety isolation at a connection point. Suggest combining points b and c as the later clarifies the first point.

b. The SMI De-energisation service request can only seek to stop supply at a premise for the purpose of (a) move out, (b) non-payment, and (c) satisfying a customer request’. The SMI De-energisation service request must not be used to request electrical safety isolation at a connection point.

AGL 1

10.0 The identified business processes support the new SMI functionality, they are not assigned functions. Please update description to reflect the suggested wording.

AEMO 1

11.0 Add Local Retailer (LR) AGL 1 11.1 1. The Roles defined must be participants in the NEM who need to

know the status of the Supply Contactor, i.e. the customer and the Market System are not participants in the NEM. The supply contactor status does not impact the status of the NMI…or does it? Have we defined that yet? The only Roles applicable are as per suggested wording. 2. Update description to reflect the suggested wording.

AEMO 1

13.2 AEMO Suggests that the GRAPL limitations are not required in the requirements paper. If there is a preference by the other members to add the summary of the GRAPLS, the ‘limitations’ should be translated into ‘issues’ without referencing to solutions. Issues can then be used in the ICF/Whitepaper. As per the suggested wording: NSMP07 “Supply Contactor Operation dot point 2 – limitation # 2, 3, 7, 6, 8, 9, 10, 12.

AEMO 1




FR#(1) Suggestions (2)(3) Supported by (4) Count # 2, 7, 8, 9 –Current De-en times require review to ensure they are applicable do not cater for SMI operation. # 6 –Current Applicable events and their codes may require review to ensure they are applicable for SMI operation. limit reasons why SMI did or didn’t operate # 3 – Due to additional SMI functionality, Tthe FRMP may requesting supplementary additional information from the DNSP. # 10 – The Current CATS_NMI_Data table will require review to ensure all SMI data are included may limit operation of Supply Contactor

# 12 – As a result of additional SMI functionality, there is a requirement to introduce new transactions between the The FRMP sending a request to and the DNSP.

15.7 (common

f)

[Current wording:] Where the De-en service can’t be performed by the SMI, the CSFP will advise the current FRMP. [Suggested wording:] Where the De-en service can’t be performed by the SMI remotely, the CSFP will advise the current FRMP.

AGL 1

15.8 (common

g)

[Current wording:] A FRMP can request SMI De-en to be applied to a meter level. [Suggested wording:] A FRMP can request SMI De-en to be applied at either a NMI or meter level.

AGL 1

15.9 (common

i)

Need to remove references to solutions in [describing] principles. [The] suggested wording for 15.(i) [is as follows]: [Suggested wording:] A De-energisation service request will not be used by a FRMP to de-energise a customer’s site if the customer has requested the site to be isolated so as to allow electrical work to be performed at the premise. In this case, an Additions and Alterations request must be used.

AEMO 1

15.10 (common

j.1)

[Current wording:] Where a De-en service request does not contain a preferred time, only a preferred date, the CSFP will batch service requests and the batch process will be performed in accordance with the agreed service levels [TBD]

Assuming a solution is not preferred while defining role requirements. [Suggested wording:] Remove (j) or remove the batching solution to ensure that the principle is agnostic of how this is done.

AGL 1

15.11 (common

j.2)

This [the above current wording] implies a solution (batching) rather than a principle.

Where a De-en service request does not contain a preferred time, only a preferred date, the CSFP will execute in accordance with the agreed service levels.

AGL 1

15.12 (common

k)

[Current wording:] If the remote opening of the Supply Contactor is not possible the DNSP will (a) advise the FRMP of this situation, and (b) advise the FRMP that the Supply Contactor will be opened remotely or locally but not before the original scheduled time.

[Suggested wording:] Replace DNSP with CSFP

AGL 1

16.0 Process for verifying standing data (CP#02). step BP01.9 ‘Obtain and send Information’.

AGL 1




FR#(1) Suggestions (2)(3) Supported by (4) Count A step needs to be included for the CSFP to query the market systems to determine if the data that current FRMP requested verification on is out of alignment. If the information is different then the CSFP should obligated to update the market systems. Modify flowchart and add a new principle

16.1 AEMO suggests that the Process Flowcharts is moved to the start of the document as the analysis of the flowchart highlights the requirements for this paper.

AEMO 1

18.0 CSFP is not a NEM participant therefore should be removed. AEMO 1 20.0 This “RP[DNSP]” needs to be replaced with the DNSP as per section 11. AEMO 1 21.0 The customer is not a NEM participant therefore should be removed. AEMO 1

Notes: (1) FR# means Feedback Register ‘section reference’ number. (2) The suggestions’ are made up of the ‘concern/issues’ followed by ‘suggested wordings’ as recorded in the Feedback

Register. Suggestions that do not adequately state the ‘concern/issue’ or the ‘suggested wording’ have not been recorded in this Table.

(3) General suggestions also include suggestions on any matter, after that matter had been discussed at a workshop. (4) Generally, there are 11 companies represented at WG workshops, viz: AGL, Origin, TRUenergy, CPPCA, SPAN,

Jemena, EA, IE, CE, Ergon, AEMO. (a) The suggestion needs to be supported by 6 or more companies for the suggestion to be implemented. Support

is to be registered through the Stakeholder Feedback facility (that is a ‘count’ of 6 or more means that the suggestion will be implemented).

(b) Discussion of these matters in a workshop forum will not be scheduled, as such discussion will put at risk the achievement of the timetable.

(c) A member of the workshop (in forum) may request discussion of any suggestion but the request will require a majority of WG members to support the request for the discussion to proceed.

(d) Working Group members in a workshop forum may determine whether or not a suggestion is implemented without the need for formal registration of individual support through the Stakeholder Feedback facility.




Contents: [Version History]

1. RRP No: 2. Version: 3. Status: 4. Date: 5. Long Title: 6. Short Title: 7. References: 8. Objective: 9. Scope: 10. SMI Functions: 11. Roles: 12. SMI visual context: 13. Limitations with existing NEM Procedures: 14. Role Functionality Tables: 15. Role Related Principles: 16. NEM business process flowchart: 17. Current FRMP unique needs: 18. CSFP unique needs: 19. MDP unique needs: 20. RP[DNSP] unique needs: 21. Customer unique needs: 22. AEMO unique needs: 23. NEM Requirements: 24. Infrastructure Performance Level: 25. Participant Service Levels: 26. Customer Service Standards: 27. Progress reporting: 28. Endorsed: Attachment A – Flowchart Attachment B – Control Point Records Attachment C – Description of process steps within each entity

The hyperlinks can be used to navigate to and from a chosen Line Item in the paper.

1. RRP No: NSMP BP 01 [back]

2. Version: 0.4 [back]

3. Status: Draft/Final [back]

4. Date: 27 Jun 2010 [back]

5. Long Title [back]

NEM Business Process – De-energisation service using the SMI

6. Short Title [back]

SMI De-en process

7. References: [back]

The following documents have been referred to in preparing the SMI De-en process: (a) MCE Statement of Policy Principles - refer to Section 3.2 of Workshop Manual]

(b) SMI Functional Specification (draft v0.26, dated 22 April 2010);

Comment [PE2]: These 3 Sections are now redundant with the Version History. I suggest that they be deleted.

Deleted: Common needs

Comment [PE3]: Added by PE to provide the context, which is applied when the expression is used in sentence construction.

Comment [PE4]: SB to advise of which principles are applicable to De-en. If general, should this be moved to the cover page?




(c) NSSC ‘Access and Contestability’ Policy Principles (draft v5, dated 21 April 2010);

(d) Chapter 7 Rules changes (draft vxxx, dated May 2010);

(e) NSSC ‘Load Management and Network Security’ protocol <<to be provided>>

(f) NSSC ‘Communications and Data Security’ protocol <<to be provided>>

(g) VIC AMI Process Model, as discussed and presented by WG members.

8. Objective: [back]

The objective of the SMI De-en process is to prevent customers consuming electricity without authorisation by the FRMP when electrical safety isolation is not required.

9. Scope: [back]

(a) An SMI De-en service request can only be initiated by the FRMP.

(b) The SMI De-en service request can only seek to stop supply at a premise for the purpose of (a) move out, (b) non-payment, and (c) satisfying a customer request’.

(c) The SMI De-en service request must not be used to request electrical safety isolation at a connection point.

(d) SMI De-en covers remote opening of the Supply Contactor only.

(e) Status of the Supply Contactor in this process relates to ‘normal supply conditions’ at a connection point and does not include instances where the Supply Contactor is opened for other reasons (for example: network security, supply capacity control).

10. SMI Functions: [back]

The following functions have been assigned to this business process: (a) Function #7.7: Supply Contactor Operation.

(b) Function #7.10: Quality of supply & other Event Recording.

(c) Function #7.12: Remote Service Checking.

(d) Function #7.2: Remote Acquisition.

(e) Function #7.20: Meter Communications: Issuing Messages and Commands.

11. Roles: [back]

The following entities are directly involved in this business process:

(a) Current FRMP;

(b) Service Provider [CSFP];

(c) Service Provider [MDP];

(d) Responsible person [DNSP - mandate];

(e) Customer;

(f) Smart Meter;

(g) Market Systems;

(h) AEMO.

12. SMI visual context: [back]

The Schematic Diagram for that part of the SMI De-en process that occurs at the Smart Meter is shown in Diagram 1. In the diagram, the red dotted boxes indicate the parts of the meter affected by this business process. The meter is shown with a Supply Contactor, a measurement element and the ‘Meter Event Log” (representing all meter Event Logs). Inbound and outbound commands for Remote Service Checking are shown. The ‘Meter Communications: Issuing Messages and Commands’ is assumed to be part of the features of the SMMS.

Deleted: service




Diagram 1: Schematic representation of SMI De-en

This diagram represents the impact of the 5 nominated functions on SMI De-en.

13. Limitations with existing NEM Procedures: [back]

Refer to GRAPLs NSMP07, NSMP10, NSMP02 and NSMP20 for details of anticipated limitations when Smart Metering Infrastructure is introduced into the NEM.

NSMP07 “Supply Contactor Operation”:

There is one limitation that is not addressed in existing NEM Procedures and its silence will require a new or altered procedure to remove any doubt in the way this limitation is to be actioned by each Role. It relates to:

• The DNSP initiating the operation of the Supply Contactor (Limitation#1).

There are 28 limitations that raise questions about IT support systems or principles of behaviour that will or may require a new process to emerge and be adopted by the Roles. In general, the limitations relate to:

• De-en times do not cater for SMI operation (Limitations#2, #7, #8, #9);

• The FRMP requesting supplementary information (Limitation#3);

• Definition of De-en is too narrow to permit SMI operation (Limitation#4);

• Certain rules may limit requests to operate the SMI (Limitation#5);

• Applicable events and their codes may limit reasons why SMI did or didn’t operate (Limitation#6);

• CATS_NMI_Data table may limit operation of Supply Contactor (Limitation#10);

• Information on Connection Point status needs to be automated (Limitation#11);

• The FRMP sending a request to the DNSP (Limitation#12, several points);

Register(data channels)

1

Settings:1234567

Smart Meter

Supply Contactor

Incoming power supply

operation signals, messages, settings

premise general power supply

SMMS

Smart Meter Communication Network

7.6 load management(dedicated load contactor)

acknowledgements, setting status information,

Event Log information

7.7 switching supply contactor (ON, OFF)

Enabled parameters

Load control circuit to one appliance

7.12 Remote service checking status (push)

common

2A relays

common

75% mode

50% mode

31.5A ‘contactor’

7.6 load management(1 or more relays)

On & OFF pulses

7.9 Master HAN Device

Acknowledgement, Slave HAN Device alarms

Slave HAN

Device

7.9 HAN codes (registration, re-registration, deregistration)

Load contactor#1

Relay#1

Utility HAN

Acknowledgement, Slave HAN Device alarms

Meter Event Log

Event Log information (pull)

7.10 QOS & other event recording

7.12 Remote service checking

Supply contactor7.7 switching supply contactor

WWWMeasurement

element

7.1 energy data(active, reactive)

• Export & Import• Active and reactive• Net energy• Interval value• Cumulative value

7.2 remote acquisition (pull) (active, reactive)

7.20 Meter Communications: issue messages and commands




• The DNSP sending information to the FRMP in response to a request (Limitation#12, several points);

• The DNSP updating market systems (Limitation#2).

A new or altered procedure may be required to control the operation of the IT system or key elements of any new process.

NSMP10 “Quality of Supply and Other Event Recording”:

There are three limitations that are not addressed in existing NEM Procedures and their silence will require a new or altered procedure to remove any doubt in the way these limitations are to be actioned by each Role. They relate to:

• Meter alarm attributes (Limitation#1);

• Meter Event Log attributes (Limitation#2);

• Collection of ‘translated’ event data by DNSP (Limitation#4);

There are two limitations that raise questions about IT support systems or principles of behaviour that will or may require a new process to emerge and be adopted by the Roles. In general, the limitations relate to:

• The DNSP receiving a request from the FRMP (Limitation#8 (c));

• The DNSP sending information to the FRMP in response to a request (Limitation#8 (d)).


NSMP12 “Remote Service Checking”:

There are four limitations that raise questions about IT support systems or principles of behaviour that will or may require a new process to emerge and be adopted by the Roles. In general, the limitations relate to:

• The FRMP requesting and receiving status information from the DNSP (Limitation#1 (a) & #1(b));

• The DNSP sending information to the FRMP in response to a status request (Limitation#1 (c) & #1(d)).


NSMP02 “Remote Acquisition”:

There are no limitations that require changes to NEM Procedures for remote acquisition in regard to SMI De-en.

NSMP20 “Meter Comms – Issuing Messages and Commands”:

There are no limitations that require changes to NEM Procedures for Meter Communications: Issuing Messages and Commands in regard to SMI De-en.

14. Role Functionality Tables: [back]

The relationship between the entities and the ‘characteristics’ of the technology (as recorded in the SMI Functional Specification) are shown in the following Tables. In these tables, a tick indicates that an entity has an interest in the specified characteristics of the function, whereas a ‘cross’ indicates that an entity has no interest in those characteristics.

The extent to which an entity is interested to know that the Supply Contactor has been switched to the OFF position (equivalent to the contactor being in the Open state) is shown in Table 1, as follows:

Deleted: , point

Deleted: , point

Deleted: , points

Deleted: , points

Comment [PE5]: Need to rework process maps into spreadsheet and gap analysis to confirm if this is an accurate statement.




Table 14.1: Position of Supply Contactor (Fn#7.07)

The extent to which an entity is interested to know that the Supply Contactor will be switched to the OFF position by an Open command is shown in Table 2, as follows:

Table 14.2: switching commands to the Supply Contactor (Fn#7.07)

The extent to which an entity is interested to know that the Supply Contactor status has been recorded in the QOS Event Log is shown in Table 3, as follows:

Table 14.3: Supply Contactor operation events stored in the QOS Event Log (Fn#7.10)

The extent to which an entity is interested to know that the Supply Contactor has been recorded in the Access and Security Event Log is shown in Table 4, as follows:

Table 14.4: Supply Contactor operation events stored in the Access & Security Event Log (Fn#7.10)

The extent to which an entity is interested to know the setting status of routine acquisition of metering data is shown in Table 5, as follows:

Supply Contactor position states FRMP CSFP MDP RP [DNSP] Customer Market AEMO Explanation SettingsSystems

ON - normal Closed total supply within the limits of settingsON - monitor supply Closed export active power level exceeded >> 20w to 25kW in 20W increments (X)ON - monitor supply Closed export active power level exceeded >> 1 to Z secs in 1 sec increments (Y)ON - monitor supply Closed export active power measurement peeriod >> 1 to 3,600 minutes in 1 sec increments

ON - Armed Armed supply contactor in OFF position >> 1 to 48 hours in 1 hr incrementsOFF - normal Open premise is without supply

OFF - supply capacity exceeded Open monitor supply' setting exceeded as aboveOFF - meter loss of supply Open loss of supply to meter enable / disable

switching commands FRMP CSFP MDP RP [DNSP] Customer Market AEMO ExplanationSystems

Close hold in ON positionMonitor switch OFF

Armed switch ON when Armed condition aceptedOpen hold in OFF position

Meter events stored in QOS Log FRMP CSFP MDP RP [DNSP] Customer Market AEMO ExplanationSystems

Meter Loss of Supply Power restoration

Under/over voltage event startUnder/over voltage event end

Under voltage event minimum voltageOver voltage event maximum voltage

Supply contactor status has changedCLC or relays status changed by priority over-ride

Boost activatedHAN messages acknowledged

HAN interace load control report event exception statuscustomer supply monitoring possible fault in premise detected

network tariff update received

Meter events stored in A&S Log FRMP CSFP MDP RP [DNSP] Customer Market AEMO ExplanationSystems

Tamper detectedImport energy detected (if not configured to measure this flow)

Accumulated energy flows set to zeroMeter settings changed (remotely or locally)

Meter clock adjusted by more than 20 seconds + valuesoftware upgrade status completed or failed

Meter error flags all recordedMeter warning flags all recorded

HAN device has joined the meter's Network Coordinator




Table 14.5: remote operation – routine acquisition (Fn#7.02)

The extent to which an entity is interested to know that special reads of metering data are available shown in Table 6, as follows:

Table 14.6: remote operation – special read (Fn#7.02)

The extent to which an entity is interested to know that special reads of metering data are available shown in Table 6, as follows:

Table 14.7: remote operation – remote service checking (Fn#7.12)

There is no functionality in the Smart Meter for Function 7.20 “Meter Communications: Issuing Messages and Commands” that impacts on the SMI De-en process.

15. Role Related Principles: [back]

The Role related principles for the FRMP and the DNSP are as follows:

FRMP:

(a) In conjunction with a SMI De-en completion notification, the FRMP requires meter data. [The DNSP requires a timeframe in order to consider the merits of this principle]

DNSP:

(a) There are no unique principles for the DNSP.

Common:

(a) The retailer has an option to not request a De-en service in circumstances where a minimum supply service can be retained at the customer’s site.

(b) Where the SMI is available, a remote De-en service must only be performed if it meets its jurisdictional safety obligations.

(c) The current FRMP requires visibility of the current Supply Contactor status.

routine acquisition FRMP CSFP MDP RP [DNSP] Customer Market AEMO SettingsSystems

interval energy data enable and disableaccumulated energy data enable and disable

meter event logs enable and disable

Special Read FRMP CSFP MDP RP [DNSP] Customer Market AEMO ExplanationSystems

interval energy data command availableaccumulated energy data command available

meter event logs command available

FRMP CSFP MDP RP [DNSP] Customer Market ExplanationSystems

Supply Contactor ON statusSupply Contactor OFF statusSupply Contactor Monitor suply statusSupply Contactor Exceed supply capactity statusSupply Contactor Exceed supply capactity state time remaining before switching to ONSupply Contactor Armed status

Instantaneous voltage value at meter per phaseActive power total net importedActive power total net exportedActive power total per measuring element importedActive power total per measuring element exported

HAN statusOther status indicators watch this space!!




→ The Supply Contactor state (Open and Closed) and NMI status are to be readily visible to a current FRMPfollowing any change of state.

→ Other methods of disconnection are to be visible if they have been applied to the connection point (such as fuse, pole, tails, pit, etc) [AGL]

(d) The DNSP will make visible to FRMP the capability of the SMI for Supply Contactor operation.

→ CSFP to make available the method of disconnection to the market.

→ CSFP to make available the status of the Supply Contactor to interested entities on their request in accordance with agreed service levels.

(e) Where the Minister has mandated the SMI and it is installed [commissioned/operational], the remote operation of the Supply Contactor must be available.

(f) Where the De-en service can’t be performed by the SMI, the CSFP will advise the current FRMP.

(g) A FRMP can request SMI De-en to be applied to a meter level.

(h) The FRMP requires notification that a De-en service request has been completed in accordance with agreed service levels [TBD].

(i) A De-en service request will not be used by a FRMP to de-energise a customer’s site if the customer has requested the site to be isolated so as to allow electrical work to be performed at the premise. In this case, an Additions and Alterations request must be used.

(j) Where a De-en service request does not contain a preferred time, only a preferred date, the CSFP will batch service requests and the batch process will be performed in accordance with the agreed service levels [TBD]

(k) If the remote opening of the Supply Contactor is not possible the DNSP will (a) advise the FRMP of this situation, and (b) advise the FRMP that the Supply Contactor will be opened remotely or locally but not before the original scheduled time.

16. NEM business process flowchart: [back]

The major points of interaction within and between ‘entities’ for SMI De-en is shown in the flowchart contained in Attachment A.

In particular, the flowchart shows the transactions that are external to an entity. It is these transactions that are of most interest in formulating new NEM procedures and in making changes to existing NEM procedures. Each of these transactions cross the interface between the initiating entity and the receiving entity. Control points can be established at these interfaces to enable the details of the transaction at that point to be recorded. Control Point Records are the facility for recording this information.

The Control Point Records for SMI De-en are contained in Attachment B.

17. Current FRMP unique needs: [back]

The FRMP has the following unique needs, which have been summarised from the relevant Control Point Records (the Control Point Record details are to be considered in conjunction with this summary):

In regard to CPR#01, the FRMP requires:

(a) An electronic facility to query Market Systems for the status of the connection point; and (b) 24 hours by 7 day access to the facility; and (c) Automatic turn-around of the query in the Market Systems, for the purpose of obtaining an independent check of the FRMP held information.


(a) An electronic facility to query the CSFP for validating connection point data; (b) Normal office hours access to the facility; and (c) Turn-around of the query within 2 hours of initiating the query, for the purpose of removing any doubt about the accuracy of the information held in the Market Systems.

Comment [PE6]: Point 15.0 in the Stakeholder Feedback Register.

Deleted: List the details specified in the Control Point Record template for each interaction between the nominated Role and each of the entities to which it has a relationship. ¶Control Point Record#01 (details)¶Control Point Record#02 (details)¶etc ………………….¶(There is usually more than 1 Control Point Record for any one Role)¶





(a) An electronic facility to receive validating information from the CSFP; and (b) Normal office hours access to the facility, for the purpose of removing any doubt about the accuracy of the information held in the Market Systems.


(a) An electronic facility to send to the CSFP a request to remotely open the Supply Contactor of a nominated Smart Meter;

(b) Normal office hours access to the facility; and (c) Turn-around of the request within 10 minutes of initiating the query, unless circumstances

require / permit a longer period for the request to be completed. for the purpose of obtaining a de-energistation of a nominated premise within a known time limit.


(a) An electronic facility to receive planned scheduled information from the CSFP; and (b) Normal office hours access to the facility, for the purpose of allowing the FRMP to obtain de-energisation of a nominated Smart Meter within a known time limit.


(a) An electronic facility to receive validating information from the CSFP; and (b) Normal office hours access to the facility, for the purpose of allowing the FRMP to manage customer expectations.


(a) An electronic facility to receive metering data from the MDP; and (b) Normal office hours access to the facility, for the purpose of allowing the FRMP to prepare a bill to serve on the customer outside the normal billing run.


(a) An electronic facility to receive notification from the CSFP that the SMI de-energisation request had been successfully completed; and

(b) Normal office hours access to the facility, for the purpose of informing the FRMP of the day & time that the Supply Contactor was opened.

The current FRMP has summarised these needs in the following way:

(a) The FRMP needs to know the SMI capability of the site [a Service Level is required for updating Market Systems]

o The current requirement is that the FRMP needs to know the SMI capability of the site (AGL)

o A Service Level is required for updating Market Systems (AGL)

o The service levels should not only be on the timeframe to update the system but include accurate information (AGL)

(b) The FRMP needs to determine the type [details?] of Service Order required to be sent to the CSFP [NMI, day, time]

(c) The FRMP needs to send an electronic request for SMI De-en to the CSFP.

(d) The FRMP needs confirmation that the Supply Contactor is open.

Suggestions Table: FR# Suggestions Sponsor

Comment [PE7]: The above summary from reference to the CPRs can be compared to the summary produced from freely considering the information that contributes to the SMI De-en process. Only one summary is necessary. Hence, these two view need to be blended.







FR# Suggestions Sponsor 17.0a Summary (a): Modify by including the following points:

• The current requirement is that the FRMP needs to know the SMI capability of the site

• A Service Level is required for updating Market Systems. • The service levels should not only be on the timeframe to update the

system but include accurate information.

AGL

17.1a Summary (a): the information is insufficient and needs to be more descriptive of the actual requirement. Modify by adding:

• SMI Capability of the site • Enabled/ disabled status • Method of disconnection (pole, fuse, tails, pit, remote SC, local SC) • Service level for updating MSATS. The service level should not only be

the timeframe to update the system but include accurate information.

AGL

17.2a Remove reference to solution as per example in suggested wording: (a) The FRMP needs to know the SMI capability of the site [a Service Level is required for updating Market Systems] o The current requirement is that the FRMP needs to know the SMI capability of the site (AGL ) o A Service Level is required for providing changes to supply contactor status to the market updating Market Systems (AGL)

o The service levels should not only be on the agreed timeframe to update the system but include and accuratecontain information (AGL)

AEMO

17.3

18. CSFP unique needs: [back]

The CSFP has the following unique needs, which have been summarised from the relevant Control Point Records (the Control Point Record details are to be considered in conjunction with this summary):

In regard to CPR#02, the CSFP requires:

(a) An electronic facility to receive information from the FRMP on connection point data; and (b) Normal office hours access to the facility,

for the purpose of removing any doubt about the accuracy of the information held in the Market Systems.


(a) An electronic facility to notify the FRMP of the requested information; and (b) Normal office hours access to the facility; and (c) Internal systems to enable the information to be turned around within 2 hours of receiving the

query. for the purpose of providing the FRMP with the means of performing an independent check of the information held by the FRMP.


(a) An electronic facility to receive information from the FRMP to perform de-energisation of a premise;

(b) Normal office hours access to the facility, and (c) Internal systems to automatically route the request in accordance with agreed service levels.

for the purpose of obtaining a de-energisation of a nominated premise within a known time limit.


Deleted: List the details specified in the Control Point Record template for each interaction between the nominated Role and each of the entities to which it has a relationship. ¶Once listed, remove any common needs to a single record.¶Control Point Record#01 (details)¶Control Point Record#02 (details)¶etc ………………….¶(There is usually more than 1 Control Point Record for any one Role)




(a) An electronic facility to notify the FRMP of the schedule for de-energising the nominated premise in accordance with the request;

(b) Normal office hours access to the facility, and (c) Internal systems to provide notification of the schedule time & day to the FRMP within 1 hours

of receiving the FRMP request. for the purpose of allowing the FRMP to obtain a de-energisation of a nominated premise within a known time limit.


(a) An electronic facility to notify the FRMP of a failure to de-energise the nominated Smart Meter in accordance with the request;

(b) Normal office hours access to the facility, and (c) Internal systems to provide notification of the failure to the FRMP within 30 mins of receiving

information that a SMI failure has occurred. for the purpose of allowing the FRMP to manage customer expectations.


(a) An electronic facility to send a command to the Smart Meter to change the position of the Supply Contactor from ON to OFF;

(b) 7am to 7pm access to the facility on each calendar day, and (c) Internal systems to establish the state of the premise and Supply Contactor prior to executing

the command to the Smart Meter. for the purpose of switching the Supply Contactor to the OFF state.


(a) An electronic facility to receive information from the Smart Meter on the state of the Supply Contactor;

(b) 24 hours by 7 days access to the facility, and (c) Internal systems to automatically assess the information received from the Smart Meter.

for the purpose of allowing the CSFP to determine if the Supply Contactor has changed to the open state.


(a) A facility to visit a premise and locally switch the Supply Contactor to the off position; (b) Normal working day access to the premise, and (c) Internal systems to mobilise a visit to the premise.

for the purpose of allowing the CSFP to fulfil the FRMP request to de-energise the nominated Smart Meter.


(a) An electronic facility to notify the MDP to arrange for a part day special read of the Smart Meter;

(b) Normal business day access to the facility; and (c) Internal systems to automatically create the notification on receipt of information that the

Supply Contactor is in the open state. for the purpose of informing the MDP that a special read should be performed within a short timeframe.


(a) An electronic facility to notify the FRMP that the SMI d-energisation request had been successfully completed;


Supply Contactor is in the open state.




for the purpose of informing the FRMP of the day & time that the Supply Contactor was opened.


(a) An electronic facility to notify the RP[DNSP] that a SMI de-energisation request had been performed;


Supply Contactor is in the open state, for the purpose of informing the RP[DNSP] of the day & time that the Supply Contactor was opened.


(a) An electronic facility to update the Market Systems that a Supply Contactor had been opened in a particular Smart Meter;

(b) Normal business day access to the facility; and (c) Internal systems that will automatically send the required information to the Market Systems.

19. for the purpose of providing a common point for checking the status of the Supply Contactor for each Smart Meter.MDP unique needs: [back]

The MDP has the following unique needs, which have been summarised from the relevant Control Point Records (the Control Point Record details are to be considered in conjunction with this summary):

In regard to CPR#11, the MDP requires:

(a) An electronic facility to send metering data to the FRMP; (b) Normal office hours access to the facility; and (c) Internal systems to collect and process the metering data within the specified time limit, for the purpose of allowing the FRMP to prepare a bill to serve on the customer outside the normal billing run.

20. RP[DNSP] unique needs: [back]

The RP[DNSP] has the following unique needs, which have been summarised from the relevant Control Point Records (the Control Point Record details are to be considered in conjunction with this summary):

In regard to CPR#13, the RP[DNSP] requires:

(a) An electronic facility to receive notification from the CSFP that a SMI de-energisation request had been performed; and

(b) Normal business day access to the facility, for the purpose of informing the RP[DNSP] of the day & time that the Supply Contactor was opened.

21. Customer unique needs: [back]

There are no unique needs for the customer.

22. AEMO unique needs: [back]

There are no unique needs for AEMO.

23. NEM Requirements: [back]

The NEM requirements to allow participants to request, undertake and/or support the de-energisation of a nominated Smart Meter are specified as follows:

Deleted: ¶





Deleted: Common needs

Deleted: Confirm the needs that are common to all Roles.¶(these needs are assembled from the unique needs of each Role identified above)




(a) An electronic facility with access to Market Systems is required to enable participants to search for and identify relevant information and to maintain currency of that information.

[GRAPL#07/02]

(b) Market Systems are required to contain information relevant to SMI de-energisation activities.

[GRAPL#07/3(a)]

(c) An electronic facility to transfer information between participants is required for facilitation of short time frames in which to perform SMI de-energisation activities.

[GRAPL#07/03(b), #07/04, #07/05, #07/06, #07/07, #07/08, #07/09, #07/11, #07/12]

[GRAPL#10/08(c), #10/08(d)]

[GRAPL#12/01(a), #12/01(b), #12/01(c), #12/01(d)]

(d) Rules are required to govern times of access to the electronic facility to allow participants to develop internal processes to support the SMI de-energisation activities.

[GRAPL#07/05, #07/07, #07/08, #07/09]

(e) Rules are required to govern the operation of the electronic facility, including the information that may be or should transmitted between participants.

[GRAPL#07/05, #07/06]

[GRAPL#10/01, #10/02, #10/04, #10/08(c), #10/08(d)]

[GRAPL#12/01(a), #12/01(b), #12/01(c), #12/01(d)]

(f) Rules are required to govern the turn-around time within a participant’s internal business process.

[GRAPL#07/01, #07/03(b), #07/04]

TEST needs:

The ‘common needs’ are to be tested against the following comments:

Test 01: Have all the limitations (Line Item#13) been addressed?

Test 02: Has the supplementary information be adequately explained and detailed? [Comments T3 and T8 against limitations#3(b) & #12(a) respectively in GRAPL NSMP07].

Test 03: Has the statement that “the LNSP will still define periods where they will not perform remote reco/disco” been satisfied?

[Comment T4 against limitation#7 in GRAPL NSMP07].

Test 04: Has the statement “the option for the FRMP to pick between these two methods [remote Supply Contactor operation or main fuse] is not available for all LNSP area” been satisfied?

[Comment T9 against limitation#12(c) in GRAPL NSMP07].

Test 05: Will the information on connection point status have been provided to the FRMP?

[Comment T2 against limitation#3(a) in GRAPL NSMP07]

Test 06: Will the additional information be provided automatically to a request for that information?

24. [Comment T7 against limitation#11 in GRAPL NSMP07]Infrastructure Performance Levels: [back]

The indicative performance levels for the Supply Contactor operation for SMI De-en are as follows:

Comment [PE11]: Yes

Comment [PE12]: Yes – CPR#02

Comment [PE13]: Yes – NEM Requirements (e) and CPR#05 where a Service level Agreement provides for this situation

Comment [PE14]: Yes – the SMI de-energisation request is only for remote Supply Contactor operation, where this capability is available.

Comment [PE15]: Yes – CPR#01 and CPR#02

Comment [PE16]: Yes – CPR#01 and CPR#14.

Deleted: ¶




List#1: Indicative Infrastructure Performance Levels for the Supply Contactor operation

1. It is noted that the performance level provides statements on both the outbound and inbound signals. In particular, the inbound signal is an acknowledgement from the Smart Meter that the Supply Contactor had operated. The acknowledgement is based on the assumption that (a) the Smart Meter received an outbound command, and (b) the Smart Meter processed that outbound command to a point where it is reasonable to accept that the Supply Contactor will in fact ‘turn OFF’. The specification was based on the position that ‘back-office’ processes will accept that the Supply Contactor had changed position to OFF when the inbound acknowledgement command is received.

The Smart Meter does not verify that the Supply Contactor had actually changed state. The verification is possible from an examination of the metering data (if after sending an open command the load continues to be supplied) then it is demonstrated that the Smart Meter did not act on the SMMS outbound command. The examination would involve a back office process with knowledge of the outbound command details.

2. It is possible that the SMI Functional Specification may be changed by the BRWG to provide for configuration of the Event Logs such that the CSFP can configure the Event Log to report immediately the the ARM event has been activated (eith the Supply Contactor moved to the Open state or timeout had occurred).

The indicative performance levels for remote acquisition in regard to SMI De-en are as follows:

List#2: Indicative Infrastructure Performance Levels for Remote Acquisition

There are no indicative performance levels for:

• The Quality of Supply and other Event Recording function;

• The Meter Communications: Issuing Messages and Commands,

in regard to SMI De-en.

<<<BPPWG to prepare an acceptable Role related set of performance levels>>>

25. Participant Service Levels: [back]

The ‘service levels’ that relate to the service between Roles for operation of the Supply Contactor in regard to SMI De-en are as follows:

List of performance levels: outbound inbound#commands acknowledgement meters period

switch command (OFF)-individual total # 90% 10 minsswitch command (OFF)-individual total # 0.015%(1) 10 mins

SMMS reporting (SC exceeded) 99% 10 minsswitch commands (OFF) total # 0.5%(1) 24 hrs

Notes (1): represents percentage of smart meters installated in DNSP area

List of performance levels (1): outbound inbound#commands acknowledgement meters period

energy data and event logs - routine 1 per NMI nil 99% 4 hrsenergy data and event logs -special read 1 nil 90% 30 minsenergy data and event logs -special read total 0.1%(2) 30 minsenergy data and event logs -special read total 24 hrs

Notes (1): 48 intervals of energy data, or all accumlated dataNotes (2): represents percentage of smart meters installated in DNSP area




List#1: Indicative Participant Service Levels for the Supply Contactor operation

The ‘service levels’ that relate to the service between Roles for remote acquisition in regard to SMI De-en are as follows:

List#2: Indicative Participant Service Levels for Remote Acquisition

There are no indicative service levels for:

• The Quality of Supply and other Event Recording function;

• The Meter Communications: Issuing Messages and Commands,

in regard to SMI De-en.

<<<BPPWG to prepare an acceptable Role related set of service levels>>> 26. Customer Service Standards: [back]

<<<Identify and record the ‘service standards’ that are to apply to the services provided by a Role to its customer>>>.

(Commence with acceptable standards identified by Roles and refine these standards through discussion with customer advocates.)

27. Progress reporting: [back]

List the dates and version each time a progress report is provided to the NSSC, IEC/RMEC and/or AEMO.

28. Endorsement: [back]

Record the entity that ‘endorsed’ this paper (including date and version).

Legend: Working Group Leader Workshop WG members WGM with assistance from WGL Template comment - to be reworked

List of service levels: meters periodCommand received & SC operated 90% 1 hrCommand received & SC operated 99% 3 hrs

List of service levels: duration meters periodenergy data and event logs - daily overnight 96% by 6amenergy data and event logs - daily overnight 99% 24 hrs

energy data and event logs - special read per read 90% 2 hrsenergy data and event logs - special read per read 99.9% 8 hrs




ATTACHMENT A – Flowchart [back to Contents] [back to Item 16]

BP01.1Customer requests

de-energisation

BP01.2Customer request

acceptedBP01.3Non payment conditions met

BP01.aIs SMI available?

BAU

BP01.bIs min.

supply OK?

BP01.4Determine

safety requirements

BP01.c:Is SMI safe to

use?

Supply Capacity Control

BP01.5Check

visibility of SC

BP01.7Request

standing data

BP01.6Check status

AEMO

MARKET SYSTEMS

CUSTOMER

CURRENT FRMP

RP [DNSP]

CSFP

SMART METER

MDP

BP01.8Receive request

BP01.9Obtain and

send information

BP01.11Finalise request details

BP01.10Receive standing

data

BP01.12Send De-en

service request

BP01.13Receive request

BP01.14Plan work

BP01.15Send planned

schedule

BP01.16Receive planned schedule

BP01.17Remote De-en

attempted

BP01.18Supply

Contactor opened

BP01.19Meter messages

examined

BP01.20Manual De-en of the SC

BP01.21Notify SMI

failure

BP01.22Receive

notification of failure

BP01.eSC

opened?

BP01.23Send

notifications

BP01.24Collect

metering data

BP01.25Validate / substitute

metering data

BP01.26Send

metering data

BP01.27Receive metering

data

BP01.28Receive

notification of SC opened

BP01.29Receive

notification of SC opened

BP01.30Update

SC status

start

start

end

yes

no

yes

no

no yes

yes

noVerifying standing data

Legend:Core process shown in blueTemporary located process shown in dark red

remote local

CP#02

CP#01

CP#03

CP#04

CP#05 CP#06

CP#07 CP#08 CP#09

CP#10 CP#12 CP#13 CP#14

BPPWG business process flowchart BP01 De-en v02

SMI De-en business process flowchart

CP#11

BP01.dIs SC

visible?

yes

no

no

Flowchart 1: SMI De-en business process

Noteworthy conditions for SMI De-en are:

• Constraints: end of business day cut-off will flow-over activities to the next day and hence not provide turn-around in a short time limit.

• Limitations: all limitations have been addressed.

• Manual interventions: there are no manual interventions.

• Transitional considerations: internal processing for CP#02 & CP#03 may not include automatic processing capacity.

Formatted: Indent: Left: 0.75 cm,Hanging: 0.75 cm, Bulleted + Level: 1+ Aligned at: 0.63 cm + Indent at: 1.27 cm

Formatted: Not Highlight

Formatted: Not Highlight




ATTACHMENT B – Control Point Records [back] [back to Item 16] Contents of Attachment B for SMI De-en: CP#01 Check connection point status information CP#02 Request standing data for verification CP#03 Send standing data for verification CP#04 Send SMI De-en service request CP#05 Send planned schedule CP#06 Notify SMI failure CP#07 Remote De-energisation attempted CP#08 Smart Meter operation CP#09 Manual De-en of the Supply Contactor CP#10 Send notification – to collect metering data CP#11 Send metering data CP#12 Send notification – Supply Contactor opened CP#13 Send notification – Supply Contactor opened CP#14 Send notification – Supply Contactor opened The hyperlinks may be used to navigate to and from a selected Control Point Record.

Deleted: supplementary information

Deleted: supplementary information




CONTROL POINT RECORD [back to Content]

BP01 Business Process De-en service

CP#01 Control Point transaction Check connection point status information

18 Jun 2010 Initiating Entity: FRMP

v02 Status: Draft/Final

GUIDELINE:

WHAT: Objective/content/target/outcome

WHEN: Initiator timing information, frequency, counterparty timing for a transaction

WHERE: Location ID/address /source/device/repository

WHO: Responsibility, one or more parties

WHY: Describe event: reason / need/ principle / driver (generally used as support info)

HOW: Actions to be taken

HOW MANY: Estimate the quantity (or volume) of transactions involved per day

Details: WHAT: Objective FRMP to query Market Systems for connection point status

Outbound Content

NMI

Inbound Content

NMI level: NMI status. Metering installation classification Number of phases Fuse status Annual consumption Safety information:

o Known safety hazards; o Site isolated for safe working conditions

Information to describe whether ARM functionality is being used [SPAN]. Meter level: Supply Contactor status per meter per NMI. Meter type (SM, AMI or other) Meter attributes:

o Meter configuration details o Energy measurement channels that have been configured

CLC/R status Customer Service function settings and status. If the connection point is already disconnected, the method of disconnection (fuse, pole, pit, SC).[AGL]

Outcome The Market Systems provide the FRMP with readily available information on the Meter status (SC status) and the NMI status.

WHEN: Initiator Timing

Any time (24 hours by 7 days).

Frequency Multiple times per day.

Counterparty timing

Market system to be available at all times, with automatic turn-around of query.

Comment [PE17]: I suggest that the header be revised as some elements (date, version, status) are now better represented in the Version History.

Comment [PE18]: I consider that the ‘Guideline’ section has served its purpose and can now be removed. It is replicated in the CPR template for ready reference at any time.

Comment [PE19]: See DNSP comment at the bottom of the CPR

Comment [PE20]: Point 17.3 in the Feedback Register [AGL]


Formatted: Indent: Left: 0.56 cm,Hanging: 0.75 cm, Bulleted + Level: 3+ Aligned at: 3.17 cm + Tab after: 3.81 cm + Indent at: 3.81 cm, Tabstops: 1.31 cm, List tab + Not at 3.81cm

Comment [PE22]: See SPAN comment at bottom of the CPR

Comment [PE23]: Requires reason for its inclusion. See SPAN comment at the bottom of the CPR.

Formatted: Indent: Left: 0.56 cm,Hanging: 0.75 cm, Bulleted + Level: 3+ Aligned at: 3.17 cm + Tab after: 3.81 cm + Indent at: 3.81 cm, Tabstops: 1.31 cm, List tab + Not at 3.81cm



Comment [PE26]: For review




WHERE: Location ID From a database that is electronically available to the FRMP

WHO: Entities FRMP, market systems

WHY: To obtain an independent check of the FRMP held information

HOW: Outbound Electronic access ‘service request’ type transaction

Inbound Download of search results.

HOW MANY Number of transactions per day

More than <<10>> transactions per day.

SPAN comment on ‘inbound content’ (see reference 20.1 in the Feedback Register): As party responsible of maintaining market systems the DSNP/RP/CSP considers that only selected inbound content is relevant to the process: (A) Incorporated off the power point presentation:

• Information to describe whether ARM functionality is being used

• NMI status

• Metering installation classification and Meter type (SM, AMI or other)

• Requestor needs information to determine whether there is an expectation that the supply contactor will be operated remotely or locally <<is this a comment on the SMI ‘capability’. If yes, then these words in the description would help the understanding>>

(B) Items not incorporated off the power point presentation: • Meter attributes: Meter configuration details – not relevant to supply contactor process, it may be relevant

to another process

• Meter attributes: Energy measurement channels that have been configured – not relevant to supply contactor process, it may be relevant to another process

• Meter attributes: Customer Service function settings – not relevant to supply contactor process, it may be relevant to another process

• Meter contactor status – not relevant to a Market System (C) Fuse status – not relevant to a Market System Green already included in ‘Inbound Content’ Blue added to ‘Inbound Content’ Red for discussion

Comment [PE27]: What is the basis of ‘10 transactions per day? Initial estimate to act as a starting point. The FRMP is expected to rely on the quality of its internal systems for the connection point status. It is expected that the FRMP would only seek clarification of data from marker systems when there was doubt about the internal FRMP system data. The quantity 10 was determined from the scenario where doubt was expressed on 0.1% of the daily transactions and there were 1,000 CP#4 transactions a day. Please rework these numbers to provide a value that is more consistent with the company’s view.






CP#02 Control Point transaction Request standing data for verification



Guideline:








Details: WHAT: Objective FRMP to request clarification / confirmation from the CSFP of information held in the

Market Systems

Outbound Content

One or more pieces of information that are in doubt, for example: Number of phases; Meter type (single phase, 3 phase, SMI, AMI, other) Plus any of the information included in CP#01 Inbound Content.

Inbound Content Acknowledgements: o Handshake; o Transaction; o Business

Outcome The request is conveyed to the CSFP by electronic means. The acknowledgements are conveyed by electronic means.

WHEN: Initiator Timing Any time between the hours of <<8am to 5pm on any business day>>.

Frequency Anticipated <<once per month>> on average.

Counterparty timing

Request to be acted on within <<2>> hours unless a shorter period is specified.

WHERE: Location ID NMI

Device Meter serial number(s)

WHO: Entities FRMP, CSFP

WHY: FRMP has a doubt on the accuracy of the information held in the Market Systems

HOW: Outbound Transaction sent via B2B

Inbound Acknowledgements sent via B2B


Less than 1 transaction per day.

Formatted: Bulleted + Level: 1 +Aligned at: 0.63 cm + Indent at: 1.27cm




Deleted: ¶Address ...

Comment [PE31]: Deleted in accordance with Stakeholder Feedback 17.3 and 20.3






CP#03 Control Point transaction Send standing data for verification

18 Jun 2010 Initiating Entity: CSFP


GUIDELINE:








Details: WHAT: Objective CSFP to send any additional information to the FRMP

Outbound Content

One or more pieces of information that replicate the submitted FRMP information and additionally confirms if that information is correct, and if not correct, includes the correct information. For example: [SPAN] • Information to describe whether ARM functionality is being used

• NMI status


• Requestor needs information to determine whether there is an expectation that the supply contactor will be operated remotely or locally

• Meter contactor status

• Energisation status

• Method of last disconnection

Inbound Content

Acknowledgements: o Handshake; o Transaction; o Business

Outcome The request is conveyed to the FRMP by electronic means. The acknowledgements are conveyed by electronic means.


Any time between <<8am and 5pm of any calendar weekday>>.

Frequency Anticipated <<once per year>> on average.

Counterparty timing

Response to be sent within <<2>> hours unless a shorter period is specified, or a flow-over to the next business day occurs.

WHERE: Location ID As provided by FRMP

WHO: Entities CSFP, FRMP

WHY: In response to FRMP request



Comment [PE32]: See SPAN comments below the CPR








Less than 1 transaction per day.

SPAN comment on ‘outbound content’ (see reference 20.5 in the Feedback Register): As party responsible for responding considers that only selected content is relevant to the process: (A) Items incorporated off the power point presentation:

• Information to describe whether ARM functionality is being used

• NMI status


• Requestor needs information to determine whether there is an expectation that the supply contactor will be operated remotely or locally

• Meter contactor status

• Energisation status

• Method of last disconnection Green already included in ‘Inbound Content’ Blue added to ‘Outbound Content’ Red for discussion






CP#04 Control Point transaction Send De-en service request



GUIDELINE:


WHEN: Initiator timing information, frequency, counterparty timing per transaction





HOW MANY: List the quantity (or volume) of transactions involved per day

Details: WHAT: Objective FRMP to send a request to the CSFP to remotely open the Supply Contactor of a

nominated Smart Meter.

Outbound Content

SC to be opened by SMI (default) OR manual. Method of disconnection NMI and meter information. Priority Validity of the request (start date and time and end date and time) Customer Contact Information Information on site problems, if any. Information on alternative arrangements suitable to FRMP. Priority to be given to the request [Defining the ‘priority’ of the request should be governed by business rules and the timing of the request] (AGL). Date and time when the request is to be performed. ‘Not before’ time. ‘Not after’ time. The transaction rules are to include a ‘time to live’ (lifetime) and once expired, the request will no longer be required. During the lifetime a number of retries will be permitted/expected (AGL). Whether or not the De-en is for non-payment, Move-out or transfer to another FRMP [SPAN] Any safety information from customer relevant to local De-en [SPAN]

Inbound Content

Acknowledgements: o Handshake; o Transaction; o Business.

The ‘business acknowledgement’ is to incorporate a check to validate if the FRMP is the current FRMP, and is permitted to request a SMI De-en at that time. The request should be rejected if the FRMP check returns inconsistent results (AGL).

Outcome The request is conveyed to the CSFP by electronic means. The acknowledgements are conveyed by electronic means.


Any time between <<8am and 5pm of any business day>>, subject to an agreed Service Level.

Frequency <<Multiple times per day>>.

Deleted: De-en Service Order

Comment [PE36]: Is this appropriate. Should be deleted, as this is a discretionary action for the CSFP [PE].

Comment [PE37]: From AGL (17.7 in the Feedback Register). Isn’t this a repeat of the above? [PE]

Comment [PE38]: From AGL (17.7 in the Feedback Register).


Comment [PE40]: Not before’ and ‘not after’ time is not for the requester to specify, rather they are constraints imposed by the jurisdictional regulator and by the DNSP/CSP in accordance with a Energy Safety Management Scheme. Remove ‘Not before’ and ‘not after’ time [SPAN]. See 20.7 in the Feedback Register. Other views??


Comment [PE42]: Point 20.7 in the Stakeholder Feedback Register


Deleted: calendar weekday

Comment [PE44]: Based on data from Scenario ‘C’ as recorded by the BRWG, being 8 hours per day.





Counterparty timing

SC to be opened within 10 mins unless a flow-over to the next business day occurs or the retailer specifies a later time (within the same day) or a future date for this action to occur.


Device Meter serial number

WHO: Entities FRMP, CSFP

WHY: To obtain a de-energistation of a nominated premise within a known timeframe.




More than <<50>> transactions per day.

Deleted: <<2>> hours

Comment [PE46]: Reassessed in accordance with Scenarios ‘A’ and ‘C’ as recorded by the BRWG, being between 10 mins and 1 min for the SMI. In discussion with AGL, a further 5 mins should be allowed from the point of initiation by the FRMP into the B2B facility and its transfer to the SMI facility. This give a range of between 15 mins and 6 mins, and suggests that a 10 min average is reasonable to use for the purpose of the CPR context.

Deleted: shorter period is specified, or a

Deleted: De-en service

Comment [PE47]: Initial estimate to act as a starting point for discussion. The quantity 10 was determined from scenario ‘C’ (high) as recorded by the BRWG, where the daily volume of SMI De-en transactions was 1.0% of the meter stock. For a stock of 100,000 meters, the daily volume would be 1,000 meters. This seems a bit on the high side, as it implies that on average a premise is consciously de-energised once every 100 business days (5 months). If the average rate for de-energising a premise was once every 1,000 business days (~3 years), then in a stock of 100,000 meters the number of meters de-enegised per day would be 100, or 0.1% of the meter stock. Based on this assessment, more than 50 transactions per day would be a reasonable representation for context purposes. Would retailers please comment on this reasoning??






CP#05 Control Point transaction Send planned schedule



GUIDELINE:








Details: WHAT: Objective CSFP to send a notice to FRMP advising of the time planned to perform the SMI de-

energisation request in those instances where a time is not included in the request for SMI De-en or as specified in a Service Level Agreement.[AGL] & [SPAN] [

Outbound Content

Date and time (or period) for performing the SMI De-en. NMI and meter affected by the De-en operation.

Inbound Content

Acknowledgements: o Handshake; o Transaction.

Outcome The notice is conveyed to the FRMP by electronic means. The acknowledgements are conveyed by electronic means.


As soon as the request is received.


Counterparty timing

The planned schedule to be received within <<1 hour>> of the FRMP request, except where a flow-over to the next business day is permitted.




WHY: To allow FRMP to obtain de-energisation of a nominated Smart Meter within a known time limit.




More than 50 transactions per day.

Deleted: SMI De-en Service Order

Comment [PE48]: Modified in accordance with comments provided in 17.9 and 20.8 of the Feedback Register.

Deleted: Note that This step is relevant to the FRMP only if the De-en service request is prospective. There is no point in receiving the schedule for requests which will require immediate action (depending upon priority]. <<more information on ‘prospective’ is required. Does it mean any request that is for tomorrow, next week, next month?>> (AGL)



Deleted: SC to be opened within


Deleted: unless a shorter period is specified

Deleted: or

Deleted: manage customer expectations for executing the requested SMI De-en






CP#06 Control Point transaction Notify SMI failure



GUIDELINE:








Details: WHAT: Objective CSFP to send a notice to FRMP advising of the failure to perform the SMI de-

energisation request.

Outbound Content

Day planned to perform the De-en service. Time range in which De-en service was attempted. Number of retries before concluding a Failure. NMI and meter on which the De-en operation was attempted. Reason code [+ additional description] for failure (such as, comms issues, meter issues, network issues, emergency over ride operation). Advise FRMP with options in case the remote de-energisation has failed [AGL]

Inbound Content


Outcome The notice is conveyed to the FRMP by electronic means. The acknowledgements are conveyed by electronic means.


As soon as the request is declared as ‘failed’.

Frequency Once per week on average.

Counterparty timing

Failure reason to be provided within <<30>> mins after failure identified.




WHY: To allow FRMP to manage customer expectations




Less that 1 transaction per day.

Deleted: De-en Service Order

Comment [PE51]: Modified in accordance with comments provided in 17.10 of the Feedback Register








CP#07 Control Point transaction Remote de-energisation attempted



GUIDELINE:








Details: WHAT: Objective CSFP to send a command to Smart Meter to change position of Supply Contactor

(SC) from ON to OFF.

Outbound Content

Command selected in SMMS.

Inbound Content

Nil

Outcome The Smart Meter SC changes from ON state to OFF state. The action is recorded in the QOS Event Log. [Note that an event alarm is not sent to the SMMS to be reviewed for possible change to Functional Specification]


Any time between 7am and 7pm of any calendar weekday, subject to an agreed Service Level.


Counterparty timing

SC to be opened within 1 hour of the command being sent (for 90% of all commands sent). SC to be opened within 3 hours for the command being sent if not opened within 1 hour (for 99% of all commands sent. SC to be opened within 10 mins of the command being sent to any one individual Smart Meter. SC to open in excess of 10 mins if commands are sent at any one time to more than 0.015% of Smart Meters in any one DSNP area [1,500 meters in 100,000].

WHERE: Location ID Command sent to identified NMI

Device Command sent to identified meter serial number

WHO: Entities CSFP, Smart Meter

WHY: To switch the Supply Contactor to the OFF state.

HOW: Outbound Command sent via SMMS and SMCN

Inbound No acknowledgements sent to SMMS

HOW MANY Number of commands per day

More than 50 commands at SMMS end per day.

Comment [PE54]: For reviews








CP#08 Control Point transaction Smart Meter operation

18 Jun 2010 Initiating Entity: Smart Meter


GUIDELINE:








Details: WHAT: Objective Smart Meter to send information on the state of the Supply Contactor (SC) to the

CSFP.

Outbound Content

‘Command completed’ message with date & time stamp, if appropriate. Command failed message with date – time stamp, number of remote retries and reasons for failure, if appropriate. [AGL] QOS Event Log (SC opened). NMI and meter serial number.

Inbound Content

Nil

Outcome The CSFP can act on the information to either advise the FRMP of the SC status or retry in accordance with the Service Level.


Any time. Next day QOS Event Log retrieval << to be reviewed if Event log becomes configurable.


Counterparty timing

Remote Service Check performed within <<1 hour>> of De-en service command initiated. Command completed message by midday of the day after (via QOS Event Log) Failure reason by midday of the day after (via QOS Event Log).

WHERE: Location ID NMI confirmed

Device Meter serial number confirmed

WHO: Entities Smart Meter, CSFP

WHY: To enable the CSFP to determine if the SC has changed to the Open state

HOW: Outbound Message sent via SMCN to SMMS

Inbound No acknowledgements sent to Smart Meter

HOW MANY Number of messages per day

More than 50 messages per day.

Deleted: ¶

Comment [PE57]: Modified in accordance with comments provided in 17.10 of the Feedback Register.

Comment [PE58]: SPAN requests that the reference to QOS Event Log be deleted as its reference here is too prescriptive. See Feedback Register 20.10. Other views??










CP#09 Control Point transaction Manual De-en of the SC



GUIDELINE:








Details: WHAT: Objective To locally change the position of the Supply Contactor (SC) to open.

Outbound Content

On-site Service Order NMI, meter serial number, address. Day and time that De-en service is to be performed Reasons failure and site visits, Mode of disconnection (pole, pit, fuse, tails), priority [AGL] Any safety information from customer relevant to local de-en [SPAN]

Inbound Content

Advice that SC has been switched OFF. Event Log message.

Outcome The SC has been switched to the open state.


Any time between 8am and 5pm of any business day, subject to an agreed Service Level. Next day QOS Event Log retrieval.

Frequency Once per month on average.

Counterparty timing

Same or next business day, as per Service Level Agreement.



WHO: Entities CSFP, Smart Meter

WHY: To allow the CSFP to fulfil the FRMP request to de-energise the nominated Smart Meter.

HOW: Outbound Local operation of SC

Inbound Local confirmation of SC operation. QOS Event Log record

HOW MANY Number of local commands per day

Less that 1 local command per day



Comment [PE65]: For discussion

Comment [PE66]: Based on every 3 out of 4 failures (see CPR#06) are successful on the second attempt. For review

Comment [PE67]: For discussion

Deleted: enable the FRMP request for a De-en service to be carried out in accordance with the Service Level Agreement






CP#10 Control Point transaction Send notification – to collect metering data

18 Jun 2010 Initiator Entity: CSFP


GUIDELINE:








Details: WHAT: Objective To notify the MDP of the need to perform a part day special read of the Smart

Meter.

Outbound Content

NMI, meter serial number. Day and time that part day meter reading is to be provided to the FRMP QOS events log report [AGL]

Inbound Content

Acknowledgements: o Handshake; o Transaction; o Business??

Outcome The MDP has been notified.


Any time between 8am and 5pm of any business day, subject to an agreed Service Level.

Frequency Triggered by customer.

Counterparty timing

As soon as confirmation has been received by the CSFP that the SC has opened.



WHO: Entities CSFP, MDP

WHY: To inform the MDP that a special read should be performed within a short timeframe

HOW: Outbound Message send via B2B



More than 10 per day.

Comment [PE68]: SPAN suggests that this Control Point Record be deleted because the De-en process should not link to the meter read process. When a type 1-4 meter is de-energised a read is provided separately on the next day. Other views??

Deleted: that

Deleted: is required



Deleted: is required to






CP#11 Control Point transaction Send metering data

18 Jun 2010 Initiating Entity: MDP


GUIDELINE:








Details: WHAT: Objective To provide FRMP with metering data to support a SMI de-energisation request.

Outbound Content

MDFF file (note that this file format may note be sufficient) Validated and substituted interval data, QOS events log details [AGL]

Inbound Content


Outcome The FRMP receives metering data.


Same day if notice received prior to <<3pm>>, otherwise next business day.

Frequency Triggered by notice from CSFP.

Counterparty timing

Any time.



WHO: Entities CSFP, MDP

WHY: To enable the FRMP to prepare a bill to serve on the customer outside the normal billing run

HOW: Outbound MDFF send via NEMNet

Inbound Acknowledgements sent via NEMNet



Deleted: De-en service








CP#12 Control Point transaction Send notification – SC opened



GUIDELINE:








Details: WHAT: Objective To notify the FRMP that the SMI de-energisation request has been successfully

completed.

Outbound Content

NMI, meter serial number. Date and time when request was sent, day and time that SC was opened, reasons for delay (if any), exceptional circumstances at a site which FRMP needs to be aware of.

Inbound Content


Outcome The FRMP has received notice that the De-en service had been performed.




Counterparty timing

Any time.




WHY: To inform the FRMP of the day & time that the SC was opened

HOW: Outbound Message send via B2B



More than 50 per day

Deleted: De-en

Deleted: in accordance with the De-en service request









GUIDELINE:








Details: WHAT: Objective To notify the RP[DNSP] that a SMI de-energisation request has been performed.

Outbound Content

NMI, meter serial number. Date and time when request was sent, day and time that SC was opened, reasons for delay (if any), exceptional circumstances at a site which FRMP needs to be aware of.

Inbound Content


Outcome The RP[DNSP] has received notice that the De-en service had been performed.




Counterparty timing

Any time.

WHERE: Location ID NMI provided by FRMP

Device Meter serial number provided by FRMP

WHO: Entities CSFP, RP[DNSP]

WHY: To inform the RP[DNSP] of the day & time that the SC was opened

HOW: Outbound Transaction send via B2B



As per ‘frequency’

Deleted: De-en

Deleted: in accordance with the De-en service request









GUIDELINE:








Details: WHAT: Objective To update the Market Systems that a SC has been opened in a particular Smart

Meter.

Outbound Content

NMI, meter serial number. Day and time that SC was opened. SC open state

Inbound Content

Acknowledgements:??? o Handshake; o Transaction.

Outcome The Market Systems have been updated to record the SC in the open position for a particular Smart Meter.




Counterparty timing

Any time.



WHO: Entities CSFP, Market Systems

WHY: To provide a common access point for checking the status of the Supply Contactor for each Smart Meter

HOW: Outbound Message send via Market Systems

Inbound Acknowledgements sent via Market Systems



Deleted: at

Deleted: inform the RP[DNSP] of the time that the SC was opened in accordance with the De-en service request




ATTACHMENT C – Description of process steps within each entity [back] Description of process steps within each entity for SMI De-en: Ref # Flowchart name for step Description of step BP01. 1 Customer requests de-

energisation This is the start of process if initiated by a customer. Possible customer move-out triggers the request to the current FRMP.

BP01. 2 Customer request accepted The current FRMP receives, understands and accepts the advice that the customer is vacating the premise and consequently switching the supply contactor to off would be an appropriate action.

BP01. 3 Non payment conditions met This is the start of the the process if initiated by the current FRMP after deciding that all other courses for a correction of the non- payment condition had been exhausted.

BP01.a Is SMI available? Yes proceed to BP01.b No pass to a BAU transaction for disconnection if appropriate, or leave premise energised.

BP01.b Is min supply OK? Yes proceed to Supply Capacity Control flowchart No proceed to BP01. 4

BP01. 4 Determine safety requirements The current FRMP assesses the known information about the site in regard to any safety issues that may need to be taken into account.

BP01.c Is SMI safe to use? Yes proceed to BP01. 5 No pass to a BAU transaction if appropriate.

BP01. 5 Check visibility of SC FRMP checks internal systems for visibility of supply contactor BP01.d Is SC visible? Is SC visible within the current FRMP’s internal systems?

Yes proceed to BP01.10 No proceed to BP01. 6

BP01. 6 Check status Check performed through market systems BP01. 7 Request Standing Data Seek confirmation that FRMP standing data is correct. BP01. 8 Receive request The CSFP [MP??] receives the transaction and carries out a confirmation

check on the person submitting the request to remove any doubt that the person is the current FRMP. A business acknowledgement is returned to the sender.

BP01. 9 Obtain and send information The CSFP [MP??] undertakes a verification of the submitted information and sends the results to the current FRMP to confirm or otherwise indicate the status of the information provided for verification.

BP01.10 Receive standing data The current FRMP receives the results of the verification process. BP01.11 Finalise request details The current FRMP finalises the details of the SMI De-en service request. BP01.12 Send De-en service request The current FRMP sends the SMI De-en service request to the CSFP BP01.13 Receive request The CSFP receives the SMI De-en service request and acknowledges that

the request is acceptable in all regards. BP01.14 Plan work The CSFP plans to perform the SMI De-en service, including assessment

of the site and any restrictions that may be imposed in using the remote service or the local service, including time restrictions.

BP01.15 Send planned schedule If the SMI De-en request is ‘prospective’ the CSFP will notify the current FRMP of the proposed day and time that the service request will be actioned.

BP01.16 Receive planned schedule The current FRMP receives the planned schedule and assesses if the work has been scheduled within the limits of the initial request.

BP01.17 Remote De-en attempted The CSFP attempts to open the Supply Contactor by sending a remote command using the SMI facility.

BP01.18 Supply Contractor opened The Smart Meter receives the command, acts on the command and returns a message to the CSFP within a few minutes.

BP01.19 Meter messages examined The CSFP examines the message from the Smart Meter and assesses whether the Supply Contactor has opened. If the Supply Contactor was assessed as remaining closed, the CSFP may undertake a further attempt to open the Supply Contactor by proceeding back to process BP01.17. Otherwise, the CSFP may choose to perform the opening by

Comment [PE72]: Should the check be to the CSFP or to the MP? The MP is the person who installs the meter.




local action on site, in which case process step BP01.20 is undertaken. BP01.20 Manual De-en of the SC The CSFP initiates a manual opening of the Supply Contactor on site if

the Service Agreement support this action before notifying the current FRMP that the remote operation had failed.

BP01.21 Notify SMI failure The CSFP determines that operation of the Supply Contactor by the SMI facility (either remote or local or both) is not possible and sends the required information to the current FRMP.

BP01.22 Receive notification of SMI failure

The FRMP receives notification of the SMI failure and determines what additional course of action is required.

BP01.e SC opened? Yes proceed to BP01.23 No proceed to BP01.17

BP01.23 Send notifications The CSFP sends notifications to the relevant parties advising that the Supply Contactor is in the opened state, and requesting the MDP to collect the metering data for that NMI.

BP01.24 Collect metering data The MDP arranges to collect the relevant metering data within the standard timeframes agreed in a Service Level Agreement.

BP01.25 Validate / substitute metering data

The MDP validates and if necessary substitutes metering data for the NMI under consideration.

BP01.26 Send metering data The MDP sends the processed metering data to the current FRMP. BP01.27 Receive metering data The current FRMP receives the processed metering data for the

nominated NMI. BP01.28 Receive notification of SC

opened The FRMP receives notification from the CSFP that the Supply Contactor for a nominated NMI has been opened.

BP01.29 Receive notification of SC opened

The FRMP receives notification from the CSFP that the Supply Contactor for a nominated NMI has been opened.

BP01.30 Update The CSFP updates the Market Systems with the change in Supply Contactor status

Business Process and Procedures Workstream Role ... Smart Metering Program Business Process and...

Documents

Transcript of Business Process and Procedures Workstream Role ... Smart Metering Program Business Process and...