# 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 (`/2012/`). |
| **Section** | A major area of an installation (e.g. *Utilities*). |
| **Zone** | A specific location within a section (e.g. *Pump Station*). Locations read as `Section / Zone`. Zones have their own page for documents and photos. |
| **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 [Health states](health-states.md). |
| **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. |
