Multi-Region Risk Data Store Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual updating of multi-region risk relationship electronic records is time-consuming and prone to errors, especially when dealing with numerous countries and diverse types of information, and existing macro-based spreadsheet tools are inefficient in data integration and accuracy.

Innovation Solution

A system and method that utilize a back-end application server to access a multi-region risk relationship data store, allowing for dynamic configuration and automatic assembly of electronic records through an interactive user interface, with a standalone risk calculation unit to ensure accuracy and reduce manual input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updating of electronic records is performed, then flexibility in editing individual records is maintained, but time consumption and error rates increase substantially

Engineering Contradiction:
Improveaccuracy of electronic recordsVSAvoidtime to update electronic records
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the multi-region risk relationship data into hierarchical components (global attributes and local attributes for each region). This segmentation allows automated processing of individual regions while maintaining overall relationship integrity, resolving the contradiction by enabling both accuracy through structured data handling and efficiency through automated region-by-region processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates and maintains electronic records as digital copies of risk relationship data, allowing automated retrieval, validation, and updating without manual re-entry. This copying approach ensures accuracy through consistent data representation while reducing time consumption by eliminating repetitive manual data input across multiple regions.

Inventive Principle:
Principle #26Copying

2Productivity

If macro-based spreadsheet toolkits are used, then data processing capability is provided, but excessive manual input and repetitive operations are required

Engineering Contradiction:
Improvespeed of creating electronic recordsVSAvoidmanual input effort required
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system implements self-service through automated data validation, consistency checking, and record assembly. The back-end application server automatically processes risk relationship data, validates attributes against defined schemas, and generates electronic records without requiring manual macro operations. This resolves the contradiction by maintaining high productivity through automation while eliminating repetitive manual input efforts.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual spreadsheet macro operations with an automated back-end application server that programmatically processes risk relationship data. This substitution eliminates the need for users to manually create and execute complex spreadsheet macros, thereby maintaining productivity while dramatically reducing manual input effort and operational complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If data integration and cleansing are performed manually, then data quality can be maintained, but system integration capabilities remain limited

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem integration capability
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges data integration, validation, and cleansing functions into a unified back-end application server architecture. This integration combines multiple previously separate processes (data retrieval, validation, transformation, and record generation) into a cohesive automated system, thereby maintaining data accuracy through comprehensive validation while enhancing system integration capabilities across multiple regions and data sources.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The back-end application server is designed as a universal platform that handles multiple functions: data retrieval from various sources, validation against hierarchical schemas, automated cleansing, and electronic record generation. This multi-functional approach maintains data accuracy through consistent validation rules while improving system integration by providing a single platform that works across all regions and data types.

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

4Measurement precision

If comprehensive validation and confirmation processes are implemented, then data accuracy is improved, but processing time may increase

Engineering Contradiction:
Improvevalidation accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary validation and consistency checking during data entry and before final record generation. By validating attributes against hierarchical schemas upfront and identifying potential issues early, the system ensures high measurement precision without adding significant processing time to the final record creation, as the validation occurs incrementally rather than as a separate time-consuming step.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11694274B2Processing system to facilitate multi-region risk relationships
Publication Date: 2023.07.04 HARTFORD FIRE INSURANCE CO
  • US11694274B2 patent drawing
  • US11694274B2 patent drawing
  • US11694274B2 patent drawing

AI summary

A multi-region risk relationship data store may contain electronic records representing a plurality of multi-region risk relationships and, for each multi-region risk relationship, an electronic record identifier and a set of multi-region attribute values including a plurality of hierarchical local risk relationship attribute values. A back-end application computer server may receive an indication of a selected risk relationship and display at least some of the associated multi-region attribute values. The server may receive adjustments to some of the multi-region or local risk-relationship attribute values, and displayed information may be automatically and dynamically configured based on the received adjustments and a standalone risk calculation unit. At least some local risk relationship attribute values may be replicated for multiple regions. When adjustments have been completed, the server may automatically assemble a multi-region risk relationship document.