- Bookmark
- Share
- Documentation
- prev
- next
Objective
This solution aims to allow customers to monitor complex trigger conditions directly on Litmus Edge.
Running as a flow does provide some additional benefits to customers, as the trigger event can not just be published to Litmus Production Record Database, but can also be used to trigger additional custom code created by the user on either Litmus Edge or docker applications.
Further does the flow allow for scalability, as the flow is capable of tracking he same event for different DeviceHub devices. Or track different event configurations for different devices and scenarios within the same flow.
Making it unnecessary to deploy and manage several different flows.
The JSON configuration processed by the flow, can be created with the Litmus Solution Litmus Production Record External Event Configurator.
Example Use Case
The Litmus Production Record Event Processing Flow allows to process trigger conditions for many different use case.
The only requirement is, that a trigger source for the start and stop and clear identifiers for the source and type of an event/production record do exist.
So that it can clearly be identified when it, where and what happened while executing a production process.
If these conditions are met, Litmus Production Record Database makes it possible to record nearly every possible event type such as:
If these conditions are met, Litmus Production Record Event Processing Flow makes it possible to monitor for nearly every possible event type such as:
-
- Downtime Events
- Production Traceability Events
- Maintenance or Turnaround
- Work processes or production steps
- Alarms and events
- Quality Events
Basic Attributes
-
Solution Versionv1.0.0
-
Supported Litmus Edge versionsLE 3.5.6 and above
-
Litmus Edge modules usedLitmus Flows
-
Approximate Size1MB
-
Technologies usedJavascript
-
Skill LevelAdvanced
Product Category
Knowledge Prerequisites
The Litmus Production Record Event processing flow is a supporting solution to Litmus Production Record Database.
To successful make use if this flow, users will need to have a base understanding of the Concepts behind Litmus Production Record Database such as the data models used to store the data for production record events.
As the flow does run on Litmus Edge, it is also required to have base knowledge about Litmus DeviceHub and Litmus Flows.
While not required, it is recommended to use Litmus Integrations to send the data to Litmus Production Record Database from Litmus Edge.
Installation Guide
How to deploy Litmus Production Record Event Processing Flow
This section will provide instructions on how to deploy Litmus Production Record Event Processing Flow.
Requirements
- The tags which are used as trigger as well as data are defined in DeviceHub.
- A Litmus Flows Instance is available.
- An event trigger configuration in JSON format does exist.
- This configuration can be created using the Litmus Solution Litmus Production Record External Event Configurator.
Please check out the Documentation Portal.
Additional Information
Documentation for this solution are available on the Solutions documentation page.
Version Information
-
Solution Version
-
Supported Litmus Edge versionsLE 3.5.6 and above