Connection of an additional client to a car insurance tariff interface
Brief description
The customer has a pricing interface that car manufacturers can use to sell insurance directly when selling a car. A new client is to be connected to this interface. For this purpose, separate insurance rates are created for the client and the missing process steps are implemented. The technical requirements for access, such as certificates and firewall activations, need to be created.
Supplement
The application has been developed using Spring Boot and runs in a Kubernetes cluster hosted on AWS. For the sales department of a car manufacturer as a new client, general technical access to the interface must first be enabled. This requires IP activations and the setup of certificates for secure access. Since separate insurance rates are created for the new client, these must be stored in the system. Some of the existing processes must be adapted or expanded to match the new client's requirements.
Subject description
Several clients have already been connected via the interface, so that a distinction between processes and tariffs for different clients is already available. Since each client has different insurance rates and, in some cases, different processes, it is necessary to check what changes to the existing system are required for the new client. This is done in close consultation with the client, as the interface only provides the data, but the UI must be created by the client itself. To this end, the functional and technical processes between the UI and the interface must be well coordinated.