50 articles
An asset condition insight can sound current even when the evidence behind it has changed. A practical freshness contract connects the assistant's output to the asset, the source records, the review decision and the moment when the answer must be checked again.
A vehicle service schedule is only as dependable as the readings and decisions behind it. This practical guide connects meter ownership, preventive maintenance configuration, exception handling, and work order evidence.
A fluent answer is not the same as an accepted maintenance decision. Build a repeatable test that checks scope, source records, permissions, freshness, and human review.
A floor-aware map is more than a set of drawings. It is a contract between facility records, spatial features, relationship keys, and the people who maintain them.
A completed installation is not the same as a fleet operation ready for work. A hands-on Transportation lab exposes the permissions, meter semantics, and warranty checks that deserve acceptance tests before rollout.
Importing a building handover can create an impressive asset register, but a populated register is not automatically ready for reliability decisions. This guide defines the evidence and ownership needed between import, commissioning and dependable asset performance analysis.
A photograph can make a service request useful, but the order in which a mobile request and its attachment are saved changes what users and support teams must verify. This guide turns a community question and IBM documentation into a practical attachment recovery and acceptance contract.
A community waste management lab follows spent battery acid from a forklift job through storage, disposal and record closure. Its most useful implementation lessons concern saved child records, deadline queries and the difference between a completed form and a dependable environmental control.
Restoring a Manage database and requesting an older application version are not enough to prove recovery. IBM documents an Entity Manager failure in which a newer operator, an older version lock and missing resource permissions prevent the application from starting.
CanMUG Calgary's published program connects scheduling, inspections, materials, mobile work, and adoption. Read it as a set of operating handoffs to examine, not as proof that a product demonstration has solved the work between teams.
An AI security review can miss the transport and cache components surrounding the model. Two IBM security bulletins provide a concrete starting point for reviewing Maximo Assistant dependencies without inventing an Assistant-specific exploit.
IBM describes Dubai Municipality bringing more than 350,000 assets into a unified enterprise asset management platform. The useful lesson is its information framework, not an unsupported claim about savings or artificial intelligence.
A faster Maximo Assistant response is not an improvement if it loses the records, business context or evidence users need. IBM's documented configuration arguments provide a practical starting point for testing response time and correctness together.
A Transportation lab demonstrates how a successful meter load can produce the wrong operational history. Design the integration around reading meaning, vehicle identity, transaction effects and downstream maintenance evidence before connecting another feed.
A hands-on MREF budgeting lab separates approved budget, available funding, contractual commitments and forecast final cost. Its unfinished approval path also shows why a convincing project summary is not automatically evidence of a working financial control.
A documented Maximo Optimizer lab moves from infeasibility to a valid solution while leaving work unresolved. Reliability teams should treat solver status, excluded work and dashboard provenance as separate acceptance questions before trusting a maintenance plan.
Maximo Mobile brings permit requests to the job site, but capturing a request is not the same as authorizing hazardous work. A defensible rollout tests authority, server-side controls and handback evidence rather than celebrating a successful form submission.
IBM's Manage dependency bulletin describes URI interpretation defects alongside resource exhaustion vulnerabilities. Read its release-specific remediation rows carefully, then build a patch evidence package that separates affected packages from demonstrated exploit paths.
Maximo Monitor 9.2 removes the mandatory IoT Platform dependency and moves device management into Monitor. The upgrade deserves a migration evidence plan, not just a smaller deployment diagram.
NEMUG's published fall agenda brings data decisions, AI Service components, facilities integration, and peer discussion into the same event. Use those topics to prepare testable questions and return with evidence rather than an unqualified roadmap promise.
The hardware requirement for an on-premises Maximo Assistant depends on its AI Service patch level. Start with the documented deployment boundary, then prove tool readiness, permissions, and operational control before promising a production service.
A six-exercise integration lab on MAS 9.2 draws a line through the estate: operational data on one side, business records on the other, and one arrow where an alert becomes a service request. The most useful part is the eleven-minute gap between saving an asset and delivering it.
A fifty-asset district cooling portfolio was run through Maximo Asset Investment Planning with a ten-year horizon and a fixed capital target. Five of eight budget levels came back feasible, the requested target was not one of them, and the cheapest plan was not the one with the lowest capital spend.
Maximo Mobile 9.2 adds permits, locations, timesheets, crew work orders and an assistant, and IBM's own documentation is explicit that the assistant works only in online mode. The features are real. The boundary is the part worth designing around.
Maximo Manage 9.2 can publish an active workflow process as a tool on its MCP server, and a practitioner walkthrough from October 2026 shows the whole path from a workflow description to a tool call. The interesting part is not the publish step. It is the filter that drops the tool, and the empty…
The Model Context Protocol server in MAS 9.2 changed what a Maximo deployment exposes. It is no longer a fixed endpoint performing one operation; it is a catalogue of discoverable tools an autonomous agent can enumerate, reason about, and invoke in sequences nobody explicitly wrote. This article…
Fifteen days past the 7.6.1 extended-support deadline, migration decisions are still usually argued in the abstract: no new fix packs, no security responses. CVE-2026-90920 supplies a sharper example than anyone could have scripted, because the remediation vehicle exists only on the supported…
On 12 October 2026 the NVD published three CVEs against IBM Maximo AI Service 9.1.0 and 9.2.0, all rated CVSS 7.5, all denial-of-service class, all remediated by 9.1.19 or later and 9.2.3 or later from the MAS catalog. This article separates what an attacker can actually do from what the headline…
MaximoLive Melbourne 2026 lands three days after this article is written, and the community's agenda has shifted noticeably toward governance, identity, and adoption. This article previews the sessions and themes worth a practitioner's attention, separates the roadmap signal from the vendor…
The most common reason agentic Maximo programmes never leave the pilot is a data-quality objection that rarely survives contact with close inspection. IBM's own position, published in October 2026, is that Maximo asset data is more ready for AI than practitioners assume. This article takes that…
The Model Context Protocol server that connects AI agents to Maximo is a genuine new attack surface, and IBM's AI Service RCE advisory proves the tooling layer is already being probed. This article maps the MCP trust boundary end to end, explains what CVE-2026-90920 exposes about the agentic…
Dubai Municipality unified more than 350,000 assets across ERP, CRM, GIS, and IoT on MAS 9.1 and was recognised as a UAE government pioneer. This article reads that announcement as an engineering document, extracting the asset hierarchy, data-integrity, and integration decisions that made a…
Maximo Real Estate and Facilities looks like Maximo Manage with different labels, and that assumption is what breaks reliability programmes during migration. This article builds the full vocabulary translation table from Manage to MREF, then shows where the mappings hold, where they silently…
A transit operator's move onto Maximo Manage and Asset Configuration Manager is the rare visible window into how public-sector EAM programmes really run. This article unpacks what a transit estate demands from an asset platform, why ACM sits at the center of the build, and what the delivery…
IBM is swapping the bundled AWS SDK for Java from v1 to v2 inside ordinary Maximo Manage fix packs, and any automation script or library that imports com.amazonaws.* stops compiling the moment the pack lands. This article maps the affected releases, shows how to enumerate your exposure before…
IBM published the Maximo Application Suite 9.2.7 readme on 29 September 2026 with three named upgrade and identity fixes and a fresh set of application versions on the 260924 operator catalog. This article unpacks what each fix actually addresses, why the MAXUSER and MASISSUER interaction is the…
IBM has acquired Prescinto, a Bengaluru-based renewables asset-performance SaaS firm, with IBM stating the deal will enhance the capabilities of Maximo Application Suite and further its leadership in energy and utilities. This article examines what the acquisition signal means for Maximo estates…
IBM community has published a first-party account of IBM Bob applied to Maximo documentation, while the MAS 9.2 MCP Server extends governed tool exposure into agentic workflows. This article examines the two halves of the agentic Maximo stack, the critical distinction between the first-party MCP…
The Maximo 7.6.1.x support entitlement ended on September 30, 2026, and the reliability organisation is one of the two functions that feels it first. This article explains why asset health and the integration layer below it are now the organisation's own remediation problem, what the September…
Extended support for Maximo 7.6.1.x ended on September 30, 2026, and nothing stopped working on October 1. What did change is the cost and risk calculus behind the mobile tooling decisions that field organisations deferred for ten weeks of countdown. This article explains what the post-entitlement…
The removal of AWS SDK for Java v1 JARs from Maximo Manage means custom code importing the com.amazonaws package will fail once the relevant fix pack is installed. This playbook gives teams a concrete inventory, triage, and remediation process for finding every affected artifact, including…
Extended support for Maximo 7.6.1.x ends September 30, 2026, and the most common practitioner question has shifted from how to stop the deadline to what happens the day after. This article explains precisely what stops on October 1, what continues to run, and how to build a defensible continuity…
IBM announced new capabilities in Maximo for Civil Infrastructure on September 16, 2026, and eight days later almost no one in the Maximo trade press has written about it. This article works through what lifespan extension for bridges, tunnels, highways, and railways actually demands from an asset…
Partners are now demonstrating conversational, multi-language agentic control of Maximo on the record, and every demonstration raises the same unanswered question about identity and authorization. This article applies IBM's own published AI security guidance to the specific mechanics of Maximo…
IBM Maximo Manage is migrating its bundled AWS SDK for Java from v1.x to v2.x and removing three com.amazonaws JARs in the process. Any automation script, custom Java class, or packaged integration that imports com.amazonaws.* will stop working after the fix pack lands, and the fix packs carrying…
There are four working days left before Maximo 7.6.1.x extended support ends on September 30, and September 22 is the second of them. This article treats the remainder as a business-day budget rather than a countdown, allocating each day to a specific gate and naming the work that cannot be…
UCLA Facilities Management has publicly committed to moving off aging on-premises Maximo onto Maximo Application Suite in the cloud, and the details it gave are the details most migration programs never document from inside. This article reads the announcement as a reference case: what the three…
When Maximo 7.6.1.x Extended Support ends on September 30, 2026, estates keep working but lose the entitlement that turns a disclosed defect into a vendor fix. This article maps the exposure surface that sits underneath Maximo and sets out a defensible compensating posture for teams that will run…
A cluster of IBM MQ defects published two weeks before the Maximo 7.6.1.x support deadline has no vendor workaround and sits directly on common Maximo file-based integration paths. This article examines the disclosure, the ownership gap it exposes, and a concrete remediation sequence for…
Extended support for Maximo 7.6.1.x ends on September 30, 2026, and only five full working days remain to prove anything about a cutover. This runbook sequences those five days into rehearsable gates, then covers the interim-support, compensating-control, and triage paths for estates that will not…
