UTILMD Utilities master data

TBG1 Supply Chain

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.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. 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 13B 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

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

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

  4. A segment to specify to which market the object relates.

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

  6. A segment to identify the transport service such as express or normal when the message is used to provide transport routing information for multiple transport products. This information may determine which transport route might be used to carry goods from one shipper to one location.

  7. Segment group 1
    Repeat 9

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

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

  8. Segment group 2
    Repeat 99

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

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

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

    4. A segment used to identify attributes of the relevant party, such as additional functions of the sender or receiver.

    5. Segment group 3
      Repeat 9

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

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

  9. Segment group 4
    Repeat 99999

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

    2. A segment providing identification of the quantity in the lower- level object specified, such as a product code.

    3. A segment providing additional identification to the object specified.

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

    5. A segment to specify dates associated with the object.

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

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

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

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

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

    11. A segment for specifying agreement details connected to the object, such as the type of contract.

    12. A segment to specify parties to an instruction, the instruction, or both, such as instruction to read a meter.

    13. A segment to identify the transport service such as express or normal when the message is used to provide transport routing information. This information may determine which transport route might be used to carry goods from one shipper to one location.

    14. Segment group 5
      Repeat 999999

      1. A segment to identify locations connected to the object, such as a metered grid area or a metering point.

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

    15. Segment group 6
      Repeat 99

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

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

    16. Segment group 7
      Repeat 99

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

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

    17. Segment group 8
      Repeat 99999

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

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

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

      4. Segment group 9
        Repeat 99

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

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

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

        4. A segment providing identification of the quantity in the lower-level object specified, such as a product code.

      5. Segment group 10
        Repeat 99

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

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

    18. Segment group 11
      Repeat 99

      1. A segment for specifying monetary amounts related to the object.

      2. A segment for identifying a reference to the amount.

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

    19. Segment group 12
      Repeat 99

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

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

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

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

      5. A segment to indicate the langauges for the specified party.

      6. Segment group 13
        Repeat 9

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

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

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

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

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.