Market Message Implementation Guide v003.00.002
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 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) ............. 62 3.9 G206N – Change of Shipper Completion Notification (Outgoing Shipper) ............. 65 3.10 G207N – Change of Shipper Rejection Notification (Outgoing Shipper) ................ 65 3.11 G208RQ– Change of Shipper Cancellation NDM Request .................................... 69
Market Message Implementation Guide v003.00.002
3
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 .................................................. 113
4. NMD Market Messages ....................................................................... 115
4.1 M801RQ – Meter Read Request – NDM .............................................................. 116 4.2 M802RJ – Meter Read Rejection .......................................................................... 120 4.3 M803N – Meter Read Completion Notification – (Single Read) ........................... 123 4.4 M804N – Meter Read Completion Notification – (Double Read) .......................... 124 4.5 M901RQ – Meter Read Query Request ................................................................ 125 4.6 M902RJ – Meter Read Query Rejection ............................................................... 128 4.7 M903N – Meter Read Query Completion Notification ........................................... 130 4.8 M1101RQ – Estimated Read Request .................................................................. 131 4.9 M1102RJ – Estimated Read Rejection ................................................................. 133 4.10 M1103N – Estimated Read Completion Notification ............................................. 135 4.11 M1401N – Read Cycle Update Notification .......................................................... 136
5. Site Works Market Messages ............................................................ 137
5.1 S1501N - Site Works Appointment Re-Scheduling Notification ............................ 138 5.2 S1502RQ – Site Works Appointment Re-Scheduling Request ............................. 140
Market Message Implementation Guide v003.00.002
4
5.3 S1503RJ – Site Works Re-Scheduling Request Rejection ................................... 142 5.4 S1504A- Site Works Re-Scheduling Request Acceptance ................................... 144 5.5 S1601RQ - Site Works Request ........................................................................... 146 5.6 S1602RJ – Site Works Rejection .......................................................................... 151 5.7 S1603A- Site Works Acceptance .......................................................................... 153 5.8 S1604N- Site Works Completion Notification ....................................................... 155 5.9 S1701RQ – Site Works Cancellation Request ...................................................... 159 5.10 S1702RJ – Site Works Cancellation Request Rejection....................................... 161 5.11 S1703A- Site Works Cancellation Acceptance ..................................................... 163 5.12 S1901RQ - Site Works Complaint Request .......................................................... 165 5.13 S1902RJ - Site Works Complaint Rejection ......................................................... 169 5.14 S1903A- Site Works Complaint Acceptance ......................................................... 172 5.15 S1904N- Site Works Complaint Acceptance Notification ...................................... 175 5.16 S1905N- Site Works Complaint Completion Notification ...................................... 178 5.17 S2301RQ –Gas Point Address Update Request .................................................. 181 5.18 S2302RJ –Gas Point Address Update Rejection .................................................. 184 5.19 S2303N- Gas Point Address Update Notification.................................................. 186
6. Miscellaneous ..................................................................................... 187
6.1 H3001N - End of Day Totals Notification ............................................................... 188
Market Message Implementation Guide v003.00.002
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.
Market Message Implementation Guide v003.00.002
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
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
Market Message Implementation Guide v003.00.002
7
CR047 Add Meter Size to Market Messages
CR064 Identify priority customers
CR046 Request Street Disconnect on S1601 RQ Message
CR060 Sitework Closure Codes
CR063 Provision of Gas Meter Read Calendar
Market Message Implementation Guide v003.00.002
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.
Market Message Implementation Guide v003.00.002
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).
Market Message Implementation Guide v003.00.002
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.
Market Message Implementation Guide v003.00.002
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
- Transporter Header
- Gas Point Address
- End User Details
- Meter Read
- Gas Point Status
- Meter Details
- Read Cycle
Market Message Implementation Guide v003.00.002
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
Market Message Implementation Guide v003.00.002
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.
Market Message Implementation Guide v003.00.002
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
2.2.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 Validation
Shipper Header M Segment All data items in the Shipper Reference Segment must be populated to defined formats and lengths.
Market Message Implementation Guide v003.00.002
15
Structure Opt Ln Typ Composition Instructions Validation
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 TRANSPORTER 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.
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 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.
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 not
longer than 3 characters.
Market Message Implementation Guide v003.00.002
16
Structure Opt Ln Typ Composition Instructions Validation
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]
Market Message Implementation Guide v003.00.002
17
2.3 Transporter Header Segment
2.3.1 Description
This segment provides Gas Networks Ireland Transporter Reference details for the gas point to which the market message relates. The TRANSPORTER Reference Segment is sent by the Transporter to the registered Shippers as part of the following market messages:
Market Message Code Market Message Name Sender Receiver
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
G206N 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
G702N Deregistration Tariff Exemption Removal Notification Transporter Shipper
Market Message Implementation Guide v003.00.002
18
Market Message Code Market Message Name Sender Receiver
G703N Deregistration Completion 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 Updates to Read Cycle Information 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
2.3.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.
Market Message Implementation Guide v003.00.002
19
Structure Opt Ln Typ Composition Instructions Validation
Transporter Header M Segment All data items in the TRANSPORTER 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 TRANSPORTER 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 TRANSPORTER Reference Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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 TRANSPORTER Reference segment is primarily used in replies to the market message originally sent by the Shipper).
GNI Systems will validate the information before sending the market message to 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 TRANSPORTER Reference segment is primarily used in replies to the market message originally sent by the Shipper).
GNI Systems will validate the information before sending the market message to 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 TRANSPORTER Reference segment is primarily used in replies to the market message originally sent by the Shipper)
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G205N Change of Shipper Request Completion Notification Transporter Shipper
G404N End User Assignment Completion Notification Transporter Shipper
G603N Registration Request Provisional Acceptance Transporter Shipper
G604N Registration Completion Notification 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
2.4.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 Validation
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.
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.
Market Message Implementation Guide v003.00.002
21
Structure Opt Ln Typ Composition Instructions Validation
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.
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G101RQ Update End User Details Request Shipper Transporter
G103N Notification Message for Update End User Details Transporter Shipper
G201RQ Change of Shipper NDM Request Shipper Transporter
G401RQ End User Assignment Request Shipper Transporter
G403N End User Assignment Request Provisional Acceptance Transporter Shipper
G404N End User Assignment Completion Notification Transporter Shipper
G601RQ Registration Request Shipper Transporter
G604N Registration Completion Notification Transporter Shipper
2.5.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 Validation
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
Mrs Missus
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 one of the available codes.
Market Message Implementation Guide v003.00.002
23
Structure Opt Ln Typ Composition Instructions Validation
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
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 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 chosen in the ‘End User TypeCode’ field, then no value should be provided in this field.
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 greater
than 50 characters.
Market Message Implementation Guide v003.00.002
24
Structure Opt Ln Typ Composition Instructions Validation
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.
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 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 any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 50 characters.
The following validation will be applied to this data field by GNI Systems:
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:
That the format is correct – not greater than 35 characters.
End User Market Sector Code [euMarketSectorCode]
M 2 List The sector of the market that an End User belongs to. 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.
Market Message Implementation Guide v003.00.002
25
Structure Opt Ln Typ Composition Instructions Validation
Code Description
RD Residential
IC Industrial/Commercial
That the format is correct – that it is one of the available codes.
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.)
CONC Concrete and Cement
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 one of the available codes.
The following validation will be applied to this data field by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
26
Structure Opt Ln Typ Composition Instructions Validation
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
FINS Financial Services
Market Message Implementation Guide v003.00.002
27
Structure Opt Ln Typ Composition Instructions Validation
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
TKAW Take-Aways
Market Message Implementation Guide v003.00.002
28
Structure Opt Ln Typ Composition Instructions Validation
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
MEDC Medical Consultants (MDs)
Market Message Implementation Guide v003.00.002
29
Structure Opt Ln Typ Composition Instructions Validation
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
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 one of
the available codes.
The following validation will be applied to this data field by GNI Systems:
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 4 characters.
Market Message Implementation Guide v003.00.002
30
Structure Opt Ln Typ Composition Instructions Validation
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 11 characters.
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 4 characters.
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 11 characters.
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 4 characters.
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 11 characters.
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
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,
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
Market Message Implementation Guide v003.00.002
31
Structure Opt Ln Typ Composition Instructions Validation
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.
That the format is correct – not greater 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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – not greater than 11 characters.
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:
That the format is correct – not greater than 50 characters.
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:
That the format is correct – not greater than 25 characters.
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:
That the format is correct – not greater than 25 characters.
End User Contact Address (Line 2) [euContactAddress2]
O 25 Char Line 2 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:
That the format is correct – not greater than 25 characters.
End User Contact Address (Line 3) [euContactAddress3]
O 25 Char Line 3 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:
That the format is correct – not greater than 25 characters.
End User Contact Address (Line 4) [euContactAddress4]
O 25 Char Line 4 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:
That the format is correct – not greater than 25 characters.
End User Contact Address (Line 5) [euContactAddress5]
O 25 Char Line 5 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:
That the format is correct – not greater than 25 characters.
Market Message Implementation Guide v003.00.002
32
Structure Opt Ln Typ Composition Instructions Validation
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
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 one of the available codes.
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.
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 one of
the available codes.
The following validation will be applied to this data field by GNI Systems:
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
Market Message Implementation Guide v003.00.002
33
Structure Opt Ln Typ Composition Instructions Validation
Must be one of the following available codes:
Code Description
Y Yes
N No
That the format is correct – that it is one of 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
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.
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 any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
That the format is correct – that it is one of the available codes.
The following validation will be applied to this data field by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
34
Structure Opt Ln Typ Composition Instructions Validation
0003 Hearing impaired
0004 Elderly
0005 Speech Impaired
0006 Language Difficulty
0007 Learning Difficulty
0008 Mental Health
0009 Dexterity Impaired
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G205N CoS Request Completion Notification Transporter Shipper (Incoming)
G206N CoS Request Completion Notification Transporter Shipper (Outgoing)
G404N End User Assignment Completion Notification Transporter Shipper
G604N Registration Completion Notification Transporter Shipper
G702N Deregistration Tariff Exemption Removal Notification 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
M1103N Estimate Read Request Notification Transporter Shipper
S1604N Site Works Completion Transporter Shipper
2.6.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 Validation
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
36
Structure Opt Ln Typ Composition Instructions Validation
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
37
Structure Opt Ln Typ Composition Instructions Validation
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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)
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
38
Structure Opt Ln Typ Composition Instructions Validation
GP PPM - GasCard Read @ credit purchase
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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).
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
39
Structure Opt Ln Typ Composition Instructions Validation
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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).
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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).
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Gas Point Correction Factor
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
40
Structure Opt Ln Typ Composition Instructions Validation
[mrGasPointCorrectionFactor]
there is no on-site conversion device. Where there is an on-site volume corrector this value is set to 1.000.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
41
Structure Opt Ln Typ Composition Instructions Validation
B Band 2 23,500 Band 2
C Band 3 73,000 Band 3
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).
GNI Systems will validate the information before sending the market message to the Shipper.
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).
GNI Systems will validate the information before sending the market message to the Shipper.
[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.
GNI Systems will validate the information before sending the market message to the Shipper.
[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 10 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.”
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G205N CoS Request Completion Notification Transporter Shipper
G604N Registration Completion Notification Transporter Shipper
G702N Deregistration Tariff Exemption Removal Notification Transporter Shipper
M803N Meter Read Completion Notification – (Single Read) Transporter Shipper
M804N Meter Read Information Notification – NDM – Generic/Volume Corrected (Double Read Segment)
Transporter Shipper
S1604N Site Works Completion Transporter Shipper
2.7.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 Validation
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
DD Disconnected
SL Shipper Lock
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
43
Structure Opt Ln Typ Composition Instructions Validation
SA Safety Lock
SE Service Lock
LN 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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G201RQ Change of Shipper NDM Request Shipper Transporter
G401RQ End User Assignment Request Shipper Transporter
G403N End User Assignment Request Provisional Acceptance Transporter Shipper
2.8.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 Validation
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. 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:
Gas Shipper Communication Component will validate the data in this field to ensure:
That a value has been provided. That it is one of the available codes.
Market Message Implementation Guide v003.00.002
45
Structure Opt Ln Typ Composition Instructions Validation
[meVolumeCorrectorFlag]
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).
The following validation will be applied to this data field by GNI Systems:
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]
Meter Read Volume Index [mrVolumeIndex]
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.
Gas Shipper Communication Component will validate the data in this field to ensure:
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 GNI Metering [RFRV]
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 ‘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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
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:
If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [MHNG]
Market Message Implementation Guide v003.00.002
46
Structure Opt Ln Typ Composition Instructions Validation
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]
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 ‘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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
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:
If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [UING]
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]
Meter Read Taken Date [mrTakenDate]
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.
Gas Shipper Communication Component will validate the data in this field to ensure:
That a value has been provided. That the format is correct – YYYY-MM-DD
– and is not less or greater than 10 characters.
The following validation will be applied to this data field by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
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:
Market Message Code Market Message Name Sender Receiver
G205N Change of Shipper Request Completion Notification Transporter Shipper
G404N End User Assignment Request Completion Notification Transporter Shipper
G604N Registration Completion Notification Transporter Shipper
M1401 Updates to Read Cycle Information Notification Transporter Shipper
Market Message Implementation Guide v003.00.002
48
2.9.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 Validation
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
[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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
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
G303N Historical Consumption Data
Market Message Implementation Guide v003.00.002
50
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
Market Message Implementation Guide v003.00.002
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 exist on GNI Systems. [GDNE]
GPRN must be that of an NDM site. [NNDG]
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.
In addition to the validation listed in section 2.5, the following validation will be applied by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
52
3.2 G102RJ – Update Existing End User Details Rejection
3.2.1 Purpose/Description
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.
3.2.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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
NNDG Not an NDM GPRN
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
53
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
Market Message Implementation Guide v003.00.002
54
3.3 G103N – Update Existing End User Details Completion Notification
3.3.1 Purpose/Description
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 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.
3.3.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
End User Details M Segment Please refer to Section 2.5 for End User Details Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
55
3.4 G201RQ – Change of Shipper NDM Request
3.4.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Initiator: Shipper Recipient: Transporter
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.
3.4.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 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]
At least 20 business days must have elapsed since previous Change of Shipper for this GPRN. [LTTD]
Market Message Implementation Guide v003.00.002
56
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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]
Market Message Implementation Guide v003.00.002
57
3.5 G202RJ – Change of Shipper Rejection
3.5.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Initiator: Transporter Recipient: Shipper
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.
3.5.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Change of Shipper Rejection Reason
M Segment Please see data field level instructions below.
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GARS GPRN already registered to requesting Shipper
GDNM GPRN does not match Meter Number
GDNS GPRN does not support CoS request
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
58
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
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’
OVCT At least one Vulnerable Customer Type must be provided if Vulnerable Customer 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’
DEUF End User First Name must be provided if End User Indicator is ‘Domestic’
Market Message Implementation Guide v003.00.002
59
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
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.
Market Message Implementation Guide v003.00.002
60
3.6 G203N – Change of Shipper Receipt Notification (Incoming Shipper)
3.6.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
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.
3.6.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Vulnerable Customer O Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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 TRANSPORTER 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 Shipper cancellation process (G208RQ). It is also a useful reference if the
GNI Systems will validate the information before sending the market message to the Incoming Shipper.
Market Message Implementation Guide v003.00.002
61
Segment Opt Ln Typ Composition Instructions Validation
Data Field
Shipper wishes to initiate the Change of Shipper Correction / Amendment process later.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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 GNI 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 GNI system or a read was received on G201RQ and was not valid or no read was received with the G201RQ message)
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
62
3.7 G204N – Change of Shipper Receipt Notification (Outgoing Shipper)
3.7.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
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.
3.7.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
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 is a unique identifier for the Change of Shipper process. The number for this message will be the same as the TRANSPORTER Reference Systems number.
The Change of Shipper ID will 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 Incoming Shipper.
3.8 G205N – Change of Shipper Completion Notification (Incoming Shipper)
3.8.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Market Message Implementation Guide v003.00.002
63
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 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.
3.8.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
COS Incoming Completion M Segment Please see data field level instructions below.
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 TRANSPORTER Reference Systems number.
The Change of Shipper ID is 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 Incoming Shipper.
Vulnerable Customer O Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read M Segment Please refer to Section 2.6 for Meter Read Common Data Segment.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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.
Market Message Implementation Guide v003.00.002
65
3.9 G206N – Change of Shipper Completion Notification (Outgoing Shipper)
3.9.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
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 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.
3.9.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
COS Outgoing Completion M Segment Please see data field level instructions below.
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 TRANSPORTER Reference Systems number.
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.
3.10 G207N – Change of Shipper Rejection Notification (Outgoing Shipper)
3.10.1 Purpose/Description
Market Message Implementation Guide v003.00.002
66
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
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 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.
.
3.10.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Change of Shipper Rejection Notification
M Segment Please see data field level instructions below.
Change of Shipper ID [cosID]
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 TRANSPORTER Reference Systems number.
GNI Systems will validate the information before sending the market message to the Incoming Shipper.
G207 Rejection Code [g207RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GARS GPRN already registered to requesting Shipper
GDNM GPRN does not match Meter Number
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
GNI Systems will validate the information before sending the market message to the Outgoing Shipper.
Market Message Implementation Guide v003.00.002
67
Segment Opt Ln Typ Composition Instructions Validation
Data Field
LTTR Less than 20 business days have elapsed since Registration was completed for this NDM Supply Point
ISSC Invalid Shipper/Supplier ID combination
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”
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’
OVCT At least one Vulnerable Customer Type must be provided if Vulnerable Customer 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
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
CMPS Current Gas Point Status does not support CoS
GSSN Gas Service Status is not ‘Gas in Service’
UAVC Vulnerability Information is required to use alternate address
CDVC Contact Address Information should be provided for Alternate Address for Vulnerable Customers
SDHA Shipper does not have an agreement with the PPMSP
RFRV Read Failed Read Validation tolerance levels
Market Message Implementation Guide v003.00.002
68
Segment Opt Ln Typ Composition Instructions Validation
Data Field
Market Message Implementation Guide v003.00.002
69
3.11 G208RQ– Change of Shipper Cancellation NDM Request
3.11.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
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.
3.11.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 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] 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.
Change of Shipper ID [cosID]
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.
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 it is not
shorter or longer than 8 digits.
Market Message Implementation Guide v003.00.002
70
Segment Opt Ln Typ Composition Instructions Validation
Data Field
The following validation will be applied to this data field by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
71
3.12 G209RJ – Change of Shipper Cancellation Rejection
3.12.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Initiator: Transporter Recipient: Shipper
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.
3.12.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
CoS Cancellation Rejection M Segment Please see data field level instructions below.
Change of Shipper ID [cosID]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
CoS Cancellation Rejection Reason
M Segment Please see data field level instructions below.
G209 Rejection Code [g209RejectionCode]
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 identified below.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
72
Segment Opt Ln Typ Composition Instructions Validation
Data Field
Code Description
GDNE GPRN does not exist
NNDG Not an NDM GPRN
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
Market Message Implementation Guide v003.00.002
73
3.13 G210N –CoS Cancellation Notification (Incoming Shipper)
3.13.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Initiator: Transporter Recipient: 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.
3.13.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
COS Cancellation Completion M Segment Please see data field level instructions below.
Change of Shipper ID [cosID]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
74
3.14 G211N – CoS Cancellation Notification (Outgoing Shipper)
3.14.1 Purpose/Description
MPD Reference: MPD2 – Change of Shipper and Cancellation of a CoS NDM Market Process
Initiator: Transporter Recipient: 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.
3.14.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
COS Cancellation Completion M Segment Please see data field level instructions below.
Change of Shipper ID [cosID]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
75
3.15 G301RQ –Historical Consumption NDM Request
3.15.1 Purpose/Description
MPD Reference: MPD3 – Request for I/C Historical Consumption Data NDM Market Process
Initiator: Shipper Recipient: Transporter
Description: Shippers will use this message when they wish to request historical consumption data for an Industrial/Commercial NDM Supply Point.
3.15.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 exist on GNI Systems. [GDNE].
GPRN must be that of an NDM site. [NNDG]
GPRN must be an I&C GPRN. [NICG] The Shipper status must permit this
request type. [SSDS] A valid Shipper/Supplier ID combination
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
M Segment Please see data field level instructions below.
Shipper Authoriser Name [shipperAuthoriserName]
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. That the format is correct.
Market Message Implementation Guide v003.00.002
76
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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]
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]
Market Message Implementation Guide v003.00.002
77
3.16 G302RJ – Historical Consumption Rejection
3.16.1 Purpose/Description
MPD Reference: MPD3 – Request for I/C Historical Consumption Data NDM Market Process
Initiator: Transporter Recipient: Shipper
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.
3.16.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Historical Consumption Rejection Reason
M Segment Please see data field level instructions below.
G302 Rejection Code [g302RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
NICG Not an I&C GPRN
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
78
Segment Opt Ln Typ Composition Instructions Validation
Data Field
GNIC Current Gas Service Status does not support HC Requests
GDNM GPRN does not match meter number
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
Market Message Implementation Guide v003.00.002
79
3.17 G303N – Historical Consumption Completion Notification
3.17.1 Purpose/Description
MPD Reference: MPD3 – Request for I/C Historical Consumption Data NDM Market Process
Initiator: Transporter Recipient: Shipper
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.
3.17.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Historical Consumption Completion
M Segment Please see data field level instructions below.
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
Z Band 5 5,550,000 Band 5
GNI Systems will validate the information before sending the market message to the Shipper
Market Message Implementation Guide v003.00.002
80
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
GNI Systems will validate the information before sending the market message to the Shipper
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.
GNI Systems will validate the information before sending the market message to the Shipper
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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 Date [mrTakenDate]
M 10 Date
Always associated with a meter reading index. Indicates the date on which the meter read was taken.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
81
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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).
Market Message Implementation Guide v003.00.002
82
3.18 G401RQ – End User Assignment Request
3.18.1 Purpose/Description
MPD Reference: MPD4 – End User Assignment Market Process
Initiator: Shipper Recipient: Transporter
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.
3.18.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 exist on GNI Systems. [GDNE]
GPRN must be that of an NDM site. [NNDG]
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]
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.
Market Message Implementation Guide v003.00.002
83
Segment Opt Ln Typ Composition Instructions Validation
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
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 one of
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
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 one of
the available codes.
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.
In addition to the validation listed in section 2.8, the following validation will be applied by GNI Systems:
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]
Market Message Implementation Guide v003.00.002
84
Segment Opt Ln Typ Composition Instructions Validation
Data Field
Meter Read Index and Taken Date must be provided if Read Available flag set to ‘Y’ [MRRA]
Market Message Implementation Guide v003.00.002
85
3.19 G402RJ – End User Assignment Rejection
3.19.1 Purpose/Description
MPD Reference: MPD4 – End User Assignment Market Process
Initiator: Transporter Recipient: Shipper
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).
3.19.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. GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
End User Assignment Rejection Reason
M Segment Please see data field level instructions below.
G402 Rejection Code [g402RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN is not registered to Shipper
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
86
Segment Opt Ln Typ Composition Instructions Validation
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
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
TDNF Taken Date can not be in the future
OVCT At least one Vulnerable Customer Type must be provided if Vulnerable Customer set to ‘Y’
VCFN If No is Chosen in End User Vulnerable Flag, then no value should be provided
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’
GDNM GPRN does not match Meter Number
IGVC If GPRN is Volume Corrected, 3 reads must be provided
TVCS This is a Volume Corrected site
Market Message Implementation Guide v003.00.002
87
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
ARAE Actual/Customer reading already exists for this taken date
INRC Invalid read combination
EDMP End User Details must be provided if Assignment Option is set to ‘Assign’
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
Market Message Implementation Guide v003.00.002
88
Segment Opt Ln Typ Composition Instructions Validation
Data Field
CDVC Contact Address Information should be provided for Alternate Address for Vulnerable Customers
MRRA Meter Read Index and Taken Date must be provided if Read Available flag set to ‘Y’
RFRV Read Failed Read Validation tolerance levels
Market Message Implementation Guide v003.00.002
89
3.20 G403N – End User Assignment Provisional Acceptance Notification
3.20.1 Purpose/Description
MPD Reference: MPD4 – End User Assignment Market Process
Initiator: Transporter Recipient: Shipper
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.
3.20.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
End User Assignment Type M Segment Please see data field level instructions below.
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 De-assignment
The ‘End User Assignment Type Code’ will be the same value as submitted by the Shipper in the original G401RQ message.
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
90
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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.
Market Message Implementation Guide v003.00.002
91
3.21 G404N – End User Assignment Completion Notification
3.21.1 Purpose/Description
MPD Reference: MPD4 – End User Assignment Market Process
Initiator: Transporter Recipient: Shipper
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.
3.21.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
End User Assignment Type M Segment Please see data field level instructions below.
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 De-assignment
This will be the same value as submitted by the Shipper in the original G401RQ message.
GNI Systems will validate the information before sending the market message to the Shipper.
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 ‘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.
Market Message Implementation Guide v003.00.002
92
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Market Message Implementation Guide v003.00.002
93
3.22 G601RQ – Registration NDM Request
3.22.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Shipper Recipient: Transporter
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.
3.22.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 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;
Code Description
FIT Fit Meter
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 field by GNI Systems; Gas Point Status must be appropriate for the
requested Site Works type. [MPSA]
Market Message Implementation Guide v003.00.002
94
Segment
Opt Ln Typ Composition Instructions Validation Data Field
FPM Fit PPM Meter
UNL Unlock Meter
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.
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 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]
Meter ID [meterID] D 24 Char The number of the meter.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
Market Message Implementation Guide v003.00.002
95
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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.
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 15
digits.
Site Works Contact Phone No:2 [swContactPhoneNo2]
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; Appointment ID must have been reserved via
“Real-time” Gas Shipper Self-Service Component. [IAID]
Market Message Implementation Guide v003.00.002
96
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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]
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]
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.
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 10
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 [gpHouseTypeCode]
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 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.
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.
Market Message Implementation Guide v003.00.002
97
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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]
Market Message Implementation Guide v003.00.002
98
Segment
Opt Ln Typ Composition Instructions Validation Data Field
End User Details M Segment Please refer to Section 2.5 for End User Details Common Data Segment
Market Message Implementation Guide v003.00.002
99
3.23 G602RJ – Registration Rejection
3.23.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Transporter Recipient: Shipper
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.
3.23.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Registration Rejection Reason
M Segment Please see data field level instructions below.
G602 Rejection Code [g602RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GRSA GPRN registered to a Shipper already
ORRG Outstanding Registration Request for GPRN
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
100
Segment
Opt Ln Typ Composition Instructions Validation Data Field
OVCT At least one Vulnerable Customer Type must be provided if Vulnerable Customer set to ‘Y’
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.
EUCR End User Consent must be received in advance
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
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’
Market Message Implementation Guide v003.00.002
101
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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’
AIAP Appointment Illegal – Awaiting Prepayment from End User
SDHA Shipper does not have an agreement with PPMSP
FHOA Financial Hardship only applies to Prepayment Meters
FHMB Financial Hardship indicator must be poplulated for PPM Meters
IHTB Invalid House Type/Bedroom combination
UAVC Vulnerability Information is required to use alternate address
CDVC Contact Address Information should be provided for Alternate Address for Vulnerable Customers
NARS No appointment required for this Site Works activity.
Market Message Implementation Guide v003.00.002
102
3.24 G603N- Registration Provisional Acceptance
3.24.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Transporter Recipient: Shipper
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.
3.24.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data 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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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 request was accepted.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
103
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
104
3.25 G604N- Registration Completion Notification
3.25.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Transporter Recipient: Shipper
Description: The Transporter will send this message to Shippers once the Registration process has been successfully completed.
3.25.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data 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
UFI Action Required - Flue Inadequate
UFS Action Required - Failed Soundness Test
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
105
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Location D Segment Please see data field level instructions below.
Gas Point Meter Location [gpMeterLocation]
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 one of the following: CPD, CPS, WNC, WNR, VCP
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.
Market Message Implementation Guide v003.00.002
106
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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
End User Details M Segment Please refer to Section 2.5 for End User Details Common Data Segment.
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
Market Message Implementation Guide v003.00.002
107
3.26 G605RQ – Registration Cancellation Request
3.26.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Shipper Recipient: Transporter
Description: Shippers will use this message when they wish to cancel a previously submitted G601RQ – Registration NDM Request Market Message.
3.26.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 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
must be provided. [ISSC] Shipper Status must support this request type.
[SSDS] There must not be an outstanding Registration
Cancellation Request for this GPRN (to avoid duplication). [ORCR]
Registration Cancellation Request
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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.
The following validation will be applied to this data field by GNI Systems;
Market Message Implementation Guide v003.00.002
108
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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]
Market Message Implementation Guide v003.00.002
109
3.27 G606RJ – Registration Cancellation Rejection
3.27.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Transporter Recipient: Shipper
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.
3.27.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Registration Cancellation Rejection
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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 Segment Please see data field level instructions below.
G606 Rejection Code [g606RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GPPS GPRN not provisionally registered to Shipper
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
110
Segment
Opt Ln Typ Composition Instructions Validation Data Field
ISSC Invalid Shipper ID/Supplier ID Combination
SSDS Shipper status does not support this request type
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
Market Message Implementation Guide v003.00.002
111
3.28 G607N - Registration Cancellation Completion Notification
3.28.1 Purpose/Description
MPD Reference: MPD6 – Registration Market Process
Initiator: Transporter Recipient: Shipper
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.
3.28.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Registration Cancellation Completion
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Date [swAppointmentDate]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Time Frame [swAppointmentTimeFrame]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
112
3.29 G701N – Deregistration Tariff Exemption Notification
3.29.1 Purpose/Description
MPD Reference: MPD7 – Deregistration Market Process
Initiator: Transporter Recipient: Shipper
Description: The Registered Shipper at an NDM Supply Point will receive this notification when they are exempt from transportation charges for that Supply Point
3.29.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.
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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
113
3.30 G702N – Deregistration Tariff Exemption Removal Notification
3.30.1 Purpose/Description
MPD Reference: MPD7 – Deregistration Market Process
Initiator: Transporter Recipient: Shipper
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.
3.30.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
3.31 G703N – Deregistration Completion Notification
3.31.1 Purpose/Description
MPD Reference: MPD7 – Deregistration Market Process
Initiator: Transporter Recipient: Shipper
Market Message Implementation Guide v003.00.002
114
Description: The Transporter will send this message to Shippers once the Deregistration process has been successfully completed.
3.31.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.
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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data 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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
115
4. NMD Market Messages
This section outlines the market messages in the NMD business area as they appear in the Gas MaP Market Messaging solution.
The NMD Market Messages are:
M801RQ Shipper Entered Meter Read Entry – NDM Generic / Volume Corrected
M802RJ Meter Read Rejection
M803N Meter Read Information Notification – NDM – Generic/Volume Corrected (Single Read Segment)
M804N Meter Read Information Notification – NDM – Generic/Volume Corrected (Double Read Segment)
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 Read Cycle Information Notification
Market Message Implementation Guide v003.00.002
116
4.1 M801RQ – Meter Read Request – NDM
4.1.1 Purpose/Description
MPD Reference: MPD8 – Meter Read Information Market Process
Initiator: Shipper Recipient: Transporter
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.
4.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 exist on GNI Systems. [GDNE]
GPRN must be that of an NDM site. [NNDG]
GPRN must be registered to Shipper sending message unless pending CoS to that shipper. [GNRC]
There must be a meter at the Meterpoint [NMAM]
The Shipper status must permit this request type. [SSDS]
A valid Shipper/Supplier ID combination must be provided. [ISSC]
Meter Read Request M Segment Please see data field level instructions below.
Market Message Implementation Guide v003.00.002
117
Segment Opt Ln Typ Composition Instructions Validation
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.
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 has 2
characters. That it is one of the available codes.
The following validation will be applied to this data field by GNI Systems:
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]
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. This is defined with the following XML format:
YYYY-MM-DD
Gas Shipper Communication Component will validate the data in this field to ensure:
That a value has been provided. That the format is correct – dd/mm/yy –
and is not less or greater than 8 characters.
The following validation will be applied to this data field by GNI Systems:
A date in the future must not be provided. [TDNF]
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
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 not
shorter or longer than 1 character. That it is one of the available codes.
Market Message Implementation Guide v003.00.002
118
Segment Opt Ln Typ Composition Instructions Validation
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 following validation will be applied to this data field by GNI Systems:
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]
Meter Read Volume Index [mrVolumeIndex]
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.
Gas Shipper Communication Component will validate the data in this field to ensure:
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 GNI Metering [RFRV]
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 ‘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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
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:
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]
Market Message Implementation Guide v003.00.002
119
Segment Opt Ln Typ Composition Instructions Validation
Data Field
If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [MHNG]
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 ‘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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
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:
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]
If a value is provided, the read index provided must be equal to or greater than the previous Actual read. [UING]
Market Message Implementation Guide v003.00.002
120
4.2 M802RJ – Meter Read Rejection
4.2.1 Purpose/Description
MPD Reference: MPD8 – Meter Read Information Market Process
Initiator: Transporter Recipient: Shipper
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.
4.2.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Rejection M Segment Please see data field level instructions below.
Meter Read Taken Date [mrTakenDate]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Volume Index [mrVolumeIndex]
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’.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Type Code (Shipper Read) [mrTypeCodeShipper]
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 ‘Meter Read Request’, the ‘Meter Read Type Code’ on the original
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
121
Segment Opt Ln Typ Composition Instructions Validation
Data Field
M801RQ market message sent by the Shipper is quoted back in this field as the ‘Meter Read Type Code’.
Meter Read Rejection Reason
M Segment Please see data field level instructions below.
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
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
ARAE Actual/Customer reading already exists for this taken date
RTDE Read Type does not exist on GNI System
INRC Invalid read combination
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
TDNF Read Taken Date can not be in the future
IGVC If GPRN is Volume Corrected, 3 reads must be provided
TVCS This is a Volume Corrected site
VING Volume Index not equal to or greater than previous Actual read
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
122
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
RFRV Read Failed Read Validation tolerance levels
Market Message Implementation Guide v003.00.002
123
4.3 M803N – Meter Read Completion Notification – (Single Read)
4.3.1 Purpose/Description
MPD Reference: MPD8 – Meter Read Information Market Process
Initiator: Transporter Recipient: Shipper
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 NMD Procedures.
4.3.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
124
4.4 M804N – Meter Read Completion Notification – (Double Read)
4.4.1 Purpose/Description
MPD Reference: MPD8 – Meter Read Information Market Process
Initiator: Transporter Recipient: Shipper
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.
4.4.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
125
4.5 M901RQ – Meter Read Query Request
4.5.1 Purpose/Description
MPD Reference: MPD9 – Meter Read Query Resolution Market Process
Initiator: Shipper Recipient: Transporter
Description: Shippers will use this message when they wish to query a read that has been provided by the Transporter previously.
4.5.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 exist on GNI Systems. [GDNE]
GPRN must be that of an NDM site. [NNDG]
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]
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.
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 does
not exceed the maximum of 50 characters.
Market Message Implementation Guide v003.00.002
126
Segment Opt Ln Typ Composition Instructions Validation
Data Field
There is no individual business logic validation for this field.
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. The expected format for all date inputs is YYYY-MM-DD, giving a length of 10 characters.
Gas Shipper Communication Component will validate the data in this field to ensure:
That a value has been provided. That the format is correct – YYYY-MM-DD
– and is not less or greater than 10 characters.
The following validation will be applied to this data field by GNI Systems:
A date in the future must not be provided. [TDNF]
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).
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 value
is not less than 1 integer and not greater than 2 integers in length.
That only numeric values have been provided.
There is no individual business logic validation for this field.
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.
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 value
is not greater than 250 characters in length.
The following validation will be applied to this data field by GNI Systems:
The complete message will be manually checked by a TRANSPORTER 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
Market Message Implementation Guide v003.00.002
127
Segment Opt Ln Typ Composition Instructions Validation
Data Field
detail of the message is insufficient, the message will be rejected. [
Market Message Implementation Guide v003.00.002
128
4.6 M902RJ – Meter Read Query Rejection
4.6.1 Purpose/Description
MPD Reference: MPD9 – Meter Read Query Resolution Market Process
Initiator: Transporter Recipient: Shipper
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.
4.6.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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).
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Query Rejection Reason
M Segment Please see data field level instructions below.
M902 Rejection Code [m902RejectionCode]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
129
Segment Opt Ln Typ Composition Instructions Validation
Data Field
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN is not registered to Shipper MRTP Meter Read taken prior to Shipper being assigned to
GPRN
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not support this request type
TDNF Read Taken Date can not be in the future
Market Message Implementation Guide v003.00.002
130
4.7 M903N – Meter Read Query Completion Notification
4.7.1 Purpose/Description
MPD Reference: MPD9 – Meter Read Query Resolution Market Process
Initiator: Transporter Recipient: Shipper
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.
4.7.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read Query Completion
M Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
131
4.8 M1101RQ – Estimated Read Request
4.8.1 Purpose/Description
MPD Reference: MPD11 – Shipper Estimated Read Request Market Process
Initiator: Shipper Recipient: Transporter
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.
4.8.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 exist on GNI Systems. [GDNE]
GPRN must be that of an NDM site. [NNDG]
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]
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 [mrRequestedEstimateDate]
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
Gas Shipper Communication Component will validate the data in this field to ensure:
That a value has been provided. That the format is correct – YYYY-MM-DD
– and is not less or greater than 10 characters.
Market Message Implementation Guide v003.00.002
132
Segment Opt Ln Typ Composition Instructions Validation
Data Field
The following validation will be applied to this data field by GNI Systems:.
A date in the future must not be provided. [TDNF]
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]
Market Message Implementation Guide v003.00.002
133
4.9 M1102RJ – Estimated Read Rejection
4.9.1 Purpose/Description
MPD Reference: MPD11 – Shipper Estimate Read Request Market Process
Initiator: Transporter Recipient: Shipper
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.
4.9.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Estimated Read Rejection Reason
M Segment Please see data field level instructions below.
M1102 Rejection Code [m1102RejectionCode]
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 list of pre-defined codes identified below.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
134
Segment Opt Ln Typ Composition Instructions Validation
Data Field
Code Description RAET Reading already exists for this taken date
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN is not registered to Shipper
TDNF Read Taken Date can not be in the future
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
ISSC Invalid Shipper/Supplier ID combination
SSDS Shipper status does not permit this request type
NMAM No Meter at Meterpoint
NPRN No Previous Reads. Read can not be accepted
Market Message Implementation Guide v003.00.002
135
4.10 M1103N – Estimated Read Completion Notification
4.10.1 Purpose/Description
MPD Reference: MPD11 – Shipper Estimate Read Request Market Process
Initiator: Transporter Recipient: Shipper
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.
4.10.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Meter Read M Segment Please refer to Section 2.6 for Meter Read Information Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
136
4.11 M1401N – Read Cycle Update Notification
4.11.1 Purpose/Description
MPD Reference: MPD14 – Notification for Read Cycle Updates Market Process
Initiator: Transporter Recipient: Shipper
Description: The Transporter will send this message to Shippers whenever the Read Cycle for a Gas Point is updated (i.e. that the meter at the specified Gas Point is going to be read on a different frequency than it has been to date).
4.11.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.
GNI Systems will validate the information before sending the market message to the Shipper.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Read Cycle M Segment Please refer to Section 2.9 for Read Cycle Information Common Data Segment.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
137
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
Market Message Implementation Guide v003.00.002
138
5.1 S1501N - Site Works Appointment Re-Scheduling Notification
5.1.1 Purpose/Description
MPD Reference: MPD15 – Management of Appointments Market Process
Initiator: Transporter Recipient: Shipper
Description: The Transporter will send this message to Shippers when the Transporter has to reschedule an appointment for operational reasons.
5.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Appointment Notification
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
139
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Site Works Appointment Date [swAppointmentDate]
M 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
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Time Frame [swAppointmentTimeFrame]
M 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
GNI Systems will validate the information before sending the market message to the Shipper.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
140
5.2 S1502RQ – Site Works Appointment Re-Scheduling Request
5.2.1 Purpose/Description
MPD Reference: MPD15 – Management of Appointments Market Process
Initiator: Shipper Recipient: Transporter
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.
5.2.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 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
must be provided. [ISSC] Shipper Status must support this request type.
[SSDS]
Site Works Appointment Request
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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. Please note the following;
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.
Market Message Implementation Guide v003.00.002
141
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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]
Site Works Appointment ID [swAppointmentID]
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.
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
Gas Shipper Communication Component will validate the data in this field to ensure: That the format is correct. That the entered value has 6 characters.
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]
Reserved Appointment Date must be within 30 days from now. [RSDW]
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 no Pending CoS. [SCRP]
Market Message Implementation Guide v003.00.002
142
5.3 S1503RJ – Site Works Re-Scheduling Request Rejection
5.3.1 Purpose/Description
MPD Reference: MPD15 – Management of Appointments Market Process
Initiator: Transporter Recipient: Shipper
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.
5.3.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Appointment Rejection Reason
M Segment Please see data field level instructions below.
S1503 Rejection Code [s1503RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
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
OSRN Original Site Works Request not set aside for this Shipper
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
143
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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
Market Message Implementation Guide v003.00.002
144
5.4 S1504A- Site Works Re-Scheduling Request Acceptance
5.4.1 Purpose/Description
MPD Reference: MPD15 – Management of Appointments Market Process
Initiator: Transporter Recipient: Shipper
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.
5.4.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Site Works Appointment Completion
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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;
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
145
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Site Works Appointment Date [swAppointmentDate]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Time Frame [swAppointmentTimeFrame]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
146
5.5 S1601RQ - Site Works Request
5.5.1 Purpose/Description
MPD Reference: MPD16 – Creation and Completion of Operational Site Works Request for NDM Sites
Initiator: Shipper Recipient: Transporter
Description: Shippers will use this message when they wish to raise a request for an Operational Site Works Activity to be carried out.
5.5.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 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;
Code Description Code Description
UNL Unlock Meter RPR Repair Riser Cover
DCT Disconnect INV Investigation
NGS No Gas RPM Repair Meter Box
LCK Lock Meter SPR Special Read
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 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]
Market Message Implementation Guide v003.00.002
147
Segment
Opt Ln Typ Composition Instructions Validation Data Field
EXC Exchange Meter TSP Test Service Pipe
TEM Test Meter NOH Notice of Hazard
RBK Request Meter Box Key SDC Street Disconnect
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
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. Note: If this option is used and the End User currently has a legacy prepayment meter, it will
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]
Market Message Implementation Guide v003.00.002
148
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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 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; Job Remarks/Access Information must be
provided – Market Message will fail validation if the provided value for “Site Works Request
Market Message Implementation Guide v003.00.002
149
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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 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. There is no individual business logic validation for this field.
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 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 15
digits. There is no individual business logic validation for this field.
Site Works Contact Phone No:2 [swContactPhoneNo2]
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.
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. There is no individual business logic validation for this field.
Site Works Appointment D Segment Please see data field level instructions below.
Site Works Appointment ID [swAppointmentID]
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.
Code Description Code Description
UNL* Unlock Meter RPR Repair Riser Cover
DCT** Disconnect INV* Investigation
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
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 data field value is provided for a Site Works Request Type that does not require an appointment. [NARS]
Market Message Implementation Guide v003.00.002
150
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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]
Reserved Appointment Date must be within 30 days from now. [RSDW]
Market Message Implementation Guide v003.00.002
151
5.6 S1602RJ – Site Works Rejection
5.6.1 Purpose/Description
MPD Reference: MPD16 – Creation and Completion of Operational Site Works Request for NDM Sites
Initiator: Transporter Recipient: Shipper
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.
5.6.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Rejection Reason M Segment Please see data field level instructions below.
S1602 Rejection Code [s1602RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN not registered to Shipper
ISSC Invalid Shipper/Supplier ID Combination
SSDS Shipper Status does not support this request type
MPSA Gas Point Status is not appropriate for this Site Works type
GPSA Gas Service Status is not appropriate for this Site Works type
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
152
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
SDHA Shipper does not have an agreement with PPMSP
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 works not valid for this gas point
Market Message Implementation Guide v003.00.002
153
5.7 S1603A- Site Works Acceptance
5.7.1 Purpose/Description
MPD Reference: MPD16 – Creation and Completion of Operational Site Works Request for NDM Sites
Initiator: Transporter Recipient: Shipper
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.
5.7.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Site Works 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 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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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 S1601RQ - Site Works Request Market Message for information purposes only.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
154
Segment
Opt Ln Typ Composition Instructions Validation Data Field
This field will be populated with a value for 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
Site Works Appointment Date [swAppointmentDate]
D 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
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Time Frame [swAppointmentTimeFrame]
D 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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
155
5.8 S1604N- Site Works Completion Notification
5.8.1 Purpose/Description
MPD Reference: MPD16 – Creation and Completion of Operational Site Works Request for NDM Sites
Initiator: Transporter Recipient: Shipper
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.
5.8.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.2 for Shipper Header Common Data Segment.
Gas Point Status M Segment Please refer to Section 2.7 for Gas Point Status 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
USL Action Required - Safety Locked - Leak
UFI Action Required - Flue Inadequate
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
156
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.)
CMN Complete (Locked, no answer from shipper.)
LMC Complete (Locked, after call from shipper.)
Market Message Implementation Guide v003.00.002
157
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
GNI Systems will validate the information before sending the market message to the Shipper.
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 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.
GNI Systems will validate the information before sending the market message to the Shipper.
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 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.
Meter Read D 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.
Market Message Implementation Guide v003.00.002
159
5.9 S1701RQ – Site Works Cancellation Request
5.9.1 Purpose/Description
MPD Reference: MPD17 – Cancellation of Site Works Market Process
Initiator: Shipper Recipient: Transporter
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.
5.9.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 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
must be provided. [ISSC] Shipper Status must support this request type.
SSDS]
Site Works Cancellation Request
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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;
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
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.
The following validation will be applied to this data field by GNI Systems; Original Site Works Request Reference must be
generated previously by S1601RQ. [ISRN]
Market Message Implementation Guide v003.00.002
160
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
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]
Market Message Implementation Guide v003.00.002
161
5.10 S1702RJ – Site Works Cancellation Request Rejection
5.10.1 Purpose/Description
MPD Reference: MPD17 – Cancellation of Site Works Market Process
Initiator: Transporter Recipient: Shipper
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.
5.10.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Cancellation Rejection
M Segment Please see data field level instructions below.
S1702 Rejection Code [s1702RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN not registered to Shipper
ISSC Invalid Shipper ID/Supplier ID Combination
SSDS Shipper Status does not support this request type
ISRN Site Works Reference Number does not exist
SRBS Site Works Reference Number belongs to another Shipper
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
162
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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
Market Message Implementation Guide v003.00.002
163
5.11 S1703A- Site Works Cancellation Acceptance
5.11.1 Purpose/Description
MPD Reference: MPD17 – Cancellation of Site Works Market Process
Initiator: Transporter Recipient: Shipper
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.
5.11.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Site Works Cancellation Completion
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
M 12 Char A unique reference number for the original Site Works request that is cancelled as per the Shipper’s S1701RQ market message.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment ID [swAppointmentID]
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;
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
164
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
Site Works Appointment Date [swAppointmentDate]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Appointment Time Frame [swAppointmentTimeFrame]
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
165
5.12 S1901RQ - Site Works Complaint Request
5.12.1 Purpose/Description
MPD Reference: MPD19 – Management of Site Works Complaints Market Process
Initiator: Shipper Recipient: Transporter
Description: Shippers will use this message when they wish to submit a Site Works-related complaint.
5.12.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 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
must be provided. [ISSC] Shipper Status must support this request type.
[SSDS]
Site Works Complaint Request
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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 be able to submit a complaint request without any “Site Works Reference” for non-site works activity specific complaints.
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 applied to this data field by GNI Systems; Original Site Works Request Reference must be
generated previously by S1601RQ. [OSNE]
Market Message Implementation Guide v003.00.002
166
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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
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
0024 Quality Permanent Reinstatement
0025 Quality Temporary Reinstatement
0026 Service Quality
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.
There is no individual business logic validation for this field.
Market Message Implementation Guide v003.00.002
167
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
There is no individual business logic validation for this field.
Site Works Complaint 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 the relevant Site Works Complaint.
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. There is no individual business logic validation for this field.
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 the relevant Site Works Complaint.
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 15
digits. There is no individual business logic validation for this field.
Site Works Contact Phone No:2 [swContactPhoneNo2]
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.
If any value provided, Gas Shipper Communication Component will validate the data in this field to ensure:
Market Message Implementation Guide v003.00.002
168
Segment
Opt Ln Typ Composition Instructions Validation Data Field
That the format is correct – not longer than 15 digits.
There is no individual business logic validation for this field.
Market Message Implementation Guide v003.00.002
169
5.13 S1902RJ - Site Works Complaint Rejection
5.13.1 Purpose/Description
MPD Reference: MPD19 – Management of Site Works Complaints Market Process
Initiator: Transporter Recipient: Shipper
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.
5.13.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Complaint Rejection
M Segment Please see data field level instructions below.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Complaint Rejection Reason
M Segment Please see data field level instructions below.
Site Works Complaint Type Code [swComplaintTypeCode]
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
0003 Broken Appointment
0004 Broken Appointment Fitter
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
170
Segment
Opt Ln Typ Composition Instructions Validation Data Field
0005 Collect Barriers/Equipment
0006 Customer Unhappy about Lay Service Charge
0007 Cutting in Dangerous Condition
0008 Damage to Property
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
0024 Quality Permanent Reinstatement
0025 Quality Temporary Reinstatement
0026 Service Quality
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
Market Message Implementation Guide v003.00.002
171
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Site Works Complaint Rejection Reason
M Segment Please see data field level instructions below.
S1902 Rejection Code [s1902RejectionCode]
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
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN not registered to Shipper
ISSC Invalid Shipper/Supplier ID Combination
SSDS Shipper Status does not support this request type
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
172
5.14 S1903A- Site Works Complaint Acceptance
5.14.1 Purpose/Description
MPD Reference: MPD19 – Management of Site Works Complaints Market Process
Initiator: Transporter Recipient: Shipper
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.
5.14.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Common Data Segment.
Site Works Complaint Acceptance
M Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Complaint Type Code
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
173
Segment
Opt Ln Typ Composition Instructions Validation Data Field
[swComplaintTypeCode]
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
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
0024 Quality Permanent Reinstatement
0025 Quality Temporary Reinstatement
0026 Service Quality
0027 Site in Poor Condition
0028 Siteworks Charges
0029 Spoil to be removed
0030 Technical Query/Complaint
0031 Traffic Restrictions
Market Message Implementation Guide v003.00.002
174
Segment
Opt Ln Typ Composition Instructions Validation Data Field
0032 Upgrading Work Unsightly
0033 Delay in Issuing Quotations
0034 Wayleave/Licence held
0035 Payment/Const not started
Market Message Implementation Guide v003.00.002
175
5.15 S1904N- Site Works Complaint Acceptance Notification
5.15.1 Purpose/Description
MPD Reference: MPD19 – Management of Site Works Complaints Market Process
Initiator: Transporter Recipient: Shipper
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.
5.15.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Complaint Notification
M Segment Please see data field level instructions below.
Site Works Complaint Reference [swComplaintRef]
M 7 Char The unique reference number generated by GNI Systems for a site works complaint logged by the End User.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Reference [swRef]
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
176
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Site Works Complaint Type Code [swComplaintTypeCode]
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
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
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
0024 Quality Permanent Reinstatement
0025 Quality Temporary Reinstatement
0026 Service Quality
0027 Site in Poor Condition
0028 Siteworks Charges
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
177
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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
Market Message Implementation Guide v003.00.002
178
5.16 S1905N- Site Works Complaint Completion Notification
5.16.1 Purpose/Description
MPD Reference: MPD19 – Management of Site Works Complaints Market Process
Initiator: Transporter Recipient: Shipper
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.
5.16.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Site Works Complaint Completion
M Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Site Works Reference [swRef]
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 directly. If the complaint is related with a Site Works request that was previously initiated by the Shipper, the Shipper will
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
179
Segment
Opt Ln Typ Composition Instructions Validation Data Field
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.
Site Works Complaint Type Code [swComplaintTypeCode]
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
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
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
0024 Quality Permanent Reinstatement
0025 Quality Temporary Reinstatement
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
180
Segment
Opt Ln Typ Composition Instructions Validation Data Field
0026 Service Quality
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 Resolution Details [swComplaintResolutionDetails]
M 250 Char Mandatory free text area allowing the Transporter to enter some resolution remarks in relation to the complaint resolution.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
181
5.17 S2301RQ –Gas Point Address Update Request
5.17.1 Purpose/Description
MPD Reference: MPD23 – Creation and Maintenance of Gas Point Address Market Process
Initiator: Shipper Recipient: Transporter
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.
5.17.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 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
must be provided. [ISSC] Shipper Status must support this request type.
[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.
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 3
digits.
Market Message Implementation Guide v003.00.002
182
Segment
Opt Ln Typ Composition Instructions Validation Data Field
There is no individual business logic validation for this field.
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.
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 1
character.
There is no individual business logic validation for this field.
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.
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 25
characters.
There is no individual business logic validation for this field.
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.
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 50
characters.
There is no individual business logic validation for this field.
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.
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 25
characters.
There is no individual business logic validation for this field.
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.
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 25
characters.
There is no individual business logic validation for this field.
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 ensure:
Market Message Implementation Guide v003.00.002
183
Segment
Opt Ln Typ Composition Instructions Validation Data Field
That the format is correct – not longer than 25 characters.
There is no individual business logic validation for this field.
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.
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 10
characters.
There is no individual business logic validation for this field.
Meter Location O Segment Please see data field level instructions below.
Gas Point Meter Location [gpMeterLocation]
O 40 Char The physical location of the Meter at the Gas Point Address.
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 40
characters.
There is no individual business logic validation for this field.
Gas Point Address Update Reason
M Segment Please see data field level instructions below.
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
characters. There is no individual business logic validation for this field.
Market Message Implementation Guide v003.00.002
184
5.18 S2302RJ –Gas Point Address Update Rejection
5.18.1 Purpose/Description
MPD Reference: MPD23 – Creation and Maintenance of Gas Point Address Market Process
Initiator: Transporter Recipient: Shipper
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.
5.18.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address Update Rejection
M Segment Please see data field level instructions below.
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.
GNI Systems will validate the information before sending the market message to the Shipper.
Gas Point Address Update Rejection Reason
M Segment Please see data field level instructions below.
S2302 Rejection Code [s2302RejectionCode]
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 codes identified below.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
185
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Code Description
GDNE GPRN does not exist
NNDG Not an NDM GPRN
GNRS GPRN not registered to Shipper
ISSC Invalid Shipper/Supplier ID Combination
SSDS Shipper Status does not support this request type
GPAI Gas Point Address Details Incomplete
AUNR Address Details Update not required
ADCO Address Details Conflict with TRANSPORTER 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.
Market Message Implementation Guide v003.00.002
186
5.19 S2303N- Gas Point Address Update Notification
5.19.1 Purpose/Description
MPD Reference: MPD23 – Creation and Maintenance of Gas Point Address Market Process
Initiator: Transporter Recipient: Shipper
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).
5.19.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.
Transporter Header M Segment Please refer to Section 2.3 for Transporter Header Common Data Segment.
Gas Point Address M Segment Please refer to Section 2.4 for Gas Point Address Information Common Data Segment.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Implementation Guide v003.00.002
187
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
Market Message Implementation Guide v003.00.002
188
6.1 H3001N - End of Day Totals Notification
6.1.1 Purpose/Description
MPD Reference: Not applicable
Initiator: Transporter Recipient: Shipper
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.
6.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.
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
GNI Systems will validate the information before sending the market message to the Shipper.
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
GNI Systems will validate the information before sending the market message to the Shipper.
Message Reconciliation Inbound
M Segment Please see data field level instructions below.
Market Message Type Code [mmTypeCode]
M 10 Char This defines the type of message to be sent by the Market Participant.
GNI Systems will validate the information before sending the market message to the Shipper.
Market Message Type Count [mmTypeCount]
M 9 Integer Will indicate the total number of each of the market message types received by the Transporter in the defined period.
Market Message Implementation Guide v003.00.002
189
Segment
Opt Ln Typ Composition Instructions Validation Data Field
Message Reconciliation Outbound
M Segment Please see data field level instructions below.
Market Message Type Code [mmTypeCode]
M 10 Char This defines the type of message to be sent by the Market Participant.
GNI Systems will validate the information before sending the market message to the Shipper.
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.