Building Project Data Validation System with Scope ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional project management systems for building projects are inadequate in managing risk, data integrity, and stakeholder interactions, leading to issues like schedule delays, cost escalations, and disputes due to poor data input, unreliable data distribution, and lack of real-time collaboration and risk allocation.
Innovation Solution
A computer system that validates and manages building project data by linking stakeholder information with instance data items using scope IDs, ensuring data integrity and real-time collaboration across a controlled platform, and providing mechanisms for risk management and immutable data storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional project management systems allow user customization of basic configuration, then system adaptability improves, but data integrity deteriorates due to poor data input and incomplete model data
Solution Approach 1:
The patent introduces a centralized project management system that acts as an intermediary between multiple stakeholders (owners, architects, contractors, etc.). This system enforces standardized data input protocols and validation rules, preventing poor data entry while maintaining system adaptability through controlled customization options. The intermediary controls what data can be customized and ensures all inputs meet quality standards before processing.
Solution Approach 2:
The system implements parameter validation and standardization by defining specific data requirements, formats, and validation rules for all project parameters. Instead of allowing free-form user input, the system enforces standardized parameter structures (e.g., standardized WBS codes, standardized data formats) that ensure data integrity while still allowing customization within defined boundaries.
2Productivity
If federated computer systems are used to share building project data, then data distribution capability improves, but data reliability deteriorates due to false, misleading and unreliable data
Solution Approach 1:
The patent implements comprehensive feedback mechanisms including automated validation checks, data quality monitoring, and stakeholder verification processes. The system continuously monitors data inputs from all stakeholders, validates them against predefined criteria, and provides feedback loops for correction. This ensures that distributed data maintains high reliability while enabling broad participation from multiple project stakeholders.
Solution Approach 2:
The system performs preliminary validation and verification actions before data is fully integrated into the project management system. Data from stakeholders undergoes pre-processing checks, format validation, and completeness verification before being accepted into the centralized system. This preliminary action prevents false or misleading data from entering the distribution network.
3Ease of operation
If conventional systems lack technical barriers against counterfeit derivatives of project data, then data accessibility improves, but project control deteriorates due to unauthorized changes
Solution Approach 1:
The centralized system acts as an intermediary that controls all data access and modification operations. While data remains highly accessible to authorized stakeholders through the system interface, all changes must pass through the intermediary's validation and approval processes. This maintains ease of operation for legitimate users while preventing unauthorized counterfeit derivatives and unauthorized changes.
Solution Approach 2:
The system implements preliminary authorization checks and digital signature validation before allowing any data modifications or derivatives to be created or distributed. Authorized stakeholders receive digital credentials that enable them to access and modify data within their scope of authority, while the system pre- validates all modification requests against project constraints and stakeholder permissions.
4Device complexity
If conventional systems lack real-time interaction capability, then system simplicity improves, but risk management deteriorates due to inability to manage escalation risk
Solution Approach 1:
The patent creates a universal platform that handles multiple functions including real-time collaboration, risk monitoring, data validation, and stakeholder coordination within a single integrated system. While the system performs complex risk management and real-time monitoring functions, it presents a unified, user-friendly interface that maintains relative simplicity for end users. The multi-functionality consolidates what would otherwise require multiple separate systems.
Solution Approach 2:
The system implements real-time feedback loops that continuously monitor project parameters, stakeholder interactions, and risk indicators. When escalation risks are detected, the system automatically alerts relevant stakeholders and can trigger predefined mitigation protocols. This real-time feedback capability enables effective risk management while maintaining system simplicity through automated responses rather than requiring complex manual intervention processes.
Data Source
AI summary
A method of validating an electronic computer model of a building project includes: providing one or more electronic building project databases storing: (i) stakeholder information, (ii) element data; (iii) material data; (iv) specification data; (v) requirement data; (vi) procurement data and a plurality of instance data items are provided by at least one stakeholder of the first subgroup of stakeholders; generating a scope ID associated with each instance data item (c) storing the scope ID; (d) receiving a first electronic computer model including a plurality of existence objects associated with the first building project; (e) validating, the first electronic computer model (f) receiving updated data; (g) repeating step (e)-(f) until no alert is generated; (h) generating and transmitting a certification query; (j) receiving, a certification message from each stakeholder and (k) storing, in immutable form, the plurality of instance data items and respective scope ID of each instance data item.