IBM Maximo Reviews

IBM Maximo is used across the organization for purchasing inventory service management.

IBM Maximo has improved our organization because we have been able to reduce printed paper by using the application. We have handheld devices and the information being sent is via email saving us money.

The most valuable features of IBM Maximo are the overall power and interface, and there are a lot of different modules that we use that are helpful. Additionally, it's an integrated solution and it has a lot of capabilities.

IBM Maximo can improve the financial support and financial application, to make it more similar to an ERP as opposed to an EAM. Overall they can improve the financial processes.

I have been using IBM Maximo for approximately 10 years.

IBM Maximo is stable.

The scalability of IBM Maximo is good.

We have approximately 20 users using this solution. The users that use the solution are typically purchasing officers, inventory officers, and managers.

We have plans to increase the usage of IBM Maximo.

The IBM technical support is very good.

I rate the support from IBM Maximo a four out of five.

Positive

We did not use another solution in this category, we only used IBM Maximo.

The initial setup of IBM Maximo is complex to install and set up. It requires expert knowledge. The full implementation took approximately four months.

I rate the initial setup of IBM Maximo a four out of five.

We have a team of two engineers and two support persons that does the implementation of IBM Maximo with the help of the vendor. 

We have not evaluated the ROI of IBM Maximo at this time.

The price of IBM Maximo could reduce, it is expensive.

Upgrading is not covered in the annual support, it is an additional cost.

I rate the price of IBM Maximo a four out of five.

We evaluated other solutions before choosing IBM Maximo, such as Microsoft Dynamics.

My advice to others is they need to have someone who's an expert assist them with the implementation. They cannot do it alone. If they're not familiar with the solution, they need to have an implementation specialist in IBM Maximo.

I rate IBM Maximo a nine out of ten.

I rated the solution a nine because it's easy to use and very powerful. It has a lot of features and capabilities, and it's easy to configure.  

We are using the solution as a computerized maintenance management system, for condition monitoring, and for IoT.

The solution can be deployed on-prem and on the cloud.

The solution helps transform a manual system into an automated system. As part of this process, we are mailing KPIs, and performance indicators, to our team. The quick reports give us a snapshot of how our team is performing.

The most valuable feature is the ability to correct maintenance.

The pricing model of the solution has room for improvement as well as the after-sales support.

I have been using the solution for 15 years.

The solution is stable.

The solution is scalable in terms of license and hardware.

The technical support is good.

Positive

The initial setup is straightforward. I give the setup a ten out of ten.

Initially, we are deploying the web and DB-2, then we have the initial data configuration, the transitional data, setting up the preventive maintenance condition, monitoring parameters, and then comes the report development.

The deployment time depends on the organization's complexity. In medium organizations, it generally takes around five to six months to deploy the time management system using five or six consultants and developers. This time includes the training.

We can see a return on investment with IBM Maximo anywhere between six months to a year.

I give the solution a nine out of ten.

We require two to three people for the maintenance of the solution.

IBM Maximo is a very good solution, particularly for those who want to maintain their facilities.

The main use case is for managing electrical company assets. The solution is deployed on-premise.

It's probably improved by a lot because previously they had a different kind of product. It was okay, but it was based on the old technology and wasn't as centralized as Maximo. Maximo also has connections with external applications.

The most valuable features are the ability to create work orders and preventative maintenance.

Maximo is quite a big product, so maybe we don't even know everything that is possible. I see the presentations of new things to come, and I don't see a concern. Whatever a customer needs is pretty much covered.

I have been using this solution for 8 years. The first week of implementation, it was ControlDesk, but then we started with Maximo also. It's the same.

Maximo is stable. There aren't any system performance issues, but in every organization there has to be some because of integrations with different tools and applications. Maximo doesn't crash, but if it does, it's mostly because of integrations or issues with integrations.

The solution is scalable. Altogether, there are about 3,000 people using the solution.

Right now, the solution is being used extensively, but we are expanding usage. We are expanding the applications that we were using at the beginning. So every time we are working with them, let's say the tickets that come into the ControlDesk, part of them are daily issues and some are quick resolve, but part of them are also changes for processes, implementations, and projects like this. The tool is evolving and the processes are evolving and adding up.

Technical support is from IBM.

Before using Maximo, we used our in-house product. At the time, our customers decided to go onto another platform with different tools, so we had to do the migration.

It's pretty much the same as ControlDesk, but maybe a little bit easier, even though it's a bigger tool. From the installation point of view, it's a little bit simpler.

It's a longer process because Maximo is bigger and has more processes. I think it was a year-long project.

A lot of people are needed for maintenance because it's a bigger solution that has more implementations and a lot of configurations. You need at least 10 people for maintenance. We have more implementations of Maximo, which is why we need so many people. If we had only one implementation, then maybe we would need fewer people.

In the beginning, there was an external company that did pretty much everything, but now it's like a share. We do more than 80% and we just need their support for the harder or difficult types of implementation.

The license structure is quite different here, but now it's changing. We are planning to change the model in January 2022 because IBM has changed the licensing policy. As I understand now, they are going from a complex way of licensing to a more simple way of licensing.

IBM hasn't rebranded, but they changed the licensing policy. There are different types of licenses for different types of users. For the different kinds of models they're using in Maximo, they would need to have a certain type of license. Now they have application points. If you are using this module in Maximo, you need to have three points. If you are using this type of product, you need to have four points. It's more simple.

The company also evaluated SAP.

I would rate this solution 8 out of 10.

It's a good tool for what it was built for. For what it represents and what it gives you, it is a very powerful tool.

I usually sell this solution to customers with equipment that requires asset management and maintenance. Maximo enables them to schedule maintenance reliably and on time. I'm the company co-founder and we are resellers and implementers of various solutions. 

Maximo has a powerful audit combination that helps achieve high accuracy. For example, if I need to buy parts for maintenance, it requires procurement and therefore contact with the supplier. All the information is in the system, and that reduces human error in companies where parts are a crucial element and managing stock and costs is key. Maximo also controls maintenance schedules. The solution also has many valuable APIs that are easy to integrate with SAP, Oracle ERP, Scaler and more. 

The solution has been around for a long time, 20 or 30 years. They have improved the interface but unfortunately, it requires a lot of computing power. All the servers, the desktops, are very stable but they are not sufficiently robust for the graphical interface. The new version of IBM Maximo is a little too fancy. As a result, the system is a little slow because of the lack of power. Simplifying the user interface would make life easier for everyone. They need to find a balance where the solution is updated but performance is not affected

The new UI is great but it means customers not only need to upgrade to the new version but also upgrade older laptops and that's not what they want. If they would offer two versions, one with a simplified interface, that would be helpful. 

I've been using this solution for two years. 

The solution is stable. 

The solution is scalable. 

I'm lucky because I worked at IBM so I had some background knowledge before starting here. As a reseller, I think the IBM website resources are good enough. But if you have less experience then you may find the support to be lacking. It's not as good as it used to be. 

The initial setup is reasonable - not too simple and not too complex. 

I think the price is generally competitive but sometimes you have to consider the exchange rate because it's an American product and you have to consider the exchange rate. The cloud version is more expensive. 

Most of the competitors here in Taiwan use an SAP EAM module. Maximo also competes with some local brands like Advantag or MiTek. It integrates with almost every kind of ERP but it's difficult to integrate with the local ERP. If a customer is already using SAP, that's a challenge for IBM Maximo. But on the other hand, because of the APIs, we can easily integrate with other MES systems. Other solutions are more vendor-centric, and more easily integrate with products from the same vendor. IBM Maximo has better variety in regards to integration and it can be integrated with other ERPs as well.

It's a pretty good product and I rate it nine out of 10. 

In one a period of one year, we receive lots of work orders. There were lots of paperwork by end of the year. With IBM Maximo we are able to have everything on the computer. If we want to see what kind of service we have done on our assets we only need to go to the Maximo and we can see all the history in front of us. Earlier, everything was on paper, and it was too hard to find out what kind of services and what we did in the past.

We were doing all kinds of paperwork for every type of order and to maintain our assets but with the use of the IBM Maximo application, we can automate a lot of the processes.

IBM Maximo is a large piece of software that has lots of functionality. I have not even used it to its full potential.

I have used IBM Maximo within the last 12 months.

The solution is not stable. We can have one day when it is stable and another day it is not. Sometimes it crashes or becomes very slow, and there are times we are not even able to download all the databases. Without the database, we cannot work on that application. These are the small glitches, and stability issues we are facing.

The solution is easy to scale, I did not find it not very difficult.

There will be 1,500 people using this solution.

The implementation process is complex. The region has implemented one solution to all nine divisions. It was a global solution to all their problems. When integrating all the legacy systems with IBM Maximo is when the complexity began.

We started the implementation process in 2013 and we are in 2021, it has taken us eight years for the whole process. Next week we are going live and next year we are going to be deploying the project.

The implementation was done by a large team. There are a few stakeholders and users working with us, approximately, nine divisions. We have approximately 20 people from those nine different divisions and our team is another 30 people. Additionally, there are the third-party legacy system team and different directors from different stakeholders. There is a large number of people involved.

The maintenance team will include less than ten individuals and will be assembled soon.

I do not know about the price of the solution. However, this has been an expensive project overall.

We are planning on receiving an extended or advanced version of IBM Maximo.

It's a nice product and I think it is going to add a lot of value to the region because now they can see all the history. Moreover, they're going to get an automated process.

I recommend IBM Maximo to others.

I rate IBM Maximo a seven out of ten. However, I have never worked on any of the competitive products of IBM Maximo.

The main use is help desk. But we also use it for asset management, catalog offering, and CNDB.

It's much more reliable, it's much more configurable.

It's reliable, and it's all integrated in the same database.

It's actually a little too much for what we need. It could be good but there are too many conflicts and it's not user-friendly. It could use shortcuts for frequently requested services.

Other areas for improvement include:

• Enhanced Service Catalog on Mobile
• Agent intelligence
• Better dashboards for KPIs
• Full-service visibility - There are a lot of things that are hard for users to find out. For example, the Service Catalog is not too friendly. You really have to know what you're looking for.

It's quite reliable, but new versions often are not too stable. They bring in enhancements but they break other stuff. We're okay with it but it could be better.

Scalability is very good. It's easily scalable.

We have often set up PMRs and their support is quite good. We have issues that have reappeared in other releases, and things that aren't really supposed to be happening like that. We migrated to a different version, one thing was solved but then a new issue appeared, related to the same module. 

They give good service, but they could be a little more reliable in terms of solving defects and having it work as it should.

We used an old Lotus Notes solution that we implemented ourselves and then we migrated to Maximo. Now, our main client doesn't really like the way Maximo works, at least for them. So that's making us into a new solution.

In terms of selecting a vendor, I don't do the selection. I just evaluate the functional and technical aspects. Regarding pricing and things like that, I'm not the one that will decide. My main concern is that it does what it's supposed to do, does it well, and that the client likes it.

The initial setup was complex but that was 10 years ago. It might have changed since then.

The options we are now considering are JIRA and ServiceNow.

They have a preview site where you can log in as a user and try it for yourself. That is a really good way to get a feel for the solution; better than Youtube or whitepapers and things like that. You have a preview site, you log in, and you can try it.

I would give Maximo a seven out of 10 because it's good, but it's not too user-friendly, and some of the issues we have come across, the impact to us was a little too much to be coming from a big company such as IBM.

This is a broad tool with many functionalities (i.e. tracking, enterprise asset management, etc.). I am looking at it from a government contractor's point of view allowing them to become compliant with the CMM. This is a standard based on the NIST 800-171, which is about protecting sensitive information.

We were able to sell their software to track the daily maintenance of space shuttles.

They have a real strength of tracking the asset itself along with the condition of the asset, the maintenance of the asset and who has access to the asset, etc. 

It could use some alignment regarding some standards and the tracking of the IT assets. Even though they have all of the information (i.e. where are the assets, who owns the asset, etc.), they were not mapping it to different cyber standards.

I have been using this solution for nearly twenty years.

From my experience it is very stable.

The solution is scalable.

I did not utilize their support.

Setup is as easy as possible for this complex system, it really depends on
what level of fidelity you want to have it. For example, we put the system in to track the maintenance of US space shuttles. Here, we were tracking anybody that touched it, or anybody that was near it in addition to the condition of any level of detail, of any part of that asset in the supply chain.

Level of maintenance required varies by project size.

Pricing is competitive.

Find people that know how to use it and have experience with it. Learn how to integrate other products, other third-party applications into it. Like any other product, you want to find people that have experience using it and know how to push it beyond what they do. There are all kinds of add-ons to it.

I would rate this an eight out of ten.

We are using IBM Maximo as a service desk. It is primarily used for incident management but also covers service request management, asset management, and other areas.

The most powerful features are the database and integration with CMDB.

The interface is not very easy or user-friendly and is in need of improvement.

Compared to products like ServiceNow or Jira, it is very difficult to customize Maximo. For example, a layperson is able to customize ServiceNow or Jira to a certain degree, but that is not possible with IBM Maximo. The customizations are code-based and it requires a programmer to do the work.

The licensing model should be much simpler for an organization like us to add more end-users. As it is now, we have to keep looking back at the available licenses.

Maximo has been in use for more than a decade in our company.

This is a stable product.

The scalability is quite good. We have between 2,000 and 3,000 users in the company. Most of them are end-users, although there are a few administrators who can make changes.

The support is not bad because we have a local support team that is available around the clock. We have a local support contract with one of the service providers that offers complete support for a variety of products.

For cases that the local team is not able to handle, we can open up a ticket with the IBM product team and they respond accordingly. Ultimately, in any case, the support is fine.

The company has been using IBM Maximo since before I joined. My understanding is that they were using solutions by HP, including HP Service Desk. However, I do not know the specific reasons for the switch. All I have been told is that HP was more expensive at the time, but there could be other factors involved.

The initial setup is quite complex and it takes a long time. In particular, in our environment, we are using it quite extensively for event and incident management. These are core areas for us and it is a bit complex.

We are considering moving away from IBM Maximo to Jira. We have evaluated both Jira and ServiceNow, and the interfaces are GUI-based, making them easier to use and easier to customize. In general, they are much easier to change and adapt to the end-user requirements.

I would rate this solution a six out of ten.