The Complete Guide
IBM ended regular base support for Maximo Asset Management 7.6.1.x on September 30, 2025. The announcement covers Maximo for Life Sciences 7.6.1.x as well. IBM EOS announcement
Before you commit to the next Maximo project, compare your alternatives. Put your maintenance work, calibration records, and the evidence Quality needs at the center of that decision.
Updated September 2026
We want Blue Mountain RAM (Regulatory Asset Manager) on your shortlist. Before you commit more budget to Maximo, ask us to demonstrate how RAM would handle your maintenance and calibration work. Bring your records, your exceptions, and the evidence Quality expects.
Then compare the proposals: What’s included, who does the work, who supports it, and what will it cost over time? This guide gives you the questions to ask IBM — and us — before you choose.
Keep these three questions separate:
Check your support and license position. Compare the IBM proposal with an alternative, including Blue Mountain RAM, against the same requirements. Ask each supplier to demonstrate your workflows and document implementation, ongoing responsibilities, and cost assumptions. You can start evaluating alternatives before you’ve decided to leave Maximo.
A deadline is a constraint on the decision. It isn’t a substitute for the decision.
Different roles come to this decision with different questions. Open the role closest to yours for the sections that answer your first question, then the deeper resources behind them.
GxP refers to the family of regulated good practices, including GMP.
First question: What are our options, and what do we have to prove about calibration and maintenance before we move?
First question: What do we have to assess before we accept any plan, and does end of support change our compliance position?
First question: What will change, and what evidence will we need for the new system?
First question: Who owns hosting, interfaces, access, and support under each option?
First question: What decision needs funding, by when, and what happens if we wait?
| Term | What it means here |
|---|---|
| EAM | Enterprise Asset Management. IBM uses "EAM" for the Maximo Asset Management 7.6.1.x product family. |
| MAS / Manage | Maximo Application Suite, IBM's current platform. "Manage" is Maximo Manage, the MAS application IBM's migration and dual support statements refer to. |
| Base, Extended, and Sustained Support | Base support is IBM's regular support period. Extended and Sustained Support are separately purchased offerings IBM may make available for a specific product and version; neither follows automatically. Which apply to you depends on your product and contract. |
| Dual support | IBM's term for the arrangement described under The 4 Dates That Shape Your Position. Read the trade-up, total-entitlement, and EAM-discontinuation conditions together. |
| AppPoints | The unit used in IBM's customer-managed Maximo Application Suite (MAS) 9.2 licensing guidance. See Licensing and AppPoints for the allocation questions to ask. |
| GMP / GxP | Good Manufacturing Practice, and the wider family of "good practice" regulations. A GxP system is one that supports regulated records or decisions. |
| CSA | Computer Software Assurance, FDA's February 2026 guidance for medical device production and quality system software. |
| OOT | Out of tolerance: a calibration result outside its limits. |
| RMI / SI bus | Remote Method Invocation and Service Integration buses, two ways a Maximo 7.6.1.x system can connect to other software. IBM's MAS migration conditions apply if you use them; see Integrations and Archiving. |
Three different things get lumped together when people say “end of support.” Keep them apart.
An end-of-support date on its own doesn’t make a validated system compliant or noncompliant. What changes is the risk picture: who fixes a defect, who patches a security issue, and how you’d recover from an outage. Write down what the new support position means for your installation, who owns the interim risk, and when you’ll review it.
Not every date applies to every customer. Check which ones match your product and your contract.
| Date | What happened or happens | What to check |
|---|---|---|
| September 30, 2025 | IBM’s regular base support for Maximo Asset Management 7.6.1.x ended. | What support agreement, if any, covers your installation today? |
| September 30, 2026 | The one-year, separately purchased Extended Support term for eligible EAM 7.6.1.x customers ends. | If you bought it, what still needs resolving before it ends, and what covers you afterward? This isn’t a new option to plan around. |
| April 30, 2027 | IBM’s dual support ends. It applies to EAM 7.6.1.x running under a MAS license obtained by trade-up. | If you’re on a trade-up, when does your technical migration to Manage finish? EAM use must stop at that point, even if it’s before April 2027. |
| September 30, 2030 | The published horizon for optional, separately purchased Sustained Support for eligible EAM 7.6.1.x customers. | Is it available to you, and what does the contract cover? The date isn’t an entitlement. |
The extension dates describe purchased, product-specific offerings. They don’t tell you whether you’re eligible, whether you can still order them, or that one follows the other. IBM EAM 7.6.1.x EOS announcement, IBM dual support statement
For customers with a MAS license obtained by trade-up, IBM describes “dual support”: EAM 7.6.1.x and MAS may run in any combination up to the total MAS entitlements. That arrangement ends April 30, 2027. Once technical migration to Maximo Manage is complete, the customer must discontinue EAM use. Confirm how the agreement applies to your deployment before scheduling coexistence or cutover. IBM dual support statement
IBM’s public support pages can’t tell you what your contract says. Contact your IBM sales representative, ask how these dates and any trade-up terms affect your current licensing contract, and get the answer in writing. Then read the Maximo 7.6.1.x support timeline for the questions to bring to that conversation.
These are categories to investigate. Whether each one is available to you, and whether it fits, depends on your contract and your requirements.
Staying with IBM can be the right call when MAS demonstrably handles your processes and you accept the commercial terms, hosting responsibilities, and migration work. Your existing experience and integrations are inputs to that assessment, not a substitute for it. Ask who will implement it. If the answer is a partner rather than IBM, get the partner’s scope and validation deliverables in writing, too.
Paying for continued support buys time; it doesn’t make the decision. If the offering is available to you, get the contract, the exclusions, and the response commitments in writing. Then set a date by which you’ll choose the next system, and decide what work the interim period funds.
Ask the provider to spell out, in writing, what it will diagnose, work around, or fix, and what it can’t support. Then check separately whether your IBM license lets you keep running the software under that arrangement; the service contract and the right to use the software are different questions.
Worth evaluating when your future requirements differ from what got you onto Maximo. Separate what you need from preferences about vendors or deployment technology. Then hold every candidate, IBM included, to the same demonstrations and the same written scope.
Equipment status, preventive maintenance history, calibration results, and approvals often feed quality decisions. Map which functions and records do. Quality should set the requirements and approve the assurance approach for those uses. A system-wide “it’s validated” label isn’t enough.
IBM’s customer-managed MAS 9.2 licensing guidance places Calibration within Maximo Manage entitlement, with access at the Base and Limited tiers. Calibration doesn’t carry a separate installation AppPoint charge; user access still consumes AppPoints under the applicable tier. Evaluate the calibration processes and records you actually run against the proposed release and configuration.
Ask each vendor to walk a calibration through using your own records. Cover standards, tolerances, data sheets, readings, as-found and as-left results, traceability, reverse traceability of standards, and how exceptions are handled. Reverse traceability is the question you’ll need answered when a standard is later found out of tolerance (OOT). Which instruments were calibrated with it during the period under review, and can you pull those records? That’s what your site’s impact assessment will need. Ask separately how review and approval would work. Record capability, entitlement, configuration, and the evidence you still need as separate items.
IBM states: “IBM Maximo for Life Sciences is covered in Maximo Calibration.” That describes where the legacy product landed in MAS. It doesn’t compare your configured environment feature by feature. IBM migration overview
Build your own list of the applications, records, workflows, supplier documents, and local extensions you use. Ask for the target release, required configuration, commercial scope, and demonstration evidence against each one. An item nobody has verified yet is an open item, not proof that a feature is missing.
A laboratory, a manufacturing site, and an organization managing buildings, utilities, and production equipment may need different workflows. Ask to see how the proposed design handles regulated and non-regulated work without losing the controls either one needs. One department’s successful demo doesn’t prove fit for the whole company.
For the MAS proposal, get clear written answers on licensing, hosting, integrations, and records. Here’s what to ask for. The Post-EOS Migration Guide provides additional planning context.
IBM licenses MAS with AppPoints and distinguishes concurrent, authorized, and install license types. For customer-managed MAS 9.2, the points a user consumes depend on the application tier that role needs. Industry solutions and add-ons are treated differently from supplemental add-ons, including whether Base-tier access applies.
Don’t try to reverse-engineer the quote. Ask IBM or your partner for a role-by-role allocation, any component installation charges, the release assumed, and the environments covered. Then have them reconcile that calculation to the price.
Customer-managed MAS 9.2 runs on Red Hat OpenShift, and you need entitlement for the cores you use. IBM’s bundled Red Hat rights apply in support of MAS and while IBM Subscription and Support is in effect; Reserved entitlements are excluded. MAS software as a service (SaaS) has its own service terms, and an existing Dedicated contract runs on its own terms.
Whatever the hosting model, get one written answer: who operates the platform, handles incidents, restores service, controls access, and approves changes?
Check whether your installation uses either connection method. If your Maximo talks to other systems through Remote Method Invocation (RMI), IBM says RMI isn’t supported in MAS. IBM points to Representational State Transfer (REST), a web-interface style, for custom extensions and external applications. If you use Service Integration buses, IBM says those clients “must migrate to Apache Kafka or another supported JMS provider.” JMS stands for Java Message Service. IBM migration overview
One more: if you rely on the bundled Maximo Archiving with InfoSphere Optim offering, IBM has withdrawn that bundle and says Maximo Archiving isn’t supported in MAS. Separately licensed Optim is a different question. IBM EOS announcement, IBM migration overview
Inventory what you actually use before you assume rebuild work either way. The migration workstreams post covers the integration and archiving decisions in detail.
“Maximo is old” is not a requirement. Neither is “cloud is modern.”
Write requirements you can watch someone perform: a technician records the reading, an authorized reviewer approves it, a historical record comes back with its context, an interface fails the way you agreed it should. Then ask every vendor to demonstrate those requirements with your scenarios, not theirs.
Three questions keep the comparison honest:
Whether you land on MAS or another platform, the work breaks into five workstreams. The migration workstreams post covers each in depth.
Start from intended use and what could reasonably go wrong for product quality, patient safety, record integrity, and the decisions people make from the system. Then choose assurance activities to match: scripted, unscripted, automated, or a mix. A feature name doesn’t decide the risk or the testing method.
FDA’s February 2026 Computer Software Assurance guidance covers medical device production and quality management system software under 21 CFR Part 820, as amended by the Quality Management System Regulation. Pharmaceutical manufacturers shouldn’t describe it as directly governing their Part 211 systems. Quality documents the applicable requirements and any use of the guidance’s principles within your own quality system. FDA CSA guidance
Supplier documentation helps when it’s relevant, current, and traceable. It doesn’t replace your own assessment of intended use or your verification of configuration, data, interfaces, access control, and procedures.
Decide what to migrate, what to keep somewhere else, and what you can retire under approved rules. Set acceptance criteria before the first trial load: counts, field values, units, relationships, attachments, signatures, and audit information. Check any plan to keep the old system running against your license and the dual support conditions above.
Separate real requirements from workarounds you built around the old system. For each required process, record the proposed design and the evidence it works, including how exceptions get handled.
Name the person who can approve go-live. Define freeze windows, the final load, rollback triggers, and how work due during the switch gets captured. Train by role, and set a stabilization period with owners and exit criteria.
For every interface, write down the source, destination, owner, transformation, authentication, recovery behavior, and acceptance evidence. Decide who owns failures after go-live.
Compare the same operating scenario over the same planning period, and keep quoted prices apart from estimates. These categories are inputs, not a verdict that one platform costs less.
| Cost category | Include in the scope |
|---|---|
| Software and entitlements | User roles, applications, installation charges, environments, support agreements, renewal assumptions, and exit rights. |
| Infrastructure and operations | Hosting, platform operation, monitoring, backup, recovery, security responsibilities, and internal labor. |
| Implementation and migration | Configuration, integrations, data preparation, conversion, reconciliation, archive access, training, and cutover. |
| Assurance and lifecycle | Supplier assessment, customer verification, documentation, change assessment, and ongoing review. |
| Transition and disruption | Temporary coexistence where permitted, continuity arrangements, stabilization, and contingency. |
Ask what changes if the site count, user roles, integration scope, or retained-record design changes. Show a range where assumptions aren’t settled. Don’t turn one customer’s example or an unscoped list price into a company-wide savings claim.
If you’re raising this from Maintenance, Metrology, or Engineering, identify who needs to assess the quality requirements, technical design, and budget. Use these questions to prepare for those conversations, then confirm who can approve or stop the decision at your company.
Record all three sets of answers together so the decision team can review the same assumptions.
If you’re evaluating alternatives, put Blue Mountain RAM through the same test. Ask us to demonstrate the maintenance and calibration processes you run, and to put implementation scope, supplier evidence, ongoing responsibilities, and record access in writing.
Bring Quality, IT, Maintenance, and Metrology to that evaluation. Every requirement should trace to a demonstration, a documented scope, or an item we’ve told you is unresolved.
Regular base support for IBM Maximo Asset Management 7.6.1.x ended September 30, 2025. Purchased extensions and license usage rights are separate questions. The support timeline lists the milestones and the questions to take to IBM.
Your license decides what you can run; your support contract decides what's covered. Neither follows from a support date, so check both. If you're on a MAS trade-up, IBM requires EAM use to stop once technical migration to Manage is complete.
Not by itself. Quality assesses the system's intended use, what the changed support position means for it, and the controls and evidence behind continued operation. Software licensing is a separate contractual question.
For EAM 7.6.1.x, it depends on the specific agreement that would apply after the purchased Extended Support term ends. Don't assume you're eligible for Sustained Support or that a third-party contract covers the same things. Get scope, exclusions, and dates in writing.
IBM's dual support ends. It applies to EAM 7.6.1.x running under a MAS license obtained by trade-up, in any combination up to the total MAS entitlements. EAM use must stop once technical migration to Maximo Manage is complete, even if that happens earlier. See the 4 dates and confirm how the agreement applies to your deployment.
Customer-managed MAS 9.2 uses OpenShift, with entitlement for the cores you use and conditions on the bundled Red Hat rights. SaaS runs under its own service terms, and existing Dedicated arrangements under their own contracts. See Hosting above.
In IBM's customer-managed MAS 9.2 licensing guidance, Calibration sits within Maximo Manage entitlement at the Base and Limited tiers, with no separate installation AppPoint charge; user access still consumes AppPoints. Evaluate the calibration processes and records you need against the proposed release and configuration. See Calibration Is Part of the Decision.
Whether you use the bundled Maximo Archiving with InfoSphere Optim offering. IBM has withdrawn that bundle and says Maximo Archiving isn't supported in MAS; separately licensed Optim is a different question. Confirm licensing, compatibility, retrieval, and retention needs for your design. See Integrations and Archiving.
There isn't a universal best replacement. It depends on your processes, asset mix, records, integrations, assurance evidence, operating responsibilities, and cost assumptions. MAS may meet those requirements; another platform may meet them. The useful comparison is the documented fit for your operation.
A credible estimate needs an inventory, a target design, an evidence plan, resource commitments, and a dependency schedule. Ask the implementation team to show you the critical path and its assumptions. A vendor's typical duration, or another site's experience, doesn't set your schedule.
Decide by data class and intended use: what the new system needs, what you'll keep elsewhere and how you'll retrieve it, and the basis for anything you retire. Don't forget attachments, audit information, signatures, and historical context.
Start with a written support and license position. Agree on the requirements and the evidence you’ll use to judge each path. Then put owners and dates against the open work.
Download the Post-EOS Migration Guide or discuss your migration requirements with Blue Mountain.
This material is a planning framework, not legal or regulatory advice, an IBM entitlement determination, or a guarantee of compliance. Confirm contractual terms with IBM or the relevant supplier and approve the assurance approach through your quality system.
