Unified Namespace and Historians 

It just admits one like, I would give it dozens. This is one of the most clarifying videos I have seen from you in the almost three years I've been following you. It's a masterpiece, another one

"...one of the things we want to solve with UNS was to historize things that typically are not historized" This statement is so eye opening for me, thank you very much for this super clear explanation. I am a fan of the channel, you are the best

I love so much this video you can imagine how you are making my Life just better. I have to fight with IT département about this issue so many time. Thank you very much!

Really interesting.Thank you!

Great video, discussion and insights as always!

I would also be very interested in seeing how you structure business data in the unified name space for example, employee names, and information, ERP data project information and how you handle projects and information within your company. These are really great videos. Thank you.

Key takeaways for me: Three types of data: Transactional, Time-Series (Historical), and Events. UNS → Kafka → Hadoop Great job Walker!

Excellent explanation of historian and data lake functuons. Looking forward to adding both to the virtual factory. Everything will be much clearer when we see the UNS, historian anf data lake in operation. Great question and answer format. Even better from a new hire, since we all benefit from foundational review. Thanks for sharing your question Justin!

Great video , full of useful information. But not sure if you answered the core question , why not build the UNS just out of historical data and allow all nodes "publish" and "subscribe" to the Historian and use the same. there are probably a bunch of performance related issues if you were to try to use a historian as the source of live data. Given the time lags I have seen I would not like to operate a SCADA that is pulling information from a historian. Historians weren't created to publish live values quickly. but Tech can be improved. So if there was a historian that could handle all the requirements of the UNS would it be a good idea to use it? To me the fist thought is that doing so would break to me the greatest asset of the UNS. Its vendor/application agnosticism. If 4.0 Solutions created a historian that came with in Integrated UNS* ( or MQTT Broker) I still would be slow to recommend it as the that plant would be forever tied to the Vendor As the UNS itself is not a node in the eco system, you can replace any node relatively easily, certainly very easily compared to replacing the same node in an I3.0 architecture. *as the UNS is more of a metaphysical construct( or amorphous blob) and not a thing that we can point to you could never really integrate it into a single node. As always love the stuff, and let me know if I've missed the mark completely

Awesome - a question I needed answering 😎 - cheers Walker

Historian should be namespace independent. Namespace is a viewpoint and viewpoints change over time.

hey, which drawing/whiteboard application is this? Great stuff!

When you have a semantic hierarchy using ISA95, how does a business transaction look like, let`s say a sale "living" in the ERP system, is it then a functional namespace tied to one of the Ent->Site->Area->Line->Cell? If that question makes any sense :)

Biggest missing item to start ML is "sufficient quantity of correctly labelled training data".

Would a historian consumer of the UNS at the enterprise level equal an enterprise historian I.e. it stores all the events from child nodes. Equally an historian consuming events at site level equals a plant historian?

I like the shirt! Walker. As always, awesome content! Agape! Bro.

Also masters computer science and large experience: The kid is right

#shfm "semantic heirarchy fn matters!!" ~ you know who

Great video Walker! Curious to get your thoughts on where the example below falls: 1,2 or 3? Also, with review by exception, is data compression in historians still needed? ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-aspp6TVb9Kw.html

I love so much this video you can imagine how you are making my Life just better. I have to fight with IT département about this issue so many time. Thank you very much!