Unified Namespace (UNS) Panel Discussion at Tulip Operations Calling 2024

[@4.0Solutions]

A Big Thank You to Tulip! We’re grateful to Tulip for hosting us on the Unified Namespace Panel Discussion at Operations Calling 2024. It was an incredible experience sharing insights and connecting with industry leaders. 👉Learn more about Operations Calling and register for updates here: www.operationscalling.com

[@MNSundarNarayanaan]

As usual, Mr. Walker MAKES GREAT AGAIN progress in the UNS discussion with innovative topics.

[@youriregnaud8461]

An insightful debate that continues to elevate the discussion around UNS. Thank you, Walker, for your kind words about me and for allowing me to be a part of this journey with you this year. Looking ahead, future UNS discussions will likely focus on polyglot persistence-covering events, transactions, and historical data-within a shared ontology supporting an Industrial Knowledge Graph

[@4.0Solutions]

Thank you for the support, and thanks for the discussion idea.

[@karlbraun9507]

Great discussion. Moar please!

[@MosesMakarios]

Great panel chasing the hole on the needle

[@dronehomeless]

Let's go!

[@Lampshadx]

On Dylan’s question about transactional or historical data - say I have historical data in PI, historical maintenance records in FiiX, sure I can push all the snapshot and realtime events to my MQTT Broker, but then how does this help me if as a reliability engineer I want to get some process data (PI), maintenance data, and asset information to solve, say a static asset with fouling issues. I still have to access all of those systems separately or have a system integrator built that integration. How can a UNS help here?

[@SaurabhGuptacurious]

You at tulips 🙏🥳

[@VastCNC]

Why not get a UNS spec incorporated into opentelemetry? Would be great to build into a massive standard that’s already being adopted everywhere.

[@walkerreynolds973]

A spec is putting the cart before the horse right now… first thing we need is wider adoption so we have data to draw from on data and info models - it’s why standards struggle to get adopted, they are theory over application. We want the standard to be a codification of application not a theoretical model of what a committee deems ideal. 🙏

[@ДонПедро-г6ы]

Cool session! Just one question- are you guys familiar with OpenUSD alliance, founded by NVIDIA, Pixar, Autodesk, Rockwell, Wistron, Pegatron, Continental, Siemens etc?

[@walkerreynolds973]

Yes 🙏

[@meghansudha]

UNS need a additional layer for data cleaning, sorting to extract a clean data for dedicated applications

[@vitorioyosifov4842]

We have data hub for that at HiveMQ

[@CasaDeMold]

Simple question. I have a simple 2 steps for send, receive container. This send start in one department and received in another. How to determinate structural? Department A -> Actions -> Group of Actions 2 ? but how I can add it in department B? it will be duplicates records.

[@alexanderr2688]

Thanks for the discussion. Could you elaborate on the 1 million data points per second 30:10 ? If I am not mistaken, this is not a load a typical MQTT broker can handle. Do you use Kafka in tandem with it? I actually know you do as you said it on your recent video about historians, however it would be great if you could explain how to integrate Kafka and an MQTT broker together. My company uses Kafka as the primary strategy so that all domains interact with one another through it. Ima trying to figure out how to incorporate UNS into this.

[@walkerreynolds973]

Multiple brokers, horizontally scaled with Kafka streams for optimization to cloud.

[@meghansudha]

So people should be educated UNS as a data repository from manufacturing, operations, historical, Sales applications etc..

[@4.0Solutions]

The Unified Namespace (UNS) is not a data repository; it’s a real-time representation of the current state of your business. Rather than storing static data, the UNS acts as an architecture for structuring your data in a way that reflects the real-time status of your entire enterprise. It’s organized in a semantic hierarchy that brings together data from manufacturing, operations, sales, historical systems, and more. This enables all systems to publish and subscribe to relevant data streams in real time. So, instead of thinking of the UNS as a repository where data is stored, think of it as a live, continuously updated digital ecosystem where systems communicate and share data instantly, ensuring complete transparency across the business at all times.

[@CasaDeMold]

Or for example, I have 999 items created in one day. So it will be Factory -> Department -> Room -> Employee -> list of created items. But also I need who supervised when. Factory -> department -> room -> Supervisor -> list of same items?. Or in UNS should be only specific data for share this data, if we don't want to share we just don't put it in UNS. so should we have internal data schema and for public give some UNS format?

[@ДонПедро-г6ы]

Solution is not about to share or not to share. If a a business process owner need this data he subscribes on it in UNS without special requests-he gets it online once it is published in UNS. It’s interesting to hear a difference of UNS from MDM and ESB paradigms.

[@VastCNC]

Why not get a UNS spec incorporated into opentelemetry? Would be great to build into a massive standard that’s already being adopted everywhere.