Great video, thank you, Walker! Actually, OPC UA was designed to support exactly unified namespace ideas, keeping in mind the possibility to convey not just raw data, but also information and object models from sensor level to the cloud. So when you for example build a dashboard, information about measurement units, range of values, display name in various languages, etc. would be available. But when data is pushed to leading cloud providers platforms, that information is usually lost. Although there is still the possibility to convey metadata using protocols like MQTT, they are not standardized, every platform has its own approach in how topics and payload are structured. I would like also to remind you that OPC UA supports Pub/Sub to deliver data in scale. In my opinion, OPC UA deserves to be at the center of such solutions. It is interesting if HighByte utilizes the power of OPC UA in its architecture.
Hi One-Way Automation. We recommend you watch this video: th-cam.com/video/f4LZtQ2SEDk/w-d-xo.html OPC-UA has a place in the enterprise, but it's definitely not as your Unified Namespace. It might take some time, but we promise you will eventually come around to realize that OPC-UA (even with such edge cases you mentioned) is not the future of IIoT.
It would be great if you make a video about Kepware vs Ignition vs High byte or combinations of two systems for more robust solution for different applications.I'm a student this information could help me to choose a possible solution for the company in the future.
I believe the concept of unified namespace also requires not only flowing the data from domains into a centrally owned data platform or namespace, also need to host and serve the other data consumers in an easily consumable way.
I just came across your videos recently while looking up topics on IIoT. Great concept on pushing everything to a "Unified Namespace". I am assuming here that one option is to push everything to the namespace using MQTT. Hence, having a centralized MQTT broker at the enterprise level could achieve this. But the question that I have with this kinda setup is, how exactly do you deal with all the different types of data (image, audio, format, structures). Let's take the JSON structure of IoT devices for example. It could come in many combinations of "key: value" pair structure, depending on where that JSON file originated from. And then there are data that is sent in CSV, XML, image, audio, video, documents, etc... All these data would need to be normalized for a particular system to understand and take action on the data (storage, visualization, analytics, reporting, etc...) Would really appreciate your thoughts on this. Keep up the great work!
Your enthusiasm is contagious Walker. However, I must say that there are many software out there doing the same thing. Just that they do not use the term unified namespace which I think is just a marketing gimmick. Actually the space is already getting crowded with lot of options. It will be good to see Walker do a side by side comparison of many of these tools. Off-course unless you are not a reseller/system integrator for Hbyte.
We will do this. We are not sponsored by highbyte. We just think it's the best out there for this role. (It was designed just for it) Ignition, Factory Studio, WinCC OA are other platforms that would serve as the unified namespace. We are just trying to help educate people on the concept.
Mike, thanks for the comment -- there are a handful that do this, yes... there are even fewer who do it and meet our requirements: Open Architecture, edge driven, report by exception, using an IIoT protocol. We are not a reseller for HighByte and have no business relationship with their organization. I spent several years trying to get Kepware to build a UNS and support our requirements, but after the PTC acquisition, that possibility evaporated. Tony Paine is the former President of Kepware and he and John broke off with Tory to create the Intelligence Hub -- its built to fill a vacuum in the market that has lingered for some time. HighByte is the first company to build a solution that, in our eyes, checks off all the boxes in a no-frills way. Ignition, FactoryStudio, WinCC-OA and a handful of other options work too -- but HighByte is the first to offer a solution that breaks the UNS outside of another specialized application. I'm interested to hear what other platforms out there that do the same thing -- I think our requirements might not be the same. Could you share some examples and I'd be happy to comment on them?
Great explanation!! I have two questions: 1/ is it possible to push the data from our ERP and MES systems to the UNS through MQTT or is it typically done thru HTTP? 2/ Can AWS or Azure DataOps be used to design and build a UNS? Thanks again
While it is possible to use MQTT and more softwares are... it's more common to use HTTP and APIs. And Yes you can build a UNS on top of AWS... it's a bit easier to accomplish in AWS than Azure.. see our video on AWS vs Azure for Industry. th-cam.com/video/eyDcWPic0Do/w-d-xo.html
Walter, great info as always. Does the UNS concept support a redundancy model? To avoid a single point of failure and as part of IIOT best practice deployment, have you deployed multiple Ignitions in a cluster?
You mention in the video that a UNS is NOT a Data Lake. Can you or have you already elaborated more why that is so and where they might be overlapping. The reason is that I hear a lot that you just need a Data Lake to store all your data and everything is happy days.
Yes. You are hearing a lot from people who will fail at Digital Transformation. The biggest misconception people think is that the UNS is just simply all data. It's your business structure, all events, and current state. Historical data is in the node application. If you just dump everything into a day like you don't have a unified namespace which means you will fail to scale. We recommend watching: What is the Unified Namespace? th-cam.com/video/PB_9HIgSCWc/w-d-xo.html
Hi, thanks for all the great information!!! Can Tango-Controls open source solution be used to create the unified namespace? Thanks again and keep sharing videos please.
@@Croja77 HighByte specializes in data aggregation, abstraction and organization -- it is not meant for visualization, it relies on other applications in the ecosystem to do that.
Hi Walter, Your videos have highly informative and have opened new perspectives while defining an IIOT Solution. Thanks a Lot!!! Coming to Unified Namespace, does Wonderware/Aveva has any product providing this.
Great question -- the historian monitors changing events in the namespace and stores them. Very often, we will store the last 24 hrs of datapoint x (time series) in a dataset topic in the namespace. This is a very common approach. It is important to remember -- the UNS is structure and events, the clients that plug into the UNS handle the capabilities (like history).
It is not -- it can connect to a UNS and publish back, but it cannot act as a UNS. Your question was answered in the Live Q&A on 1/11. Thank you for the feedback!
![โรงเรียนตอนตี 2 โคตรหลอน..!! [โรงเรียนไดเม่]](http://i.ytimg.com/vi/2MAEMwqVYh8/mqdefault.jpg)
Getting back to UNS, understand more each time I watch the video
Thank you for sharing!!
Great video, thank you, Walker!
Actually, OPC UA was designed to support exactly unified namespace ideas, keeping in mind the possibility to convey not just raw data, but also information and object models from sensor level to the cloud. So when you for example build a dashboard, information about measurement units, range of values, display name in various languages, etc. would be available. But when data is pushed to leading cloud providers platforms, that information is usually lost. Although there is still the possibility to convey metadata using protocols like MQTT, they are not standardized, every platform has its own approach in how topics and payload are structured.
I would like also to remind you that OPC UA supports Pub/Sub to deliver data in scale.
In my opinion, OPC UA deserves to be at the center of such solutions.
It is interesting if HighByte utilizes the power of OPC UA in its architecture.
Hi One-Way Automation. We recommend you watch this video: th-cam.com/video/f4LZtQ2SEDk/w-d-xo.html
OPC-UA has a place in the enterprise, but it's definitely not as your Unified Namespace. It might take some time, but we promise you will eventually come around to realize that OPC-UA (even with such edge cases you mentioned) is not the future of IIoT.
It would be great if you make a video about Kepware vs Ignition vs High byte or combinations of two systems for more robust solution for different applications.I'm a student this information could help me to choose a possible solution for the company in the future.
This is a great idea -- we will shoot this video next week!
Thank you and looking forward to it !!
Thank you Sai!
As always.... to the point. The rougher the better!
Thank you!
I believe the concept of unified namespace also requires not only flowing the data from domains into a centrally owned data platform or namespace, also need to host and serve the other data consumers in an easily consumable way.
You get it!
I just came across your videos recently while looking up topics on IIoT.
Great concept on pushing everything to a "Unified Namespace". I am assuming here that one option is to push everything to the namespace using MQTT. Hence, having a centralized MQTT broker at the enterprise level could achieve this.
But the question that I have with this kinda setup is, how exactly do you deal with all the different types of data (image, audio, format, structures). Let's take the JSON structure of IoT devices for example. It could come in many combinations of "key: value" pair structure, depending on where that JSON file originated from. And then there are data that is sent in CSV, XML, image, audio, video, documents, etc...
All these data would need to be normalized for a particular system to understand and take action on the data (storage, visualization, analytics, reporting, etc...)
Would really appreciate your thoughts on this.
Keep up the great work!
Your IIoT Platform, like Igntion, HighByte, FrameworX can handle these different datatype. We have a new video on MQTT coming out this week!
@@4.0Solutions looking forward to it! Hope you can share the link here when the new video is up.
@@zain-im-lazim6770 th-cam.com/video/KAYNg7meAdo/w-d-xo.html
Your enthusiasm is contagious Walker. However, I must say that there are many software out there doing the same thing. Just that they do not use the term unified namespace which I think is just a marketing gimmick. Actually the space is already getting crowded with lot of options. It will be good to see Walker do a side by side comparison of many of these tools. Off-course unless you are not a reseller/system integrator for Hbyte.
We will do this. We are not sponsored by highbyte. We just think it's the best out there for this role. (It was designed just for it) Ignition, Factory Studio, WinCC OA are other platforms that would serve as the unified namespace. We are just trying to help educate people on the concept.
Mike, thanks for the comment -- there are a handful that do this, yes... there are even fewer who do it and meet our requirements: Open Architecture, edge driven, report by exception, using an IIoT protocol. We are not a reseller for HighByte and have no business relationship with their organization. I spent several years trying to get Kepware to build a UNS and support our requirements, but after the PTC acquisition, that possibility evaporated. Tony Paine is the former President of Kepware and he and John broke off with Tory to create the Intelligence Hub -- its built to fill a vacuum in the market that has lingered for some time. HighByte is the first company to build a solution that, in our eyes, checks off all the boxes in a no-frills way. Ignition, FactoryStudio, WinCC-OA and a handful of other options work too -- but HighByte is the first to offer a solution that breaks the UNS outside of another specialized application. I'm interested to hear what other platforms out there that do the same thing -- I think our requirements might not be the same. Could you share some examples and I'd be happy to comment on them?
@@walkerreynolds973 love this comment Walker!
Great explanation!!
I have two questions:
1/ is it possible to push the data from our ERP and MES systems to the UNS through MQTT or is it typically done thru HTTP?
2/ Can AWS or Azure DataOps be used to design and build a UNS?
Thanks again
While it is possible to use MQTT and more softwares are... it's more common to use HTTP and APIs. And Yes you can build a UNS on top of AWS... it's a bit easier to accomplish in AWS than Azure.. see our video on AWS vs Azure for Industry. th-cam.com/video/eyDcWPic0Do/w-d-xo.html
Can OPC Router consider as Unified namespace?
Walter, great info as always. Does the UNS concept support a redundancy model? To avoid a single point of failure and as part of IIOT best practice deployment, have you deployed multiple Ignitions in a cluster?
Yes it does! MQTT can publish it's entire namespace to another broker :)
You mention in the video that a UNS is NOT a Data Lake. Can you or have you already elaborated more why that is so and where they might be overlapping. The reason is that I hear a lot that you just need a Data Lake to store all your data and everything is happy days.
Yes. You are hearing a lot from people who will fail at Digital Transformation. The biggest misconception people think is that the UNS is just simply all data. It's your business structure, all events, and current state. Historical data is in the node application. If you just dump everything into a day like you don't have a unified namespace which means you will fail to scale. We recommend watching: What is the Unified Namespace? th-cam.com/video/PB_9HIgSCWc/w-d-xo.html
Check out the most recent video on Why you Will Fail.
Hi, thanks for all the great information!!! Can Tango-Controls open source solution be used to create the unified namespace? Thanks again and keep sharing videos please.
Here is the answer on video! th-cam.com/video/pPVomEYWgco/w-d-xo.html
HighByte vs. Ignition? Pros / Cons?
HighByte vs. Ignition as Unified Namespace? Does HighByte support dashboard creation?
High Byte is only an industrial namespace. You would still need other applications to visualize data.
@@Croja77 HighByte specializes in data aggregation, abstraction and organization -- it is not meant for visualization, it relies on other applications in the ecosystem to do that.
Hi Walter, Your videos have highly informative and have opened new perspectives while defining an IIOT Solution. Thanks a Lot!!!
Coming to Unified Namespace, does Wonderware/Aveva has any product providing this.
Glad it was helpful!
Hello - would are your thoughts on using Kafka as a unified namespace solution?
Kafka is not a UNS.
How does historical data (e.g. metrics stored in time series databases or e.g. stored by Ignition Historian Module) fit into the unified namespace?
Great question -- the historian monitors changing events in the namespace and stores them. Very often, we will store the last 24 hrs of datapoint x (time series) in a dataset topic in the namespace. This is a very common approach. It is important to remember -- the UNS is structure and events, the clients that plug into the UNS handle the capabilities (like history).
can i use arduino for iiot?
👏 yes! Arduino pro!
@@4.0Solutions i have arduino uno is it possible?
Is ThingworX Unified Namespace platform?
It is not -- it can connect to a UNS and publish back, but it cannot act as a UNS. Your question was answered in the Live Q&A on 1/11. Thank you for the feedback!
Show us a real world example, please
Check it out here! th-cam.com/video/vkTGRfwcFyM/w-d-xo.html