Console Main Concepts

The Servitly console is a standalone web application you can use to manage your Projects and configure all the Environments where the DPS applications are deployed.

You can access the console by navigating to this URL

https://console.servitly.com

The console is designed to be accessed with these two account types:

Company: the owner of the DPS application, for instance, the OEM.
Each user under this account can see and configure all the environments of the DPS applications.
Expert Partner: the system integrator organization that configures and manages the DPS applications on behalf of the Company.
An expert partner can manage multiple companies.

Company View

This is the main page a Company user will find entering the Console.

The page is subdivided into two tabs:

Projects: the list of Projects with the relative Environments.
Users & Authorizations: all the users registered under this company, and the authorizations between each user and environment.

Expert Partner View

This is the main page an Expert Partner user will find entering the Console.

The page is subdivided into two tabs:

Companies: the list of companies managed by the expert partner.
Users & Authorizations: all the users registered under this partner, and the authorizations between each user, company, and environment.

By clicking on a company box, you can enter the list of Projects with the Environments configured for that company.

Project

A Project is the container of the environments where your DPS application is deployed.
In the top part of the project card, you can see the project name and the subscribed bundle.

By clicking on the ACTIVATE ENVIRONMENT button, you can activate the environment and start using it.
By clicking on an environment, you can enter the Environment Configuration page.

Each company has only one project, but if you need more than one, you should contact your Customer Success Manager or write to support@servitly.com.

Environment Types

Within a Project frame, you can find a block for each environment where the DPS is deployed.
To cover all the phases involved in your DPS development, you can use the following environments, each one with a specific purpose.

DEVELOP	The environment used to design your DPS by testing any Servitly feature. Here you can make changes, configure, and test all the features without breaking anything that is visible to your customers.
STAGING	The environment that uses the same configuration as `PRODUCTION`, but with sample data (Customer, Partners, Products). Here you can test in advance the configuration you are going to put in `PRODUCTION`.
PRODUCTION	The environment used to distribute the DPS to all your partners and customers publicly.
SANDBOX	The environment used to access Servitly features in advance of other environments. The SANDBOX must be enabled. Contact your Customer Success Manager to request access.

STAGING and PRODUCTION environments are subject to limitations as defined by the subscribed bundle.

Access to a company or environment requires explicit authorization for the console user.
You can authorize console users only to the company and environments where you are already authorized.

Environment Limits

According to the target environment, different limits are applied to the DPS in terms of the number of business objects (e.g., Customers, Things) you can create, the Data Points publishing rate, and the API request rate.

	DEVELOP	STAGING	PRODUCTION
Max Users	10	20	No limits
Max Organization	3	3	No limits
Max Partners	5	5	No limits
Max Customers	10	10	No limits
Max Things	50	50	No limits
Max API Calls	60/min	600/min	600/min
Max Data Points / Hour per Thing	3600/hour	10800/hour	10800/hour

Data Points per Hour indicates the maximum number of data points the remote product can publish to the IoT Connector channel every hour. For more details, see the Publishing Rate Limit article.