UNS and the Data Historians Role

[@rezahamzeh3736]

Great Video Zack! It would be amazing if you can show a simplified version of UNS from the manufacturing industry to demonstrate the implementation and application of UNS in a real case

[@posullivan3805]

Great job Zack. This was informative, especially the dive into the historian side of things, you addressed timestamps, security (the bit about inbound ports needed for opc vs not needed for mqtt), the mqtt connector to add all tags to canary... all great stuff

[@ZackScriven]

Thank you Paul!

[@firataksahan3626]

Thanks Zack and Canary for this video! I should come to discord to discuss more:)

[@ZackScriven]

Thank you! Yes please do!

[@aldhal202]

Am still confused about UNS containing the real or actual state of business: Does UNS has a DB where data and information are stored not only exposed in hierarchical manner? Or it just exposes data and information from nodes (be it MEs application, erp, historian, plc, sensor....) in a hierarchy adding more context using pub/sub integration?

[@4.0Solutions]

The UNS itself does not contain a database, the UNS is the real time state of your business. You dont query the UNS to get past data. However, in your architecture you can attach a database that can consume the hierarchical structure either through spb or by directly connecting to your IIoT platform of choice. The data itself gets stored in the structure of the UNS. DB's such as Influx, Pi, Canary, Timescale, etc can be used to achieve this. We also have a Discord server where you can reach out to us or any community member in public channels and ask questions. You can join here: www.iiot.university/discord

[@aldhal202]

@4.0Solutions thanks for the insight. Knowing that legacy or current nodes (especially MES and ERP) have their own object structures, what tools do you recommend to easily map their model into the UNS semantic and then publish it to the infrastructure? In case replacing current architectures in one shot is not feasible, how would one plug in UNS into nodes (mainly talking about from the shelf MES) that do not publish but they have API and act in on-demand way? Any preferred tools?

[@barsvelioglu2276]

I like the way which you tell the concepts. Good job Zack.

[@4.0Solutions]

Thanks Baris!

[@Jonafets]

Why are the client tools reading from the historian? Is the point not to get rid of that point to point connection and to have the client tools also read from the UNS? Or will clients still read from historians and MES databases and from OPC?

[@bartwybouw4657]

Depends if you want current state (UNS) or historical data(historian), it seems to me.

[@blackstar160686]

Hi Zack, thanks for the video Great content. In your architecture when you want share historical with third party systems, will you still pass from the UNS?

[@ZackScriven]

Great question. Historical data would be passed via a historical connector. ignition and FrameworX both have this Native Canary History connector.

[@Matt-n9l1l]

In a legacy environment where the data is coming from OPC would it make sense to go through the MQTT layer and add the UNS there, or to go directly into Canary using their OPC connection and add the UNS hierarchy within Canary? Pros? Cons?

[@leehunt1261]

Great job with the video Zack. It's great to see a true data historian adopt I4.0 technology/capabilities!!

[@4.0Solutions]

Thanks Lee!

[@belleflamm]

Nice and well explained, could we have a clear picture where to choose OSI, Wonderware or Canary historians ? I know you are pushing software like ignition and/or canary however I think for this you should know where each software is strong or weak even those you're reselling right ? Thank you

[@4.0Solutions]

We have no financial interest in selling I Any of the software we recommend. Yes this month is sponsored by Canary, but that money goes to paying for content production costs. If you had an entire wonder where ecosystem then maybe pi would make sense… but the problem is AVEVA doesn’t make the software that’s best in class at every layer In the stack, but they don’t care they just want to sell you more software in their ecosystem.

[@belleflamm]

@@4.0Solutions not sure it's a good idea to have Pi on top of Wonderware. They are at the Beginning of the integration and the connector isn't yet mature. However, If I understand correctly, Pi will be considered as a tier2 in their ecosystem replacing their tier2 staged Wonderware historian and offer more possibilities like native connector to DCS (not included in Historian). Another point, because I have a bit experienced with Wonderwaee Historian, is that what you mention in your video is not fully true. They have a MQTT sparkpkug B compliant driver which will update automatically the UNS (model like Enterprise -> Plant -> .. -> Edge device in the scada). This scada is an Historian client and share the UNS with it. So finally Historian will get new values when a new device will be connected to the UNS. Let me know your thoughts please

[@ryanclavette921]

Great video Zack - this is explained very well.

[@4.0Solutions]

Thank you Ryan!

[@sherylmccrary9045]

UNS is/contains the current state of your business. Historian interacts but is not the UNS.

[@posullivan3805]

Absolutely Sheryl, we'll said

[@hobbes1069]

Of course regex could be multiple hour videos, but to boil it down to its essence, it lets you match and return what you want from complex patterns.

[@4.0Solutions]

Thank you!

[@leightaylor7556]

Great Video Zack.

[@4.0Solutions]

Thanks!

[@Lachlan.Wright]

Dont why I hadn't seen this vidoe before. Its a good one!

[@4.0Solutions]

Thanks! Glad you found it helpful - Zack

[@youriregnaud8461]

Great job

[@adelleloots4991]

Great video - can't stop wondering why you are in a kitchen though?

[@4.0Solutions]

Because we’re cooking up that great educational content!