Skip to main content
Version: Next

Setup Overview

This section of the documentation describes how to setup the individual resources offered by Tributech.

The following table offers a quick overview covering our core components. Product Overview

Tributech Node

The Node serves as central platform and is the part of the system which should be deployed first, since it allows you to connect Tributech Agents. Please refer to the Node setup to learn more about the available hosting options.

Tributech Agent

The device that is responsible for transmitting auditable data is the Tributech Agent. This device can be an Embedded device or also an Edge device. There are three variants of the Agent available:

  • Agent Edge (software-based)
  • Agent Embedded (hardware-based)
  • Agent Integrated (running at the Tributech Node)

Tributech Agent Edge

The Agent Edge is our containerized, software-based solution perfect for all devices/environments offering a container runtime. Learn more in our setup guide.

When to choose:
This option should be preferred if you have access to the controllers of the machines on the shop-floor but not to the sensors directly (e.g. Industrial IoT Gateway).

Data signing:
Data is signed on the shop-floor still close to the data-source (the closer to the data-source, the better for security).

Integration:
You can use your existing connectors, the Agent is integrated at the message bus layer (e.g. MQTT, OPC-UA, Beckhoff ADS,...).

Tributech Agent Embedded

The Agent Embedded is our solution designed to read data directly from interfaces/sensors on the hardware level. It uses a dedicated hardware security module for signing the data-streams. The Agent Embedded is available as either a C implementation or as a dedicated hardware module.

  • OEM Module
    We offer two variants, the OEM Module itself which can be directly integrated into your hardware design and an Arduino Shield for prototyping. The shield can be used with all popular hardware development platforms like Arduino Uno, STM32 Nucelo, Infineon XMC Relax Kit and more.
    OEM Module
    An IoT device based on the OEM Module typically consists of three parts. Part 1: the Tributech OEM Module which takes care of connectivity, data management, configurations, updates and security. Part 2: the application-specific microcontroller which takes care of data pre-processing and business logic. Part 3: the sensors and interfaces needed for the application. OEM Board
    On the device side, the OEM module provides a UART interface for exchanging configurations, providing telemetry data and performing updates. This allows developers to focus on firmware development for data pre-processing and sensor/interface integration, as all complexity is abstracted via an easy-to-use interface.

    Overview highlighting the role of the OEM module: OEM Board

When to choose:
This option should be preferred if you have access to your system on a hardware interface/sensor level.

Data signing:
Data is signed as close as possible to the data-source (the closer to the data-source, the better for security). This option offers the highest level of security.

Acquire:
Contact us if you need more information or wish to acquire one of our embedded devices.

Tributech Agent Integrated

The Tributech Node comes with an integrated agent, there is no additional setup required for it.

When to choose:
This option should be preferred if you are looking to use a software system (for example an ERP system) as a data-source.

Data signing:
Data is signed as soon as it reaches the node.

Integration:
Data can be sent to the integrated agent through the Trust-API - have a look at API integration. Generated API Clients for C# can be found here.