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.