Field Device Frontend Generation Using Companion Specifications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face usability issues due to ad-hoc solutions for interacting with field devices, which are often error-prone and cumbersome, lacking a standardized and user-friendly approach for controlling and managing these devices.

Innovation Solution

A method is introduced that generates a controlling frontend for field devices by reading specifications from a database, using an operational frame based on companion specifications to create structured display elements connected to the device's operating elements, incorporating OPC UA standards for standardized information models and interfaces, and providing a scalable diagnostic and visualization approach.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If ad-hoc solutions are used for interacting with field devices, then device control is achieved, but usability is poor and errors are frequent

Engineering Contradiction:
ImproveusabilityVSAvoiderror-prone
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent changes the parameter of interaction from ad-hoc custom solutions to standardized interfaces defined by companion specifications. By establishing standard parameters for device interaction, the system improves both usability (easier operation) and reliability (fewer errors) simultaneously.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal controlling frontend that can interact with multiple different field devices through standardized interfaces. This universal approach allows the same frontend to control various devices consistently, improving usability through familiarity and reliability through standardized protocols.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If standardized interfaces are implemented for field device control, then interoperability is improved, but initial system complexity increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining standardized interfaces and companion specifications before actual device interaction. The controlling frontend is pre-configured with knowledge of standard device behaviors and parameters, reducing the complexity of ad-hoc integration work during deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer (the standardized controlling frontend) that mediates between the user and diverse field devices. This intermediary handles the complexity of device-specific protocols internally while presenting a unified simple interface to users, thereby improving interoperability without exposing system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If custom solutions are developed for each field device, then specific device requirements are met, but development time and cost increase

Engineering Contradiction:
Improvedevice-specific customizationVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates a universal controlling frontend that can adapt to different field devices through standardized interfaces. This single universal solution replaces the need for multiple custom-developed solutions, significantly reducing development time while maintaining the ability to meet specific device requirements through the standardized parameter set.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the device control requirements into standardized functional components defined by companion specifications. By breaking down device interaction into standardized segments (parameters, commands, data structures), the system can handle device-specific requirements through composition of standard segments rather than custom development.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3992736A1A method for providing a controlling frontend for an operating device
Publication Date: 2022.05.04 ABB (SCHWEIZ) AG
  • EP3992736A1 patent drawingFigure 1~2
  • EP3992736A1 patent drawingFigure 3
  • EP3992736A1 patent drawingFigure 4a~4c

AI summary

The invention relates to the field of industrial system automation, particularly for accessing and/or controlling field devices (30) by means of a controlling frontend (10). A method for providing a controlling frontend (10) for an operating device (40) configured for operating a field device (30) comprises steps of: providing an operational frame (14), wherein the operational frame (14) is based on a companion specification; reading a field device specification (24) from a database (50), wherein the field device specification (24) comprises a structured set of field device attributes (22), which are related to the operating elements (32); and generating, based on the field device specification (24) and the operational frame (14), a structured set of display elements (12) for the controlling frontend (10), wherein at least some of the display elements (12) of the controlling frontend (10) are connected to the operating elements (32) of the field device (30).