Modular Plant Software Configuration Using Inherited Function Modules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Modular Type Package (MTP) approach for developing modular plants faces issues with semantic ambiguity of services and inefficient reuse of function modules across different technical applications, leading to increased development costs and time.

Innovation Solution

Implementing a full object-oriented approach for function modules using inheritance, interfaces, and semantic definitions to allow for flexible adaptation and reuse of function modules across various applications, while enabling or restricting functionality as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the MTP approach is used for developing modular plants, then a framework for interoperability between function modules is established, but semantic ambiguity of services implemented in function modules occurs

Engineering Contradiction:
Improveinteroperability between function modulesVSAvoidsemantic meaning of services
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces semantic parameters and metadata to function modules to disambiguate service meanings. By adding semantic descriptors, ontological identifiers, and detailed parameter definitions to the function module interfaces, the system transforms the ambiguous service specifications into precise, machine-understandable semantic information while maintaining interoperability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent employs an intermediary layer of semantic modeling and ontological frameworks that sit between the function modules and the orchestration system. This intermediary layer provides semantic annotation services that translate and clarify the meaning of services, enabling both interoperability and semantic precision simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If function modules are developed for specific technical applications, then specialized functionality is achieved, but efficient re-use of function modules in other fields is prevented

Engineering Contradiction:
Improvespecialized functionalityVSAvoidre-use across different applications
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal function module framework where modules are designed with abstract, parameterizable interfaces that can adapt to multiple applications. By using generic service definitions with configurable parameters and semantic metadata, a single function module can serve multiple technical domains while maintaining its specialized functionality through parameter configuration rather than code modification.

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

Solution Approach 2:

The patent segments function modules into independent, loosely-coupled units with clearly defined interfaces and semantic boundaries. This segmentation allows modules to be developed for specific applications while maintaining the flexibility to be reused elsewhere by configuring their parameters and semantic descriptors appropriately, without requiring modification of the core module logic.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If function modules are created for each specific application, then application-specific requirements are met, but development costs and time increase

Engineering Contradiction:
Improveapplication-specific requirementsVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent establishes preliminary semantic frameworks, ontological models, and standardized interface definitions that are prepared in advance. By pre-defining service templates, parameter schemas, and semantic relationships, the system enables rapid deployment of application-specific function modules without requiring extensive development work for each new application, thus reducing development costs and time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables copying and reusing of proven function modules across different applications by maintaining their semantic descriptions and configurations. Once a function module is developed and validated for one application, its semantic model and interface definition can be copied and adapted to other applications through parameter configuration, eliminating the need to recreate modules from scratch and significantly improving development efficiency.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4343538B1Method of providing a software configuration for a modular plant
Publication Date: 2026.04.08 ABB (SCHWEIZ) AG
  • EP4343538B1 patent drawingFigure 1~2
  • EP4343538B1 patent drawingFigure 3~4
  • EP4343538B1 patent drawingFigure 5

AI summary

The present invention relates to a method (100) of providing a software configuration for a modular plant, the method comprising: - providing (101) a first function module (10) as a parent object, wherein the first function module comprises a function information of the first function module (10); - generating (103) at least a second function module (10), wherein the second function module (12) is a derived child object of the first function module (12) that inherits the function information of the first function module (10).