Configuring the Litmus Production Record Digital Twin Message Conversion Flow

o allow the flow to create the right message payload so that the data can be successfully ingested by litmus production record database using a litmus integration, there are two mandatory configurations the user has to make configure the topics for the tags to be used the purpose of the flow, is to ingest digital twin data published by litmus edge digital twin instances and modify the message payload to meet the requirements of litmus production record database the flow has to therefore subscribe to the topics of the digital twin instances which are to be send to litmus production record database the user provides these topics through the use of the litmus pallet node datahub subscribe to provide a topic, users edit the datahub subscribe node and replace the placeholder "please enter topic" with the topic of a digital twin instance to be used by the event configuration and press the done button if more than one digital twin instance is required, users have one option for providing all the instances they require, as wildcards are not supported at this point in time for litmus edge digital twins option 1 add more datahubsubscribe nodes the flow comes with a single datahub subscribe node in the section but users are able to add more nodes as they need and wire them all into the output the example shows how a user added more node by creating copies of the original node configure the item and publishing topic for the modification of the message payload, the flow requires at the minimum an api key to create an api key please visit the litmus documentation on how to create a rest api key by default the flow will use as writetopic "litmus dt prorec" but users are able to modify these to modify the api key and/or writetopic, the user has to edit the sub flow this allows to set the desired values for these two settings and press the done button to start the processing, deploy the flow optional settings as litmus production record stores production event data such as downtimes, energy management, product traceability and more against a unique combination of identifiers as explained in the chapter how are data for a production record data model stored docid\ n26ytjyqxp15wxwtqi j , these have to be defined also for data coming from a digital twin as a digital twin may not have such items defined, the flow will by default use as identifiers digital twin instance name the current year the current month the current day the current hour this means, if a digital twin model does not have any items directly under their root which satisfy the need for identifiers, the user does not have to do any changes and the flow will take care of it and the optional options can be left as they are if a digital twin model has items directly under the root which would satisfy the needs for identifiers the user is able to provide these instead final step after all configurations have been done and are deployed, it is recommended to setup a litmus integration using the db microsoft sql server connector how to setup an integration can be read up on using our litmus edge documentation after the integration is established, the user needs to subscribe to the topic which has been setup in the sub flow how a subscription for an integration is added, can be found in the litmus edge documentation add as local data topic the value used in your event configuration now, every time the flow publishes a new message on this topic, the integration will send it to litmus production record database