# One governed data layer for your whole operation. > A common namespace for operating data: each source publishes once, with context and quality, and each system subscribes to what it needs. URL: https://www.summan.com/en/solutions/digital-twins/unified-namespace/ :::html

Without a Unified Namespace

Sound familiar?

  1. 01Multiple point-to-point integrations and higher cost
  2. 02Different interpretations of the same data
  3. 03Lack of traceability
  4. 04More time to get to analytics and AI

With a Unified Namespace

Data is born governed, with operational context, quality and traceability. One data point for many consumers: dashboards, historians, applications and models read the same data with the same meaning.

From raw data to governed data

The sensor is the same. What changes is what the data carries.

::: :::html
::: :::html
Without a Unified NamespaceRaw data, no context

Data travels without structure, governance or context. Each system interprets and handles it differently.

How the data arrives

  1. Sensorraw signal
  2. Technical taga code only its creator understands
  3. Value and timeno unit, quality or origin

Fragmented consumption

  • Dashboardlocal interpretation
  • Data lakedifferent normalizations
  • Reportsinconsistent units
  • Models / analyticscleansing in every project
What this causes
  • Multiple integrations and higher cost
  • Different interpretations of the same data
  • Lack of traceability
  • Longer time to analytics and AI
With a Unified NamespaceGoverned, contextualized data

Data is born governed, with operational context, quality and traceability. One source, for many consumers.

How the data arrives

  1. Sensorraw signal
  2. Edgecontext and quality
  3. Unified Namespacepublished once

What the data carries

  • Locationwhere it is in the plant
  • Meaningwhat it measures
  • Unit and rangehow to read it
  • Qualitywhether it is reliable
  • Traceabilitywhere it comes from

Dashboards, historians, applications and models consume the same governed data, without point-to-point integrations.

::: :::html
::: :::html

What you gain

Five advantages of a common space

  1. 01

    Decoupling

    Adding a model, a dashboard or an application is a subscription, without touching the sources.

  2. 02

    A single source of truth

    The meaning of each variable is defined once for the whole organization.

  3. 03

    Quality and traceability

    Every data point travels with its quality status and origin.

  4. 04

    Scalability

    From one line to a site and from a site to the whole company, with the same structure.

  5. 05

    Foundation for the twin and AI

    The current state of the operation is available in real time, ready for the models.

How it connects to the digital twin

With a common space, every new model or dashboard is a subscription, not a new integration project.

Edge Computing adds context and quality to data at the plant before it is published. Explore the Journey to Digital Twin too.

Start governing your operating data.

With an assessment we define how to integrate your sources on top of each plant's installed base.

Request an assessment
::: :::html
::: ## Frequently asked questions ### What is a Unified Namespace? A common namespace where each source publishes its data once, organized according to the plant structure and accompanied by its context, and where each system subscribes to what it needs. It replaces point-to-point integrations. ### Does it work in the cloud or on-premises? Both, or in a hybrid model. The solution adapts to each client's infrastructure and data governance. ### Do we need to change instrumentation or the control system? The architecture builds on the installed base. We start with an assessment to define the safest way to connect each plant. :::html
:::