Default Back-office View

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

In some cases, the Service team is also responsible for the back-office activities, so you can merge the back-office functionalities directly into the Service view.

The default back-office view is composed of the following pages.

Overview

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

This page includes 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, anomalies, or other criteria.

Partners

This page allows the back office to manage and search for partners registered in the DPS.

It includes a Partner List of partners visible by the back-office entity (Organization, Partner), including these details:

• partner name

• partner country and city

• customer count

Clicking a row opens the Partner details page, while pressing the Add Partner button allows the back office to create a new partner.

Customers

This page allows the back office to manage and search for customers they are responsible for, or managed by a partner.

It includes a Customer List of customers visible by the back-office entity (Organization, Partner), including these details:

• customer name

• customer country and city

• customer creation date

• machine count

• last access timestamp

• any additional meaningful property (e.g., service contract associated with the customer).

Clicking a row opens the Customer details page, while pressing the Add Customer button allows the back office to create a new customer.

Refer to the Customer Base Management article for more details about how to manage customers.

Machines

The Machines page (subdivided into two tabs) allows the back office to search for and register new machines.

All Machines

This page allows the back office to search for machines.

It includes a Thing List of machines visible by the back-office entity (Organization, Partner), including these details:

• activation date

• machine serial number

• machine alias

• model

• customer and location

• subscribed service level

• operating status

• cloud status

Clicking a row opens the Machine details page, while to manually add a new machine, a specific location details page must be navigated.

Register Machines

This page allows the back office to register new machines that can be activated by customers.

It includes:

• Register Things widget that allows the back office to register new things (Machines).

• Thing List of available machines (Serial Number and Model)

• Connection Tokens List with all the Connection Tokens that can be used for thing activation.

Orders

This page allows the back office to manage orders.
Refer to the Order Management article for more details.

All Payments

This page allows the back office to monitor and manage payments.
Refer to the  Payments Management article for more details.

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

• search for customers;

• search for machines with a specific model;

• search for events with a certain severity and timing;

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

Back-office users can only search for objects limited to their context visibility (e.g., partners, customers, locations, things, events).

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.