Common use of Maintenance of Data Clause in Contracts

Maintenance of Data. Optional Data Groups and Data Items only need to be populated where the data is readily available. The data sent will be processed according to the relevant rules, or may be ignored. • The design does not prescribe what Data Items might be maintained by an incremental update rather than being sent on each RGMA Data Flow, as this is considered a matter for commercial agreement. The file layouts allow all information a Market Participant wishes to send to be sent, and the file layouts allow MAMs (for example) to return updates. Some organisations may not require this extra functionality e.g. Meter Point addresses, information on consumers (names, addresses, care details and contact mechanisms) may all be maintained by incremental updates. • The flows do not prescribe who originates data. For example, some Suppliers may wish the MAM to organise the appointments, contacts and site addresses as part of their service. If this is the case then the related consumer name, address, care details and contact mechanisms would not be required. • Validation of data should be appropriate to ensure minimal delay in the transfer of Asset information across the industry. For example, if a Meter is removed, the transfer of this information needs to have priority over updating the information on the removed Meter. Similarly, unless Meter Point address updates indicate that the Meter Worker has visited the wrong property, the transfer of the Asset data should not be delayed until the Meter Point address has been corrected. • Minimisation of data integrity issues: In the file formats, if a value of a Data Item is not always known then the Data Item is Optional. The exception to this is the Meter Point address (ORJOB and ONAGE appointment), where the postcode, if not known, is set to a default value as allocated by the GT responsible for the relevant Meter Point address.