An IOTICS data ecosystem is formed of multiple IOTICSpaces. Each party has its own IOTICSpace, which contains one or more Digital Twins. Each IOTICSpace presents its own API.

On this page we will cover:

An introduction to IOTICSpace

In IOTICS, each party has its own IOTICSpace (represented as a circle), which together form a decentralised data ecosystem.

Each IOTICSpace contains one or more Digital Twins (represented as a dot). The twins can publish and exchange data with other Digital Twins in your own or others' IOTICSpaces.

The owner of an IOTICSpace is in control of all its twins, and therefore of all the data stored and streaming through them. Owners can decide to make their twins visible (or not) and to share data with all, none, or a select number of parties and, by extension, join one or more data ecosystems or consortia.

The formation of IOTICSpaces might look similar to the illustration above where all parties can find and access data from the other parties’ shared twins.

Each IOTICSpace comes fully deployed and set up on the IOTICS Cloud. The ecosystem is built on a decentralized infrastructure, so each IOTICSpace is deployed on its own and data separation is guaranteed. Each IOTICSpace also presents its own API.

Technical components

Each IOTICSpace corresponds to one node called “Host” on the decentralised IOTICS network. The Digital Twins therefore “live” and are stored within the Host.


IOTICSpace = Host

For the purposes of this guide, we’re using the terms IOTICSpace and Host interchangeably.

Each host has its own metadata storage database, therefore ensuring separation of metadata and data per IOTICSpace (important for machine-readability) as well as guaranteeing the separation of data by owner across the network.

Each IOTICSpace or host has:

  1. One Twin of the Host (Host Twin), controlling access permissions
  2. Multiple Digital Twins, owned and controlled by the owner of the IOTICSpace
  3. Its own API
  4. Its own metadata database
  5. Its own user interface, allowing non-technical users to create and manage Digital Twin Models, Twins and Data Interactions. Your user interface can be accessed at https://{your-space-name}

When configuring your IOTICSpace, consider the following best practices:

  1. Who owns and controls the data? An IOTICSpace should belong to one and only one party, which owns and controls all the data within it.
  2. Who should have access to the data? And who shouldn’t have? Access to your IOTICSpace can be granted to all, none or select other IOTICSpaces. You can update your IOTICSpace permissions through the Host Twin (see Selective Data Sharing)
  3. If you require more granular access permissions, remember that selective access can also be granted on a Digital Twin level to all, none or select other IOTICSpaces (see Selective Data Sharing).

IOTICSpace access permissions

IOTICS distinguishes between two settings:

  1. Visibility: whether a Digital Twin's metadata is visible (or not) to another IOTICSpace (the F in FAIR)
    • this is set by updating the Host Twin's or Digital Twin's Visibility property
  2. Accessibility: whether a Digital twin's data can be accessed (or not) by a Digital Twin from another IOTICSpace (the A in FAIR)
    • this is set by updating the Host Twin's or Digital Twin's AllowList property
    • it can be enabled for the entire IOTICSpace and selectively on a twin-by-twin basis

For more information about access permissions, including for examples of how to update them, go to the Selective Data Sharing page.

Did this page help you?