Infrastructure Model Version Tracking via Cloud Change Summaries

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Infrastructure modeling software lacks efficient mechanisms for clients to track changes and transitions in infrastructure models over time, making it difficult for users to understand the development and modification history of infrastructure models.

Innovation Solution

A cloud-based process generates and retrieves change summary data and aggregated model version data by applying changesets to construct newer versions of infrastructure models, using APIs to compare briefcases and generate summaries in JSON, BSON, or XML formats, and maintains comprehensive aggregated data with entries for inserted, updated, and deleted elements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional infrastructure modeling software is used, then local copies of the model can be maintained and modified at different devices, but clients do not have visibility into changes made to the infrastructure model over time

Engineering Contradiction:

Improvevisibility into changesVSAvoidchange tracking mechanism

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

A cloud-based service acts as an intermediary between local client devices and the infrastructure model. The service receives briefcases and changesets from clients, applies changesets to construct newer versions, compares briefcases to generate change summaries, and stores aggregated model version data. This intermediary mechanism provides visibility into changes without requiring complex direct connections between all client devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates copies of the infrastructure model in the form of briefcases representing different versions. Each briefcase is a complete copy of the model at a specific version, allowing clients to view and compare different versions without modifying the original. The cloud service maintains these copies and generates change summaries by comparing them.

Inventive Principle:

Principle #26Copying

2Loss of information

If detailed change tracking is implemented, then comprehensive version history can be maintained, but processing requirements and system complexity increase

Engineering Contradiction:

Improvecomprehensive version historyVSAvoidprocessing requirements

Core Design Contradiction:

Loss of informationVSUse of energy by moving object

Solution Approach 1:

The system extracts only the necessary change information by applying changesets to briefcases and generating change summaries that capture modifications between versions. Rather than storing every detail of every change, the system extracts and stores aggregated model version data that represents the essential information needed for version comparison and history tracking.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The cloud-based service performs preliminary processing by applying changesets to construct newer versions of the model before storing them. This preliminary action of constructing and comparing versions allows the system to prepare change summaries and aggregated data in advance, reducing processing requirements when clients need to access version history.

Inventive Principle:

Principle #10Preliminary action

3Loss of information

If all version data is stored and retrieved, then complete model evolution can be accessed, but data retrieval complexity and time increase

Engineering Contradiction:

Improvemodel evolution dataVSAvoiddata retrieval time

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The system segments version history into discrete briefcases, each representing a specific version of the infrastructure model. Changes between versions are segmented into changesets. The cloud service stores these segmented units and generates change summaries that can be retrieved independently, allowing clients to access specific versions or change intervals without retrieving the entire version history.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The cloud-based service performs preliminary comparison of briefcases and generation of change summaries in advance of client requests. By pre-processing and preparing version data, the system can quickly retrieve and deliver change summaries and aggregated model version data when clients make requests, reducing retrieval time.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11455437B1Techniques for generating and retrieving change summary data and aggregated model version data for an infrastructure model

Publication Date: 2022.09.27 BENTLEY SYSTEMS INC

AI summary

Techniques are provided for generating and retrieving change summary data and aggregated model version data for an infrastructure model. A process obtains a briefcase representing a particular version of the infrastructure model and one or more changesets. The process applies the changeset(s) to the briefcase to construct a briefcase that represents a newer version of the infrastructure model. The process compares the briefcases to generate a change summary indicating modifications between the two versions. Further, the process generates aggregated model version data as the infrastructure model transitions to newer versions. The process updates the aggregated model version data utilizing the change summaries such that the aggregated model version data is comprehensive regarding each element that is and was included in the infrastructure model from its genesis to its current state. A client device issues requests to obtain a particular version of the infrastructure model and/or to obtain modifications between versions.