MOM Software Module Deployment Using Metadata-Based Resource Selection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing manufacturing operation management systems lack an automated method for deploying software modules across a distributed network of computational resources without requiring manual intervention and specific knowledge of deployment locations.

Innovation Solution

A method involving software modules with metadata that include deployment criteria, evaluating layer-specific data to autonomously determine and deploy software modules on appropriate computational resource layers within the MOM system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software modules are manually deployed by IT administrators, then deployment control and decision-making are maintained, but deployment time increases and operational complexity increases

Engineering Contradiction:

Improvedeployment operationVSAvoiddeployment time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The software module itself provides deployment information through embedded metadata that describes its deployment requirements and constraints. The deployment instance automatically evaluates this metadata against available computational resources to determine the optimal deployment location without requiring manual intervention from IT administrators.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Deployment criteria and metadata are prepared in advance within the software module before deployment occurs. This preliminary preparation of deployment information enables the automated deployment instance to quickly evaluate and execute deployment decisions without time-consuming manual analysis.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If software modules are manually deployed with business scope knowledge, then correct deployment decisions are made, but operator knowledge requirements increase and process complexity increases

Engineering Contradiction:

Improvedeployment correctnessVSAvoiddeployment process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Metadata acts as an intermediary between the software module and the deployment instance. This structured data format translates business requirements into machine-readable deployment criteria, enabling automated evaluation while ensuring deployment correctness without requiring operators to possess specialized business knowledge.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The manual cognitive process of evaluating deployment suitability is replaced by an automated computational evaluation process. The deployment instance systematically compares metadata criteria against available computational resources using algorithmic logic, eliminating the need for human operators to manually assess deployment appropriateness.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If the MOM system uses a distributed architecture with multiple computational resource layers, then system flexibility and scalability are improved, but deployment complexity and difficulty of determining deployment location increase

Engineering Contradiction:

Improvesystem flexibilityVSAvoiddeployment architecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Each computational resource layer is assigned specific deployment criteria and characteristics that match the requirements of different software modules. The deployment instance evaluates metadata against the specific properties of each layer to determine the most appropriate deployment location, enabling automated decision-making in distributed architectures.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The deployment problem is transformed from a manual selection process to a multi-dimensional evaluation process. Metadata contains deployment criteria across multiple dimensions (computational requirements, constraints, preferences), and the deployment instance systematically evaluates these dimensions against available resources to determine optimal deployment locations.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12517499B2Method for the deployment of a software module in a manufacturing operation management system

Publication Date: 2026.01.06 SIEMENS AG

AI summary

A software module is deployed in a MOM system without requiring the operator to know where to deploy the software module within the network of the computational resources that are addressed and/or accessed within the MOM system. A number of software modules are provided, each including a set of metadata with a number of deploy criteria. A plurality of computational resource layers are provided, with each resource layer having different computational resources and being enabled to communicate layer specific data, which include resource availability information. A deployment instance is executed that evaluates the metadata and the layer specific data and, depending on the evaluation, the computational resource layer and the computational resource on which the software module will be deployed is determined. The software module is then executed on the determined computational resource within the determined computational resource layer.