Asset Monitoring Example based on MindSphere Web Components
The Asset Monitoring Example offers a ready-to-use application that can be deployed to MindSphere. It is a compilation of the MindSphere Web Components Widgets into a user-friendly Dashboarding Application. It shows basic monitoring functionality by using the
Asset View, the
Aggregate Chart component and many more.
This example application should provide a first starting point to use the MindSphere Web Components with Mendix. For a general example application of MindSphere on Mendix refer the Pump Asset Example.
Get the demo application¶
The Siemens MindSphere Asset Monitoring Example can be downloaded directly via the Mendix App Store. To get the Web Components Widgets directly imported into your project, we recommend to start the App Store via the Mendix Modeler.
Follow the instructions to deploy a Mendix application at Deploying Mendix Apps to MindSphere.
Make sure to add the following MindSphere core roles to your app in Developer Cockpit to grant the needed access rights for the app.
|MindSphere core role|
Many MindSphere Web Components Widgets have been integrated into this Mendix build Example Application. For example,
- the component
Asset Viewwhich displays available assets in the current tenant.
Mapcomponent which displays a geographic map based on OpenStreetMap.
Aggregate Chartwhich shows the aggregated values of the aspect variables for a specific date/time range in a line graph. The selected range can be changed interactively by dragging, zoom in and out inside the chart, according to the set parameters.
More detailed information and a description of the web components in MindSphere can be found here.
Note that the used version of the MindSphere Web Components Widgets is only released for MindSphere within Region Europe 1 and not within other regions. Therefore, the Asset Monitoring Example based on MindSphere Web Components are also only released for MindSphere on AWS.
The application is based on the MindSphere Web components which can fetch data by their own from MindSphere by calling MindSphere APIs. This works fine if the app runs in the Cloud as a registered MindSphere app. In order to work locally, a MindSphere API reverse proxy is necessary. The MindSphereSingleSignOn Module provides such a local reverse proxy. The reverse proxy is enabled by default.
- Rule Widget: Currently it is not possible to delete a rule when running locally via the MindSphere API reverse proxy. The function works fine when app is running and deployed in the Cloud.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.