InCBM

InCBM is an Android app for maintenance teams that need to monitor multiple motors, pumps, and blowers without walking from unit to unit. The app receives vibration and temperature values from sensors attached to the machines, summarizes sensor health values, and alerts when values exceed your set thresholds.

Motors, pumps, and blowers often send signals before they fail, such as gradually increasing vibration or becoming hotter than usual. If teams only check these values during routine inspections or wait for monthly reports, they usually find out when the machine has already stopped working. InCBM collects sensor data as a history for each machine, allowing teams to see which machines are starting to malfunction and plan inspections before significant damage occurs.

InCBM integrates sensor health values, alert thresholds, trend graphs, notification history, and plant layout into a single app. Maintenance teams can see which machines need attention first.

• Home-screen overview — shows the number of machines at Critical, Warning, and Normal levels, along with the latest data update time
• Sensor-level health values — each sensor point has its own health value as a percentage, allowing comparison to determine which points are lower.
• Historical trend graph — Overall Trend and Health Trend plot values over time, showing when values started to decrease.
• Set your own alert thresholds for each sensor — the Condition Alarm page allows you to define what percentage is Normal, what range is Warning, and what is considered Critical.
• Acknowledged notifications — Every time a value goes out of threshold, the system records the time, source, level, and message. When Acknowledge is pressed, the item closes but remains in history.
• Create your own plant layout — create areas or zones, add machines, link sensors to machines, and edit or delete at any level. Data for each account is separate.

Daily dashboard

InCBM works in 4 steps: sign up, map your factory, set thresholds for each sensor, and monitor with acknowledge alerts. Sensor values are sent to the app via the nimitFlow workflow, so you don’t need to key in numbers yourself.

1. 1

   Sign up

   Sign up with your factory email, confirm with an OTP code (one-time password) sent to your email, and start using immediately. If you forget your password, reset it through the same email.

2. 2

   Map your factory

   Create areas or zones according to the actual site, place machines in each zone, and link sensors to the machines with named points.

3. 3

   Set thresholds for each sensor

   Define what percentage and above is normal, which range triggers a warning, and below what level is critical. Adjustments can be made at any time and take effect immediately.

4. 4

   Monitor and acknowledge

   View an overview from the homepage, open sensor graphs when abnormal values are detected, and press Acknowledge once resolved. All history is still available for review.

InCBM does not come with sensors. Machines must have vibration or temperature sensors and a nimitFlow workflow that sends data to the app. If the factory does not have sensors, we assess the site and suggest ways to collect data.

InCBM is suitable for machines with rotating parts, such as motors, pumps, and blowers, that have vibration or temperature sensors and require maintenance teams to see status on mobile devices or tablets. The table below summarizes suitable jobs, jobs that require additional preparation, and unsuitable jobs.

Between B.E. 2568-2569, we developed a tablet app extension for InCBM for a food and beverage factory through partners. The factory had already installed vibration measurement boxes at motors, pumps, and blowers, but the measured values were separated into 3 boxes. The app reads 76 Tags (data points) from these boxes via Modbus (industrial device communication standard) and receives data from 5 additional machines via Gateway (sensor signal collector)

The backend for this project runs on a server inside the factory. The app includes a zoned factory layout, status colors for each machine, trend graphs, per-sensor threshold settings, and an alert history with acknowledgement buttons. We have installed the app on 2 factory tablets and delivered the user manual. Client acceptance is still in progress

What we learned

Connecting with existing measurement devices depends on how the device sends data out. In this project, the app reads values and event (incident) lists from the measurement box, but cannot read analysis (analysis) messages and cannot send thresholds back to the box because the box does not support APIs (program connection interfaces). Thresholds set in the app are therefore used only within the app itself.

Plant layout, equipment list, and actual equipment images with sensor positions are the main information on the screen. Information and equipment obtained from the user side directly affect the project timeline.

What does it mean to you?

If your factory already has vibration monitoring boxes or systems, we start by checking which data output channels the devices use and what values they can read or write before designing the interface. If there are no sensors yet, we assess installation points and data collection methods first. You can prepare equipment lists, zones, and sensor positions from the beginning to avoid having to modify the plant layout later.