First‑hand Experience: Sending Real‑Time Temperature Data to Fiix CMMS via Our New API

Our development team has recently advanced the final stages of the new Fiix CMMS API. Designed for seamless integration, the API allows external applications to communicate directly with Fiix, enabling native use of CMMS data across financial systems, maintenance tools, and machine‑to‑machine (M2M) environments.

My Experiment with the CMMS API

Over the past few weeks I tested the API’s ability to receive data from a low‑cost industrial sensor. I chose a BeagleBone Black and a TMP36 temperature sensor, costing under $60 in total. The goal was to stream temperature readings to Fiix and trigger maintenance tasks automatically.

TMP36 and BeagleBone Black setup

The BeagleBone Black is a budget Linux computer (~$55) available from Adafruit, Creatronic, and Sparkfun. The TMP36 sensor (~$3) outputs a voltage proportional to temperature, which is ideal for rapid prototyping.

After wiring the sensor to the BeagleBone with a breadboard, I adapted JavaScript code from Adafruit to read the temperature. Using the forthcoming client library, the device sent a temperature value to the CMMS every three seconds, tagging the data to an asset labeled “My office.”

The result was a continuous stream of temperature readings recorded in Fiix, each spaced roughly three seconds apart:

The stream of temperature readings

To demonstrate practical value, I configured a scheduled maintenance rule that activates whenever the temperature exceeds 35 °C. The work instruction simply reads: “Check the Air Conditioner – CMMS API experiment.”

The scheduled maintenance, set to create a work order when the temperature exceeded 35 °C

Success

Testing the trigger involved pointing a hair dryer at the sensor. As the temperature climbed, Fiix automatically generated a work order. Technicians received the notification within the CMMS, could review the sensor history, and address the issue—all without manual intervention.

Temperature datapoints after hair dryer test. The point that triggered maintenance is highlighted yellow.

Details of the datapoint that triggered the scheduled maintenance.

Beyond triggering work orders, the recorded temperature history can aid root‑cause analysis. For more complex diagnostics, additional sensors—such as pressure or humidity—could feed data into the same stream, providing a richer context for technicians.

Machine‑to‑Machine Communication and CMMS Integration

M2M capabilities open a spectrum of possibilities: a vehicle could log odometer readings via a mobile connection, automatically generating a service work order every 10,000 km; an air‑conditioner power meter might trigger maintenance when load spikes; vibration sensors on rotating machinery could flag abnormal conditions before failure. Even if not immediately actionable, continuous data collection creates a valuable operational record for future insights.

The Fiix CMMS API will be released soon, with access available to selected pricing tiers. If you have specific use cases or ideas, feel free to share them in the comments below.