Within Servitly you can leverage the following entities in order to map your company, partners and customers.
Within the DPS, you can define these entities:
An organization is a business unit inside the manufacturer company.
Recursively, under an organization, you can have sub-organizations. Supposing to be a multinational corporation, you will have the main organization and, under it, an organization for each country where your company is present. You can have also multiple levels (e.g. North Europe, South Europe).
In case your organization has external business partners like dealers, TACs (Technical Assistance Centers), resellers, or others, you can manage them by using the concept of Partner, which is an entity between the organization and final customers.
A partner is associated with an organization and has visibility on a set of customers.
Customers are the entities that own/use the products of the manufacturer.
A customer can be structured in locations, where the products are installed/located. 1
You can register business customers (B2B) or personal customers (B2C).
A location is a geographical place where the product is installed. A location belongs to only one customer, and a customer can have multiple locations (e.g. Site 1, Site 2).
It is the digital representation of a physical product/machine owned/used by the customer.
A product belongs to a location, and a location can have multiple products installed.
Represents a person accessing the application; the visibility on related entities depends on the parent entity to which the user belongs and the associated permissions.
A user is associated with a user type that defines what it can see and do through a set of permissions.
A user belongs to an entity, and an entity may have multiple users with different user types.
Below is an example of the ACME company that manufactures and sells its products worldwide. The main organization has sub-organizations for each region and uses local partners to provide support and maintenance.
Authorizations are interconnection between partners, organizations, and customers/locations.
Authorizations are defined by users having specific permission to do this, and optionally authorizations may have a start or end validity date. For instance, the TAC has visibility on a certain location only if there is a valid maintenance contract between the partner and the customer.
The visibility of products, clients, partners, and sub-organizations depends on the parent entity to which a user belongs, as well as the permissions he or she has been assigned.
It has visibility on all entities, including sub-organizations, partner customers, and their products.
It has visibility only to customers belonging to Italy, except for the Food Packaging SPA customer, which is visible by the ACME Italy sub-organization.
It has visibility on the products (Dishwasher 1) of the House (Munich) under the customer named Mark Hamill, and it cannot see the other location named House (Berlin).
It has visibility on one location and relative products (Conveyor 1, Oven 1) of the customer named Food and Beverage s.r.l.
It has visibility on one location of the customer named Food and Beverage s.r.l., but the visibility on the underlying products is limited to Oven 1, this due to the presence of specific user-to-thing authorizations (Oven 1 GRANT, Conveyor 1 DENY).