Finding the needle in a haystack of more than 100,000 variations
Today, tech giants like Google and Amazon are setting standards at a pace not every industry can keep up with. Especially in times of same-day delivery and video-on-demand, the Service Level Agreement (SLA) to resolve uncomplicated cases within seven days seems like half an eternity.
But it's more complicated than it looks. If you look at property and vehicle damage alone, UNIQA's internal processes are highly complex. Reported claims are processed across five individually specialized locations.
These locations have their own team mailbox which receives damage reports via email, fax, or physical mail. These damage reports are in turn assigned to a responsible clerk within the location.
At the same time, UNIQA’s system landscape resembles a widely-branched root system: First, there is the core system for the claims processing, which in turn interacts with numerous other systems. On top of that, UNIQA has separate systems for incoming mail, EDF (electronic document flow), document management, expert commissioning, and field claim services.
"There was a lot of friction between systems that actually have to work together. Our primary concern was to get a better overview and to find out where the process was stalling," Fiedler recalls.
With the focus on elementary insurance, Celonis was able to identify over 100,000(!) different process variants in the POV phase alone.