Start with one equipment question
A compressor keeps running after the last shift. Is it serving a scheduled load, maintaining pressure against a leak, or cycling under an unexpected control schedule? A useful pilot records when the compressor runs, relates those periods to operating hours, and gives maintenance a short list of periods to investigate.
We start with one site, one asset, and one operating question. Bring the asset model, the records or controller points you can already access, and the name of the person who would act on a finding.
Connect, instrument, or custom design
- Connect what you have
- Read approved points from controllers, meters, building systems, or historians. Map equipment identity, units, timestamps, and operating state to the tools your team uses.
- Add measurement where it is missing
- Select commercial sensors, loggers, and gateways. Define mounting, power, network coverage, calibration, and commissioning before the readings become part of a maintenance workflow.
- Design and program a custom device
- Where the job calls for it, we can design electronics and interfaces, specify a board and enclosure, write embedded firmware, and connect the device to dashboards and maintenance systems. Candidate technologies include ESP32, STM32, Nordic microcontrollers, and industrial gateways. Selection depends on the measurements, site environment, and support requirements.
What the pilot leaves with your team
- A measurement plan. Agree which condition is worth tracking, how to verify it, and what decision the reading should support.
- A working monitoring path. Collect the agreed signal and show a usable history or alert with asset identity and data freshness.
- An acceptance record. Check the reading against a known reference and test what the system reports when a sensor, connection, or power supply fails.
- A handover and decision. Record who owns the device, reviews alerts, and maintains the installation. Recommend expanding, revising, or stopping based on the evidence.
The pilot is read-only. Existing controllers, interlocks, and staff procedures retain authority. Installation work and support responsibilities are agreed in scope, including the roles of facilities, IT, and qualified site trades.
See how the system is designed
Explore ESP32 and embedded monitoring systems → Compare platforms and follow worked examples through sensing, firmware, connectivity, fault handling, and field acceptance.