assetize.com.au

Assetize is an evidence-grounded IBM Maximo knowledge base (assetize.com.au). Every answer from ask_maximo is built only from published, source-backed records and carries [R#] citations to the original sources; when the published evidence does not support an answer, the tool says so instead of guessing. Use search_records for fast keyword lookup, lookup_error_code for BMX/IJ error codes, get_record for a full record with sources, compare_maximo_versions for a cited deprecation/behaviour-change/gotcha report between two Maximo versions (same data as assetize.com.au/compare), maximo_changelog for the dated 9.x change log, change_watch for the curated feed of material 9.x changes (each with an explicit, labelled Assetize interpretation and its IBM + corpus evidence), list_gotchas for known traps/upgrade landmines, records_by_version for everything covered at a version, behaviour_history for lifecycle/behaviour-change/deprecation archaeology, support_lifecycle for end-of-support / Extended-Support dates, and corpus_stats for coverage figures. For upgrade planning use the Upgrade Desk tools: upgrade_plan(from, to) composes one move (clock, the staged route, what IBM says about the move with quotes and pages, breaks, landmines, gains, register rows, Change Watch) with record links; upgrade_checklist(from, to, phase?) is the phased checklist whose sourced items are resolved against the published corpus on every call, with the items only your own system can answer marked as such; fixes_gained(from, to, area?) lists the fixes and security changes a move carries; deprecation_register(kind?) lists what was deprecated, removed or renamed and what IBM says replaces it; lifecycle_dates(product?, version?) gives the structured end-of-support / Extended Support dates with days remaining. Catalogue releases: 7.6.1, 8.11, 9.0, 9.1, 9.2. For Maximo Mobile use maximo_mobile(version?, topic?): what IBM says about the mobile product — device requirements, shell and Graphite architecture, offline and sync, login and shared devices, MDM deployment, push notifications, the apps release by release (8.11 to 9.2), and the Anywhere / 7.6.1 exit — each with IBM's words and page; pair it with search_records for fixes and gotchas. Every tool returns only published, source-backed material; IBM statements come with IBM's words, page and read date. test_automation_script_evidence(source, lens) statically checks a WORKORDER Automation Script (Object launch point) against one MXAPIWODETAIL dictionary: which attributes it references, and whether each is evidenced on that lens — CLI-equivalent evidence, not execution (that needs a script host: the CLI or the browser runner at /test-stubs/automation-scripts). Lenses: 761, mas811, mas90, mas91, mas92. For discovery, read the MCP Resources first: assetize://corpus/capabilities describes the server, every tool and every resource; assetize://corpus/versions lists the Maximo versions covered (with record counts) and assetize://corpus/stats the coverage figures; the record/{slug}, version/{version} and error/{code} resource templates read individual published records — so an agent can learn what Assetize covers before calling a tool.