1. Modularity
The value chain of life insurance companies is subject to a wide range of expectations and requirements. Modern core systems must therefore satisfy various stakeholders.
On the one hand, there is a need for competitive products and product innovations and, on the other hand, for cost-effective processes. In addition, there are requirements from the areas of law, compliance and risk management.
Flexible product models can be one solution. These must be able to completely map today's product world and its business transactions and at the same time be future-proof.
If you continue to consistently think of modularity, algorithms, products and processes can all be decomposed. The result is a quasi modular system. The parts of the modular system must then be integrated into a clear technical model. Attributes and methods require clear technical designations.
This results in the following advantages:
- The core system does not exist only as a monolith.
- Nor does it consist entirely of implemented code.
- Reusability of recurring business transactions and product characteristics.
But what concrete benefits do these advantages offer?
- For example, a modular system can be modeled in Eclipse by employees with expertise, but no programming knowledge. Keyword: "The Programming Actuary"
- From the point of view of the internal control system (ICS), this avoids head monopolies and sovereign knowledge. This is an objective that is also frequently cited in the context of tenders.
- The sustainable reuse of recurring product characteristics and business transactions leads to shorter time-to-market lead times and economies of scale.
- There is also a substantial and complete time-to-market completion, as not only the tariffs, but also all related business transactions are already fully available at market launch.
- A necessarily creative "definition of ready" with an actual degree of completion below 100%, which is due to market pressure and causes the backlog to swell ever further, is a thing of the past.
Java technology, for example, offers independence from individual operating systems. Customers should be able to choose between different providers. This applies to databases as well as to application servers.
3. High integration capability
Connection of external systems:
Modern LV systems must be easy to integrate into the existing system environment. As a rule, various peripheral systems must be connected. Typically, these are the following system types (excerpt):
- DWH-systems
- Partner systems
- Printing- and textsystems
- Commission systems
- IAM systems
- Mailbox systems
- Collection/disbursement systems
- Workflow systems
- Reporting systems to government agencies
