---
title: "Initial DPS Configuration"
slug: "initial-dps-configuration"
updated: 2026-07-06T10:40:22Z
published: 2026-07-06T10:40:22Z
canonical: "learn.servitly.com/initial-dps-configuration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.servitly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Initial DPS Configuration

This is the initial guide we recommend you follow before going in-depth with more advanced use cases. Let's start with the simple visualization of metric data published by a connected product. Whether you're tracking temperature, humidity, power consumption, or any other machine parameter, setting up the correct initial configuration ensures accurate data collection and visualization.

By the end, you'll have a simple functional setup that can be used as a base for more complex use case configurations.

Here are the main steps:

1. Establishing the IoT connection.
2. Creating a Base Thing Definition.
3. Creating the initial Product Model.
4. Creating an initial product instance.
5. Defining the Status metric.
6. Publishing IoT data.
7. Try your configuration.

## Establishing the IoT connection

Before starting with the actual configuration, we suggest that you establish and implement the method by which the connected products communicate with the DPS system. For this purpose, Servitly offers these options:

1. [Direct connection via MQTT](/docs/direct-http-connector)
2. [Direct connection via HTTP](/docs/direct-mqtt-connector)
3. Cloud-to-Cloud integration with a [market IoT platform](/docs/third-party-connectors)

If you have to choose an IoT connector, you should also consider:

- Will your connected products need to receive remote updates?

*If yes, we suggest you use a connector based on MQTT.*
- Do your connected products have limited bandwidth or data traffic?

*If so, we recommend using an HTTP-based connector, which avoids using an always-open channel such as MQTT.*

If you do not have a ready-to-connect product, you can take advantage of the concept of [Virtual Things](https://learn.servitly.com/docs/virtual-things), which allows you to publish data to the DPS without having a physical product.

## Creating a Base Thing Definition

In the [Catalog / Thing Definition](/docs/thing-definition) page, you can create the Thing Definition that abstractly represents your base product. You can define a hierarchy of thing definitions, where each level inherits common elements from the parent level. In this way, you can create a generic Thing Definition that is extended by more specific ones. For instance, below you can see a generic *Machine Tool* definition that is inherited by others, like *Drilling Machine*, *Sawing Machine*, and so on. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(683).png)

This thing definition will be used to define all the elements that are common to more specific thing definitions.

1. Click the *Add Thing Definition* button.
2. Provide the required information and press *Save*. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(714).png)

For more details on how to configure Thing Definitions, you can refer to the [Thing Definition Insight Metrics](/v1/docs/thing-definition-configuration) article.

## Creating the initial Product Model

We are currently defining a generic product model, which we can call *Alpha*. When you go on to define the actual product models you want to manage, you can rename them whatever you like.

This Product Model is mandatory to register a thing in the DPS.

1. Enter the [Catalog / Product Models](/docs/product-model) page.
2. Click the Add Item button. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(708).png)
3. Select Product Model.
4. Enter the name (e.g., Alpha) and then press *Save.*
5. In the Thing Definition, select the Base thing definition (or the one you created). ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(709).png)

## Creating the initial product instance

When configuring the DPS, and especially a thing definition, it is essential to be able to try the configuration in the DPS.

Below you can find all the steps you can follow to manually create a new thing in the DPS representing the instance of your *Alpha* product model.

1. In the Console, you can leverage the [User View](/docs/user-view) function to impersonate a specific Persona in the DPS. In this case, you should create a back-office user view, which is required to create a Thing that you can then use to try your configuration.
2. Select the back-office user view and navigate the DPS.
3. Enter the *Customers* page, select one of the sample customers already present, and then a location. In the alternative, you can create your own customer to be used for development.
4. From the [Thing List](/docs/thing-list-widget) in the location details page, click the *Add Thing* button.
5. Enter the *Name* and the *Serial Number*.
6. Select the *Alpha* product model and press *Save* to create the thing
7. Select the [*Connection*](/docs/dps-connection-mapping) panel and configure the [IoT Connector](/docs/iot-connectors-1).
8. Provide the *Asset ID* (you can reuse the Serial Number) and press *Save*.
9. In the [*Cloud*](/docs/cloud-status-2) panel, you will see that the status changes from `PROVISIONING` to `ACTIVE`. This operation takes a few seconds. In the meantime, the page is automatically updated.

## Defining the Status metric

Among all the metrics you can define, the operating status is the most important one to configure first, because it provides information about what the remote product is doing (e.g., `STANDBY`, `WARMUP`, `HEATING`, `CUTTING`, `CLEANING`), and gives meaning to everything else the connected product publishes.

1. Enter the [RAW Data](/docs/raw-data) page.
2. Select the *Base* thing definition. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(712).png)
3. Press the *Add Metric* button and provide the required information. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(711).png)
4. Press *Confirm*, and the metric will be created.
5. In the Mapping section, verify whether it is ok for your machine. If not, you can change the mapping according to how your machine is publishing the operating status through the [IoT Connector](/docs/initial-configuration#establishing-the-iot-connection). ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(713).png)

## Publishing IoT data

Now you are ready to publish data to the created thing, and to do this, you can:

- Publish data through the [IoT Connector](/docs/iot-connectors-1). This is feasible if you have a thing that is already publishing data, or if you are using a client capable of doing so (even emulated).
- Use Virtual Thing based on [CSV](/docs/csv-data-publishing). This requires a CSV with sample data for each metric you want to publish.
- Use Virtual Thing based on [Data Mirroring](/docs/thing-data-mirroring). This requires a thing already registered and connected to another environment (e.g., `PRODUCTION` → `DEVELOP`).

## Trying the configuration

Before continuing with more advanced concepts and use cases, now is the time to check the result of the configuration done so far.

1. In the Console, select or create a new [User View](/docs/user-view) to impersonate a customer user.
2. Navigate the DPS by using the customer user view.
3. Enter the *Machines* page and select the thing associated with the *Alpha* product model. The predefined thing view is displayed.

When the Thing Definition is [created](/docs/initial-configuration#creating-a-base-thing-definition), the default customer view is also created with some widgets helping you in the early configuration phases, so for the moment, you don’t need to edit any template. Within the predefined thing view, you can find a single page with:

- [Metrics Data](/docs/metrics-data-widget) widget that displays the last values of all defined metrics. The widget is automatically refreshed every 30 seconds. You will see metrics highlighted in case a new value is detected.
- [Message Logger](/docs/message-logger-widget) widget that displays any incoming message to the IoT Connector. Note that the widget is real-time updated and there is no message history, so you need to keep the page open to see incoming messages.

This allows you to check that all metrics are defined correctly. If you publish a message to the IoT Connector, you will see the incoming message in the Message Logger widget and, a few seconds later, the new metric’s value in the Metrics Data widget.