Insurance Product Graph Compiler for Immutable Rate Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Insurance products face challenges in development and maintenance due to complex logic and frequent regulatory changes across jurisdictions, making it difficult to ensure immutability, traceability, and reproducibility of rate computations, while also extracting and storing useful data from insurance policies.

Innovation Solution

A system that represents insurance products as directed graphs, transforming source code into graph object artifacts using a meta-model with a data model, behavior components, and compute types, and executes them through a compiler and execution engine with a web-based runtime environment, ensuring immutability and efficient data handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If insurance products are implemented using general-purpose programming languages, then the products can be developed and executed, but the complex logic and frequent regulatory changes make maintenance costly and difficult to ensure immutability, traceability, and reproducibility

Engineering Contradiction:
Improveimmutability, traceability, and reproducibility of rate computationsVSAvoidcomplex logic and cascading effects on components
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the insurance product into a directed graph data model where the product is divided into nodes representing insurance entities (e.g., insured, vehicle, coverage) and edges representing relationships between them. This segmentation allows each component to be independently defined and modified without cascading effects, enabling regulatory changes in one area without impacting the entire product structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a domain-specific language (DSL) compiler as an intermediary layer between the high-level insurance product requirements and the underlying execution system. The DSL provides abstractions that automatically handle immutability, traceability, and reproducibility requirements, shielding developers from the complexity of implementing these features in general-purpose programming languages.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the data model of the insurance product is modified to accommodate regulatory changes, then the product can adapt to new requirements, but the changes impact many different components and are difficult to implement

Engineering Contradiction:
Improveability to accommodate regulatory changesVSAvoidease of implementing changes
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The directed graph data model segments the insurance product into independent nodes and edges, where each node represents a discrete insurance entity. This segmentation enables localized modifications - regulatory changes can be applied to specific nodes or edges without requiring changes to the entire data model or cascading updates across multiple components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a dynamic configuration system where the directed graph data model can be modified at runtime through configuration files or code updates. The system supports hot-swapping of graph definitions, allowing regulatory changes to be deployed without recompiling the entire product, thus improving adaptability while reducing implementation complexity.

Inventive Principle:
Principle #15Dynamics

3Reliability

If insurance products are represented as directed graphs and transformed through multiple compilation steps, then immutability and data integrity are maintained, but the compilation process complexity increases

Engineering Contradiction:
Improvedata integrity and immutabilityVSAvoidcompilation process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary validation and type checking during the compilation process to ensure data integrity and immutability before execution. The DSL compiler includes built-in checks that verify graph structure, node types, and edge relationships during compilation, catching errors early and preventing runtime issues without requiring complex runtime verification mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates an intermediate representation (IR) of the directed graph during compilation that serves as a verified copy of the source definition. This IR is then used for execution, ensuring that the runtime system operates on a validated structure. The copying process includes type checking and structure verification to maintain data integrity while simplifying the runtime complexity.

Inventive Principle:
Principle #26Copying

4Productivity

If a meta-model with data model, behavior components, and compute types is used to define insurance products, then the products can be efficiently executed, but the initial development and learning curve increase

Engineering Contradiction:
Improveexecution efficiencyVSAvoidmeta-model structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal meta-model that can represent different types of insurance products (auto, property, liability) using the same directed graph structure and node types. This universal framework provides execution optimizations that work across all product types, improving productivity through efficient graph traversal and computation while reducing the need for product-specific code paths.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The DSL compiler acts as an intermediary that translates the complex meta-model definitions into optimized execution code. The compiler handles the complexity of the meta-model structure, performing type checking, scope resolution, and code generation that transforms the high-level directed graph definition into efficient runtime representations, thereby improving execution efficiency while shielding developers from the underlying complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20230008057A1System for representing insurance products as graphs
Publication Date: 2023.01.12 INSURANCE QUANTIFIED LLC
  • US20230008057A1 patent drawing
  • US20230008057A1 patent drawing
  • US20230008057A1 patent drawing

AI summary

A system for representing insurance products as directed graphs and transforms the directed graphs into graph object artifacts for execution. The system includes a compiler, an execution engine and a web-based runtime environment. The compiler transforms source code defining an insurance product as a directed graph into a plurality of nodes, where each node represents one of a computation and an input, and outputs a graph object artifact. The execution engine has an execution model derived from the graph object artifact that is loaded into memory and an application program interface that provides an interface to the web-based runtime environment. The web-based runtime environment provides a layer of abstraction between the execution engine and external services or systems.