IBM has published the March 2026 release of the Maximo Application Suite 9.2 Feature Channel, the latest in a monthly cadence that started in September 2025. For organisations running MAS, the MAS 9.2 Feature Channel is the visible part of how IBM now delivers Maximo: one major release per year, with a non-production early-access stream feeding into it. It is worth understanding what that stream is actually for, because the wrong assumptions in either direction (treating it as production-grade, or ignoring it entirely) tend to surface during an upgrade rather than during planning.
What The Feature Channel Is
The Feature Channel is a continuous-delivery stream that IBM publishes alongside the maintained MAS releases. New features being built towards the next major release are bundled into monthly drops that subscribed customers can install in non-production environments. The mechanism is the same operator catalog upgrade flow already used for moving between MAS versions, so the plumbing is familiar.
A few points are worth being precise about, because the support rules around the Feature Channel are different from the standard maintained release:
- For client-managed MAS deployments, the Feature Channel is non-production only. Subscribing is a deliberate act by the MAS administrator. It is not pushed onto an environment by default.
- IBM Support accepts cases only against the latest available Feature Channel bundle in a non-production environment. Severity must be 3 or 4, and cases cannot be escalated.
- Defects found in a Feature Channel are tracked in the same way as any other defect, but the fix appears in a future Feature Channel drop, not in a back-port to the maintained release.
- The MAS UI does not surface whether a given environment is on a Long-Term Release or a Feature Channel build. Identifying which stream an environment is on is an operational responsibility.
- SaaS customers are an exception. They can run Feature Channel functions in production, and IBM treats those functions like any other when raising cases.
When the next major release is generally available, the Feature Channel that fed it is retired and a new one opens against the release after that. Today’s MAS 9.2 Feature Channel is the on-ramp to MAS 9.2 general availability. The previous 9.1 Feature Channel closed when 9.1 went GA in June 2025.
Where MAS 9.2 Sits On The Calendar
The pattern is becoming readable. MAS 9.0 reached general availability in June 2024. MAS 9.1 reached general availability in June 2025. Monthly MAS 9.2 Feature Channel drops have been appearing since September 2025, and as of the March 2026 release, IBM continues to publish updates to Core, Manage, Visual Inspection, AI Service, Optimizer, Real Estate and Facilities, and Maximo IT through the same channel.
The annual major plus monthly Feature Channel rhythm is now the planning baseline. This sits alongside the support changes already in effect for the 8.x line, which we covered in the April 2026 MAS support transitions. For teams still on classic Maximo 7.6.x or early MAS 8.x, the Feature Channel is not a route. It is a stream that only opens once an environment is on the current MAS major release.
What Early Access Is Actually For
The most useful framing is to think of the Feature Channel as test capacity that IBM gives back to customers, not as a way to get production features faster.
There are three things it is genuinely good for:
- Validating customisations against forthcoming code. If a programme has invested in Automation Scripts, custom UI behaviour, integrations through Object Structures and Enterprise Services, or report changes, running those in a Feature Channel environment surfaces breakage early. Six or nine months of lead time on a regression problem is worth more than the same finding during the upgrade window.
- Evaluating new features in context. A feature list reads the same to every reader. A new feature working against your own data, your own roles and your own configuration is the conversation that produces a real adoption decision. The Feature Channel makes that conversation possible before commercial commitment.
- De-risking the major upgrade. When the major release lands, the environment that has been tracking the Feature Channel has already absorbed most of the change. The remaining step is smaller, better understood, and easier to plan.
What the Feature Channel is not good for is filling gaps in production today. The support model deliberately limits what IBM will commit to, and rightly so. Treating a non-production stream as a substitute for the maintained release is a category error that lands on the wrong end of the support arrangement.
Practical Guardrails
For client-managed estates, a small number of operating decisions repay attention.
Pick the right environment
The Feature Channel needs an environment that is genuinely non-production but representative. A barely-used sandbox tells you very little. The most useful target is a Test or Pre-Production cluster that mirrors the production configuration closely enough that the regression and integration behaviour is informative. The cost of standing up that environment is part of the cost of using the Feature Channel well.
Decide who subscribes and why
Subscription is a conscious act. The decision of when to enable the Feature Channel, against which environment, and for which window, belongs to whoever owns MAS platform operations. A clean log of when the subscription was switched on and off is more useful than it sounds when a defect investigation needs the timeline.
Treat each drop as a change
Each Feature Channel drop is a substantive change to the platform. Apply normal change governance: a test pass on critical journeys, a check of integration endpoints, a glance at automation script libraries, and a record of what changed. Skipping that discipline reproduces a common upgrade failure pattern at smaller scale, every month.
Keep an upgrade plan separate
Tracking the Feature Channel is not the same as planning the move to the next major release. The production cutover still needs a properly scoped upgrade workstream with the standard checks on object structure design, customisation inventory, integration contracts, OpenShift readiness, and user adoption. Confusing early-access exposure with upgrade readiness is one of the more expensive mistakes available in this model.
Watch the SaaS divergence
Organisations running MAS as a Service have a materially different Feature Channel experience: features can land in production through that route, and the operational implications are mostly IBM’s to manage. Hybrid estates (some SaaS workloads, some client-managed) should expect to see the same feature available at different times in different parts of the estate. That is not a defect, but it should not be a surprise either.
What To Do Now
For programmes already on MAS 9.1, a Feature Channel subscription on a representative non-production environment is a low-risk way to start absorbing what 9.2 will bring. The cost is small. The benefit, in upgrade certainty and adoption time, accrues quietly across the year.
For programmes on MAS 8.10 or 8.11 still bridging the support transition, the Feature Channel is not the next decision. Reaching a supported MAS 9.x baseline comes first; the Feature Channel becomes useful after that.
For programmes still on classic Maximo 7.6.x, the relevant work is the migration itself. The Feature Channel is a downstream consideration, not part of the path to 9.x.
The annual major release and the monthly Feature Channel are the operating rhythm of MAS now. Reading them as one system, rather than two competing streams, is what turns IBM’s release model into an asset rather than a complication.