MES GUI Configuration via Metadata Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for customizing Manufacturing Execution System (MES) web-screens require modifying source code, leading to high development and maintenance costs, intellectual property risks, and reduced reusability, as they need to be tailored for each customer's specific requirements without access to the database configuration.

Innovation Solution

A dynamically built GUI configuration tool using meta-data fixed structure allows customization of MES screens without modifying the source code, enabling users to create graphical user interfaces through a client application builder tool, configuration file, and MES database, decoupling GUI changes from database structure updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If source code modification is used for customization, then customer-specific requirements are met, but development and maintenance costs increase

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

Solution Approach 1:

The system segments the customization process from the core source code by introducing a configuration file layer. The GUI parameters are divided into fixed structure elements and configurable parameters, allowing customization without modifying the actual source code. This segmentation enables independent configuration changes while preserving the integrity of the core application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A configuration file acts as an intermediary between the user's customization needs and the application's source code. Instead of directly modifying source code, users edit the configuration file which then drives the GUI generation. This intermediary layer decouples customization from source code modification, reducing development and maintenance costs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If source code modification is used for customization, then specific customer requirements are fulfilled, but intellectual property risks increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoidintellectual property risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The configuration file serves as a safe intermediary that allows customization without exposing or modifying proprietary source code. Sensitive business logic and IP-protected code remain intact in the compiled application, while all customizations are externalized to the configuration file, eliminating IP risks associated with source code distribution and modification.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If source code modification is used for customization, then MES screens are tailored to customer needs, but reusability decreases

Engineering Contradiction:
Improvecustomization capabilityVSAvoidreusability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments customization parameters from the core application code into a separate configuration file. This allows the core application to remain unchanged and reusable across multiple customers, while each customer's specific requirements are met through their own configuration file instances. The fixed structure ensures consistency while enabling unlimited customization scenarios.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If source code modification is used for customization, then GUI is adapted to requirements, but maintenance costs increase

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

Solution Approach 1:

The configuration file acts as a maintenance-friendly intermediary that isolates customization changes from the core application. When maintenance or updates are needed, only the configuration file requires adjustment, not the entire source code base. This dramatically reduces maintenance costs and complexity while preserving all customizations.

Inventive Principle:
Principle #24Intermediary (Mediator)

5Adaptability or versatility

If source code modification is used for customization, then specific project needs are met, but regression testing is required

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

Solution Approach 1:

The system segments the application into a stable core (source code) and a flexible configuration layer. Since the core source code remains unchanged during customization, regression testing is eliminated or minimized. Only the configuration file needs validation, which is a much smaller and simpler testing scope, thereby reducing time loss significantly.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2808784B1A system and a method for creating a graphical user interface within a manufacturing execution system (MES)
Publication Date: 2017.11.29 SIEMENS AG
  • EP2808784B1 patent drawingFigure 1
  • EP2808784B1 patent drawingFigure 2
  • EP2808784B1 patent drawingFigure 3

AI summary

A method and a system for creating graphical user interfaces (GUI) within a manufacturing execution system (MES), comprising: a client application builder tool enabling displaying MES screens and customizing MES and/or proprietary applications, a MES database comprising data to be displayed; where the data from a production process controlled by the MES are stored into the database; specification data having a meta-data fixed structure are determined within a configuration file to enable the generation of a configuration interface (CI); a GUI configuration tool calls the specification data from the configuration file and offers the CI for the user to create the GUI; the CI is generated using the meta-data fixed structure; the GUI is generated as specified by the user over the CI; and the data from the MES database is filled into the respective data fields of the GUI.