IBM Maximo Application Suite 9.2 Alerts: The Missing Layer Between Operational Events and Maintenance

Every industrial organization generates alerts.

A SCADA system detects a pressure deviation. An IoT sensor reports increasing vibration. A drone identifies corrosion on a storage tank. An inspection robot discovers a thermal anomaly. An AI vision system detects an oil leak.

The technology to generate alerts has been around for years.

The real challenge has always been deciding what to do next.

With IBM Maximo Application Suite 9.2, IBM introduces the new Alerts application. At first glance it may seem like another application in the suite, but I believe it represents something much more significant: a missing decision layer between Operational Technology (OT) and Enterprise Asset Management (IT).

But what exactly is an Alert?

It sounds like a simple question, yet the answer is surprisingly difficult.

Is an Alert an Incident?

A Service Request?

A Work Order?

In my opinion, the answer is none of the above.

An Alert is simply an observation that deserves attention.

At the moment an alert is generated, we often don't yet know whether maintenance is required. We only know that something unusual has been detected.

That distinction is important.

A Service Request assumes someone is requesting service.

An Incident assumes something has already gone wrong.

A Work Order assumes we've already decided maintenance should be performed.

An Alert makes none of those assumptions.

It represents the earliest stage in the decision-making process.

The industrial world is producing more alerts than ever

Traditionally, maintenance activities were triggered by operators making phone calls, sending emails, or creating Service Requests.

Today's industrial environments look very different.

Alerts are continuously generated by:

• IoT sensors

• SCADA systems

• PLCs

• Building Management Systems

• Historian platforms

• AI vision systems

• Inspection drones

• Autonomous robots

• Energy management systems

• Environmental monitoring solutions

The number of operational events is growing rapidly.

The challenge is no longer collecting data.

The challenge is understanding which events actually require action.

Think of Alerts as industrial triage

One comparison immediately came to mind when I started exploring the new application.

A hospital emergency department.

Every patient first goes through triage.

Not every patient is rushed into surgery.

Some require immediate intervention.

Others simply need observation.

Some can safely return home.

Maintenance should work the same way.

Every operational event deserves assessment before it automatically becomes work.

That is exactly the role I see for Alerts.

Reliability provides the missing context

An alert by itself rarely tells the complete story.

A bearing temperature of 85°C.

A vibration increase of 20%.

A drone detecting corrosion.

Without context, these are simply observations.

The real value comes from combining the alert with asset knowledge:

• Asset criticality

• Failure modes

• Maintenance strategy

• Operating conditions

• Maintenance history

• Business risk

Only then can an organization determine whether immediate action is required, whether additional inspection is needed, or whether the event should simply be monitored.

This is where reliability engineering and operational technology truly come together.

Drones and robots are becoming the new sensors

One development I find particularly exciting is the rise of autonomous inspection technologies.

When we think about sensors, we often imagine temperature probes or vibration transmitters.

But today's inspection drones and mobile robots are simply a new generation of sensors.

Instead of measuring a single value, they observe the physical condition of assets using cameras, thermal imaging, LiDAR, ultrasound, or AI-powered vision.

The output remains the same.

An observation.

An observation becomes an Alert.

And only after evaluation should it become maintenance work.

AI should help understand Alerts—not create Work Orders

Artificial Intelligence will undoubtedly play an increasingly important role in maintenance.

However, I don't believe AI should immediately create Work Orders.

Instead, AI should help us understand Alerts.

It can identify similar historical events, analyse maintenance history, evaluate asset criticality, recognise patterns, estimate risk, and recommend possible actions.

The final decision should remain based on operational context.

In that role, AI becomes a decision-support capability rather than an automation shortcut.

A stronger bridge between OT and IT

For many years, organizations have invested heavily in connecting Operational Technology with Enterprise Asset Management.

The technical integrations are largely solved.

The missing piece has often been determining how operational events should enter maintenance processes.

To me, IBM MAS Alerts fills exactly that gap.

Rather than forcing every signal to become a Service Request or a Work Order, organizations now have a dedicated place to assess, enrich, prioritise, and decide.

As industrial environments continue to evolve with IoT, SCADA, AI, drones, and autonomous robots, I believe this decision layer will become increasingly important.

For me, that is the real significance of the new Alerts application in IBM Maximo Application Suite 9.2.

It is not simply another application.

It is a smarter starting point for modern asset management.