Check the error code against master data
Exception MK-7742, meter number differs by 2 digits
Energy
The clock keeps running, and nothing can be backdated.Open agent
Enlarge demo
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
The registration goes to the grid operator as a UTILMD and comes back as an APERAK with an error code. The specialist opens the exception, looks up the market location in the billing system and checks the meter number and address against the counterparty's records. Then she checks the process description for the deadline that now applies. Only then can she write the new message.
24 hours
switching deadline
A supplier switch must be processed within one day.
6
error codes
Six different APERAK responses come in during a single morning.
17 minutes
per exception
Compare master data, look up the rule, build the response message.
3
system switches
Market partner data, billing system and process description are not in one place.
The 55% reduction in manually handled exceptions comes from cases where cause, rule and draft response are already attached before anyone opens them.
This agent's headline figure is 55% fewer manual exceptions. The switching deadline comes from the regulated procedure; the error codes and minutes per exception describe a typical morning in market communication and are illustrative, not measured.
The agent attaches the suspected cause, the applicable process rule and a resolution path to the exception; the market communication specialist decides whether the corrected message goes out to the market.
Exception MK-7742, meter number differs by 2 digits
Start of supply, to be processed by 14 March, 07:12
utilmd_MK-7742.xml, 2 digits of the meter number corrected
It saves the corrected UTILMD to the exception as a draft. The market communication specialist sends it from the market communication system.
For exception MK-7742 it names the field, the value sent and the counterparty's value. Billing enters the corrected meter number in the system of record.
It derives the assumption from the error code and the data comparison, and says what it is based on. If the grid operator gives a different reason, the grid operator's account takes precedence.
Connected systems
EDIFACT market communication
billing system
exception management
Operations
Deployment model
Data processing
Responsible teams
How quickly is the Market Communication Exception Agent ready to use?
Where is the data processed?
Where does the figure “55% fewer manual exceptions” come from?
All agents
50%
less manual review effort
Billing, network operators
50%
less review effort
Grid operations, billing, regulation
60 to 75%
less data entry effort
Grid services, customer service
60%
fewer corrections
EEG, Billing
55%
faster case resolution
Customer service, billing, legal
up to 65%
less handling time
Customer service, billing