Litmus Edge Guide for Azure Manufacturing Data Solutions (MDS)

manufacturing data solutions in microsoft fabric and copilot template for factory operations on azure ai once litmus edge brings ot data from the edge into microsoft fabric, the data are transformed into a refined or silver layer for use in the manufacturing data solutions knowledge graph the mkg leverages the isa 95 data protocol, an international standard that enables the knowledge graph to represent factory data in an accurate, nuanced, and timely manner these data in turn provide the foundation for the copilot template to deliver valuable insight into factory operations the copilot template provides domain specific prompt templates, data grounding skills, and connectors; validation of outputs, via post processing, to avoid incorrect information; and rai guardrails to ensure only relevant, safe, responsible responses are given partners can extend these capabilities by creating their own prompt templates, skills, and connectors in addition, they can use these capabilities to extend and enhance existing data and collaboration apps from both microsoft and isvs to learn more about mds and copilot template, visit the microsoft cloud for manufacturing page on microsoft learn deploy litmus edge manager via azure marketplace (cloud) navigate & log into your azure portal > marketplace lem azure application marketplace page litmus edge manager azure application microsoft azure litmus edge manager site model microsoft azure define the following resource group – define a resource group to deploy in region – define a region to deploy in size – please refer to lem system requirement documentation for minimum & recommended sizing https //docs litmus io/edgemanager/quickstart guide/system requirements https //docs litmus io/edgemanager/quickstart guide/system requirements application name – define a name for the lem app managed resource group – select managed resource group click review + create agree to terms & conditions and fill in contact information on the next page click create once the application is deployed successfully check the inbound firewall rules in the virtual network 443/tcp lem ui access 8446/tcp lem admin console ui access 8883/tcp le to lem mqtt connection 51820/udp le to lem remote access connection depending on desired network and architecture, we can define specific ranges of ip for source and destinations firewall port configuration requirements review for all required and optional inbound/outbound lem firewall ports navigate back to the overview page in the essentials section you will find the ip address associated to lem app by azure \[optional] configure dns enter the ip or dns in a browser to access the lem ui access to litmus edge manager note user access to ui will be determined by network & firewall configuration deploy litmus edge (on premise) there are multiple deployment methods for le, depending on your on premise architecture and infrastructure installation and deployments system requirement for le when selecting a size for litmus edge instance once the le is deployed, we will need to configure firewall rules require & optional firewall ports log in to the litmus edge web ui the first time each deployment of litmus edge comes with 15 day trial license to full license le we will need to activate it with lem or apply a license key activate an edge device for licensing of litmus edge & litmus edge manager, please contact your litmus account representative setup litmus edge to send data to azure mds & azure fabric the litmus mds container can run either internally in a litmus edge instance or externally in the same host machine deploying the container externally is used when litmus edge is also running as a container prerequisites event hub or event grid credentials to set up the integration connector litmus edge access token litmus edge api account token knowledge prerequisites basic knowledge of docker containers, images, and docker run commands download the image download the image download the image from litmus central portal upload the image upload the image to litmus edge instance using ftp or from your hard driver upload the image to the target machine using the docker load command docker load i \<path to image tar file> deploy the image make sure the nats proxy is enabled enable the api account token and add the following topics read topics > write topics mds data payload > , mds metadata payload > , and mds config > deploy the image internal to litmus edge using the following command docker run d network host e edge ip address=\<edge ip address> e edge api token=\<access token> e edge nats token=\<api token> e mds publisher id suffix=\<publisher id suffix> e batch size=100 us docker pkg dev/litmus customer facing/litmus solutions/le azure mds integration \<image version> deploy the image external to litmus edge using the following command docker run d e edge ip address=\<edge ip address> e edge api token=\<access token> e edge nats token=\<api token> e mds publisher id suffix=\<publisher id suffix> e batch size=100 us docker pkg dev/litmus customer facing/litmus solutions/le azure mds integration \<image version> edge ip address litmus edge ip address or hostname edge api token litmus edge access token edge nats token litmus edge api account token mds publisher id suffix publisher id suffix for mds (optional set to litmus edge hostname by default) batch size number of messages to be sent in a single batch (optional value is between 1 and 2000, set to 100 by default) important notes if the mds container is deployed externally to the litmus edge instance, ensure that instance allows inbound access from the mds container on port 4222/tcp if litmus edge is deployed as a container, it is necessary to open port 4222 in the docker run command or in the kubernetes deployment file this can be specified using the following syntax p 4222 4222 azure event hub / event grid integration to send data from litmus edge to mds, you can use either azure event hub or event grid connectors see azure event hubs or azure event grid for more details refer to the following azure resources for learning more about azure event hub and azure event grid event grid event hub once the integration connector is set up, you can choose what device(s) data to send to mds by adding the following topics in the integration connector local topic mds data payload \<devicename> device data to be sent to mds mds metadata payload \<devicename> device metadata to be sent to mds ensure you have added the corresponding remote topic for each of the above topics in the integration connector for each device you want to send data to mds, you need to repeat the above by replacing \<devicename> with the actual device name optional you can use the following topics to request the metadata of a device or all devices from litmus edge mds config republish metadata republish the metadata of a device to mds the payload should contain the device name mds config republish metadata all republish the metadata of all devices to mds note subscribe to mds config callback to check the status of the metadata republish request you can now verify that the data is being sent to mds by checking the azure event hub or event grid on azure portal 🎉 that’s it! you have successfully deployed the integration between litmus edge and mds in microsoft fabric conclusion upon successful deployment, data from litmus edge will be transformed into the mds schema and sent to mds via azure event hub or event grid customers can use azure fabric and copilot llms to gather analytics and insights on their industrial data for technical support and any questions please contact your litmus account representative