bots.st/assetize-ibm-maximo-knowledge
Assetize — IBM Maximo knowledge
Cited IBM Maximo upgrade, errors, lifecycle guidance
4578 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 19
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://assetize.com.au/mcp
What it can do
| Tool | What it says it does |
|---|---|
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… |
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. |
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… |
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… |
corpus_stats | Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items. |
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. |
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. |
get_record | Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL. |
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. |
list_gotchas | Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas. |
lookup_error_code | Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...). |
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… |
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… |
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>. |
search_records | Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs. |
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. |
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… |
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. |
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… |
In its maker's words
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
- Website
- assetize.com.au/connect
- Source
- github.com/softwarecomparereview/Assetize
- Publisher
- assetize.com.au
- Listed from
- the official MCP Registry as
au.com.assetize/maximo - Version
- 1.0.0, updated 25 Sep 2026
- Kinds of work
- Search and research, Law, tax and government, Other work
The domain it lives on
- assetize.com.au
- in our records
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 4578 ms | |
| Answered | 3521 ms | |
| Answered | 2283 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.