Skip to main content

Introduction

Welcome to the Korint logical engine demo documentation 🙂

Demo features:​

Our goal with this demo is to showcase our ability to handle any policy in real time, across the whole lifecycle of the product (new business and policy modification).

Our demo can handle:

  • Simple, mono-asset as well as complex, fleet-type policies
  • Complete versioning of all the states of the policy
  • Multiple MTA projects in parallel - and instant merging of the Confirmed MTA version
  • Asynchronous MTAs, ie multiple changes with retroactive or deferred effect date
  • Real time building of policy calendar and payment schedule.

With these features, we have built the core logical engine of a Policy Management System that will natively scale to any product 🙂

Note on Demo features:​

Because this is not a real product, we have made several choices that are specific to our Demo environment:

Date simulator

We have created a feature where our engine “pretends” that the user is creating events at a later or earlier date than the real timestamp.

This enables us to model the whole policy lifecycle over 24 months as well as complex policy MTAs, notably multiple assets with delayed / deferred effect date.

This however creates a slightly higher level of complexity compared to a real product where only the “real” timestamp would only ever be used for events.

The key features related to the date simulator are:

  • You can visualize the policy at any date between 01/01/2023 and 31/12/2024. You will instantly access any version of the policy at a given date, choosing to take into account events that happened before or at that date or events that are applied before or at that date. See the simulatedAt and whenAt parameters for more details.
  • You can modify a policy anytime between its creation date and 31/12/2024.
  • You can access an updated payment schedule and detailed pricing calculations for any version of the policy.

However, please bear in mind a few logical constraints specific to our date simulator feature that will not exist in a real life product.

  • You cannot create create events before the simulated date of the last previous event. Example: If you create an asset with a date simulated at 01/09/2023, you cannot create another asset while simulating yourself at 01/08/2023. Events must be created in chronological order (like in real life !)

As a result, please note that some API parameters such as simulatedAt and whenAt are experimental and might not remain in a real product.

Simplified object model

We are handling simplified versions of customers, assets and policy objects. This allows to make the demo faster by avoiding filling of long question sets and allow partners to focus on core features rather than frontend / implementation items.

As a result, we have not expanded to “real” cases like vehicle (15/20 fields per object), companies (10/15 fields). We have also not added “perils” yet (Fire, Theft, Third party,…) or taxes.

Breaking changes

This API is currently a demo version. As such, it is subject to breaking changes at any time as well as changes to the object model or to any other part of the service.