One crucial initiative at this stage was the launch of an “AI factory” to standardize processes, scale up model deployment, and share knowledge and best practice. The planning of this unit was a deliberately inclusive exercise that sought views from business users, data engineers and the IT department, which had been charged with implementing the technology. Their objective was to move away from piecemeal AI initiatives to a more systematic approach that involved working with partners on business problems and value cases.
Key elements of the AI factory include a “feature store,” which is a repository of clean, standardized data and a system to allow data scientists to access features of the model. It also includes an AI platform, a set of tools, guidelines and templates that save data scientists’ valuable time, and an MLOps platform that transforms the algorithms they develop into consumable solutions. A model governance framework is also important, setting out requirements for performance monitoring.
Over time, RIMAC has also begun to develop a federated model that supports the scaling of its AI activities. As business units began to compete more strongly for attention from the CoE, they also began to push for distributed capabilities. RIMAC began to develop a model for this in its health insurance business, where a dedicated team of 10 worked on organizing and structuring claims data. One positive outcome was the launch of an incentive program to encourage customers to adopt healthier lifestyles.
Overcoming the challenges
RIMAC’s progress on AI may sound straightforward, but the reality was anything but. At each stage of the project, all those involved faced significant challenges. First, they uncovered a number of gaps in the data, both in terms of availability and quality, with only limited data sharing across business units. While this might, at a glance, seem inconsequential, there could be significant commercial repercussions. For instance, RIMAC’s health insurance business knew whether a customer had a child, but the life insurance business, ideally placed to sell important protection policies to such a customer, did not receive this data.
Another problem was organizational dynamics. Having split its capabilities between advanced analytics (within the marketing function) and data engineering (IT), RIMAC had to manage the tensions that arose between the two teams (a not uncommon occurrence, with the latter responsible for the complex task of delivering clean, usable data, and the former under pressure to deliver quickly for the business).
Indeed, increased demand from the business has become a significant challenge. The CoE initially focused on quick wins, particularly in vehicle and health insurance, but life insurance leaders saw the bigger picture and wanted a share of the benefits. As a natural consequence of this, the demands on the team have grown very rapidly.
Other obstacles include a lack of alignment of the objectives set for the CoE and for individual business units. This has sometimes led to issues around prioritization and co-operation. Similarly, defining and accounting for the value created by the team’s AI models has proved challenging.