Multi-perspective Business Process Configuration via Hierarchical Solution Maps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The implementation of enterprise resource planning (ERP) software often fails due to a lack of understanding of business requirements by implementation partners or inflexible ERP software, leading to incorrect installations and delays, as different stakeholders require varying levels of abstraction in configuration processes.
Innovation Solution
A computer-implemented method for configuring business processes involves creating a solution map, deriving pre-configured collaborative business scenarios, and event-driven process chains, which allows for flexible abstraction levels to facilitate effective communication and correct ERP software installation across managerial levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a single detailed configuration approach is used for all stakeholders, then technical analysts can perform precise configuration, but senior management cannot understand the process due to excessive detail
Solution Approach 1:
The patent segments the configuration process into multiple hierarchical levels: solution maps at the strategic level for senior management, and detailed process configurations at the operational level for technical analysts. This segmentation allows each stakeholder group to interact with the appropriate level of detail without being overwhelmed by unnecessary information.
Solution Approach 2:
The patent introduces a hierarchical dimension to the configuration process, organizing configuration data across multiple levels of abstraction. Solution maps represent high-level strategic configurations, while underlying detailed configurations provide operational specifics. This dimensional organization enables stakeholders to navigate and understand configurations at their appropriate level.
2Adaptability or versatility
If ERP software is made highly flexible to accommodate various organizational requirements, then adaptability improves, but implementation complexity and time increase
Solution Approach 1:
The patent implements pre-configured solution maps and process templates that capture common business scenarios in advance. These pre-configured elements can be directly applied to many implementations, reducing the need for extensive custom configuration while maintaining flexibility for unique requirements.
Solution Approach 2:
The patent creates a dynamic configuration system where solution maps can be selectively applied and customized based on organizational needs. The system allows stakeholders to choose and combine different solution maps and process configurations, providing adaptability without requiring complete customization of every element.
3Manufacturing precision
If implementation partners closely follow organizational requirements, then configuration accuracy improves, but misinterpretation of requirements at different abstraction levels occurs
Solution Approach 1:
The patent introduces solution maps as an intermediary layer between senior management's strategic requirements and technical analysts' operational configurations. Solution maps translate high-level business goals into structured process configurations, ensuring accurate requirement interpretation across different stakeholder levels without loss of information.
4Ease of operation
If different languages and models are used for different decision makers, then each stakeholder can understand their level, but integration and communication between levels become difficult
Solution Approach 1:
The patent creates a universal configuration framework where solution maps serve multiple functions: they represent strategic requirements for senior management, provide process blueprints for business analysts, and guide technical configurations for implementation partners. This multi-functionality reduces integration complexity by using a common framework across all stakeholder levels.
Data Source
AI summary
A computer-implemented method for configuring a business process includes configuring a solution map and deriving a pre-configured set of collaborative business scenarios based on the solution map. The pre-configured set of collaborative business scenarios is then configured and a pre-configured set of event driven process chains is derived based on the configured set of collaborative business scenarios. Finally, the pre-configured set of event driven process chains is configured.