Assetize
MADD 2.0 Maximo Autonomous Deep Diagnosis

Evidence in. Root cause out.

Diagnose what broke — and watch what might break next.

MADD correlates tickets, logs, traces, Maximo configuration, runtime signals, recent changes and version-breaking changes. The pilot never executes corrective actions.

Observer online7 streams · 34 probes · upgrade watch active

Intake

Start from the evidence you already have

Local simulation

Investigation

Waiting for incident

NEW
Select a scenario and run the investigation.
MAS SuiteManageOpenShiftDB2Liberty/JVMMIFCron/ReportsUpgrade feed
Exception rate2/daybaseline
Integration backlog142stable
Manage restarts024h
DB2 lock waits3baseline
JVM GC p9542msbaseline
Anomaly score0.08normal

Live simulator

Environment stream

Pre-emptive diagnosis

Signals worth investigating

No abnormal signals yet.

Past + future breaking change watch

Version exposure

Continuous intelligence

What MADD watches

Explainable diagnosis

Evidence graph

Observed ≠ inferred
Jira / ServiceNow / ADO

Ticket-created webhook → classify → investigate → append evidence and status.

incident.read · comment.write
Maximo / MAS

GET APIs, metadata queries, approved SQL SELECT probes, logs and system information.

read-only capability contract
OpenShift / telemetry

Pod status, events, restarts, logs, metrics and OpenTelemetry streams.

get/list/watch only

Pilot boundary

No generic shell. No arbitrary SQL. No remediation tool.

The agent chooses from explicit read-only probes. Real customer connectors replace the simulator adapters without changing the investigation model.