PlantPulse
Machine Monitoring and Maintenance: Control Room, Technician and Planner Apps
A concept study: we worked up this product, its architecture and its screens as an example of how we would approach it. The screens use fictional demo data and are design concepts, not screenshots of a live product, and this is not a client project.

About the Project
PlantPulse is a design concept for three connected apps that a mid-size Indian factory could use to watch its machines and keep them running. A control-room app on Windows shows machine status and OEE (overall equipment effectiveness) on a wall of lines and machines. A technician app on Android handles job cards on the shop floor. A web planner gives maintenance managers the work order backlog, schedule, spares and history per machine.
The control room must never show a number it cannot explain. Every tile carries its data source, the time of its last data and a clear stale or offline state, so a shift lead can tell a stopped machine from a lost connection. Machine data arrives through OPC UA (the common industrial data standard) and MQTT (a light messaging protocol), kept vendor-neutral so the broker and connectors can be swapped without touching the apps.
An alert can create a work order in one step, and the technician sees it on a phone that works without a network and syncs when it is back in range. Every change has an audit trail and sits behind role-based access, and each build is signed with a software bill of materials kept alongside it. All screens in this concept use fictional demo data for an imaginary plant.
Why This Matters Now
Market, rule and technology context for this kind of product, checked on 16 November 2026. Each item names its source.
- CISA publishes industrial control system advisories continuously; one of them, ICSA-26-307-01, was released on 3 Nov 2026.CISA, via a GovDelivery bulletin, 3 Nov 2026
- Rockwell Automation's 11th State of Smart Manufacturing report says only 43% of collected data is used effectively; its Augury partnership feeds machine findings into Fiix MAX, which turns them into work orders.Processing magazine, reporting Rockwell Automation and Augury, 23 Jul 2026
- The open62541 OPC UA library released v1.5.5, which adds the ECC security policies of OPC UA spec 1.05.07, drops older ECC policies from the defaults and hardens against denial-of-service and memory-safety flaws.open62541 project mailing list, 28 Jun 2026
- CERT-In issued AI vulnerability guidelines for equipment makers and technology providers: keep a live software bill of materials, disclose Critical and High flaws to Indian customers and tie patch timelines to AI exploitability.S.S. Rana & Co., a law firm, summarising the CERT-In guidelines, 10 Jun 2026
- Microsoft's Azure IoT Operations 2603 release adds an optional OPC UA connector, MQTT broker reliability fixes and no-code dataflow graphs for moving machine data.Microsoft Tech Community blog, 9 Apr 2026
- Nexdigm, a consultancy, estimates the India smart factory market at about USD 7.7 billion in 2025, growing about 12% a year. This is a vendor estimate, and the forecast headline is blank on its page.Nexdigm (vendor estimate), Apr 2026
Requirements & Objectives
- Show machine status and OEE on a Windows control-room app, with the source, time of last data and stale or offline state on every tile.
- Read machine data through OPC UA and MQTT, vendor-neutral, with the broker and connectors swappable without changing the apps.
- Raise alerts from machine data and let a manager or rule turn an alert into a work order in one step.
- Give technicians an Android app that works offline: QR asset scan, job cards, photo and note capture, and sync when back in range.
- Give maintenance managers a web planner for the work order backlog, schedule, spares and the history of each machine.
- Keep an audit trail of every change and enforce role-based access for operators, technicians, planners and administrators.
- Sign every build and keep a software bill of materials for each release.
- Handle gaps honestly: mark missing data as a gap instead of filling it in, and keep jobs safe when a phone loses its connection.
The Engineered Solution
1Control Room app that shows its sources
A Windows desktop app with a line status wall and an OEE screen for each line. Each tile and each figure shows its source, the time of its last data and a stale or offline state, and the last good value stays visible but marked.
2Vendor-neutral machine data layer
OPC UA and MQTT connectors feed one internal data model. The broker and the connectors sit behind a small interface, so a plant can change either without a rewrite, and each connector can be patched on its own.
3Alerts that become work orders
Alert rules watch machine data, and an alert can create a work order that carries the machine, the reading and the time. This turns collected data into action instead of leaving it on a screen.
4Offline-first technician and planner apps
The Android app keeps jobs, machines and parts on the phone, scans QR tags, captures photos and notes, and syncs when back in range. The web planner shows the same work orders, technician load, spares and machine history.
Design Concept Screens
Design concepts with fictional demo data. They show how the product could look and work, not a live release.
01 / 05 Control Room app (Windows) - see every machine's state with its source and last data time, spot stale or offline data, and acknowledge alarms
Engineering Process
- Map the plant: lines, machines, data sources, shifts and who does what when a machine stops.
- Define the data model and the OPC UA and MQTT connectors, with a simulated plant for testing.
- Prototype the control-room wall and OEE screens with maintenance staff and refine how stale and offline states look.
- Build the technician app with a local database, QR scan, photo capture and a sync queue, and test it with the network off.
- Build the web planner: work order board, schedule, technician load, spares and machine history.
- Add the audit trail, role-based access, signed builds and a software bill of materials to the release pipeline.
- Run a pilot on one line, review the alert rules with the team and plan the rollout to the rest of the plant.
Production Tech Stack
| Layer / Component | Production Technologies |
|---|---|
| Control room app | Tauri 2 (Rust) with React and TypeScriptpackaged as a signed Windows installer |
| Technician app | React Native with ExpoSQLite on the phonea background sync queue |
| Web planner | Next.js and TypeScript |
| Machine data | OPC UA client (open62541 or node-opcua)an MQTT 5 broker such as Mosquitto or EMQX |
| Backend and data | Node.js APIPostgreSQL with TimescaleDB for time seriesrow-level access rules |
| Build and supply chain | GitHub Actionscode signingCycloneDX software bill of materials |
What the design aims for
PlantPulse aims to put a factory's control room, technicians and planners on one honest picture of the machines, where every figure shows its source and freshness.







