Default Customer View

The Customer View is the view used by customers to access the digital services related to the machines they use.
The initial configuration of your DPS already contains a Customer View you can use as a starting point.

The default customer view is composed of the following pages.

Overview

This is the home page of a customer user who accesses the DPS. It is designed to provide a glance at the overall status of their machines.

The overview page includes:

• The Active Alert List widget, which displays the presence of active alerts visible by the customer, including these details:

  • machine ID

  • location

  • alert title and short description

  • duration (the time the alert is active).

  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 Thing List widget, which lists the machines belonging to the customer, including these details:

  • machine ID

  • location

  • connection status (offline/online)

  • operating status (standby, working, error)

  • presence of active failures

  • other relevant machine insights.

  By clicking on a row, the user can access the customer product/machine details page.

Actions

This page helps customers to take control of pending actions (periodic calibration, cleaning procedures, consumable check, and replacement).

It includes the Action List widget displaying all the pending actions the customer should perform, including these details:

• machine ID

• location

• action name

• due date

• priority

By clicking on the action, the user can access the action details page, providing all the information about the tasks to perform.
In the sidebar menu, aside the page, it is possible to display a badge with the count of pending actions.

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 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);

Customers can only search for objects limited to their context visibility (e.g., 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.