When addressing the first configuration of your DPS system or when performing a review to improve your existing system, we suggest you to divide the work in phases.
Each phase is characterized by:
- a single layer to focus your attention on
- a criteria of evaluation and completion
The phases corresponds exactly to main entries of the Servitly Console menu
In the Appearance section you set every single detail that affects the appearance of your DPS system: images, graphics, labels and messages.
Everything here has a purely aesthetic effect, not a functional one.
Through images and CSS you can set your DPS as close to your brand as possible, to make you feel at home and let your users feel at your premises.
Your partners’ brand
If you associate a subdomain to a partner, with the same approach you can change here the appearance of the DPS system published at the subdomain’ address according to your partners’ brand.
Help Center: Custom Domain
Labels and translations
Through Labels you manage every single piece of text in your DPS system. You can add as many languages and translations as you want.
Help Center: Labels
Through Messages you can configure all the messages the DPS system sends to the users when a certain event occurs.
Help Center: Messages
In the Catalog section you define the catalog of all the product models that will be connected to the DPS system.
Every product model is represented by a Thing Definition.
Help Center: Thing Definition
The catalog is hierarchical, allowing you to easily manage many product families, series, models and sub models. The hierarchy allow you to work only on what is different and share what is common.
In the Properties section you extend the metadata of the DPS business objects.
You can add and edit:
- Things properties
- Customer properties
- Location properties
- Partner properties
- User properties
In the RAW Data section you define all the metrics that a product sends to the DPS system.
Metrics are defined for each Thing Definition.
In the Computed Data section you can add new metrics that are computed taking RAW metrics as input.
In the Remote Control section you define all the possible commands and parameters that the DPS is allowed to send to a product.
Commands and parameters are defined for each Thing Definition.
In the Events section you define all possible event types that can occur on the product or location and that are worth to be recorded.
- Event instance: a single occurrence of an event that happened at a given moment in time
- Event type (or Event definition): the type of event that occurred
- Event class: a higher level for classifying event types
We classify event types in these classes:
- failure → the product is blocked, down, unavailable
- major anomaly → the product is still working but something wrong has happened that affects product health and could potentially cause a failure in the short term; a short term action is needed to avoid this risk
- minor anomaly → the product is still working but something wrong has happened that could potentially affect product health in the long term; there is no risk of short term failure, therefore a programmable action is enough to deal with this case
- operations → these are operational events that are not the main ones
- work session (or job) → these represent the jobs that the product performed and for which it was designed and purchased
- maintenance → a maintenance operation has been performed on the product
Event instances creation
Event instances can be created in the DPS system in two ways:
- detected automatically by processing RAW Data → a condition is checked against past values
- inserted manually by a user → a widget is exposed to the user
The purpose of insights is to extract synthetic, interesting and actionable information from data and events.
Insights are implemented through Insight metrics.
An Insight metric is a calculated metric that clearly and quickly illuminate and summarize a certain topic that is interesting for the product-service stakeholders
Help center: Insights
Potentially, insight metrics can measure and illuminate on all topics of interest to product-service stakeholders: health, productivity, consumption, quality, etc.
Learn more →
The purpose of Alerts is to raise the attention of the user on a particular event.
The purpose of Actions is to ask the user to performa a particular activity that is suggested or prescribed upon an event.
Automations let the DPS automatically launch command on a connected product or trigger a workflow through an external information systems (like FSM, CRM, ERP) upon an event.
In the Service section you define the packages composing your service offering.
In the Interfaces section you configure the organization, layout and content of any page of the DPS system.
Pages are organized in Views. Each View is dedicated to a single persona.