Axentra CMMS

A CMMS for maintenance in industry.

Axentra manages industrial maintenance: assets, planned and condition-based work, work orders, spare parts, permits and calibration. It runs in the cloud, or on your own servers with no outbound connection.

Overview

Maintenance software for industrial sites.

Axentra covers the whole maintenance cycle — the fault reported from the shop floor, the work order it becomes, the diagnosis, the parts, the safety permit, the calibration record, and the history that proves the asset was looked after.

It runs as one product in two shapes: multi-tenant cloud, or self-hosted behind your firewall with an air-gap bundle for sites that have no route out. Same code, same data model, your choice of perimeter.

5Languages: EN, FR, DE, IT, JA
ISO 14224Failure coding standard
GanttScheduling with conflict detection
OfflineTechnician app works without signal
See it work

Axentra in under a minute.

Three short clips, no slides: the paperwork it replaces, the two failures it prevents, and what an alarm looks like when the right technician already knows.

From reactive chaos to complete control

An alarm becomes a work order before anyone walks to the panel.

When a critical machine raises an alarm, every second counts. Axentra opens the work order at the machine and routes it to the technician with the right skill and the free capacity — so the response starts with the fault, not with a phone call about the fault.

Spreadsheets and paper logs

One scan opens the work order.

Paper logs mean slow repairs and costly downtime. Instead of a fault written on a clipboard and retyped at the end of the shift, a technician scans the asset and the work order opens against it — with its history, its parts and its checklist already attached.

Two maintenance nightmares

The spare part, and the audit trail.

The part nobody can find, and the evidence nobody can produce. Axentra answers both from the same record: digital sign-off on every intervention, live stock levels behind the parts consumed, and full traceability from the fault code to the closed work order.

Capabilities

What it covers

All of it shares one asset hierarchy and one history.

01

Asset & meter hierarchy

Deep asset registers with hierarchical locations, spare-parts bills of materials, and meters attached to the asset they belong to.

  • Locations
  • Spare-parts BOM
  • Counters
  • Gauges
02

Condition-based & preventive

Scheduling driven by calendar intervals, runtime counters, cycle thresholds, or live condition triggers — with hysteresis re-arming so a reading hovering at the limit does not spam work orders.

  • Calendar
  • Runtime
  • Condition
  • Hysteresis
03

Work order & defect lifecycle

Standardised failure coding to ISO 14224, structured root-cause analysis, checklists, labour time tracking and inventory reservation on the same work order.

  • ISO 14224
  • 5 Whys
  • Fishbone
  • Fault tree
  • 8D
04

Safety & industrial compliance

Permit-to-work for hot work, confined space and working at heights; lockout/tagout isolation flows; calibration and metrology management.

  • Permit to work
  • LOTO
  • Calibration
  • Inspections
05

ERP & plant telemetry hub

Two-way connectors for enterprise ERPs, plus an automated intake pipeline for IoT gateways, controllers and shop-floor middleware.

  • Enterprise ERPs
  • PLC / SCADA
  • IoT gateways
  • Two-way sync
  • REST / JSON
Energy telemetry

How Axentra reads energy meters — through the middleware layer.

Four tiers, from a meter's register to a work order. Axentra never talks to a meter directly: the middleware layer owns the field bus, and Axentra owns the decision.

01Physical instrumentation

Energy meter

A power meter on the feeder measures active and reactive energy, real power, voltage, current per phase, power factor and run-hours.

  • kWh / MWh
  • kvarh
  • kW
  • V · A · PF
  • Run-hours
Modbus RTU (RS-485) · Modbus TCP (Ethernet, port 502)
02Field bus

Serial or Ethernet link

The meter answers over a two-wire RS-485 chain or over plant Ethernet on Modbus TCP. Measurements arrive as counters and gauges, which the middleware layer decodes into engineering units.

  • RS-485
  • Modbus TCP
  • Counters
  • Gauges
Polled by the middleware layer on an edge computer or gateway
03Middleware layer

Polling, decoding, buffering

The middleware layer polls the configured meters on a fixed cadence, decodes their registers, applies the transformation ratios and maps raw addresses to named parameters. Readings buffer locally if the link upstream drops.

  • Polling engine
  • Register decode
  • Scaling
  • Edge buffering
HTTPS POST · x-telemetry-token
04Axentra CMMS

REST ingest and CBM engine

Axentra validates the source token, matches each reading against a registered meter on that asset, then applies it: counter deltas and rollover checks for accumulators, warn bands for gauges.

  • Token auth
  • Meter matching
  • Counter deltas
  • Warn bands
Meter compatibility

Energy meters, read through the middleware layer.

We do not resell meters and we are not tied to one brand. The middleware layer polls the meter, decodes its registers and hands engineering-unit values to Axentra — so which meter is on the feeder is an electrical decision, not a software one.

Modbus RTU

Serial RS-485 daisy chains, polled by the middleware layer at a configured cadence.

Modbus TCP

Meters on the plant Ethernet, addressed on port 502.

Engineering units

Counter and float registers decoded, with transformation ratios applied.

Meters already installed? If they expose a Modbus interface, they are probably readable today. Send us the make and model and we will confirm before anyone commits to a project.

The ingest contract

One endpoint, one token, one payload.

The middleware layer posts readings to a single public ingest route. Axentra provisions a dedicated source for each gateway and stores only a hash of its bearer token, so a leaked database does not hand anyone a way in.

  • Between 1 and 500 readings per request
  • Each reading names an asset code and a meter name
  • 401 unknown token · 400 malformed body · 422 rejected readings
  • Nothing is applied unless the meter is registered on that asset

A reading that fails validation is rejected, not silently coerced — so a wrong register map shows up as an error rather than a plausible-looking number in your history.

POST · middleware layer → Axentra
POST /api/public/v1/telemetry/readings
Host: cmms.yourplant.com
x-telemetry-token: <source token>
Content-Type: application/json

{
  "readings": [
    {
      "asset_code": "SUB-MAIN-01",
      "meter": "Active Energy",
      "value": 184520.4,
      "note": "substation main feeder"
    },
    {
      "asset_code": "COMP-01",
      "meter": "Operating Hours",
      "value": 4215.8,
      "note": "Auxiliary run-hour register"
    }
  ]
}
accepted · readings applied to the asset record
After ingest

What the reading sets in motion.

Storing a number is not the point. These four behaviours turn a telemetry feed into maintenance that happens on time.

01

Usage-based preventive work

When accumulated energy or run-hours cross a configured threshold — a transformer inspection at 500 MWh, a motor overhaul at 5,000 h — the preventive plan generates and schedules the work order itself.

02

Threshold alarms

An abnormal instantaneous load or a phase imbalance outside the configured band dispatches an alert to the maintenance supervisors and planners responsible for that asset.

03

Hysteresis re-arming

A work order raised at high demand does not repeat while the reading oscillates. The condition must fall back below the reset band before the trigger arms again.

04

Usage-rate forecasting

Average daily energy and runtime over a rolling 30-day window forecast the actual date the next service is due, instead of a date guessed at plan creation.

Bring us a meter and a threshold.

We will show you the reading, the counter change, and the work order it raises, on your own asset structure.