Schema-less Handover Repository for Construction Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

General ETL technologies are inadequate for automating handover processes in engineering and construction projects due to complexities such as large amounts of unstructured information, loosely related data sources, and a significant information modeling gap between design/construction and operation/maintenance systems, making it difficult to define a common schema and requiring deep reconfiguration for each project.

Innovation Solution

A schema-less building information model, known as the Handover Repository, is used with a 2-step script-based transformation process and Information Stitching technology, along with standard exports via COBie and web programming APIs, to manage handover information, eliminating the need for predefined information modeling knowledge and accommodating unique project data structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If general ETL technologies are used for handover automation, then data extraction and loading capabilities are provided, but the system cannot handle unstructured project information, loosely related data sources, and information modeling gaps

Engineering Contradiction:
Improveability to handle unstructured project informationVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (handover repository with schema-less information model) between the diverse project data sources and the target O/M systems. This intermediary handles the complexity of unstructured data and loose relationships, allowing the ETL system to adapt to various project formats without requiring complex reconfiguration for each project type.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter of data structure flexibility by using a schema-less information model that can accommodate unstructured project information. This allows the system to handle varying data formats, relationships, and structures from different project sources without being constrained by rigid predefined schemas.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If a common schema is defined for ETL processing, then data standardization is achieved, but the system cannot accommodate unique project data structures and owner-specific requirements

Engineering Contradiction:
Improveaccommodation of unique project data structuresVSAvoiddata transformation precision
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent implements a dynamic information model where the schema is not fixed but adapts to the specific project data structures and owner requirements. The system can dynamically adjust the information model to match unique project needs while maintaining data transformation precision through automated scripting and information stitching techniques.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The transformation process is segmented into two distinct steps: first transforming project data to a semi-normalized handover repository, then transforming from the repository to owner-specific specifications. This segmentation allows each step to handle different requirements independently, maintaining precision while accommodating uniqueness.

Inventive Principle:
Principle #1Segmentation

3Reliability

If deep reconfiguration of ETL solution is performed for each project, then unique project requirements are met, but the process becomes economically impractical

Engineering Contradiction:
Improvehandover automation reliabilityVSAvoidhandover process efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a universal handover repository information model that can serve multiple project types and owner requirements without requiring deep reconfiguration. The schema-less design and automated information stitching enable the system to handle diverse projects reliably while maintaining high productivity through standardized processes.

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

Solution Approach 2:

The system performs preliminary actions by establishing the handover repository with a flexible information model before specific project data processing begins. This preliminary setup enables automated handling of unique project requirements without requiring time-consuming reconfiguration for each project.

Inventive Principle:
Principle #10Preliminary action

4Manufacturing precision

If information modeling knowledge is required to manage transformation, then transformation accuracy is improved, but the system becomes harder to use and operate

Engineering Contradiction:
Improvetransformation accuracyVSAvoidsystem usability
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements a self-service system where the automated ETL process handles transformation accuracy internally without requiring users to possess information modeling knowledge. The system automatically performs information stitching and transformation while maintaining accuracy, making it easy to operate for users regardless of their expertise in information modeling.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10740346B2System and method for automating information handover from facility project to operations/maintenance
Publication Date: 2020.08.11 AGILE HANDOVER & AUTOMATION SOLUTIONS LLC
  • US10740346B2 patent drawing
  • US10740346B2 patent drawing
  • US10740346B2 patent drawing

AI summary

In one embodiment, a technique is provided for automating handover information from project (construction & design) to operation/maintenance. A schema-less repository is defined for holding handover asset objects and governing transformation automation. An information stitching method is defined for multiple-sourced project data integration and incorporating owners' requirement into the repository. A 2-step script-based transformation process is provided to encapsulate information modeling knowledge from a transformation definition.