MX Platformenterprise build

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

MX is the central platform where operational data, workflows, assets, people, locations, forms, inspections, mobile field activity, reporting, and AI-enabled automation come together. Configurable enough to support different operational models — governed enough for the enterprise.

↳ Built for the operations that cannot wait.

mx.platform / architecture
01 · INTERFACE4 components
MX webMX+ mobileDashboardsAI chat
02 · CAPABILITIES10 components
WorkAssetsInventoryWorkforceSpatialLogisticsFormsReportingQuotingFinance
03 · PLATFORM6 components
Data modelWorkflowPermissionsAuditEventsAI / MCP
04 · INTEGRATION7 components
APIsWebhooksSSOERPGISEAMData warehouse
§ 01 · The 5 building blocks of MX

Five disciplines. One platform.

MX is built around five operational disciplines that share a common data model, permission system, audit trail, and field execution layer. They reinforce each other — that is the point.

01

Asset

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. Each rule can be described in plain words or started from a named regime such as the UK MOT or LOLER. Register, hierarchy, condition, maintenance history, inspections, photos and documents, linked to the work, locations and crews that act on them. Start from a catalogue of ready-made blueprints, or describe your equipment or attach its manuals and MX drafts them; nothing is created until someone saves it. Supports GPS, RFID, barcoding and NFC. Assets can be held within other assets, and warehouse stock is recorded where it is held and moves with it. Asset codes download in bulk, ready for a print supplier. And the register is checked against the yard: send someone round with a phone, and MX shows what has not been seen, what the list never mentioned, and which trackers disagree with the scan.

RegisterTemplatesAI-drafted templatesYard reconciliationBulk labellingHierarchyContainersConditionCondition alertsMaintenanceInspectionsDocuments
02

Work

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 dispatch themselves. A job's steps can be required in order, and a step's form started only at its location, with every exception recorded. Auto-allocation runs on rules your own team writes, tested against recent work before it goes live. And the whole project, not just the day: every work request can be laid out as one plan, so move a job, stretch it or set it to follow another, and the knock-on from one late delivery is visible. The same screen switches to the allocation board for that project.

TemplatesDispatchStep orderOn-site startProject planScheduling boardAppointmentsRecurring dispatchEscalationsReactive tasksAuto-allocation
03

Workforce

A skilled, credentialed, accountable workforce.

Credentials, certifications, training records, access control (physical and digital), time, internal and contractor personnel. Workers upload and renew their own credentials from the app, a rejected upload carries the reviewer's reason, and an approval can be taken back. Courses are built and delivered in MX, with each learner's progress tracked. What a new starter receives is set up before day one. Where people are staying — hotel, rented housing or camp bed — is on one page, and a hotel carries its own register of floors, rooms and beds, so a room can be handed to a company to fill. People run a clock against what they are on, and supervisors see who is on what live, on a board that also runs as a wall display, and plan each person's week ahead. Every start, pause, stop and correction is kept, so time reports by activity, person, job, asset and cost category. Compliant, safe, secure operations.

CredentialsTrainingOnboardingAccessTimeContractorsSafetyAccommodation
04

Spatial

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.

ZonesRoutesPolygonsField navigationReal-time
05

Mobile

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.

OfflineOTAScanningPhotosForms

↳ Supported by Business Intelligence (BI) and Artificial Intelligence (AI) layers, hooking into data from each block.

§ 02 · Configurable data model

Your operation. Your objects. Your workflow.

MX is not a fixed schema with a few custom fields tacked on. The data model is configurable — object types, fields, relationships, statuses, workflows — and configuration is governed, versioned, and reversible.

CONFIG · WORK ORDER TYPEv3 · published
type "damage-assessment" {  fields {    severity:      enum ["low", "med", "high"]    photo_required: true    linked_asset:    ref(asset)    location:        geometry(point)    narrative:       text  }  workflow {    created → triaged → dispatched → in_progress → completed    escalate_after: 4h if severity == "high"  }  permissions {    create:   role("field-supervisor")    complete: role("crew-lead") && location.in(zone)  }}

Object types

Work orders, assets, locations, forms, inspections, crews, equipment, sites — and anything else your operation needs to model.

Fields, refs, geometry

Typed fields. Relationships across objects. Geometry attributes (point / line / polygon) on anything that has a location.

Workflow states

State machines per object type. Transitions gated by role, condition, location, or time. Escalations built in.

Asset blueprints

MX ships a catalogue of ready-made asset blueprints — generators, sleeper trailers, light towers, shower units — that you copy into your own set and adjust. Each blueprint carries its own extra fields, so what matters about your kit is recorded in the same place on every unit.

Versioned & audited

Every config change is versioned, peer-reviewable, and reversible. No live tinkering against production data.

↳ Configurable, not lightweight. MX retains the data integrity and control of an enterprise platform. Your own team configures it: scheduled jobs, settings, and AI-drafted asset templates, forms and dashboards are all self-service.

§ 03 · Role-based permissions

Everything an action touches is governed.

No default of 'admin can see everything'. Permissions apply to reads, writes, workflow transitions, AI tool calls, and configuration changes — across data, work, fields, and integrations.

ACTION ↓   ROLE →
Field crew
Crew lead
Field supervisor
Ops manager
Admin
AI agent
Read assigned work
●
●
●
●
●
●
Update work status
●
●
●
●
●
●
Complete work
·
●
●
●
●
◐
Approve / void cost lines
·
·
·
●
●
·
Edit configuration
·
·
·
·
●
·
Run AI tool calls
◐
●
●
●
●
●
Bypass workflow
·
·
·
·
·
·
● granted◐ conditional (location, scope, or rule)· denied

↳ AI agents are subject to the same permission model as users. There is no AI bypass.

§ 04 · Operational record

Who did what, where, when, and why.

Every action — by user, by mobile crew, by integration, by AI agent — is recorded with context. The audit trail is not a separate log; it is how MX remembers.

WO-48217 · breaker inspection · Sub 14complete
08:14
systemWork order WO-48217 created from incident report INC-9821
08:18
k.morganTriaged · severity=high · zone=Grid 14·E
08:20
systemAuto-dispatched to Crew B (nearest with credential E-HV)
08:34
crew-bAcknowledged · ETA 14 min · MX+ mobile · offline-capable
08:51
j.singhOn-site · photo captured · location confirmed
09:22
ai-agentSuggested grouping with WO-48218 (same pole) · permission requested
09:23
k.morganAI suggestion approved · work orders merged
10:48
j.singhCompleted · 3 photos · narrative · cost line CL-90420 generated
§ 05 · Logistics & haulage

Every load accounted for, out as well as in.

Debris haul, equipment moves and demobilization are where recovery budgets leak. In MX each load is a record — bill of lading, hauler, tracked movement — reconciled into its purchase order at day end. Raising one is a guided flow, not an afternoon of paperwork.

mx.logistics / day-end · Rt 22 debris program · PO-44715 loads · 4 reconciled · 1 held
BILL OF LADINGHAULERFROM → TOLOADSTATUS
BOL-30417V-22 · truck 3Rt 22 staging → Landfill N18.2 t debris
delivered
BOL-30418V-22 · truck 1Rt 22 staging → Landfill N17.6 t debris
delivered
BOL-30421V-07 · lowboyBasecamp A → Depot 31 × excavator
delivered
BOL-30422V-07 · flatbedBasecamp A → Depot 32 × light tower
in transit
BOL-30425V-22 · truck 2Sector 7 → Landfill N19.4 t debris
held
weight ticket missing
PO-4471 · debris haulage · V-22  ·  55.2 t reconciled today  ·  19.4 t heldaudit trail per load · weight tickets attached
RAISING A LOAD
01

From the tasks

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

02

Stops in the right order

A run with several stops is put into the fastest driving order in one click — the first stop stays where you put it, and every pickup stays ahead of its own delivery.

03

To the driver

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

04

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.

05

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.

06

Shared outside

Send the load's tracking link to the client or receiving site. They follow it without an account: the whole run, not one leg — each stop and the time it is expected, updating as the truck moves.

  • 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. And they can look it up themselves. A carrier or broker sees every load issued to it in the contractor portal — status, paperwork, signed proof of delivery and the live tracking link — instead of phoning your office. They see only their own loads, and never your rates.

  • 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. When the load is on somebody else's truck, the tracker on the trailer or generator itself shows where it is — on the tracking link and the dashboards — and the delivery completes once the unit has settled at its destination. Driving past doesn't count.

  • 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.

  • What's coming to you, on the wall

    A site manager sees every load heading to their site: the carrier, what is on board, where it is now and when it should arrive, with what has arrived and what is leaving. A Delivery Board puts the same list full screen on the site-office wall and keeps itself current. Head office sees every site at once.

  • 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.

See it in recovery, where demobilization is the endgame →
§ More platform capabilities

The rest of the platform, in brief.

The same data model and permissions underlie everything else MX offers — so each capability stays connected to the operation around it.

§ 06 · Forms & inspections

The form is the record, the document, and the proof.

Configurable forms with conditional logic, linked to assets, work, locations, and reporting. Produces a PDF matching your own paperwork layout — boxed and shaded sections, checked option lists, repeatable tables, full-page photos, custom headers and footers. Captures mapped geography, can require a video be watched in full before the rest of the form opens — a file you upload, or the training video you already host — and closes with a signed agreement. Upload the document the form came from and MX drafts the printable output alongside the form, so what comes out of the printer mirrors what went in. And a completed form keeps the layout it was filled in under, however often the template changes afterwards — a form signed two years ago still prints as it was signed. Written in your language, read in theirs: set up a form or a notification in the language you work in, and Translate with AI fills in English and every other supported language in one go, asking before it replaces anything already written. Each person sees it in the language they chose.

PDF outputMapped geographyVideo gateSigned agreementTranslate with AIOffline
Have a form's documents sent on a schedule →
§ 07 · Multi-employer sites

Contractor companies run their own crews.

Every company on the platform works within its own scope. A subcontractor's manager runs their own people, training records and fleet from the contractor portal and, on a site, fills the block of beds allocated to them — seeing only what belongs to their company. The operator sees the whole picture.

Contractor portalPeopleTrainingFleetBedsLoads
See it on a basecamp →
§ 08 · Spatial in the platform

Not a separate GIS tool.

Operational mapping, location-aware work, field-captured site boundaries, generated features. Real-time crew and asset tracking, with location history. Spatial reasoning, not just display. And a map each team can look after itself: each user group starts with the layers it needs, so a new crew member opens the map on their operation rather than an empty basemap. People who publish their own layers can share them with their own teams. The layer library shows which layers you already have and warns when one would show no data. Styling is driven by the data — an icon per team, a line color per status — and layers can be drafted, changed and published from a plain-language request.

ZonesRoutesLive trackingSite boundariesLayers per teamData-driven styling
Who maintains your map →
§ 09 · Reporting & dashboards

The people who need a view build it themselves.

Dashboards are built in minutes by the person who needs the view, over data they are already allowed to see and nothing more, then owned and shared. Describe one in plain English and MX drafts it, every widget checked against live data; or start from a gallery of ready-made widgets, previewed on your own data, to use as they are or adjust. The builder explains each option as you go, including when a chart would mislead.

Sources include the project roster, bills of lading, work allocations and asset assignments, each described in plain words, and the time between any two dates — how long loads sit before dispatch, how long work waits to be picked up. Complete, pending and overdue can read green, amber and red without a legend, and times show in the viewer's time zone, the project's or a fixed one. Alongside it: live operational views, SITREP-style reports, exceptions, executive roll-ups, exports and BI hooks for analytics and warehousing.

For the report that has to leave the building, describe the job in a sentence — what to collect, how often, who gets it — and MX emails a form's new submissions on that schedule, as a zip of the documents or one merged PDF. Set up by the team that needs it, not raised as a request.

Dashboard builderWidget galleryOwned & sharedPlain-English draftLiveTime zonesSITREPExceptionsExportScheduled delivery
How AI drafts a dashboard →
§ 10 · Quoting & the quote pipeline

The priced proposal, before the work exists.

A quote starts with the questions that decide what a job costs — permits, ground, power, climate control, catering — chosen for each type of work. Sales answer what they can and put the rest to operations on the same quote, and a quote can't move on while a required answer is missing.

Sales build the quote, operations review it before the company commits, and every save is a numbered version showing who changed what. A quote cannot be sent until it is approved, and changing an approved quote sends it back round.

The pipeline view shows every open quote, its value, the stage it is in, how long it has sat there and which team it is waiting on — with won and lost counts, the reasons for the losses, and the operation's own workload beside it, so the mobilization date you promise is one you can meet.

Request checklistVersioned quotesOperations reviewApproval before sendPipelineWon & lostWorkload
§ 11 · Finance

Every charge explains itself.

Project-scoped and rules-driven: the activity already captured in MX — scans, completions, mileage — becomes auditable cost lines. Open a person or an asset and see why it is charged as it is; what is not being charged at all is listed too, rather than quietly missed. A new project's charging is set up by its own administrators, with no release needed. And subcontracted work bills the way it actually happens: the same day's work is charged to the client and costed from the supplier, side by side.

Project-scopedRules-drivenExplains each chargeMissing RulesClient & supplier
Finance overview →
§ 12 · APIs & integration

Fits your enterprise architecture.

REST APIs, webhooks, event streams. Versioned and access-controlled. ERP, GIS, EAM, HR, finance, data warehouse, and customer-specific systems.

RESTWebhooksEventsSSO
Integration overview →
§ 13 · AI services

Within the platform's permission model.

Operational assistant, document RAG, MCP-enabled tools, event-driven agents. Governed, audited, role-aware. AI extends MX — it does not bypass it.

AssistantRAGMCPGovernance
Explore AI & Automation →
§ 14 · Planning & dispatch

From the single job to the whole project.

Every work request on a project can be laid out as one plan next to the list: move a job to a new date, stretch it to a longer duration, or set it to follow another job, and the knock-on from one late delivery is visible rather than recalculated by hand. The same screen switches to the allocation board for the project in front of you, so handing work out does not mean starting again somewhere else.

On the allocation board, work nobody has taken sits in its own column on the left, oldest first and showing how long it has waited. Each person and crew has a column; drag a job across to assign it. The picker suggests who is in today with the least on, and each column shows what that person has finished today. 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.

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.

Project planAllocation boardUnassigned queueRecurring dispatchStep orderAuto-allocation
§ 15 · Time

Time, where the work is.

People say what they are on and run a clock against it — a job dispatched to them, a task their supervisor planned, or something they describe themselves. Supervisors see who is on what live, on a board that also runs full screen as a wall display, and plan each person's week ahead; the plan then arrives on that person's own list, grouped into today, overdue and later, on the desktop and on the phone. Every start, pause, stop and correction is kept, so time reports by activity, person, job, asset and cost category. And the clock nobody stopped is caught: a task running past its expected time reminds whoever is running it, or their crew lead, supervisors see who is over time with the most overdue first, and a forgotten clock stops itself at the project's limit and waits to be confirmed or corrected. Give a job a labor plan and operations hear the same day when crew hours pass it.

ClockLive boardWall displayWeek planningOverrun alertsTime reports
§ 16 · Credentials & training

Credentials, training and onboarding.

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.

CredentialsCoursesOnboardingBadges
Explore the platform

One platform.
Configured to your operation.

Walk us through the work you manage today. We will map MX to it — what it looks like configured, what it integrates with, and what it changes.

See MX in action ↗Request the MX Platform Overview