retail market harmonisation working group 4 · 2009. 11. 16. · niaur offices, belfast 16 november...

Harmonisation Working Group

NIAUR Offices, Belfast

16 November 2009

Retail Market Harmonisation Working Group 4


Agenda

Minutes from HWG3 2nd NovemberMatters Arising & Outstanding from previous HWG meetingsEU Third PackagePresentation of Customer Data and Meter Point CharacteristicsProposal Agreements for FieldworkData Processing and Aggregation – Advance ThinkingAny Other Business

Including Baseline and Change ControlNext Meeting

2 Private and Confidential


Matters From Previous HWG - Resolved

NIE to issue message 303R when a CoS read provided on message 010 or 210 is rejectedCoS Estimate Is Not Allowed

Last Actual Read Date is included on messages 102 and 102PThis field can be used to determine if an estimate would not be allowed



Matters From Previous HWG – Carried Forward

NIE MPRN Website Data Publication Legal ReviewCER Consultation & CoP on Objection & DebtEAC effective date available in aggregation audit trail – to Dec 1stESB and NIE will investigate possible differences in the check digit algorithm and report backDe-energisation CoP review – to detailed designReview of response messages when a CoS estimate is not possibleReview of CoS cancellation time-out reasonsExtension of CoS customer read window to D-5 (IGG status)



3rd Package

IntroductionMain provisions of the Third Energy PackageRetail market amendments


Third Package: main provisions Retail market measures Stronger powers for national regulators Effective unbundling of networks Regulatory Agency at EU level (ACER) Cooperation of network operators (ENTSO)

3rd Package


New provisions for the operation of the retail market: Published rules on the roles and responsibilities of all market players Information for consumers: European Energy Consumer checklist New deadlines on switching, 3 weeks, and receipt of final bill, 6 weeks Consumer access to consumption data in sufficient time periods Implementation of Smart Metering .Promotion of Smart Grids

3rd Package


Uncertainty on 3rd package:Only the directive is published.We still need the EU Commission Guidance Document.Governments use that to draft legislation.We comply with the legislation.

3rd Package


Customer Details and Meter Point Characteristics

NIE proposeTo introduce a separate process for Change of Legal Entity / Change of Tenancy similar to that employed in the RoITo introduce additional market messages for Suppliers as follows:

• 016, 116 and 116N (CoLE/CoT)• 301N (Meter Point Characteristics Change notification) • Note 014R, 114, 301, 321 introduced by Enduring Solution

– (014R was originally identified as N114R),To retain message N140 sent to a previous Supplier for previous tenancy tracking



Change of Customer Details (mod 1.1)

Change of Customer Details submitted by Supplier using message 013Message 014R issued to reject changesMessage 114 issued to confirm changesThere may be a mixture of items accepted and items rejected

Common address, name and contact data segment formats adopted as per previous HWG2 and HWG3 presentationsMultiple messages required if more than one medical or special needs valueDeletion flags will be introduced in NI for some data fields

Medical and special needs vales to be deleted to be specified Previous tenancy data

No longer supported on message 013 in Northern IrelandWill be processed on message 016 (CoLE/CoT) in Northern Ireland only

MCR0169 agreed in RoI introduces new field on the following messages whereby a Supplier can indicate customer agreement to display medical equipment details via the MPRN web-site :

010, 013, 016 and 017



Change of Customer Details Message 013


Message additionally contains MP Address, Customer Name, Customer Contact, Notification Address and Technical Contact segments

Republic of Ireland 013 Northern Ireland N013Field Use Chars Type Pattern Value Use Field Use Chars Type Pattern Value Comment

MPRN req 11 string no no MPRN req 11 string no no Supplier must hold registrationMPBusinessReference req 35 string no no MPBusinessReference req 35 string no noChangeMeterAddressFlag req boolean ChangeMeterAddressFlag req booleanDeletePOBoxAddressFlag req boolean DeletePOBoxAddressFlag req boolean PO box in notification addressSupplierMPID req 3 string no no SupplierMPID req 3 string no no AccessInstructionsText opt 40 string yes no AccessInstructionsText opt 40 string yes no NIE review before updatingDeleteAccessInstructionsFlag req boolean DeleteAccessInstructionsFlag req boolean NIE review before deleting

ChangeOfUsageCode opt 2 string no yes ChangeOfUsageCode opt 2 string no yesCombined premise value applies in NI only

EAI_Code opt 5V string no yes EAI_Code opt 5V string no yes NI / RoI code sets differ

DeleteMedicalEquipmentNeedsFlag req boolean DeleteMedicalEquipmentNeedsFlag req booleanValue to be deleted provided below

DeleteCustomerServiceDetailsFlag req boolean DeleteCustomerServiceDetailsFlag req booleanValue to be deleted provided below

Missing COT_LE_FlagMissing SupplyAgreementFlag

MeterReaderPassword opt 8 string no no MeterReaderPassword opt 8 string no noUsed in NIE only, regulatory requirement

DeleteMeterReaderPassword req boolean DeleteMeterReaderPassword req boolean

MedicalEquipmentDetailsCode opt 4 string no yes MedicalEquipmentDetailsCode opt 4 string no yesNIE adopt ESB approach; multiple values possible in NI

CustomerServiceDetailsCode opt 4V string no yes CustomerServiceDetailsCode opt 4V string no yesNIE to adopt ESB approach and merge lists

Remove from schemaRemove from schema


Change of Customer Details Rejection 014R


Message does not currently exist in NIMessage additionally contains MP Address and Customer Name segments

Republic of Ireland 014RUse Field Use Chars Type Pattern Value

MPRN req 11 string no noSupplierMPID req 3 string no noMPBusinessReference req 35 string no no

reqM RejectReasonCode req 2-3V string no yes


Change of Customer Details Confirmation 114


Message does not currently exist in NI (message N195 is used)Message will also be sent where networks detect MP address changeMessage additionally contains MP Address and Customer Name segmentsOther than MP Address, Customer Name, DUoS Group and Load Profile message 114 does not contain updated values

Republic of Ireland 114Use Field Use Chars Type Pattern Value

MPRN req 11 string no noSupplierMPID req 3 string no noMPBusinessReference opt 35 string no noDUOS_Group opt 4 string no yesChangeOfUsageFlag req none boolean no noMeterPointAddressChangedFlag req none boolean no noCustomerDetailsChangedFlag req none boolean no noMessageStatusCode req 1 string no yesLoadProfileCode opt 3 string no yesEffectiveFromDate opt date


Change of Tenancy / Legal Entity

Change of Tenancy / Legal Entity submitted by Supplier using message 016Message 116R issued to reject CoT / CoLEMessage 116 issued to confirm changesCannot receive both 116R and 116 for same transactionMessage 116N issued to New Supplier if a Change of Supplier is in progress

• Responsibility with New Supplier to cancel; otherwise CoS continuesMessage 300 issued to confirm readings (if provided or, in RoI only, estimated)Message 303R issued to reject readings when invalid meter data

• Does not apply to future dated readings or invalid readingsMessages 014R issued to reject change of usage Message 114 issued to confirm change of usage (i.e. a change of DUoS tariff)Message 701 (consumption) issued by ESB in RoI only for unmetered sites Message 140 issued to previous Supplier based on previous tenancy data supplied in Northern Ireland only

Where 303R and/or 014R are issued, the CoT/CoLE itself will continueNote detail of messages 300, 303R and 701 will be covered in a future HWG on December 1st



Change of Tenancy / Legal Entity - Data

Common address, name and contact data segment formats adopted as per previous HWG2 and HWG3 presentationsA request to change Meter Point Address cannot be submitted using message 016A Supplier must follow up with additional 013 message(s)

if more than one medical or special needs valueif it is required to provide or change access instructions



Change of Tenancy / Legal Entity Required Data and Readings

CoT / CoLE may be future dated or past datedCoT / CoLE and any readings will be dated at a provided, valid required dateIf there is no date provided, then the message receipt date will be used for both the CoT/CoLE and any estimates. Readings will be ignoredIf date is prior to the last DUoS bill date, then the message receipt date will be used for the CoT/CoLE but any readings are ignored

• and an estimate is used in RoI for non MD sites below 30kVANIE propose to introduce a check against dates that are significantly into the future

Readings may be provided on message 016Readings are ignored for interval, MD or unmetered sitesReadings are ignored on a future dated CoT/CoLEReadings accepted will be advised using message 300Readings rejected will be advised using message 303R

• This does not reject the CoLE/CoT and does not apply to future dated readingsWhere readings are invalid or no readings are provided:

• ESB will estimate readings, provided DUoS billing has not occurred, and provide these on message 300. If necessary ESB wait until the “future” date before estimation

• NIE do not propose to estimate readings



Change of Tenancy/Legal Entity Message 016


Message does not currently exist in NI (message N013 is used)Message additionally contains Customer Name, CoT History, Customer Contact, Notification Address, Technical Contact and Party Contact segments

MeterID optM MeterCategoryCode opt 15V string no no Not used by NIESerialNumber opt 9V string no no Mandatory in NI, under ESB review

Register optM MeterRegisterSequence opt 3V string no noTimeslotCode opt 10V string no yes Mandatory in NIReadingValue req 15,3 string no noReadTypeCode req 2V string no yes Set to SCRegisterTypeCode opt 2F string no yes Not used by NIE

Republic of Ireland 016Segment Use Field Use Chars Type Pattern Value Comment

Top Level MPRN req 11 string no no Supplier must hold registrationMPBusinessReference req 35 string no noReadReasonCode opt 2F string no yes Set to 27 if reading providedSupplierMPID req 3 string no noRequiredDate opt date Can be omitted, future or past

ChangeOfUsageCode opt 2 string no yesCombined premise value applies in NI only

EAI_Code opt 5V string no yes NI and RoI code sets are differentSupplyAgreementFlag req boolean

MeterReaderPassword opt 8 string no noNIE only, regulatory requirement, ESB have different process

MedicalEquipmentDetailsCode opt 4 string no yesNIE to adopt ESB approach; multiple values possible in NI

CustomerServiceDetailsCode opt 4V string no yesNIE to adopt ESB approach and merge lists


CoT / CoLE Rejection Message 116R


Message does not currently exist in NI

Republic of Ireland 116RUse Field Use Chars Type Pattern Value

MPRN req 11 string no noMPBusinessReference req 35 string no no

reqM RejectReasonCode req 2-3V string no yes


CoT / CoLE Confirmation Message 116


Message does not currently exist in NI Message additionally contains Party Contact segmentOther than DUoS Group and EAI code message 114 does not contain updated values

Republic of Ireland 116Field Use Chars Type Pattern Value

MPRN req 11 string no noSupplierMPID req 3 string no noMPBusinessReference req 35 string no noEffectiveFromDate req dateDUOS_Group req 4 string no yesEAI_Code opt 5V string no yes


CoT / CoLE Notification Message 116N


Message additionally contains Party Contact segmentMessage does not currently exist in NI

Republic of Ireland 116NField Use Chars Type Pattern Value

MPRN req 11 string no noSupplierMPID req 3 string no noEffectiveFromDate req dateDUOS_Group req 4 string no yesEAI_Code opt 5V string no yes


Previous Tenancy Message 140


Message will continue to be sent by NIE only to the previous Supplier when a Supplier advises a CoT and provides previous Supplier data Message contains:

MPRNSupplier ID (of the Supplier reporting the CoT)Customer Name segmentMeter Point Address segmentChange of Tenancy History detailsCustomer Contact detailsNotification Address details

Common address, name and contact data segment formats adopted asper previous HWG2 and HWG3 presentations


Change of Usage

Change of Usage may be submitted on messages 013 or 016NIE also propose to infer a Change of Usage from a requested Meter Configuration where this can be done uniquely

Refer to NIE data codes spreadsheet for allowable MCC to usage type combinationsWhere usage type cannot be uniquely determined, NIE will look for message 013 or 016

Change of Usage will take effect from:The date of any valid readings provided with the CoU message (016)The date of any fieldwork if the CoU is derived from or associated with fieldworkThe day after any previous billable reading The day after the last DUoS bill, if none of the above applyThe Change of Usage date may therefore vary from the CoT/CoLE date as estimates other than those used in CoS or DUoS Billing are not used for CoU



Message Matrix – Fieldwork & Customer Data


ScenarioChange of Usage

Change of MCC

Change of Tenancy

Change of MP Status Mess.1 Mess.2 Mess.3 Mess.1 Mess.2 Mess.3

1 YES YES YES Energisation 030 016 017 030 0132 YES YES YES NO 030 016 030 0163 YES YES NO Energisation 030 013 017 030 0134 YES YES NO NO 030 013 030 0135 YES NO YES Energisation 017 013 017 0136 YES NO YES NO 016 0167 YES NO NO Energisation 017 013 017 0138 YES NO NO NO 013 0139 NO YES YES Energisation 030 016 017 030

10 NO YES YES NO 030 016 030 01611 NO YES NO Energisation 030 017 03012 NO YES NO NO 030 03013 NO NO YES Energisation 017 017

13d (NIE) NO NO YES De-energise 017 01714 NO NO YES NO 016 01615 NO NO NO Energisation 017 017

15d NO NO NO De-energise 017 017

Sent in NI

Sent in RoI or in NI where Supplier wishes to explicitly use

017 energise

Matrix showing message combinations for Change of Usage, Change of MCC, Change of Tenancy and Energisation

requests.


Meter Point Characteristics

NIE is introducing message 301N, aligned to ESB, to provide an advance notification of changes to Meter Point Characteristics

Will be sent when a quote is issued to customer for changesOptional fields will communicate the data that is to be changedCompletion of process may lead to issue of messages 331 and/or 332

If a change only requires a change in metering configuration the request should be made through the Supplier using message 030NIE is aligning with the ESB format for message 301 notification of changes to Meter Point Characteristics

Chargeable service capacity will be added but not used in RoIWill be used on message 301 in NI when annual CSC updates are madeFull data is provided as it stands on system following the change, together with an effective date for the changesMessage 301 was already agreed to be introduced within Enduring Solution



MP Characteristics Notification Message 301N


Message additionally contains Meter Point Address segmentMessage does not currently exist in NI

Republic of Ireland 301NField Use Chars Type Pattern Value Comments

MPRN req 11 string no no DLF_Code opt 5 string no noTransformerLossFactor opt 6,4 decimal no no Not used in NIConnectionSystemCode opt 10 string no yesUnmeteredDetails EstimatedUsageFactorLoadProfileCode opt 3 string no yesMaximumImportCapacity opt 9 int no noLoadFactorCode opt 10 string no yes Not used in NIMaximumExportCapacity opt 9 int no noMeterConfigurationCode opt 10 string no yesDUOS_Group opt 4 string no yes

agreed to remove from schemaagreed to remove from schema


MP Characteristics Change Message 301


Message does not currently exist in NI (message N195 is used)Message additionally contains Meter Point Address segmentMessage does not contain MIC Start Date, to be reviewed

Republic of Ireland 301Field Use Chars Type Pattern Value Comment

MPRN req 11 string no no DLF_Code opt 5V string no noTransformerLossFactor opt 6,4 decimal no no Not used in NIConnectionSystemCode opt 10V string no yesUnmeteredDetails EstimatedUsageFactorLoadProfileCode opt 3 string no yesMaximumImportCapacity opt 9 int no noCurrentChangeableServiceCapacity opt 9 int no no Not used in RoILoadFactorCode opt 10V string no yes Not used in NIMaximumExportCapacity opt 9 int no noMeterConfigurationCode opt 10V string no yesEffectiveFromDate req dateDUOS_Group opt 4 string no yes

agreed to remove from schemaagreed to remove from schema


Read Cycle Change Message 321


Message does not currently exist in NI (Message N195 currently used)

Republic of Ireland 321Field Use Chars Type Pattern Value Comment

MPRN req 11 string no no ReadFrequencyCode req 3V string no yes Code list merged

ReadCycle req 3 string no noCycle code matches to read calendar

NIE is aligning with the ESB format for message 321 notification of permanent changes to Read Cycle

Message was agreed to be introduced within Enduring Solution


Proposal Agreement - Fieldwork

We will briefly reviewProposals presented on 2nd NovemberProposal changes made as a result of comments made and clarifications discussed on 11th November – highlighted in red

We will thenSeek general agreementList exceptions to agreementWork on the items agreed as outstanding – requiring further workRefer other exceptions to next HSG (26th November) for decision Issue message guides (date t.b.a.)Issue document summarising procedural changes (early December)

• NIE and ESB will issue separate documents• There may be no changes and hence no document for ESB



Fieldwork Summary

What key items has changed since HWG3Message 017 is not used for unmetered in Northern IrelandExtension to scope of message 260 in Northern IrelandProposals on message 311 have been withdrawn pending reviewClarification of fieldwork withdrawal message handling

What remains the sameMessagingItems not in red type

What remains outstanding and is excluded from agreementMerging and agreement of various data code listsTechnical facilities to allow integration of appointment bookingsystems and supplier systems (to be addressed in detail design)



Fieldwork – Appointment Booking

ESB Web-Site allows Supplier to identify available appointment slotsAppointment date and time is entered on messageAppointment ID is not appropriate as a firm appointment has not been made

NIE Web-Site allows Supplier for book an appointmentAppointment ID is entered on messageAppointment date and time:

• can be used to indicate a preferred date where an appointment cannot be booked (e.g. HH metering) ; but

• should be omitted if an appointment ID has been madeSuppliers have requested facilities to integrate web-site appointments with their own fieldwork management systems

• this will be considered during detailed design



Fieldwork – Messaging Introduction

NIE to introduce messages 017, 030, 252 and 260Message 031 replaced by the above messagesNIE to introduce response messages as per RoI design

106D/E; 117R/D; 130R/D; 137R; 352RMessage 131 replaced for most purposes with a new version consistent with ESB MCR0171



Fieldwork – Messaging Fields General

NIE to carry Market Participant Business Reference through to response messagesReview of code list contents to harmonise

e.g. works type, observation codes, reason codes, rejection codesChange of Tenancy allowed on message 017 only

Also will be allowed on 010 and 016Message 017 is only fieldwork message to include customer name, contact address, notification address and technical contactAll request messages include party contact segment



Party Contact

Republic of Ireland 017,030,252,260 Northern Ireland N031Use Field Use Chars Pattern Value Use Field Use Chars Pattern Valueopt Email opt 70V no no opt Email opt 70V no noopt PhoneOne - Number opt 20 no no opt PhoneOne - Number opt 20 no no

PhoneOne - Extn opt 10 no no PhoneOne - Extn opt 10 no noPhoneTwo - Number opt 20 no no PhoneTwo - Number opt 20 no noPhoneTwo - Extn opt 10 no no PhoneTwo - Extn opt 10 no noFax - Number opt 20 no no Fax - Number opt 20 no noFax - Extn opt 10 no no Fax - Extn opt 10 no no


Meter Point Status Change (mod v1.1)MP Status Change using Message 017Responses using

106D/E Interval Meter Point De-Energised or Energised117R Request Rejection137R Appointment Rejection (ESB only)117D Delay prior to appointment date – no significant NIE use expected131 Usage described in later section on message 131306; 307; 331, 332; Readings, Meter Installs if removed on de-energising700 Unmetered Inventory and 701 Unmetered Consumption in RoI only

Message 700 will also be sent in NI after energisation/de-energisationMessage 017 can be used to advise CoT/CoLE

Required Date will refer to the CoT/CoLE Date (not fieldwork date)• If omitted for CoT/CoLE then CoT/CoLE occurs on receipt

Change of Usage Type can only be notified on message 013/01634 Private and Confidential


Meter Point Status Change – Process DifferencesRestrictions on domestic de-energisation in NI

De-energisation for non payment not allowedDe-energisation when there is no supply agreement is allowed

• Supply agreement flag must be set to “No”, site must be vacant. • De-energisation is not completed if there is evidence of occupation

– Request cancelled using message 131 status C2– DUoS charges are not suspended

NIE to review De-energisation Code of Practice• Including repeat visits to de-energise when no Supply Agreement

De-energisation suspends capacity and standing charges in NIIn NI, message 017 will not be used for unmetered energisation/de-energisation

• There are no single point unmetered sites in NIKeypad tariff configuration can be changed on energisationCustomer name is required in NI for HV Sites



Message 017 Change of Meter Point Status Request


Also includes party contact, customer name, contact address, notification address and technical contact

Republic of Ireland 017 Northern Ireland N031Field Use Chars Pattern Value Use Field Use Chars Pattern Value Comments

MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noMeterPointStatusCode req 2V no yes MeterPointStatusCode req 2V no yesMeterPointStatusReasonCode req 3V no yes MeterPointStatusReasonCode req 3V no yesSupplierMPID req 3 no no SupplierMPID req 3 no noCOT_LE_Flag req COT_LE_Flag reqSupplyAgreementFlag opt SupplyAgreementFlag opt Must be Y for re-energisationRequestStatusCode req 3V no yes RequestStatusCode req 3V no yesAppointmentDate opt AppointmentDate opt Usage varies, see presentationAppointmentTimeSlot opt 3F no yes AppointmentTimeSlot opt 3F no yes Usage varies, see presentationAccessInstructionsText opt 40 yes no AccessInstructionsText opt 40 yes noEAI_Code opt 5V no yes EAI_Code opt 5V no yesMedicalEquipmentDetailsCode opt 4 no yes MedicalEquipmentDetailsCode opt 4 no yesCustomerServiceDetailsCode opt 4V no yes CustomerServiceDetailsCode opt 4V no yesRequiredDate opt RequiredDate opt Apply to CoT onlyAccessArrangements req 100 yes no AccessArrangements req 100 yes noTariffConfigurationCode opt 2F yes no TariffConfigurationCode opt 2F yes no NIE use onlyAppointmentId opt AppointmentId opt NIE use onlyMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing UsageTypeMissing NotesMissing EnquiryID to be removed from schema

to be removed from schemato be removed from schema

to be removed from schema

To Be Defined To Be Definedto be removed from schema


Message 117R Rejection of Request


Republic of Ireland 117R Northern Ireland N131RUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value

MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noRequestStatusCode req 3V no yes RequestStatusCode req 3V no yesMissing NetworksReferenceNumberMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing SupplierMPIDMissing RequiredDateMissing EffectiveDateMissing CommentsMissing AppointmentIDMissing EnquiryIDMissing NewAppointmentDateMissing optM RequestStatusReason

reqM RejectReasonCode req 2-3 no yes reqM RejectReasonCode req 2-3 no yes








Message 137R Rejection of Appointment

Message 137R in RoI is used for a variety of reasonsInvalid call typeRoute/time invalidTimeslot not availableMeter works delay

Use of 137R in NI will be restricted to failure to provide a fieldwork request message after making an online appointment booking

NIE will issue warning by e-mail prior to rejectionTimeline for e-mail and rejection to be addressed in detailed design

Applies toChange of Meter Point StatusMeter WorksSpecial Read Request (NI only)



Message 137R Appointment Rejected


Republic of Ireland 137RField Use Chars Pattern Value Comments

MPRN req 11 no noMPBusinessReference opt 35 no noAppointmentDate optAppointmentTimeSlot opt 3F no yesAppointmentRejectionReason req 4F no yes Missing fieldwork request only in NIAppointmentID opt To Be Defined


Message 117D Fieldwork Delayed


Republic of Ireland 117D Northern Ireland N131DUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value


reqM DelayReasonCode req 4V no yes reqM DelayReasonCode req 4V no yes







Delay reason codes may be extended


Message 106D Interval Meter Point De-energised


Republic of Ireland 106D Northern Ireland N131CField Use Chars Pattern Value Use Field Use hars Pattern Value Comments

MPRN req 11 no no MPRN req 11 no noMPBusinessReference opt 35 no no MPBusinessReference opt 35 no noMeterPointStatusCode req 2 no yes MeterPointStatusCode req 2 no yesEffectiveFromDate req Date EffectiveFromDate req Date

Comments opt 254 no no Comments opt 254 no no

e.g. reason for NIE initiated de-energisation

Missing NetworksReferenceNumberMissing MeterWorksTypeCodeMissing MeterConfigurationCode Missing SupplierMPIDMissing RequiredDateMissing RequestStatusCodeMissing AppointmentIDMissing EnquiryIDMissing NewAppointmentDate

Missing optM RequestStatusReason to be removed from schema







Message 106E Interval Meter Point Energised


Republic of Ireland 106E Northern Ireland N131CField Use Chars Pattern Value Use Field Use Chars Pattern Value

MPRN req 11 no no MPRN req 11 no noMPBusinessReference opt 35 no no MPBusinessReference opt 35 no noMeterPointStatusCode req 2 no yes MeterPointStatusCode req 2 no yesEffectiveFromDate req Date EffectiveFromDate req DateComments opt 254 no no Comments opt 254 no noEstimatedUsageFactor MissingMissing NetworksReferenceNumberMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing SupplierMPIDMissing RequiredDateMissing RequestStatusCodeMissing AppointmentIDMissing EnquiryIDMissing NewAppointmentDateMissing optM RequestStatusReason




to be removed from schema to be removed from schema





Meter WorksMeter Works requested using Message 030Responses using

130R Request Rejection137R Appointment Rejection (ESB only)130D Delay prior to appointment date – no significant NIE use expected131 Usage described in later section on message 131 331 (Interval), 332 (Non Interval, to be presented December 1st)

Message 030 cannot be used to advise CoT/CoLEAn updated set of Meter Works Types to be agreed reflecting the differing metering arrangements in NI and RoI

Includes meter tests and, in NI, other problems where the Supplier knows an on-site appointment is required



Meter Works – Processing DifferencesDifferences between keypad and token metering

Site visit may not always be required in NIData to support request is different

Validation of customer name in NI for HV Sites (not on message)NIE propose to imply change of usage type from message 030

Message 013/016 not required where usage type can be determined from metering configurationNIE will trap certain types of ‘implausible’ changes (e.g. non-domestic to keypad)NIE will look for message 013 or 016 if usage type cannot be determinedUsage type remains as is if it is supported by new meter configuration Supplier to send message 013 or 016 if implied usage type is incorrect

NIE propose to imply energisation is required when receiving an 030 message that requests a change of metering configuration

Supply agreement must previously be set to ‘Y’Typically supports installing/energising keypad at site de-energised for non-payment by using only one message (assuming no change of tenancy)ESB expect message 017 to energise in addition to 030NIE will also support message 017 in addition to 030 but appointment ID must be the same on both messages



Message 030 Meter Works Request



MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noTokenMeterDetails opt 30 no no TokenMeterDetails opt 30 no no ESB use onlyMeterWorksTypeCode req 3 no yes MeterWorksTypeCode req 3 no yes Merge work type listsMeterConfigurationCode opt 10 no yes MeterConfigurationCode opt 10 no yes SupplierMPID req 3 no no SupplierMPID req 3 no noSupplyAgreementFlag SupplyAgreementFlagRequestStatusCode req 3V no yes RequestStatusCode req 3V no yesAppointmentDate opt Date AppointmentDate opt Date Usage varies, see presentationAppointmentTimeSlot opt 3 no yes AppointmentTimeSlot opt 3 no yes Usage varies, see presentationAccessArrangements req 100 yes no AccessArrangements req 100 yes no TariffConfigurationCode opt 2 yes no TariffConfigurationCode opt 2 yes no NIE use onlyAppointmentID opt AppointmentID opt NIE use onlyMissing COT_LE_FlagMissing RequiredDateMissing UsageTypeMissing NotesMissing EnquiryID


To Be Defined To Be Defined


to be removed from schema to be removed from schema


Also includes party contact


Message 130R Rejection of Request


Republic of Ireland 130R Northern Ireland N131RUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value










Message 130D Meter Works Delayed


Republic of Ireland 130D Northern Ireland N131DUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value


reqM DelayReasonCode req 4V no yes reqM DelayReasonCode req 4V no yes







Delay reason codes may be extended


Special ReadsMeter Works requested using Message 252Responses using

352R Request Rejection137R Appointment Rejection (NI only)131 Usage described in later section on message 131 (NI only)300S Special Read



Message 252 Special Read Request




MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noSupplierMPID req 3 no no SupplierMPID req 3 no no ReadTypeCode req 2V no yes ReadTypeCode req 2V no yesReadReasonCode req 2V no yes ReadReasonCode req 2V no yesRequestStatusCode req 3V no yes RequestStatusCode req 3V no yesRequiredDate opt Date RequiredDate opt Date ESB use onlyAccessArrangements opt 100 yes no AccessArrangements opt 100 yes noAppointmentID opt AppointmentID opt NIE use onlyMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing COT_LE_FlagMissing SupplyAgreementFlagMissing TariffConfigurationCode Missing UsageTypeMissing NotesMissing EnquiryID to be removed from schema






Message 352R Special Read Request Rejection


Republic of Ireland 352R Northern Ireland N131RUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value Comments

MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noSupplierMPID req 3 no no SupplierMPID req 3 no noRequiredDate opt RequiredDate opt ESB use onlyRequestStatusCode req 3V no yes RequestStatusCode req 3V no yesReadTypeCode req 2V no yes ReadTypeCode req 2V no yesReadReasonCode req 2V no yes ReadReasonCode req 2V no yesMissing NetworksReferenceNumberMissing MeterWorksTypeCodeMissing MeterConfigurationCode Missing EffectiveDate Missing CommentsMissing AppointmentIDMissing EnquiryIDMissing NewAppointmentDateMissing optM RequestStatusReason








Meter Problems and Damage

Meter problems / damage reported by Supplier using message 260NIE propose to include the following in the scope of message 260

• revenue protection complaints • meter reading complaints• usage queries • general meter reading enquiries

Observation text can be used for any special customer contact detailsResponse report using message 261

Message 261 will only issue in response to message 260 to close off process upon final resolutionMessage 131 can also issue as an interim, see later slide

Meter problems and damage raised through message 260 (Supplier) may also lead to meter replacements reported using the normal messages 331 and 332



Meter Problems and Damage - DifferencesSending message 261 in response to message 260

NIE will always return a 261 message in response to a 260 messageIn RoI there are exceptions to responses using message 261

• E.g. glass broken does not generate a response• A full list is available with HWG4 materials on RMDS web-site



Message 260 Observation of Problem/Damage or Tampering



Republic of Ireland 260 Northern Ireland N031Use Field Use Chars Pattern Value Use Field Use Chars Pattern Value Comments

MPRN req 11 no no MPRN req 11 no noMPBusinessReference req 35 no no MPBusinessReference req 35 no noSupplierMPID req 3 no no SupplierMPID req 3 no no ObservationCode

req 3F no yesObservationCode

req 3F no yesList of codes may be extended

ObservationDate req Date ObservationDate req Date ObservationText opt 512 yes no ObservationText opt 512 yes noMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing COT_LE_FlagMissing SupplyAgreementFlagMissing RequestStatusCodeMissing RequiredDateMissing AccessArrangementsMissing TariffConfigurationCodeMissing AppointmentIDMissing UsageTypeMissing NotesMissing EnquiryID

opt MeterCategoryCode opt 15V no no opt MeterCategoryCode opt 15V no noSerialNumber req 9V no no SerialNumber req 9V no no









Message 261 Resolution of Problem or Damage


Republic of Ireland 261 Northern Ireland N131CUse Field Use Chars Pattern Value Use Field Use Chars Pattern Value Comments

MPRN req 11 no no MPRN req 11 no noMPBusinessReference opt 35 no no MPBusinessReference opt 35 no no

ObservationCode req 3 no yes ObservationCode req 3 no yesList of codes may be extended

ObservationDate req ObservationDate req DateObservationText opt 512 yes no ObservationText opt 512 yes no Missing NetworksReferenceNumberMissing MeterWorksTypeCodeMissing MeterConfigurationCodeMissing SupplierMPIDMissing RequiredDateMissing RequestStatusCode Missing EffectiveDateMissing CommentsMissing AppointmentIDMissing EnquiryIDMissing NewAppointmentDate Missing opt RequestStatusReason

opt MeterCategoryCode opt 15V no no opt MeterCategoryCode opt 15V no noSerialNumber req 9V no no SerialNumber req 9V no no







Date




Message 311 Meter Problem Notification


Republic of Ireland 311Use Field Use Chars Pattern Value Comments

MPRN req 11 no noMPBusinessReferenceObservationCode req 3 no yes List of codes may be extendedObservationDate req Date ObservationText opt 512 yes no

opt Email opt 70V no noopt PhoneOne - Number opt 20 no no

PhoneOne - Extn opt 10 no noPhoneTwo - Number opt 20 no no PhoneTwo - Extn opt 10 no noFax - Number opt 20 no noFax - Extn opt 10 no no

optM MeterCategoryCode opt 15V no no SerialNumber opt 9 no no


NIE proposals for message 311 remain under review


Fieldwork Withdrawal

In RoI withdrawal messages should mirror request messages…..except that the request status is set to ‘W’

Matching of Market Participant Business Reference is keyIn NI withdrawal messages should also mirror request messages

NI will check at least the following fields for a direct match:• MPRN• Market Participant Business Reference• Appointment Id• MP Status(017),Meter Works Type(030),Read Type/Reason (252)

Where a withdrawal request is rejected, NI propose to respond using message 117R, 130R and 352R with a request status of ‘W’



Message 131 Fieldwork Status

Message 131 implementation will be broadly consistent with MCR171 in RoIMessage 131 will advise on cancellation, rescheduling, completion, non-completion of fieldwork initiated through messages 017, 030, 252 and 260)Message 131 will not be used to acknowledge acceptance of requests

Suppliers have indicated this has little valueReason, observation, work type and other codes described in MCR0171 will be reviewed and additional codes relevant to NIE business practice added where appropriate



Message 131 Fieldwork Status Code


Status Code

Meaning Usage

X Work is Cancelled

Supplier Withdrawal Duplicate (RoI only)

C1 Work Complete, Call Complete

Meter tests and revenue protection only

C2 Work Incomplete, Call Complete - cancelled

Call complete but work cancelled (either as a result of visit or subsequently). Process terminated.

R Call complete, work (to be) rescheduled

A further visit is required which the networks company will arrange

S (NI only)

Call complete, work (to be) rescheduled

A further visit is required which the Supplier must arrange through on-line booking

Use of status R in NI includes cases where NIE are unable to keep an appointment


Message 131 Usage Matrix


Status Code S and responses to 252 applies in NI only260/R,S,X,C2 – No circumstance envisaged for use in NI 311 – Sending of message 131 apply to ESB onlyC1 – responses and alternatives detailed on next slide

Table describes where each message 131 type is issued

Sent only by NIE

Sent by ESB & NIE Sent

only by ESB

A R S X C1 C2 017 NO YES NIE YES NO YES 030

NO YES NIE YES YES

(M02/3) YES 252 NO NIE NIE NIE NO NIE 260 NO ESB NO ESB YES ESB 311

(ESBN)

N/A NO

N/A

N/A ESB ESB


Message 131 Usage Matrix – C1

017Messages 106D/E, 306, 307, 700, 701 issues instead of C1

030C1 – Issues for M02/M03/K03 special and major meter tests onlyMessages 331 and 332 otherwise issues instead of C1

252Message 300S issues instead of C1

260C1 – Issues as result of initial meter assessment and testsC1 will also issues in NI to provide enquiry status updatesC1 issue in RoI is restricted to revenue protection


Message 131



MPRN req 11 no no MPRN req 11 no noMPBusinessReference opt 35 no no MPBusinessReference opt 35 no noMeterWorksTypeCode req yes MeterWorksTypeCode req 3F no yes Merge work type listsRequestStatusCode req 3V no yes RequestStatusCode req 3V no yes C1, C2, R, S (NI only), XAppointmentID opt AppointmentID opt DateOfVisit opt DateOfVisit optMeterPointStatus opt 2V no yes MeterPointStatus opt 2V no yesOutcomeReasonCode opt no yes OutcomeReasonCode opt no yes OrderStatusCode req no yes OrderStatusCode req no yesObservationText opt 512 no no ObservationText opt 512 no noMissing NetworksReferenceNumberMissing MeterConfigurationCode Missing SupplierMPIDMissing RequiredDateMissing EffectiveDateMissing CommentsMissing EnquiryIDMissing NewAppointmentDate

optM RequestStatusReason

Date Date




To Be Defined To Be Defined





Message 131 – Process Differences


Status ‘S’ applies in NI onlyA supplier can arrange a new appointment through the on-line booking system using the same appointment ID. To be used where non-completion was due to customer fault (missed appointment, site not ready)

Duplicate RequestNIE will generally reject the request rather than issue 131X

NIE propose to also use 131 message for special read request 252


Agreements and Exceptions


Supplier exceptions to proposals for changes to NI processes


Data Processing – Comment Requested


Will be discussed in detail on December 1st

To align with ESB, NIE provisionally propose removal of usage factors at register level

ESB provide this data at Meter Point/Timeslot level but not Register level• Introduction at register level is not a feasible option using SAP• ESB have a working practice (005) to address issues that may arise

NIE currently provide this data at Meter Point/Timeslot and Register level• This is relevant only where multiple instance of same timeslot• Multiple instances of same timeslot are relatively rare

Note that estimated consumption will continue to be provided on message 320 at register level to help in first bill calculation

How do Suppliers use AUF and EUF at Register level in NI?What would be the impact of removal in NI?


Data Aggregation – Comments Requested


Aggregation filesESB provide analysed aggregation data on messages 591 (NQH import), 595 (QH import), 598 (non-participant generator)NIE provide this data through a secure server

• How do Suppliers use this data• What would be the impact of removal• If the data is required, should messages 591, 595 and 598 be used in NI

Messages 594 provides analysed data on distribution connected participant generators which may be sent to associated Suppliers

• Suppliers may receive such data where generator does not have MPCC • Do any Suppliers need this data through a market message in NI

Messages 596 and 597 provide copies of SU and participant GU aggregated data sent to SMO

• Message 597 (GU) available to Suppliers under similar arrangement to 594• Do Suppliers need this data to be provided through either or both of these

market messages in NINI alternative to market messages is to remain with the secure server approachDUoS group and MCC breakdown will be lost if market messaging is used

Will be discussed in detail on December 1st


Technical Workgroup

NIE intend to provide functionality wherebyA Supplier will be able to access an NIE web-site to view messages they have sent to NIE and which NIE have received

• a Supplier will be able to view only those messages that have completed processing and were successful.

A Supplier will be able to access an NIE web-site to view messages NIE have sent to them

NIE and ESB are continuing to review options to enable a Supplier with MPCC/EMMA or equivalent to send messages on behalf of another Supplier (e.g. a retailer) that does not have MPCC/EMMA or equivalent



NIAUR Offices, Belfast

16 November 2009

Retail Market Harmonisation Working Group 4

Update on Harmonisation Baseline and Change Control


An update on current proposals…

What is the Harmonisation Baseline?How will it be authorised?How will change control work?


What is the Harmonisation Baseline?

Formal record of all changes to schema and processes needed within both jurisdictions to achieve harmonisationThose elements common to both jurisdictions, or relating solely to NI, will need to be documented, authorised and baselined by early January 2010, in order to form part of the contract documentation for the Enduring SolutionThose elements relating solely to RoI can be authorised after this date, provided that such authorisation does not change any aspects of documentation relating to NIAuthorisation will initially be through the HSGOnce authorised, all documentation will need to be placed under strict change control


Contents of the Harmonisation Baseline

What is included in the Harmonisation Baseline:Message Schema spreadsheetMessage GuidesAgreed Changes documentation summarising agreed changes to Market Procedures in both jurisdictions

What contributes to the Harmonisation Baseline:HWG presentations and minutes

What will become part of the Harmonisation Baseline in due course:

Updated Market Procedures (both jurisdictions)Updated Operational Framework (NI)


Genesis of Harmonisation DocumentationMessage Schema

ESB / NIE workshop

documentation

HWG presentations /

minutesMessage Guides

Changes to Market

ProceduresNI Market

Procedures* / Operational Framework

Order of production

Part of Harmonisation Baseline; under change control

once authorised

Will become part of Harmonisation Baseline; under change control

once authorised

Contributory document

Authorised document; not

under HSG change control

* Position on RoI Market Procedures tbc


Baseline Documentation (1)

Message Schema spreadsheetsExcel files setting out content and format of all messagesHighlight any changes needed in either / both jurisdictionsReviewed and approved by HWG as part of HWG presentationsWill be held on RMDS website

Message GuidesSet out message content and structure, and message validation (which may vary by jurisdiction)Separate sets of documentation NI and RoIESB production for RoI as-is situation in handTo be passed to NIE as a basis for NI version early Dec – to be completed by christmasFurther ESB updates to reflect RoI to-be situation can be completed during early 2010


Baseline Documentation (2)

Agreed Changes to Market ProceduresSeparate documents for each jurisdiction, summarising changes which will be made to each individual market procedurePossibility of no changes, and therefore no documentation, for RoIIn NI, documentation will serve two purposes:

• An interim record of changes prior to update of Market Procedures next year (see next slide)

• An aide-memoire for Enduring Solution (ES) bidders to help understand the impact of harmonisation on their proposals

NIE will prepare this document (as part of ES project) by end DecemberDocument needs to be included in Harmonisation Baseline (and therefore authorised and change controlled) as bidders may rely on its information in preparing their proposals for ES deliveryRoI position tbc (depends on need for such a document)


Other important documentationHWG presentations

Essential summary of all harmonisation-driven changes to market processes and schema in both jurisdictionsWalked through in detail at HWG meetings, with full opportunity for Supplier input, comment and updateApproved by HWG at relevant meetingMinutes of HWG meeting form record of approval

NI Market ProceduresWill need to be fully updated to reflect impact of harmonisationEnduring Solution design process may also drive further detailedchangeWork to be completed during 2010Agreed Changes document (see previous slide) will need to be read in conjunction with existing Market Procedures in the meantime

NI Operational FrameworkDraft developed as basis for Enduring Solution project, published September 2009To be updated and authorised in parallel to Market Procedures (above)


Document Authorisation – Harmonisation Baseline

HSG is responsible for authorising the Harmonisation Baseline (Message Schema, Message Guides and Agreed Changes to Market Procedures)HSG meeting on 26 November to agree how the required authorisations will be completed:

HSG authorisation likely to be through presentation of evidence of internal review (NIE / ESB as appropriate), and clear recommendations from HWGFor NI-related material, authorisation needs to be completed in time for inclusion in NIE procurement documentation end January 2010

Message guides (and Agreed Changes documentation, if any) for ROI subject to later running process and likely to be authorised early 2010


Document Authorisation – Other Documentation

NI Market Procedures and Operational Framework:All activities to update, review and authorise these documents to be covered as part of Enduring Solution Stage 3 planning

Position on ROI market procedures tbc


Future Evolution of the Harmonisation Baseline

Baselined market

processes(Jan 2010)

Start of ES Design Phase

Start of ES Build Phase

Start of ES Test Cycle

Start of Market

TestGo Live (c.

+24 months)

ES Delivery Timeline ES Test Market

TestContract let ES Design ES Build

Timeline not to scale

B: Harmonisation Baseline agreed

A C & D F

E: Updated Harmonisation

Baseline agreed

H: ESB Schema Drop

I: ESB Schema Drop

G: All participants ready to enter

market test


Approach to Change Control

Proposals for change control procedures for the Harmonisation Baseline currently under developmentOutline proposals to be presented to HSG 26th November; detailed proposals (+ authorisation of these) to HSG 18th DecemberProposals need to be in place early January 2010 to manage the approved Harmonisation BaselineSome principles:

Change control procedure for Harmonisation Baseline likely to bebased on the existing RMDS procedureWill only be used for changes which impact on the Harmonisation Baseline – all other jurisdiction-specific changes will continue to go through existing channels (RMDS in RoI, CDA in NI)Procedure will need to involve all market participants …… including the Enduring Solution delivery project, recognising its particular scope / timescales / pace of delivery


Any Other Business



Comments on Todays Proposals

To be forwarded [email protected]@[email protected]

By Friday November 20th 2009 for Customer and MP DataBy Monday November 23rd 2009 for DP/DA usage factors and aggregation files


mailto:[email protected]

mailto:[email protected]


Next MeetingsTuesday December 1st, 11am to 3pm

At CER offices, TallaghtProposal agreement on customer and meter point characteristics dataPresentation

• Data Processing & Aggregation• Unmetered Supplies• DUoS Billing• Message 311• Market Message Infrastructure


retail market harmonisation working group 4 · 2009. 11. 16. · niaur offices, belfast 16 november...

Documents