IBM Maximo Application Suite (BYOL)

What do you like best about the product?

What I like best about IBM Maximo Application Suite is how effectively it centralizes asset management, maintenance operations, and operational visibility into a single platform. Before implementing it, our teams were managing maintenance schedules, asset records, and incident tracking across multiple disconnected systems, which created delays and inconsistent reporting.

One of the biggest advantages for us has been predictive maintenance capabilities. The platform helped us move from a mostly reactive maintenance process to a more proactive approach by identifying potential equipment issues earlier through monitoring and analytics.

We also found the work order management and asset tracking features extremely valuable for improving operational efficiency. Maintenance teams now have better visibility into equipment history, service schedules, and downtime trends, which has reduced manual coordination significantly.

Another strong point is scalability. We manage operations across multiple facilities, and Maximo made it easier to standardize maintenance workflows and reporting without losing flexibility for different operational requirements.

Overall, Maximo helped improve asset reliability, reduce unplanned downtime, and give operations teams much better visibility into maintenance performance across the organization.

What do you dislike about the product?

One of the main challenges with IBM Maximo Application Suite is the overall complexity of implementation and customization. The platform is extremely feature-rich, but that also means onboarding can take significant time and planning, especially for organizations with large or highly customized operational environments.

We experienced a fairly steep learning curve during the initial rollout, particularly for teams that were newer to enterprise asset management systems. Some workflows and configuration settings required specialized expertise to fully optimize.

Another area that could improve is the user interface experience. While the functionality is strong, certain modules can feel less intuitive compared to newer cloud-native platforms, especially for non-technical users or field teams who primarily need quick access to work orders and maintenance updates.

Performance was generally stable, but we did notice that large deployments with complex integrations sometimes required additional tuning and infrastructure planning to maintain responsiveness.


That said, once the environment was fully configured and teams became familiar with the workflows, the platform delivered strong operational value. Most of the limitations we encountered were related more to implementation complexity and usability than the core asset management capabilities themselves.

What problems is the product solving and how is that benefiting you?

IBM Maximo Application Suite helped us solve several operational challenges related to asset maintenance, downtime tracking, and fragmented maintenance workflows across multiple facilities. Before implementation, our maintenance teams were relying on disconnected spreadsheets, manual reporting, and separate tracking systems, which made it difficult to maintain consistent visibility into asset performance.

One of the biggest problems was unplanned equipment downtime. Maintenance activities were mostly reactive, so issues were often identified only after equipment failures had already impacted operations. With Maximo, we were able to move toward a more preventive and predictive maintenance approach using centralized monitoring and maintenance scheduling.

The platform also improved work order management significantly. Earlier, tracking maintenance requests, approvals, technician assignments, and service history required a lot of manual coordination. Now, teams can manage everything from a centralized system with much better visibility and accountability.

Finally, Maximo helped reduce operational disruptions, improve maintenance efficiency, increase asset reliability, and give our operations teams more data-driven visibility into overall facility performance.

What do you like best about the product?

It is a very clear cut application. Training on it was is easy and even if you don't know every single function, it is self explanatory in a way that you can almost always figure it out.

What do you dislike about the product?

Maximo experiences issues and outages at random times that can keep me from doing my job.

What problems is the product solving and how is that benefiting you?

It makes processing purchase orders for our company a pretty streamlined process. it allows us to view information about a purchase order and make updates very easily.

What do you like best about the product?

What I like most is the depth of asset management it delivers right out of the box. The hierarchical asset structure, work order management, and PM scheduling feel mature, and they handle complex industrial environments that lighter CMMS tools simply can’t.

I also appreciate how flexible the data model is—you can configure almost anything through the Application Designer without touching code, which is rare for a platform at this scale. Reporting through BIRT and the REST APIs are also solid, especially for integration with ERP and IoT systems.

What do you dislike about the product?

OOB isn’t very user-friendly and feels quite complex to use. Getting started seems to require a lot of data integration, which makes the initial setup difficult for typical users.

What problems is the product solving and how is that benefiting you?

As an integrator I saw maximo giving a very scalable CMMS, adaptative to the needs easily and giving satisfaction as a solid piece of software.

What do you like best about the product?

I like using IBM Maximo Application Suite for its advanced features that help manage asset inventory effectively. I appreciate the new products and add-ons like monitoring, predicting, and health assessment tools, which are particularly useful for visual inspections and reviewing the condition of assets. It has features that predict asset failures and downtimes in advance, which is incredibly helpful. I also find the health score feature beneficial for knowing the status of assets, helping clients decide if they need to decommission assets or purchase new ones. Overall, IBM Maximo is very reliable and suitable for large-scale operations, providing tools like maintenance planners. I rate it as good and dependable for users.

What do you dislike about the product?

The installation process for IBM Maximo Application Suite is a bit lengthy and could be faster. You have to install clusters in Red Hat OpenShift and then go through Ansible Playbooks to install different components. Once that's done, you install applications, add-ons, and everything related to Maximo. This makes it time-consuming. Also, the tuning of databases attached to the managers becomes slow as days pass by due to the large volume of queries, which requires frequent tuning. This is something I feel can be improved.

What problems is the product solving and how is that benefiting you?

I find IBM Maximo Application Suite solves inventory and procurement problems while managing assets effectively. It includes features like monitoring, predicting failures, and assessing asset health, providing crucial insights for maintenance and decision-making.

What do you like best about the product?

UI/UX*
The modern Maximo Application Suite interface is cleaner and more web‑friendly than older Maximo versions, with better dashboards and navigation. Still, it can feel complex for new users due to the breadth of functionality and configuration options. It’s designed more for power users and technical teams than for casual, “click-and-go” users.

Integrations*
Integration is one of Maximo’s strengths. It offers robust, supports common enterprise integration patterns, and connects well with ERP, EAM, IoT platforms, and OT systems. However, achieving deeper or customized integrations typically requires skilled implementation partners or in‑house expertise.

Performance*
When properly sized and configured, performance is generally strong and scalable for large organizations with many assets and users. That said, complex configurations, heavy customizations, and large data volumes can impact responsiveness, so tuning and good architecture are important.

Pricing & ROI*
Licensing and implementation costs are high compared to lighter EAM/CMMS solutions, making it most suitable for medium‑to‑large enterprises. The ROI can be very attractive in asset‑intensive industries (utilities, manufacturing, oil & gas, transportation) thanks to improved reliability, reduced downtime, and optimized maintenance strategies, but this is contingent on a solid deployment and adoption strategy.

Support & Onboarding*
IBM and its partner ecosystem offer extensive documentation, training, and professional services. Onboarding is not trivial: organizations usually need structured rollout, change management, and formal training to fully exploit the suite. Ongoing support is generally good, but navigating IBM’s support structure can be complex for smaller teams.

AI & Intelligence*
The suite increasingly leverages AI for predictive maintenance, anomaly detection, and insights based on sensor and historical data (e.g., failure prediction, condition‑based maintenance, work prioritization). These capabilities are a major differentiator, but they rely heavily on data quality, integration with IoT/OT sources, and proper configuration.

Overall*
IBM Maximo Application Suite is a strong choice for large, asset‑intensive organizations seeking deep functionality, strong integrations and advanced AI‑driven maintenance capabilities. It is less suitable for companies that want a simple, low‑cost, plug‑and‑play maintenance system.

What do you dislike about the product?

When you want to configure and customize the program there are specialized skills required. There are still a lot of clicks necessary to do certain things, sometimes you have the feeling that this can be reduced. Network is also an issue, when the network is not working fast enough you will see a lot of loading circles.

What problems is the product solving and how is that benefiting you?

It is helping us manage the maintenance within the organization, with workorder/ po management and procurement orders.