IGG Agenda 27th June 2012
Minutes from Previous IGG Meeting
10:30 – 10:35
Review of Action Items
10:35 – 10:45
CER Update
10:45 – 10:55
Gemserv Update
10:55 – 11:05
MRSO Update
11:05– 11:15
HSP Project Update
11:15 – 11:25
Retail Market Design Service Update
11:25 - 11:45
AOB
11:45 – 11:55
Next Steps
11:55 - 12:00
27th June 2012
Retail Market Design Service
Page 1
Minutes
Draft Minutes from IGG meeting
23rd May 2012
For approval today.
27th June 2012
Retail Market Design Service
Page 2
IGG Action Items
Updated IGG Action List issued in
advance of meeting
 Actions closed since last IGG meeting: 11
 IGG Actions carried forward: 7
27th June 2012
Retail Market Design Service
Page 3
IGG Actions Carried Forward
AP
No.
Title
Assigned To
Date Due
645
Provide list of open Defects and timelines for delivery
RMDS
16/07/2010
791
Market System Outages: Suppliers to provide feedback to
aid development of appropriate process
Suppliers
27/06/2012
795
LTNA Sites: Suppliers to consider ESBN Proposals & forward Suppliers
14/06/2012
feedback to RMDS
799
Harmonisation: EULA - CER to liaise with MRSO/ESBN
regarding potential Data Protection issues
CER
31/05/2012
800
Essential Plant: Suppliers to forward feedback to CER on
ESB Networks' Proposals
Suppliers
14/06/2012
801
Essential Plant: ESB Networks to forward list of relevant
MPRNs to each Supplier
ESBN
27/06/2012
805
MCR 87: RMDS to update status to Withdrawn and remove
from Active List
RMDS
29/06/2012
27th June 2012
Retail Market Design Service
Page 4
LTNA Sites: Suppliers to consider ESBN Proposals
and forward feedback to RMDS

Feedback from 2 Suppliers
 1 preference for Option 3; Supplier requests de-energisation and
cost of work is socialised
–
–
–

1 Supplier preference for alternative Option 4
–

It is better for the market as a whole that long term vacant sites are deenergised to ensure there are no safety risks.
numbers across the market are not significant.
With option 1 & 2 suppliers are still exposed to the cost associated with
the reduced MIC (50 kVA or 100 kVA).
ESBN would allow the supplier to be deregistered 3 months after the
supplier has requested the de-energisation of the site
In order to quantify what impact the proposal will have on
costs ESBN require details from suppliers on the
connections that qualify (include MPRN, DUoS Group and
current MIC).
27th June 2012
Retail Market Design Service
Page 5
CER Update
Industry Governance Group
27th June 2012
Retail Market Assurance
Services for the Irish Electricity
Market
Peter Varley
IGG 27th June 2012
peter.varley@gemserv.com
7
Assurance Activity Update
Business As Usual (RMDS)
• Assurance Process Document
– Third review comments from RMDS received
– Final draft compiled and being reviewed by RMDS
– Expect it to be ready for next IGG
21 September 2011
8
Assurance Activity Update
Harmonisation (HRDS)
• PQ
– Most questionnaires received but some still awaited
• IPTs
–
–
–
–
have been prioritised and streamed
scenarios and evidence requirements have been written
individual Supplier Packs are being prepared
Supplier test slots planned
21 September 2011
9
Assurance Activity Update
Harmonisation (HRDS)
• Proposed Go/No-go criteria (for discussion):
–
All
– No major issues raised at ESBN site visit(s)
– No major issues arising at EMMA/Webforms
commissioning
– All Priority 1 scenarios successfully completed for all Large
Suppliers
• If criteria not met CER take advice and then
determine whether to go/no-go
21 September 2011
10
IPT Streaming – Large Suppliers, TSO
IPT Number
HSP Changes Grouping MM Trigger
Target MM
Title
Priority
ESB Networks, Large Suppliers, TSO
IPT001
BAU
030
332
Successful meter works - Change of Meter Configuration
IPT002
IPT003
New Message
017
131
NPA De-energise (W103) - fail - not resched - Refused Access (DN05)
017
131
NPA De-energise (W103) - fail - Rescheduled - snag customer fault (R002)
IPT004
017
131
NPA Re-energise (W203) - fail - not resched -Safety Problem (RE04)
IPT005
030
131
Change to MCC (W306) - fail - no access - resched (R001)
260
131
RP Inspection Visit (W402) - fail - missed appointment ESB fault (R008)
010
102R
CoS registration of NI MPRN
013
014R
CoCD for NI MPRN
210
303R
Supplier provides customer reading for NI MPRN
010
010
016
016
016
017
017
017
017
101
101
010
010
016
016
016
017
017
017
017
101
101
CoS Add 1 SN
CoS Add 2 SNs
CoLE Add 1 SN
CoLE Add 2 SNs
CoLE Add 4 SNs
Energise Add 1 SN - successful so no MM131
Energise Add 7 SNs - successful so no MM131
De-Energise add 5 SNs - successful so no MM131
De-Energise add 6 SNs - successful so no MM131
N/C with 1 SN
N/C with 3 SNs
105
013
013
013
013
013
013
105
013
013
013
013
013
013
Included in CoS above
CoCD delete 1 CSSN
CoCD delete 3 CSSNs
CoCD delete all CSSNs
CoCD add 1 CSSN
CoCD add 2 CSSNs
CoCD add 5 CSSNs
IPT006
IPT007
IPT008
Non-RoI MPRN
IPT009
IPT010a
IPT010b
IPT011a
IPT011b
IPT011c
IPT012a
IPT012b
IPT013a
IPT013b
IPT014a
IPT014b
IPT015, incl in
IPT010
CSSNs
IPT016a
IPT016b
IPT017
IPT018a
IPT018b
IPT018c
21 September 2011
1
1
3
2
3
1
3
1
2
3
11
IPT Streaming – Small Suppliers
IPT Number
HSP Changes
Grouping
MM Trigger
Target MM
Title
Priority
ESB Networks, Small Suppliers
IPT030a
Webforms - CSSNs
013
013
CoCD add 2 CSSNs
Webforms - CSSNs
013
017
013
131
CoCD delete 1 CSSNs
10
10
10
10
13
16
017/210
17
30
10
10
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
IPT030b
1
IPT031
IPT030
IPT031
IPT032
IPT033
IPT034
IPT035
IPT036
IPT037
IPT038
IPT039
IPT040
Webforms -New Msg
131
Webforms
NPA De-energise (W103) - fail - not resched - Refused Access (DN05)
Simple NQH CoS Gain/Loss (2 small suppliers)
Simple QH CoS Gain/Loss (2 small suppliers)
NQH Cos with Objection (2 small suppliers)
QH Cos with Objection (2 small suppliers)
CoCD
CoLE
De-energise
Re-energise
Change to Meter Configuration
New Connection NQH
New Connection QH
3
IPT041-NEW
21 September 2011
12
IPT scenario definition
Script Name:
IPT005
Unsuccessful Change to Meter Configuration Code
Test objectives:
The Supplier receives and correctly interprets the requested Meter Works
Status from the new market message, MM131.
Participant roles under
Supplier,
Participant roles requiring
test:
ESB
simulation:
None.
Networks
Initial Conditions:

The Metering Point is registered to the Supplier with all Registration Data items set;

The Metering Point is currently energised;

The Supplier has a recorded history for the Metering Point; and

The Supplier has retained evidence of all of the above.
The Scenario:

The Supplier requests a change of Meter configuration code by submitting a meter works
(MM030) request, with no CoLE to ESB Networks Central Market Systems;

ESB Networks validates the meter configuration is from the standard set and that both the meter
work request and appointment date are valid and that all permits and requisite requirements to
perform the meter works are in place.

ESB Networks is unable to perform the change as they are unable to access the customer’s
site;

ESB Networks reschedules the visit, updates their records, and informs the Supplier via relevant
market message (MM131).
Test Ends
Final Conditions:
21 September 2011

The requested Meter Configuration Code change is not performed;

The Supplier receives the new MM131 (Work Type W103 and Outcome Reason (R001))
informing them of the status of their requested meter works; and

The Supplier processes the new MM131 according to their business processes.
13
IPT Evidence Required
ESB Networks sends sample of daily
IPT027 MM342s to Suppliers, TSO and
applicable Generators
1. Receipt of MM342 by Supplier;
2. Recognition by BGE of:
IntervalStatusCode,
IntervalValue, and
NetActiveDemandValue
3. "Sxx" (SupplierID) be recipient ID
BGE withdraws initial request Change of
Supplier requests change of UnM Group Unmetered Group (UM010_CoG.doc) due
IPT022 characteristics which is withdrawn due to to incorrect estimation.
incorrect incorrect estimation
IPT011 Change of Legal Entity - Add 2
b
Customer Services Special Needs
IPT028
Supplier provides customer reading with
the meter serial number
IPT042 Readings Processing - Non QH
21 September 2011
1. XML of MM342 received by Supplier for sample
of 3 MPRNs; and
2. Evidence that interval data has been correctly
processed by Supplier
1. Screen print of withdrawal of UM010_CoG sent;
2. XML of 700 (received);
3. XML of 700W (received); and
3. Evidence of interpretation of PSOExemptionFlag
BGE submits multiple Customer Services 1. XML of MM016 (sent); and
Special Needs requirement on a Change of 2. XML of CoLE Confirmation (MM116) (received);
Legal Entity (MM016) request.
and
3. Screen print / confirmation of the interpreted
confirmation in the Supplier's internal systems.
1. BGE submits an invalid Customer
1. XML of MM210 (sent);
Reading (MM210) including the Serial
2. XML of Vlaidated Read (MM300) (received);
Number which is now required for
validation;
2. BGE receives the Validated Reading
(MM300)
The Supplier receives and process their
standard NQH reads using their normal
business processes as per business as
usual (BAU).
XML of sample of three received reads ((MM300)
14
Questions & Discussion
15
MRSO Update
Jim Long
27 June 2012
21 September 2011
16
105L Market Messages
60,000
2010
50,000
2011
2012
40,000
30,000
20,000
10,000
0
Januar y
F eb r uar y
M ar ch
A p r il
M ay
June
July
A ug ust
Sep t emb er
Oct o b er
N o vemb er
D ecemb er
2 0 10
2 9 ,9 6 9
4 2 ,6 0 1
4 4 ,79 2
4 0 ,4 70
3 7,16 3
3 7,6 8 9
2 0 11
2 8 ,3 6 9
3 5,54 2
3 7,8 71
3 1,0 3 5
2 8 ,9 18
3 0 ,4 3 2
4 0 ,3 9 8
3 7,114
4 2 ,9 6 1
4 3 ,152
4 3 ,6 11
3 5,8 9 9
3 6 ,0 2 9
3 3 ,3 3 3
2 1,3 2 5
19 ,4 6 1
19 ,8 15
2 2 ,113
2 0 12
16 ,9 9 0
2 2 ,8 2 0
2 5,3 4 9
2 0 ,2 13
2 4 ,8 6 0
010 Market Messages
60, 000
2010
2011
2012
50, 000
40, 000
30, 000
20, 000
10, 000
0
Januar y
Febr uar y
M ar ch
A pr i l
M ay
June
Jul y
A ugust
Se p t e mb e r
Oct ober
N o v e mb e r
D e c e mb e r
2010
35, 195
45, 059
49, 370
41, 699
38, 873
41, 806
40, 567
41, 710
46, 762
45, 035
49, 176
31, 265
2011
35, 629
37, 899
40, 477
28, 747
32, 688
34, 577
36, 818
33, 783
22, 052
20, 093
24, 687
20, 960
2012
20, 296
26, 421
27, 875
24, 292
27, 055
COS In Progress 19/05/2012 – 8,013
• Reviewed Monthly
• Suppliers notified of individual
switches outstanding and
reason
• Switch outstanding for
Energisation or Token Meter
Removal will not time-out
• Contact Customer or submit
cancellation
• 32 Switches held due to an
existing Open Service Order
21 September 2011
Oct 11
Nov 11
Dec 11
Jan 12
Feb 12
Mar 12
Apr 12
1
1
5
8
12
40
163
19
COS and CoLE
Month
Explicit
CoLE
Inferred
CoLE
Mar-12
5,702
3,814
Apr-12
4,945
May-12
5,173
21 September 2011
Total
CoLE
Total 010
% Explicit
CoLE
% Total
CoLE
9,516
27,875
20%
34%
2,998
7,943
24,292
20%
33%
3,343
8,516
27,055
19%
31%
20
% Registration Rejections 102R
5.0%
4.5%
2010
2011
2012
4.0%
3.5%
3.0%
2.5%
2.0%
1.5%
1.0%
0.5%
0.0%
January
February
21 September 2011
March
April
May
June
July
August
September
October
November December
21
Debt Flagging
Mar-12
Apr-12
May-12
Total MPRNs Received
447
749
599
Total Inferred CoLEs Returned to Outgoing
Supplier
120
222
186
Returned for other reason to Outgoing supplier
(Invalid MPRN, Switch Completed, Explicit CoLE)
36
19
26
Valid Debt Flags issued to Gaining supplier
291
508
387
Total Cancelled
204
197
246
Valid Debt Flags as % of total COS
1.1%
2.5%
1.6%
21 September 2011
22
21 September 2011
11
149
12
135
M
ay
-
12
12
149
Ap
r-
M
ar
-
128
Fe
b12
100
Ja
n12
120
ec
-1
1
ov
-1
1
137
D
N
ct
-1
1
164
O
201
Se
p11
207
Au
g11
190
Ju
l-1
1
214
Ju
n11
150
M
ay
-
11
11
299
Ap
r-
259
M
ar
-
400
Fe
b11
Ja
n11
ec
-1
0
ov
-1
0
206
D
N
ct
-1
0
200
O
Se
p10
Au
g10
250
Ju
l-1
0
Ju
n10
Disputed Reads Processed
392
350
300
302
260
235
185
197
164
172
144
97
50
0
23
Total withdrawal of 310 reads for all Suppliers
2,500
6.0%
5.0%
1,962
2,000
1,859 1,881
1,793
1,764
1,662 1,677
4.0%
1,587
1,512
1,500 1,465
1,390
1,354
1,292
1,283
1,181
1,000
3.0%
1,163
947
943
924
768
819
749
780
2.0%
520
500
1.0%
21 September 2011
ar
-1
2
Ap
r-1
2
M
ay
-1
2
12
M
Fe
b-
n12
Ja
-1
1
De
c
-1
1
No
v
-1
1
ct
O
-1
1
-1
1
Se
p
Au
g
l-1
1
Ju
n11
-1
1
Ju
ay
M
-1
1
1
Ap
r
ar
-1
11
M
Fe
b-
n11
Ja
-1
0
De
c
-1
0
No
v
-1
0
O
ct
-1
0
-1
0
Se
p
Au
g
l-1
0
0.0%
Ju
Ju
n10
0
24
Objections – Erroneous Transfers
50,000
308
300
45,000
259
40,000
250
232
224
35,000
No. of CoS Completions
230
No. of Objections
200
30,000
166
25,000
153
150
134
20,000
120
114
111
109
104
96
100
94
15,000
88
78
79
67
64
57
10,000
53
43
50
25
5,000
21 September 2011
12
12
M
ay
-
Ap
r-
Fe
b12
M
ar
-1
2
Ja
n12
ec
-1
1
D
ov
-1
1
N
ct
-1
1
O
Se
p11
Ju
l-1
1
Au
g11
11
Ju
n11
11
M
ay
-
Ap
r-
Fe
b11
M
ar
-1
1
Ja
n11
ec
-1
0
D
ov
-1
0
N
ct
-1
0
O
Se
p10
0
Ju
l-1
0
Au
g10
Ju
n10
0
25
Objections
Mar-12
Apr-12
May-12
No. of Objections
53
25
43
Cancellations from Objections
44
24
33
Objection Emails to MRSO
21
16
8
Uncontactable by phone
2
3
1
Written communication
3
-
-
COS Confirmed
15
13
6
Other
1
-
1
Escalation Emails
14
4
0
Reasons:
21 September 2011
26
ROI HSP Project Update
Conor Garrigan
21 September 2011
27
HSP Agenda Items
• Project Plan Update
• Design Clarifications (Extranet and Data
Formats)
21 September 2011
28
Design Phase
Ja
n- 1
2
Fe
b-1
2
Ma
r-1
2
Ap
r-1
2
Ma
y-1
2
Ju
n-1
2
Ju
l-1
2
Au
g-1
2
Se
p-1
2
Oc
t-1
2
No
v-1
2
De
c-1
2
De
c-1
1
v-1
1
No
Oc
t-1
1
Se
p-1
1
g-1
1
Au
Ju
HSP Project
l-1
1
High Level Schedule
Design ends
20/02
Build Phase
Build ends 30/05
Test ends
11/09
Test Phase - Incl. IPT
EMMA Rollout
04/6
Gemserv PQ
27/6
IPT Scenarios
10/7
Sign EULA
IPT Slots
Cutover Phase
Cutover 22 & 23/09
Final Cutover Plan
3//9
Post Go
Live ends
22/10/12
Post Go Live
Definition & Design
21 September 2011
Build & UT
System
Test
Cutover
29
ROI HSP Design Clarification
Standard Load Profile on Supplier
Extranet
21 September 2011
30
Final position and format for new Standard Load Profile field on Extranet
21 September 2011
31
ROI HSP Design Clarification
Data Format Changes
(aligning with existing live Harmonised Design in NI)
21 September 2011
32
Data Format Changes in Market Messages to Support new TIBCObased Communications
Background
The introduction of the new TIBCO-based communications technology requires a number of changes in the
contents and/or format of certain fields in some Market Messages.
Summary of Impact
Changes are being introduced in the following areas:
1.
Changes in naming convention for XML Messages
2.
Dropping of leading zeroes in Transaction Reference Number in Message Header on all outbound from
Supplier messages created by Webforms
3.
Change in format of MarketTimeStamp field in Header Segment on all Messages to conform with UTC
format
These changes are described fully overleaf.
All of these changes will be added to the ROI Extended Impact Summary spreadsheet as presented at the ROI
MP Planning Workshop on 17 April 2012. The updated presentation will be Version 1.3 and will be replaced
in the HSP Project Folder on the RMDS Calendar.
21 September 2011
33
1. Change in Market Message File Naming
convention
Inbound to Supplier
Outbound from Supplier
(via Webforms)
As-Is
MM Number
Date and Time
MM Number
Mxxxx_YYYYMMDDHHMMSSSSS
To-Be
MM
Number
Seconds
since base
date
DSO_MIM_xxxx_sssssssssssss_pppp
•
Mxxxx_YYYYMMDDHHMMSSSSS
MM
Number
TIBCO
Process ID
MIM_xxxx_sssssssssssss_pppp
Date and Time
(Pending or
Outbound
Folder)
Seconds
since base
date
TIBCO
Process ID
MIM_xxxx_sssssssssssss_pppp (Inbound
Folder)
DSO_MIM_xxxx_sssssssssssss_pppp (Archive/
(Archive/
Inbound
Outbound Folder)
Folder)
Planning and Implementation Notes
–
–
This change does not impact on the HBL or Harmonised Schema
This change is separate from the12 message name changes in the Harmonised Schema
(see the category “Message Name Changed” in the ROI Extended Impact Summary
spreadsheet on page 16 of the MP Planning Workshop slide deck)
21 September 2011
34
2. Dropping of leading zeros in Transaction Reference Number
(TxRefNbr) in Header Segment on all messages outbound from
Supplier created by Webforms
MIM
As-Is
(assuming
message is
from S98)
YYYYMMDD
HHMMSSSSS
S98_20120627090105001
To-Be
MPID
(assuming
message is
from S98)
S98_20120627915001
•
YYYYMMDD HHMMSSSSS
Planning and Implementation Notes
–
–
–
–
–
–
–
Change applies only to outbound messages to Networks created by Webforms
Leading zeroes are dropped from HH, MM and SS but not from milliseconds
This field is populated automatically on messages created by Webforms users
This field is unchanged on all outbound to MPs messages
Validation rules for this field on inbound to Networks messages are unchanged
This field is not to be confused with the MP Business Reference field in the body
of many Market Messages (that field remains unchanged by this change)
This change does not impact on the HBL or Harmonised Schema
21 September 2011
35
3.1 Change in format of MarketTimeStamp in Header
segment of all messages – Inbound to Supplier
WinterTime
YYYYMMDD
As-Is
SummerTime
HH:MM:SS.SSS
TimeZone
2012-01-01T10:15:20.073+00:00
To-Be
YYYYMMDD
HH:MM:SS.TT
TimeZone
2012-01-01T10:15:20.07Z
•
YYYYMMDD
TimeZone
HH:MM:SS.SSS
2012-06-01T10:15:20.073+00:00
YYYYMMDD
HH:MM:SS.TT
TimeZone
2012-06-01T10:15:20.07Z
Planning and Implementation Notes
–
–
–
–
Change applies only to the MarketTimeStamp field and not to other timestamp
fields in the message body such as those for IntervalPeriodTimestamp in 341,
342 and aggregation messages
602 Message: the existing StartTime and EndTime timestamps are both in the
format “DD-MMM-YY HH:MM:SS” so are not impacted by this change
This change does not impact on the HBL or Harmonised Schema
Note: As-Is TimeZone does not change with Wintertime/Summertime changes
21 September 2011
36
3.2 Change in format of MarketTimeStamp in Header
Segment of all messages – Outbound from Supplier (by
WinterTime
YYYYMMDD
As-Is
HH:MM:SS.mmm
Webforms)
SummerTime
TimeZone
2012-01-01T10:15:20.073+00:00
To-Be
YYYYMMDD
HH:MM:SS
2012-01-01T10:15:20
•
YYYYMMDD
HH:MM:SS.mmm
TimeZone
2012-06-01T10:15:20.073+01:00
YYYYMMDD
HH:MM:SS
2012-06-01T10:15:20
Planning and Implementation Notes
–
–
–
MarketTimeStamp is populated automatically on all messages created by
Webforms
Validation rules for this field on inbound from Supplier messages are unchanged
This change does not impact on the HBL or Harmonised Schema
21 September 2011
37
RMDS Update
Retail Market Design Update
Aileen O Connor, RMDS
27th June 2012
27th June 2012
Retail Market Design Service
Page 38
LTCA Working Group

Working Group held 13/06/12

Draft WG Report issued 22/06/12

Wide variety of issues and partial solutions

Actions for ESBN/Suppliers to provide evidence and statistics for
next meeting

Facilitate better focus on effective solutions

Conference Call 28/06/12 to discuss next meeting date

Terms of Reference V5.0 for Approval
27th June 2012
Retail Market Design Service
Page 39
ESB Networks
DR1111 Automated Debt Flagging
Discussion Document
Meeting of the IGG , 27th June 2012
40
21 September 2011
DR1111 Automated Debt Flagging
Background
CER Decision Customer Bad Debt in Electricity & Gas Markets CER/11/106 requires
an automated solution to replace the current interim Debt Flagging Process
•
Since October 2011 the manual interim process based on WP20 is in place
•
Subsequently a fast-track solution for Service Orders was implemented
DR1111
The objective of these slides is to present options on the Automation of Debt Flagging to
inform the debate within the industry
The options are based on a market messaging solution
Discussion Request DR1111 will be raised and will be based on the outcome of the debate
and CER requirements
Key Concepts of Debt Flagging
Old Supplier must Debt Flag where specific conditions and thresholds are met
New Supplier can if they choose Cancel the COS, but is not obliged to do so
41
21 September 2011
DR1111 Automated Debt Flagging – Two Options
Two Options are presented for consideration
Option A : 3*New Market Messages; Debt Flag passed through MRSO from Old to New
Supplier
Option B : 3*New Market Messages, Do not raise Service Orders (Re-energisation /Remove
Token Meter), Introduce automated timelines
Comment
Option A retains the disadvantage of a need for a manual fast-track process for certain Service
Orders
Option B is a more complex solution and necessitates a delay in the raising of certain Service
Orders
3* New Market Messages
018
new MM sent from Old Supplier to MRSO indicating that there is a Debt Flag being raised on an MPRN
118R new MM sent from MRSO to Old Supplier , rejection of 018
118
new MM sent from MRSO to New Supplier indicating that there is a Debt Flag being raised on an MPRN by the
old Supplier
Comment : the old supplier is not identified on the MM
42
21 September 2011
DR1111 Automated Debt Flagging – Option A : 3*New Market Messages
Debt Flag passed through MRSO from Old to New Supplier
Option A : 3*New Market Messages Debt Flag passed through MRSO from Old to New
Supplier
•
The Old Supplier will get a notification message 110 from MRSO that they are losing an MPRN
in a COS process.
•
•
Old Supplier carries out their own checks and where a Debt Flag is necessary then the MPRN
is sent to MRSO via the 018MM .
•
This should be timed to arrive while the COS is still in progress.
In this Option the COS process does not wait for an 018MM
•
Where the 018MM is not received by MRSO from the Old Supplier while the COS is still
in progress then it will be rejected via 118R , and the COS process will continue as
normal See #2
•
Where the Old Supplier does not Debt Flag then MRSO will not receive an 018.
•
and the COS process remains as-is
•
MRSO will perform automated checks via the Central Market System [See #7] on the 018MM
and where passed will send the Debt Flagged MPRN to the New Supplier via the 118MM
•
however, should these checks detect a problem then the 018MM will be rejected and the
118R will be sent to the Old Supplier with the appropriate reject reason code
•
After receiving a 118MM the New Supplier can cancel the COS for Debt Flagging on
011MM an via a new cancellation reason See #6
•
The 011MM should be timed to arrive while the COS is in progress otherwise it will be rejected
See #6
Similar to the current interim solution, a manual fast-track process will be needed for certain
Service Orders viz Re-energisation where previously Deenergised NPA / Remove Token
Meter
43
21 September 2011
DR1111 Automated Debt Flagging – Sundry items relevant to both
Options
#1
The 110 is proposed to be amended to indicate where there is a COLE either explicit or
inferred
#2
Where the Old Supplier submits a late 018MM notice of Debt Flagging then the proposal is to
reject back to the old supplier via 118R
- 018MM must arrive into MRSO while the COS is in progress otherwise it will be late - Option
A
- For Option B an 018MM must arrive into MRSO during the <<24hr or 48hr >> First Wait
Period
#3
QH sites, where eligible for Debt Flagging, will need to be accommodated in the final approved
design and where needed changes to the Central Market System will be proposed
#4
Assumption tbc is that Unmetered will be included in Debt Flagging and
#5
- As Unmetered is a manual process the assumption is that the Debt flagging process for
Grouped Unmetered will be manual and via the current SFTS
- Single Point Unmetered is assumed to be part of the automated solution
Should Suppliers’ sign-up process include a warning where a prospective customer is deenergised due to NPA or has a token meter to be removed that the physical work of ReEnergisation or Removal of Token Meter may be prevented from starting until the Debt
Flagging process has run its course
44
21 September 2011
DR1111 Automated Debt Flagging – Sundry items relevant to both
Options
#6
Proposals for cancellation of COS due to Debt Flagging
General
The 011 is proposed to be amended to indicate a cancellation due to a Debt Flag
Currently the Cancellation Reason code ME is being used in the interim process and this is
proposed to be replaced by a new value
Where a Supplier submits an 011MM and the cancellation is for Debt Flagging there will be new
validations to check if MRSO has received the 011MM before an expiry window
For Option A the expiry window is proposed as follows
•
After receiving a 118MM the New Supplier can cancel the COS for Debt Flagging on 011MM
The 011MM should be timed to arrive while the COS is in progress otherwise it will be rejected
Note should Option A be the favoured option to progress then further work would be needed to define the
cancellation window for a manual fast track solution, as well as all other details related to this subprocess
For Option B the expiry window is proposed as follows
•
There will be new validations to check if MRSO has received the 011MM before the SWP expiry.
and where late the cancellation will be rejected on a 111R and with either the existing TIM or a new
rejection reason code.
Note that the Cancellation 011MM for Debt Flagging will not be accepted if sent in before the start of the SWP
45
21 September 2011
because the 118MM will not have been sent out
DR1111 Automated Debt Flagging – Checks on the 018MM - both Options
#7 Automated Checks proposed on the 018MM leading to rejections on the 118R to the Old
Supplier
eg
•
Invalid MPRN [IMP]
•
MPRN is not registered to Supplier [SNR]
•
Duplicate 018MM has been sent in by the Old Supplier [IA]
•
COS not in Progress or Cancelled [IA]
•
There is a COLE with the COS [COLE rejection reason - New]
•
DUoS Group is invalid [DG Rejection Reason - New]
Comment existing reject reason codes will be used where possible ; new values are likely to be
needed
46
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter),
Introduce automated timelines
•
•
•
For all COS, MRSO via the Central Market System will perform automated checks similar to those for the
018MM
and where there is a COLE either implied or explicit , or a DUoS Group that is valid for Debt Flagging , then
there will be a further check carried out such that
•
if the MPRN has been Deenergised for NPA or has a Token Meter that is to be removed then no
Service Order will at this point be raised for Reenergisation / Removal of Token Meter resp.
The Old Supplier will get a notification message 110 from MRSO that they are losing an MPRN in a COS
process.
•
The First Wait Period of << 24hr or 48hr >> is kicked off. [FWP]
•
This is to allow the Old Supplier to carry out their own checks and where a Debt Flag is necessary
then the MPRN is sent by the Old Supplier to MRSO via the 018MM .
MRSO will perform automated checks via the Central Market System [See #7] on the 018MM and where
passed will send the Debt Flagged MPRN to the New Supplier via the 118M
Should these checks detect a problem then the 018MM will be rejected and the 118R will be sent to the
Old Supplier with the appropriate reject reason code
•
Should the 018MM not be received by MRSO from the Old Supplier while FWP is open then it will be
rejected via 118R
•
Where the Old Supplier has not sent in a valid Debt Flag message 018 before the expiry of FWP then the
ReEnergisation or Token Meter Removal Service Order is now raised, where needed.
•
and the Cos process will continue as normal
47
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove
Introduce automated timelines...continued
•
Otherwise at the expiry of FWP and where the Old Supplier has sent in a valid Debt Flag message 018 the
ReEnergisation or Token Meter Removal Service Order will not be raised
•
The Second Wait Period of <<24hr or 48hr >> is kicked off [SWP]
This is to allow the New Supplier time to send in an 011 Cancellation Message before Service Orders are raised.
•
•
If the New Supplier sends in a Cancellation 011MM there will be a new cancellation reason code for Debt
Flagging, and where a cancellation is for Debt Flagging there will be new validations to check if MRSO has
received the 011MM before the SWP expiry.
If not then the cancellation will be rejected on a 111R and with either the existing TIM or a new rejection
reason code.
Note that the Cancellation 011MM for Debt Flagging will not be accepted if sent in before the start of the
SWP because the 118MM will not have been sent out
See #6
Where the New Supplier does not send in a valid Cancellation 011MM by the expiry of the SWP then the
ReEnergisation or Token Meter Removal Service Orders will be raised, where needed.
•
and the Cos process will continue as normal
48
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Items specific to Option B
#8
Service Orders for certain MPRNs that are Deenergised for NPA or need a Token Meter to be removed are
prevented from being raised by this process from << 2 or 3>> and possibly up to << 3 or 4>> time periods
ref#11 for time periods
- There is no Fast-tracking element in this proposal
- Operationally, ESB Networks would not favour a new manual fast-tracking process
#9
Not all MPRNs that are Deenergised for NPA or need a Token Meter to be removed will meet the euro
criteria for Debt Flagging.
•
It is the Old Supplier and not MRSO who is able to perform this calculation after receipt of the 010MM.
This is why all of these MPRNs would be included in the process to prevent the Service Orders from being
raised , and not just those that are eligible for Debt Flagging
#10 In the specific Debt Flagging scenario where Service Orders are not being raised pending the outcome of
the Debt Flagging process then Suppliers would need to be aware that the 102P will issue even though no
Service Order has been raised at that point , and in cases where there is a cancellation of that COS then no
Service Order may have been raised at all even though a 102P has issued
•
ESB Networks SLA timelines start as normal once the Service Orders are raised.
49
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
#11
Slides on Option B follow illustrating sample Message Flows and timelines for wait periods
General
The proposal is that the start of the automated timeline will be from an identified trigger , and not from midnight.
This allows for a Service Order to be raised earlier than if using a midnight-midnight clock , and from a Customer
perspective the Re-Energisation following NPA to be processed as soon as possible
Days are Working days, and therefore Weekends and Bank Holidays are not counted within the wait period
timelines
<<48hr + 48hr >> wait periods
FWP starts from when 110 is outbound from SAP and ends a max of 48hr later
SWP starts from when 118 is outbound from SAP and ends a max of 48hr later
This timeline is consistent with WP20 and along Gas timelines
Up to 4 days longer for impacted Customers to have Service Order raised for Reenergisation of NPA or Token
Meter removal
<< 24hr + 24hr >> wait periods
FWP starts from when 110 is outbound from SAP and ends a max of 24hr later
SWP starts from when 118 is outbound from SAP and ends a max of 24hr later
Earlier raising of Service Orders than with <<48hr + 48hr >>
Less time for Suppliers to respond with 018MM [Old] , 011MM [New]
50
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Example Message flows : <<48hr + 48hr >> Wait Periods.
Slide 1 of 3
Scenarios, Timelines
2 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*2
110
FWP 48hr wait period for Debt Flag
24*1
24*2
old
new
old
new
118MM
018MM
011MM
018MM
118MM
011MM
3 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*3 [may be late]
110
018MM
118MM
4 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*4 but this is late
110
018MM
118MM
5 Old Supplier Debt Flags in 24*1, No 011 Cancellation from New Supplier
110
018MM
118MM
6 Old Supplier Debt Flags in 24*1, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
7 Old Supplier Debt Flags in 24*2, new supplier cancels directly after [ie at start SWP]
110
018MM
8 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*3
110
018MM
118MM
011MM
118MM
9 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*4 [may be late]
110
018MM
118MM
10 Old Supplier Debt Flags in 24*2, No 011 Cancellation from New Supplier
110
018MM
118MM
11 Old Supplier Debt Flags in 24*2, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
12 Old Supplier raises Debt Flag any time after 48hrs, and this is rejected via 118R
110
13 Old Supplier does not Debt Flag, New Supplier does not cancel
Pending loss of Customer is notified to Old Supplier by MRSO via 110MM
Old Supplier raises Debt Flag on using new Debt Flag field on new 018MM
Debt Flag Notification is sent from MRSO to New Supplier via 118MM
Rejection of Debt Flag Notification from MRSO to Old Supplier via 118R
New Supplier Cancels COS via existing MM with new Debt Flag viz 011MM
110
1 Old Supplier Debt Flags in 24*1, new supplier cancels in same period
Start
Time
FWP
110
SWP 48hr wait period for Cancellation
24*3
24*4
old
new
old
new
Late
011MM
011MM
011MM
018MM
118R
011MM
011MM
011MM
018MM
118R
018MM
118R
018MM
FWP Starts from when 110 is outbound from SAP
FWP ends 48hr after start of FWP
SWP starts from when 118 is outbound from SAP
SWP ends48 hrs after start of SWP
51
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Example Message flows : <<48hr + 48hr >> Wait Periods.
Slide 2 of 3
Scenarios, Timelines
2 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*2
110
FWP 48hr wait period for Debt Flag
24*1
24*2
old
new
old
new
118MM
018MM
011MM
018MM
118MM
011MM
3 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*3 [may be late]
110
018MM
118MM
4 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*4 but this is late
110
018MM
118MM
5 Old Supplier Debt Flags in 24*1, No 011 Cancellation from New Supplier
110
018MM
118MM
6 Old Supplier Debt Flags in 24*1, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
7 Old Supplier Debt Flags in 24*2, new supplier cancels directly after [ie at start SWP]
110
018MM
8 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*3
110
018MM
118MM
011MM
118MM
9 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*4 [may be late]
110
018MM
118MM
10 Old Supplier Debt Flags in 24*2, No 011 Cancellation from New Supplier
110
018MM
118MM
11 Old Supplier Debt Flags in 24*2, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
12 Old Supplier raises Debt Flag any time after 48hrs, and this is rejected via 118R
110
13 Old Supplier does not Debt Flag, New Supplier does not cancel
Pending loss of Customer is notified to Old Supplier by MRSO via 110MM
Old Supplier raises Debt Flag on using new Debt Flag field on new 018MM
Debt Flag Notification is sent from MRSO to New Supplier via 118MM
Rejection of Debt Flag Notification from MRSO to Old Supplier via 118R
New Supplier Cancels COS via existing MM with new Debt Flag viz 011MM
110
1 Old Supplier Debt Flags in 24*1, new supplier cancels in same period
Start
Time
FWP
110
SWP 48hr wait period for Cancellation
24*3
24*4
old
new
old
new
Late
011MM
011MM
011MM
018MM
118R
011MM
011MM
011MM
018MM
118R
018MM
118R
018MM
FWP Starts from when 110 is outbound from SAP
FWP ends 48hr after start of FWP
SWP starts from when 118 is outbound from SAP
SWP ends48 hrs after start of SWP
24*2 = Earliest for Re-Energisation NPA and Token Meter
removal Service Order to be raised – this will happen where
No valid Debt Flagged MM018 has been received viz
scenarios 12, 13
52
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Example Message flows : <<48hr + 48hr >> Wait Periods.
Slide 3 of 3
Scenarios, Timelines
2 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*2
110
FWP 48hr wait period for Debt Flag
24*1
24*2
old
new
old
new
118MM
018MM
011MM
018MM
118MM
011MM
3 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*3 [may be late]
110
018MM
118MM
4 Old Supplier Debt Flags in 24*1, new supplier cancels in 24*4 but this is late
110
018MM
118MM
5 Old Supplier Debt Flags in 24*1, No 011 Cancellation from New Supplier
110
018MM
118MM
6 Old Supplier Debt Flags in 24*1, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
7 Old Supplier Debt Flags in 24*2, new supplier cancels directly after [ie at start SWP]
110
018MM
8 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*3
110
018MM
118MM
011MM
118MM
9 Old Supplier Debt Flags in 24*2, new supplier cancels in 24*4 [may be late]
110
018MM
118MM
10 Old Supplier Debt Flags in 24*2, No 011 Cancellation from New Supplier
110
018MM
118MM
11 Old Supplier Debt Flags in 24*2, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
12 Old Supplier raises Debt Flag any time after 48hrs, and this is rejected via 118R
110
13 Old Supplier does not Debt Flag, New Supplier does not cancel
Pending loss of Customer is notified to Old Supplier by MRSO via 110MM
Old Supplier raises Debt Flag on using new Debt Flag field on new 018MM
Debt Flag Notification is sent from MRSO to New Supplier via 118MM
Rejection of Debt Flag Notification from MRSO to Old Supplier via 118R
New Supplier Cancels COS via existing MM with new Debt Flag viz 011MM
110
1 Old Supplier Debt Flags in 24*1, new supplier cancels in same period
Start
Time
FWP
110
SWP 48hr wait period for Cancellation
24*3
24*4
old
new
old
new
Late
011MM
011MM
011MM
018MM
118R
011MM
011MM
011MM
018MM
118R
018MM
118R
018MM
FWP Starts from when 110 is outbound from SAP
FWP ends 48hr after start of FWP
24*4 = During this period Service Orders are
raised for a COS that has had a Debt Flag
raised by the Old Supplier and the New
supplier does not cancel , or cancels late
24*2 = Earliest for Re-Energisation NPA and Token Meter viz scenarios 5, 6, 10, 11
removal Service Order to be raised – this will happen where
No valid Debt Flagged MM018 has been received viz
scenarios 12, 13
SWP starts from when 118 is outbound from SAP
SWP ends48 hrs after start of SWP
53
21 September 2011
DR1111 Automated Debt Flagging – Option B :
3*New Market Messages
Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated
timelines
Example Message flows : <<24hr + 24hr >>
Wait Periods
Scenarios, Timelines
Start
Time
FWP
FWP 24hr wait period
for Debt Flag
SWP 24hr wait period
for Debt Flag
24*1
Late
24*2
1
Old Supplier Debt Flags in 24*1, new supplier cancels directly after [ie at start SWP]
110
old
018MM
2
Old Supplier Debt Flags in 24*1, new supplier cancels in SWP 24*2 [may be late]
110
018MM
new
118MM
011MM
118MM
3
Old Supplier Debt Flags in 24*1, 011 Debt Flag Cancellation [New Sup] is late
110
018MM
118MM
4
Old Supplier Debt Flags in 24*1, No 011 Cancellation from New Supplier
110
018MM
118MM
5
Old Supplier raises Debt Flag any time after the end of FWP 24hrs, and this is rejected via 118R
110
6
Old Supplier does not Debt Flag, New Supplier does not cancel
Pending loss of Customer is notified to Old Supplier by MRSO via 110MM
Old Supplier raises Debt Flag on using new Debt Flag field on new 018MM
Debt Flag Notification is sent from MRSO to New Supplier via 118MM
Rejection of Debt Flag Notification from MRSO to Old Supplier via 118R
New Supplier Cancels COS via existing MM with new Debt Flag viz 011MM
110
018MM
118R
old
new
011MM
011MM
018MM
118R
018MM
FWP Starts from when 110 is outbound from SAP
FWP ends 24hr after start of FWP
SWP starts from when 118 is outbound from SAP
SWP ends 24 hrs after start of SWP
24*1 = Earliest for Re-Energisation NPA and Token Meter
removal Service Order to be raised – this will happen where
No valid Debt Flagged MM018 has been received viz
scenarios 5, 6
24*2 = During this period Service Orders are
raised for a COS that has had a Debt Flag
raised by the Old Supplier and the New
supplier does not cancel , or cancels late
viz scenarios 3,4
54
21 September 2011
DR1111 Automated Debt Flagging – Volumes
DeEnergisations
Apr-2012
No COLE , Debt Flag Valid
35
COS Cancelled
7
DeEnergisations
May-2012
No COLE , Debt Flag Valid
64
COS Cancelled
20
These stats indicate the level of MPRNs where there would be a
delay under Option 6 in raising Service Orders for ReEnergisation
•
35 in April , 64 in May
also indicated is the level of those where the COS is subsequently cancelled
•
7 in April , 20 in May
and where the COS continued
•
28 in April, 44 in May
55
21 September 2011
DR1111 Automated Debt Flagging – Next Steps
Asking for your consideration of this presentation and to feedback your comments to RMDS
over the next three weeks and by 18th July 2012
•
If you wish to comment on identified items then we ask you to flag your comment with the
associated item # reference number
•
feedback will be circulated by the next IGG
•
the intention is to arrive at a draft text for DR1111 for the earliest possible IGG
Thank You
56
21 September 2011
IGG Meeting
AOB
27th June 2012
Retail Market Design Service
Page 57
Next Steps
Diary dates for next two IGG meetings:
Wednesday 8th August 2012 – Belfast
Wednesday 19th September 2012 - Dublin
Dates included on Calendar of Events
on RMDS website www.rmdservice.com
27th June 2012
Retail Market Design Service
Page 58
Next Steps
 Diary Dates for next two Conference Calls:
Thursday 19th July 2012
Thursday 30th August 2012
Dates included on Calendar of Events on
RMDS website www.rmdservice.com
 Call details are as follows:
 LoCall: 0818 301 111
Local Access: +353-(0)1- 664 8888
 Guest Passcode (Pin):167172
27th June 2012
Retail Market Design Service
Page 59
Thank You
27th June 2012
Retail Market Design Service
Page 60