Skip to content

MindSphere Remote Services in a Nutshell

Remote Services provides the following set of key features and business values
1. Secure transmission of IP-based protocols and streams used by customers' apps
2. Forward network access for apps in Service Networks connecting to many Device Networks
3. Reverse network access for apps in Device Networks connecting to many Service Networks or MindSphere
4. Customer sets up Fine-Grained Access Control for users and devices
5. Tunnels provide protocol encryption and typically require minium network configuration
6. Downloadable software endpoints for Windows (R) and Linux (C) terminate tunnels and may be used to upgrade devices such as Edge Devices
7. IPsec routers may be used as hardware gateways in Device Networks
8. MRS administrative functionalities comprise supervision such as audit log or reports
9. Easy-to-use User Interface alleviates everyday use with a workflow-driven design

Key Features of Remote Services

Since MRS is a genuine MindSphere app and benefits from further MindSphere advantages
1. MRS is an out-of-the-box service used in your existing MindSphere tenant
2. MRS is a managed auto-updated app, which frees you from updates or patches and which scales on MindSphere cloud
3. MRS integrates with other MindSphere apps and solutions providing additional business value
4. MRS pricing is transparent and competitive
5. MindSphere development is certified per IEC62443-4-1
6. MindSphere operation is certified per ISO27001
7. MindSphere is also certified for TISAX (automotive) and CSA (Cloud Security Alliance)



Getting started with Remote Services

This section gives a brief orientation on the steps needed in order to get started with MRS.

Note: below actions may require different MRS user roles, which are described in section concepts used in MRS. User, who have multiple user roles assigned, may easily switch to other roles (top right corner of UI).

Step Action for Getting Connected see section
1. Add MRS to your tenant Product structure and procurement
2. Add needed MRS capabilities and resources Product structure and procurement
3. Assign users with MRS-specific roles and rights Setting things up - users and access
4. Create an adminstrative tree structure with sub-organizations and Sites Setting things up - users and access
5. Create a catalog of Protocol Application templates defining Device-specific access protocols Getting connected
6. Onboard Devices to organizational Sites and download MRS Endpoints where needed Getting connected
7. Assign Protocol Applications to Devices and establish connections to them Getting connected
8. Activate optional permission mechanism for Protocol Applications to enforce approval of connection requests Getting connected
Step Optional Action for Additional Use Cases see section
1. Onboard Devices in secondary Device Networks Advanced connections
2. Leverage IPsec hardware routers for brownfield connectivity Advanced connections
3. Leverage custom protocols & streams for connecting to Devices Engineering Option: use of custom apps and protocols
4. Setup remote engineering and commissioning with Siemens TIA portal Engineering Option: use of custom apps and protocols
5. Reverse connectivity enables Devices to access apps and data in Service Networks Data & Server Option: reverse access to other network
Step Support or Operational Action see section
a. Supervise or audit the system Supervising the system
b. Leverage MRS Endpoints on operating system level or on Edge Devices Appendix for Experts
c. Network setup with firewalls and proxies Appendix for Experts
d. Hints for overcoming hurdles Troubleshooting
e. Acronyms and some cross-references Glossary


Any questions left?

Ask the community


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


Last update: November 18, 2022