When you try to modernize Maximo for IT, you might run into roadblocks that have nothing to do with the tech itself. Most of the time, the real culprit is history. Old design choices made for a different era are still hanging around — a form of data drift baked into the architecture itself — even though they stopped making sense a long time ago.
Maximo has lived through three eras, each with its own set of rules.
Back in the day, Maximo handled IT Service Management (ITSM) right out of the box. Then IBM split those features off into IBM Control Desk, which came with its own rules, licenses, and workflows. Now, with MAS, everything is back together again on one platform with a single architecture and AppPoints licensing.
If you bring your old Control Desk workflows into MAS, you might hit some bumps. Those workflows were built for a world where IT and asset management were separate — but that split is gone. Plus, with AppPoints, every IT workflow decision now impacts your platform usage and costs in ways Control Desk never did.
The best place to start? Figure out which era shaped your Maximo setup. That way, you can modernize with your eyes wide open — and build the data governance and work management consistency that the new platform model actually requires.
Additional guidance and technical insights are available throughout the Maven Insights library.