Object-Based Workflow Management System for Plant Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing workflow management systems face challenges in scaling with expanding manufacturing plants, as they may overload due to dynamic generation of event objects, leading to communication network overload and difficulty in managing complex workflows across disparate processes and systems.
Innovation Solution
An object-based business process management system that executes workflows by generating scripts associated with workflow objects, rather than dynamically creating event objects, allowing for efficient management and scalability by promoting users to define scripts that launch tasks and workflows upon specific events, such as control inputs or threshold changes, without overloading the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If dynamic event objects are generated for each workflow event, then workflow automation capability is improved, but system overload and network congestion occur
Solution Approach 1:
The patent uses template-based event definitions where a single event template is copied and instantiated for multiple occurrences rather than creating unique dynamic event objects each time. This reduces the overall number of event objects in the system while maintaining full automation capability, as the template serves as a reusable blueprint for event handling.
Solution Approach 2:
Event templates are designed to be universal and multi-functional, capable of handling multiple different workflow scenarios through parameterization. A single event template can be instantiated multiple times with different parameters to handle various events, reducing the need for numerous specialized event objects and thereby preventing system overload.
2Adaptability or versatility
If complex workflows are managed across disparate systems, then workflow versatility is improved, but management complexity increases
Solution Approach 1:
The patent segments workflows into discrete, manageable tasks that can be independently defined and executed. Each workflow is broken down into smaller workflow objects that can be managed separately, reducing the overall management complexity while maintaining versatility across disparate systems through standardized interfaces.
Solution Approach 2:
The patent introduces an intermediary layer of workflow templates and event templates that mediate between disparate systems. These templates serve as standard interfaces that simplify the management of complex cross-system workflows by providing a unified way to define and execute tasks across different platforms and systems.
3Adaptability or versatility
If more event objects are created to handle additional workflow scenarios, then workflow adaptability is improved, but network overload occurs
Solution Approach 1:
Instead of creating numerous unique event objects for different workflow scenarios, the patent uses a copying approach where event templates are instantiated multiple times with different parameters. This maintains high workflow adaptability while keeping the actual number of event objects in the system manageable, as the same template can serve multiple purposes through parameter variation.
Solution Approach 2:
The patent achieves workflow adaptability through parameter changes rather than through creating different event objects. Event templates contain configurable parameters that can be adjusted to handle various workflow scenarios, allowing the system to adapt to different situations without increasing the number of event objects, thereby preventing network overload.
Data Source
AI summary
A system is provided. The system comprises a first computer located in a first plant, a first memory, and a first object based process management application stored in the first memory. The system further comprises a second computer located in a location separate from the first plant, a second memory, and a second object based process management application stored in the second memory. When executed on the first computer, the first application invokes scripts in response to events and the scripts launch tasks. When executed on the second computer, the second computer invokes scripts in response to events and the scripts launch tasks, one of the events acted on by the second application is a message received from the first application.