Sub-Board Template Application for Multi-Structured Collaborative Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current project management software applications are inefficient in managing complex operations across multiple employees and departments, lacking features for customizable data types and real-time data integration, which hinders optimal resource allocation and management.

Innovation Solution

A system that includes a processor configured to display customizable table headings, generate hybrid table templates pre-populated with real-time data, and represent data via multi-structured tables, enabling users to customize headings, associate data types, and integrate data from preexisting tables, thus enhancing data management and collaboration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If project management software uses standardized table structures, then system simplicity is maintained, but adaptability to customize data types and headings is reduced

Engineering Contradiction:
Improvecustomizability of data types and headingsVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically adapts table structures based on user needs. When users customize headings or data types, the system automatically adjusts the underlying data model, relationships, and validation rules. This dynamic reconfiguration allows the same platform to support both standardized and customized structures without requiring separate systems for each case.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention allows users to modify parameters such as column headings, data types, and field properties. When these parameters are changed, the system automatically updates the database schema, user interface, and business logic to reflect the new configuration. This parameter-driven approach enables flexible customization while maintaining system integrity through automated consistency management.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If manual data entry and table creation is required, then system simplicity is maintained, but time consumption and operational efficiency deteriorate

Engineering Contradiction:
Improveoperational efficiencyVSAvoidtime for data management tasks
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating table structures, data models, and user interfaces based on high-level user specifications. Instead of requiring users to manually create each table and field, the system pre-configures the necessary database schemas, relationships, and UI elements, significantly reducing the time required for data management setup and ongoing operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides self-service capabilities where users can define custom data types and headings through simple interface interactions, and the system automatically handles the complex tasks of schema generation, data validation rule creation, and interface updates. This self-service approach eliminates the need for manual configuration of technical details, allowing users to focus on business logic rather than system administration.

Inventive Principle:
Principle #25Self-service

3Reliability

If real-time data integration from preexisting tables is implemented, then data accuracy and collaboration are improved, but system complexity and computational resources increase

Engineering Contradiction:
Improvedata accuracyVSAvoiddata integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges data from multiple preexisting tables into unified views while maintaining real-time synchronization. By combining data access layers and using shared underlying data models, the system achieves real-time integration without duplicating data storage or creating complex independent synchronization mechanisms. The merged views present integrated data while the backend maintains efficient separate table structures.

Inventive Principle:
Principle #5Merging (Combining)

4Ease of operation

If customizable data types and automatic template application are implemented, then ease of operation is improved, but processing overhead and system complexity increase

Engineering Contradiction:
Improveuser interface simplicityVSAvoidprocessing overhead
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system uses templates that store pre-configured data type definitions, validation rules, and interface patterns. When users need new tables or fields, the system copies existing templates and automatically applies them, generating the necessary database structures and UI elements. This copying mechanism reduces processing overhead by reusing proven configurations rather than creating everything from scratch, while maintaining ease of operation through template-based rapid deployment.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11347721B2Digital processing systems and methods for automatic application of sub-board templates in collaborative work systems
Publication Date: 2022.05.31 MONDAY COM LTD
  • US11347721B2 patent drawing
  • US11347721B2 patent drawing
  • US11347721B2 patent drawing

AI summary

Systems, methods, and computer-readable media for representing data via a multi-structured table are disclosed. The systems and methods may involve maintaining a main table having a first structure and containing a plurality of rows; receiving a first electronic request for establishment of a first sub-table associated with the main table, wherein the electronic request includes column heading definitions and wherein the column heading definitions constitute a second structure; storing the second structure in memory as a default sub-table structure; associating the first sub-table with a first row in the main table; receiving a second electronic request for association of a second sub-table with a second row of the main table; performing a lookup of the default sub-table structure following receipt of the second electronic request; applying the default sub-table structure to the second sub-table.