Default Service View

The initial configuration of your DPS already contains a Service View you can use as a starting point.

The default service view is composed of the following pages.

Overview

This is the home page of a service user who accesses the DPS. It is designed to provide a glance at the overall status of the install base.

It includes the Active Alert List widget displaying the presence of active alerts visible by the technician, including these details:

• machine ID

• customer and location

• alert title and short description

• duration (the time the alert is active)

• takeover status related to the event

By clicking on a row, the user can access the alert details page, which provides all the information about the event that generated the alert.

The overview page also contains the Map widget, which provides a map with the geolocated markers of the machines managed by the service.
Markers can be highlighted according to the presence of failures and anomalies.

Customers

This page allows technicians to efficiently manage and search for customers they are responsible for.

It includes a Customer List of customers visible by the service, including these details:

• customer name

• machine count

• presence of active failures

Machines

This page allows technicians to efficiently track, monitor, and search the machines they are responsible for.

It includes a Thing List of machines visible by the technician, including these details:

• machine ID

• customer and location

• connection status (offline/online)

• operating status (standby, working, error)

• presence of active failures

• presence of a service contract

ToDo

This page helps technicians efficiently manage their workload by listing pending actions (scheduled maintenance, urgent repairs).

It includes the Active Alert List widget displaying all the active alerts the technician must manage, including these details:

• alert activation date

• severity

• alert name

• machine ID

• customer and location

• alert duration

By clicking on a row, the technician can access the action details page, which provides all the information about the tasks to perform.

Data

On this page, technicians can download data for the machine they are responsible for.

Through the Data Export widget, they can select a period, a customer, and a set of machines and metrics to export through a CSV file.

How search works

Depending on the navigated page, the DPS user can interact with a Search Field to filter the page content, for instance:

• search for customers;

• search for machines with a specific model;

• search for events with a certain severity and timing;

• search for active alerts or historical alerts with a certain severity and timing;

• search for active work sessions or historical work sessions with a certain severity and timing;

• searches for actions;

• display aggregated values on the searched things (e.g., Value, Time Series Chart);

Service users can only search for objects limited to their context visibility (e.g., customers, locations, things, events, alerts, work sessions, actions).

The search form can be located at the top of the page. In this case, updating an input field updates all the other widgets on the same page that are bound to it.
It can be composed of a simple text key input, but it can also include advanced search inputs, allowing the definition of multiple search conditions.

The Search Field can be placed in a common template (e.g., Control Bar) and reused among different pages. In this case, when navigating another page, the search inputs are preserved.

Optionally, the search field can be embedded directly into widgets (e.g., Thing List). This is usually done when there is only one widget on the page.