Positive

IBM Maximo is one of the best enterprise asset management solutions I have been using. In my organization, we use IBM Maximo Application Suite and its EAM and IT suite to streamline asset management, as well as maintenance and operations activities. IBM Maximo Suite helps to bring the asset lifecycle in front of decision-makers to get the best out of the client investment.

A specific example of how my team uses IBM Maximo in our day-to-day work is that it helps with asset management, facilities management, work requests, and work orders through to end life cycle. Implementing these core modules and components of IBM Maximo has allowed our organization to properly track physical assets and inventory, as well as how they are used to support end-user requests for services and supervisors or technicians picking up those requests and assessing the work to be completed.

The best features IBM Maximo offers are that it is very simple to deploy on OpenShift using Ansible playbooks. It also has excellent support for integration, is simple to configure, and the asset register is very straightforward. Work management and managing inventory are seamless.

In terms of integration support, I have used preventive maintenance, work generation, accurate work execution planning, tracking actuals, and I can easily integrate with other tools and systems.

IBM Maximo Suite gives me a single place where service cycles are standardized and tied to compliance.

IBM Maximo has positively impacted my organization as it has been a very useful tool. It reduced human error by moving away from pen and paper-based scheduling. It saved cost by minimizing unexpected downtime of assets, with approximately 50% of time being saved. We have also reduced overwork among staff by removing redundant information and smoothing task flows. It helps us scale our team without micromanaging small issues.

One way IBM Maximo can be improved is that the interface is not modern or particularly user-friendly. It takes a lot of time to load, especially when dealing with large data.

The interface should be made more intuitive and easy to customize according to user needs.

I have been using IBM Maximo for four years and a few months.

IBM Maximo is very stable; I have not experienced any lagging or load time issues.

IBM Maximo's scalability is very good as it can grow with my organization's needs. However, in terms of large data, it can sometimes load slowly.

The customer support I experience is very responsive and proactive 24/7.

I previously used Microsoft Azure and also Amicron Factura.

I have seen a return on investment as preventive maintenance and compliance tracking have helped streamline asset management and decision-making. We have also reduced overwork among staff by removing redundant information and smoothing task flows. It has helped us to scale our operations team without micromanaging small issues, thereby saving a lot of time.

My experience with pricing, setup cost, and licensing is that the cost was cost-effective and the licensing cost is also reasonable, especially for mid and large enterprises. However, for smaller organizations working on a tight budget, it might exceed their budget and could be considered expensive.

Before choosing IBM Maximo, I evaluated other options including Microsoft Azure.

I highly recommend IBM Maximo Suite because it gives better control over assets without needing multiple tools. It also makes planning and tracking easier and enables data-driven decisions.

I am solving the problem of employees being overworked with a better overview of who is doing what. I find the integration with IBM modules really powerful as it connects everything smoothly. The ability to capture equipment defects quickly and convert them into work orders has been a significant time-saver. I would rate this product an 8 out of 10.

My main use case for IBM Maximo is as a technical consultant, so I help companies to use IBM Maximo.

A quick, specific example of how I've helped a company use IBM Maximo is that it is quite generic, so we help companies to add customization in workflow processes, for example, organization and how to use the asset or location application.

In addition to my main use case, I do install IBM Maximo environment for the clients.

The best features IBM Maximo offers, in my opinion, are agility and the fact that we can customize the application to adapt to the business of the client.

The agility and customization features help my clients specifically. For example, we have a client at the airport of Nice in France who had the need to adapt the mobile application of IBM Maximo, and we were able to do it very fast compared to other solutions.

I have seen specific metrics or outcomes from these improvements. For some clients we have up to 89% downtime reduction of equipment that generates over 1.2 million euro growth in revenue because we don't spend that much money on downtime and repair costs.

IBM Maximo can be improved by providing developers with more documentation. I think IBM lacks a lot of documentation and hopefully the community who uses IBM Maximo can help if other developers have questions, but we really need official documentation because what is available on the internet is not official and we don't have strong documentation from IBM.

I would also note that around usability, we see some lack of real custom needs in the applications of IBM Maximo Mobile. For example, in applications such as inspections, we cannot really sort by specific field and the search or filtering methods are not very clear, making it difficult to easily find what we are looking for.

I have been using IBM Maximo for four to five years.

IBM Maximo is very stable in my experience, as we have zero downtime, especially since we switched to cloud, and we have technical solutions to avoid any downtime in the production environment.

I would say that IBM Maximo's scalability is very good.

The customer support for IBM Maximo is very helpful and they respond very quickly.

On a scale of 1 to 10, I would rate the customer support a nine.

Positive

Previously, we used Carl and we switched to IBM Maximo because we didn't have the possibility to add simply and without a lot of customization our business rules to the previous application. Now we use IBM Maximo because we can add our business logic directly and without really having a lot of cost of development or customization.

My experience with pricing, setup cost, and licensing for IBM Maximo is that the licensing process is very intuitive. We have app points and the users or the clients buy a certain number of app points that suits their business need. For example, if they have a thousand users or thousand concurrent users, they will need to buy around 300 app points.

I have seen a return on investment with IBM Maximo for some clients, where we have saved up to 93% downtime of equipment and 1.2 million euro for one client on return on investment.

Before choosing IBM Maximo, we evaluated other options including Infor and SAP.

IBM Maximo in their last version includes mobility functionalities which can use the offline mode for technicians that do not have internet connection, and that is really helpful for them. Additionally, we can build workflow processes very fast that suit the business rules for the companies.

I would advise others looking into using IBM Maximo to really use only the application that they need. IBM Maximo can be really complicated if we want to use all the functionality of it. However, if we can be small and only use what we need, it is awesome, and if we need more complex scenarios, then we have to teach them to the user before we deploy it.

I would rate this review an overall 8 out of 10.

I am using IBM Maximo for asset management and work management. As part of the asset tracking, the work and maintenance regimes occur on the asset, and as part of that, the asset gets tracked. Asset tracking and predictive maintenance are all part of the standard asset management capability.

Flexibility is one of the key components, along with ease of use. The ease of installation depends on how you set your solution up and whether you're going for Windows or Linux. If you know what you're doing, it's fairly simple. However, if you're a new user to the product, I'd rate it a seven. If you understand the product and you've got your design set up, then it's probably looking at about an eight or nine.

I think there could be a bit more focus on the UI components. IBM Maximo has had the same UI for many years, and it hasn't really changed. From that perspective, the UI is quite old-fashioned, and that would be one of my main concerns. Additionally, some standard processes would be handy. IBM Maximo is very flexible, but it would be beneficial if they had some standard processes that you could adopt quite easily without having to configure everything yourself. Those would be my two key points.

I have been using IBM Maximo for more than five years, probably closer to ten.

The stability depends on and comes down to your setup and your implementation. You're not so much talking about the product itself, but rather your infrastructure and how that's been set up. I would probably rate it an eight or nine.

I do not report directly from IBM Maximo. Instead, I pull the data into the data lake and do the reporting from there.

I have experience with both IBM Maximo, and I am currently in the process of implementing IFS.

IBM Maximo released AI components in their latest version 9.1, so I cannot comment on that at this point in time. The AI components are still brand-spanking-new and have only just been implemented in version 9.1, so there hasn't been much uptake of that at this point in time. My overall review rating for IBM Maximo is an eight out of ten.

I worked with IBM Maximo during an IT consulting engagement for a large asset-intensive organization in the utilities and energy sector, where the client's needs required a centralized platform to manage physical assets, maintenance operations, and work orders across multiple sites. IBM Maximo was implemented to support asset lifecycle management, preventive and corrective maintenance, and integration with ERP and IoT data sources. The solution was deployed in a cloud environment serving multiple operational teams.

I used IBM Maximo asset register as an asset registry and lifecycle tracking. I configured IBM Maximo to create a single, centralized asset registry for critical equipment, such as transformers, pumps, and production machinery, consolidating data previously spread across spreadsheets and legacy systems. Each asset was tracked across its full lifecycle: installation, operation, maintenance history, and decommissioning. IBM Maximo was configured to manage time-based and usage-based preventive maintenance plans where maintenance activities were automatically generated based on operating hours, calendar schedules, and asset criticality, which reduced missed maintenance and improved overall asset reliability.

IBM Maximo provides a very mature and structured model for managing assets, work orders, maintenance plans, and spare parts, which is well-suited for complex real-world operational processes. Another best feature is configurability without heavy customization because many business rules, workflows, and forms can be configured through the platform without writing custom code, which helps align the tool with existing operational processes.

I configured IBM Maximo to integrate with ERP.

IBM Maximo is a very robust and mature EAM platform that covers end-to-end asset and maintenance processes. It is also highly configurable for complex organizations, which was very good for us. It has a strong ecosystem and long-term vendor support because our customer colleagues, when they contacted the vendor for support, had a very positive experience.

IBM Maximo can be improved because the user interface is not as modern as newer SaaS tools, and implementation and configuration can be time-consuming. If IBM wants to improve the tool, I think that these two points are essential.

IBM Maximo can be improved in order to make it easier to understand how to manage and evolve the tool because it is not easy to use at the beginning.

For our needs, IBM Maximo's reporting and analytics capabilities are sufficient. It is a little difficult to use at the beginning, but when you learn how to use the tool overall, IBM Maximo is very strong and useful, and for us, it was a very good experience.

It is not easy to learn IBM Maximo at the beginning. I think that it is possible to improve the learning curve to make it easier to use in the future.

I have been using IBM Maximo since 2024.

IBM Maximo is stable.

IBM Maximo proves to be highly scalable, supporting thousands of assets and users across multiple sites, and it scales well both functionally and technically, especially in enterprise and multi-site environments.

Unplanned downtime decreased by 15 to 20%, work order processing time decreased by 30%, and data consistency across sites significantly improved, which are very good metrics for us.

IBM Maximo is highly scalable because it supports thousands of assets and users across multiple sites without any problems as it scales well.

The customer support for IBM Maximo was very good, but it was not a direct experience. It was a customer experience where colleagues talked with the support team during the development of the solution, and they were very happy about this.

IBM Maximo was the first solution used.

IBM Maximo is deployed in a public cloud.

Our measurable results show that unplanned downtime decreased by a minimum of 15 to 20%, work order processing time decreased by 30%, data consistency across sites significantly improved, and preventive maintenance compliance increased by 20 to 25%.

IBM Maximo was chosen by the customer without evaluating other options.

I would recommend IBM Maximo to asset-intensive enterprises looking for a comprehensive and battle-tested EAM solution, which is a very good solution. I gave this review a rating of 9.