Skip to content

MindSphere Remote Services - Sample Setup Used in Documentation

This user documentation uses a MindSphere tenant to which MRS was deployed. We will setup this MRS instance by means of various quick start guides outlining to the reader, how to work with the provided MRS functionality and workflows.

The upper half of below MRS setup outlines the elements, structures and users that are relevant to the Service Network, whilst the lower part outlines those relevant to the Device Networks.

In this sample setup the topmost Organization level is called "Service Global", which has two Sub-Organizations named "Region Europe" and "Region Asia". The associated administrators manage the MRS-wide catalog of Protocol Applications, which is a customer-specific and administrator-defined set of Device-protocols as supported by the procured commercial offerings and capability options outlined in Product Structure and Procurement.

Beyond that, the user "Service Admin Global" as the responsible tenant administrator for MRS may further manage a set of customer-specific Product Types. These are relevant for Fine-Grained Access Control to ensure, that users with the MRS role of "Remote User" may access only Devices with specific type tags as outlined in Concepts Used in MRS. Such access rights should be granted to them by the respective "Site Owners". In this example we assume two Remote Users named "User Europe" and "User Asia" both belonging to the company owning the Service Network.

Sample Tenant Used in Documentation

The sample setup uses three different Device Networks referred to as Sites. Here, these are called Munich, Istanbul and Pune. Each of these Sites comprises several Devices registered with MRS, such as IPCs, PLCs, IEDs, HMIs or even hardware routers.

Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: September 6, 2022