Appendices#
Quick references to keep beside you: the vocabulary, the keyboard shortcuts, the health states, and how Mechbase connects to other systems.
A. Glossary#
Term |
What it means |
|---|---|
Installation |
A single physical site Mechbase monitors — a plant, terminal, factory, or vessel. Its number appears in the web address ( |
Section |
A major area of an installation (e.g. Utilities). |
Zone |
A specific location within a section (e.g. Pump Station). Locations read as |
Zone type |
A kind of zone (e.g. a room type), created by a room-list import. Documents added to a type appear on every zone of that type. |
Asset |
A piece of equipment (pump, compressor, panel…). Its equipment type is rotating, electrical, static, or infrastructure. |
ISO 10816 class |
The vibration severity class of a rotating machine (I–IV); it sets the default vibration alarm bands. |
Measurement point |
One specific thing measured on an asset, in one place — e.g. drive-end vibration. Named by its location (Motor DE). |
Measurement / reading |
A single value recorded at a point in time, automatically or by hand. Numbered per point (the number in its web address). |
Transducer type |
What a point measures: vibration, temperature, thermography, ultrasound, pressure, flow, current, voltage, tachometer, counter, boolean, state, production. |
Trend |
A point’s readings plotted over time, with alarm limits shown. Vibration points show a grid of trends, one per metric. |
Normal band |
Where a value usually sits — the middle 80% of its running readings over the previous 30 days. |
Waveform / spectrum |
The full vibration signal behind a reading, and its frequency content. Opened in the Inspect panel. |
1X / 2X |
The vibration at once and twice shaft speed, with its phase — measured when a tachometer is wired. |
Bearing |
A rolling-element bearing from the library (or added by you), with its defect frequencies BPFO, BPFI, BSF, FTF in orders of shaft speed. |
Baseline |
A point’s learned “normal”, used by relative alarm rules. Can be cleared or relearned from a date. |
Finding |
An analyst’s recorded diagnosis on a reading — fault, severity, recommended action, due date — with a work-order status (Open, Acknowledged, Closed). |
Alarm rule |
How a point’s status is judged — a method (threshold, narrowband envelope, maintenance-due), a direction, and Warning/Critical limits. An installation (or ISO) default, or a per-point override. |
Bearing band rule |
An alarm on a bearing’s defect band, as an absolute value or a multiple of the baseline. |
Health state |
An asset or point’s condition: Nominal, Check, Warning, or Critical. See Appendix C. |
Silent |
An asset whose sensors used to report but haven’t for 30 days, or whose live feed has stopped. |
Stale |
A running-state or device signal that hasn’t checked in recently. |
Production / running state |
Whether a machine is running (On / Off), from a tachometer, a run signal, or the vibration itself. Totalled as running hours. |
Run detection |
How a vibration sensor tells running from stopped, learned from its own history. |
State point |
An on/off signal (a fault contact, a run lamp) recorded as periods rather than a trend. |
Needs attention |
The list of every asset that isn’t Nominal, most urgent first, followed by silent assets — on the home page and its own page. |
Points page |
Every measurement point on the site in one filterable table. |
Hours page |
Running hours for every asset that tracks them. |
Dashboard |
A live board of chosen points, in sections, refreshing every minute. Built by staff; an automatic board shows live MaintNode points until one is built. |
Route |
A repeatable inspection round, made of stops and checks. |
Stop |
A zone or an asset visited during a route. |
Check |
One item completed on a route. Types: Pass / Fail, Numerical, Multi-check, Measurement. |
Survey |
A route built as you walk it, starting from an empty checklist. |
Run / execution |
One performance of a route — Running, Completed, or Cancelled. A route has at most one run in progress. |
Non-conformity (NC) |
A check that didn’t pass, graded Warning or Critical. Pinned to the asset’s activity until Resolved. |
Amend |
Filling in a completed run afterwards — skipped checks, late readings, photos, notes — by the person who ran it or a staff user. |
MaintNode |
The edge device wired to your sensors (built-in inputs, USB DAQ, Modbus) that measures on a schedule and uploads readings into Mechbase automatically. |
Acquisition group |
A set of channels on one MaintNode measured together, on the same hardware and schedule. |
Channel |
One input on a MaintNode device, connected to a measurement point as a source. |
Claiming |
Registering a MaintNode to your installation, from its label QR code or its UUID. |
Source |
Where a point’s data comes from automatically — a MaintNode channel, or an MQTT device channel. |
Undo |
The short-lived button that reverses a small delete (a reading, a note, an alarm override, a route check). |
Member |
A user on an installation’s Users list — they can open it and work with everything in it. |
Staff |
A user who can also build dashboards, amend others’ runs, delete equipment with history, and use the admin back office. |
Microsoft sign-in (SSO) |
Signing in with a Microsoft 365 work account, for organisations set up for it. |
B. Keyboard shortcuts#
Mechbase is built to be driven from the keyboard. Page shortcuts are shown as small key caps on their buttons, and don’t fire while you’re typing in a field or a dialog is open.
Anywhere
Key |
Action |
|---|---|
|
Open or close the menu |
|
Home |
|
Routes |
|
Needs attention |
|
Hours |
|
Points |
|
Dashboards |
|
Search |
|
Back — up to the page above; also closes dialogs and the menu, and leaves a focused field first |
|
Move through and pick from the menu, the installation picker, and pickers |
|
Submit the current form (sign in, save, create) |
On a specific page
Key |
Action |
Where |
|---|---|---|
|
Edit |
Section, asset, point, route |
|
Add a zone |
Section page; an empty route |
|
Add a measurement point |
Asset page |
|
Record a reading |
Measurement-point page |
|
Search |
Readings list; Bearings |
|
New route |
Routes |
|
Start / resume a route |
Route page |
|
Latest report |
Route page |
|
Route history |
Route page |
|
Post or save a note |
Asset notes; reading and check notes |
C. Health states#
Every asset and measurement point is always in one of four states, coloured the same way throughout Mechbase — and always written out as a word as well, never shown by colour alone.
State |
Meaning |
What to do |
|---|---|---|
Nominal |
Within normal limits; healthy. |
Nothing. |
Check |
A soft, early signal that something is slightly off baseline. |
Keep an eye on it. |
Warning |
Clearly degraded beyond normal limits. |
Plan an intervention. |
Critical |
A severe deviation. |
Act now. |
How they look: in tables, Check, Warning, and Critical rows are tinted, and Warning and Critical rows carry a small ▸ flag in the margin; state chips put a solid ■ before the word. A hollow □ marks Stale data, and Silent marks an asset that has stopped reporting — both are about the data, not the machine.
States are derived automatically from measurements and inspections — never set by hand — and a short averaging window means they reflect a sustained pattern, not a single reading (Measurements, trends, and alarms). Every change is timestamped and written to the activity feed in plain language:
“Degraded to warning / critical” — the condition got worse.
“Improved to check / warning” — it got better but isn’t fully healthy yet.
“Returned to nominal” — it’s healthy again.
An asset’s state is the worst current state among its points and its open non-conformities. It feeds the in alarm count on the asset, the Needs attention list and its menu badge, the section cards’ warning and critical counts, dashboards, and alert emails.
Times are shown in your own time zone, and recent dates read naturally — Today, Yesterday, 3 days ago, 2 weeks ago.
D. Connecting Mechbase to other systems#
Mechbase is designed to fit alongside the rest of your toolset rather than stand apart from it:
MaintNode devices — measure on a schedule, keep readings on the device, and upload them to Mechbase over HTTPS, landing on measurement points through their sources. Devices are claimed to an installation from their label’s QR code (MaintNode devices and automatic data).
Modbus — a MaintNode can read registers and coils from a PLC, drive, or gateway over TCP or serial (RTU), and feed them to points like any other sensor.
Your own devices — stream readings over MQTT (Streaming from a device over MQTT), or push them through the REST API and SDK (Pushing data into Mechbase).
Analytics & BI feeds — a read-only API pulls measurements, events, and inspection data into pandas, Power BI, Excel, or Grafana, with bulk export and an OData feed (Analytics & BI, Consuming Mechbase data).
CMMS — two ways to connect a maintenance system:
the findings API, which lets any CMMS pull analysts’ findings and report back a work-order number and status (Consuming Mechbase data);
a built-in AIMMS connector, set up by Arpedon, which mirrors your AIMMS asset structure into Mechbase, pushes inspection non-conformities back as AIMMS maintenance tasks, and keeps AIMMS operating-hours counters up to date.
Ultrasound surveys — UE Systems DMS exports (
.dmsbak) can be imported by Arpedon, bringing in the survey points, dB readings with their sound and image files, and the survey rounds as completed route runs.Email — alert, route-report, and export-ready notifications, chosen by each user (Getting started).
Raw-signal files — every vibration waveform can be downloaded as the native
.drdata-recorder file for analysis in specialist tools (Measurements, trends, and alarms).Microsoft 365 — single sign-on with Entra ID (Setting up and managing your account).
Where to find each:
Resource |
Where |
|---|---|
API reference (all endpoints) |
|
Mechbase SDK (Python · Go · Swift · Kotlin) |
|
|
|
dr-files (read raw |
|
Analytics & BI cookbook |
Note: Exact integration options, endpoints, and credentials depend on your deployment. For the AIMMS connector, a DMS import, or a custom integration beyond the documented API, contact Arpedon.