| Version: | D |
|---|---|
| Release: | 03B |
| Contr. Agency: | UN |
| Revision: | 3 |
| Date: | 2003-12-22 |
| SOURCE: | TBG1 Supply Chain |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Utilities master data message (UTILMD) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The Utilities master data message is sent between responsible parties in a utilities infrastructure for the purpose of exchanging characteristics of objects and services. In addition the Utilities master data message may be used to request information.
A party in a utilities infrastructure can for example be a net owner, a supplier, a balance responsible or a transmission system operator.
The Utilities master data message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
The Utilities master data message is used for exchanging characteristics of objects and services in the specified field, normally used for updating data bases with administrative and technical information of long validity, such as information concerning customers, partners and installations. The information may be of technical or administrative character, such as characteristics of a meter, tariffs, suppliers etc.
In addition the Utilities master data message may be used to request information.
Each set of master data can be identified according to its nature, e.g. by a metering point identification or a location identification. The message may be an initial message and does not require a response.
Examples of use are:
Information regarding change of supplier, such as: Request for end user information. Information regarding the characteristics of an end user. Information about change of supplier. Information of contract termination from an end user. Exchange of changes in characteristics of objects or services
between parties in a utilities infrastructure.
Change of identity of an object. Change of components or characteristics of components, such as
change of a meter.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
MASTER DATA: Data used as a reference when routine transactions are being processed. Master data will normally be exchanged or updated infrequently relative to the transaction data depending upon it. It will normally contain information of long validity.
OBJECT: The entity (component or logical entity) that is being reported in the detailed section of the message.
TIME SERIES: A sequence of observations of a single process often taken at equal time intervals.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Utilities master data message is UTILMD.
Note: Utilities master data messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | UTILMD |
| 0052 | D | |
| 0054 | 03B | |
| 0051 | UN |
A segment by which the sender uniquely identifies the Utilities master data message by means of its name and number and its function.
A segment specifying general dates related to the whole message and the time zone used in the message. The segment must be specified at least once to specify the message date as allocated by the sender.
A segment to specify to which market the object relates.
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A group of segments giving references and, where necessary, their dates relating to the whole message.
A segment identifying a reference by its type and number, such as references to an earlier sent messages or a contract number.
A segment specifying the date/time related to the referenced information.
A group of segments identifying the parties with associated information relevant to the whole message, such as the sender and the receiver of the message.
A segment for specifying the identification and/or the name and the address of the party, in coded or clear form, and the function relevant to the message. It is recommended that, if possible, only the coded form of the party ID should be specified.
A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.
A segment to identify an account and a related financial institution connected to the current party.
A group of segments giving contact details of a specific person and/or department within the party identified.
A segment to identify a person and/or department, and their function, to whom communications should be directed.
A segment to identify a communication type and number for the contact specified.
INP-SG5-SG6-SG7-SG8-SG11-SG12 A group of segments providing details and characteristics of an object, such as a metering point.
A segment starting a new set of master data for an object, and identifying the type of object, such as a metering point.
A segment providing identification of the quantity in the lower-level object specified, such as a product code.
A segment providing additional identification to the object specified.
A segment for describing the object being reported. The segment may be used for specification of the use of the object (e.g. the type of consumption or production in the object).
A segment to specify dates associated with the object.
A segment to specify to which business activity phase the object relates.
A segment giving a status for the object, such as active or closed.
A segment to specify relevant duty/tax/fee information, such as value added tax percentage.
A segment for communication of priority information, such as if an installation is disconnectable or not.
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A segment for specifying agreement details connected to the object, such as the type of contract.
A segment to specify parties to an instruction, the instruction, or both, such as instruction to read a meter.
A group of segments identifying locations connected to the object, such as a metered grid area or a metering point and its position in a hierarchy.
A segment to identify locations connected to the object, such as a metered grid area or a metering point.
A segment to identify hierarchical connections from a given location to a higher or lower leveled location, such as the connections between an aggregated metering point to the lover level metering points.
A group of segments for specifying any references and associated dates valid for the object.
A segment identifying any references related to the object, such as a transaction reference number or a reference to a time series.
A segment to specify any dates associated with the current reference.
A group of segments providing characteristics and characteristic details connected to the object.
A segment to identify characteristic and/or the characteristic name and characteristic relevance for the object, such as method for balance settlement or measurement method, number of digits of a meter etc.
A segment to specify the value of the characteristic previously defined in either coded form or in free format.
A group of segments to specify quantities, characteristics and references of lower-level objects related to the current object, such as meters and/or registers of a meter.
A segment to provide a sequence number of the lower-level objects, such as the register number within a meter.
A segment identifying any references related to the lower-level object, such as a register number or a reference to a contract.
A segment providing additional product identification connected to the lower-level object, such as a register of a meter.
group of segments providing quantities connected to the lower-level object.
A segment identifying the quantity details, such as estimated annual consumption or production.
A segment to specify dates or periods related to the previously specified quantity information.
A segment giving the status for the quantity, such as metered, estimated or corrected.
A segment providing identification of the quantity in the lower-level object specified, such as a product code.
A group of segments providing characteristics and characteristic details connected to the lower-level object.
A segment to identify a characteristic and/or the characteristic name and characteristic relevance for the lower-level object, such as number of digits of a meter etc.
A segment to specify the value of the characteristic previously defined in either coded form or in free format.
A group of segments for specifying monetary amounts related to the object and connected references and dates, such as grid access fee.
A segment for specifying monetary amounts related to the object.
A segment for identifying a reference to the amount.
A segment specifying the date/time related to the referenced information.
A group of segments identifying parties related to the object or service, with associated information, such as end user, installation, invoicee, etc.
A segment for specifying the identification and/or the name and address of the party, in coded or clear form, and the functions relevant to the object or service. It is recommended that, if possible, only the coded form of the party identification should be specified.
A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.
A segment specifying the date and/or the time related to the referenced information, such as the date of birth for the end user.
A segment to identify an account and a related financial institution connected to the current party.
A segment to indicate the langauges for the specified party.
A group of segments giving contact details of a specific person and/or department within the party identified.
A segment to identify a person and/or department, and their function, to whom communications should be directed.
A segment to identify a communication type and number for the contact specified.
A segment by which control totals may be sent by the sender for checking by the receiver.
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
| AGR | Agreement identification | |
| BGM | Beginning of message | |
| CAV | Characteristic value | |
| CCI | Characteristic/class id | |
| CNT | Control total | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FII | Financial institution information | |
| FTX | Free text | |
| HYN | Hierarchy information | |
| IDE | Identity | |
| IMD | Item description | |
| INP | Parties and instruction | |
| LAN | Language | |
| LIN | Line item | |
| LOC | Place/location identification | |
| MKS | Market/sales channel information | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| PIA | Additional product id | |
| PRC | Process identification | |
| PTY | Priority | |
| QTY | Quantity | |
| RFF | Reference | |
| SEQ | Sequence details | |
| STS | Status | |
| TAX | Duty/tax/fee details | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×9 | (M) |
| ├─MKS Market/sales channel information | ×9 | (C) |
| ├─FTX Free text | ×9 | (C) |
| ├─Segment Group 1 | ×9 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×9 | (C) |
| ├─Segment Group 2 | ×99 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─RFF Reference | ×1 | (C) |
| │─├─FII Financial institution information | ×1 | (C) |
| │─└─Segment Group 3 | ×9 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×9 | (C) |
| ├─Segment Group 4 | ×99999 | (C) |
| │─├─IDE Identity | ×1 | (M) |
| │─├─LIN Line item | ×1 | (C) |
| │─├─PIA Additional product id | ×9 | (C) |
| │─├─IMD Item description | ×9 | (C) |
| │─├─DTM Date/time/period | ×99 | (C) |
| │─├─PRC Process identification | ×9 | (C) |
| │─├─STS Status | ×9 | (C) |
| │─├─TAX Duty/tax/fee details | ×9 | (C) |
| │─├─PTY Priority | ×9 | (C) |
| │─├─FTX Free text | ×9 | (C) |
| │─├─AGR Agreement identification | ×9 | (C) |
| │─├─INP Parties and instruction | ×9 | (C) |
| │─├─Segment Group 5 | ×99999 | (C) |
| │─│─├─LOC Place/location identification | ×1 | (M) |
| │─│─└─HYN Hierarchy information | ×9 | (C) |
| │─├─Segment Group 6 | ×99 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×9 | (C) |
| │─├─Segment Group 7 | ×99 | (C) |
| │─│─├─CCI Characteristic/class id | ×1 | (M) |
| │─│─└─CAV Characteristic value | ×99 | (C) |
| │─├─Segment Group 8 | ×99 | (C) |
| │─│─├─SEQ Sequence details | ×1 | (M) |
| │─│─├─RFF Reference | ×9 | (C) |
| │─│─├─PIA Additional product id | ×9 | (C) |
| │─│─├─Segment Group 9 | ×99 | (C) |
| │─│─│─├─QTY Quantity | ×1 | (M) |
| │─│─│─├─DTM Date/time/period | ×9 | (C) |
| │─│─│─├─STS Status | ×9 | (C) |
| │─│─│─└─LIN Line item | ×9 | (C) |
| │─│─└─Segment Group 10 | ×99 | (C) |
| │─│───├─CCI Characteristic/class id | ×1 | (M) |
| │─│───└─CAV Characteristic value | ×99 | (C) |
| │─├─Segment Group 11 | ×99 | (C) |
| │─│─├─MOA Monetary amount | ×1 | (M) |
| │─│─├─RFF Reference | ×9 | (C) |
| │─│─└─DTM Date/time/period | ×9 | (C) |
| │─└─Segment Group 12 | ×99 | (C) |
| │───├─NAD Name and address | ×1 | (M) |
| │───├─RFF Reference | ×9 | (C) |
| │───├─DTM Date/time/period | ×9 | (C) |
| │───├─FII Financial institution information | ×1 | (C) |
| │───├─LAN Language | ×9 | (C) |
| │───└─Segment Group 13 | ×9 | (C) |
| │─────├─CTA Contact information | ×1 | (M) |
| │─────└─COM Communication contact | ×9 | (C) |
| ├─CNT Control total | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |