new market message implementation guide · 2019. 3. 20. · market message implementation guide...

Market Message Implementation Guide

v003.00.003

15th January 2019

Market Message Implementation Guide v003.00.003

2

Contents

Contents ........................................................................................................ 2

Revision History ............................................................................................ 5

History of Changes ....................................................................................... 6

1. Introduction ............................................................................................. 8

1.1 Purpose of the Market Message Implementation Guide ........................................... 8 1.2 Scope ........................................................................................................................ 8 1.3 Related Documentation ............................................................................................. 9 1.4 Validation ................................................................................................................... 9 1.5 Note ......................................................................................................................... 10

2. Common Data Segments ..................................................................... 11

2.1 Message Header Segment ..................................................................................... 12 2.2 Shipper Header Segment ........................................................................................ 14 2.3 BG Transporter Header Segment ........................................................................... 17 2.4 Gas Point Address Segment ................................................................................... 20 2.5 End User Details Segment ...................................................................................... 22 2.6 Meter Read Segment .............................................................................................. 35 2.7 Gas Point Status Segment ...................................................................................... 42 2.8 Meter Segment ........................................................................................................ 44 2.9 Read Cycle .............................................................................................................. 47

3. GPRO Market Messages ...................................................................... 49

3.1 G101RQ – Update Existing End User Details Request .......................................... 51 3.2 G102RJ – Update Existing End User Details Rejection.......................................... 52 3.3 G103N – Update Existing End User Details Completion Notification ..................... 54 3.4 G201RQ – Change of Shipper NDM Request ........................................................ 55 3.5 G202RJ – Change of Shipper Rejection ................................................................. 57 3.6 G203N – Change of Shipper Receipt Notification (Incoming Shipper) ................... 60 3.7 G204N – Change of Shipper Receipt Notification (Outgoing Shipper) ................... 62 3.8 G205N – Change of Shipper Completion Notification (Incoming Shipper) ............. 63 3.9 G206N – Change of Shipper Completion Notification (Outgoing Shipper) ............. 65 3.10 G207N – Change of Shipper Rejection Notification (Outgoing Shipper) ................ 66


3

3.11 G208RQ– Change of Shipper Cancellation NDM Request .................................... 69 3.12 G209RJ – Change of Shipper Cancellation Rejection ............................................ 71 3.13 G210N –CoS Cancellation Notification (Incoming Shipper) ................................... 73 3.14 G211N – CoS Cancellation Notification (Outgoing Shipper) ................................... 74 3.15 G301RQ –Historical Consumption NDM Request .................................................. 75 3.16 G302RJ – Historical Consumption Rejection .......................................................... 77 3.17 G303N – Historical Consumption Completion Notification ..................................... 79 3.18 G401RQ – End User Assignment Request ............................................................. 82 3.19 G402RJ – End User Assignment Rejection ............................................................ 85 3.20 G403N – End User Assignment Provisional Acceptance Notification ..................... 89 3.21 G404N – End User Assignment Completion Notification ........................................ 91 3.22 G601RQ – Registration NDM Request ................................................................... 93 3.23 G602RJ – Registration Rejection ............................................................................ 99 3.24 G603N- Registration Provisional Acceptance ....................................................... 102 3.25 G604N- Registration Completion Notification ....................................................... 104 3.26 G605RQ – Registration Cancellation Request ..................................................... 107 3.27 G606RJ – Registration Cancellation Rejection ..................................................... 109 3.28 G607N - Registration Cancellation Completion Notification .................................. 111 3.29 G701N – Deregistration Tariff Exemption Notification ........................................... 112 3.30 G702N – Deregistration Tariff Exemption Removal Notification ........................... 113 3.31 G703N – Deregistration Completion Notification .................................................. 114 3.32 G2401N – Revenue Protection Case Notification ................................................. 115

4. NDM Market Messages ....................................................................... 118

4.1 M801RQ – Meter Read Request – NDM .............................................................. 119 4.2 M802RJ – Meter Read Rejection .......................................................................... 123 4.3 M803N – Meter Read Completion Notification – (Single Read) ........................... 126 4.4 M804N – Meter Read Completion Notification – (Double Read) .......................... 127 4.5 M901RQ – Meter Read Query Request ................................................................ 128 4.6 M902RJ – Meter Read Query Rejection ............................................................... 131 4.7 M903N – Meter Read Query Completion Notification ........................................... 133 4.8 M1101RQ – Estimated Read Request .................................................................. 134 4.9 M1102RJ – Estimated Read Rejection ................................................................. 136 4.10 M1103N – Estimated Read Completion Notification ............................................. 138 4.11 M1401N – Meter Update Notification .................................................................... 139

5. Site Works Market Messages ............................................................ 141


4

5.1 S1501N - Site Works Appointment Re-Scheduling Notification ............................ 142 5.2 S1502RQ – Site Works Appointment Re-Scheduling Request ............................. 144 5.3 S1503RJ – Site Works Re-Scheduling Request Rejection ................................... 147 5.4 S1504A- Site Works Re-Scheduling Request Acceptance ................................... 149 5.5 S1601RQ - Site Works Request ........................................................................... 151 5.6 S1602RJ – Site Works Rejection .......................................................................... 156 5.7 S1603A- Site Works Acceptance .......................................................................... 158 5.8 S1604N- Site Works Completion Notification ....................................................... 160 5.9 S1701RQ – Site Works Cancellation Request ...................................................... 164 5.10 S1702RJ – Site Works Cancellation Request Rejection....................................... 166 5.11 S1703A- Site Works Cancellation Acceptance ..................................................... 168 5.12 S1901RQ - Site Works Complaint Request .......................................................... 170 5.13 S1902RJ - Site Works Complaint Rejection ......................................................... 174 5.14 S1903A- Site Works Complaint Acceptance ......................................................... 177 5.15 S1904N- Site Works Complaint Acceptance Notification ...................................... 180 5.16 S1905N- Site Works Complaint Completion Notification ...................................... 183 5.17 S2301RQ –Gas Point Address Update Request .................................................. 186 5.18 S2302RJ –Gas Point Address Update Rejection .................................................. 189 5.19 S2303N- Gas Point Address Update Notification.................................................. 191

6. Miscellaneous ..................................................................................... 192

6.1 H3001N - End of Day Totals Notification ............................................................... 193


5

Revision History

Version Date Author Description

1.0 01/02/2007 Draft for Approval

1.1 31/05/2007 Cathal McCarthy Draft for Approval v1.1

2.0 27/07/2007 Cathal McCarthy Baselined v2.0.1

002.00.002 26/11/2007 Cathal McCarthy Baselined v002.00.002

002.00.003 07/03/2008 Cathal McCarthy Baselined v002.00.003 in tandem with schema release. Clarification notes also included in G601RQ and S1601RQ.

002.00.004 03/07/2008 Cathal McCarthy Baselined v002.00.004 in tandem with schema release. Changes made following approval of CR017 and CR018

002.01.000 16/09/2008 Cathal McCarthy Baselining for go-live

3.0 17/11/2008 Cathal McCarthy Baselining for go-live. Link between version number for this document and XML schema version number has been broken. MMIG v3.0 is to be used in conjuction with schema version 002.00.004 and these releases will be used for go-live.

3.01-3.03 20/10/2009 Donal O Caoimh Include changes to schema expected February 2010.

3.04 26/03/2010 Donal O Caoimh Minor changes to bands, read type names, end user detail field lengths

3.05 01/10/2011 Rickard Lucey Reviewed and tidied up previous version and reissued as version 3.05.

003.00.001 09/09/2014 Rickard Lucey Aligned version number of document with market message schema version number.Changed the length of the “swRef” attribute from 7 to 12 in all market messages that include it.

003.00.002 09/12/2014 Fergus Lester

Ronnie Gallagher

Rickard Lucey

Updated with respect to change requests being included in the summer 2015 GasMap release

003.00.003 15/01/2019 Con O’Donnell

Barry Gould

Ronnie Gallagher

Diarmaid McAuliffe

Updated with respect to change requests being included in the January 2019 GasMap release

S1601RQ - New Lock Type “SX” Shipper Lock (No Contract)

New Message G2401N – Revenue Protection Notiifcation Message

M1401N – Meter Update Notification (previously Read Cycle Update Notification)


6

History of Changes

Changes Description of Change

CR003 House/Unit Number extended from 3 integers to 4

CR004 MPD5 – Change of Shipper Correction Amendment converted into a manual process. Associated market messages have been removed.

CR005 Numerous updates to validations as discrepancies were discovered during test script preparation.

CR006 Format of Timestamp in market messages changed to XML standard format.

CR007 Renaming of ‘Meter Point Status’ to ‘Gas Point Status’.

CR008 Removal of ‘Meter Sequence Number’ field from market messages

CR009 150 Euros Charge for Non-registered Installer (provisional)

CR010 Prepayment Meters

CR011 Corrections to MMIG 2

CR016 Corrections to MMIG and schema

CR017 Read Type Update

CR018 Dials and Digits

CR021 Baselined for go-live and changes made in line with Change Request 021

CR026 Deregistration changes

CR031 Field length changes

CR033 Energisation status


7

CR037 New Smart Meter Codes

CR038 Change of shipper

CR070 Extend the length of the “swRef” attribute from 7 to 12 in all messages that include it.

CR043 Increase length of Siteworks information attribute from 50 to 250 characters

CR047 Add Meter Size to Market Messages

CR064 Identify Priority Customers

CR046 Request Street Disconnect on S1601 RQ Message

CR060 Siteworks Closure Codes

CR063 Provision of Gas Meter Read Calendar

CR076 New Site Works Reason Code

CR077 Meter Characteristic Change Message

CR078 Revenue Protection Case Notification Message


8

1. Introduction

1.1 Purpose of the Market Message Implementation Guide

The purpose of the Market Message Implementation Guide is to assist Shippers in the following areas:

- The construction of market messages to be sent to the Transporter

- The interpretation of messages received from the Transporter.

This document lists all the validations rules for market messages and supersedes the ‘Validation Rules’ listed in the individual Market Process Definitions (MPDs).

1.2 Scope

This document combines all the data fields that are contained in market messages as outlined in the Gas MaP Market Process Definition documentation. The various attributes of each field in the Market Messages are presented below – segment name, field name, length, whether mandatory, optional or dependant, the type of input expected (i.e. integer, character, decimal etc.), an explanation of what the field is and guiding principles on composition or interpretation of the market message data fields, and the validation it is subject to.


9

1.3 Related Documentation

Market Message Implementation Guide is a consolidated final version of the Market Message Catalogue, Business Data Definitions, Market Message Definitions and Data Codes documents as illustrated below;

The Market Message Implementation Guide outlines the main requirements for the XML-Schema, therefore it is going to be the main source for development efforts for the relevant technical solutions. Changes on this document will be managed via Market Change Control Process once this document is approved by the CER.

1.4 Validation

Two levels of validation will be performed – Gas Shippers Communication Component (GSCC) Syntax Validation and Business Logic Validation.

1.4.1 GSCC Syntax Validation

The Gas Shippers Communication Component (GSCC) will perform the first level of validation. This level of validation will check syntax only. It will check that some input has been made in all mandatory fields and that inputs match the expected formats for all data fields (e .g. Integer fields should only contain numeric values, date fields should be in the specified date format etc).


10

1.4.2 Business Logic Validation

The second level of validation will be performed when a market message reaches the GNI Systems. Market Messages will be checked for validity against existing information and business logic rules on the GNI Systems.

1.5 Note

The following terms used in the tables.

Structure: outlines segment and data field level details of the market message including the datafield abbreviation used in the XML Schema.

Optional (Opt): whether the field is (M)andatory, (O)ptional or (D)ependent on the content of another field.

Length (Ln): the number of characters expected or the maximum number of character accepted.

Type (Typ): the type of input expected/accepted e.g. integers, characters, decimals, date or an item chosen from a predefined list of codes.

Composition Instructions: The purpose and composition instructions for the data field. What the field refers to and how it should be composed.

Validation: The validation that data in the field will be subject to.


11

2. Common Data Segments

This section outlines the market message segments that have common contents, rules for composition and validations across all the messages in which they appear in the Gas MaP Market Messaging solution.

Common Data Segments are:

- Message Header

- Shipper Header

- BG Transporter Header

- Gas Point Address

- End User Details

- Meter Read

- Gas Point Status

- Meter Details

- Read Cycle


12

2.1 Message Header Segment

2.1.1 Description

This segment provides message header details that allow the market message information to be interpreted by a receiving Market Participant. The Message Header segment is mandatory on all market messages in the Gas MaP Market Messaging Solution.

2.1.2 Segment Structure and Validation

This section outlines the rules for composition and validation of the market message segment. All data fields in the market message must be populated to defined formats and lengths aligned with the “Opt – Optional” attribute that is defined at data field level.

Structure Opt Ln Typ Composition Instructions

Message Header M Segment All items in the message header must be populated to defined formats and lengths.

Market Message Type Code [mmTypeCode]

M 10 Char This defines the type of message to be sent by the Market Participant. Every Market Message that is sent and received will have a unique identifier (e.g. M803N, G101RQ etc.). This message type must match one of the currently supported values for this item. Where it does not the message will fail validation

Market Message Operational Flag [mmOperationalFlag]

M 1 List This field determines whether the message is ‘operational’ or not (i.e. whether the message is intended to update a live, operational system or whether it is intended as a test message. As a default, messages will be ‘operational and will only be otherwise during testing. Must be one of the following available codes:

Code Description

Y Yes (i.e this message is operational)

N No (i.e. this message is not operational and is intended as a test only)

Market Message Version [mmVersion]

M 10 Char The version number of the market message. This, in tandem with the ‘Message Type’ above, uniquely identifies each market message. Only current supported versions of the message will be allowed. Where it does not match the currently supported version the message will fail validation The version number is intended to be in the Format 000.00.000

The first three digits will indicate major version releases of the messages starting with Market Go live release (e.g. Set to 001.00.000 at go live)

The second two digits will be used to indicate minor version releases due to revision to messages that will alter the structure of existing messages and require validation with a new schema

The last three digits will indicate intermediate version releases used for correction of minor releases.

Market Message TimeStamp [mmTimestamp]

M 20 Time This is a time and date stamp. This is defined with the GMT offset in the following format (this is the XML standard format): CCYY-MM-DDThh:mm:ss

This must match the defined format. Where it does not match this format the message will fail validation


13

Structure Opt Ln Typ Composition Instructions

Market Message Sender ID [mmSenderID]

M 2 Char This is the unique identifier of the Market Participant Sending the message. A unique identifier will exist for all parties interacting with the GNI systems via market messages. The identifier of the party originating a message will be stamped on every market message being sent to and from the GNI systems. This must be a valid sender’s reference. Where it is not the message will fail validation.

Market Message Recipient ID [mmRecepientID]

M 2 Char This is the unique identifier of the Market Participant receiving the message. A unique identifier will exist for all parties interacting with the GNI systems via market messages. The identifier of the intended recipient will be stamped on every market message being sent to and from the GNI system. This must be a valid recipient‘s reference. Where it is not the message will fail validation.

Market Message Reference [mmRef]

M 20 Char Unique serial number for the market message. This will be a system generated number which can be used for auditing or tracing purposes (created by Shipper’s back end system or GSCC for Shipper initiated messages and by GNI Systems for Transporter Initiated messages messages). This item must match the defined format and length. Where it does not the message will fail validation.


14

2.2 Shipper Header Segment

2.2.1 Description

This segment provides Shipper Reference details for the gas point to which the Shipper’s request is related. The Shipper Reference Segment is sent by the registered Shippers to the Transporter as part of the following market messages:

Market Message Code Market Message Name Sender Receiver

G101RQ Update End User Details Request Shipper Transporter

G201RQ Change of Shipper NDM Request Shipper Transporter

G208RQ Cancellation of Change of Shipper NDM Request Shipper Transporter

G301RQ Historical Consumption Request Shipper Transporter

G401RQ End User Assignment Request Shipper Transporter

G601RQ Registration Request Shipper Transporter

G605RQ Registration Cancellation Request Shipper Transporter

M801RQ Shipper Entered Meter Read Entry – NDM Generic / Volume Corrected Shipper Transporter

M901RQ Meter Read Query Shipper Transporter

M1101RQ Estimate Read Request Shipper Transporter

S1502RQ Site Works Appointment Rescheduling Request Shipper Transporter

S1601RQ Site Works Creation Request Shipper Transporter

S1701RQ Site Works Cancellation Request Shipper Transporter

S1901RQ Site Works Complaint Request Shipper Transporter

S2301RQ Update Request for Maintenance of Gas Point Address Shipper Transporter




15

Structure Opt Ln Typ Composition Instructions Validation

Shipper Header M Segment All data items in the Shipper Reference Segment must be populated to defined formats and lengths.

Shipper Reference [shipperRef]

O 20 Char The Shipper may put their own reference number on market messages that they generate and send to the GNI systems. This can be used for the Shipper’s own reference purposes. When responding to a market message sent by a Shipper (rejection or notification messages), the Shipper’s original reference number (if provided when first message is sent by Shipper) will be quoted in the ‘Shipper Reference No’ field in the GNI Reference Segment.

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:

That the format is correct – that is not longer than 20 characters.

This field will not be validated by GNI Systems. Shippers may populate this field with their own reference number if they wish but the Transporter will not have any means of validating it.

Gas Point ID [gaspointID]

M 7 Integer A unique seven digit reference number used to identify a Gas Meter connection to the Gas Network. One, and only one, GPRN(Gas Point ID) must be specified in each market message.

Gas Shipper Communication Component will validate the data in this field to ensure:

That a value has been provided. That only numeric values have been

provided. That the format is correct – that is not

longer than 7 integers.

The following validation will always be applied to this data field by GNI Systems:

GPRN must exist on GNI Systems. [GDNE]

GPRN must be that of an NDM site. [NNDG]

There are additional message-specific validations that will be carried out for certain market messages and details of these can be found in the individual ‘Validation’ sections for those messages.

Shipper ID [shipperID] M 2 Char The Shipper’s unique identifier must be entered on market messages that the Shipper generates and sends to the GNI systems.


That a value has been provided. That the format is correct – that is not

longer than 2 characters. The following validation will be applied to this data field, in conjunction with the ‘Supplier ID’ field below, by GNI Systems to ensure that:

A valid Shipper/Supplier ID combination has been provided. [ISSC]

Supplier ID [supplierID] M 3 Char The Shipper’s unique identifier for the Supplier must be entered on market messages that the Shipper generates and sends to the GNI systems.



longer than 3 characters.


16


The following validation will be applied to this data field, in conjunction with the ‘Shipper ID’ field above by GNI Systems to ensure that:

A valid Shipper/Supplier ID combination has been provided. [ISSC]


17

2.3 BG Transporter Header Segment

2.3.1 Description

This segment provides Bord Gais Transporter Reference details for the gas point to which the market message relates. The GNI Reference Segment is sent by the Transporter to the registered Shippers as part of the following market messages:


G102RJ Rejection Message for Update End User Details Request Transporter Shipper

G103N Notification Message for Update End User Details Transporter Shipper

G202RJ Rejection message for Change of Shipper NDM Request Transporter Shipper

G203N CoS Request Receipt Notification Transporter Shipper

G204N CoS Request Receipt Notification Transporter Shipper

G205N CoS Request Completion Notification Transporter Shipper


G207N CoS Request Rejection Notification Transporter Shipper

G209RJ Cancellation of CoS Request Rejection Transporter Shipper

G210N Notification Message to Incoming Shipper for Cancellation of Change of Shipper NDM Request

Transporter Shipper

G211N Notification Message to Outgoing Shipper for Cancellation of Change of Shipper NDM Request

Transporter Shipper

G302RJ Rejection Message for Historical Consumption Transporter Shipper

G303N Historical Consumption Data Transporter Shipper

G402RJ End User Assignment Rejection Message Transporter Shipper

G403N End User Assignment Request

Provisional Acceptance

Transporter Shipper

G404N End User Assignment Completion Notification Transporter Shipper

G602RJ Registration Request Rejection Message Transporter Shipper

G603N Registration Request Provisional Acceptance Transporter Shipper

G604N Registration Completion Notification Transporter Shipper

G606RJ Cancellation of Registration Request Rejection Message Transporter Shipper

G607N Cancellation of Registration Request Acceptance

Notification

Transporter Shipper

G701N Deregistration Tariff Exemption Notification Transporter Shipper


18


G702N Deregistration Tariff Exemption Removal Notification Transporter Shipper

G703N Deregistration Completion Notification Transporter Shipper

G2401N Revenue Protection Case Notification Transporter Shipper

M802RJ Meter Read Rejection Transporter Shipper

M803N Meter Read Information Notification – NDM – Generic/Volume Corrected (Single Read Segment)

Transporter Shipper

M804N Meter Read Information Notification – NDM – Generic/Volume Corrected (Double Read Segment)

Transporter Shipper

M902RJ Meter Read Query Rejection Transporter Shipper

M903N Meter Read Query Resolution Notification Transporter Shipper

M1102RJ Estimate Read Request Rejection Transporter Shipper

M1103N Estimate Read Request Notification Transporter Shipper

M1401N Meter Update Notification Transporter Shipper

S1501N Site Works Appointment Re-Scheduling Notification Transporter Shipper

S1503RJ Site Works Re-Scheduling Request Rejection Transporter Shipper

S1602RJ Site Works Rejection Transporter Shipper

S1603A Site Works Request Acceptance Transporter Shipper

S1604N Site Works Completion Transporter Shipper

S1702RJ Site Works Cancellation Request Rejection Transporter Shipper

S1703A Site Works Cancellation Request Acceptance Transporter Shipper

S1902RJ Site Works Complaint Request Rejection Transporter Shipper

S1903A Site Works Complaint Request Acceptance Transporter Shipper

S1904N Receipt Notification for End User Complaint Relating to Shipper Initiated Site Works Request

Transporter Shipper

S1905N Resolution Notification for End User Complaint Relating to Shipper Initiated Site Works Request

Transporter Shipper

S2302RJ Rejection for Update Request for Maintenance of Gas Point Address Transporter Shipper

S2303N Notification for Maintenance of Gas Point Address Update Transporter Shipper

H3001N End of Day Totals Notification Transporter Shipper


19




BG Transporter Header M Segment All data items in the GNI Reference Segment must be populated to defined formats and lengths.

Transporter Reference [transporterRef]

O 10 Char A GNI Systems reference number is a unique identifier for a transaction, which will be integrated into all market messages sent by the Transporter when responding to market messages sent by Shippers, as part of the GNI Reference Segment.

GNI Systems will validate the information before sending the market message to the Shipper.

Shipper Reference [shipperRef]

D 20 Char The Shipper may put their own reference number on market messages that they generate and send to the GNI systems. This can be used for the Shipper’s own reference purposes. When responding to a market message sent by a Shipper (rejection or notification messages), the Shipper’s original reference number (if provided when first message is sent by Shipper) will be quoted in the ‘Shipper Reference no’ field in the GNI Reference Segment.


Gas Point ID [gaspointID]

M 7 Integer A unique seven digit reference number used to identify a Gas Meter connection to the Gas Network. One GPRN – Gas Point ID - (and one GPRN only) must be specified in each market message. In most cases, the GPRN quoted in this segment will be the same one provided by the Shipper when initiating the communication by market message (this GNI Reference segment is primarily used in replies to the market message originally sent by the Shipper).


Shipper ID [shipperID] M 2 Char Unique identifier for the Shipper. The Supplier ID quoted in this field will be the same one provided by the Shipper when initiating the communication by market message (this GNI Reference segment is primarily used in replies to the market message originally sent by the Shipper).


Supplier ID [supplierID] M 3 Char Unique identifier for the Supplier. The Supplier ID quoted in this field will be the same one provided by the Shipper when initiating the communication by market message (this GNI Reference segment is primarily used in replies to the market message originally sent by the Shipper)



20

2.4 Gas Point Address Segment

2.4.1 Description

This segment provides details of Gas Point Addresses. The Gas Point Address Segment is incorporated into the following market messages sent between the Transporter and Registered Shippers:


G205N Change of Shipper Request Completion Notification Transporter Shipper


G603N Registration Request Provisional Acceptance Transporter Shipper



S1504A Site Works Re-Scheduling Request Acceptance Transporter Shipper

S1603A Site Works Request Acceptance Transporter Shipper

S1703A Site Works Cancellation Request Acceptance Transporter Shipper

S1903A Site Works Complaint Request Acceptance Transporter Shipper

S2303N Notification for Maintenance of Gas Point Address Update Transporter Shipper




Gas Point Address M Segment All data items in the Gas Point Address Segment must be populated to defined formats and lengths.

Gas Point House/Unit No [gpHouseNo]

M 4 Integer Number of house or unit, if applicable, where Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point House Letter [gpHouseLetter]

M 1 Char Letter of house, if applicable, where Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.


21


Gas Point House Name [gpHouseName]

M 75 Char Name of house or unit, if applicable, where Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point Street Name [gpStreetName]

M 75 Char Name of street where a Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point Area Name [gpAreaName]

M 75 Char The area of a city/county in which a Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point Town Name [gpTownName]

M 75 Char The town in which a Gas Point is located GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point County Name [gpCountyName]

M 75 Char The county in which a Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.

Gas Point Post Code [gpPostCode]

O 10 Char The post code in which a Gas Point is located. GNI Systems will validate the information before sending the market message to the Shipper.


22

2.5 End User Details Segment

2.5.1 Description

This segment provides Details of the End User to whom a market message relates. The End User Details Segment is incorporated into the following market messages sent between the Transporter and Registered Shippers:


G101RQ Update End User Details Request Shipper Transporter

G103N Notification Message for Update End User Details Transporter Shipper



G403N End User Assignment Request Provisional Acceptance Transporter Shipper


G601RQ Registration Request Shipper Transporter





End User Details M Segment All data items in the End User Details Segment must be populated to defined formats and lengths.

End User Title [euTitle] O 4 List The title by which the End User is known. Must be one of the following available codes:

Code Description

Miss Miss

Mr Mister


That the format is correct – that it is one of the available codes.


23


Mrs Missus

Ms Miss

Dr Doctor

Arch Archbishop

Br Brother

Capt Captain

Cdt Commandant

Cllr Councillor

Col Colonel

Fr Father

Gen General

Maj Major

Rev Reverend

Sr Sister

End User Type Code [euTypeCode]

M 1 List Code indicating whether the End User is ‘Domestic’ or ‘Company’. This has a direct bearing on the details that must be provided for the End User. For ‘Domestic’ End Users, the End User First Name and End User Surname fields must be populated. For ‘Company’ End Users, only the Company Name field has to be populated. Must be one of the following available codes:

Code Description

D Domestic

C Company


That a value has been provided. That the format is correct – that it is one of

the available codes.

End User First name [euFirstName]

D 50 Char First name of End User. This field is dependent on the ‘End User Type Code’ field above. If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then a value must be provided in this field. If ‘Company’ is


That a value has been provided.


24


chosen in the ‘End User TypeCode’ field, then no value should be provided in this field.

That the format is correct – not greater than 50 characters.

The following validation will be applied to this data field by GNI Systems:

If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then a value must be provided. [DEUF]

If ‘Company’ is chosen in the ‘End User Type Code’ field, then no value should be provided. [CEUF]

End User Surname [euSurname]

D 50 Char Surname of End User. This field is dependent on the ‘End User Type Code’ field above. If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then a value must be provided in this field. If ‘Company’ is chosen in the ‘End User Type Code’ field, then no value should be provided in this field.


That a value has been provided. That the format is correct – not greater

than 50 characters. The following validation will be applied to this data field by GNI Systems:

If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then a value must be provided. [DEUS]

If ‘Company’ is chosen in the ‘End User Type Code’ field, then no value should be provided. [CEUS]

End User Company Name [euCompanyName]

D 50 Char Name of company registered as an End User, if applicable. This field is dependent on the ‘End User Type Code’ field above. If ‘Company’ is chosen in the ‘End User Type Code’ field, then a value must be provided in this field. If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then no value should be provided in this field.




If ‘Company’ is chosen in the ‘End User Type Code’ field, then a value must be provided. [CEUC]

If ‘Domestic’ is chosen in the ‘End User Type Code’ field, then no value should be provided. [CEUD]

End User Company Trading Name [euCompanyTradingName]

O 35 Char Alternate trading name for above company, if applicable. If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:


End User Market Sector Code

M 2 List The sector of the market that an End User belongs to.



25


[euMarketSectorCode] Must be one of the following available codes:

Code Description

RD Residential

IC Industrial/Commercial



End User Business Type Code [euBusinessTypeCode]

D 4 List The type of business that the End User is involved in. This field is dependent on the ‘End User Market Sector’ field above. If the ‘End User Market Sector Code’ is ‘Industrial/Commercial’ then a value for Business Type must be provided in this field. Must be one of the following available codes:

Code Description

PRPR Primary Producer

AGRC Agriculture

MRGA Market Gardening

PAPO Pig and Poultry

INDL Industrial

FDTO Food,Drink,Tobacco

MEAT Meat

DAIR Dairy

BREW Brewing

OFPR Other Food Processing

CATR Caterers

BACK Baking/Confectioneers

LGIN Large Industry (H/P int.)




If ‘Industrial/Commercial’ is chosen in the ‘End User Market Sector Code’ field, then a value must be provided. [BMPM]

If ‘Residential’ is chosen in the ‘End User Market Sector Code’ field, then no value should be provided. [NBTR]


26


CONC Concrete and Cement

GLCR Glass and Ceramic

METC Metals and Chemicals

PHAR Pharmaceutical

PAPP Paper and Printing

SMIN Small Industry (semi-com)

TEXT Textile

COMP Computer/IT

WDLE Wood and Leather

ELEC Electrical & Instruments

RTLC Retail Commercial

RTLP Retail Parks (s/c l’lord)

LGMU Large (Multi,D/S,W/H,W/S)

WHSL Wholesalers

CHRS Chain Retail Stores

DPTS Department Stores

WHOU Warehouse Outlets

RTOU Retail Outlets

SMLS Small (Local Shops)

MOTT Motor Traders

PHMC Pharmacies

SVCO Services Commercial


27


FINS Financial Services

BANK Banking

INSP Insurance & Pensions

CRUN Credit Unions

BUSC Building Society

BRKC Brokers & Consultants

CONS Construction Industry

BDEV Builders & Developers

ARCH Architects & Engineers

ESAG Estate Agents

PROB Professional/Business

VETS Vets

LEGL Legal

ACCT Accountants

SOLC Solicitors

AUCT Auctioneers

FDAC Food,Drink & Accomodation

HOTL Hotels

OTAC Other Accomodation

REST Restaurants

PUBR Pub/Restaurants

PUBS Pubs


28


TKAW Take-Aways

UTIL Utilities

FLPW Fuel and Power

WATR Water and Waste Water

TELC Telecommunications

ARRS Air,Road,Rail,Shipping

LOSV Local Services

LAUN Laundrettes

CLNR Cleaners

HAIR Hair & Beauty Parlours

MOMC Motor Mechanics no retail

TATO Travel Agents/Tour Oper,.

SPLS Sports and Leisure

SPOR Sports Clubs

PLFA Private Leisure Facility

PMFA Public/Municipal Facility

COMM Community Centres

ENTM Entertainment

PUBV Public/Voluntary

HETH Healthcare

HOSP Hospitals

NURS Nursing Homes


29


MEDC Medical Consultants (MDs)

EDUC Education

SCHL Schools

TLCO 3rd Level Colleges

GOVN Government

LOCA Local Authority

NGCR NGO’s,Charities/Religious

CHUC Churches

RESD Residences

BTUK Business Type Unknown

End User Contact Number Flag [euContactNumberFlag]

M 1 List Checkbox indicating whether a contact number is available for this End User or not. If set to ‘Y’, it is mandatory to supply at least one full pair of numbers (number and prefix) in the fields below. Must be one of the following available codes:

Code Description

Y Yes

N No





If ‘Yes’ is supplied in this field, at least one complete set of contact numbers must be provided over the following 9 fields. A complete set is to be taken as a prefix and phone number for one category (e.g. mobile number and prefix or home number and prefix). [ALOS]

End User Home Phone Number Prefix [euHomePhonePrefix]

D 4 Char Prefix for the End User’s home phone number – e.g. 021. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.




30


End User Home Phone Number [euHomePhoneNo]

D 11 Char End User’s home phone number, excluding the prefix. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Mobile Phone Prefix [euMobilePhonePrefix]

D 4 Char Prefix for the End User’s mobile phone number – e.g. 087. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Mobile Phone Number [euMobilePhoneNo]

D 11 Char End User’s mobile phone number, excluding the prefix. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Work Phone Number Prefix [euWorkPhonePrefix]

D 4 Char Prefix for the End User’s work phone number – e.g. 021. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Work Phone Number [euWorkPhoneNo]

D 11 Char End User’s work phone number, excluding the prefix. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Work Phone Extension Number [euWorkPhoneExtn]

D 4 Integer Extension number for End User’s work phone number, if applicable. This field will not be required to form a complete set of contact numbers. Although a value may be provided in this field, the ‘End User Work Phone Number Prefix’ and ‘End User Work Phone Number’ fields alone will constitute a complete set of contact numbers.


That the field contains numeric values only

That the format is correct – not greater than 4 integers.

End User Fax Number Prefix [euFaxPhonePrefix]

D 4 Char Prefix for the End User’s fax number – e.g. 021. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field,


That the format is correct – not greater


31


then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.

than 4 characters.

End User Fax Number [euFaxPhoneNo]

D 11 Char End User’s fax number, excluding the prefix. This field is dependent on the ‘End User Contact Number Flag’ field above. If ‘Y’ is chosen in the ‘End User Contact Number Flag’ field, then it will be necessary to provide a complete set of contact numbers in at least one category of numbers. If ‘N’ is chosen in the ‘End User Contact Number Flag’ field, then no value should be entered.



End User Email Address [euEmailAddress]

O 50 Char The email address for the End User. If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:


End User Contact Name [euContactName]

O 25 Char Name of person to contact in relation to request/notification etc. If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:


End User Contact Address (Line 1) [euContactAddress1]

O 25 Char Line 1 of the contact address for an End User. If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:















32


End User Contact Method Code [euContactMethodCode]

O 2 List Indicates the best method for contacting the customer. Must be one of the following available codes:

Code Description

DM Direct Mail

MC Mini Comm

EM E-mail

HP Home phone

MO Mobile phone

WP Work Phone



End User Vulnerable Flag [euVulnerableFlag]

M 1 List Indicates whether the customer is considered ‘vulnerable’. Must be one of the following available codes:

Code Description

Y Yes

N No

Note: If the GPR states that an End User is vulnerable and a Shipper enters ‘N’ in this field, the Shipper will be warned of the previous vulnerability (see G103N – Notification Message for Update End User Details). This is to warn the Shipper of a mistake that they may have made in indicating that the End User is no longer vulnerable. This is also used in MPD2 – Change of Shipper & Cancellation of a CoS for NDM to notify the incoming Shipper that the End User was treated as vulnerable previously. The Shipper then has the opportunity to establish the nature of the vulnerability and submit an Update End User Details Request so that the vulnerable status of the End User is correct.





That the value provided matches the vulnerable customer status held on the Gas Point Register. [No data code has been defined for this validation. Instead, a predefined text will be sent: ‘Record of vulnerability at GPRN. Please verify’]

Use Alternate Contact Address Flag [euAltAddrFlag]

D 1 List Indicates whether the customer that was indicated as vulnerable above should be contacted via Contact Details. This field is dependent on End User Vulnerable Customer Flag. If ‘End User Vulnerable Customer Flag’ is set to ‘N’, then no value will be required for this field.


That the format is correct – that it is one of


33


Must be one of the following available codes:

Code Description

Y Yes

N No

the available codes. The following validation will be applied to this data field by GNI Systems:

If ‘Y’ is chosen, then the ‘End User Vulnerable Customer Flag’ should have a value of ‘Y’. [UAVC]

If ‘Y’ is chosen and the ‘End User Vulnerable Customer Flag’ is set to ‘Y’, then a value should be provided in one of the Contact Address lines. [CDVC]

[euPriorityFlag] M 1 Char This attribute is used to indicate whether the customer is considered a priority end user. Must be one of the following available codes:

Code Description

Y Yes

N No


That a value has been provided.

That the format is correct.

That is one of the available codes.

End User Vulnerability Segment

D This segment is dependent on the ‘End User Vulnerable Flag’ datafield. This segment is also defined as a repeated segment with a maximum of 20 datafields. If ‘End User Vulnerable Flag’ is set to ‘Y’, then at least the first available datafield in this segment should be populated.

End User Vulnerability Code [euVulnerabilityCode]

D 4 List Indicates which classification of ‘Vulnerable Customer’ that an End User belongs to. This field is dependent on the ‘End User Vulnerable Flag’ field above. If ‘Y’ is chosen in the ‘End User Vulnerable Flag’ field, then a value must be provided in this field. If ‘N’ is chosen in the ‘End User Vulnerable Flag’ field, then no value should be entered. Must be one of the following available codes:

Code Description

0001 Visually Impaired

0002 Mobility impaired




If ‘Y’ is chosen in the ‘End User Vulnerable Customer Flag’ field, then a value must be provided. [OVCT]

If ‘N’ is chosen in the ‘End User Vulnerable Customer Flag’ field, then no value should be provided. [VCFN]


34


0003 Hearing impaired

0004 Elderly

005 Speech Impaired

006 Language Difficulty

007 Learning Difficulty

008 Mental Health

009 Dexterity Impaired


35

2.6 Meter Read Segment

2.6.1 Description

This segment provides information about Meter Reads. The Meter Read Information Segment is incorporated into the following market messages sent between the Transporter and Registered Shippers:


G205N CoS Request Completion Notification Transporter Shipper (Incoming)

G206N CoS Request Completion Notification Transporter Shipper (Outgoing)





Transporter Shipper


Transporter Shipper

M1103N Estimate Read Request Notification Transporter Shipper





Meter Read M Segment All data items in the Meter Read Segment must be populated to defined formats and lengths. The entire segment is repeated twice in two market messages – M804N and S1604N – to cater for situations where a meter has been exchanged. When a meter exchange has taken place, the segment is repeated – once with details of the old (outgoing) meter and once with details of the new (incoming) meter.

Meter Read Creation Date [mrCreationDate]

M 10 Date The date that details of a read were entered on the GNI System. This is defined with the following XML format:

YYYY-MM-DD



36


Meter Read Sequence Number [mrSequenceNo]

M 2 Integer Number denoting the order in which a read was taken – this becomes relevant if two or more reads of the same type are taken on the same day because it allows a distinction to be made between the various reads.


Meter Read Taken Date [mrTakenDate]

M 10 Date Always associated with a meter reading index. Indicates the date on which the meter read was taken.


Meter ID [meterID] M 24 Char

The number of the meter GNI Systems will validate the information before sending the market message to the Shipper.

Meter Type Code [meTypeCode]

M 1 List Denotes the meter type. Indicates whether the meter measurement/indexes are metric or imperial. Will be one of the following available codes:

Code Description

M Metric

I Imperial


Meter Category Code [meCategoryCode]

M 1 List Denotes the category of meter – whether it is a prepayment meter or otherwise. Will be one of the following available codes:

Code Description

C Credit Meter

L Legacy PPM

P PPM

V Smart Meter with Valve

S Smart Meter for SME

D Smart Meter for Domestic


Meter Volume Corrector Flag [meVolumeCorrectorFlag]

M 1 List Indicates whether there is a Volume Corrector Unit on Site or not. Will be one of the following available codes:

Code Description

Y Yes

N No


Meter Dials/Digits O 1 Integer The number of dials/digits on a meter. This field is optional and will be populated when the information is available on GNI Systems.



37


[meDials]

Meter Read Type Code [mrTypeCode]

M 2 List Indicates the type of meter reading that was taken. Will be one of the following available codes:

Code Description

AB Meter Reader Amend

AC Amend Consumption

AM Amend meter Mix-up

AN Amend Read (billing optional) / Site Visit Read

AR Amend Reading Index Only

BR Bridge Read

CI CoS Amendment (Correction Incoming)

CL Lock/Retain Meter

CM Amend Consumption (for Meter Mixup)

CO CoS Amendment (Correction Outgoing)

CR Customer Read

CU Unlock Meter

DM Disconnect Meter

EC Exchange Closing

EG Exchange/Close to GasCard

EL Last Read at LPG

EO Exchange Opening

ER Shipper Estimate Request

FC Forced Complete

FG Fit Gascard Meter

FM Fit Meter

FN Final Read

GA PPM Actual Read

GC GasCard Closing Read (for use in PPM CoS) (read type not active)

GO Gas Card Opening Read (for use in PPM CoS) (read type not active)

GP PPM - GasCard Read @ credit purchase



38


GR PPM Statement Read

MN Meter Mix-Up

MR Meter Read

NR No Read Estimate

OR CoEU Opening Read

PC Customer Phone Read (Late)

PR Customer Phone Read

QC MRS LTNA read (billing optional) / Out of cycle Postponed Read RC Re-Lock Shipper Locked Meter (for future use)

RM Re-Lock Service Locked Meter (for future use)

RR Special Read

RP Revenue Protection

SL Lock

SU Service Unlock

YL Safety Lock

YU Safety Unlock (Turn On Meter)

ZC CoS Closing Read

ZL LPG Closing (CoS)

ZM COS Amend Read Index

ZO CoS Opening Read

ZX CoS Correction Opening Rd

ZY CoS Correction Closing Rd

Meter Read Volume Index (Previous Read) [mrVolumeIndexPrev]

M 9 Integer This will be the volume index that was recorded as part of the preceding read.


Meter Read Volume Index [mrVolumeIndex]

M 9 Integer Measure of volume of gas in Standard Cubic Meters (scm). GNI Systems will validate the information before sending the market message to the Shipper.

Meter Read Head Index (Previous Read) [mrHeadIndexPrev]

D 9 Integer This will be the meter head index that was recorded as part of the preceding read, if applicable. This field is dependent on the ‘Meter Volume Corrector Flag’ field above – if ‘Yes’ is selected there, a value will be provided in this field (assuming that a previous read exists).


Meter Read Head Index [mrHeadIndex]

D 9 Integer Read index as displayed on the mechanical Meter Head. This only applies to Volume Corrected Gas Points. This field is dependent on the ‘Meter Volume Corrector Flag’ field above – if ‘Yes’ is selected there, a value will be provided in this field.



39


Meter Read Uncorrected Index (Previous Read) [mrUncorrectedIndexPrev]

D 9 Integer This will be the uncorrected index that was recorded as part of the preceding read, if applicable. This field is dependent on the ‘Meter Volume Corrector Flag’ field above – if ‘Yes’ is selected there, a value will be provided in this field (assuming that a previous read exists).


Meter Read Uncorrected Index [mrUncorrectedIndex]

D 9 Integer Read index as displayed on the digital Uncorrected unit. This only applies to Volume Corrected Gas Points. This field is dependent on the ‘Meter Volume Corrector Flag’ field above – if ‘Yes’ is selected there, a value will be provided in this field.


Meter Read Consumption (Units) [mrConsumptionUnits]

M 10 Integer Is a measure of the quantity of gas used since the last recorded read. It is calculated by subtracting the Previous Volume Index from the Current Volume Index.


Meter Read Consumption (kWh) [mrConsumption]

M 10 Integer Is a measure of the quantity of gas offtaken at a given Gas Point in kilowatts-hours (kWh) since the last recorded read. (See Code of Operations for method of calculation).


Meter Read Conversion Factor [mrConversionFactor]

M 7 Decimal (4)

Is used to convert the volume of gas used into the equivalent energy value in “kWh” (but does not take account for any GPRN Correction Factor). Please refer to Code of Operations for formula.


Meter Read Average Calorific Value [mrAverageCalorificValue]

M 4 Decimal (1)

This is the average amount of energy generated by a given mass of gas. More specifically, it is the ratio of energy to volume measured in Megajoules per cubic meter (MJ/m3) which for a gas is measured and expressed under standard conditions of temperature and pressure. The CV value for a gas will therefore vary daily, depending on the type of gas (from where) and the temperature and the pressure of the gas.


Meter Read Meter Conversion Factor [mrMeterConversionFactor]

M 9 Decimal (6)

Denotes whether the conversion factor to be applied is metric or imperial. This will be determined by the ‘Meter Type METRIC / IMPERIAL’ field above.


Meter Read Calorific Value Zone Corrector Factor [mrCVZoneCorrectionFactor]

M 9 Decimal (6)

Correction Factors are used to convert the metered volume of gas into the equivalent volume of gas at standard reference conditions (1,013.25 mbar, 15 C) when there is no on-site conversion device. Where there is an on-site volume corrector this value is set to 1.000.


Meter Read Gas Point Correction Factor [mrGasPointCorrectionFactor]

M 7 Decimal (4)

Used to convert the metered volume of gas into the equivalent volume of gas at standard reference conditions (1,013.25 mbar, 15 C) when there is no on-site conversion device. Where there is an on-site volume corrector this value is set to 1.000.



40


Gas Point Read Cycle Code [gpReadCycleCode]

M 3 List Indicates the frequency with which a Meter is read. One of the following available codes will be provided as appropriate:

Code Description 001 Monthly

002 Bimonthly

003 Annual


Gas Point Next Read Date [gpNextReadDate]

M 10 Date Indicates the next date on which a Meter is scheduled to be read. The next read date will be +/- 3 Business days as per consultation at GMARG for MRS metrics. This is defined with the following XML format:

YYYY-MM-DD


Gas Point Peak Day Capacity [gpPeakDayCapacity]

M 7 Integer The capacity at a supply point which is deemed to be reserved for the peak day. It is used for the purposes of transportation charging and exit capacity bookings.


Gas Point Annual Consumption (kWh) [gpAnnualConsumption]

M 9 Integer Annual Quantity means:

(a) in respect of an Offtake Point at which there has been a Shipper registered for a minimum period of 12 months, the quantity of Natural Gas offtaken in respect of such Offtake Point over the immediately preceding 12 month period; or

(b) in respect of a Proposed Offtake Point, the quantity of Natural Gas which is anticipated to be offtaken at the Proposed Offtake Point over the first 12 month period following a Shipper becoming the Registered Shipper in respect of such Proposed Offtake Point.


Gas Point Consumption Band Code [gpConsumptionBandCode]

M 1 List Each Gas Point belongs to a band depending on its Annual Quantity as follows:

Code Description Max Value (kWh) Description

A Band 1 6,000 Band 1

B Band 2 23,500 Band 2

C Band 3 73,000 Band 3



41


Y Band 4 750,000 Band 4

Z Band 5 5,550,000 Band 5

Meter Read A-Factor [mrFactorA]

M 10 Decimal (4)

The A&B factors are regression coefficients used to model the demand characteristics at each NDM gas point. These coefficients are derived from the regression of the consumption at a gas point within the last 1000 days to the aggregate AWDDs. If consumption history is not available, default settings are used for the A & B factors. This is calculated in accordance with FAR Procedures: Ancillary Procedure 1 (Code of Operations).


Meter Read B-Factor [mrFactorB]

M 10 Decimal (4)

The A&B factors are regression coefficients used to model the demand characteristics at each NDM gas point. These coefficients are derived from the regression of the consumption at a gas point within the last 1000 days to the aggregate AWDDs. If consumption history is not available, default settings are used for the A & B factors. This is calculated in accordance with FAR Procedures: Ancillary Procedure 1 (Code of Operations).


[gpReadDay] M 3 Integer Indicates the read day corresponding to the read calendar. This will ensure the read day information for shipper GPRN portfolios are kept up to date from the baseline extract.


[mrStartDate] O 10 Date Start date used in Revenue protection read estimate calculation GNI Systems will validate the information before sending the market message to the Shipper.

[mrEndDate] O 30 Date End date used in Revenue protection read estimate calculation GNI Systems will validate the information before sending the market message to the Shipper.

[mrReason] O 30 Char This value will be used to give additional context to a meter read. For example, the value “RP” denoting “Revenue Protection” will be used to distinguish normal disconnect reads from revenue protection disconnect reads. Unlike other schema attributes, this attribute will not have a hard coded set of values built into the market message schema and any values used will be on a consensus basis with all market participants. Currently, apart from blank values, the only valid value is “RP” which indicates “Revenue Protection.”



42

2.7 Gas Point Status Segment

2.7.1 Description

This segment provides status details of the Gas Point to which the market message relates. The Gas Point Status Details Segment is incorporated into the following market messages sent between Registered Shippers and the Transporter:






M803N Meter Read Completion Notification – (Single Read) Transporter Shipper


Transporter Shipper





Gas Point Status M Segment All data items in the Gas Point Status Details Segment must be populated to defined formats and lengths.

Gas Point Status Code [gpStatusCode]

M 2 List Indicates the status of the Gas Point (i.e. whether there is gas connected to the Gas Point). One of the following available codes will be provided to the Shipper in this data field to indicate the status of the Gas Point.

Code Description

NW New

GO Gas On



43


DD Disconnected

SL Shipper Lock

SA Safety Lock

SE Service Lock

LN BGE Safety Lock

Gas Point Service Status Code [gpServiceStatusCode]

M 3 List Indicates whether there is a live Gas Service for the GPRN (i.e. whether gas is connected to the GPRN). The following available code will be provided to the Shipper in this data field to indicate the Gas Service Status of the Gas Point.

Code Description

GIS Gas in Service


Gas Point Registration Status Code [gpRegistrationStatusCode]

M 4 List Indicates the registration status of GPRN. One of the following available codes will be provided to the Shipper in this data field to indicate the registration status of the Gas Point.

Code Description

REGD Registered

DREG Deregistered

NREG Not-Registered



44

2.8 Meter Segment

2.8.1 Description

This segment provides details for the Meter to which the Shipper’s request relates. The Meter Details Segment is incorporated into the following market messages sent between Registered Shippers and the Transporter:




G403N End User Assignment Request Provisional Acceptance Transporter Shipper




Meter M Segment All data items in the Meter Details Segment must be populated to defined formats and lengths.

Meter ID [meterID] M 24 Char The number of the meter. Gas Shipper Communication Component will validate the data in this field to ensure:

That a value has been provided. That the format is correct – that it is not

longer than 24 characters.

Read Included Flag [meReadIncludedFlag]

M 1 List Indicates whether a read is to be included with the segment.

Code Description

Y Yes

N No If ‘Y’ is chosen, Meter Read Volume Index and Meter Read Taken Date are mandatory. This must always be ‘Y’ for G401RQ and G403N messages.

Meter Volume Corrector Flag

D 1 List Indicates whether there is a Volume Corrector Unit on Site or not.



45


[meVolumeCorrectorFlag]

This is dependent on the ‘Read Included Flag’ field. One of two available options must be provided if the ‘Read Included Flag’ is set to ‘Y’, otherwise it must be left blank:

Code Description

Y Yes

N No If ‘Y’ is chosen, then values must be provided in all three read fields (‘Volume Index’, ‘Meter Head Index’ and ‘Uncorrected Index ‘– see below).

That a value has been provided. That it is one of the available codes.


The value provided must correspond to the GPR record for that GPRN (i.e. the GPR must match the Shipper’s statement about whether the site is Volume-Corrected or not). [TVCS]

If the GPRN is Volume-Corrected, valid reads must be provided in all three of the ‘Volume Index’, ‘Meter Head Index’ and ‘Uncorrected Index ‘ fields. [IGVC]

That a correct combination of reads has been provided. [If the site is Volume-Corrected, all three reads should be provided. If the site is not Volume-Corrected, the ‘Volume Index’ and no other reads should be provided.] [INRC]


D 9 Integer Measure of volume of gas in Cubic Meters or Cubic Feet (Based on Metric/Imperial meter type on site). For sites with a volume corrector fitted, this reading is the Corrected read from the site corrector, and is the meter head index for all other sites.

This field is dependent on the ‘Read Included Flag’. If ‘Y’ is chosen in the ‘Read Included Flag’ field then a value must be provided whether regardless of the value in the ‘Meter Volume Corrector Flag’ field above. If the ‘Read Included Flag’ is ‘N’ then this field will be ignored but ideally should be blank.


That a value has been provided. That the input contains numeric values

only. That the format is correct – that it is not

longer than 9 digits. The following validation will be applied to this data field by GNI Systems:

The read index provided must be equal to or greater than the previous Actual read. [VING]

The read index provided must be within read validation tolerance levels as set by BGN Metering [RFRV]


D 9 Integer Read index as displayed on the mechanical Meter Head. This only applies to Volume Corrected Gas Points.

This field is dependent on the ‘Meter Volume Corrector Flag’ field above. If ‘Y’ is chosen in the ‘Meter Volume Corrector Flag’ field, then a value must be provided in this field. If ‘N’ is chosen in the ‘Meter Volume Corrector Flag’ field or it is left blank, then no value should be entered.

If the ‘Read Included Flag’ is ‘N’ then this field will be ignored but ideally


That the input contains numeric values only.

That the format is correct – that it is not longer than 9 digits.



46


should be blank. If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [MHNG]

If ‘Y’ is chosen in the ‘Meter Volume Corrector Flag’ field, then a value must be provided. [IGVC]

If ‘N’ is chosen in the ‘Meter Volume Corrector Flag’ field, then no value should be provided. [INRC]


D 9 Integer Read index as displayed on the digital Uncorrected unit. This only applies to Volume Corrected Gas Points.

This field is dependent on the ‘Meter Volume Corrector Flag’ field above. If ‘Y’ is chosen in the ‘Meter Volume Corrector Flag’ field, then a value must be provided in this field. If ‘N’ is chosen in the ‘Meter Volume Corrector Flag’ field or it is left blank, then no value should be entered.

If the ‘Read Included Flag’ is ‘N’ then this field will be ignored but ideally should be blank.



That the format is correct – that it is not longer than 9 digits.


If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [UING]




D 10 Date This field is dependent on the ‘Read Included Flag’. If ‘Y’ is chosen in the ‘Read Included Flag’ field then a value must be provided. Indicates the date on which the meter read was taken. If the ‘Read Included Flag’ is ‘N’ then this field will be ignored but ideally should be blank. The expected format for all date inputs is YYYY-MM-DD, giving a length of 10 characters.


That a value has been provided. That the format is correct – YYYY-MM-DD

– and is not less or greater than 10 characters.


The Read Taken Date must not exceed the allowed time lapse tolerance of 30 days. [TEAT]

The Read Taken Date must not predate the previous Actual or Customer Read. [TDPP]

A date in the future must not be provided. [TDNF]


47

2.9 Read Cycle

2.9.1 Description

This segment provides details for the Meter to which the Shipper’s request relates. The Meter Details Segment is incorporated into the following market messages sent between Registered Shippers and the Transporter:


G205N Change of Shipper Request Completion Notification Transporter Shipper

G404N End User Assignment Request Completion Notification Transporter Shipper


M1401N Updates to Meter Characteristics Information Notification Transporter Shipper


48




Read Cycle M Segment All data items in the Read Cycle Segment must be populated to defined formats and lengths.

Gas Point Read Cycle Code [gpReadCycleCode]

M 3 List Indicates the frequency with which a Meter is read. One of the following available codes will be provided as appropriate:

Code Description 001 Monthly

002 Bimonthly

003 Annual



M 10 Date Indicates the next date on which a Meter is scheduled to be read. The next read date will be +/- 3 Business days as per consultation at GMARG for MRS metrics. This is defined with the following XML format:

YYYY-MM-DD


[gpReadDay] M 3 Integer Indicates the read day corresponding to the read calendar. This will ensure the read day information for shipper GPRN portfolios are kept up to date from the baseline extract.



49

3. GPRO Market Messages

This section outlines the market messages in the GPRO business area as they appear in the Gas MaP Market Messaging solution.

The GPRO Market Messages are:

G101RQ Update End User Details Request

G102RJ Rejection Message for Update End User Details Request

G103N Notification Message for Update End User Details

G201RQ Change of Shipper NDM Request

G202RJ Rejection message for Change of Shipper NDM Request

G203N CoS Request Receipt Notification

G204N CoS Request Receipt Notification

G205N CoS Request Completion Notification

G206N CoS Request Completion Notification

G207N CoS Request Rejection Notification

G208RQ Cancellation of Change of Shipper NDM Request

G209RJ Cancellation of CoS Request Rejection

G210N Notification Message to Incoming Shipper for Cancellation of Change of Shipper NDM Request

G211N Notification Message to Outgoing Shipper for Cancellation of Change of Shipper NDM Request

G301RQ Historical Consumption Request

G302RJ Rejection Message for Historical Consumption Request


50

G303N Historical Consumption Data

G401RQ End User Assignment Request

G402RJ End User Assignment Rejection Message

G403N End User Assignment Request Provisional Acceptance

G404N End User Assignment Completion Notification

G601RQ Registration Request

G602RJ Registration Request Rejection Message

G603N Registration Request Provisional Acceptance

G604N Registration Completion Notification

G605RQ Registration Cancellation Request

G606RJ Cancellation of Registration Request Rejection Message

G607N Cancellation of Registration Request Acceptance Notification

G701N Deregistration Tariff Exemption Notification

G702N Deregistration Tariff Exemption Removal Notification

G703N Deregistration Completion Notification

G2401N Revenue Protection Case Notification


51

3.1 G101RQ – Update Existing End User Details Request

3.1.1 Purpose/Description

MPD Reference: MPD1 – Update Existing End User Details Market Process

Initiator: Shipper Recipient: Transporter

Description: Shippers will use this message when they wish to update the details of an existing End User at a Gas Point to which the Shipper is registered.

3.1.2 Market Message Structure and Validation

This section outlines the rules for composition and validation of the market message. All data fields in the market message must be populated to defined formats and lengths aligned with the “Opt – Optional” attribute that is defined at data field level.

Segment Opt Ln Typ Composition Instructions Validation

Data Field

Message Header M Segment Please refer to Section 2.1 for Message Header Common Data Segment.

Shipper Header M Segment Please refer to Section 2.2 for Shipper Header Common Data Segment.

In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems:



GPRN must be registered to Shipper sending message. [GNRS]

The Shipper status must permit this request type. [SSDS]

A valid Shipper/Supplier ID combination must be provided. [ISSC]

End User Details M Segment Please refer to Section 2.5 for End User Details Common Data Segment.


An End User must be assigned to the GPRN in advance. (Details can not be updated before the End User is assigned. To assign the End User see MPD4 – End User Assignment and its associated messages). [NEUA]


52

3.2 G102RJ – Update Existing End User Details Rejection


MPD Reference: MPD1 – Update End User Details Market Process

Initiator: Transporter Recipient: Shipper

Description: The Transporter will send this message to Shippers if the G101RQ – Update Existing End User Details Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G101RQ – Update Existing End User Details Request Market Message.




Data Field



BG Transporter Header M Segment Please refer to Section 2.3 for BG Transporter Header Common Data Segment.


End User Update Rejection Reason

M Segment Please see data field level instructions below.

G102 Rejection Code [g102RejectionCode ]

M 4 List The code identifying the reason why an ‘Update End User Details Request’ market message was invalid will be from a list of pre-defined codes. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below. Will be one of the following available codes:

Code Description

GDNE GPRN does not exist



53


Data Field

NNDG Not an NDM GPRN

GNRS GPRN is not registered to Shipper

VCFN Vulnerable Customer Types should not be provided if Vulnerable Customer Flag = ‘No’

ISSC Invalid Shipper/Supplier ID combination

NEUA No End User Assigned

OVCT At least one Vulnerable Customer Type must be provided if Vulnerable Customer set to ‘Y’

ALOS At least one set of End User contact numbers must be provided if Contact No. Avail. Set to ‘Y’

SSDS Shipper status does not support this request type

DEUF End User First Name must be provided if End User Indicator is ‘Domestic’

DEUS End User Surname must be provided if End User Indicator is ‘Domestic’

CEUF End User First Name should not be provided if End User Indicator is ‘Company’

CEUS End User Surname should not be provided if End User Indicator is ‘Company’

CEUC Company Name must be provided if End User Indicator is ‘Company’

CEUD Company Name should not be provided if End User Indicator is ‘Domestic’

NBTR No Business Type should be provided if End User Market Sector is ‘Residential’

BMPM Business Type must be provided if End User Market Sector is ‘Industrial/Commercial’

UAVC Vulnerability Information is required to use alternate address

CDVC Contact Address Information should be provided for Alternate Address for Vulnerable Customers


54

3.3 G103N – Update Existing End User Details Completion Notification


MPD Reference: MPD1 – Update End User Details Market Process


Description: The Transporter will send this message to Shippers if the G101RQ – Update Existing End User Details Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper of the current End User Details held by the Transporter following the Shipper’s most recent update.




Data Field







Vulnerable Customer O Segment Please see data field level instructions below.

Gas Point Vulnerability Warning [gpVulnerabilityWarning]

O 50 Char

If the Gas Point Register states that an End User is vulnerable and a Shipper enters ‘N’ in the ‘End User Vulnerable Flag’ in G101RQ above, the Shipper will be warned that the previous customer was a vulnerable customer. This is to warn the Shipper of a mistake that they may have made in indicating that the End User is no longer vulnerable. The following text will be sent to the Shipper in this field: ‘Record of vulnerability at GPRN. Please verify’ This will not apply

a) if the Shipper indicates that the End User is vulnerable in the G101RQ message and this field will be left blank.

b) if there has been no record of vulnerability at the GPRN in GNI Systems.



55

3.4 G201RQ – Change of Shipper NDM Request


MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process


Description: When an End User appoints a new Shipper, the incoming Shipper will use this message to register a Change of Shipper Request with the Transporter.




Data Field


Shipper Header M Segment Please refer to Section 2.2 for Shipper Header Common Data Segment. In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems:

GPRN must exist on GNI Systems. [GDNE] GPRN must be an NDM GPRN. [NNDG] The Shipper status must permit this

request type. [SSDS] A valid Shipper/Supplier ID combination

must be provided. [ISSC] The Incoming Shipper must not already be

registered to the GPRN. [GARS] The GPRN must be eligible for a Change of

Shipper Request. [GDNS] There must not be an outstanding Change

of Shipper Request for the GPRN. [OCSG] There must not be an outstanding

Registration Request for the GPRN. [ORRG]

There must not be an outstanding Change of Shipper Correction/Amendment Request for the GPRN. [OCAR]


56


Data Field

At least 20 business days must have elapsed since previous Change of Shipper for this GPRN. [LTTD]

At least 20 business days must have elapsed since Registration Request for this GPRN was processed. [LTTR]

There must not be any outstanding meter-related Site Works Requests at the GPRN. [OMRS]

If the Change of Shipper request is for a gas point with a PPM meter, the Shipper must have an agreement with the PPMSP. [SDHA]

Shipper must not have had a CoS rejected for lack of valid read for CoS in previous 7 days. [SLOC]

End User Details M Segment Please refer to Section 2.5 for the End User Details Common Data Segment.

Meter M Segment Please refer to Section 2.8 for the Meter Common Data Segment. In addition to the validation listed in section 2.8, the following validation will be applied by GNI Systems:

The meter number received in the message matches the GPRN. [GDNM]

Meter Read Index and Taken Date must be provided if Read Available flag set to ‘Y’ [MRRA]

End User Consent M Segment Please see data field level instructions below.

End User Consent Flag [euConsentFlag]

M 1 List

Code indicating whether End User consent has been received by the Shipper in advance of making a request of the Transporter, must be one of the following available codes.

Code Description

Y Yes

N No

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided. That the format is correct. That is one of the available codes.

The following validation will be applied to this data field by GNI Systems; End User consent must be received. [EUCR]


57

3.5 G202RJ – Change of Shipper Rejection




Description: The Transporter will send this message to Shippers if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G201RQ – Change of Shipper NDM Request Market Message.




Data Field



Change of Shipper Rejection Reason


G202 Rejection Code [g202RejectionCode]

M 4 List

One of the following available rejection reason codes will be provided as appropriate to identify the reason why a ‘Change of Shipper Request’ market message was rejected This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description



GARS GPRN already registered to requesting Shipper

GDNM GPRN does not match Meter Number



58


Data Field

GDNS GPRN does not support CoS request

OCSG Outstanding Change of Shipper Request for this GPRN

ORRG Outstanding Registration Request for this GPRN

OCAR Outstanding CoS Correction/Amendment Request

OMRS Outstanding Meter-related Site Works

LTTD Less than 20 business days have elapsed since last CoS for this NDM Supply Point

LTTR Less than 20 business days have elapsed since Registration was completed for this NDM Supply Point



MRTD Meter Read Taken Date does not match CoS request date

RTDT Read Taken Date must be “today”

ARAE Actual/Customer reading already exists for this taken date

ALOS At least one set of End User contact numbers must be provided if Contact No. Avail. set to ‘Y’


VCFN If No is Chosen in End User Vulnerable Flag, then no value should be provided

IGVC If GPRN is Volume Corrected, 3 reads must be provided

TVCS This is a Volume Corrected site

EUCR End User Consent must be received in advance

ZRNA Zero read not accepted – consumption has occurred

VING Volume Index not equal to or greater than previous Actual read

MHNG Meter Head Index not equal to or greater than previous Actual read

UING Uncorrected Index not equal to or greater than previous Actual read

INRC Invalid read combination

CMPS Current Gas Point Status does not support CoS

GSSN Gas Service Status is not ‘Gas in Service’


59


Data Field











SDHA Shipper does not have an agreement with PPMSP

MRRA Meter Read Index and Taken Date must be provided if Read Available flag set to ‘Y’

CSTO Change of Shipper timed out after 21 days

SLOC Shipper Locked Out of CoS for 7 days following unsuccessful CoS period.


60

3.6 G203N – Change of Shipper Receipt Notification (Incoming Shipper)



Initiator: Transporter Recipient: Incoming Shipper

Description: The Transporter will send this message to the Incoming Shipper if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Incoming Shipper that the G201RQ – Change of Shipper NDM Request Market Message has been received successfully and that the Change of Shipper process is under way.




Data Field




Gas Point Vulnerability Warning

[gpVulnerabilityWarning]

O 50 Char Message provided indicating the previous customer was vulnerable. The following text will be sent to the Shipper in this field: ‘Record of vulnerability at GPRN. Please verify’ This will not apply if there is no record of vulnerability at the GPRN (i.e. the End User was not considered vulnerable) and this field will be left blank.


COS Incoming Receipt M Segment Please see data field level instructions below. GNI Systems will validate the information before sending the market message to the Shipper.

Change of Shipper ID [cosID]

M 8 Integer

The Change of Shipper ID is a unique identifier for the Change of Shipper process. The number for this message will be the same as the GNI Reference Systems number.

The Change of Shipper ID is a mandatory field that is required if the Shipper wishes to initiate the following market message: Change of

GNI Systems will validate the information before sending the market message to the Incoming Shipper.


61


Data Field

Shipper cancellation process (G208RQ). It is also a useful reference if the Shipper wishes to initiate the Change of Shipper Correction / Amendment process later.


M 1 List Denotes the category of meter – whether it is a prepayment meter or otherwise. Will be one of the following available codes:

Code Description

C Credit Meter

L Legacy PPM

P PPM

V Smart Meter with Valve

S Smart Meter for SME

D Smart Meter for Domestic


Valid Read Received [mrValidRead]

M 1 List Indicates whether or not a valid read was received with the G201RQ message or if a valid scheduled read is available on the BGN system for that GPRN within the previous 7 days.

Code Description

Y Yes (i.e. a valid read is available for CoS)

N

No (i.e. no valid read on the BGN system or a read was received on G201RQ and was not valid or no read was received with the G201RQ message)



M 10 Date Indicates the next date on which a Meter is scheduled to be read. The next read date will be +/- 3 Business days as per consultation at GMARG for MRS metrics. This is defined with the following XML format: YYYY-MM-DD



62

3.7 G204N – Change of Shipper Receipt Notification (Outgoing Shipper)



Initiator: Transporter Recipient: Outgoing Shipper

Description: The Transporter will send this message to the Outgoing Shipper if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Incoming Shipper passes validation. This message is intended to notify the Outgoing Shipper that a G201RQ – Change of Shipper NDM Request Market Message has been received for an End User currently registered to them and that the Change of Shipper process is under way.




Data Field



COS Outgoing Receipt M Segment Please see data field level instructions below. GNI Systems will validate the information before sending the market message to the Shipper.

Change of Shipper ID

[cosID]

M 8 Integer


The Change of Shipper ID will be a useful reference if the Shipper wishes to initiate the Change of Shipper Correction / Amendment process later.



63

3.8 G205N – Change of Shipper Completion Notification (Incoming Shipper)




Description: The Transporter will send this message to the Incoming Shipper if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Shipper passes overnight validation. This message is intended to notify the Incoming Shipper that the Change of Shipper process has been completed successfully and that they are now the registered Shipper for the GPRN in question.




Data Field



COS Incoming Completion M Segment Please see data field level instructions below.


M 8 Integer


The Change of Shipper ID is a useful reference if the Shipper wishes to initiate the Change of Shipper Correction / Amendment process later.



Gas Point Vulnerability Warning

[gpVulnerabilityWarning]

O 50 Char Message provided indicating the previous customer was vulnerable. The following text will be sent to the Shipper in this field: ‘Record of vulnerability at GPRN. Please verify’ This will not apply if there is no record of vulnerability at the GPRN (i.e. the End User was not considered vulnerable) and this field will be left blank.


Meter Read M Segment Please refer to Section 2.6 for Meter Read Common Data Segment.


64


Data Field

Meter Location M Segment Please see data field level instructions below.

Gas Point Meter Location [gpMeterLocation]

M 40 Char The physical location of the Meter at the Gas Point Address


Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.

Read Cycle M Segment Please refer to Section 2.9 for Read Cycle Common Data Segment.

Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Common Data Segment.


65

3.9 G206N – Change of Shipper Completion Notification (Outgoing Shipper)




Description: The Transporter will send this message to the Outgoing Shipper if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Shipper passes overnight validation. This message is intended to notify the Outgoing Shipper that the Change of Shipper process has been completed successfully and that they are no longer the registered Shipper for the GPRN in question.




Data Field



COS Outgoing Completion M Segment Please see data field level instructions below.


M 8 Integer


The Change of Shipper ID can be a useful reference if the Shipper wishes to initiate the Change of Shipper Correction / Amendment process later.

GNI Systems will validate the information before sending the market message to the Outgoing Shipper.

Meter Read M Segment Please refer to Section 2.6 for Meter Read Information Common Data Segment.


66

3.10 G207N – Change of Shipper Rejection Notification (Outgoing Shipper)




Description: The Transporter will send this message to the Outgoing Shipper if the G201RQ – Change of Shipper NDM Request Market Message submitted by the Shipper fails overnight validation. This message is intended to notify the Outgoing Shipper that the Change of Shipper process has not been completed successfully and that they are still the registered Shipper for the GPRN in question. The reason why the Change of Shipper process has not been completed will be included in the message.

.




Data Field



Change of Shipper Rejection Notification



M 8 Integer

The Change of Shipper Number is a unique identifier for the Change of Shipper process. The number for this message will be the same as the GNI Reference Systems number.



M 4 List

One of the following available rejection reason codes will be provided as appropriate to identify the reason why a ‘Change of Shipper Request’ market message failed the overnight validation process.

Code Description



GARS GPRN already registered to requesting Shipper


GNI Systems will validate the information before sending the market message to the Outgoing Shipper.


67


Data Field

GDNS GPRN does not support CoS request

OCRG Outstanding CoS or CoSA request for this GPRN

OMRS Outstanding Meter-related Site Works

LTTD Less than 20 business days have elapsed since last CoS for this NDM Supply Point

LTTR Less than 20 business days have elapsed since Registration was completed for this NDM Supply Point


SSDN Shipper status does not support this request type

ORRG Outstanding Registration for GPRN

CGSS Current Gas Service Status does not support CoS

MRTD Meter Read Taken Date does not match CoS request date

PRIN Physical Read Index is not greater than or equal to the previous physical Read

RTDT Read Taken Date must be “today”


ALOS At least one set of End User contact numbers must be provided if Contact No. Avail. set to ‘Y’









CMPS Current Gas Point Status does not support CoS

GSSN Gas Service Status is not ‘Gas in Service’



68


Data Field


SDHA Shipper does not have an agreement with the PPMSP

RFRV Read Failed Read Validation tolerance levels


69

3.11 G208RQ– Change of Shipper Cancellation NDM Request



Initiator: Incoming Shipper Recipient: Transporter

Description: Incoming Shippers will use this message when they wish to cancel a G201RQ – Change of Shipper NDM Request Market Message that they themselves have submitted previously.




Data Field





GPRN must be an NDM GPRN. [NNDG] The Shipper status must permit this


must be provided [ISSC] There must not be an outstanding

Change of Shipper Cancellation Request for this GRPN (to avoid duplicate cancellations). [OCSC]

COS Cancellation Request M Segment Please see data field level instructions below.


M 8 Integer

The Change of Shipper ID is a unique Change of Shipper reference number that was provided to the Shipper in the Change of Shipper Notification Messages.


That a value has been provided. That only numeric values have been

provided.


70


Data Field

That the format is correct – that it is not shorter or longer than 8 digits.


The CoS can only be cancelled while the Change of Shipper Request has not been completed. [PCPE]

The CoS request must exist. [CSNE] The CoS request must not have been

completed (and completion message sent). [CSCP]

The CoS Request must match the GPRN provided in the message. [CRDN]

Shipper can only cancel requests that were raised by that Shipper. [CSAS]


71

3.12 G209RJ – Change of Shipper Cancellation Rejection




Description: The Transporter will send this message to Shippers if the G208RQ – Change of Shipper Cancellation NDM Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G208RQ – Change of Shipper Cancellation NDM Request Market Message (if applicable). It may also be the case that it is too late to cancel the Change of Shipper Request because it has already been completed and the Shipper will be advised of this.




Data Field



CoS Cancellation Rejection M Segment Please see data field level instructions below.


M 8 Integer

The Change of Shipper Number is a unique Change of Shipper reference number that was provided to the Shipper in the Change of Shipper Notification Messages.


CoS Cancellation Rejection Reason



M 4 List

One of the following available rejection reason codes will be provided as appropriate to identify the reason why a ‘Cancellation of Change of Shipper Request’ market message was rejected. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes



72


Data Field

identified below.

Code Description



SSDS Shipper status does not permit this request type

CSNE CoS Request does not exist

CSCP CoS Request has been completed

PCPE Permitted cancellation period elapsed

CSAS CoS Number belongs to another Shipper

ISSC Invalid Shipper ID/Supplier ID combination

OCSC Outstanding CoS Cancellation request at this GPRN

CRDN CoS Request does not match GPRN provided


73

3.13 G210N –CoS Cancellation Notification (Incoming Shipper)




Description: The Transporter will send this message to the Incoming Shipper if the G208RQ – Cancellation of Change of Shipper NDM Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Incoming Shipper that the G208RQ – Cancellation of Change of Shipper NDM Request Market Message has been received successfully and that the Change of Shipper process that had previously been requested has now been cancelled.




Data Field



COS Cancellation Completion M Segment Please see data field level instructions below.


M 8 Integer The Change of Shipper ID is a unique Change of Shipper reference number that was provided to the Shipper in the Change of Shipper Notification Messages.



74

3.14 G211N – CoS Cancellation Notification (Outgoing Shipper)




Description: The Transporter will send this message to the Outgoing Shipper if the G208RQ –Change of Shipper Cancellation NDM Request Market Message submitted by the Incoming Shipper passes validation. This message is intended to notify the outgoing Shipper that the Change of Shipper process that had previously been requested by the Incoming Shipper (as notified to the Outgoing Shipper in the G204N – Change of Shipper Request Notification Market Message) has now been cancelled.




Data Field



COS Cancellation Completion M Segment Please see data field level instructions below.


M 8 Integer The Change of Shipper ID is a unique Change of Shipper reference number that was provided to the Shipper in the Change of Shipper Notification Messages.



75

3.15 G301RQ –Historical Consumption NDM Request


MPD Reference: MPD3 – Request for I/C Historical Consumption Data NDM Market Process


Description: Shippers will use this message when they wish to request historical consumption data for an Industrial/Commercial NDM Supply Point.




Data Field


Shipper Header M Segment Please refer to Section 2.2 for Shipper Header Common Data Segment. In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems:

GPRN must exist on GNI Systems. [GDNE].


GPRN must be an I&C GPRN. [NICG] The Shipper status must permit this


must be provided. [ISSC] The gas point must have a valid Gas

service status. {GNIC] The GPRN must match the meter number

provided. [MNPD]

Historical Consumption Request


Shipper Authoriser Name [shipperAuthoriserNam

M 25 Char The name of the person within the Shipper’s organisation who has placed

the Historical Consumption Request.

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided.


76


Data Field

e] That the format is correct.

Shipper Contact Phone Number [shipperContactPhoneNo]

M 15 Integer Contact phone number for the person/s who applied for/authorised the

Historical Consumption Request.

End User Name [euName]

M 25 Char Name of the End User for whom the Historical Consumption details are required.

End User Email Address [euEmailAddress]

O 50 Char The email address for the End User.

Meter ID [meterID] M 24 Char

The number of the meter.

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided. That the format is correct – that it is not greater

than 24 characters. The following validation will be applied to this data field by GNI Systems:

The meter number provided must match the GPRN. [GDNM]



M 1 List


Code Description

Y Yes

N No




77

3.16 G302RJ – Historical Consumption Rejection




Description: The Transporter will send this message to Shippers if the G301RQ – Historical Consumption NDM Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G301RQ – Historical Consumption NDM Request Market Message.




Data Field



Historical Consumption Rejection Reason



M 4 List One of the following available rejection reason codes will be provided as appropriate to identify the reason why a ‘Historical Consumption Information Request’ market message was rejected, This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description

EUCR End User Consent not received





78


Data Field

NICG Not an I&C GPRN

GNIC Current Gas Service Status does not support HC Requests

GDNM GPRN does not match meter number




79

3.17 G303N – Historical Consumption Completion Notification




Description: The Transporter will send this message to Shippers if the G301RQ – Historical Consumption NDM Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper of the historical consumption data for the GRPN that they queried.




Data Field



Historical Consumption Completion


Meter ID [meterID] M

24 Char The number of the meter. GNI Systems will validate the information before

sending the market message to the Shipper

Gas Point Consumption Band Code [gpConsumptionBandCode]

M 1 List

Each Gas Point belongs to a band depending on its Annual Quantity as follows:

Code Description Max Value (kWh) Description

A Band 1 6,000 Band 1

B Band 2 23,500 Band 2

C Band 3 73,000 Band 3

Y Band 4 750,000 Band 4

GNI Systems will validate the information before sending the market message to the Shipper


80


Data Field

Z Band 5 5,550,000 Band 5

If the site has changed consumption band within the 24 month period the consumption band indicated will always be the latest status.

Gas Point Connection Type Code [gpConnectionTypeCode]

M 4 List

Each gas point is connected to the distribution or transmission network. The code is identified in the table below.

Code Description

DIST Distribution

TRAN Transmission


Gas Point Annual Consumption (kWh) [gpAnnualConsumption]

M 9 Integer

Annual Quantity means:

(a) in respect of an Offtake Point at which there has been a Shipper registered for a minimum period of 12 months, the quantity of Natural Gas offtaken in respect of such Offtake Point over the immediately preceding 12 month period; or

(b) in respect of a Proposed Offtake Point, the quantity of Natural Gas which is anticipated to be offtaken at the Proposed Offtake Point over the first 12 month period following a Shipper becoming the Registered Shipper in respect of such Proposed Offtake Point.


Gas Point Peak Day Capacity (kWh) [gpPeakDayCapacity]

M 7 Integer

The capacity at a supply point which is deemed to be reserved for the peak day. It is used for the purposes of transportation charging and exit capacity bookings.


Historical Consumption End User

M Segment

Please see data field level instructions below.

End User Name [euName]

M 25 Char

End User Name GNI Systems will validate the information before sending the market message to the Shipper.

Historical Consumption Meter Read

M Segment

Three data fields form part of this segment which will be repeated. The number of repetitions will vary according to the number of reads carried out in the 24 month period.

Meter Read Taken M

10 Date Always associated with a meter reading index. Indicates the date on GNI Systems will validate the information before

sending the market message to the Shipper.


81


Data Field

Date [mrTakenDate] which the meter read was taken.

Meter Read Type Code [mrTypeCode]

M 2 List

Indicates the type of meter reading that was taken.

Meter Read Consumption (kWh)

[mrConsumption]

M 10 Integer

A measure of the quantity of gas offtaken at a given Gas Point in kilowatts-hours (kWh) since the last recorded read. (See Code of Operations for method of calculation).


82

3.18 G401RQ – End User Assignment Request


MPD Reference: MPD4 – End User Assignment Market Process


Description: Shippers will use this message when they wish to assign or de-assign an End User to/from an NDM Supply Point on the Gas Point Register.




Data Field









The End User Assignment Request can not be processed if there is an outstanding Change of Shipper Request at the GPRN. [OCSG]

There should not be any outstanding meter-related Site Works at the GPRN. [OMRS]

End User Assignment Type M Segment Please see data field level instructions below.


83


Data Field

End User Assignment Type Code [euAssignmentTypeCode]

M 4 List End User Assignment Type Code indicates that a new End User is to be assigned to that address. De-assignment option allows the shipper to de-assign the End User with no new End User details required. Will be one of the following available codes:

Code Description

ASSN Assignment

DSSN Deassignment



the available codes. The following validation will be applied by GNI Systems:

If the ‘Deassignment’ option is chosen, an End User must be assigned to the GPRN in advance. An End User can not be deassigned if it has not been assigned in the first place. [NEUA]

End User Details D Segment Please refer to Section 2.5 for End User Details Common Data Segment. Note that the End User Details segment is dependent on the ‘End User Assignment Type Code’ data field. If the ‘Assignment’ option is selected the End User Details will be a mandatory segment, if the ‘De-assignment’ option is selected ‘End User Details’ are not required.

End User Assignment Meter M Segment Please see data field level instructions below.

End User Meter Details Flag [euMeterDetailsFlag]

M 1 List The Shipper must indicate whether Meter Details are available when submitting an End User Assignment Request message. Will be one of the following available codes:

Code Description

Y Yes

N No




Meter D Segment Please refer to Section 2.8 for Meter Common Data Segment. Note: in this message all the fields in the Meter Common Data Segment are classified as ‘dependent’. If the ‘End User Meter Details Flag’ flag above is set to ‘Y’, then this Meter Details segment should be populated. The inter-dependencies within this segment, listed in Section 2.8 for Meter Common Data Segment, will still apply.


Meter Details must be provided if Meter Details Available is set to ‘Y’. [MDMB]

The read must not have been taken prior to the Shipper being registered to the GPRN [RTPS]

The meter number received in the message must match the GPRN. [GDNM]

An Actual or Customer Read must not already exist for the same date. [ARAE]

Read included Flag must be Yes if Meter Details Flag is yes i.e. read must always be included when meter segment is used. [RFMY]

Meter Read Index and Taken Date must


84


Data Field

be provided if Read Available flag set to ‘Y’ [MRRA]


85

3.19 G402RJ – End User Assignment Rejection




Description: The Transporter will send this message to Shippers if the G401RQ – End User Assignment Request Market Message submitted by the Shipper fails validation (either initial validation or overnight validation). This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G401RQ – End User Assignment Request Market Message (if applicable).




Data Field

Message Header M Segment Please refer to Section 2.1 for Message Header Common Data Segment. GNI Systems will validate the information before sending the market message to the Shipper.



End User Assignment Rejection Reason



M 4 List Code identifying the reason why an ‘End User Assignment Request’ market message was invalid. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description






86


Data Field

TEAT

Read Taken Date exceeds the allowed time lapse tolerance of 30 days

TDPP

Read Taken Date predates previous Actual/Customer read date

RTPS Read Taken Prior to Shipper being registered to GPRN

ALOS

At least one set of End User contact numbers must be provided if Contact No. Avail. set to ‘Y’

OCSG Outstanding Change of Shipper for GPRN

OMRS Outstanding Meter Related Site Works

NEUA No End User Assigned



TDNF Taken Date can not be in the future



MDMB Meter Details must be provided if Meter Details Available is set to ‘Y’

RFMY Read included Flag Must be set to ‘Y’ if Meter Details Available is set to ‘Y’




VING

Volume Index not equal to or greater than previous Actual


87


Data Field

read





EDMP End User Details must be provided if Assignment Option is set to ‘Assign’










CDVC Contact Address Information should be provided for


88


Data Field

Alternate Address for Vulnerable Customers

MRRA Meter Read Index and Taken Date must be provided if Read Available flag set to ‘Y’



89

3.20 G403N – End User Assignment Provisional Acceptance Notification




Description: The Transporter will send this message to Shippers if the G401RQ – End User Assignment Request Market Message submitted by the Shipper passes the initial validation. This message is intended to let the Shipper know that the Request to assign or de-assign the End User has been provisionally accepted and is being processed.




Data Field








Code Description

ASSN Assignment

DSSN De-assignment



90


Data Field

The ‘End User Assignment Type Code’ will be the same value as submitted by the Shipper in the original G401RQ message.

End User Details D Segment Please refer to Section 2.5 for End User Common Data Segment. Note that the End User Details segment is dependent on the ‘End User Assignment Type Code’ data field. If the ‘Assignment’ option is selected the End User Details will be a mandatory segment, if the ‘De-assignment’ option is selected ‘End User Details’ will not be included in the message.


Meter O Segment Please refer to Section 2.8 for Meter Common Data Segment. GNI Systems will validate the information before sending the market message to the Shipper.


91

3.21 G404N – End User Assignment Completion Notification




Description: The Transporter will send this message to Shippers if the G401RQ – End User Assignment Request Market Message submitted by the Shipper passes the overnight validation. This message is intended to let the Shipper know that the Request to assign or de-assign the End User has been completed successfully.




Data Field








Code Description

ASSN Assignment

DSSN De-assignment

This will be the same value as submitted by the Shipper in the original G401RQ message.


End User Details D Segment Please refer to Section 2.5 for End User Details Common Data Segment. Note that the End User Details segment is


92


Data Field

dependent on the ‘Assignment’/De-assignment’ data field. If the ‘Assignment’ option is selected the End User Details will be a mandatory segment, if the ‘De-assignment’ option is selected ‘End User Details’ are not included in the message.

Meter Read D Segment Please refer to Section 2.6 for Meter Read Common Data Segment. Note that the Meter Read Information segment in this message is dependent on whether the Shipper submitted a read in the G401RQ – End User Assignment market message. If the G401RQ message contained a read, this segment will be populated and if the Shipper did not submit a read, this segment will be left blank.



93

3.22 G601RQ – Registration NDM Request


MPD Reference: MPD6 – Registration Market Process


Description: Shippers will use this message when they wish to become the Registered Shipper at an NDM Supply Point. The Registration Market Process contains two processes – an Operational Site Works Request for Fit Meter or Unlock Meter and an End User Assignment.



Segment

Opt Ln Typ Composition Instructions Validation Data Field



In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must not be already registered to the

Shipper. [GRSA] A valid Shipper ID and Supplier ID combination

must be provided. [ISSC] Shipper Status must support this request type.

[SSDS] There must not be an outstanding Registration

Request for this GPRN [ORRG]

Registration Request M Segment Please see data field level instructions below.

Site Works Registration Type Code [swRegistrationTypeCode]

M 3 List

These Codes for Operational Site Works activities in this market message should only be used when the Gas Point is not registered to the Shipper. Registration Related Site Works Request Type identifying the type of Site Works Activity must be one of the following available codes;

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided. That is one of the available codes.

The following validation will be applied to this data


94

Segment


Code Description

FIT Fit Meter

FPM Fit PPM Meter

UNL Unlock Meter

field by GNI Systems; Gas Point Status must be appropriate for the

requested Site Works type. [MPSA] Gas Service Status must be appropriate for the

requested Site Works type. [GPSA] There should not be any ongoing meter-related

Site Works at the GPRN (e.g. Transporter initiated safety-related Site Works. [OMRS]

There must not be a similar Site Works activity outstanding – except the “NGS – No Gas” request type. [SSWO]

If ‘Fit PPM Meter’ is chosen, the Shipper must have an agreement with the PPMSP. [SDHA]

End User Financial Hardship Flag [euFinancialHardshipFlag]

D 1 List

This field is used to indicate that a Prepayment Meter is to be fitted due to the fact that the End User is suffering financial hardship. This field is dependent on the ‘Site Works Registration Type Code’ field above. If “Fit PPM Meter” Site Works Request Type is selected, then this data field is mandatory and must be one of the following available codes:

Code Description

Y Yes (Financial Hardship)

N No

If “FIT – Fit Meter” or “UNL – Unlock Meter” Site Works Request Type is selected, then this data field should be left blank.


The following validation will be applied to this data field by GNI Systems; A value must be provided if PPM Meter is

chosen. [FHMB] No value should be provided unless PPM Meter

is chosen [FHOA]

Site Works Registration Reason Code [swRegistrationReasonCode]

D 2 List

Site Works Request Reason Code identifying the particular sub-category of Site Works Activity must be one of the following available codes based on the provided Site Works Request Type. If Registration related Site Works Request Type is selected as UNL – Unlock Meter;

Code Description

UE Service Unlock

UL Shipper Unlock

If “FIT – Fit Meter” or “Fit PPM Meter” Site Works Request Type is selected in the previous data field, then Site Works Request Reason Code data field should be left blank.

Gas Shipper Communication Component will validate the data in this field to ensure: That is one of the available codes.

The following validation will be applied to this data field by GNI Systems; Provided value must be one of the valid

combination for Site Works Activity Type and Reason Code. [IARC]


95

Segment


Meter ID [meterID] D 24 Char

The number of the meter. This field is dependent on the ‘Registration Related Site Works Request Type’ field above. If “UNL – Unlock Meter” Site Works Request Type is selected, then this data field is mandatory. If “FIT – Fit Meter” or “Fit PPM Meter” Site Works Request Type is selected, then this data field should be left blank.

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct – that it is not longer

than 24 characters. The following validation will be applied to this data field by GNI Systems: If Registration Related Site Works Request Type

is ‘Unlock Meter’, a value must be provided for Meter Number. [UMMN]

Registration Remarks M Segment Please see data field level instructions below.

Site Works Information [swInformation]

M 250 Char

Free text area for any additional job information or access information that a Shipper may wish to include as part of a Registration Request. This segment is defined as a repeated segment with a maximum of 5 repeating elements and at least the first element in this segment must be populated.

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the entered text must be up to a maximum

of 250 characters.

Registration Contact M Segment Please see data field level instructions below.

Site Works Contact Name [swContactName]

M 50 Char Name of the person who should be contacted if more information is required in relation to a Registration Related Site Works Activity.

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided. That the format is correct – not longer than 25

characters.

Site Works Contact Phone No:1 [swContactPhoneNo1]

M 15 Char

Contact phone number for the person who should be contacted if more information is required in relation to a Registration Related Site Works Activity.


digits.


O 15 Char

Secondary contact phone number for the person who should be contacted if more information is required in relation to a Registration Related Site Works Activity.

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct – not longer than 15

digits.

Registration Appointment M Segment Please see data field level instructions below.

Site Works Appointment ID [swAppointmentID]

O 10 Char

A unique reference number for each appointment slot. Shippers must acquire an Appointment ID for relevant site works activities from the “Real-time” Gas Shipper Self-Service Component in advance of submitting Registration Requests.

Gas Shipper Communication Component will validate the data in this field to ensure: That a value has been provided. That the format is correct. That the entered value has 6 digits.

The following validation will be applied to this data field by GNI Systems;


96

Segment


Appointment ID must have been reserved via “Real-time” Gas Shipper Self-Service Component. [IAID]

Appointment ID must have been set aside for the Shipper. [ANSS]

Appointment ID must have been set aside for the GPRN. [ANSG]

Appointment ID must have been set aside for the Site Works request type. [ANRT]

Appointment ID must not have been already set aside for another Site Works Request. [ASAS]

Reserved Appointment Date must be within 30 days from now. [RSDW]

An appointment should only be reserved if a registered Installer was used. [AIAP]

If an appointment is provided, it should be for a Site Works activity that requires an appointment. [NARS]



M 1 List


Code Description

Y Yes

N No



Installer Segment Please see data field level instructions below.

Installer ID [installerID] D 10 Char

ID number of the Installer. Installer ID is only required when Registration related Site Works activity type is selected as “FIT – Fit Meter” or “FPM – Fit Prepayment Meter”. Full list of valid Installer IDs can be found on the “Real-time” Gas Shipper Self-Service Component.


characters. The following validation will be applied to this data field by GNI Systems; Provided Installer ID is one of the valid codes

displayed on the “Real-time” Gas Shipper Self-Service Component. [IIDE]

House Profile Segment Please see data field level instructions below.

Gas Point House Type Code

D 1 List Code indicating the type of house for which Registration is requested. This field is dependent on the End User Market Sector.

If any value provided, Gas Shipper Communication Component will validate the data in this field to


97

Segment


[gpHouseTypeCode] If the End User Market Sector is ‘Residential’, then this field must be populated. If the End User Market Sector is’I/C’, then this field should be left blank. Must be one of the following available codes.

Code Description

B Bungalow

D Detached

F Flat

O O/O Residential

S Semi-Detached

T Terrace

This field is also dependent on the Site Works Registration Type Code. If “UNL – Unlock Meter” Site Works Request Type is requested, then this data field should be left blank.

ensure: That the format is correct. That is one of the available codes.

The following validation will be applied to this data field by GNI Systems; “House Type” should be provided if Site Works

Registration Type Code is “FIT – Fit Meter”. [FMHP]

Gas Point House Bedrooms Code [gpHouseBedroomsCode]

D 1 List

The number of bedrooms in the house for which Registration is requested. This field is dependent on the End User Market Sector. If the End User Market Sector is ‘Residential’, then this field must be populated. If the End User Market Sector is’I/C’, then this field should be left blank. This field is also dependent on the Site Works Registration Type Code. If “UNL – Unlock Meter” Site Works Request Type is requested, then this data field should be left blank. Must be one of the following available codes:

Code Description

1 One bedroom

2 Two bedrooms

3 Three bedrooms

4 Four bedrooms

5 Five bedrooms

6 Six bedrooms

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That is one of the available codes.

The following validation will be applied to this data field by GNI Systems; “Number of Rooms” should be provided if Site

Works Registration Type Code is “FIT – Fit Meter”. [FMNR]

Valid House Type and Number of Bedrooms combination should be provided. [IHTB]


98

Segment


End User Details M Segment Please refer to Section 2.5 for End User Details Common Data Segment


99

3.23 G602RJ – Registration Rejection




Description: The Transporter will send this message to Shippers if the G601RQ – Registration NDM Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G601RQ – Registration NDM Request Market Message.



Segment




Registration Rejection Reason



M 4 List

This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description



GRSA GPRN registered to a Shipper already

ORRG Outstanding Registration Request for GPRN


SSDS Shipper status does not support this request



100

Segment


type


VCFN Vulnerable Customer Types should not be provided if Vulnerable Customer Flag = ‘No’

OMRS Outstanding Meter Related Site Works

MPSA Gas Point Status is not appropriate for this Site Works type

GPSA Gas Service Status is not appropriate for this Site Works type

SSWO Similar Site Works activity outstanding.

IARC Invalid Combination of Site Works Activity Type and Reason Code

SRAI Site Works Activity Requires Appointment

IAID Appointment ID does not exist

ANSS Appointment ID not set aside for this Shipper

ANSG Appointment ID not set aside for this GPRN

ANRT Appointment ID not set aside for this Site Works request type

ASAS Appointment ID already set aside for another Site Works Request

RSDW Reserved AppoIntment Date must be within 30 days from now.


IIDE Installer ID does not exist

FMHP Site Works Type (Fit Meter) requires House Profile Details to be provided.

FMNR Site Works Type (Fit Meter) requires Number of Rooms information to be provided.

ALOS At least one set of End User contact numbers must be provided if Contact No. Avail. Set to ‘Y’

UMMN If Unlock Meter request, Meter Number must be provided

ICMS Invalid combination for GPRN/ Meter No provided




101

Segment








AIAP Appointment Illegal – Awaiting Prepayment from End User


FHOA Financial Hardship only applies to Prepayment Meters

FHMB Financial Hardship indicator must be poplulated for PPM Meters

IHTB Invalid House Type/Bedroom combination



NARS No appointment required for this Site Works activity.


102

3.24 G603N- Registration Provisional Acceptance




Description: The Transporter will send this message to Shippers if the G601RQ – Registration NDM Request Market Message submitted by the Shipper passes validation. This message is intended to let the Shipper know that the Registration request has passed the validation and that the Registration is being processed.



Segment





Registration Acceptance M Segment Please see data field level instructions below.

Site Works Reference [swRef]

M 12 Char

A unique reference number that will be assigned to the Registration related Site Works Request by the GNI Systems and will be quoted back to the Shipper when the Registration request was accepted. This reference number must be used by the Shippers in the relevant market messages as outlined below;

If the Shipper wishes to cancel the registration request, then G605RQ – Registration Cancellation Request Market Message should be submitted using this reference number.

If the Shipper wishes to re-schedule the registration request, then S1502RQ – Appointment Re-Scheduling Request Market Message should be submitted using this reference number.



O 10 Char A unique reference number for each appointment slot, which was provided by the Shipper in G601RQ – Registration Request Market Message, will be quoted back to the Shipper when the Registration



103

Segment


request was accepted.

Site Works Appointment Date [swAppointmentDate]

O 10 Date

The date on which a scheduled appointment is due. This will be determined by the Appointment ID that has been chosen on the “Real-time” Gas Shipper Self-Service Component. This is defined with the following XML format:

YYYY-MM-DD


Site Works Appointment Time Frame [swAppointmentTimeFrame]

O 11 Char

The time at which a scheduled appointment is due (time from, time to). This will be determined by the Appointment ID that has been chosen on the “Real-time” Gas Shipper Self-Service Component. This is defined with the GMT offset in the following format:

hh:mm-hh:mm



104

3.25 G604N- Registration Completion Notification




Description: The Transporter will send this message to Shippers once the Registration process has been successfully completed.



Segment




Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Reference Common Data Segment.

Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Details Common Data Segment.

Registration Completion M Segment Please see data field level instructions below.

Site Works Registration Completion Code [swRegistrationCompletionCode]

M 3 List

Code identifying the status of the completed Site Works Activity. One of the following codes will be provided to the Shipper in this data field to indicate the completion status of site works request.

Code Description

CPD Completed

SHC Shipper Cancelled – No Charge

SCC Shipper Cancelled – Charge Applies

WNR Work Not Required – No Charge

WNC Work Not Required – Site Attendance Charge Applies

SNR Action Required - Site was not Ready

USL Action Required - Safety Locked – Leak



105

Segment


UFI Action Required - Flue Inadequate

UFS Action Required - Failed Soundness Test

ULA Action Required - Location of Appliances

UIV Action Required - Inadequate Ventilation

UPI Action Required - Pipe work Incomplete

UWP Action Required - Water in Internal Pipe work

ASR Action Required – Shipper must create an additional Site Works request.

NOC Action Required – No Cert

NOF Action Required – No Access – House can not be found

NOP Action Required - No Access - Site Works Contact Phone Number is not working/reachable

NOR Action Required - No Access - Not requested by this End User

NOM Action Required - No Access - Meter is not accessible

USS Action Required – Leak on Supply

CPS Completed, Meter is Safety Locked

MMM Action Required – Meter Mix-up issue discovered

MRM Action Required – Meter Previously Removed

MNC Work Not Required – Site Attendance Charge Applies - No Reads Available

MNR Work Not Required – No Charge - No Reads Available

IVC Action Required – Invalid Cert

VCP Work Completed, Vulnerable Customer at premises

Site Works Completion Comment [swCompletionComment]

M 50 Char The description of the Site Works Job Completion Status Code as provided in the previous data field.


Meter Location D Segment Please see data field level instructions below.

Gas Point Meter Location

D 40 Char The physical location of the Meter at the Gas Point Address. This segment will only be populated if the ‘Site Works Completion Code’ is



106

Segment


[gpMeterLocation] one of the following: CPD, CPS, WNC, WNR, VCP

Site Works Invoice M Segment Please see data field level instructions below.

Site Works Invoice Amount (Euro) [swInvoiceAmount]

M 10 Decimal (2)

The amount payable (where applicable) by the Shipper for a Registration related Site Works Activity.


Read Cycle D Segment Please refer to Section 2.9 for Read Cycle Common Data Segment. This segment will only be populated if the ‘Site Works Completion Status Code’ is one of the following: CPD, CPS, WNC, WNR, VCP


Meter Read D Segment

Please refer to Section 2.6 for Meter Read Common Data Segment. This segment is dependent on the ‘Site Works Completion Status Code’. Meter Read Information will only be provided if no further action is required to complete the Site Works Request. This segment will only be populated if the ‘Site Works Completion Status Code’ is one of the following: CPD, CPS, WNC, WNR, VCP


107

3.26 G605RQ – Registration Cancellation Request




Description: Shippers will use this message when they wish to cancel a previously submitted G601RQ – Registration NDM Request Market Message.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must be provisionally registered to the

Shipper. [GPPS] A valid Shipper ID and Supplier ID combination


[SSDS] There must not be an outstanding Registration

Cancellation Request for this GPRN (to avoid duplication). [ORCR]

Registration Cancellation Request



M 12 Char

If the Shipper wishes to cancel a Registration request, the GNI Systems reference number for the original Site Works request (Site Works Reference Number) must be quoted in the Cancellation Request, so the Transporter knows which site works job is to be cancelled.

Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That the entered value has 7 digits.


108

Segment


The following validation will be applied to this data field by GNI Systems; Original Site Works Request Reference must be

generated previously by G601RQ. [ISRN] Original Site Works Reference Number must

have been set aside for the Shipper. [RRBS] Original Site Works Reference Number must

have been set aside for a Registration Related Site Works Activity (Fit Meter/ Unlock Meter). [OSNS]

Registration related Original Site Works Request must have been set aside for the GPRN. [SRBG]

Cancellation request should comply with the Cancellation rules (i.e. Site Works requests can not be cancelled via market messaging after 13:00 one day before the actual appointment date). [SCCT]

Registration Completion Market Message must not have been sent in advance of Registration Cancellation Market Message being received. [SWAC]


109

3.27 G606RJ – Registration Cancellation Rejection




Description: The Transporter will send this message to Shippers if the G605RQ – Registration Cancellation Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can take corrective action, amend and resubmit the G605RQ – Registration Cancellation Request Market Message, if applicable. It may also be the case that the cancellation request can not be processed because the Registration is already complete, in which case this message would signify the end of the process.



Segment




Registration Cancellation Rejection



M 12 Char GNI Systems reference number for the original Site Works request. GNI Systems will validate the information before sending the market message to the Shipper.

Registration Cancellation Rejection Reason



M 4 List


Code Description





110

Segment


GPPS GPRN not provisionally registered to Shipper

ISSC Invalid Shipper ID/Supplier ID Combination


ISRN Site Works Reference Number does not exist

RRBS Original Site Works Reference Number belongs to another Shipper

SRBG Original Site Works Reference Number belongs to another GPRN

OSNS Original Site Works Reference Number not set aside for Registration Related Activity

SCCT Site Works cannot be cancelled because of time constraints

SWAC Site Work already complete

ORCR Outstanding Registration cancellation request at this GPRN


111

3.28 G607N - Registration Cancellation Completion Notification




Description: The Transporter will send this message to Shippers if the G605RQ – Registration Cancellation Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that the Registration Request has been cancelled.



Segment





Registration Cancellation Completion



M 12 Char A unique reference number for the original Site Works request that is cancelled as per the Shipper’s G605RQ – Registration Cancellation Request Market Message.



O 10 Char

A unique reference number for each appointment slot. The information provided in this data field belongs to the cancelled site works request and it is provided to the Shipper for information purposes only.



O 10 Date

The date on which the cancelled appointment was due. This will be determined by the Appointment Reservation ID. This is defined with the following XML format:

YYYY-MM-DD



O 11 Char

The time at which the cancelled appointment was due (time from, time to). This will be determined by the Appointment Reservation ID. This is defined with the GMT offset in the following format:

hh:mm-hh:mm



112

3.29 G701N – Deregistration Tariff Exemption Notification


MPD Reference: MPD7 – Deregistration Market Process


Description: The Registered Shipper at an NDM Supply Point will receive this notification when they are exempt from transportation charges for that Supply Point


This section outlines the rules for composition and validation of the market message. All data fields in the market message must be populated to defined formats and lengths.

Segment




BG Transporter Header

Deregistration Tariff Exempt M Segment Please see data field level instructions below.

Gas Point Deregistration Tariff Exempt Date [gpTariffExemptDate]

M 10 Date The date on which a Deregistration tariff exemption became effective. This is defined with the following XML format: YYYY-MM-DD



113

3.30 G702N – Deregistration Tariff Exemption Removal Notification




Description: The Transporter will send this message to Shippers when the NDM Supply Point is no longer exempt from transportation charges for that supply point.


This section outlines the rules for composition and validation of the market message. All data fields in the market message must be populated to defined formats and lengths aligned with the “Opt - Optional” attribute that is defined at data field level.


Data Field





Meter Read M Segment Please refer to Section 2.6 for Meter Read Common Data Segment. GNI Systems will validate the information before sending the market message to the Shipper.




114

3.31 G703N – Deregistration Completion Notification




Description: The Transporter will send this message to Shippers once the Deregistration process has been successfully completed.



Segment




Deregistration Completion M Segment Please see data field level instructions below.

Gas Point Registration Status Code

M 4 List

Indicates the registration status of GPRN. One of the following available codes will be provided to the Shipper in this data field to indicate the registration status of the Gas Point.

Code Description

DREG Deregistered


Gas Point Deregistration Status Date [gpRegisteredDate]

M 10 Date The date on which a Deregistration became effective. This is defined with the following XML format:

YYYY-MM-DD



115

3.32 G2401N – Revenue Protection Case Notification


MPD Reference:


Description: The Transporter will send this message to Shippers to notify when a new revenue protection case is opened, updated or closed at a registered gas point.



Segment




Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment

Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Common Data Segment

Case Notification M Segment Please see data field level instructions below.

Case ID [caseID]

M 10 Integer The unique case number assigned to the case in question.


Type Code [caTypeCode]

M 2 Char Code Description

RP Revenue Protection


Supplier Flag [caSupplierFlag]

M 1 Char

Indicates if the respective supplier initiated the creation of the case and will contain one of the following values:

Code Description

Y Yes

N No



116

Segment


Action [caAction]

M 30 Char

Action Description

Open The respective case has been opened

Update The respective case has been updated

Close The respective case has been closed


Phase [caPhase]

O 30 Char

Phase Scheduled Site Visit Site Visit Outcome Off-Site Testing Outcome Siteworks Cost Recovery


State [caState]

O 30 Char

State Site Visit Scheduled Site Visit NOT Scheduled Meter Exchanged Meter NOT Exchanged No Access Access Denied Meter Tampered Meter NOT Tampered Payment Received Meter Disconnected Service Cut-Off Meter Reconnected Service Reconnected No Reconnection Case Cancelled


Closure Code [caClosureCode]

O 2 Char

Code

NS Site Visit Not Scheduled

NE Meter NOT Exchanged

NA No Access

AD Access Denied

NT Meter NOT Tampered

PR Payment Received

MR Meter Reconnected

NR No Reconnection

CC Case Cancelled



117

Segment


Comment [caComment]

O 250 Char May be used to provide an additional free text comment about the respective case.



118

4. NDM Market Messages

This section outlines the market messages in the NDM business area as they appear in the Gas MaP Market Messaging solution.

The NDM Market Messages are:

M801RQ Shipper Entered Meter Read Entry – NDM Generic / Volume Corrected

M802RJ Meter Read Rejection



M901RQ Meter Read Query

M902RJ Meter Read Query Rejection

M903N Meter Read Query Resolution Notification

M1101RQ Estimate Read Request

M1102RJ Estimate Read Request Rejection

M1103N Estimate Read Request Notification

M1401N Updates to Meter Update Notification


119

4.1 M801RQ – Meter Read Request – NDM


MPD Reference: MPD8 – Meter Read Information Market Process


Description: Shippers will use this message when they wish to enter a customer read.

This section provides segment and data field details of M801RQ – Meter Read Request – NDM Market Message that allow the market message information to be interpreted by a receiving Market Participant. This market message is used in MPD8 – Meter Read Information Market Process.




Data Field






GPRN must be registered to Shipper sending message unless pending CoS to that shipper. [GNRC]

There must be a meter at the Meterpoint [NMAM]



Meter Read Request M Segment Please see data field level instructions below.


120


Data Field

Meter Read Type Code (Shipper Read) [mrTypeCodeShipper]

M 2 List Indicates the type of meter reading that was taken. In this message, there will only be one available option for Shippers to select:

Code Description

CR Customer Read The expected value, therefore, will be ‘CR’. This refers to a Meter Read received by the Shipper directly from the End User.


That a value has been provided. That the format is correct – that it has 2

characters. That it is one of the available codes.


The Read Type must exist on GNI Systems. [RTDE]

The Read Type must be approved for the Shipper. [RTNA]

There must be at least one previous read for the GPRN [NPRN]


M 10 Date Always associated with a meter reading index. Indicates the date on which the meter read was taken. This is defined with the following XML format:

YYYY-MM-DD


That a value has been provided. That the format is correct – dd/mm/yy –

and is not less or greater than 8 characters.



The read must not have been taken prior to the Shipper being registered to the GPRN unless there is a pending CoS. [RTPC]

An Actual or Customer Read must not already exist for the same date. [ARAE]

The Read Taken Date must not predate the previous Actual or Customer Read. [TDPP]

The Read Taken Date must not exceed the allowed time lapse tolerance of 30 days. [TEAT]

Meter Volume Corrector Flag [meVolumeCorrectorFlag]

M 1 List Indicates whether there is a Volume Corrector Unit on Site or not. One of two available options must be provided:

Code Description

Y Yes

N No



shorter or longer than 1 character. That it is one of the available codes.


121


Data Field

If ‘Y’ is chosen, then values must be provided in all three read fields (‘Volume Index’, ‘Meter Head Index’ and ‘Uncorrected Index ‘– see below). If the site is Volume-Corrected, all three reads should be provided. If the site is not Volume-Corrected, the ‘Volume Index’ and no other reads should be provided.


The value provided must correspond to the GPR (Gas Point Register) record for that GPRN (i.e. the GPR must match the Shipper’s statement about whether the site is Volume-Corrected or not). [TVCS]

If the GPRN is Volume-Corrected, valid reads must be provided in all three of the ‘Volume Index’, ‘Meter Head Index’ and ‘Uncorrected Index ‘ fields. [IGVC]

That a correct combination of reads has been provided. [INRC]


M 9 Integer Measure of volume of gas in Cubic Meters or Cubic Feet (Based on Metric/Imperial meter type on site).

For sites with a volume corrector fitted, this reading is the Corrected read from the site corrector, and is the meter head index for all other sites.

This field is mandatory and a value must be provided regardless of the value in the ‘Meter Volume Corrector Flag’ field above.


That a value has been provided. That the input contains numeric values

only. That the format is correct – that is not

longer than 9 digits. The following validation will be applied to this data field by GNI Systems:

The read index provided must be equal to or greater than the previous Actual read. [VING]

The read index provided must be within read validation tolerance levels as set by BGN Metering [RFRV]


D 9 Integer Read index as displayed on the mechanical Meter Head. This only applies to Volume Corrected Gas Points.

This field is dependent on the ‘Meter Volume Corrector Flag’ field above. If ‘Y’ is chosen in the ‘Meter Volume Corrector Flag’ field, then a value must be provided in this field. If ‘N’ is chosen in the ‘Meter Volume Corrector Flag’ field, then no value should be entered.



That the format is correct – that is not longer than 9 digits.





122


Data Field

If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [MHNG]


D 9 Integer Read index as displayed on the digital Uncorrected unit. This only applies to Volume Corrected Gas Points.

This field is dependent on the ‘Meter Volume Corrector Flag’ field above. If ‘Y’ is chosen in the ‘Meter Volume Corrector Flag’ field, then a value must be provided in this field. If ‘N’ is chosen in the ‘Meter Volume Corrector Flag’ field, then no value should be entered.



That the format is correct – that is not longer than 9 digits.




If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [UING]


123

4.2 M802RJ – Meter Read Rejection




Description: The Transporter will send this message to Shippers if the M801RQ – Meter Read Request – NDM Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the M801RQ – Meter Read Request – NDM Market Message.




Data Field





Meter Read Rejection M Segment Please see data field level instructions below.


M 10 Date The ‘Meter Read Taken Date’ of the read supplied as part of ‘Meter Read Request’ market message that is being rejected. If the Transporter rejects a ‘Shipper Entered Meter Read Entry’, the ‘Taken Date’ of the read on the original message sent by the Shipper is quoted back in this field as the ‘Meter Read Taken Date’. This is defined with the following XML format:

YYYY-MM-DD



M 9 Integer The ‘Meter Read Volume Index’ supplied as part of ‘Meter Read Request’ market message that is being rejected. If the Transporter rejects a ‘Meter Read Request’, the ‘Meter Read Volume Index’ on the original M801RQ market message sent by the Shipper is quoted back in this field as the ‘Meter Read Volume Index’.


Meter Read Type Code (Shipper Read)

M 2 List The ‘Meter Read Type Code’ supplied as part of ‘Meter Read Request’ market message that is being rejected. If the Transporter rejects a



124


Data Field

[mrTypeCodeShipper] ‘Meter Read Request’, the ‘Meter Read Type Code’ on the original M801RQ market message sent by the Shipper is quoted back in this field as the ‘Meter Read Type Code’.

Meter Read Rejection Reason


M802 Rejection Code [m802RejectionCode]

M 4 List Code identifying the reason why a ‘Meter Read Request’ market message was invalid. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description



GNRC GPRN is not registered to Shipper and is not pending CoS to that shipper

RTNA Read Type not approved for Shipper

RTPC Read taken prior to Shipper being registered to GPRN and GPRN is not pending CoS to that Shipper

NMAM No Meter at Gas Point

NPRN No Previous Reads. Read can not be accepted

TEAT Read Taken Date exceeds the allowed time lapse tolerance of 30 days

TDPP Read Taken Date predates previous Actual/Customer read date


RTDE Read Type does not exist on GNI System




TDNF Read Taken Date can not be in the future






125


Data Field





126

4.3 M803N – Meter Read Completion Notification – (Single Read)




Description: The Transporter will send this message to Shippers if the M801RQ – Meter Read Request – Market Message submitted by the Shipper passes validation. This message is intended to pass the Meter Read Information on to the Shipper. A single Meter Read Information Segment is included in this message. This message will also be sent to Shippers for Meter Read Information as part of NDM Procedures.




Data Field









127

4.4 M804N – Meter Read Completion Notification – (Double Read)




Description: This message is intended to pass the Meter Read Information on to the Shipper where two single reads are required as part of a logical business transaction e.g. Transporter initiated meter exchange.




Data Field






Meter Read M Segment Please refer to Section 2.6 for Meter Read Common Data Segment. The entire segment is repeated twice in this market message where two sets of read information are required to complete one logical business transaction e.g. meter exchange. When a meter exchange has taken place, the segment is repeated – once with details of the old (outgoing) meter and once with details of the new (incoming) meter. The structure of the segments is identical.





128

4.5 M901RQ – Meter Read Query Request


MPD Reference: MPD9 – Meter Read Query Resolution Market Process


Description: Shippers will use this message when they wish to query a read that has been provided by the Transporter previously.




Data Field







The Shipper status must permit this request type.[SSDS]


The message will be set to ‘Y’ to ensure that it is not a duplicate of an existing query. [DUQU]

Meter Read Query Request M Segment Please see data field level instructions below.

Meter Read Query Subject [mrQuerySubject]

M 50 Char When submitting a ‘Meter Read Query Request’ message, Shippers must supply the subject line of the query in this field.


That a value has been provided. That the format is correct - that is does

not exceed the maximum of 50 characters.


129


Data Field

There is no individual business logic validation for this field.


M 10 Date Always associated with a meter reading index. Indicates the date on which the meter read was taken. The expected format for all date inputs is YYYY-MM-DD, giving a length of 10 characters.



– and is not less or greater than 10 characters.



The read must not have been taken prior to the Shipper being assigned to the GPRN. [MRTP]

Meter Read Sequence Number [mrSequenceNo]

M 2 Integer Number denoting the order in which a read was taken – this becomes relevant if two or more reads of the same type are taken on the same day because it allows a distinction to be made between the various reads. It is mandatory to supply a value in this field so if only one read was taken on the day in question, then a value of ‘1’ should be entered. The Meter Read Sequence Number will be included in every Meter Read market message (M803N/M804N).


That a value has been provided. That the format is correct – that the value

is not less than 1 integer and not greater than 2 integers in length.

That only numeric values have been provided.


Meter Read Query Details [mrQueryDetails]

M 250 Char When submitting a ‘Meter Read Query Request’ message, Shippers must supply some details of the query (up to a maximum of 250 characters) in this field.


That a value has been provided. That the format is correct – that the value

is not greater than 250 characters in length.


The complete message will be manually checked by a GNI operator to ensure that there is sufficient detail in the combined ‘Meter Read Query Details Information’ fields for the query to be followed up successfully. If the combined detail of the


130


Data Field

message is insufficient, the message will be rejected. [


131

4.6 M902RJ – Meter Read Query Rejection




Description: The Transporter will send this message to Shippers if the M901RQ – Meter Read Query Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the M901RQ – Meter Read Query Market Message.

This section provides segment and data field details of M902RJ – Meter Read Query Rejection Market Message that allow the market message information to be interpreted by a receiving Market Participant. This market message is used in MPD9 – Meter Read Query Resolution.




Data Field





Meter Read Query Rejection M Segment Please see data field level instructions below.

Meter Read Query Rejection Subject [mrQuerySubject]

M 50 Char When rejecting a ‘Meter Read Query Request’ message sent by a Shipper, the Transporter will supply the subject line of the Rejection in this field. This will be the original information sent in by the Shipper in the ‘Meter Read Query Subject’ field in M901RQ (see above).


Meter Read Query Rejection Reason



132


Data Field


M 4 List Code identifying the reason why a ‘Meter Read Query Request’ market message was invalid. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined codes identified below.

Code Description



GNRS GPRN is not registered to Shipper MRTP Meter Read taken prior to Shipper being assigned to

GPRN






133

4.7 M903N – Meter Read Query Completion Notification




Description: The Transporter will send this message to Shippers if the M901RQ – Meter Read Query Request Market Message submitted by the Shipper passes validation. This message is intended to let the Shipper know the resolution to their Meter Read Query. If any read amendments are made as part of the Meter Read Query Resolution, then it will be sent as part of the MPD8 – Meter Read Information Market Process.




Data Field





Meter Read Query Completion


Meter Read Query Resolution Subject [mrQueryResolutionSubject]

M 50 Char When responding to a ‘Meter Read Query Request’ message, the Transporter will supply the subject line of the Resolution Notification for the query in this field.


Meter Read Query Resolution Details [[mrQueryResolutionDetails]

M 250 Char Free text area allowing the Transporter to enter some remarks in relation to the Meter Read Query Resolution.



134

4.8 M1101RQ – Estimated Read Request


MPD Reference: MPD11 – Shipper Estimated Read Request Market Process


Description: Shippers will use this message when they wish to request an Estimated Read for Generic and Volume Corrected NDM Gas Points to which the Shipper is registered.




Data Field









There must be a meter at the Meterpoint [NMAM]

Estimated Read Request M Segment Please see data field level instructions below.

Meter Read Requested Estimate Date [mrRequestedEstimate

M 10 Date The date on which an Estimated Read will be ‘taken’ i.e. the effective date of an Estimated Read as put against the GPRN on the GNI Systems. This is defined with the following XML format:

YYYY-MM-DD



– and is not less or greater than 10


135


Data Field

Date] characters. The following validation will be applied to this data field by GNI Systems:.


The read must not have been taken prior to the Shipper being assigned to the GPRN. [MTPS]

A reading must not already exist for this date. [RAET]

The Read Taken Date must not predate the previous read date. [TDPP]

The Estimate Read Taken Date must not exceed the allowed time lapse tolerance of 30 days. [TEAT]


136

4.9 M1102RJ – Estimated Read Rejection


MPD Reference: MPD11 – Shipper Estimate Read Request Market Process


Description: The Transporter will send this message to Shippers if the M1101RQ – Estimated Read Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the M1101RQ – Estimated Read Request Market Message.




Data Field





Estimated Read Rejection M Segment Please see data field level instructions below.

Meter Read Requested Estimate Date [mrRequestedEstimateDate]

M 10 Date When rejecting an ‘Estimated Read Request’ sent by the Shipper, the Transporter will include the ‘Estimate Read Details Rejection Taken Date’ to enable the Shipper to see which ‘Estimated Read Request’ is being rejected. This will be the ‘Meter Read Requested Estimate Date’ supplied by the Shipper as part of the ‘Estimate Read Request’. This is defined with the following XML format:

YYYY-MM-DD


Estimated Read Rejection Reason



M 4 List Code identifying the reason why a ‘Estimate Read Request’ market message was invalid. This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a



137


Data Field

list of pre-defined codes identified below.

Code Description RAET Reading already exists for this taken date





TDPP Read Taken Date predates previous read date

MTPS Meter Read taken prior to Shipper being assigned to GPRN

TEAT Read Taken Date exceeds the allowed time lapse tolerance of 30 days


SSDS Shipper status does not permit this request type

NMAM No Meter at Meterpoint

NPRN No Previous Reads. Read can not be accepted


138

4.10 M1103N – Estimated Read Completion Notification


MPD Reference: MPD11 – Shipper Estimate Read Request Market Process


Description: The Transporter will send this message to Shippers if the M1101RQ – Estimated Read Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper of the estimated Meter Read Information for the Gas Point for which they requested an estimate.




Data Field





Meter Read M Segment Please refer to Section 2.6 for Meter Read Information Common Data Segment.



139

4.11 M1401N – Meter Update Notification


MPD Reference: MPD14 – Notification for Meter Update Market Process


Description: The Transporter will send this message to Shippers whenever a meter characteristic for a Gas Point is updated




Data Field



BG Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.


Read Cycle O Segment Please refer to Section 2.9 for Read Cycle Information Common Data Segment.


Meter Details O Segment Only to be included in contexts where one of the meter attributes has changed.


Meter ID [meterID]

M 24 Char The number of the meter GNI Systems will validate the information before sending the market message to the Shipper.

Meter Type Code [meTypeCode]

M 1 List Denotes the meter type. Indicates whether the meter measurement/indexes are metric or imperial. Will be one of the following available codes: Code Description M Metric I Imperial



M 1 List Denotes the category of meter – whether it is a prepayment meter or otherwise.



140


Data Field

Will be one of the following available codes: Code Description C Credit Meter L Legacy PPM P PPM V Smart Meter (Valve) S Smart Meter (SME) D Smart Meter (Domestic)

Meter Volume Corrector Flag {meVolumeCorrectorFlag]

M 1 List Indicates whether there is a Volume Corrector Unit on Site or not. Will be one of the following available codes: Code Description Y Yes N No


Meter Dials/Digits [meDials]

O 1 Integer The number of dials/digits on a meter. This field is optional and will be populated when the information is available on GNI Systems.



141

5. Site Works Market Messages

This section outlines the market messages in Site works business area in which they appear in the Gas MaP Market Messaging solution.

Site Works Market Messages are:

S1501N Site Works Appointment Re-Scheduling Notification

S1502RQ Site Works Appointment Re-Scheduling Request

S1503RJ Site Works Re-Scheduling Request Rejection

S1504A Site Works Re-Scheduling Request Acceptance

S1601RQ Site Works Creation Request

S1602RJ Site Works Rejection

S1603A Site Works Request Acceptance

S1604N Site Works Completion

S1701RQ Site Works Cancellation Request

S1702RJ Site Works Cancellation Request Rejection

S1703A Site Works Cancellation Request Acceptance

S1901RQ Site Works Complaint Request

S1902RJ Site Works Complaint Request Rejection

S1903A Site Works Complaint Request Acceptance

S1904N Receipt Notification for End User Complaint for Shipper Initiated Site Works Request

S1905N Resolution Notification for End User Complaint for Shipper Initiated Site Works Request

S2301RQ Update Request for Maintenance of Gas Point Address

S2302RJ Rejection for Update Request for Maintenance of Gas Point Address

S2303N Notification for Maintenance of Gas Point Address Update


142

5.1 S1501N - Site Works Appointment Re-Scheduling Notification


MPD Reference: MPD15 – Management of Appointments Market Process


Description: The Transporter will send this message to Shippers when the Transporter has to reschedule an appointment for operational reasons.



Segment




Site Works Appointment Notification



M 12 Char

If the Transporter wishes to reschedule an appointment, the GNI Systems reference number for the original Site Works request must be quoted in the Appointment Rescheduling Notification so Shipper knows which appointment is to be rescheduled.



M 10 Char

A unique reference number for each appointment slot. Transporter will provide an Appointment ID for the rescheduling of the following site works request types;

Code Description Code Description

UNL Unlock Meter INV Investigation

DCT Disconnect SPR Special Read

LCK Lock Meter TSP Test Service Pipe

EXC Exchange Meter TEM Test Meter

FIT Fit Meter FPM Fit PPM Meter



143

Segment



M 10 Date


YYYY-MM-DD



M 11 Char


hh:mm-hh:mm


Site Works Rescheduling Reason Code [swReschedulingReasonCode]

M 4 List

If the Transporter needs to reschedule an appointment, a code indicating the reason for rescheduling the appointment will be provided as part of the market message. This code will be chosen from a list of pre-defined options.

Code Description

OPRE Operational Reason

ESAR Service Alteration Required

ENGS No Gas in Service

ENSR New Service Required

UNRI Appointment Re-scheduled due to use of Non Registered Installer

ANRI Appointment Re-scheduled due to change of Installer ID Details

Please note the following;

ENSR will be used by the Transporter when a service doesn’t comply with standards.

ENGS will be used by the Transporter when it is discovered that there is no gas in the service e.g. an old service may not have been transferred over onto a renewed main at the time of the renewal because the property wasn't using gas.



144

5.2 S1502RQ – Site Works Appointment Re-Scheduling Request




Description: Shippers will use this message when they wish to re-schedule an appointment that has been confirmed by the Transporter previously via S1603A – Site Works Acceptance Market Message as part of MPD16 – Creation and Completion of Operational Site Works Requests Market Process.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must be registered to the Shipper.

[GNRS] A valid Shipper ID and Supplier ID combination


[SSDS]

Site Works Appointment Request



M 12 Char

If the Shipper wishes to reschedule an appointment, the GNI Systems reference number for the original Site Works request must be quoted in the Appointment Rescheduling Request, so the Transporter knows which appointment is to be rescheduled.

Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That the entered value has 7 characters.


145

Segment


Please note the following;

Shippers will be able to submit a re-scheduling request for Site Works Requests. S1603A – Site Works Acceptance Market Message will include the “Site Works Reference” that must be quoted back in this data field for re-scheduling of the relevant Site Works activity.

Shippers will be able to submit a re-scheduling request for Registration Requests. G603N – Registration Provisional Acceptance Market Message will include the “Site Works Reference” that must be quoted back in this data field for re-scheduling of the registration related Site Works activity.

The following validation will be applied to this data field by GNI Systems; Original Site Works Request Reference must be

generated previously by S1601RQ or G601RQ. [OSRD]

Original Site Works Reference Number must have been set aside for the Shipper. [OSRN]

Original Site Works Request must have been set aside for the GPRN. [OSRS]

Site Works request completion messages must not have been sent in advance of re-scheduling request market message being received. [SCCR]


M 10 Char

A unique reference number for each appointment slot. Shippers must acquire an Appointment Reservation ID from the “Real-time” Gas Shipper Self-Service Component in advance of submitting re-scheduling request for certain types of Site Works Request Types as outlined below.








The following validation will be applied to this data field by GNI Systems; Re-scheduling request should comply with the

rescheduling rules (i.e. Appointments can not be re-scheduled after 13:00 one day before the actual appointment date). [SCRT]

Market Message will fail validation if this data field value is provided for a Site Works Request Type that does not require an appointment. [NARS]

Site Works Appointment Reservation ID must have been reserved via “Real-time” Gas Shipper Self-Service Component. [IAID]


Site Works Appointment Reservation ID must have been set aside for the Shipper. [ANSS]

Site Works Appointment Reservation ID must have been set aside for the GPRN. [ANSG]

Site Works Appointment Reservation ID must have been set aside for the Site Works request type. [ANRT]

Site Works Appointment Reservation ID must not have been set aside for another Site Works Request. [ASAS]

Site Works can only be rescheduled if there is


146

Segment


no Pending CoS. [SCRP]


147

5.3 S1503RJ – Site Works Re-Scheduling Request Rejection




Description: The Transporter will send this message to Shippers if the S1502RQ – Site Works Appointment Re-Scheduling Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the S1502RQ – Site Works Appointment Re-Scheduling Request Market Message.



Segment




Site Works Appointment Rejection Reason


S1503 Rejection Code [s1503RejectionCode]

M 4 List


Code Description



GNRS GPRN not registered to Shipper

ISSC Invalid Shipper/Supplier ID Combination

SSDS Shipper Status does not support this request type

OSRD Original Site Works Request Number does not exist



148

Segment


OSRN Original Site Works Request not set aside for this Shipper

OSRS Original Site Works Request not set aside for this GPRN

SCCR Site Works Already Completed Cannot Reschedule

SCRT Site Works Cannot be Rescheduled because of Time Constraints

NARS No Appointment required for this Type of Site Works Activity

IAID Appointment Reservation ID does not exist

RSDW Reserved Appointment Date must be within 30 days from now

ANSS Appointment Reservation ID not set aside for Shipper

ANSG Appointment Reservation ID not set aside for GPRN

ANRT Appointment Reservation ID not set aside for this Site Works request type

ASAS Appointment Reservation ID already in use

SCRP Site Works Cannot be Rescheduled because of Pending CoS


149

5.4 S1504A- Site Works Re-Scheduling Request Acceptance




Description: The Transporter will send this message to Shippers if the S1502RQ – Appointment Re-Scheduling Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that the request to re-schedule the appointment has been accepted.



Segment





Site Works Appointment Completion



M 12 Char A unique reference number for the original Site Works request that is re-scheduled as per the Shipper’s S1502RQ market message.

GNIGNI Systems will validate the information before sending the market message to the Shipper.


M 10 Char

A unique reference number for each appointment slot. The information provided in this data field is the new appointment details for the re-scheduled site works request. Transporter will provide an Appointment Reservation ID for the rescheduling of the following site works request types;








150

Segment




M 10 Date

The date on which a scheduled appointment is due. This will be determined by the Appointment ID. This is defined with the following XML format:

YYYY-MM-DD



M 11 Char

The time at which a scheduled appointment is due (time from, time to). This will be determined by the Appointment ID. This is defined with the GMT offset in the following format:

hh:mm-hh:mm



151

5.5 S1601RQ - Site Works Request


MPD Reference: MPD16 – Creation and Completion of Operational Site Works Request for NDM Sites


Description: Shippers will use this message when they wish to raise a request for an Operational Site Works Activity to be carried out.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must be registered to Shipper sending

message. [GNRS] Shipper status must support the request type.

[SSDS] A valid Shipper ID and Supplier ID combination

must be provided. [ISSC]

Site Works Request M Segment Please see data field level instructions below.

Site Works Type Code [swTypeCode]

M 3 List

These Codes for Site Works activities should only be used when the Gas Point is registered to the Shipper. Site Works Request Type identifying the type of Site Works Activity must be one of the following available codes;


UNL Unlock Meter RPR Repair Riser Cover

DCT Disconnect INV Investigation


The following validation will be applied to this data field by GNI Systems; Gas Point Status must be appropriate for the

requested Site Works type. [MPSA] Gas Service Status must be appropriate for the


152

Segment


NGS No Gas RPM Repair Meter Box

LCK Lock Meter SPR Special Read

EXC Exchange Meter TSP Test Service Pipe

TEM Test Meter NOH Notice of Hazard

RBK Request Meter Box Key SDC Street Disconnect

requested Site Works type. [GPSA] There must not be a similar Site Works activity

outstanding - except the “NGS - No Gas” request type. [SSWO]

Site Works Activity must be appropriate for the vulnerable customer type. [SWNA]

Site Works Reason Code [swReasonCode]

D 2 List

Site Works Reason Code identifying the particular sub-category of Site Works Activity must be one of the following available codes based on the provided Site Works Request Type. If Site Works Request Type Code is selected as UNL – Unlock Meter;

Code Description

UE Service Unlock

UL Shipper Unlock

If Site Works Request Type Code is selected as LCK – Lock;

Code Description

SE Service Lock

SL Shipper Lock (Standard)

SX Shipper Lock (No Contract)

If Site Works Request Type Code is selected as EXC – Exchange Meter;

Code Description Meaning

IL Increased Load/Decreased Load

Shipper wants to exchange the meter due to Increased or DescreasedLoad. Relevant details for meter exchange (requested meter size etc.) should be described in Job Remarks/Access data fields.

TC To Credit Meter Shipper wants to replace a prepayment meter with a credit meter

TP To PPM Shipper wants to replace a credit meter with a prepayment meter

Leave Blank Shipper wants to exchange the meter with a new one. Meter type and size will not be changed.

Gas Shipper Communication Component will validate the data in this field to ensure: That is one of the available codes.

The following validation will be applied to this data field by GNI Systems; Provided value must be one of the valid

combination for Site Works Activity Type and Site Works Request Reason Code. [IARC]

Shipper must have an agreement with the PPMSP before requesting an exchange to a PPM. [SDHA]

Site Works are only allowed when GPRN is not pending CoS unless it’s a Shipper Lock [SWCS]


153

Segment


Note: If this option is used and the End User currently has a legacy prepayment meter, it will automatically be replaced with a new PPM

If Site Works Request Type Code is selected as NGS – No Gas;

Code Description Meaning

LP Low Pressure Shipper wants to raise a No Gas job with “Low Pressure” additional detail.

Leave Blank Shipper wants to raise a No Gas job only.

If another Site Works Request Type Code is selected different than LCK, UNL, EXC and NGS, then the Site Works Reason Code data field should be left blank.

End User Financial Hardship Flag [euFinancialHardshipFlag]

D 1 List

This field is used toindicate that a Prepayment Meter is to be fitted (as part of an exchange) due to the fact that the End User is suffering financial hardship. This field is dependent on the ‘Site Works Reason Code’ field above. If “To PPM” Site Works Reason Code is selected, then this data field is mandatory and must be one of the following available codes:

Code Description

Y Yes (Financial Hardship)

N No

If any other Site Works Reason Code is selected, then this data field should be left blank.


The following validation will be applied to this data field by GNI Systems; A value must be provided if PPM Meter is

chosen. [FHMB] No value should be provided unless PPM Meter

is chosen [FHOA]

Site Works Remarks D Segment Please see data field level instructions below.

Site Works Information [swInformation]

D 250 Char

Free text area for any additional job information or access information that a Shipper should include as part of a Site Works Creation Request. This segment is defined as a repeated segment with a maximum of 5 repeating elements and at least the first element in this segment should be populated. This field is mandatory for most of the Site Works Request Type Codes except NOH – Notice of Hazard.

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the entered text must be up to a maximum

of 250 characters. The following validation will be applied to this data field by GNI Systems;


154

Segment


Job Remarks/Access Information must be provided – Market Message will fail validation if the provided value for “Site Works Request Type” data filed is not “NOH – Notice of Hazard” and no text is provided in this field. [JRAI]

Site Works Contact M Segment Please see data field level instructions below.


M 50 Char Name of the person who should be contacted if more information is required in relation to a Site Works Activity.


characters. There is no individual business logic validation for this field.


M 15 Char

Contact phone number for the person who should be contacted if more information is required in relation to a Site Works Activity.


digits. There is no individual business logic validation for this field.


O 15 Char

Secondary contact phone number for the person who should be contacted if more information is required in relation to a Site Works Activity.



Site Works Appointment D Segment Please see data field level instructions below.


D 10 Char

A unique reference number for each appointment slot. Shippers must acquire an Appointment ID from the “Real-time” Gas Shipper Self-Service Component in advance of submitting certain types of Site Works Creation Requests (i.e. those that require an appointment shown with * below), and when rescheduling an appointment.


UNL* Unlock Meter RPR Repair Riser Cover

DCT** Disconnect INV* Investigation

NGS No Gas RPM Repair Meter Box

LCK* Lock Meter SPR* Special Read

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That the entered value has 6 digits.

The following validation will be applied to this data field by GNI Systems; Market Message will fail validation if this data

field value is not provided for a Site Works Request Type that requires an appointment. [SRAI]

Market Message will also fail validation if this


155

Segment


EXC** Exchange Meter TSP* Test Service Pipe

TEM* Test Meter NOH Notice of Hazard

RBK Request Meter Box Key

** Note that Exchange Meter jobs for Increased Load (EXC/IL) do not require an appointment as they require manual investigation to determine the type of meter required. This activity is for I/C GPRNs only and can not be used for residential End Users. Normal Exchange Meter jobs do require an appointment. Also, appointments are not required for Disconnect jobs (DCT) on large I/C GPRNs and should not be provided. This is because special arrangments need to be made before carrying out Disconnect jobs on large I/C sites. The Extranet will not return appointment IDs for Disconnect jobs on large I/C GPRNs.

data field value is provided for a Site Works Request Type that does not require an appointment. [NARS]

Appointment Reservation ID must have been reserved via “Real-time” Gas Shipper Self-Service Component. [IAID]

Appointment Reservation ID must have been set aside for the Shipper. [ANSS]

Appointment Reservation ID must have been set aside for the GPRN. [ANSG]

Appointment Reservation ID must have been set aside for the Site Works request type. [ANRT]

Appointment Reservation ID must not have been already set aside for another Site Works Request. [ASAS]



156

5.6 S1602RJ – Site Works Rejection




Description: The Transporter will send this message to Shippers if the S1601RQ – Site Works Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the S1601RQ – Site Works Request Market Message.



Segment




Site Works Rejection Reason M Segment Please see data field level instructions below.


M 4 List


Code Description






MPSA Gas Point Status is not appropriate for this Site Works type



157

Segment


GPSA Gas Service Status is not appropriate for this Site Works type

SSWO Similar Site Works activity outstanding.

SWNA Site Works Activity not appropriate for vulnerable customer

IARC Invalid Combination of Site Works Activity Type and Reason Code

JRAI Job Remarks/Access Information should be provided for this Site Works Activity

SRAI Site Works Activity Requires Appointment

NARS Appointment Not Required for Site Works Activity

IAID Appointment Reservation ID does not exist

ANSS Appointment Reservation ID not set aside for this Shipper

ANSG Appointment Reservation ID not set aside for this GPRN

ANRT Appointment Reservation ID not set aside for this Site Works request type

ASAS Appointment Reservation ID already set aside for another Site Works Request

RSDW Reserved Appointment Date must be within 30 days from now.


FHOA Financial Hardship only applies to Prepayment Meters

FHMB Financial Hardship indicator must be poplulated for PPM Meters

SWCS Site Works not allowed due to Pending CoS

SWNV Site workls not valid for this gas point


158

5.7 S1603A- Site Works Acceptance




Description: The Transporter will send this message to Shippers if the S1601RQ - Site Works Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that their request has been accepted and will be processed by the Transporter.



Segment





Site Works Acceptance M Segment Please see data field level instructions below.


M 12 Char

A unique reference number that will be assigned to the Site Works Request by the GNI Systems and will be quoted back to the Shipper when the Site Works Activity was accepted. This is the same reference number that Shippers should use if applicable in the following market messages;

If the Shipper wishes to cancel the site works request, then S1701RQ – Site Works Cancellation Request Market Message should be submitted using this reference number.

If the Shipper wishes to re-schedule the site works request, then S1502RQ – Appointment Re-Scheduling Request Market Message should be submitted using this reference number.


Site Works Appointment ID

O 10 Char A unique reference number for each appointment slot. Transporter will quote back the Appointment ID provided by the Shipper as part of



159

Segment


[swAppointmentID] S1601RQ - Site Works Request Market Message for information purposes only. This field will be populated with a value for the following site works request types;







D 10 Date


YYYY-MM-DD



D 11 Char


hh:mm-hh:mm



160

5.8 S1604N- Site Works Completion Notification




Description: The Transporter will send this message to Shippers when the Site Works Activity outlined in the S1601RQ - Site Works Request Market Message submitted by the Shipper has been completed. This message signifies the end of the process.



Segment




Gas Point Address M Segment Please refer to Section 2.2 for Shipper Header Common Data Segment.


Site Works Completion M Segment Please see data field level instructions below.

Site Works Completion Code [swCompletionCode]

M 3 List

Code identifying the status of the completed Site Works Activity. One of the following codes will be provided to the Shipper in this data field to indicate completion status of the site works request.

Code Description

CPD Completed

SHC Shipper Cancelled – No Charge

SCC Shipper Cancelled – Charge Applies

WNR Work Not Required – No Charge

WNC Work Not Required – Site Attendance Charge Applies

SNR Action Required - Site was not Ready



161

Segment


USL Action Required - Safety Locked - Leak

UFI Action Required - Flue Inadequate

UFS Action Required - Failed Soundness Test

ULA Action Required - Location of Appliances

UIV Action Required - Inadequate Ventilation

UPI Action Required - Pipe work Incomplete

UWP Action Required - Water in Internal Pipe work

ASR Action Required - Shipper must create an additional Site Works request.

NOC Action Required - No Cert

NOF Action Required - No Access – House can not be found

NOP Action Required - No Access - Site Works Contact Phone Number is not working/reachable

NOR Action Required - No Access - Not requested by this End User

NOM Action Required - No Access - Meter is not accessible

USS Action Required – Leak on Supply

CPS Completed, Meter is Safety Locked

MMM Action Required – Meter Mix-up issue discovered

MRM Action Required – Meter Previously Removed

MNC Work Not Required – Site Attendance Charge Applies - No Reads Available

MNR Work Not Required – No Charge - No Reads Available

IVC Action Required - Invalid Cert

AVC Action Required - Vulnerable Customer at premises

ICR Incomplete (Customer Refused.)

ILR Incomplete (License Refused. )

IMR Incomplete (meter disconnection requested instead.)

IMU Incomplete (Multiple end users.)

ISI Incomplete (Service inaccessible.)


162

Segment


CMN Complete (Locked, no answer from shipper.)

LMC Complete (Locked, after call from shipper.)

MCC Complete (Locked, customer agreed.)

NHC Complete (Locked, no one home.)

PVC Complete (Locked, premise was vacant.)

TML Complete (Locked, call refused.)

VPL Complete (Locked, premise was vacant.)

IAR Incomplete (Access refused.)

IER Incomplete (Exchange not required.)

ISA Incomplete (No answer from shipper.)

ISR Incomplete (Survey required.)

LNC Incomplete (PPM exchange requested instead)

MAC Incomplete (Meter already locked.)

NLC Incomplete (After call to shipper.)

NMO Incomplete (No meter on site.)

PVN Incomplete (Premise vacant, no access.)

TNL Incomplete (Call refused.)

VPN Incomplete (Vacant premise, no access.)

Site Works Completion Comment [swCompletionComment]

M 50 Char The description of the Site Works Job Completion Code as provided in the previous data field.




M 40 Char The physical location of the Meter at the Gas Point Address GNI Systems will validate the information before sending the market message to the Shipper.

Site Works Invoice M Segment Please see data field level instructions below.

Site Works Invoice Amount (Euro) [swInvoiceAmount]

M 10 Decimal (2)

The amount payable (where applicable) by the Shipper for a Site Works Activity.



Please refer to Section 2.6 for Meter Read Common Data Segment. This segment is dependent on the ‘Site Works Completion Status Code’. Meter Read Information will onlu be provided if no further action is required to complete the Site Works Request. This segment will only be populated if the ‘Site Works Completion Status Code’ is one of the following: CPD, CPS, WNC, WNR.


163

Segment



Please refer to Section 2.6 for Meter Read Common Data Segment. Please note that this segment is dependent and will be populated if the original Site Works request is EXC – Exchange Meter. This segment is for the new meter’s meter read information.


164

5.9 S1701RQ – Site Works Cancellation Request


MPD Reference: MPD17 – Cancellation of Site Works Market Process


Description: Shippers will use this message when they wish to cancel a Site Works Request that has been confirmed by the Transporter previously via S1603A – Site Works Request Acceptance Market Message as part of MPD16 – Creation and Completion of Operational Site Works Requests Market Process.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must be registered to the Shipper.

[GNRS] A valid Shipper ID and Supplier ID combination


SSDS]

Site Works Cancellation Request



M 12 Char

If the Shipper wishes to cancel a site works request, the GNI Systems reference number for the original Site Works request must be quoted in the Cancellation Request, so the Transporter knows which site works job is to be cancelled. Please note the following;


The following validation will be applied to this data


165

Segment


Shippers will be able to submit a cancellation request for Site Works Requests. S1603A – Site Works Acceptance Market Message includes the “Site Works Reference” that must be quoted back in this data field for cancelling the relevant Site Works activity.

Shippers must submit G605RQ – Registration Cancellation Request Market Message, if they wish to cancel a Registration Request. Please refer to Section 3.39 for G605RQ – Registration Cancellation Request Market Message.

field by GNI Systems; Original Site Works Request Reference must be

generated previously by S1601RQ. [ISRN] Site Works Reference Number must have been

set aside for the Shipper. [SRBS] Original Site Works Request must have been

set aside for the GPRN. [SRBG] Cancellation request should comply with the

Cancellation rules (i.e. Site Works requests can not be cancelled via market messaging after 13:00 one day before the actual appointment date). [SWAC]

Site Works request completion messages must not have been sent in advance of cancellation request market message being received. [SCCT]

Site Works Request must not have already been cancelled. [SWPC]


166

5.10 S1702RJ – Site Works Cancellation Request Rejection




Description: The Transporter will send this message to Shippers if the S1701RQ – Site Works Cancellation Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the S1701RQ – Site Works Cancellation Request Market Message, if applicable.



Segment




Site Works Cancellation Rejection



M 4 List


Code Description




ISSC Invalid Shipper ID/Supplier ID Combination


ISRN Site Works Reference Number does not exist



167

Segment


SRBS Site Works Reference Number belongs to another Shipper

SRBG Site Works Reference Number belongs to another GPRN

SWAC Site Works Already Completed Cannot Cancel

SCCT Site Works cannot be cancelled because of time constraints

SWPC Site Works Previously Cancelled


168

5.11 S1703A- Site Works Cancellation Acceptance




Description: The Transporter will send this message to Shippers if the S1701RQ – Site Works Cancellation Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that their request has passed validation and will be processed by the Transporter.



Segment





Site Works Cancellation Completion



M 12 Char A unique reference number for the original Site Works request that is cancelled as per the Shipper’s S1701RQ market message.



O 10 Char

A unique reference number for each appointment slot. The information provided in this data field belongs to the cancelled site works request and it is provided to the Shipper for information purposes only. Transporter will provide the Appointment ID for the cancelled site works request for the following site works request types;







169

Segment



Please note that if site works request type does not require an appointment, then this field will be left blank for the cancelled site works request.


O 10 Date

The date on which the cancelled appointment was due. This will be determined by the Appointment Reservation ID. This is defined with the following XML format:

YYYY-MM-DD



O 11 Char

The time at which the cancelled appointment was due (time from, time to). This will be determined by the Appointment Reservation ID. This is defined with the GMT offset in the following format:

hh:mm-hh:mm



170

5.12 S1901RQ - Site Works Complaint Request


MPD Reference: MPD19 – Management of Site Works Complaints Market Process


Description: Shippers will use this message when they wish to submit a Site Works-related complaint.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. [NNDG] GPRN must be registered to Shipper sending

message. [GNRS] A valid Shipper ID and Supplier ID combination


[SSDS]

Site Works Complaint Request



O 12 Char

The reference number of the original Site Works Activity to which a complaint relates. This is the number that will have been assigned to the original Site Works Request by the GNI Systems as per the receipt of a valid S1601RQ and will have been quoted back to the Shipper when the Site Works Activity was Accepted and Completed. Please note that this data field is optional, therefore Shippers will also

If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That the entered value has 7 digits.

If any value provided, the following validation will be


171

Segment


be able to submit a complaint request without any “Site Works Reference” for non-site works activity specific complaints.

applied to this data field by GNI Systems; Original Site Works Request Reference must be

generated previously by S1601RQ. [OSNE] Original Site Works Reference Number must

have been set aside for the Shipper. [ONSS] Original Site Works Request must have been

set aside for the GPRN. [ONSG]

Site Works Complaint Type Code [swComplaintTypeCode]

M 4 List

Code indicating the category of the site works related complaint. The one of the following available complaint category codes will be provided as appropriate.

Code Description

0001 Bad Pressure

0002 Blocked Access

0003 Broken Appointment

0004 Broken Appointment Fitter

0005 Collect Barriers/Equipment

0006 Customer Unhappy about Lay Service Charge

0007 Cutting in Dangerous Condition

0008 Damage to Property by BGE

0009 Delay Completing Reinstatement

0010 Delay Completing Gas Work

0011 Delay in Upgrading Work

0012 Delay Installing Service

0013 Delay Restoring Gas/Leak

0014 Delay Restoring Gas/Renewals

0015 Lack of Notice Renewals

0016 Limited Appointment Facility

0017 Meter Mix Up

0018 Meter Position

0019 Miscellaneous Complaint

0020 No Gas Customer Complaint

0021 Noise/Inconvenience

0022 Problem - Gas Card Meter

0023 Quality of Gas Work




172

Segment


0024 Quality Permanent Reinstatement

0025 Quality Temporary Reinstatement

0026 Service Quality Bord Gais

0027 Site in Poor Condition

0028 Siteworks Charges

0029 Spoil to be removed

0030 Technical Query/Complaint

0031 Traffic Restrictions

0032 Upgrading Work Unsightly

0033 Delay in Issuing Quotations

0034 Wayleave/Licence held

0035 Payment/Const not started

Site Works Complaint Remarks

M Segment

Site Works Complaint Information [swComplaintInformation]

M 50 Char

Mandatory free text area allowing the Shipper to enter some remarks in relation to the complaint. This segment is defined as a repeated segment with a maximum of 5 datafields and at least the first text line datafield in this segment must be populated. Please note that Complaint Remarks will be quoted back to the Shipper when the Transporter sends the Complaint Receipt Notification.

Gas Shipper Communication Component will validate the data in this field to ensure: That the value is provided. That the format is correct – not longer than 50

characters.


Site Works Complaint Contact M Segment Please see data field level instructions below.


M 50 Char Name of the person who should be contacted if more information is required in relation to the relevant Site Works Complaint.




M 15 Char Contact phone number for the person who should be contacted if more information is required in relation to the relevant Site Works Complaint.


digits. There is no individual business logic validation for


173

Segment


this field.


O 15 Char Secondary contact phone number for the person who should be contacted if more information is required in relation to a Site Works Activity.




174

5.13 S1902RJ - Site Works Complaint Rejection




Description: The Transporter will send this message to Shippers if the S1901RQ - Site Works Complaint Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the S1901RQ - Site Works Complaint Request.



Segment




Site Works Complaint Rejection



D 12 Char

If any value provided in the relevant data field of the S1901RQ Market Message, the reference number of the original Site Works Activity to which a complaint relates will be provided here. Please note that this data field is dependent to the “Site Works Reference” data field in S1901RQ Market Message.


Site Works Complaint Rejection Reason



M 4 List

Code indicating the category of the site works related complaint as provided by the Shipper in S1901RQ Market Message. The one of the following available complaint category codes will be provided.

Code Description

0001 Bad Pressure

0002 Blocked Access



175

Segment
















0017 Meter Mix Up

0018 Meter Position


















176

Segment



Site Works Complaint Rejection Reason



M 4 List


Code Description






OSNE Original Site Works Reference Number does not exist

ONSS Original Site Works Reference Number not set aside for this Shipper

ONSG Original Site Works Reference Number not set aside for this GPRN



177

5.14 S1903A- Site Works Complaint Acceptance




Description: The Transporter will send this message to Shippers if the S1901RQ - Site Works Complaint Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that the complaint has been accepted by the Transporter and will be processed.



Segment





Site Works Complaint Acceptance


Site Works Complaint Reference [swComplaintRef]

M 7 Char The unique reference number generated by GNI Systems for a site works complaint logged by the Shipper.



O 12 Char

The reference number of the original Site Works Activity to which a complaint relates. This is the number that will have been assigned to the original Site Works Request by the GNI Systems as per the receipt of a valid S1601RQ and will have been quoted back to the Shipper when the Site Works Activity was Accepted and Completed. Please note that this data field is dependent on the “Original Site Works Reference Number for Relevant Complaint” in S1901RQ Market Message since the Shippers are able to submit a complaint request without providing “Site Works Reference” for non-site works activity specific complaints.


Site Works Complaint M 4 List Code indicating the category of the site works related complaint as GNI Systems will validate the information before


178

Segment


Type Code [swComplaintTypeCode]

provided by the Shipper in S1901RQ Market Message. The one of the following available complaint category codes will be provided.

Code Description

0001 Bad Pressure

0002 Blocked Access















0017 Meter Mix Up

0018 Meter Position












sending the market message to the Shipper.


179

Segment









180

5.15 S1904N- Site Works Complaint Acceptance Notification




Description: The Transporter will send this message to Shippers if a complaint received by the Transporter from an End User relates to a Site Works Activity requested by the Shipper previously. This message is intended to notify the Shipper that a complaint concerning work requested by that Shipper previously has been received by the Transporter and will be processed.



Segment




Site Works Complaint Notification



M 7 Char The unique reference number generated by GNI Systems for a site works complaint logged by the End User.



M 12 Char

The reference number of the original Site Works Activity to which a complaint relates. This is the number that will have been assigned to the original Site Works Request by the GNI Systems as per the receipt of a valid S1601RQ and will have been quoted back to the Shipper when the Site Works Activity was Accepted and Completed. The End User can call the Transporter’s Call Centre to log complaints directly. If the complaint is related with a Site Works request that was previously initiated by the Shipper, the Shipper will be informed about the End User’s complaint and the resolution details. Please note that the value in this data field will be captured by the Transporter as per the receipt of the End User complaint.



181

Segment



M 4 List


Code Description

0001 Bad Pressure

0002 Blocked Access















0017 Meter Mix Up

0018 Meter Position













182

Segment










183

5.16 S1905N- Site Works Complaint Completion Notification




Description: The Transporter will send this message to Shippers when a complaint has been resolved, regardless of whether the complaint originated from the Shipper through a S1901RQ - Site Works Complaint Request Market Message or came directly to the Transporter from an End User and relates to a Site Work requested by that Shipper previously. This message is intended to notify the Shipper that the complaint has been resolved and signifies the end of the process.



Segment




Site Works Complaint Completion



M 7 Char The unique reference number generated by GNI Systems for a site works complaint logged by the Shipper.



O 12 Char

The reference number of the original Site Works Activity to which a complaint relates. This is the number that will have been assigned to the original Site Works Request by the GNI Systems as per the receipt of a valid S1601RQ and will have been quoted back to the Shipper when the Site Works Activity was Accepted and Completed. Please note the following;

This data field is dependent on the “Site Works Reference” in S1901RQ Market Message since the Shippers are able to submit a complaint request without any “Site Works Reference” for non-site works activity specific complaints.

End User can call Transporter’s Call Centre to log complaints



184

Segment


directly. If the complaint is related with a Site Works request that was previously initiated by the Shipper, the Shipper will be informed about the End User’s complaint and the resolution details. Please note that the value in this data field will be captured by the Transporter as per the receipt of the End User complaint and will be sent to the Shipper as part of S1904N and S1905N market messages.


M 4 List


Code Description

0001 Bad Pressure

0002 Blocked Access















0017 Meter Mix Up

0018 Meter Position








185

Segment














Site Works Complaint Resolution Details [swComplaintResolutionDetails]

M 250 Char Mandatory free text area allowing the Transporter to enter some resolution remarks in relation to the complaint resolution.



186

5.17 S2301RQ –Gas Point Address Update Request


MPD Reference: MPD23 – Creation and Maintenance of Gas Point Address Market Process


Description: Shippers will use this message when they wish to request an update the Gas Point Address for a GPRN to which the Shipper is registered.



Segment




In addition to the validation listed in section 2.2, the following validation will be applied by GNI Systems: GPRN must exist on GNI Systems. [GDNE] GPRN must be that of an NDM site. NNDG] GPRN must be registered to the Shipper.

GNRS] A valid Shipper ID and Supplier ID combination


[SSDS]

Gas Point Address Update Request

O Segment Please see data field level instructions below.

Gas Point House/Unit No [gpHouseNo]

O 4 Integer Number of house or unit, if applicable, where Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


digits.


187

Segment



Gas Point House Letter [gpHouseLetter]

O 1 Char Letter of house, if applicable, where Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


character.


Gas Point House Name [gpHouseName]

O 25 Char Name of house or unit, if applicable, where Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


characters.


Gas Point Street Name [gpStreetName]

O 50 Char Name of street where Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


characters.


Gas Point Area Name [gpAreaName]

O 25 Char The area of a city/county in which a Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


characters.


Gas Point Town Name [gpTownName]

O 25 Char The town in which a Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.


characters.


Gas Point County Name [gpCountyName]

O 25 Char The county in which a Gas Point is located. This data field will be used by Shippers to propose a change on the Gas Point Address Information.

If any value provided, Gas Shipper Communication Component will validate the data in this field to


188

Segment


ensure: That the format is correct – not longer than 25

characters.


Gas Point Post Code [gpPostCode]

O 10 Char Post code for area where Gas Point is located (to be used when national post code system is introduced). This data field will be used by Shippers to propose a change on the Gas Point Address Information.


characters.


Meter Location O Segment Please see data field level instructions below.


O 40 Char The physical location of the Meter at the Gas Point Address.


characters.


Gas Point Address Update Reason


Gas Point Address Update Reason [gpAddressUpdateReason]

M 250 Char Mandatory free text area allowing the Shipper to enter an explanation for why the update to the Gas Point Address is required.

Gas Shipper Communication Component will validate the data in this field to ensure: That the value is provided. That the format is correct – not longer than 250



189

5.18 S2302RJ –Gas Point Address Update Rejection




Description: The Transporter will send this message to Shippers if the S2301RQ –Gas Point Address Update Request Market Message submitted by the Shipper fails validation. This message is intended to let the Shipper know the reason for the validation failure so that they can amend and resubmit the S2301RQ – Gas Point Address Update Request, if applicable. It may be the case that the Transporter has a valid reason for not processing the update, in which case this message signifies the end of the process.



Segment



BG Transporter Header M Segment Please refer to Section 2.3 for Bg Transporter Header Common Data Segment.

Gas Point Address Update Rejection


Gas Point Address Update Reason [gpAddressUpdateReason]

M 250 Char

Mandatory free text area allowing the Transporter the option of providing extra information about why an ‘Update Request for Maintenance of Gas Point Address’ market message was rejected.


Gas Point Address Update Rejection Reason



M 4 List

The one of the following available rejection reason codes will be provided as appropriate to identify the reason why a ‘Gas Point Address Update Request’ market message was rejected.

This segment is defined as a repeated segment with a maximum of 5 datafields. There will be at least one rejection code in this segment. If there are multiple reasons to fail validation, all appropriate rejection codes will be provided with up to 5 values from a list of pre-defined



190

Segment


codes identified below.

Code Description






GPAI Gas Point Address Details Incomplete

AUNR Address Details Update not required

ADCO Address Details Conflict with GNI Address

Please note that S2301RQ market message will be processed manually and detailed rational will be provided in Gas Point Address Update Request Rejection Rationale data fields of this market message.


191

5.19 S2303N- Gas Point Address Update Notification




Description: The Transporter will send this message to Shippers if the S2301RQ –Gas Point Address Update Request Market Message submitted by the Shipper passes validation. This message is intended to notify the Shipper that an update has been made to the Gas Point Address Details (either as a direct result of the S2301RQ – Gas Point Address Update Request Market Message submitted by the Shipper or because of direction received by the Transporter from a Local Authority).



Segment




Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Information Common Data Segment.



M 40 Char The physical location of the Meter at the Gas Point Address



192

6. Miscellaneous

This section outlines miscellaneous market messages that do not fall into any specific business area.

Miscellaneous Market Messages are:

H3001N End of Day Totals Notification


193

6.1 H3001N - End of Day Totals Notification


MPD Reference: Not applicable


Description: The Transporter will send this message to Shippers to notify the Shipper of the end of day totals for all market messages sent to that Shipper by the Transporter and received by the Transporter from that Shipper.



Segment



Time Period M Segment Please see data field level instructions below.

Start Time M 20 Time

The start time of the period that the End of Day Totals Notification message covers. This is a time and date stamp. This is defined with the GMT offset in the following format (this is the XML standard format):

CCYY-MM-DDThh:mm:ss


End Time M 20 Time

The end time of the period that the End of Day Totals Notification message covers. This is a time and date stamp. This is defined with the GMT offset in the following format (this is the XML standard format):

CCYY-MM-DDThh:mm:ss


Message Reconciliation Inbound



M 10 Char This defines the type of message to be sent by the Market Participant.


Market Message Type M 9 Integer Will indicate the total number of each of the market message types

received by the Transporter in the defined period.


194

Segment


Count [mmTypeCount]

Message Reconciliation Outbound



M 10 Char This defines the type of message to be sent by the Market Participant.


Market Message Type Count [mmTypeCount]

M 9 Integer Will indicate the total number of each of the market message types sent by the Transporter in the defined period.

new market message implementation guide · 2019. 3. 20. · market message implementation guide...

Documents