10 · Cookbooks#
Short, task-first guides for the jobs you actually do.
A cookbook is a walkthrough of one real job, start to finish — no theory, no tour of every setting, just the steps to get it done. The rest of this manual explains what each feature is; these chapters show you how to use them together. Find the one that matches the job in front of you.
For your team#
The everyday cookbooks — written for the people who walk the site, log readings, and clear the work.
Running an inspection route — for the technician on the floor: pick up a route, work it stop by stop, and close it out.
Capturing field readings — for anyone taking readings at the machine: type a value by hand, capture a FLIR thermal image or a Bluetooth vibration signature on the phone, attach a note or photo, and see the health state land.
Triaging Needs attention — for the supervisor at the start of the day: set your alert emails, work the Needs attention list most-urgent-first, act on each item, and resolve it or let it auto-clear.
Building a route and setting alarm limits — for the person who sets things up: lay out a route from its stops and checks, and set the alarm limits that drive its health states.
For developers and integrators#
The technical cookbooks — for getting data in and out of Mechbase and wiring it to your own systems.
Analytics & BI — for the data analyst: pull your installation’s data into pandas, Power BI, Excel, or Grafana.
Consuming Mechbase data — for the integrator reading from Mechbase: feeds, bulk export, OData, and syncing findings into a CMMS.
Pushing data into Mechbase — for the integrator writing to Mechbase: upload readings, files, and photos, sync your registry by external ID, and drive routes — with the SDK or the
mechbasecommand-line tool.Streaming from a device over MQTT — for the firmware or edge engineer: stream readings straight from your own device (MaintNode doesn’t need this).
Note: the developer cookbooks are written in English only.