135 posts tagged “Maximo”

IBM framed MAS 9.2 around asset-first AI and agentic workflows. This is an evidence-tiered assessment of what that actually means — the agentic Maximo Assistant, the Maximo MCP server, AI-generated insights with confidence scores, RAG lease extraction, watsonx Orchestrate in Maximo IT, and AI Service AppPoint tracking — separating what product documentation confirms from what only the announcement claims.

A structured reality check on IBM Maximo Application Suite 9.2. Eight gates that decide whether you can and should move, five verdicts mapped to real customer profiles, and an honest accounting of what the release does and doesn't give you.

A complete, sourced walkthrough of Maximo Manage 9.2 — the new Tickets and Alerts applications, AI-generated alert insights, Collaborate moving inside Manage, automated calibration accuracy validation for ISO/IEC 17025 and ISO 15189, six new time zone processing rules, Java 25, and everything new in Maximo Optimizer 9.2.

A seven-part, primary-source series on IBM Maximo Application Suite 9.2. What actually shipped on 25 June 2026, how it compares to 9.1 and 9.0, what changed inside Manage and across the suite, what the AI layer really contains, the upgrade items that bite hardest, and an honest verdict on who qualifies.

Monitor 9.2 drops its IoT Platform dependency and becomes stand-alone. MVI removes Caffe and Darknet and retroactively drops NVIDIA Pascal GPUs. Health, Predict, Maximo IT, Real Estate and Facilities, HSE, Oil & Gas and AIP all shipped real changes. Here's the product-by-product breakdown, and which ones force work on upgrade.

A ranked, sourced watch-list for the MAS 9.2 upgrade — the Db2 12 licence trap that takes production down 30 days later, the removed user management APIs, add-on parity, SCIM migration, two irreversible settings, Java 25, MVI's retroactive GPU removal, and the small ones that still cost you a weekend.

A dimension-by-dimension comparison of Maximo Application Suite 9.0, 9.1 and 9.2 — platform and navigation, AI, applications, Java and database prerequisites, and support lifecycle — built only from IBM's own pages, with every claim we could not verify flagged as such.

A plain-language guide to MAS 9.2 for business and functional leaders: what was released, what the Feature Channel means, how support works, what 8.x customers must check, and how to confirm platform requirements.

MAS 9 gives you four different ways to get numbers out of Maximo — BIRT, the Operational Dashboard, Cognos Analytics, and the self-service BI tier beyond it. Here's how each one actually works, where its ceiling is, and a decision framework for picking the right one for every report you own.

Work Centers with no migration tool, custom Java that won't compile on 17, RMI integrations that die in a container, and an admin mode window that blocks every user. Here's the honest list of what actually breaks on a Maximo 7.6-to-MAS-9 upgrade, and how upgrade teams have prepared for each one.

A six-part series on IBM's own answer to the MAS 9 native-analytics ceiling: watsonx.data's open Iceberg lakehouse, fit-for-purpose query engines, MIF/Kafka extraction, medallion architecture, watsonx.ai and RAG, closed-loop write-back, and an honest head-to-head with Databricks.

MAS 9 native analytics has a real ceiling. This post names it, then makes the honest IBM-native case for watsonx.data — open Apache Iceberg, fit-for-purpose engines, and a bridge to watsonx.ai your MAS AI Service license already opened.

The three IBM-sanctioned ways to move Maximo data into watsonx.data — MIF REST/JSON over OSLC, the Kafka source connector, and MAS 9.1's asynchronous bulk export — plus the Cloud Pak for Data fabric and the SaaS constraint that decides which ones you can actually use.

How Apache Iceberg's ACID transactions, schema evolution, and time-travel snapshots map onto a Bronze/Silver/Gold medallion for Maximo EAM data — with the full Db2 CREATE DATALAKE TABLE syntax, named conformed entities, and the registration mechanics that keep it all in sync.

How watsonx.data routes interactive SQL, ETL/ML, and high-concurrency BI to different engines — Presto, Presto C++/Velox, Spark, Db2 Warehouse, Netezza — over a single Iceberg copy, with the coordinator/worker architecture, IBM's price/performance claims vs Photon, and the RU cost model.

How the Maximo Iceberg lakehouse stops being a reporting layer: custom PdM/RUL models on watsonx.ai, AutoAI for RAG, the Milvus/OpenSearch/OpenRAG stack over maintenance manuals and work-order text, Granite and Llama model routing, and three concrete ways to write AI outputs back into Maximo.

The series finale: a caveated head-to-head — Iceberg vs. Delta, Presto C++/Velox vs. Photon, IBM Knowledge Catalog vs. Unity Catalog, Milvus/OpenRAG vs. Databricks vector search — plus how IKC and Apache Ranger govern Maximo-derived data, LABTRANS PII masking, and watsonx.governance lineage.

How Unity Catalog's row filters, column masks, and lineage graph turn a Maximo-derived Databricks lakehouse into an auditable asset — mapped directly to the Maximo security groups, site/org restrictions, and data restrictions administrators already configure.

MAS 9 ships real native analytics — Operational Dashboards, Cognos, Health, Predict, Monitor — but every one of them has a ceiling. Part 1 names those ceilings precisely and explains why a lakehouse, not another dashboard, is what sits past them.

Four real ways to extract MAS 9 data for a Databricks lakehouse — REST/JSON API, MIF over Kafka and the Data Export framework, DB-direct, and Lakehouse Federation — with real object structures, Kafka broker config, and honest CDC framing.

A table-by-table medallion architecture for MAS 9 data — cleansing rules for WORKORDER, ASSET, MATUSETRANS, PM, and meter data, conformed dimensions, and gold marts for reliability and cost analytics.

Worked Databricks SQL for the five gold-layer questions a maintenance leader actually asks: MTBF/MTTR trend health, maintenance cost rollups, slow-moving inventory, work order backlog aging, and PM compliance — built on Part 3's silver and gold tables.

A scored decision framework for choosing between Maximo Predict's prebuilt models and a custom AutoML/MLflow model in Databricks — data needs, in-house ML skills, AppPoints economics, and how to write a score back into Maximo.

A six-part series on where MAS 9 native analytics stops and Databricks starts — data extraction patterns, the medallion architecture for Maximo objects, five concrete analytics use cases, custom ML versus Maximo Predict, and lakehouse governance.

The Maximo Assistant is not a checkbox — it's a deployment project. The real path: the Maximo AI Service operator on OpenShift, the watsonx.ai connection, training recommendation models on your own data, and the feedback loop that keeps them improving. Mapped to IBM's ten team-exploration tasks and the realistic 68–128 hour pilot estimate.

Generative AI is a governance conversation before it is a technology one. The data-residency decision baked into SaaS-versus-on-premises watsonx.ai, the human-in-the-loop controls (confidence scores and accept/modify/reject) that keep the AI a recommender not a decider, the feedback loop as a governed data process, and the AppPoints licensing that gates who gets access — with a go-live governance checklist.

When something is broken and the technician doesn't know why, this is where the Maximo Assistant earns its keep. How step-by-step troubleshooting guidance walks from symptom to likely cause, how AI failure-code identification recommends failure class, problem, cause, and remedy codes, how Visual Inspection folds in visual diagnosis, and how PM optimization recommends which preventive work to cut, tighten, or extend.

What the Maximo Assistant actually is, the IBM watsonx.ai foundation models that power it, and the Maximo AI Service that connects the two. A grounded introduction to generative AI in MAS 9 — including an honest map of what it does and, just as importantly, what it does not do.

The feature people mean when they say 'AI in Maximo.' How the Maximo Assistant drafts a work order from a plain-English description, replaces filter queries with natural-language asset search, and recommends field values — priority, work type, failure codes, craft — each with a confidence score you can accept, modify, or reject.

A grounded six-part series on the Maximo Assistant and AI Assist in MAS 9 — the watsonx.ai foundation, natural-language work guidance, SME collaboration and knowledge capture, guided troubleshooting, the AI Service deployment path, and the governance, data-privacy, and AppPoints decisions that gate it. Written for teams who want to know what generative AI in Maximo actually does, and what it does not.

Your best fixes live in your veterans' heads and in long-description fields nobody reads. Here's how the Maximo Assistant surfaces them — knowledge base search across manuals, SOPs, and repair narratives; similar-record detection that transfers knowledge from experienced staff to new staff; and remote technician assistance that connects the field to subject-matter experts.

How Maximo Civil Infrastructure uses Visual Inspection to analyze drone and camera imagery for automated defect detection on bridge decks, piers, and beams; the difference between classic CNN models and the Large Vision Models introduced in MAS 9.1 that are trained for civil infrastructure and need minimal training data; the GPU, camera, and training-data requirements; how visual evidence links to element-level inspection records; and the honest watsonx.ai/FedRAMP reality that determines whether the LVM capability is even available to a government agency.

The heart of Maximo Civil Infrastructure: FHWA-compliant bridge inspection. How the 0-9 NBI component ratings for deck, superstructure, and substructure coexist with AASHTO element condition states; how condition-state quantity tracking works; how the two-year inspection cycle and special cycles (fracture-critical, underwater) are scheduled; how load rating and scour-critical status are tracked; and how NBI-format export supports the federal submission — walked through a full bridge inspection with sample values.

The finale: the full capability-to-regulation crosswalk for Maximo Civil Infrastructure across FHWA NBIS, AASHTO, 23 CFR 650, NTIS, MAP-21/FAST Act, and GASB 34; how transit's FTA State of Good Repair and Transit Asset Management (TAM) plan data are supported; the reporting the application produces for federal submission and management; the deployment prerequisites and AppPoints posture in one place; and a rollout checklist that mirrors a real pilot from portfolio assessment to first federal-format report.

Beyond bridges: how Maximo Civil Infrastructure handles road condition (PCI scoring, distress identification, IRI ride quality, treatment recommendation), tunnel inspection under NTIS with fire/life-safety element tracking, deficiency tracking that prioritizes by severity and safety impact and links to work orders, and condition-based maintenance that triggers work when a rating drops below threshold with Maximo Health supplying the condition score — walked through a full pavement-section example.

What Maximo Civil Infrastructure is, who it is for, and how it models bridges, roads, and tunnels as element-based and linear assets that the standard Manage data model was never built to hold. Covers the AASHTO element taxonomy mapped onto a Maximo asset hierarchy, where the application sits relative to Manage, Health, and Visual Inspection, the honest licensing and deployment posture, and a fully worked bridge-modeling example.

A five-part, infrastructure-specific guide to Maximo Civil Infrastructure as it ships inside MAS Manage: the linear and element-based asset model for bridges, roads, and tunnels; FHWA NBI bridge inspection and AASHTO element condition assessment; pavement (PCI/IRI) and tunnel (NTIS) condition; AI-augmented inspection with Visual Inspection and Large Vision Models; and the full regulatory crosswalk (23 CFR 650, MAP-21/FAST Act, GASB 34, FTA State of Good Repair) with a government-deployment reality check.

The PLUSG story was only the beginning. Maximo has five distinct types of extension crossover — prefix reuse collisions (PLUSV: Primavera vs Civil Infrastructure), Nuclear's non-standard PLUS pattern with 13 cloned (Nuc) applications, and five business concepts that multiple products implement independently. Here is the complete crossover map, the SQL to diagnose which PLUSV you actually have, and the decision guidance for when two modules solve the same problem.

The CAP backbone and the safety controls around work. How Condition Reports (Nuc) runs the Corrective Action Program under 10 CFR 50 Appendix B XVI, how the Solutions library enables operating-experience reuse, why nuclear Clearances are richer than core Maximo Lockout/Tagout, and how Permits (Nuc) and Sign On/Off wrap safety controls around the work package.

Design change under 10 CFR 50.59 and the work packages that execute it. How the Configuration Change Management (Nuc) module — Configuration Change Designer, Changes, Releases, Configuration Items — drives design control, how nuclear work packages assemble in Work Order Tracking (Nuc) with Impact Plans, and where hold points, QC points, and inspection points actually live when there is no application named for them.

The honest one. There is no application called Maintenance Rule in Maximo Nuclear. This part explains how 10 CFR 50.65 is actually implemented — through Assets (Nuc) performance monitoring, failure codes, Condition Monitoring, and Maximo Health — and how AP-913 equipment reliability rides the same configuration-not-app pattern, with the critical-component flag and Reliability Strategies doing the scoping work.

The two generations of Maximo for Nuclear — legacy MNP 7.6 on WebSphere versus the current Maximo Nuclear industry solution inside MAS Manage — and why conflating them is where most analysis goes wrong. Plus the AppPoints Premium licensing model, the single part number that entitles it, the 7.6.1.x End of Support clock, and why AI Service is a separate line in your model.

One table you can hand to an auditor or an analyst: the capability-to-regulator crosswalk for Maximo Nuclear. Every nuclear capability, the IBM-named application that delivers it (or the honest no-named-app note), and the primary regulatory driver across 10 CFR 50, NRC Regulatory Guides, INPO programs, and ASME NQA-1 — with the gaps flagged, not hidden.

A seven-part, nuclear-specific guide to IBM Maximo Nuclear as it ships inside MAS Manage on the MAS 9.x stream: product lineage and AppPoints Premium licensing, Tech Specs and LCO Tracking, configuration control and nuclear work packages, the Maintenance Rule (10 CFR 50.65), the Corrective Action Program and Clearance/Tagout, a full regulatory crosswalk, and the honest state of what's new in MAS 9.x for nuclear.

The regulatory core of Maximo Nuclear: how Tech Specs (Nuc) implements the Technical Specification register under 10 CFR 50.36, how Surveillance Requirements (Nuc) proves a Tech Spec is met, how LCO Tracking (Nuc) runs the action-statement timers that operationalize completion times, and where surveillance frequency and grace live in Maximo's frequency machinery.

The grounded read on the 9.x era for nuclear. What the non-nuclear-specific 9.0 and 9.1 foundations give nuclear by inheritance, why the MAS 9.2 Feature Channel's non-production caveat matters for change control, what the AI Service language-model transition means, that Nuclear has its own 9.2 APAR/DT stream, and where the nuclear-versus-generation product boundary actually sits.

Optimizer can only honor constraints that exist as data, and most of that data has to be cleaned before the first run. This is the tactical heart of the series: the prerequisite checklist, the craft/skill and shift cleanup that is the real project, the location coordinates that unlock travel optimization, and a data-readiness checklist to run before you blame the solver.

The series finale. How an optimized schedule surfaces in Graphical Assignment and the Dispatching Dashboard, the review-adjust-re-optimize rhythm dispatchers actually run, AppPoints licensing math, the Phase 4 rollout timeline, and the three documented use cases — field service, maintenance-window planning, emergency response — with the payoffs that prove Optimizer worked.

Optimizer's behavior is defined by three things — the constraints it must respect, the objectives you tell it to pursue, and the parameters that bound the solver. This part walks all nine scheduling constraints, the five weighted objective functions, crew scheduling and resource leveling, and the parameters that make or break a run.

Travel is where field service wins or loses. This part covers how Optimizer estimates travel — from straight-line distance to real road networks — how route optimization groups and sequences work, and when the optional Esri ArcGIS integration is worth the effort versus straight-line estimation.

A five-part program for standing up true scheduling optimization in IBM Maximo Application Suite 9 — from why the 7.6 Scheduler was never an optimizer, through the constraint-and-objective model, the labor and location data it lives or dies on, routing and ArcGIS spatial integration, to the Dispatching Dashboard and a phased, Phase-4 rollout.

The 7.6 Scheduler drew what a human decided; Maximo Optimizer decides. This part draws the hard line between graphical scheduling and mathematical optimization — constraint programming and mixed-integer programming — and positions Optimizer honestly as a Phase 4 amplifier that only works on clean data underneath it.

With the spine in place, you attach the maintenance decisions. Job plans define the task, PMs define the schedule, asset templates roll both out at fleet scale, and the dedicated Reliability Strategies application brings RCM/FMEA content natively into Maximo — with a vendor library of 800+ asset types and 58,000+ failure modes.

Asset Performance Management sits on top of the Manage spine, not in place of it. Maximo Health scores criticality and risk, Monitor answers 'is it abnormal now?', Predict answers 'when will it fail?', and Asset Investment Planning turns risk into capital timing — and all of them push work orders back into Manage to close the loop.

Before you touch a Maximo application, get the method right. This is Reliability Centered Maintenance reduced to SAE JA1011's seven questions, FMEA/FMECA with the RPN screen, and the decision logic that maps every failure mode to exactly one task type — run-to-failure, PM, condition-based, predictive, failure-finding, or redesign.

The metrics are the feedback loop that tunes the strategy. This is MTBF, MTTF, MTTR, availability, failure rate and OEE from first principles, the bathtub curve explained, and the Nowlan & Heap finding turned into a concrete PM-optimization method you can run against your own Maximo failure history.

Everything in this series assembles into a phased program: Phase 0 legacy cleanse during the upgrade window, Phase 1 the reference-data spine, Phase 2 the maintenance decisions, Phase 3 the Reliability Strategies layer, Phase 4 APM, and Phase 5 closing the loop — the phase that never ends. Each phase has exit criteria so you know when you can move on.

This is where reliability implementation succeeds or stalls. The strategy is only as good as the data underneath it, and the data has a hard dependency order. Here are the five realistic load tools, the eleven-step load sequence the MBO layer forces on you, per-object load specifics including the FAILURELIST restricted-object gotcha, and the validation and cleansing that must happen before you load anything.

Methodology becomes reference data here. The reliability spine is four stock MAS 9 Manage applications — Failure Codes, asset criticality, Condition Monitoring, and Meters — that together turn free-text guesswork into a controlled vocabulary, risk-based effort, and automatic condition-based work order generation.

An end-to-end, seven-part program for standing up a real reliability strategy in IBM Maximo Application Suite 9 — from RCM and FMEA fundamentals, through the Manage reliability spine, the Reliability Strategies app, and the APM layer, to dependency-correct data loads and a phased, upgrade-window rollout.

The buyer desk has its own Tier 0. Here is the BUYER_HOME starter pack for MAS 9 Manage: seven work-queue result sets and five KPIs, eighteen copy/paste saved queries scoped by buyer code, inbox hygiene with bulk approve and delegation, and the stale-PR, open-PO, and orphan-line cleanup that clears a migration mess in an afternoon.

The once-a-year wall-to-wall count that shuts the storeroom for days is the wrong model. In MAS 9 Manage you classify items A/B/C, count A-items monthly and C-items annually, generate count books from the Physical Count application, set variance tolerances that auto-adjust the small stuff, and run the whole thing paperless on Maximo Mobile — so accuracy is found in weeks, not a year.

This is the net-new material most buyers never had out of the box: an escalation engine that chases late vendors for you on a 3/7/14/30-day ladder, a 'My Late Orders' portlet, and a match-pay flow that auto-approves clean invoices and triages only the exceptions through Buyer, AP, and Procurement Manager. No custom code — just Escalations, Comm Templates, and SQL conditions.

Receiving is where a truck becomes storeroom balance. In MAS 9 Manage you can receive a 30-line PO in one pass, let a 102% tolerance receipt through without an exception, route inspection items to a holding location, and scan barcodes on both the Carbon desktop and Maximo Mobile — including offline. Here is how the receiving desk actually runs.

Issue Current Item is gone. In MAS 9 Manage, one application — Inventory Usage (INVUSAGE) — handles every material issue, return, and transfer. Here is how it works, why everything now flows through it before it touches balance, and how to put ten parts on a single document with one action or one string of barcode scans.

Cycle time from an approved requisition to an issued purchase order is the buyer's number-one metric. In MAS 9 Manage the conversion is a one-click Create Purchase Order action, desktop requisitions push intake upstream to the person who knows what they need, and a thresholded approval workflow routes by dollar value without approver-shopping. Here is the whole PR-to-PO flow, click by click.

The finale threads both desks together. Walk the seven phases of procure-to-pay in MAS 9 Manage — Plan, Demand, Source, Order, Expedite, Receive, Match & Pay — as one continuous flow, map the status transitions of all four objects on a single page, and follow one bearing from below-reorder-point to paid invoice on both the happy path and the escalation path.

Reservation hygiene is the hidden lever behind accurate availability; reorder points are the hidden lever behind stockouts and bloat. In MAS 9 Manage, learn hard vs soft reservations, how to clear stale ones in ten minutes a week, and how to set min/max/safety-stock/EOQ you can actually trust — including the dynamic lead time MAS 9 maintains for you.

A ten-part role-and-task playbook for the two people who run supply chain in MAS 9 Manage: the storekeeper and the buyer. Not a feature tour — a Day-1 field guide of Start Center recipes, saved queries, receiving and counting rhythms, reservation hygiene, PR-to-PO conversion, RFQ discipline, vendor escalation, and the full procure-to-pay lifecycle, grounded in how MAS 9.0 and 9.1 actually behave.

Sourcing is where discipline pays for itself. In MAS 9 Manage, run a 3-bid RFQ without the pain using templates, buy on the right contract across the nine OOB contract types, pull terms from a legal-approved library instead of retyping, and score vendors on real data so 'they feel unreliable' becomes 'they were 82% on-time in Q3.'

Go-live morning is won or lost in the first hour. Here is the Tier 0 starter pack for MAS 9 Manage: a Start Center template with six result-set portlets and four KPI tiles, fifteen copy/paste saved queries scoped by home storeroom, a 60-minute admin deployment plan, and an hour-1 checklist every storekeeper uses to confirm they got it — all out-of-the-box, no code.

How to read MAXOBJECT counts as an add-on's real database footprint, why HSE ships inside Oil & Gas under one shared PLUSG prefix, why Aviation conflicts with almost everything, and the exact MAS 9 compatibility matrix that tells you which extensions can coexist.

A developer's deep dive into the four-file MBO pattern behind every Maximo object, how MAXOBJECT.CLASSNAME links an object to its MBO Set class, and how a PLUS add-on layers on top through plain Java inheritance.

MAS 9.1 moved the JVM under every Maximo customization from Java 11 to Java 17. MAS 9.2 (June 2026) adds Java 25 at the platform and AI-Service level while Java 17 stays the baseline for Manage and your custom code. Here is what changes for existing extensions, why 9.2 is a mixed Java-17/Java-25 environment, how to test and remediate, and why the extension model endured while everything around it modernized.

How Maximo add-ons are activated in the MAS Manage component model, and how custom Java is now delivered as a Customization Archive baked into a container image on OpenShift instead of dropped into WebSphere — the old-world/MAS-world post for developers and upgrade teams.

The reference every Maximo developer bookmarks: the complete PLUS prefix directory (PLUSA through PLUSV, TLOAM, custom), which prefixes are included capabilities versus paid add-ons versus legacy, the five-layer extension hierarchy, and exactly how Maximo stitches multiple add-ons into one MBO inheritance chain — with the WorkOrder and Asset chains resolved step by step.

A developer's deep dive into product.xml — the extension control file behind every Maximo add-on. Learn the anatomy of mboset, mbo, class, field, and bean declarations, why alphabetical prefix order matters, what bytecode injection does at build time, and how the resolved top-of-chain class lands in MAXOBJECT.CLASSNAME so you can predict super() behavior.

A developer's deep dive into how IBM Maximo add-ons and industry solutions extend the core through Java — PLUS prefixes, the four-file MBO pattern, MBO inheritance chains, product.xml, bytecode injection, the compatibility matrix, the MAS 9 Customization Archive, and the Java 17 shift.

Approving a work order looks different in MAS 9. Here's the honest picture — the Workflow Designer is unchanged and your 7.6 workflows carry forward, the new Approvals Role-Based Application replaces the Work Supervisor approval flow (with one gap), watsonx-powered Work Order Intelligence recommends a failure code with a confidence score at approval, and electronic signatures can be enforced on specific status changes for regulated work.

Part 3 showed you how to consume the operational dashboard. This is the other half: how to build your own work order KPIs in MAS 9. The KPI Manager application, custom queries against any Maximo object, refresh intervals, green/yellow/red thresholds, trend calculations, matching a KPI to the right card type, and the MAS 9.1 ability for KPI services to return JSON from an external API.

The work order integration surface moved in MAS 9. Here's the JSON API for work orders — /api/os/mxwodetail with lean=1 — with real query and create examples, Kafka events for near-real-time WO changes, and the honest posture on MIF: it still works, but new integrations belong on REST and Kafka.

IBM's Operational Dashboard is the strategic replacement for Start Centers as the maintenance manager's command center. Here's what ships out of the box in MAS 9 Manage — the WO KPIs, the pre-built Maintenance Manager dashboard, the card types worth knowing — and the honest 9.1 limitation that keeps many teams running Start Centers side by side.

BIRT is not formally deprecated in MAS 9 and your existing work order reports still run. The upgrade mistake is treating the report catalog as a rebuild backlog. Here's how to rationalize WO reporting into KPI Manager cards, keep the reports that must stay reports, and know exactly when Cognos Analytics earns the job.

A six-part edge-filler series on the Work Order changes that the standard MAS 9 Manage guides skip: the Service Request RBA, the Approvals application and electronic signatures, the Operational Dashboard and out-of-the-box WO KPIs, custom KPI creation, rationalizing BIRT into KPI Manager, and the new WO REST and Kafka integration surface.

The Service Request Work Center is gone. Here's what replaced it in MAS 9 Manage — the classic SR app in Carbon, the Service Request Role-Based Application on MAF, the dedicated SR mobile app in 9.0 and 9.1 — and the honest truth about the single-screen SR-to-WO conversion that no longer exists.

A practitioner's deep dive into the generative AI built directly into Maximo Manage — Work Order Intelligence (9.0), the Maximo Assistant (9.1, expanded in 9.2), and the AI Configuration application — and how it differs from the standalone Health, Monitor, Predict, and Visual Inspection suites.

A practitioner's deep dive into asset and location management in Maximo Manage 9 — asset and location hierarchies, rotating items, Asset Configuration Manager for complex serialized assets, linear assets with GIS, and meters with condition monitoring.

The practitioner's guide to configuring and administering Maximo Manage 9 — Automation Scripts, Workflow Designer, Application Designer, Database Configuration, domains, security, Operational Dashboard, new tools like Formulas and in-MAS Application Configuration, and the admin split between MAS Suite and Manage.

A practitioner's deep dive into the Maximo Manage 9 scheduling stack — Gantt-based Graphical Scheduling for outages and projects, Graphical Assignment for short-horizon dispatch, the crafts/crews/calendars foundation, and the AI-driven Field Service Management solution introduced in 9.0 with its Scheduling and Dispatching dashboards, extended in 9.1.

A practitioner's deep dive into Inspections in Maximo Manage 9 — how the Inspection Forms Work Center became a Maximo Application Framework app, the refreshed Form Builder, question types and conditional logic, scoring and pass/fail, follow-up work orders and meter updates, form versioning, and offline mobile execution.

A practitioner's deep dive into inventory and procurement in Maximo Manage 9 — the ITEM and INVENTORY objects, storerooms, costing, reorder processing, the PR-to-PO-to-receipt-to-invoice flow, contracts and vendors, and the role-based Issues and Transfers app that carries forward key Inventory Work Center workflows.

A practitioner's deep dive into Maximo Mobile for Manage 9 — why it replaced Maximo Anywhere, how its offline-first REST and sync architecture works, the Technician, Inspections, and Inventory apps, low-code app definitions in Mobile Studio, RBAC and offline security, and how to migrate off MobileFirst.

A practitioner's deep dive into Maximo Reliability Strategies — how FMEA and RCM connect failure modes to job plans and PMs, the built-in library spanning 800 asset types and 58,000 failure modes, RPN-driven actions, custom strategies, and the AI assists added in Manage 9.1.

A practitioner's deep dive into IBM Maximo Manage on MAS 9 — eleven parts covering the new MAF role-based applications, Operational Dashboard, Reliability Strategies, Inspections, Work Management, Graphical Scheduling, Maximo Mobile, embedded AI, and how to configure and administer it all.

A practitioner's map of how Maximo 7.6 EAM became Maximo Manage in MAS 9 — the move to containers on OpenShift, the Maximo Application Framework, AppPoints licensing, and why your MBOs, scripts, and database survive the journey intact.

Work Centers are removed in Maximo Manage 9.0. Key experiences moved into Maximo Application Framework role-based applications, Maximo Mobile, and Operational Dashboard surfaces. Here's what changed, where the new apps live, and how to move your users across without disruption.

The heart of Maximo Manage — a practitioner's deep dive into the work order lifecycle, job plans with the new Qualifications field and milestone tasks, preventive maintenance and routes, plus the Work Order Planning and Work Queue Manager applications added in Manage 9.

How Maximo AI Assist uses watsonx.ai for natural language queries, WO creation, and field recommendations — plus Optimizer's constraint-based scheduling with route optimization. Also covers Civil Infrastructure and Parts Identifier.

A complete technical breakdown of every MAS 9 suite add-on that impacts supply chain operations — AI Assist (intelligent search, WO material recommendations, failure-to-parts mapping, document summarization), Parts Identifier (photo-based identification, catalog cross-reference, stock level checks), Health (scores driving demand predictability, replacement procurement, criticality stocking), Predict (failure timing to pre-position parts, RUL-based reservations), Monitor (condition-based orders, IoT consumption tracking, usage pattern analytics), and Optimizer (material-aware scheduling, multi-constraint coordination). The complete AI-to-parts pipeline.

The complete AppPoints licensing strategy and 13-month implementation roadmap for MAS 9 suite applications. Role-based allocation examples, optimization tips, phased deployment with success criteria, and why Phase 0 (data quality) determines everything.

The complete UI transformation in MAS 9 — IBM Carbon Design System replaces all Maximo skins, field labels move above fields, CSS class names changed between releases, and custom CSS is unsupported. What your users need to know before they log in.

How MAS 9 replaces Start Centers with Operational Dashboards, Result Set Portlets with Work Queues, and unlocks Graphical Scheduling for free. Complete coverage of card types, KPI Manager, Work Queue configuration, and the 8 scheduling applications now included in base Manage.

A comprehensive deep dive into the six MAS 9 Industry Solutions — Aviation (MSG-3, Airworthiness Directives), Transportation (fleet lifecycle, linear assets), Utilities (grid management, smart meters), Oil & Gas (process safety, turnarounds), Nuclear (tech specs, surveillance testing), and Civil Infrastructure (NBI bridge inspection, Large Vision Models). Regulatory frameworks, AppPoints licensing, and what changed from 7.6.

How MAS 9 transforms integration with JSON API as primary, Kafka for event streaming, and RMI deprecated. Plus the painful BIRT-to-Cognos reporting migration — no automatic conversion, every report recreated from scratch.

A complete breakdown of the MAS 9 licensing restructure — five previously paid modules now included free, what still requires separate licensing, AppPoints optimization strategies, and why your organization may be overpaying for licenses it already owns.

Everything you need to know about Maximo Health — asset health scoring from 0 to 100, degradation curves, Asset Investment Optimization (AIO), risk matrix, criticality scoring, data requirements, and industry use cases. The first suite application every organization should deploy.

Maximo Anywhere is gone — replaced by Maximo Mobile built on React.js with PWA deployment, server-side updates, and full offline sync. Complete coverage of all 7 mobile apps, Technician features, GPS sharing, barcode enforcement, and the Anywhere-to-Mobile migration path.

Complete guide to Maximo Monitor — the IoT platform for real-time asset monitoring with MQTT/REST ingestion, custom dashboards, anomaly detection, Python streaming analytics, edge data collection, and automated work order generation. Your assets have been trying to tell you something.

How Maximo Predict uses machine learning to predict failure dates, estimate remaining useful life, and detect anomalies — with Cox Proportional Hazards, Weibull survival analysis, and watsonx.ai integration. Data requirements, model pipeline, and why data science skills are mandatory.

A complete deep dive into every MAS 9 Maximo Mobile supply chain application — Issues & Transfers (staging, barcode, storeroom transfers), Inventory Count (cycle counts, blind mode, photo attachment), Receiving (PO-based, rotating assets, MAS 9.1 enhancements), Technician App material features, full offline capabilities, and the migration path from Maximo Anywhere.

The final installment of the MAS FEATURES series. A numbers-first deep dive into IBM MRO Inventory Optimization — 23 AI-powered capabilities, Essentials vs Standard comparison, 7 competitor profiles (Syncron, Baxter, Servigistics, IFS, Infor, Verusen, Kinaxis), a feature comparison matrix, decision framework, and the complete 12-month, 5-phase implementation roadmap with 425 hours of team exploration across 14 topic areas.

A complete technical breakdown of IBM Maximo MRO Inventory Optimization (AI-calculated ROP/MAX, demand forecasting, what-if analysis, Essentials vs Standard tiers) and Health Safety & Environment Manager (50+ applications across 6 modules — Incident Management, Permit to Work, Emissions, Operations Management, MOC, and Workforce Competency). Everything you need to evaluate, budget, and implement.

Everything that changed under the hood in MAS 9 — the architecture shift from WebSphere to OpenShift, Java 17 migration impact, sealed databases, containerized deployment, and what your infrastructure team needs to learn. The technical foundation every upgrade team must understand.

Every detail of MAS 9 procurement (Desktop Requisitions, PRs, POs, RFQs), all 10 contract types, receiving and inspection workflows, specialized inventory (rotating assets, condition-enabled, consignment, service items), cost accounting methods, lead time calculation, item status lifecycle, reorder processing, and the RBA gap that still forces classic apps.

A complete breakdown of Maximo Renewables (Prescinto), TRIRIGA Real Estate & Facilities Management, and the connector ecosystem for SAP, Oracle, Workday, watsonx.ai, and more. Three modules, three integration layers, zero 7.6 equivalents — and why they represent where IBM is betting the future of MAS.

How automation scripts survive Java 17, the free Reliability Strategies Library with 800+ equipment types, AI-powered natural language queries in Manage 9.1, and enhanced qualifications management. The tools that make MAS 9 yours.

How MAS 9 transforms security with mandatory SAML/OIDC/LDAP authentication, Suite-level SSO, API Key management, and Cert-Manager auto-rotation. Plus the deprecation of Google and Bing Maps in favor of OpenMap and ArcGIS integration.

A 4-part series breaking down every major feature change in MAS 9 — from Manage core platform transformation, to suite AI applications, paid add-ons and industry solutions, and the supply chain revolution. Your team's complete upgrade reference.

A deep dive into four MAS 9 paid add-ons — Maximo Spatial for GIS-driven asset management, Service Provider for multi-tenant outsourced maintenance, Asset Configuration Manager for complex regulated assets, and Maximo IT for unified OT/IT service management. Prerequisites, use cases, and what changed from 7.6.

Why MAS 9 is an entire Application Suite, not a Maximo upgrade. The integrated data pipeline from sensors to scheduling, how Manage is the hub, and why integrated value is multiplicative — not additive. The most important concept for your upgrade team to understand.

Complete coverage of MAS 9 supply chain architecture -- the three-tier licensing model, 7.6 vs MAS 9 comparison, inventory module with eight transaction types, six item master types, storeroom hierarchies, reservation system, count books with six selection methods, ABC analysis, and the full issues and transfers lifecycle. Every detail your supply team needs.

How Maximo Visual Inspection automates defect detection with image classification, object detection, anomaly detection, and OCR — all without data science skills. Edge deployment on NVIDIA Jetson, Large Vision Models in 9.1, and real-world use cases from manufacturing to utilities.

Work Centers were removed entirely in MAS 9 — replaced by Role-Based Applications built on React/MAF with no automatic migration. This is the most impactful change for daily users. Complete WC-to-RBA mapping, gap analysis, migration strategy, and timeline estimates.

A deep dive into the traditional Maximo 7.x administrator role — the WebSphere configuration, EAR deployments, JVM tuning, and server-level troubleshooting that defined two decades of Maximo operations. Understanding what we're leaving behind helps us navigate what comes next.

A complete guide to the Maximo Integration Framework — Object Structures, Enterprise Services, Publish Channels, Invocation Channels, Interface Tables, and JMS queues. Understanding the foundation helps you navigate the transformation to modern MAS integration patterns.

A 9-part series for Maximo administrators navigating the transition from legacy 7.x to MAS. Covers the evolving admin role, new responsibilities, SaaS vs on-prem differences, multi-environment architecture, required skills, daily tools, troubleshooting, and the future of the MAS sysadmin.

How MAS transforms Maximo integration from MIF-centric XML processing to an API-first architecture built on REST, OSLC, and cloud-native microservices. The architectural foundation for every modern Maximo integration.

Building enterprise-grade integration pipelines with IBM App Connect Enterprise, Apache Kafka, cloud platform connectors, and iPaaS solutions. How to orchestrate complex data flows between MAS and your enterprise ecosystem.

Migrating legacy Maximo-to-ERP integrations from MEA, direct database links, and MIF enterprise services to modern API-mediated patterns. Specific guidance for SAP S/4HANA, Oracle EBS, and Oracle Cloud integrations with MAS.

How MAS transforms Maximo's legacy publish and invocation channels into modern event-driven integration patterns using webhooks, Kafka event streams, and asynchronous messaging. A side-by-side mapping from old to new.

Securing MAS integrations with OAuth 2.0, mTLS, API management, and webhook verification. Building governance frameworks for API lifecycle management, audit trails, and compliance. Plus the future vision: AI-assisted integration and autonomous data flows.

The complete guide to modernizing your Maximo integration architecture. Eight parts covering the transformation from MIF, enterprise services, and publish channels to REST APIs, event-driven patterns, Kafka, and App Connect.

How MAS connects physical assets to digital systems through Maximo Monitor, MQTT protocols, IoT sensor data streams, real-time anomaly detection, and condition-based maintenance triggers. The integration frontier that legacy Maximo could never reach.

A hands-on technical deep dive into the MAS REST API — authentication, CRUD operations, complex queries, bulk operations, attachments, action invocations, and error handling. Complete with code examples in curl, Python, and Node.js.

Learn how to leverage AI capabilities in IBM Maximo to improve asset management and predictive maintenance.