Modular Data Processing Architecture for ERP Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large-scale business applications face challenges in efficiently processing data while maintaining low operating costs, especially in enterprise resource planning (ERP) systems, due to increased complexity and the need for high-performance computing systems to handle large volumes of information and compliance requirements.
Innovation Solution
A computer system architecture comprising a first database for data objects, a second database for transaction documents, a user interface module, a fast data provider module, a user transaction provider module, and a business transaction provider module, which work together to process data objects, perform consistency checks, and update databases efficiently, reducing the need for frequent updates and improving response times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If comprehensive business information is provided at PC response times, then user interface performance is improved, but system complexity and operating costs increase
Solution Approach 1:
The system is divided into multiple independent modules: user interface module, fast data provider module, user transaction provider module, and business transaction provider module. Each module handles specific tasks independently, allowing the system to provide comprehensive business information quickly without requiring monolithic complexity in a single system component.
Solution Approach 2:
The fast data provider module acts as an intermediary between the database and the user interface module. It caches and pre-processes data objects, delivering them quickly to the user interface without requiring the interface to directly query complex database structures, thus improving response time while managing complexity through layered architecture.
2Loss of information
If multiple application areas are integrated into consolidated computing systems, then information consolidation is improved, but system complexity increases
Solution Approach 1:
The modular architecture enables a single consolidated system to handle multiple application areas (financial, sales, purchasing, production, projects, human resources) through universal modules that can process different types of business data and transactions. The fast data provider and transaction provider modules serve multiple business functions without requiring separate complex systems for each application area.
Solution Approach 2:
Different application areas are segmented into separate functional modules within the consolidated system. Each module handles specific business domains independently, allowing information consolidation across areas while managing complexity through modular organization rather than monolithic integration.
3Reliability
If frequent updates are performed to maintain data consistency, then data accuracy is improved, but processing efficiency decreases
Solution Approach 1:
The fast data provider module pre-loads and caches data objects before they are needed by the user interface. This preliminary action ensures data is readily available and consistent without requiring frequent real-time updates during user operations, thereby maintaining data reliability while improving processing efficiency.
Solution Approach 2:
The system maintains continuous data consistency through the transaction provider modules that continuously monitor and manage data integrity. The fast data provider continuously caches and refreshes data objects in the background, ensuring consistent data is always available without interrupting user operations or requiring frequent explicit update cycles.
Data Source
AI summary
A system and method for processing data objects is provided. The system and method may comprise: a data object database for storing data objects, a transaction document database for storing transaction documents, a fast data provider module configured to provide, upon request from a user interface module, data objects to the user interface module; a user transaction provider module configured to read changed data objects from the user interface module, read data objects from the fast data provider module, and store changed data objects in a user transaction document; and a business transaction provider module to read changed data objects from the user transaction document and perform updates of the changed data objects based on the user transaction document.