FAQS - Architecture

An operational data store (or “ODS“) is a database designed to integrate data from multiple sources for additional operations on the data. Allowing you to consolidate and analyze transactional data from multiple sources.

Cloverleaf Analytics comes with a pre-built class IV insurance ODS built from the Acord Reference Framework and the OMG data models. It includes property and casualty insurance with line of business specific details for all lines including workers comp.

Absolutely! You can create a cluster of Cloverleaf Analytics servers along with N number of data nodes for grid computing. These capabilities are built right in and allow you to scale by simply configuring our servers through web administration. No need for knowledge of complex grid computing.

What Does The Architecture Of Cloverleaf Analytics Look Like?-Screenshot

What Does The Architecture Of Cloverleaf Analytics Look Like?

Yes, Cloverleaf Analytics comes with support for Apache Hive (Hadoop), Redshift, Snowflake, Mongo DB, etc. built right in.

There are several very important differences between Cloverleaf Analytics and other insurance BI solutions:

An ODS and Data Warehouse –> consolidated operational reporting and analytics.

Most other solutions only include a data warehouse so you cannot do consolidated operational reporting.

Built from insurance industry standard data models like Acord & OMG.

Other BI solutions available on the market have proprietary models that they built to be “generic” and lack policy and claim details.

Line of Business details for all lines built into the models including workers compensation.

Other solutions are generic and do not include line-of-business details. You have to add them to their model and ETL processes. When doing so, all the line-of-business details are on the same risk or coverage record.

This means, for example, that homeowners and auto details are fields on the same risk record. So when populating the fields for a line-of-business (like auto) the other line-of-business fields (like homeowners) are left null and create a “swiss cheese” effect in the records, causing issues in querying data. This is not a problem with Cloverleaf Analytics since line-of-business details are built right in.