Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D01B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Utilities master data message

Version:D
Release:01B
Contr. Agency:UN
Revision:1
Date:2001-05-15
SOURCE:D2 Purchasing (SWG)

CONTENTS
Utilities master data message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
    2. Message terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      1. Segment table

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

0. INTRODUCTION

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.


1. SCOPE


1.1. Functional definition

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.


1.2. Field of application

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.


1.3. Principles

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.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


3.2. Message terms and definitions

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.


4. MESSAGE DEFINITION


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.

0010 UNH, Message header

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 element0065UTILMD
0052D
005401B
0051UN

0020 BGM, Beginning of message

A segment by which the sender uniquely identifies the Utilities master data message by means of its name and number and its function.

0030 DTM, Date/time/period

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.

0040 MKS, Market/sales channel information

A segment to specify to which market the object relates.

0050 FTX, Free text

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.

0060 Segment Group 1: RFF-DTM

A group of segments giving references and, where necessary, their dates relating to the whole message.

0070 RFF, Reference

A segment identifying a reference by its type and number, such as references to an earlier sent messages or a contract number.

0080 DTM, Date/time/period

A segment specifying the date/time related to the referenced information.

0090 Segment Group 2: NAD-RFF-FII-SG3

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.

0100 NAD, Name and address

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.

0110 RFF, Reference

A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.

0120 FII, Financial institution information

A segment to identify an account and a related financial institution connected to the current party.

0130 Segment Group 3: CTA-COM

A group of segments giving contact details of a specific person and/or department within the party identified.

0140 CTA, Contact information

A segment to identify a person and/or department, and their function, to whom communications should be directed.

0150 COM, Communication contact

A segment to identify a communication type and number for the contact specified.

0160 Segment Group 4: IDE-LOC-PIA-IMD-DTM-PRC-STS-TAX-PTY-FTX-SG5-

SG6-SG7-SG10-SG11 A group of segments providing details and characteristics of an object, such as a metering point.

0170 IDE, Identity

A segment starting a new set of master data for an object, and identifying the type of object, such as a metering point.

0180 LOC, Place/location identification

A segment to identify locations connected to the object, such as a net area or a connecting point to the central grid.

0190 PIA, Additional product id

A segment providing additional identification to the object specified.

0200 IMD, Item description

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).

0210 DTM, Date/time/period

A segment to specify dates associated with the object.

0220 PRC, Process identification

A segment to specify to which business activity phase the object relates.

0230 STS, Status

A segment giving a status for the object, such as active or closed.

0240 TAX, Duty/tax/fee details

A segment to specify relevant duty/tax/fee information, such as value added tax percentage.

0250 PTY, Priority

A segment for communication of priority information, such as if an installation is disconnectable or not.

0260 FTX, Free text

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.

0270 Segment Group 5: RFF-DTM

A group of segments for specifying any references and associated dates valid for the object.

0280 RFF, Reference

A segment identifying any references related to the object, such as a transaction reference number or a reference to a time series.

0290 DTM, Date/time/period

A segment to specify any dates associated with the current reference.

0300 Segment Group 6: CCI-CAV

A group of segments providing characteristics and characteristic details connected to the object.

0310 CCI, Characteristic/class id

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.

0320 CAV, Characteristic value

A segment to specify the value of the characteristic previously defined in either coded form or in free format.

0330 Segment Group 7: SEQ-RFF-PIA-SG8-SG9

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.

0340 SEQ, Sequence details

A segment to provide a sequence number of the lower-level objects, such as the register number within a meter.

0350 RFF, Reference

A segment identifying any references related to the lower-level object, such as a register number or a reference to a contract.

0360 PIA, Additional product id

A segment providing additional product identification connected to the lower-level object, such as a register of a meter.

0370 Segment Group 8: QTY-DTM-STS

group of segments providing quantities connected to the lower-level object.

0380 QTY, Quantity

A segment identifying the quantity details, such as estimated annual consumption or production.

0390 DTM, Date/time/period

A segment to specify dates or periods related to the previously specified quantity information.

0400 STS, Status

A segment giving the status for the quantity, such as metered, estimated or corrected.

0410 Segment Group 9: CCI-CAV

A group of segments providing characteristics and characteristic details connected to the lower-level object.

0420 CCI, Characteristic/class id

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.

0430 CAV, Characteristic value

A segment to specify the value of the characteristic previously defined in either coded form or in free format.

0440 Segment Group 10: MOA-RFF-DTM

A group of segments for specifying monetary amounts related to the object and connected references and dates, such as grid access fee.

0450 MOA, Monetary amount

A segment for specifying monetary amounts related to the object.

0460 RFF, Reference

A segment for identifying a reference to the amount.

0470 DTM, Date/time/period

A segment specifying the date/time related to the referenced information.

0480 Segment Group 11: NAD-RFF-DTM-FII-SG12

A group of segments identifying parties related to the object or service, with associated information, such as end user, installation, invoicee, etc.

0490 NAD, Name and address

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.

0500 RFF, Reference

A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.

0510 DTM, Date/time/period

A segment specifying the date and/or the time related to the referenced information, such as the date of birth for the end user.

0520 FII, Financial institution information

A segment to identify an account and a related financial institution connected to the current party.

0530 Segment Group 12: CTA-COM

A group of segments giving contact details of a specific person and/or department within the party identified.

0540 CTA, Contact information

A segment to identify a person and/or department, and their function, to whom communications should be directed.

0550 COM, Communication contact

A segment to identify a communication type and number for the contact specified.

0560 CNT, Control total

A segment by which control totals may be sent by the sender for checking by the receiver.

0570 UNT, Message trailer

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.


4.2. Segment index (alphabetical sequence by tag)

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
IDE Identity
IMD Item description
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

4.3. Message structure


4.3.1. Segment table

├─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)
├─LOC Place/location identification ×9 (C)
├─PIA Additional product id ×9 (C)
├─IMD Item description ×9 (C)
├─DTM Date/time/period ×9 (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)
├─Segment Group 5 ×99 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 6 ×99 (C)
├─CCI Characteristic/class id ×1 (M)
└─CAV Characteristic value ×99 (C)
├─Segment Group 7 ×99 (C)
├─SEQ Sequence details ×1 (M)
├─RFF Reference ×9 (C)
├─PIA Additional product id ×9 (C)
├─Segment Group 8 ×99 (C)
├─QTY Quantity ×1 (M)
├─DTM Date/time/period ×9 (C)
└─STS Status ×9 (C)
└─Segment Group 9 ×99 (C)
──├─CCI Characteristic/class id ×1 (M)
──└─CAV Characteristic value ×99 (C)
├─Segment Group 10 ×99 (C)
├─MOA Monetary amount ×1 (M)
├─RFF Reference ×9 (C)
└─DTM Date/time/period ×9 (C)
└─Segment Group 11 ×99 (C)
──├─NAD Name and address ×1 (M)
──├─RFF Reference ×9 (C)
──├─DTM Date/time/period ×9 (C)
──├─FII Financial institution information ×1 (C)
──└─Segment Group 12 ×9 (C)
────├─CTA Contact information ×1 (M)
────└─COM Communication contact ×9 (C)
├─CNT Control total ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D01B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.