Scenario Landscape Map for Business Process Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business scenario visualization tools are challenging for non-technical users due to their complexity and technical nature, making it difficult for users to understand and navigate business processes within enterprise resource planning (ERP) systems, which hinders widespread adoption and effective use.

Innovation Solution

A scenario landscape map is introduced, providing a user-friendly, intuitive visualization of business scenarios using a transit-map style, simplifying complex business processes into linear representations, allowing users to understand and navigate business scenarios without requiring knowledge of technical process modeling notations like BPMN.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If technical process modeling notations (BPMN, EPC) are used to visualize business scenarios, then measurement precision and manufacturing precision of process models are improved, but device complexity and ease of operation deteriorate for non-technical users

Engineering Contradiction:
Improveprocess model accuracyVSAvoiduser accessibility
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer between technical process models and user interfaces. Business scenario models serve as this intermediary, translating complex BPMN/EPC notations into simplified, role-based visual representations that non-technical users can understand while maintaining connection to the underlying technical processes

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates simplified copies of technical process models through business scenario visualizations. These copies preserve the essential process flow and relationships but present them in a user-friendly format using familiar concepts like organizational charts and role-based workflows, eliminating the need for users to learn technical notations

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If comprehensive business scenario models are implemented in ERP systems, then adaptability and versatility of the system are improved, but device complexity increases making it difficult for non-technical users to understand and use

Engineering Contradiction:
Improvebusiness scenario coverageVSAvoidmodel complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by tailoring the complexity and detail of process visualizations to the specific needs and roles of different users. Each user sees a customized view of business scenarios relevant to their role, with appropriate levels of detail and technical depth, rather than a single complex comprehensive model for all users

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments comprehensive business scenario models into role-based, function-based, and department-specific views. This segmentation breaks down complex organizational processes into manageable, relevant portions that users can understand and interact with based on their specific responsibilities

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9286584B2Visualizing business processes or scenarios in a business software model using transit maps
Publication Date: 2016.03.15 SAP SE
  • US9286584B2 patent drawing
  • US9286584B2 patent drawing
  • US9286584B2 patent drawing

AI summary

A business scenario landscape map can show a scenario-centric view of a business scenario landscape that includes business scenarios accessible to members of an organization and supported by a business software architecture. In the scenario-centric view, first user interface elements can be arranged to show a linear representation of business process features of a selected business scenario and a visual depiction of relationships between the selected business scenario and other business scenarios. Upon receiving selection of a first user interface element(s) related to another business scenario, at least some of the first user interface elements can be rearranged to show a new scenario-centric view of the business scenario landscape in which business process features of the newly selected business scenario are arranged in a new linear representation including a visual depiction of relationships between the newly selected business scenario, the originally selected business scenario, and/or relationships with other additional scenarios.