Service Requests in Manage 9: The Service Request RBA, the Mobile App, and the Conversion Flow That Didn't Survive

🎯 Who this is for: Service-desk leads, intake coordinators, and Maximo administrators who owned the Service Request Work Center — and opened MAS 9 to find it missing.

Series: Part 1 of 6 — MAS 9 Work Order Operations: The Missing Pieces | Read time: 18 minutes

Where the Service Request Work Center Went

You built a process around it. Requests came in, a supervisor triaged them in the Service Request Work Center, and the good ones became work orders — often without ever leaving that one screen. It was tidy. Then you logged into MAS 9 and the Work Center was simply not there.

Here's the plain truth: the Service Request Work Center was removed. It wasn't hidden behind a security setting or a feature flag. Work Centers as a whole were retired across MAS 9 (we covered that transition in the MAS MANAGE series, From Work Centers to Role-Based Applications), and Service Requests came along for the ride.

But "removed" is not "abandoned." The job the Work Center did got split and modernized into three surfaces:

  1. The classic Service Requests application — still here, now rendered in the Carbon Design System UI.
  2. The Service Request Role-Based Application (RBA) — a new React.js interface on the Maximo Application Framework (MAF), the same platform as Maximo Mobile.
  3. A dedicated Service Request mobile app — for field submitters and self-service users.

Let's map exactly what changed before we go deep on each.

📊 Old World vs. MAS 9

Capability — Maximo 7.6 — MAS 9

Classic application — Service Requests app — Still available, now in Carbon UI

Work Center — Service Request Work Center — Removed — replaced by the Service Request RBA

Mobile — Limited web access — Dedicated Service Request mobile app

Map integration — Not available — Create SRs from the map interface (MAS 9.1)

Self-service — Basic self-service portal — Enhanced SR mobile with rich text

SR duplication — Manual recreation — One-click duplication (MAS 9.1)

AI assistance — None — Similar-SR detection on create (MAS 9.1)

<aside>

💡 Key insight: Nothing about what a Service Request is changed — the object, its lifecycle, and its data model are the same. What changed is where you touch it. The Work Center was a place; MAS 9 gives you three purpose-built surfaces instead.

</aside>

🛠️ The Service Request RBA

The Service Request Role-Based Application is the day-to-day replacement for the Work Center. If your intake coordinators lived in the Work Center, this is where they live now.

What it gives you:

  • A modern React.js interface on MAF — the same framework and look-and-feel as Maximo Mobile, so the experience is consistent across desktop and device.
  • A streamlined SR creation workflow designed for speed, not for exhaustive field entry.
  • Attachment support with camera integration on mobile — a photo of the leaking valve attaches straight to the request.
  • Status tracking with visual progress indicators, so a requester can see where their request stands.
  • Rich text descriptions with hyperlinks, so the description field stops being a wall of plain text.

Notice what this is optimized for: fast, high-volume intake. The RBA is deliberately lean. When you need the full power of the Service Request object — every field, every related tab, classification-driven routing, the works — you drop into the classic Service Requests application in Carbon. The two are complementary, not competing: RBA for velocity, classic for depth.

🚫 The Conversion Flow That Didn't Survive

This is the part nobody warns you about, so here it is in bold: you can no longer review a Service Request and convert it to a Work Order in a single role-based screen.

In 7.6, the Work Supervisor Work Center let a supervisor look at an SR and create a WO from it in one continuous flow. That combined flow did not carry forward to any single RBA. It's called out in IBM's own gap documentation, and it catches teams by surprise because the individual pieces all exist — they just don't live on one screen anymore.

"So how do I convert an SR to a WO now?"

You use the classic applications together: review and manage the request in Service Requests, and create the work order in Work Order Tracking, following the create-WO-from-SR action. It works. It's just two applications instead of one Work Center panel.

<aside>

💡 Key insight: This is a design gap, not a defect. Don't burn a week hunting for a hidden RBA button that converts SRs — it isn't there. Design your intake SOP around the classic-apps path, and train your supervisors on it before go-live so upgrade day isn't the first time they meet it.

</aside>

If single-screen conversion is business-critical for you, note that this same gap is why the Approvals RBA (Part 2 of this series) also stops short of SR-to-WO conversion. Both role-based apps intentionally scope to their lane — intake and approval respectively — and leave conversion to the classic pair.

📱 The Service Request Mobile App

The dedicated SR mobile app is where MAS 9 quietly did the most work, and it's the surface your self-service and field submitters will actually use. It grew in two clear releases.

MAS 9.0

  • Rich text formatting with hyperlinks in descriptions — a real description, not a plain-text blob.
  • Attachment renaming with custom file name and description, so "IMG_4821.jpg" becomes "north-pump-seal-leak.jpg."
  • Photo attachment from camera or gallery.
  • Web link opening in the system browser.

MAS 9.1

  • Service Request duplication — one tap to clone a recurring or similar request instead of retyping it.
  • View Service Requests created by other users — visibility beyond your own submissions, for coordinators and teams.
  • Create Service Requests directly from a map interface — tap the location, file the request against it.
  • Self-registration — users can create their own accounts to submit requests, which is the feature that finally makes broad, casual self-service practical without an admin provisioning every requester.

<aside>

💡 Key insight: Self-registration (9.1) is the sleeper feature. It's the difference between "IT files tickets on behalf of everyone" and "anyone on site can raise a request from their phone." If community or tenant self-service is on your roadmap, this is the release that unlocks it.

</aside>

🤖 The One Bit of AI Here

MAS 9.1 adds similar-SR detection: when a user creates a new Service Request, Maximo can surface existing requests that look similar, so duplicates get caught at the source instead of downstream. It's a small, sensible touch — not a generative feature, just pattern matching that keeps your request queue clean.

Don't confuse it with Work Order Intelligence, the watsonx-powered feature that recommends failure codes at work order approval. That's a different mechanism on a different object, and it gets its own treatment in Part 2.

🔧 Practical Notes Before You Roll This Out

  • Keep the classic app in your security groups. The RBA is lean by design; anyone doing full-fidelity SR work (classification, complex routing, SR-to-WO conversion) needs the classic Service Requests application too.
  • Decide your conversion SOP first. Because single-screen conversion is gone, write down the two-app path (Service Requests → Work Order Tracking) and train supervisors on it before upgrade.
  • Gate self-registration deliberately. The 9.1 self-registration capability is powerful; decide who can self-register and what they can see before you enable it in production.
  • Set expectations on the RBA vs. classic split. Intake coordinators will ask "why are there two Service Request screens?" The answer — speed vs. depth — is worth putting in your training deck.

Key Takeaways

  • The Service Request Work Center was removed; the Service Request RBA on MAF is its day-to-day replacement, with the classic Service Requests app (Carbon UI) for full-fidelity work.
  • The SR mobile app gained rich text and attachments in 9.0, and duplication, cross-user visibility, map-based creation, and self-registration in 9.1.
  • Single-screen SR-to-WO conversion did not survive — use the classic Service Requests + Work Order Tracking applications together, and plan your intake SOP around it.
  • MAS 9.1 similar-SR detection trims duplicate requests at creation; it's distinct from Work Order Intelligence at approval (Part 2).

References

Series Navigation

Previous: — Series Index — MAS 9 Work Order Operations

Next: — Part 2 — Work Order Approvals

About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.

Published by TheMaximoGuys | July 2026