How are Digital Twin mesasges processed by Litmus Production Record Database

litmus edge digital twin allows users to create a hierarchical data model, which is very similar to how litmus production record database stores production event data based on an isa88 inspired hierarchy therefore, it is possible to store data published by litmus edge digital twin inside litmus production record database when sending message objects published by digital twin to litmus production record database, users will not have to define a production record configuration or tag configuration, as the database will take this directly from the message received from digital twin which is in json note using digital twin does not replace other use cases or the use of solutions like litmus production record data model configurator docid\ roav4v9ohtwtvp2zleh1c or litmus production record tag configurator docid\ qdsdqjzbjc7kkjyauvvx2 as litmus digital twin can not satisfy all use cases, especially if data are to be send based on event triggers currently, litmus edge digital twin is well suited for uses cases which do not rely on triggers but where data are send at a set frequency slower then the raw tags themselves such as energy monitoring periodic asset performance monitoring litmus production record database is able to automatically identify, if a model in accordance with the digital twin exist or not and will create any missing setup this also does include anything added later by default every item in the json message received is created either as level or item if looking at a digital twin model, every node (orange item) will become a level in litmus production record database in accordance to the position in the digital twin in this example both "properties" and "telemetry" will be sub level 1 levels with regards to the items under a node (green items) it will depend on the payload they actually hold in this example below, the items such as "asset", "country" or "manufacturer" will become items, as they do not have any further breakdown while items such as "energyratedescription" or "season" will become levels under the "properties" level, so level 2, and then they will have both two items called "value" and "timestamp" litmus production record databases will also create in addition to a production record configuration a tag configuration for any entry which uses the original devicehub message as payload or at least uses "datatype", "devicename", "tagname", "success", "timestamp" and "value" from the original devicehub message in this example, litmus production record will also create a tag called "se 8xeu powermeter" for a device "energymonitoring" and will store the data in the tag related tables as well this makes it possible to send tag data to litmus production record database, which can also be used for other models if internal event monitoring is used