Hierarchical User Interface for Industrial Automation Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional industrial automation systems present complex engineering project data in a way that overwhelms users with excessive information and functionality, requiring knowledge of the object model rather than the user's mental model of the engineering process, making it difficult for users to navigate and perform tasks effectively.

Innovation Solution

A user interface with a hierarchical and progressively disclosing portal view that separates project data into main and subordinate functions, allowing users to access only necessary information based on their expertise or role, and enabling switching to a full project view for complete data access, while supporting interruptible workflows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all functions and engineering data are presented simultaneously in conventional engineering systems, then complete information availability is achieved, but user complexity and difficulty of operation increase significantly

Engineering Contradiction:
Improveinformation availabilityVSAvoiduser operation difficulty
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The user interface is segmented into multiple hierarchical levels: a simplified portal view displaying only main functions and selected project data, and a detailed project view accessible upon request. This segmentation allows the system to present information in digestible portions rather than overwhelming the user with all data simultaneously, while still maintaining complete information availability when needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The interface dynamically adapts its complexity based on user interaction. The portal view serves as a dynamic gateway that can expand into the full project view when users need detailed information. This dynamic behavior allows the system to adjust between simplicity and completeness based on real-time user needs, resolving the contradiction between information availability and ease of operation.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If comprehensive engineering data and functionality are made accessible, then system versatility is improved, but device complexity increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The interface complexity is segmented into two distinct views: a simplified portal view for routine operations and a comprehensive project view for detailed work. This segmentation allows the system to maintain high versatility while reducing perceived complexity by only displaying necessary functions and data at any given moment, rather than presenting all capabilities simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The portal view acts as an intermediary layer between the user and the complex engineering system. It provides a simplified interface that mediates access to the full system functionality, filtering and organizing information before presentation. This intermediary reduces interface complexity while preserving system versatility, as users can access complete functionality through the portal when needed without being overwhelmed by it.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If all project data is displayed in the user interface, then data completeness is achieved, but information overload occurs overwhelming the user

Engineering Contradiction:
Improvedata completenessVSAvoidinformation overload
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

Project data is segmented and selectively displayed based on the current context and user needs. The portal view segments data into relevant categories and displays only what is necessary for current tasks, while the project view provides access to complete data when users explicitly request it. This segmentation prevents information overload while maintaining data completeness availability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements partial action by displaying only the subset of project data that is currently relevant, rather than all available data. Users can access additional data through the project view when needed. This approach avoids information overload by presenting manageable portions of data while ensuring completeness is available on demand, resolving the contradiction between data completeness and preventing information overload.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2133765B1User interface and a method thereof
Publication Date: 2019.11.27 SIEMENS AG
  • EP2133765B1 patent drawingFigure 1
  • EP2133765B1 patent drawingFigure 2
  • EP2133765B1 patent drawingFigure 3

AI summary

The invention describes an improved user interface for use in an industrial automation system based on hierarchy of functions that need to be achieved. The user interface having a portal view (100, 200) comprising a first display region (102) adapted to display at least one first user selectable identifier (104, 106, 108) representing at least one main function accomplishable within an engineering system. The portal view (100, 200) comprises of a second display region (110) adapted to display at least one second user selectable identifier (112, 114, 116, 118) representing at least one subordinate function that is usable to accomplish the main function (104), the display of the second user selectable identifier being based on a first user selection of the first user selectable identifier. Further the portal view (100, 200) comprises an optional third display region (120) adapted to display a context-specific selection of project data (122, 124, 126), the display of the context-specific selection of the project data (122, 124, 126) being based on a second user selection of the second user selectable identifier (112, 114, 116, 118). The user interface further has a project view (300) comprising a fourth display region (305) adapted to display third user selectable identifiers (340). The third user selectable identifiers (340) representing the entire accessible project data. Both the portal view (100, 200) and the project view (300) comprise a user selectable switching means for switching between the project view 300 and the portal view (100, 200).