Это видео недоступно.
Сожалеем об этом.
What is the UNIFIED NAMESPACE?
HTML-код
- Опубликовано: 30 май 2019
- In this new video series, Walker Reynolds explains what is unified Namespace looks like and why it matters in the world of automation.
Watch this video next! Unified Namespace Q&A
• What is a Unified Name...
Thanks for watching!
Subscribe!
👉 bit.ly/SubTo40...
LinkedIn 👉 bit.ly/40Solut...
Twitter 👉 bit.ly/40Solut...
Want to learn more?
Join our community Discord Server
👉 bit.ly/Industr...
Take the FREE IIoT Mini-Course
👉 bit.ly/iiotmin...
#IIoT #Industry40 #DigitalTransformation
![Finesse2Tymes & Og Boo Dirty - Real Recognize Real [Official Music Video]](http://i.ytimg.com/vi/3xb4bl5PWF8/mqdefault.jpg)
I've been mapping ERP to MES & SCADA for the last years. I can confirm that maintaining those integrations is lots of work 😅
Thanks so much! We hope you can get your company on board with IIoT. We have specific videos on selling IIoT to manufacters if you need help! Always feel free to reach out to Walker or John McCloud on LinkedIn
Best and most simplified explanation of the Unified Namespace. All machine builders need to have MQTT Sparkplug B native to their equipment. This is a low-cost software based solution. Open architecture. I would question the ethics of any company that does not offer this interface.
Just listened to this video again explaining the unified namespace. The concept takes a while to solidify but it's worth the time invested. It's priceless to understand how the unified namespace is the path to the holy Grail of automation. The holy Grail being that business operations are in a closed loop where artificial intelligence can push suggestions, based on real time data, down to any layer of the automation stack for optimization.
Well said, Jeff.
I love watching these videos! Your passion makes it like I'm watching the crocodile hunter of IIOT. I'm learning a lot. Thank you!
Lol! Thanks Mann!
Walker I came across your fantastic and educative videos short ago, and I can only thank you for all knowledge I got. It changed completely my understanding for what IIoT and Industry 4.0 means. Thank you again and keep the good work
Thanks Afonso! 🙏
Thank you for the direct view point, I thought the video was very helpful
Just a superb video. You are making the world a better place.
Although already published in 2019, still very actual. My main questions would be 1) how do you explain to your customer that the data within the seperate nodes will be stored twice (which leads to double costs) and 2) with this universal namespace available would direct interfacing between nodes become obsolete in your opinion?
Simple... manually piecing together data costs way more in time, and opportunity cost of not turning data -> information. A Unified Namespace will not become obsolete because it's a concept. Every business needs one and has one whether they realize it or not.
As Walker Reynolds explains, the namespace can be the organization data hub based on ISA-95 “Hierarchical Equipment Model”, and I find it a great idea setting the UNS as the datacenter where the level 4,3,2,1 systems ecosystem publish or subscribe to information. but ISA-95 also defines the “Functional Data Flow Model” that describes how de information flows among the functions that cross the enterprise control interfaces. I wonder if you consider a madness empowering the Unified Name Space concept with an “Unified Operations Space” concept where possible allocate functions and activities to drive the UNS interconnected ecosystem.
Well said Tomas! Please join our Community Discord Server if you have not already! www.intellic.online/discord
You are very confident and are very thorough of the I4.0 environment . That's awesome. Kindly guide me how to gain indepth knowledge of the process of transformation, steps and kind of expertise required.
Thank you!
Awesome stuff👌... please could we get a video on the problems of connecting a process control system to the Internet and how to rectify these problems 😀
So your description at the very end of seeing all the data in real time in a folder like structure sounds like you just described looking at the Ignition Tag Browser, or similarly making the IIOT Namespace = Enterprise Historian.
Excellent video, again as usual!
Thank you!
Telecom equivalence is the TM Forum SID / a.k.a Information Framework
Thanks for all the information. My question is where does the data be stored? As I understand message brokers like MQTT, they are used to communicate but not to store.
Hello, Is the unified namespace a column based database where node ID is the main key? or how would you set it up?
Thank you Vilhelm!
Excellent
Thank you!
Walker, it's been 3 years since you've posted this video...is this still exactly your view, or do have any updates to this video? Also, can you explain how the single source of truth fits into this model? Thanks, and I appreciate all the content you post!
Do I need an ERP system if I build my UNS correctly?😊
ERP would be the name of the functions you created yourself in the UNS. So yes & no.
The unified namespace sounds the big data, where the data for all software levels are in the same place. Can we consider this assumption correct? If not, what is the difference between unified namespaces and big data? And btw, your videos are great. I can’t stop watching them. They are short and precise, without saying very enthusiastic 😃
The unified namespace is more of a concept than the data itself. Check out some of our other videos on unified namsepace!
Concept? Data have to be Modeled and classified. The term unified namespace seem to be ambitious doesn't represent anything.
@ 4.0 Solutions, where can I find the documented copies of your presentations, for citation and reference purposes. Thanks
Can the unified namespace coexist with the I3.0 systems and connections that exist throughout most businesses? Can we start to transition certain assets and business systems to the unified namespace over time without business disruption caused by things running on those 3.0 systems?
100% you take a two pronged approach. 1. How do I integrate legacy equipment with gateways? 2. What specifications do I give my OEMs for our minimum technical requirements for connecting straight into our IIoT Infrastructure.
just one Question ,Is the unified name space contain all the information from all node ,or i would have only those information which is needed ,depending upon node requirement.
Ml for ladder ? maybe optimize the collected data or parameters such as a PID gain, but the code itself will remains the same.
machine learning for ladder? Great question!
How do you do this on a brown field site ?
Edge gateways to convert the data into IIoT via an MQTT payload
I understand Namespace to serve Real-Time data, the current snapshot of our bussines, but, what about serving historical data, or the snapshot in a a specific period in the past ? I mean if namespace can be queried someway to retrieve time series, data joins or agregates as if it was a database engine. On my opinion a powerfull name space should be ready to answer to questions like how was my businness model one hour ago.
Node applications can store their own historical data... Such as a data lake or a Historian. You can also publish data sets back to the Namespace for subscribing to last 60 Minutes history data set.
@@4.0Solutions Thanks, I'll have a look to some node products for a better understanding.
Is unified namespace similar to kafka + datalake ?
Perhaps. Is Kafka: 1 - Open, 2- Lightweight, 3- Report by exception, 4- Edge Driven?
How to build UNIFIED NAMESPACE?
How difficult is it to get enterprises or small businesses onboard this unified namespace in terms of months?
It depends on the scope of the architecture -- getting started can take less than 1 day or it can take a month or more.
@@4.0Solutions More like years. Most companies I know have almost zero knowledge of this and getting them to see the value in it is difficult.
@@MarkMcMillen2112 we don't spend any time working with those clients. We allow them to educate themselves on their own time watching our videos, and when they are ready to Digitally Transform... they come to us.
Why don't you include PLM, PDM and documentation control? The biggest issue passing through these systems is an engineering change.
PLM apps and the data they contain become another node in the UNS data infrastructure.
Can we consider MQTT is an UNIFIED NAMESPACE? or MQTT is a part of UNIFIED NAMESPACE?
MQTT is one of several protocols you can use to build a Unified Namespace.
@@4.0Solutions Thanks, may you give some samples of other protocols that we can use to build a United Namespace?
Is the unified namespace an event bus or a data store/service?
You can think of it that way. It's not really a historical data store, but current events and current state of the business.
Is S4 Hana is unified namespace
Answering this question today
So what is difference between data lake and UNIFIED NAMESPACE? Where we should store UNIFIED NAMESPACE?
A datalake is a node application in the Unified Namespace. The Unified Namespace is a broker application. It can exist on a server... Or many servers at once depending on your Architecture.
@@4.0Solutions thanks, so in that case, May MQTT, Azure eventHub, Kafka, RabbitMQ considered as a Unified Namespace ?
@@ThuyLe-wq6vf We will answer this Tuesday!
The structure of the UN is more important than the concept of the data consolidation. Data- both process data and product data can all be structure in UN, which basically create digital twin if we would like to represent the physical entity. The holy grail is that you now are decoupled between he systems and allow your dependencies to be only on UN but rather than on each other.
Where can we see examples of a UNS layout?
We just did a live stream last week on it! ruclips.net/video/vkTGRfwcFyM/видео.html
how to send data from sensors to MQTT ?
Report by exception & edge driven.
cool video. Is there a standard taxonomy that is suggested to build this Unified Name Space?
Daniel Rojas ISA95
ISA 95 Thank you!
So basically unified namespace = centralized database ?
not really... it's the current state and all events. Not historical database.
MES, SCADA, PLM, ERP, ... no need to create a new entity. They all are just data (realtime and historic). A MES system is very good at handling manufacturing data, erp for business data... The key for integration is standardize the way data is stored and communicated across systems. Call this integration the unified namespace if you will.
Actually creating a new entity is paramount for reframing the way we think about integration. Too many engineers still thinking in industry 3.0 methodologies.
At least two issues with this: 1. If you want to cross report on these systems you're mining each one so you're going to need to create a cube or warehouse for that anyway. 2. When the systems disagree, which one is correct?