MX · MX+ · MX:Spatialv8.4 · enterprise build

Enterprise operations
software for complex work,
assets, people, places,
and field teams.

MX is a configurable operations platform that connects work management, asset management, mobile field operations, spatial intelligence, forms, reporting, and secure AI automation — across the office and the field.

↳ Built for the operations that cannot wait.
mx.console / live operations
⌘K Search14 active
Active work
247
+12
Field teams
18
online
Assets
4,812
tracked
AI actions
36
today
WORK ORDERS · liveupd 000s
WO-48217
Substation 14 — breaker inspection
Crew B · Grid 14·E
in-progress
WO-48211
Pole replacement — Sector 7
Crew D · Sector 7
dispatched
WO-48205
Camp 3 generator service
Crew A · Camp 3
complete
WO-48198
Damage assessment — Route 22
FT-12 · Rt 22
in-progress
WO-48184
NFC wristband re-issue (basecamp)
Ops · Camp 1
queued
COMPLETIONS · 24h
00:00now
AI · ASSISTANT
Summary drafted — 3 incidents on Route 22 reference the same downed asset (POLE-09812). Suggest grouping under one recovery order?
Group ordersDismiss
sync · live · all teamsregion: ANZ · tenant: enterprise-prod
§ 01 · The problem MX solves

One operational platform for the work your core systems do not handle well.

ERPs track money. EAMs hold the asset register. GIS shows the map. MX is what connects them to the people, work, and field execution they all depend on.

ERP · FinanceEAM · MaximoGIS · EsriEOC · Incident MgmtField crews · MX+Inspections · FormsSpatial · Routes · ZonesAI agents · MCP toolsMXOPERATIONS CORE
Work ordersAssetsPeopleLocationsFormsInspectionsDocumentsDashboardsMobile teamsAI agentsExternal enterprise systems
§ 02 · Core capabilities

Twelve capabilities. One configurable platform.

MX is not twelve products bolted together. Each capability shares the same data model, permissions, audit trail, and field execution layer — configured to your operation, not forked from it.

C01

Work Management

Requests, dispatch, prioritisation, field updates, completion, and audit — from intake to close-out.

Work ordersDispatchEscalations
C02

Asset Management

Asset register, hierarchy, inspections, condition, meter readings — maintenance that raises its own work.

RegisterMetersQR / NFC
C03

Field Service Management

Coordinate crews and individual technicians, dispatch by skill or location, capture evidence in the field.

DispatchCrewsEvidence
C04

Mobile Workforce

Mobile assignments, status updates, location, and supervisor visibility across distributed teams.

AssignmentsStatusLocation
C05

MX+ Mobile App

Field-first mobile app. Continues working when connectivity is poor — syncs when the connection returns.

OfflineScanningPhotos
C06

MX:Spatial

Operational mapping, location-aware work, geometry editing — turning messy enterprise data into usable spatial intelligence.

MapsZonesRouting
C07

Forms & Inspections

Configurable forms with conditional logic. Linked to assets, work, locations, and reporting — not stranded data.

ConfigurableLinkedMobile
C08

Dashboards & Reporting

Live dashboards, SITREP-style reporting, exceptions, and management views. Turn field activity into intelligence.

LiveSITREPExport
C09

AI & Automation

Operational AI assistant, document RAG, MCP-enabled tools, event-driven automation — within the platform’s permission model.

AssistantRAGMCP
NewC10

Finance Module

Project-scoped, rules-driven. Turns scans, completions, mileage, and activity into auditable cost lines, projected to project end.

RulesAuditProjections
C11

Enterprise Integration

APIs, ERP/GIS/EAM/HR/finance connectors, data warehouse feeds, and customer-specific system integration.

APIsERPGIS
NewC12

Team Communications

The engagement layer — direct messages, multi-channel notifications, and a targeted message board. Audience-filtered by company, role, location, status — with read receipts and audit.

Direct messagesNotificationsMessage board
§ 03 · Built for the field

Designed for the field — not just the office.

MX runs where conditions are messy: connectivity drops, data is inconsistent, teams are distributed, sites change daily, and decisions cannot wait for the next sync. That's where most enterprise software quietly fails.

ENV·01< 4 hrs to deploy

Disaster response

Cyclone, flood, fire — rapid deployment, field reporting, recovery work orders.

ENV·0224/7 field tracking

Power & utilities

Substations, lines, restoration crews, inspections, damage assessment.

ENV·03Zero paper forms

Basecamps & temporary sites

Intake, NFC wristbands, beds, meals, laundry, issue QR codes.

ENV·04Spatial-first

Infrastructure

Roads, water, civil — inspections, contractor management, condition reporting.

ENV·05Offline-capable

Logistics & field ops

Routes, manifests, evidence, escalations — over patchy connectivity.

ENV·06ERP-integrated

Enterprise maintenance

EAM-connected maintenance, work history, condition, lifecycle.

§ 04 · MX+ mobile app

Keep field teams working, even when connectivity is poor.

MX+ is the field app for MX. Access work, complete inspections, capture evidence, scan tags and wristbands, and keep working offline. Sync resumes when a connection returns — with no data loss and a complete operational record.

Works offline

Continues capturing work, forms, photos, and updates when the network is gone.

Scans everything

QR, barcode, NFC tags. Wristbands and badges for basecamp ops.

Built for evidence

Photos, notes, signatures, geotag — all linked back to the work and asset.

Crew-aware

Assignment to individuals or crews. Supervisor visibility on the same record.

OFFLINE-FIRST

MX+ is designed for environments where connectivity cannot be guaranteed — disaster zones, remote sites, utilities, temporary facilities, basecamps. Field teams continue capturing work, forms, inspections, photos and updates, then synchronise when a connection becomes available.

MX+ Mobile app — home screen showing Greig McArthur assigned to SPN1 Typhoon Sinlaku ProceMX, with Message Board, Work Orders, Arrival/Departure, Assign Equipment, BOM Check-In/Checkout, Dashboards, and Face Recognition tiles.
§ 05 · MX:Spatial

Spatial intelligence, built into operational work.

Not just a map. MX:Spatial connects locations, assets, work, routes, zones, and site layouts to the operation around them — and turns messy enterprise data into usable spatial intelligence.

mx.spatial / region:anz-east · 10 features
Fsearch features
SECTOR · 7GRID · 14·E~ COAST ~ZONE · OPS-EASTSub 14 — breaker2 km
LAYERS
-33.872° · 151.207° · EPSG:4326
FEATURE
WO-48217Work orders

Sub 14 — breaker

Crew B · ETA 14:20

STATUS
in-progress
LINKED RECORDS
Work orders3 open
Inspections12 records
Documents5 files
ZoneOPS-EAST

Beyond points on a map

Lines, polygons, routes, service areas, site layouts, operational zones.

Make non-spatial data spatial

Clean addresses, resolve regions, enrich coordinates, generate features.

Location-aware work

Assignments and inspections aware of where they happen, and what is nearby.

Geometry editing in MX

Basic edit/draw inside the platform — no separate GIS tool required for routine work.

Explore MX:Spatial
§ 06 · Finance module · new

Turn operational activity into auditable, projected, rules-driven cost lines.

The Finance module is project-scoped, lives inside MX, and runs on a hybrid engine: a nightly sweep recalculates fixed and recurring charges while event hooks attach per-activity and per-completion charges in real time. Every line is reversible and audited.

mx / finance / project: OPS-EAST-2026
ExportDry-run sweepRun sweep
Budget
$2.40M
OPS-EAST-2026
Spent
$1.42M
59% of budget
Projected
$2.61M
109% of budget
Variance
+$0.21M
over budget
PROJECTION · TO PROJECT END
actual plan projected
LINEDATEKINDDESCRIPTIONQTYRATEAMOUNT
AUDIT TRAILCL-90420

WO-48205 · generator service

Created
Event hook · scan-completed · 14 May 14:08:22
Rule matched
R-WO-GEN-A · 14 May 14:08:22
Posted
Nightly sweep · 14 May 23:05:00

Generated, not entered

Cost lines are created automatically from the activity already captured in MX — scans, completions, mileage, manual entries.

Rules, not code

Administrators define billing rules with a predicate builder. Change billing behaviour without a release.

Projected to project-end

Issues surface before they hit the budget. The dashboard shows spend to date, budget vs actual, and projection to end of project.

Built for control

Voids, reversals, dry-run sweeps, on-demand sweeps, manual lines. Full audit trail per line, Excel and JSON export.

FOR THREE AUDIENCES

Project administrators configure rules and investigate discrepancies. Operations managers open the Project Financials dashboard for spend, budget, and projection. End users see, on their own user record, the costs they have personally generated on a project.

Request a Finance brief

↳ Lives inside MX. Uses existing project, item, scan, work and activity records. No separate data entry. No separate login.

§ 07 · AI & automation

AI that works inside your operational platform — with context, permissions, and control.

We're all-in on AI, but not reckless with it. AI extends MX through chat, document intelligence, MCP-enabled tools, and event-driven automation — always within the platform's permission, security, and audit model. It does not bypass governance. Ever.

mx.assistant · role: ops-supervisor
Permissions enforced
OPS-SUPERVISOR
Summarise the last 24 hours of work for Sector 7 and flag anything blocked.
Ask anything about your operation…⌘ ↵
GOVERNANCE · ENFORCED

Six controls every AI action passes through.

01
Role-based permissions
AI can only invoke functions the user already has access to.
02
Human oversight
Critical actions require explicit confirmation. Nothing posts silently.
03
Auditability
Every prompt, tool call, and resolved answer is logged with a reference ID.
04
Guardrails
Tool parameters, scopes, and rate limits configured per role and per agent.
05
Grounded answers
Document RAG only retrieves from approved corpora. Hallucinated sources rejected.
06
No platform bypass
AI does not see, write, or call anything outside the platform's access model.

Operational assistant

Ask questions, search operational knowledge, summarise activity, interact with approved MX functionality.

Document AI / RAG

SOPs, manuals, asset documents and procedures — queried through controlled retrieval, grounded in approved content.

MCP architecture

Controlled AI access to internal and external capabilities, preserving governance and role-based access control.

Event-driven agents

Triage incidents, group related work, summarise SITREPs, notify teams, prepare reports — within guardrails.

§ 08 · Enterprise integration

Fits into your enterprise architecture.

MX often sits between enterprise systems and the operational frontline, turning fragmented data into usable workflows for the people who need to act.

ERPOracle · SAP · NetSuiteEAMMaximo · IFSGISEsri ArcGIS · QGISIdentity / SSOOkta · Entra · Azure ADEmergency managementEOC Platform · Incident MgmtHR & workforceWorkday · SAP HRData warehouseSnowflake · BigQueryCustomer-specificLegacy / point systemsMXOPERATIONS PLATFORMAPIs · EVENTS · MCP · SSO

Enterprise APIs

REST, webhooks, and event streams. Versioned, documented, and access-controlled.

Identity & SSO

SAML, OIDC, SCIM. Role mapping from your enterprise identity provider.

Data warehouse

Operational data feeds for analytics, BI, and downstream reporting.

Custom systems

Customer-specific legacy systems supported through point integrations.

§ 09 · Security & compliance

Enterprise control for operational software, mobile teams, and AI-enabled workflows.

ProceMX is designed with enterprise security, access control, auditability, and compliance-aware deployment in mind. We take security review seriously — and we don't claim certifications we don't hold.

01 · ACCESS CONTROL

Access control

Role-based permissions across data, work, fields, and AI actions. No "admin can see everything" default.

02 · AUDIT TRAILS

Audit trails

Every record change, every AI tool call, every field action carries who, what, where, when, and why.

03 · HOSTING

Hosting

Secure hosting patterns. Tenant isolation. Region-aligned deployment for data residency requirements.

04 · AI BOUNDARIES

AI boundaries

AI operates strictly within the platform's permission model. No bypass paths. Approved corpora only.

05 · IDENTITY

Identity

Enterprise identity options — SAML, OIDC, SCIM provisioning, role mapping from your IdP.

06 · COMPLIANCE-AWARE

Compliance-aware

Designed for enterprise security review. We support customer-specific requirements; we do not over-claim.

STRAIGHT TALK

We do not claim SOC 2, ISO 27001, HIPAA, or CMMC certification by default. We describe MX as compliance-aware and designed for enterprise security review. For customers with specific certification or framework requirements, we work through them as part of the engagement — and document what we deliver.

Talk to ProceMX

Ready to connect your operational work,
assets, people, and field teams?

Tell us about your operation — your work types, your field teams, your spatial environment, your existing systems. We'll show you what MX would look like for you, with no abstract demos.

Book a demo Request a solution brief

Discuss your operation

For operations leaders.

Open

Explore MX for emergency ops

For response and recovery teams.

Open

Talk to ProceMX about your stack

For enterprise IT, CIO, CTO, security.

Open

Subcontractor / partner fit

For prime contractors and programme managers.

Open