Service Levels

  • 2 minute(s) read

By providing a digital service for connected products, it is natural to offer service plans with increasing level, even on a pay-as-you-go basis.

Servitly allows Service Levels to be defined that are then associated with connected products.

A Service Level, is identified by a name and a progressive level, defines which digital services are enabled (e.g., alerting, consumption monitoring, productivity).

In addition, a Service Level can be associated with a pricing model.

Creating a Service Level

To add a new Service Level, you should:

  1. Enter the Service / Service Levels page.

  2. Press the Add Service Level button.

  3. Enter the desired Service Level name.

  4. Press the Save button and edit the additional information.

Service Level Features

For each Service Level you can configure the features the service level is enabling, for instance:

  • Alerting: the Event Engine verifies events only for the things associated with a service level having this feature enabled.

  • Notifications: in case of alert activated or cleared, the system notifies users only for the things associated with a service level having this feature enabled.

Predefined features are automatically managed by the system, so there is no need to perform any extra configuration activities.

In addition, you can specify custom features, that, within the dashboard’s template editor, you can use to display or hide specific tabs, widgets, or other graphic elements. This can be done by using a Visibility

Condition like the following one:

getServiceLevel()?.features?.remoteControl

For more information on how to define and use visibility conditions, see the Visibility Conditions article.

Pricing Models

For each Service Level, you can enable or disable multiple pricing models, which are summed up in order to compute the one-shot or monthly billing for each activated thing.

The available pricing models are:

  • Thing Pricing: customers will pay a fee for each connected Thing.

  • Authorization Pricing: customers will pay a fee for each user authorization.

It is possible to mark one Service Level as FREE, in this way when a subscription expires, the service plan associated with the thing is automatically downgraded to the free one

Thing Pricing

A Thing Pricing model defines an activation and a recurring price the user has to pay to keep using the thing with this service level and relative features.

With this model enabled, you can configure:

  • Activation fee: the amount the user has to pay at thing activation time.

  • Recurring fee: the amount the user has to pay to keep using the service each recurring period.

  • Recurring period: the time between each recurring payment (1 month, 2 months, 12 months, 10 years).

Thing Pricing (LIMITED)

Optionally, when configuring a Thing Pricing, you can enable purchasing for a limited period of time (e.g. 30 days). For example, a user who has the Free service level on a product can purchase the Premium level and try it out for 30 days.

This, can be done by specifying:

  • Limited Activation Fee: he cost the user must pay to activate the service level for a limited period of time.

  • Limited Duration: the duration in days, after which the user is automatically reassigned to the previous service level.

Currently, it is not possible to purchase a service level for a limited time period in case there is already an activated subscription on the same thing, and vice versa.

In cases where both limited and recurring prices are defined, within the Subscription page, the Customer user may decide which service level to purchase or subscribe.

Authorization Pricing

This model defines the price each end-user has to pay to access the thing.

With this model enabled, you can configure:

  • Activation fee: the amount the user has to pay to activate the service.

  • Allowed devices: the number of devices the user can use to access the service.

  • Included authorizations: the number of authorizations already included within the plan.