972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Master data

UTILMD Utilities master data

The UN/EDIFACT message parties in a utilities infrastructure use to exchange characteristics of objects and services, or request them.

Sent by
Grid operator, supplier or other utility market participant
Received by
Another utility market participant
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT UTILMD message?

UTILMD is the UN/EDIFACT utilities master data message. The directory defines it as a message sent between responsible parties in a utilities infrastructure to exchange the characteristics of objects and services, and it may also be used to request information.

In liberalized energy markets, UTILMD carries processes such as customer switching, supply start and end, and changes to metering point data. Grid operators and suppliers depend on it to keep the register of who supplies which metering point accurate, under deadlines set by national market rules.

How the EDIFACT UTILMD message worksDiagram of the UN/EDIFACT UTILMD Utilities master data message. Grid operator, supplier or other utility market participant sends it to another utility market participant. It usually starts the exchange. It is usually followed by MSCONS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT UTILMD message worksUtilities master data: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeUTILMDSENDERGrid operator, supplieror other utility marketparticipantRECEIVERAnother utility marketparticipantCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYMSCONSMetered servicesconsumption report2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage UTILMDUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADIDEBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for UTILMD. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT UTILMD message worksDiagram of the UN/EDIFACT UTILMD Utilities master data message. Grid operator, supplier or other utility market participant sends it to another utility market participant. It usually starts the exchange. It is usually followed by MSCONS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT UTILMDmessage worksUtilities master data: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeUTILMDSENDERGrid operator,supplier or otherutility marketparticipantRECEIVERAnother utilitymarketparticipantCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYMSCONSMetered services consumptionreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message UTILMD (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADIDEBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for UTILMD.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends UTILMD, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around UTILMD and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Registering a customer's supply start with a new supplier
  • Ending a supply relationship
  • Updating metering point master data

Where it fits in the message flow

This message UTILMD Utilities master data
Usually followed by MSCONS Metered services consumption report

Structure

Mandatory segments in UTILMD (directory D.21A)

In UN/EDIFACT directory D.21A, the UTILMD message has 54 segment positions arranged in 13 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • UNT

Practical example

UTILMD in practice

A household switches electricity supplier in Germany. The new supplier sends the grid operator a UTILMD registering the supply start at the metering point from a given date. The grid operator confirms, notifies the previous supplier of the end of its supply, and sends meter readings to both with MSCONS.

Implementation

Implementation considerations for UTILMD

  • Follow the national market process descriptions and deadlines.
  • Use standard metering point and market party identifiers.
  • Process confirmations and rejections promptly.
  • Keep master data synchronized with billing systems.

How ECOM helps

Automate UTILMD with ECOM

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related master data messages

All 11 master data messages

Need help with UTILMD?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us