ACHANTA VENKATA SATYANARAYANA

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.

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.

How Maximo Health scores trigger inspections, prioritize backlogs, adjust PM frequencies, and feed capital planning. End-to-end use cases across manufacturing, utilities, and facilities.

How to scale Maximo Health from pilot to enterprise program. Rollout strategies, governance structures, common pitfalls, and real-world patterns from organizations that made Health permanent.

How to structure health components, map indicators, set weightings, define thresholds, and model criticality in Maximo Health. Includes safety-critical vs production-critical strategy patterns.

How to design Maximo Health dashboards for executives, reliability engineers, and planners. Core KPIs, drill-down patterns, and portfolio views that turn health data into decisions.

Deep dive into the Maximo Health data model -- how condition indicators, component scores, and weightings transform raw maintenance data into actionable health and risk metrics.

Step-by-step guide to enabling IBM Maximo Health in MAS -- prerequisites, activation, security configuration, asset onboarding, and the verification checklist that proves it actually works.

How to feed real-time IoT telemetry from Maximo Monitor and failure predictions from Maximo Predict into your Maximo Health models. Architecture, data flows, and governance.

Discover how IBM Maximo Health transforms scattered maintenance data into actionable health scores and risk indicators. Stop guessing which assets need attention first.

An 8-part series on IBM Maximo Health covering health scoring, criticality modeling, Monitor and Predict integration, dashboards, automation, and governance for data-driven asset decisions.

Configure intelligent alert rules, severity-based escalation, multi-channel notifications, and automated work order creation in IBM Maximo Monitor.

Implement built-in analytics, custom Python functions, anomaly detection with Isolation Forest and LSTM, and ML-powered predictive maintenance in Maximo Monitor.

Real-world Maximo Monitor case studies with measured ROI across manufacturing, utilities, energy, transportation, and facilities -- plus battle-tested implementation best practices.

Design effective Maximo Monitor dashboards with time-series charts, KPI cards, drill-downs, and role-based views that turn IoT data into operational decisions.

Master MQTT and HTTP protocols for IoT data ingestion, device type design, bulk registration, gateway architecture, and data quality validation in Maximo Monitor.

Step-by-step guide to deploying IBM Maximo Monitor, connecting your first IoT device via MQTT, and building your first operational dashboard.

Master Maximo Monitor REST APIs, Python SDK, webhook patterns, and enterprise integration with Manage, data lakes, ERP systems, and custom applications.

Learn what IBM Maximo Monitor is, how its IoT architecture works, and why it transforms reactive maintenance into predictive intelligence for enterprise assets.

Master IBM Maximo Monitor from zero to production. Our 8-part series covers IoT data ingestion, dashboards, AI analytics, alerts, and enterprise integration.