Unified Namespace

Unified Namespace (UNS) is a concept which in my mind is exactly what CDF is all about.

We have some customers that choose ISA 95 as base, while others use f.i. CFIHOS and OPC UA companion models to map data against. The organization in Site - Plant - Area - Process/Production Unit - Cell/Unit/Tag is quite common among such standards, as are control systems and sensors connected to these.

CDF already includes many extractors connecting to either OT and/or IT, and the very contextualization we do in CDF, is a realization of a UNS knowledge graph/data layer.

We have not fixed our technology to hold only one version of, or to provide only one approach to UNS, but CDF is rather capable of supporting different organizations’ current IT/OT situation and build from this.

So, we don’t yet have a one template solution for this, and we typically use an «investigate - analyze - suggest - support» approach to this. Perhaps, over time, we will gather enough knowledge to add further product features and work patterns with guidance on «investigate like this - find your pattern from these familiar patterns - use our product like this» kind of templates.

Thanks for your feedback.

When saying to add further features, is there any upcoming new feature that replaces the need of having an MQTT broker to fetch real-time data from any historian or smart sensors?

No, this was a figure of speech of future possible developments, not anything planned.