Assetize — IBM Maximo knowledge
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
| Endpoint | https://assetize.com.au/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 19 tools · grade A (91) · pin ts_45c0a9d567914ef43fda8ed31ae43209 · protocol 2025-06-18 |
| First / last listed | 2026-10-25 08:22 UTC / 2026-10-25 08:22 UTC |
| Grade over time | 2026-10-25: A (91), 19 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: ask_maximo search_records lookup_error_code get_record compare_maximo_versions maximo_changelog change_watch list_gotchas records_by_version behaviour_history support_lifecycle corpus_stats test_automation_script_evidence upgrade_plan upgrade_checklist fixes_gained deprecation_register lifecycle_dates maximo_mobile
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 questions. params: question*, version |
search_records | Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs. params: query*, version, limit |
lookup_error_code | Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...). params: code* |
get_record | Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL. params: slug* |
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 reviewed, source-backed comparison and ranking as assetize.com.au/compare. Accepts either a version label ( params: from*, to* |
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/changelog. Optionally filter by version ("9.1", "9.2") and/or type. params: version, type, limit |
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), the IBM sources, and the corpus records that grounded it. Pass a slug for one change in full; omi params: slug, category, limit |
list_gotchas | Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas. params: version, limit |
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>. params: version*, limit |
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. params: version, limit |
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. params: version, limit |
corpus_stats | Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items. params: none |
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 evidence for. Static evidence only — it does not run the script. A missing attribute is reported NOT_ params: source*, lens* |
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; each with IBM's words and page), the few items only the customer's own system can answer, break-class c params: from*, to* |
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. params: from*, to*, 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. params: from*, to*, area, limit |
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. params: kind |
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. params: product, version |
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 attachments, administration (Mobile Configuration app, properties), the apps release by release (8.11, 9.0, 9. params: version, topic |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.