No-Code Enterprise Software System for Rapid Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Implementing enterprise software is hindered by the need for extensive customization, high costs, and complex data migration and integration, particularly in big-data ecosystems, which requires skilled developers and leads to inefficient ongoing modifications and security challenges.

Innovation Solution

A no-code enterprise application software system that uses a database with non-relational engines, entity services, query engines, rules engines, and data orchestrators to enable configuration without programming, allowing non-technical users to manage business processes and data through graphical interfaces, ensuring data consistency and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional customized enterprise software is used, then high customization capability is achieved, but implementation cost and time increase significantly

Engineering Contradiction:
Improvecustomization capabilityVSAvoidimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-configures enterprise software applications with standardized data models, business processes, and integration templates before deployment. This preliminary setup allows organizations to rapidly implement software without extensive customization, reducing implementation time while maintaining adaptability through configurable parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a universal enterprise software platform that can serve multiple business functions and industries through a common architecture. The system provides multi-functionality by accommodating various business processes and data types within a single standardized framework, eliminating the need for organization-specific customizations.

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

2Adaptability or versatility

If traditional customized enterprise software is used, then high customization capability is achieved, but implementation cost increases

Engineering Contradiction:
Improvecustomization capabilityVSAvoidimplementation cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent pre-configures enterprise software applications with standardized data models, business processes, and integration templates before deployment. This preliminary setup allows organizations to rapidly implement software without extensive customization, reducing implementation time while maintaining adaptability through configurable parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a universal enterprise software platform that can serve multiple business functions and industries through a common architecture. The system provides multi-functionality by accommodating various business processes and data types within a single standardized framework, eliminating the need for organization-specific customizations.

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

3Loss of time

If no-code development platforms are used, then implementation cost and time are reduced, but customization capability decreases

Engineering Contradiction:
Improveimplementation timeVSAvoidcustomization capability
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent enables configuration of enterprise software through parameter changes rather than code modification. Users can adjust business logic, data models, and processes by modifying configuration parameters within the standardized platform, achieving customization without requiring programming expertise or extensive development time.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If data migration from legacy systems is performed, then data integration is achieved, but system complexity increases

Engineering Contradiction:
Improvedata integration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces standardized data intermediaries and integration layers that mediate between legacy systems and the new enterprise software platform. These intermediaries translate and normalize data from various legacy formats into the standardized data model, enabling integration without directly complicating the core system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

5Manufacturing precision

If skilled developers are involved in customization, then customization quality is improved, but ongoing maintenance cost increases

Engineering Contradiction:
Improvecustomization qualityVSAvoidmaintenance cost
Core Design Contradiction:
Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The patent enables business users to perform self-service customization of enterprise software applications through configuration interfaces. Users can modify business logic, data models, and processes without requiring developer intervention, thereby maintaining customization quality while eliminating ongoing dependency on skilled developers for minor adjustments.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11544266B1Methods and systems for efficiently and rapidly generating highly customized cloud-based enterprise software applications
Publication Date: 2023.01.03 MEZOCLIQ LLC
  • US11544266B1 patent drawing
  • US11544266B1 patent drawing
  • US11544266B1 patent drawing

AI summary

Disclosed herein are system, method, and computer-readable device embodiments of a no-code, enterprise application software (EAS) system. The system may include a database configured to store a data model including one or more parties, governors and steps. The database may be further configured to store a plurality of rules in a rules table. The system may also include a rules engine, coupled to the database, where the rules engine is configured to query a rules table utilizing a compound index to locate a rule to execute and execute the rule. Further included in the system may be a query engine coupled to the database for converting user defined queries into database-specific queries and a report engine coupled to the database for generating reports based on the data stored in the database.