Rule-Based Design Scheduling System for Build Projects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual processing of complex building project schedules is time-consuming, prone to human error, and often results in delays and additional costs due to the need for frequent updates and the complexity of managing thousands of activities across multiple subcontractors and locations.

Innovation Solution

A system and method for processing building project schedules using a graphical user interface (GUI) where a server identifies and processes schedule formats, allows users to create parsing and classification rules, maps activities to locations and work phases, and generates a design schedule, enabling quicker and more accurate updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual processing of master schedules is used, then human review and control are maintained, but processing time increases to a week or longer and human error occurs

Engineering Contradiction:
Improveaccuracy of schedule processingVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces the mechanical manual review process with an automated computer-based system that uses software algorithms to parse, validate, and process schedule data. The system automatically identifies activities, extracts parameters, checks for errors, and generates processed schedules without human intervention, thereby eliminating human error while dramatically reducing processing time from weeks to minutes or hours.

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

Solution Approach 2:

The system enables self-service processing where the schedule data automatically validates itself through built-in business rules and constraints. The software independently checks for logical errors, conflicts, and compliance with project requirements without needing manual verification, allowing the schedule to process and validate itself autonomously.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If manual review of thousands of activities is performed, then detailed human control is maintained, but the process is prone to human error and requires massive time requirements

Engineering Contradiction:
Improveease of schedule updatesVSAvoiderror rate in processing
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent replaces manual human review operations with automated computational processes that systematically examine every activity in the schedule. The software uses algorithms to parse activity data, extract parameters, validate against business rules, and identify errors automatically, providing both ease of operation through automation and high reliability by eliminating human error in processing thousands of activities.

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

3Productivity

If schedules are updated once or twice per month, then processing workload is manageable, but delays and downstream disruptions occur due to outdated information

Engineering Contradiction:
Improveschedule update frequencyVSAvoidconstruction delays
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent enables continuous schedule processing and validation rather than periodic updates. The automated system can process schedule data as it is generated or modified, providing ongoing validation and immediate identification of issues. This continuous processing eliminates delays by ensuring schedule accuracy is maintained at all times rather than only during monthly review cycles.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system provides self-service automatic validation that continuously checks schedule data for errors and conflicts without requiring scheduled manual intervention. The automated processing occurs continuously in the background, immediately detecting and flagging issues as they arise, thereby preventing construction delays caused by outdated or erroneous schedule information.

Inventive Principle:
Principle #25Self-service

4Productivity

If automated processing is implemented, then processing speed increases, but system complexity increases requiring format recognition and rule creation

Engineering Contradiction:
Improveschedule processing speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by providing pre-configured templates, standard formats, and built-in business rules that are prepared in advance. The system comes with predefined parsing rules, validation criteria, and processing logic that automatically apply to common schedule formats, reducing the complexity of implementation while maintaining high processing speeds.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system achieves universality by designing a multi-functional platform that can handle multiple schedule formats, parsing methods, and validation rules through a single integrated software solution. The automated processing engine is configured to recognize and process various standard schedule formats using universal parsing algorithms, reducing system complexity while maintaining high productivity across different project types and formats.

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

Data Source

PatentUS20240242183A9Rule-based design scheduling system for processing build project schedules
Publication Date: 2024.07.18 EVOLVE MEP LLC
  • US20240242183A9 patent drawing
  • US20240242183A9 patent drawing
  • US20240242183A9 patent drawing

AI summary

Systems and methods are described for processing a schedule for a build project. In an example, a server can receive a data file that includes the schedule. The server can extract locations from the schedule and map activities in the schedule to their corresponding locations. The server can also map each activity to a drawing type based on the type of activity. Each drawing type can have an associated work phase, and the server can map work phases to locations based on the activity mapped to their corresponding drawing types. The server can then map each activity to a corresponding work phase at its location based on the previous mappings. The server can cause a graphical user interface to display a design schedule of the build project that includes a location breakdown structure with each location's work phases, each work phase's activities, and each work phase's drawing types.