User Journey

the diagram below displays the most common user journey of the manufacturing connect edge experience this journey can include multiple paths and you are welcome to combine these as you see fit 1\ review the available options for installation and deployments docid\ amkjsx 2ufj3mfjp3tek6 to begin your journey 2\ instance setup see configure network interfaces docid\ frsjbru9mn9trgqeuhoy5 and configure dns/ntp servers docid\ wkw9ctmstfrjlj8jwox1c 3a connect a device docid\ nm1lqfefya dsiffitity in devicehub you start by connecting devices to manufacturing connect edge a typical example of a device would be a plc 3b add tags docid\ h5heqicxrcy3nch9kbg9i add tags to the connected device to subscribe to that device’s data by register for example, you may tag the plc registers that contain the current temperature and vibration values the data is collected with the frequency you define, automatically normalized, and published to the internal message broker this data becomes available to both internal and external entities 4\ process, visualize, and analyze the polled and normalized data create and manage data flows flows allow you to view device data and configure the output so you can better visualize how the device is operating for example, you can subscribe to a tag that provides temperature values, average the temperature values per hour, and then publish the average values to the message broker you can then add a function that monitors the published average temperatures and raises an alarm if the value exceeds a predefined threshold see flows manager docid\ q4jyt 6f9weaqu53lw3b to learn more create and manage analytics flows & models analytics docid\ fgjkboqwgvggd2nuqgro5 analytics docid\ dxce9032oqiligimolvlm are used to create flows you can add input, function, and output instances, and then connect them the flows can use kpis or machine learning models for example, you can apply out of the box compliance and loss or production cycle kpis to the data obtained from the message broker you can then publish the results to another tag at the message broker alternatively, you can submit the data to a pre trained tensorflow machine learning model and use the resulting predictions for decision making, visualize and analyze data with marketplace applications applications docid\ upktm t efggssljz6e7s provides a default set of applications in a public marketplace you can add your own docker container based applications in a private repository integrate connector to third party systems you can configure connectors to connect to cloud services this allows you to publish data from an edge device directly to a cloud service provider or database see integration docid\ simdy 2jhomqqjdjbhdrp to learn more add an opc ua hierarchy the opc ua protocol provides a publish subscribe client server technology for reliable data transmission you can add your edge devices and tags in a hierarchy see opc ua server docid\ q9bznezx8d o1g5wrckph to learn more customize systems customize settings such as security, network, user, and other settings to protect the integrity of your edge instance