Sample – ACM at RYLC

For our concrete scenario in RYLC, we have built the following use case. RYLC has a department that is selling insurances to everyone who rents an RYLC car. This department uses a very, very old claim-handling tool with lots of business logic in the service layer. The UIs are very old, but it would be much too expensive to rewrite this tooling (several million dollars). Additionally, there are a lot of other small tools involved in the claim regulation process.

RYLC has identified the following problem areas:

• Limited traceability and missing reporting on the status of the hardcoded processes in the tool—generally regarding systems and case related

• Missing guidance of the users while working on claim regulation, especially over system boundaries

• Expert knowledge stays in the dark

• Process automation with normative process models is hard because of the high number of different claim types and their specialties in regulation

• Missing flexibility for mass claims (for hail damage...