Siemens built Insights Hub on Mendix. We build the applications that make it useful to somebody.
MXTechies builds condition monitoring, alerting and maintenance applications on Siemens Insights Hub, formerly MindSphere, for US manufacturers who have the data and aren't acting on it.
Certified Mendix partner 250+ AI certified developers US, India and UAE
An animated reading from a press bearing sensor rises past its temperature threshold. The breach is routed to a named responder, and a work order is raised and tracked to closure.
Insights Hub is the Siemens industrial IoT platform, renamed from MindSphere in 2023 and now part of Industrial Operations X. It connects assets, collects operational data and runs analytics. Mendix is the Siemens low-code platform Insights Hub is built on, and it's what turns that data into an action somebody takes. MXTechies builds those applications for US manufacturers.
Siemens lists low-code application development as a core Insights Hub capability, and that platform is Mendix, which Siemens owns. It isn't a partnership claim — it's how the product is constructed. Building here extends the platform as designed, not from outside with a separate stack.
The people who build your Insights Hub applications also build on Teamcenter and Opcenter, which matters the moment a use case crosses systems.
| What stalled | Why | What closes it |
|---|---|---|
| Nobody owns the alert | A threshold fires into a dashboard nobody watches at 2am | Routing to a named responder, response recorded |
| It stops at the screen | Seeing a problem isn't fixing one | An app that raises the work order and tracks it to closure |
| It never left the pilot line | Built for one cell, doesn't generalize | A template configured per asset class |
| Application | What it does |
|---|---|
| Condition monitoring | Scoped by asset class, alerts routed to a named responder |
| Maintenance workflow | The alert raises the work order, assigns it, tracks it to closure |
| OEE and performance | Calculated from machine data, drillable from plant to asset |
| Energy monitoring | Consumption by line, shift and product, while it can change |
| Remote asset operations | Fleet monitoring for OEMs, service history per unit |
| Asset onboarding | A guided workflow, so connecting a machine isn't an IT ticket |
Also: quality correlation and multi-site rollups.
Four Siemens-published components cut the build.
Prebuilt UI for asset, time-series and status views.
A working application skeleton to build onto rather than from scratch.
Authentication against the identity provider you already run.
Connectivity to Insights Hub APIs and asset data without hand-rolling it.
Browse the full set on the Mendix connectors and widgets pages.
A reading on its own is a number. Joined to the systems that already run the plant, it becomes a decision somebody can make.
A stoppage becomes a reason code against an order. Opcenter MES
You know which machine revision the reading came from. Teamcenter with Mendix
Reporting covers the whole plant, not only the newly connected part of it.
The technician arrives knowing what the asset was doing.
Machine protocols on one side, business systems on the other. The application is what joins them, which is why the integration layer decides the timeline more often than the interface does.
Across US plants, the first application is usually condition monitoring with routed alerts. See manufacturing solutions and energy.
| Stage | What happens | Timing |
|---|---|---|
| 01 Assess | What's connected, and which decision nobody is making | Week 1 |
| 02 Prototype | One application on your real Insights Hub data | Weeks 1–3 |
| 03 Build | Roles, routing, escalation, edge cases | Weeks 3–8 |
| 04 Scale | More asset classes and sites by configuration | From go-live |
Stage 01 is about the decision, not the data.
Certified Mendix partner in the Siemens Xcelerator ecosystem, on a platform built with Mendix.
Delivery across six Siemens systems, so a use case that crosses them doesn't cross vendors.
Siemens-published components used, not rebuilt.
Delivery to US organizations, with teams in the United States, India and Dubai.
Yes. Siemens renamed MindSphere to Insights Hub in 2023, within Industrial Operations X. Same platform, not a replacement — existing applications and connections continue.
Yes. Siemens lists low-code development as a core capability, and that platform is Mendix, a Siemens company. Building with Mendix extends Insights Hub as designed.
Through OPC UA, MQTT and Modbus, and through Insights Hub APIs — PLCs, controllers, edge devices, SCADA and gateways.
Yes — cloud, edge or hybrid. Edge matters where a decision must happen faster than a cloud round trip, or where connectivity is too unreliable for cloud-only.
Most stalled US pilots didn't fail on connectivity. Nobody owned the alert, the dashboard didn't lead to an action, and it didn't generalize past one line. All three are application problems.
Yes. Applications join machine condition data to production context from MES including Opcenter, and to work orders and spares from ERP including SAP. That's what turns a detected condition into a work order with a real part number.
No. Existing plant data sources come in alongside newly connected assets, so reporting covers the whole plant, not only the new part of it.
A working prototype on your own data in weeks 1 to 3, and a production build by week 8. Scaling to further asset classes and US sites is configuration after that, not a rebuild.
Most plants have one: a screen showing a real problem to nobody in particular. Name yours. We'll show you what turning it into an assigned action takes.
Forty-five minutes · no prep
