V12.00.00 Release – FAQ’s

If you would like to submit a question in relation to the 2019 Release please click here.

 

FAQ
Q: Will Version 12 of the Schema be released earlier than 28th January with IPT starting the end of February?

A: A draft Version of the Schema has been published on Monday 10th December 2018.

Q: Are all schema and non-schema changes being delivered at the same time (April 2019)?

A: Yes, all scope for Market Release V12.00.00 is due to go live at the same time.

Q: What validation will ESBN complete on the Eircode received on a market message?

A: The Eircode will form part of the address validation on the A1 meter point site address. The Eircode will be checked to ensure it conforms to the Eircode structure of 7 uppercase alpha/numeric characters and should match what is in the ESB Network Central Market Systems otherwise it will be rejected via the MM014R. (See tables below for different scenarios). The Eircode will not be validated for accuracy of location or address just the structure of the Eircode.

Q: How should a Supplier update an Eircode on the A1 meter point site address?

A: After the initial Upload and where Suppliers wish to advise changes to the Meter Point Address Postal Code (A1 Address) they can do so via the MM013. They should contain 7 uppercase alpha/numeric characters as a string field. There should be no space character between the 3rd and 4th value.  Non conformance to this structure will result in the MM013 being rejected via MM014R using reject reason AD9

Q: How should a Supplier update an Eircode on the A2 notification address?

A: A Supplier can update the Notification Address (A2 address) via the 013 Market Message.  The Post Code field within the MM013 should conform to the Eircode structure of 7 uppercase alpha/numeric characters.  There will be no validation on the Notification Address (A2 address).

Q: How should a Supplier update an Eircode on the A3 Technical address?

A: Once MCR1140 is implemented, a Supplier can update the Technical Contact Address in (A3 address) via the 013 Market Message.  The Post Code field within the MM013 should conform to the Eircode structure of 7 uppercase alpha/numeric characters.  There will be no validation on the Technical Contact Address (A3 address).

Q: MCR1140 states that the Post code field in the A2 address and the A3 address should conform to the Eircode structure.  Will this be validated?

A: There will be no validation on the A2 or A3 addresses.  This is in line with current address validation processes.

Q: Will the Eircode be visible on the MP Extranet etc?

A: If there is an  Eircode on the Central Market Systems against a meter point site address this will be visible on the MP Extranet and on the Downloadable files

Eircodes Tables:

Table1

Table2

Table3

Q: In relation to the migration of the Eircode to each supplier, has the migration plan for the upload of these been put in place? ( Sequence/ Volumes/ Content)

A:

Approach:

ESBN will process through the MPRN as they appear on the input list of 1.5 Million Eircodes. This will mean that market participants may receive different volumes of associated market messages on any given day during the update period.

ESBN intend to perform the updates outside of working hours to avoid any potential negative impact on Central Market Systems.

Volumes:

Based on current indicative estimates, ESBN will be updating ~ 10K MPRN/day during week days and ~ 50K MPRN/day on weekends.

Duration:

Update Schedule will commence on Wed 1st May and run for a period of 12 weeks.

Schedule & Volumes:

Weekdays – Monday to Friday

  • From: 8.00 p.m. Until : 9.00 p.m.
  • Estimated Volumes: ~ 15K MPRNs/Day

Weekends – Saturday to Sunday

  • From: 6.00 a.m. Until: 7.00 a.m.
  • Estimated Volumes: ~ 50K MPRNs/Day

Content: A MM114 will be sent for each MPRN with:

  • Message header
  • MPRN Info
    • MPRN
    • Change of usage = No/False (i.e. because this 114MM refers to a change of address only)
    • MPRN address changed = Yes/True (i.e. address change completed)
    • Customer details changed = No/False (i.e. because this 114MM refers to a change of address only)
    • Message status = ‘A – Advice’
    • Supplier Id
  • MPRN address segment including Eircode/Postcode
  • Customer name segment
Q: In relation to the 114 market message, will this be specially used for the Eircode update, and when the migration of the Eircode detail is underway, would there be a possibility that the 114 could be used for another reason other than the Eircode update at that time?

A: During the initial Eircode upload activity, a specific MM114 will be sent for each MPRN updated by this process with the content specified above.

There is nothing that prevents other MM114s being issued on the same date for the same MPRN as a result of any other process (e.g. Change of Customer Details, MPRN address update etc.).

As per current market design it is possible than more than one MM114 may be issued for an MPRN on a specific day during this batch processing period.

Examples:

a) Request of MPRN address change via MM013, a MM114 will be sent with:

  • Message header
  • MPRN Info
    • MPRN
    • Change of usage = No/False (i.e. because this 114MM refers to a change of address only)
    • MPRN address changed =Yes/True (i.e. address change completed)
    • Customer details changed = No/False (i.e. because this 114MM refers to a change of address only)
    • Message status = R – Response’
    • Market message business ref. = MM013 reference
    • Supplier Id
  • MPRN address segment including Eircode/Postcode
  • Customer name segment

b) Address updated by Networks, a MM114 will be sent with:

  • Message header
  • MPRN Info
    • MPRN
    • Change of usage = No/False (i.e. because this 114MM refers to a change of address only)
    • MPRN address changed = Yes/True (i.e. address change completed)
    • Customer details changed = No/False (i.e. because this 114MM refers to a change of address only)
    • Message status = A – Advice’
    • Supplier Id
  • MPRN address segment including Eircode/Postcode when provided
  • Customer name segment
Q: Are there any specific updates we need to take into consideration in relation to the market message implementation guide?

A: No. ESBN confirm there are no specific updates to be taken into consideration here.

Q: Can market participants submit changes to Eircodes in batch to the CMS?

A: No. Similar to the direction provided in MCR1187 for the provision of Eircodes for the A2 Address, there should be no Mass Updates of ANY address on the 013 market message as this will cause problems for the Central Market Systems and could potentially have a serious effect on its performance. 

Q: Can Eircodes be provided by market participants on the 010MM immediately from go-live of the v12 Retail Market Release?

A: No:

  • Market Participants should check the Postcode value on the RMP Extranet for the MPRN in question, and if populated include this in the 010MM.
  • However, where no Eircode is present on the RMP Extranet for an MPRN – ESBN advise market participants not to populate this field on the 010MM until after the ESBN ~ 12 week batch Eircode upload process has completed.
  • This is a temporary measure, applicable only during this batch upload period, to avoid increased volumes of outsorted 010MMs caused by potential mismatch between the Postcode value on inbound 010MM versus the Central Market System.
  • Post completion of ESBNs batch Eircode upload process, the Postcode field can be populated by market participants on the 010MM as required.
Q: Can Eircodes be provided by market participants on the 013MM immediately from go-live of the v12 Retail Market Release?

A: No:

  • ESBN advise market participants not to populate the Post Code field on the 013MM market message until after the ESBN ~ 12 week batch Eircode upload process has completed.
  • This is a temporary measure, applicable only during this batch upload period
  • Post completion of ESBNs batch Eircode upload process, the Postcode field can be populated by market participants on the 013MM as required.