Skip to content
Nexaform Technology Solutions
Perimo Asset AgentsWorks with any EAM

AI agents for any EAM system that run the maintenance loop.

Governed AI maintenance agents for IBM Maximo, Nexaform EAM and any other EAM. They watch your assets, plan the work, prepare the parts and draft every action. Your team approves. The agents learn.

The shift

Predictive maintenance alerts were only step one

Predictive analytics stops at the alert. Agentic asset operations go further: agents plan the job, parts and schedule, act in your EAM within approved limits and learn from every outcome.

Yesterday · predictive analytics
  1. 1Detects a pattern in the data
  2. 2Raises an alert
  3. 3Waits for a person to notice
  4. 4A planner builds the work order by hand
  5. 5Learning stops at the alert
Now · agentic asset operations
  1. 1Senses conditions continuously
  2. 2Reasons over history, manuals and context
  3. 3Plans the work: job plan, parts, schedule
  4. 4Acts in your EAM within approved limits
  5. 5Learns from every outcome

Alert overload

Many alerts, few of them actionable. Teams learn to ignore them.

A manual last mile

Turning an alert into a planned, resourced work order still depends on a busy planner.

Poor data in

Missing failure codes and messy history limit what any model can learn.

No learning loop

Outcomes rarely flow back to the models, so the same failures repeat.
How it works

How AI maintenance agents work: sense, understand, decide, act, learn

Predictive analytics, anomaly detection and failure forecasting are built in. They are tools the agents use, not another dashboard to watch.

  1. 01

    Sense

    Reads meters, sensors, alarms and work history around the clock.

  2. 02

    Understand

    Puts signals in context: asset history, manuals, failure modes.

  3. 03

    Decide

    Weighs risk, cost and schedule, and picks the best next action.

  4. 04

    Act

    Drafts work orders, reserves parts and books crews in your EAM.

  5. 05

    Learn

    Feeds every outcome back so the next decision is better.

The agent loop: sense, understand, decide, act, learn, then repeat.Prediction isbuilt inmodels are tools01Sense02Understand03Decide04Act05Learn
The agent team

Seven AI maintenance agents, one coordinated team

Condition agent

Runs anomaly detection on meters and sensors, filters noise and explains real anomalies.

Reliability agent

Finds bad actors (assets with repeat failures), runs root-cause analysis, forecasts failure risk and tunes preventive maintenance strategy.

Planner agent

Builds work orders with job plans, labour and timing around planned stops.

Parts agent

Checks stock, reserves kits and raises purchase requests when needed.

Technician assistant

Guides field work on mobile or by voice and captures clean failure data.

Data steward agent

Fixes failure codes, duplicates and hierarchy gaps continuously.

Orchestrator

Coordinates the agents, applies your policies, routes approvals and records every decision in the audit trail.

Coming next

Create your own Perimo agents

In the upcoming version, users can build their own agents and run them from Perimo Copilot with a command such as /dead-stock.

A day with the agents

One issue, from first signal to closed work order

  1. 02:10Condition agentBearing temperature on pump P-104 drifts outside its learned normal range.
  2. 02:12Reliability agentMatches the pattern to past seal and bearing failures and rates the risk high.
  3. 06:30Planner agentDrafts a work order with job plan and crew, slotted into Thursday’s planned stop.
  4. 06:31Parts agentConfirms the bearing kit is in stock and reserves it against the work order.
  5. 07:05Maintenance plannerReviews the evidence and approves in the EAM with one click.
  6. ThuTechnician assistantGuides the repair and records problem, cause and remedy correctly.
  7. AfterAll agentsThe outcome updates the models, and similar pumps are re-scored.

Illustrative example, synthetic data.

You stay in control

AI agent autonomy levels: you decide how much the agents do

InformLevel 0

Agents analyse and explain. No actions are proposed.

RecommendLevel 1

Agents suggest actions. People create the work themselves.

Draft for approvalLevel 2 · default

Agents prepare complete work orders and requests. A person approves each one.

Act within limitsLevel 3 · opt-in

Agents complete low-risk, reversible actions within policy, such as reserving parts.

Safety-critical assets always need human approval. Autonomy is set per action type, asset class and site, and can be withdrawn at any time.

Works with your systems

AI agents that work inside the EAM you already run

They act through each system’s own APIs, workflows and permissions, and never see or do more than the approving user is allowed to.

Asset Agents read from and act in your EAM through its own APIs, and read context from historians, documents and ERP.YOUR EAMIBM Maximo · 7.6 and MASNexaform EAMSAP and othersAsset AgentsOrchestratorConditionReliabilityPlannerPartsAssistantData stewardPolicyApprovalsAuditCONTEXT · READ-ONLYHistorians · OPC UA, MQTTManuals and drawingsERP and inventoryreadactread

Swipe sideways to see more →

Use cases

Two AI maintenance use cases, from EAM data to outcome

Both come from metro rail, where a single failure in the morning peak can hold dozens of trains.

Signalling · IBM Maximo

Stop the point failure before the morning peak

Point machine PM-23’s throw time has drifted from 3.80 s to 4.28 s. The EAM alarm is set at 5.0 s, but similar machines failed between 4.6 and 4.9 s. The agents catch the trend, draft the work order for tonight’s possession and reserve the parts. A planner approves at 07:05.

4 days
earlier than similar failures
0
trains held
45 → 8 min
planner effort
Rolling stock · Nexaform EAM

Train doors that keep coming back

Car TS-07-C2 logs four times the fleet’s door faults, and 40% of door work orders have no failure code. The agents read the messy history, find the car-level pattern and raise one investigation covering all eight doors. No new sensors were needed.

1 visit
instead of a repair a month
≈175 h
repeat labour avoided per car per year
≈14
in-service failures avoided per car per year

Illustrative example, synthetic data.

Better every week

Every job makes the AI agents more useful

  1. 01

    Capture

    The technician assistant records correct failure codes and notes at close-out.

  2. 02

    Clean

    The data steward fixes past codes, duplicates and hierarchy gaps.

  3. 03

    Learn

    Risk and condition models retrain on better data every cycle.

  4. 04

    Trust

    Higher acceptance lets you raise autonomy where it is earned.

Enterprise-grade by design

AI agent governance built for the controls your auditors expect

Your policies decide

Scope, limits, approvers, time windows and a kill switch, versioned like any controlled change.

Every action proposed first

Approvals are bound to the exact action, single-use and time-limited.

Tamper-evident audit

An append-only, hash-chained record of every decision, replayable and exportable to your SIEM.

Security from identity to data

SSO with MFA, least-privilege agent identities, encryption and private connectivity.

Grounded AI

Every number comes from your systems. When data is missing, the agent says “cannot determine”.

Deploy anywhere

Our cloud, a dedicated cloud, your cloud account or on-premises, with your choice of AI model.

How a deployment starts

Start in shadow mode: agents advise, people decide

Proof on your own data before any agent drafts real work.

  1. Weeks 1–2

    Connect

    Read-only access to your EAM and condition data, plus a data quality baseline.

  2. Weeks 3–8

    Shadow

    Agents propose actions on live work while your team works as normal.

  3. Weeks 9–10

    Review

    Acceptance, accuracy, early catches and time saved, measured in your own numbers.

  4. Week 11 onward

    Go live

    Switch on approval-based drafting for agreed sites and action types.

Where we fit

How Asset Agents compare: built for multi-EAM estates and governed autonomy

EAM-suite agentsIndustrial AI platformsPerimo Asset Agents
Works withTheir own EAMThrough integration projectsAny EAM, inside its own workflow
Starting pointLatest suite versionData-platform rolloutYour existing EAM data
Autonomy controlVendor-definedVariesYour policy per action, asset and site
Audit trailWithin the suiteVariesTamper-evident, exportable to your SIEM
Best fitSingle-vendor estatesData-heavy process plantsMulti-EAM, mid-size to large estates

Swipe sideways to see more →

Generalised comparison of product categories; individual products differ.

FAQ

Questions about AI agents for Maximo and other EAMs

Do Perimo Asset Agents include predictive analytics and anomaly detection?

Yes. Predictive analytics, anomaly detection and failure forecasting are built in. The agents use them to turn signals into planned, resourced work orders instead of another alert.

What is an AI agent for IBM Maximo?

An AI agent for Maximo is software that reads Maximo data such as meters, work history and failure codes, reasons about what should happen next, and prepares the action in Maximo itself: a drafted work order with job plan, labour and parts. With Perimo Asset Agents, a person approves each action by default.

Do the agents change our EAM without approval?

Not by default. At Level 2 every work order and request is drafted for a person to approve. Level 3, where agents complete low-risk, reversible actions on their own, is opt-in per action type and never applies to safety-critical assets.

Which EAM systems do Asset Agents work with?

IBM Maximo, including 7.6 and MAS 9.2, and Nexaform EAM. Other EAMs such as SAP connect through connectors built on each system’s own APIs and permissions.

Do we need new sensors?

No. Agents start with the work history, meters and failure codes already in your EAM. Condition data from historians adds more signal when you have it.

Which AI models do you use, and is our data used for training?

Model providers are configurable per customer: approved hosted models, models in your own cloud account, or on-premises models. Your data never trains shared models without your explicit written consent.

See the AI agents work on your own maintenance history

Bring a few months of work orders from Maximo or another EAM. We will show you what the agents would have proposed.