MOM Software Module Deployment Using Metadata and Resource Layers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In manufacturing operation management systems, deploying software modules across complex, distributed computational resources requires significant manual effort and knowledge, as there is no automated mechanism to determine the optimal deployment layer, leading to inefficiencies and prolonged deployment times.
Innovation Solution
A method that utilizes metadata to guide the deployment of software modules within a manufacturing operation management system, where each module is equipped with deploy criteria, and a deployment instance evaluates resource availability to autonomously determine and execute the deployment on the appropriate computational resource layer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual deployment of software modules is performed by IT administrators, then deployment control and decision-making are maintained, but deployment time and operational complexity increase significantly
Solution Approach 1:
The software module performs self-deployment by automatically determining its own deployment layer based on metadata analysis. The deployment instance executes autonomously, evaluating the software module's requirements and selecting the appropriate computational resource layer without human intervention, thereby reducing deployment time while maintaining controlled deployment decisions
Solution Approach 2:
Metadata describing software module requirements and deployment criteria are prepared in advance before deployment occurs. This preliminary structuring of deployment information enables the automated deployment instance to quickly determine the correct deployment layer without manual analysis, reducing operational time while preserving deployment control
2Reliability
If software modules are manually deployed with knowledge of business scope and resource requirements, then optimal deployment decisions are made, but significant time and expertise are required
Solution Approach 1:
Metadata acts as an intermediary between the software module and the deployment instance. The metadata encapsulates business scope and resource requirements in a standardized format, allowing the deployment instance to make reliable deployment decisions without requiring administrators to possess deep domain knowledge, thus reducing operational complexity while maintaining decision quality
Solution Approach 2:
The deployment criteria in metadata are structured as specific parameters that the deployment instance evaluates. By transforming qualitative business requirements into quantifiable deployment parameters, the system enables automated decision-making that is both reliable and simple to execute
3Extent of automation
If software modules include metadata with deploy criteria, then automated deployment determination is enabled, but additional data structure requirements are introduced
Solution Approach 1:
The metadata structure serves multiple functions: it describes software module characteristics, defines deployment criteria, and guides automated deployment decisions. This multi-functional data structure enables comprehensive automation without requiring separate complex systems for each function, balancing automation extent with data structure complexity
Data Source
Figure 1
Figure 2
Figure 3
AI summary
It is the object of the present invention to provide a method for the deployment of a software module in a MOM system that does not require any knowledge of the operator where to deploy the software module within the network of the computational resources that are addressable/accessable within the MOM system. This objective is achieved according to the present invention by a method for the deployment of a software module in a manufacturing operation management system (MOM system), said method comprising the steps of: a) providing a number of software modules to be deployed, wherein each software module comprises a set of metadata; said metadata comprising a number of deploy criteria; b) providing a plurality of computational resource layers; each resource layer comprising a number of computational resources and being enabled to communicate layer specific data, said layer specific data comprising at least data representing resource availability information; c) executing a deployment instance that evaluates the metadata and the layer specific data; d) determining in dependency of the metadata and the layer specific data the computational resource layer and the computational resource on which the software module will be deployed; and e) executing the software module on the determined computational resource within the determined computational resource layer.