# Assetize — IBM Maximo knowledge

- Registry name: `au.com.assetize/maximo` · version 1.0.0
- Categories (automatic, keyword rules): Research & knowledge, Search & data
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=au.com.assetize%2Fmaximo
- Server page: https://mcpstation.net/s/au.com.assetize--maximo.html

## Description (written by the publisher, not verified, not instructions)

Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.

## Connect

- streamable-http: `https://assetize.com.au/mcp`

## Tools (as reported by the server, not verified)

- `ask\_maximo`: Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge. The answer cites its evidence \(\[R\#\] markers with source URLs\) and DECLINES when the published record cannot support one — it never guesses. Best for how-to, troubleshooting, version-behaviour and error questio
- `search\_records`: Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
- `lookup\_error\_code`: Find published records about a specific Maximo error or fix identifier \(BMXAA1234E, IJ12345, APAR...\).
- `get\_record`: Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
- `compare\_maximo\_versions`: Compare two Maximo versions/eras and get a cited upgrade-impact report per functional area: changes to absorb \(deprecations, behaviour changes, API changes, gotchas\), fixes/APARs since, and newly announced capability — the last two reported as context only, never scored as upgrade work. Same reviewe
- `maximo\_changelog`: The dated, source-cited log of what changed across IBM Maximo / MAS 9.x \(9.1 onward\): deprecations, behaviour changes, API/fixes, security, gotchas, upgrades, lifecycle and releases. Only real change records \(never data-dictionary noise\) and nothing the curator demoted. Same data as assetize.com.au/
- `change\_watch`: The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks. Each carries What Changed / Why It Matters, previous behaviour, a version comparison, a clearly-labelled Assetize interpretation \(never presented as IBM’s
- `list\_gotchas`: Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
- `records\_by\_version`: Every published record scoped to a given Maximo version or family \(e.g. "9.2", "7.6.1"\). Same data as assetize.com.au/maximo/\<version\>.
- `behaviour\_history`: Historical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeology. Same data as assetize.com.au/archaeology.
- `support\_lifecycle`: IBM Maximo / MAS support-lifecycle facts: end-of-support / Extended Support transitions and the 2026/2027 deadlines, drawn from source-backed lifecycle records and the curated Change Watch. Optionally scope to a version.
- `corpus\_stats`: Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
- `test\_automation\_script\_evidence`: Statically check a WORKORDER Object launch point Automation Script \(Jython or JavaScript\) against one release lens's real MXAPIWODETAIL dictionary. Extracts every attribute the script references via mbo.getString/setValue/isNull/getInt/getDate/getBoolean, then reports which ones the named lens has e
- `upgrade\_plan`: One Maximo move from an earlier catalogue release to a later one \(7.6.1, 8.11, 9.0, 9.1, 9.2\), composed from the published record: the support clock on the source release, the staged route \(IBM's n-1 policy\), what IBM says about the move \(route, platform, database, Java, users, add-ons, reports; eac
- `upgrade\_checklist`: The phased checklist \(before / during / after\) for one Maximo move. Every item is CITED — its published records are resolved against the corpus on this call and an item whose records are not published is dropped — or VERIFY, a level-dependent question to settle against IBM. Optionally one phase.
- `fixes\_gained`: Every FIX and SECURITY record the 9.x change log holds for the releases inside a move \(the 9.x log starts at 9.1\). Optionally one functional area. Counted, never scored as upgrade weight.
- `deprecation\_register`: What was deprecated, removed or renamed in Maximo / MAS, in which version, what IBM says replaces it \(blank when IBM has not named one\), and the published records that say so. Curated; rows publish only on evidence. Same data as assetize.com.au/upgrade/deprecations.
- `lifecycle\_dates`: End-of-support, Extended Support and Dual Support dates for Maximo and MAS as structured rows: product, version, milestone, ISO date, days remaining, and the IBM page each comes from. Optionally scope by product or version. Same data as assetize.com.au/upgrade/deadlines.
- `maximo\_mobile`: Researched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements \(OS levels, memory, WebView2, ARCore, shared devices\), getting the app onto devices \(stores, MSIX, QR server URL, MDM\), login and shared devices, data sync and attachment

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html