A configurable enterprise operations platform for complex, field-driven work.

Make assets operational, not just inventoried.

Assets that ask for their own maintenance — recurring by calendar or usage meter, raising the work order automatically when a service falls due. Asset register, hierarchy, condition, maintenance history, inspections, photos, documents. Linked to the work, locations, and crews that act on them. Supports GPS, RFID, barcoding, NFC. Assets can be held within other assets, so contents are known by place. Warehouse and inventory: stock is recorded where it is held, including inside another asset, and moves with it. Labelling at scale: asset codes download as a spreadsheet of up to 2,000 assets, each with a shareable code image, ready to hand to a print supplier — and itemised stock is created in bulk with sequential asset numbers. And the register is checked against the yard: import the list you have, send someone round with a phone, and MX shows what has not been seen since a date you choose, what was scanned that the list never mentioned, and which trackers disagree with the scan or have stopped reporting — each line retired, relocated or created on the spot.

Model real-world workflows with control and flex.

Templated standard work for consistency, ad-hoc tasks for the unexpected. A scheduling board lays out each person's day with the drive time between jobs, and warns when a turnaround is tight or cannot be made. Rounds that repeat — inspections, deliveries, generator checks — dispatch themselves on the pattern the work follows and close when the round is done. A job's steps can be required in order, and a step's form started only at that step's location — set to warn or enforce, with every exception recorded and visible to the office. Auto-allocation runs on rules your own team writes on the template — by position, company, team, resource group or whoever looks after the asset — applied only when the work matches your conditions, and tested against recent work before it goes live.

A skilled, credentialed, accountable workforce.

Credentials, certifications, training records, access control (physical and digital), time, internal and contractor personnel. Credential records are reviewable and correctable: workers upload and renew their own from the app, a rejected upload carries the reviewer's reason, and an approval can be taken back — the credential stops counting as held, including on the report that goes to your customer. Courses are built and delivered in MX, each learner's progress is tracked, and a course can complete when its form is submitted. What a new starter receives is set up before day one, down to a badge printed before they arrive. Where people are staying — hotel, rented housing or camp bed — on one page, with every move dated and the people nobody has booked anywhere counted separately. Compliant, safe, secure operations.

Spatial reasoning, not just a basemap.

Locations, zones, routes, polygons, service areas, site layouts. Generated features. Site boundaries walked in the field. Asset positions and location history from third-party telematics. Real-time crew tracking.

Battle-tested, offline-first field execution.

MX+ mobile, OTA configuration updates, offline work, forms, scanning, photos, geotag. Tested across some of the world's largest disaster responses.

From the tasks

Start from the tasks being shipped. The bill of lading is built from them, with nothing retyped.

To the driver

Assign a driver and they hold the paperwork. No driver known yet? Assign the load to the hauler instead.

Ahead of arrival

When the vehicle is within a set distance or time of its destination, an arrival alert goes out before it pulls in.

Signed, not printed

The driver and the receiver sign on the driver's phone at each stop — no account needed, so a hauler's own driver can use it. The signatures go into the bill of lading, timed when they were really signed, coverage or not.

Shared outside

Send the load's tracking link to the client or receiving site. They follow it without an account.

Bill of lading per load

Every movement — debris out, equipment between sites, plant home at demob — is a load with a bill of lading: what, how much, from where, to where, and by whom. A load can be prepared before the driver is known, or recorded after the move, and issued when it is ready.

Hauler assignment

Loads are assigned to haulage vendors and their vehicles. The vendor works within its own scope, the same way a subcontractor does on a multi-employer site.

The haulers, not just the loads

Carriers and brokers are companies in MX — contacts, dispatch email, their own people — imported from the list you keep today. Insurance certificates and tax forms sit against the company with an expiry date, and MX warns you by email before cover lapses, rather than leaving it to a diary note. When a load is raised, the pickers offer the carriers you work with and leave out the ones you have retired.

Tracked while it moves

Pickup, transit, and delivery are recorded against the load, with the weight ticket or delivery evidence attached at the point it exists.

Reconciled into purchase orders

At day end the loads are reconciled against the purchase order they draw on. A load that does not match is held with its reason, not lost in the total.

The loads that need chasing, listed

A needs-attention view flags the transports that are overdue, the ones nobody has picked up, anything booked on two jobs at once, and loads recorded as delivered somewhere other than their destination. Each flag links to its job, and how long each check waits before it complains is set per program.

Cold chain, in the same place as the load

A refrigerated trailer shows its supply, return and ambient air temperature against the set point it is holding, with a chart of how it has behaved over the last day, week or month. On the map every reefer is colored by what it is actually doing — holding, drifting out of range, switched off, or no longer reporting at all. The silent one is the one that costs you a load. And a trailer drifting out of range does not wait to be noticed — the reading raises a work request against that unit, at its location, in front of whoever covers it. So does a tracker that has stopped reporting altogether.