IBM Maximo Reviews

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.

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. 

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.  

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.

Our clients use it for various use cases, but most of them are around either service activation or asset management.

A lot of our clients use or have used, or are part of businesses that have used Maximo for over an average of around 15 to 20 years.

It's the big capital assets that are managed by the software. A lot of it is in the oil and gas utilities, however, it is also in more service-orientated organizations such as airports, et cetera.

There are not many enterprise asset management systems on the market and not many that have the categories that IBM Maximo has. It's a platform that has been here for about 30 years. Currently, the shift to having the ability for customers within the space to move from a legacy structure into a more modern microservice structure that's on the cloud is quite valuable. It gives clients a good journey map to a modern hybrid cloud infrastructure or a little more cloud infrastructure.

The solution is expensive and is quite difficult within this space. There's a lot of non-enterprise level asset management systems out there are able that are less expensive.  We're doing it for a hundred dollars per user, per month. With IBM Maximo and especially now Application Suite, that's a bit more difficult as it's grown beyond just asset management. It's now more of an asset performance management system. It's fallen a bit into a different category and has the ability for users to utilize more modern machine learning algorithms, AI-based algorithms on their asset data. From a pricing structured perspective, the list prices are out there. However, if you find the right integrator, then the list prices go down quite a bit.

I've got a pretty good view of the roadmap for the next three years. For us, it looks really exciting. It took IBM a while to get their act together and to merge the new paradigm from Kubernetes, et cetera. There were deployment methods in their Maximo roadmap. From what I can see things like visual inspection, machine learning-based image recognition, et cetera, are all quite exciting spaces and it's quite leading edge. We went a bit from being a glorified works management system, with a lot of capabilities, however, it was quite legacy orientated as in, based on older technology.

I'm in a technology that has been around for 20 years. We're now moving into a stage where it's more bleeding edge. Using all the passwords is now applicable. It's quite a transformation that's happening now. I couldn't really say that I'm missing this or that. The only thing I'd say, and this is coming from a technical person, is that I hope that the change management needed to modify the system is better suited to the customer's needs. It's not allowing us to use the development pipelines and things like that.

The stability is very dependent on your integrator. They can mess things up. We have actually quite a good track record on our managed instances. The one that has been up the longest is eight months or something and has been running without any issue. Basically, it is very stable if it is administered properly.

We run anything from two users to 6,000 users. One of the benefits is that it's very scalable.

We do anything from a small to medium-sized business to global mobiles. The largest logistics company is one of our clients. The largest facilities management company in the world is one of our clients. So is the biggest power plant in the UK. It can work for a managed building around the corner to something with a worldwide reach.

Clients do plan to increase usage. That mostly comes with the new capabilities that are now emerging in the new versions of the product. The use cases are shifting from the asset management system to be an asset performance management system.

IBM is a big company and they have a lot of products. Level One, the first level of tech support, is the one that is used to stop the tsunami. For everyone, it's always a bit of work to get past that. After you do, they're excellent.

That's primarily due to IBM itself as they do so much and they have so many products that the first level at these big companies can be difficult to move up from. We have the same issue with Microsoft, for instance.

We actually switched over quite a few customers from the more niche Focus Asset Management systems. They seem to be disappearing a bit as well as, for example, SAP, which I personally can't really say why as I'm a bit biased.

I'd say it either fits really well for those customers, whatever they're using now, or they are looking for a more APM-focused suite and there's not that many out there really.

For the average user, IBM Maximo comes in a few flavors. The first one is SAS, in which everything is installed for you. That's really simple. You can get it all from IBM's website or from an integrator like us. Then, there's the flash structure where it's more platform as a service. That gives you more ability to modify. Then, you have the infrastructure at the service site, which gets complex. At the same time, I'd say that's the point where usually businesses come to a business like us to actually deal with it.

You can't compare Maximo software, or SAP software or Zendesk, as in, I get a subscription to Zendesk and it runs. Of course, when the processes are supported by Zendesk, you can't really compare it to maintaining a capital asset. Software like SAP Access Management or Maximo gets placed right next to Joe Fix It. However, it's a different ballpark product. Maximo will probably be an expensive solution for a lot of companies. For other companies. They actually use that additional capability. In that case, it's not that expensive.

On average, our clients are up and running within days. That's including their business process integrated into the system. That's a custom deployment. We do it usually with one or two personnel.

Even if we don't look at the full software and we look at smaller use cases within the software, the ROI is often quite substantial. It is driven, of course, however, it's quite easy. A lot of these businesses have fairly inefficient processes. If they're coming from ten people that have their own Excel and you go to a unified system, it is quite easy to make big steps on the road.

It saves a lot of time and resources. Just to give you an example, on our recent project, we were able to reduce their accounts payable staff by 50%. Those people still work there, however, they're in other things. It illustrates what we were able to do. 

You have the licensing fee and then you have a yearly service subscription with IBM. That gives you access to the newest version of the software and support services. There's no additional cost to that.

We're a system integrator. We use IBM Maximo every day and we implement it as well.

Whether it's hosted on cloud or on-premises depends on the client. We host it within our own staff host service and we also have on-premise clients. The larger clients often are on-premise.

I'd advise potential new users to get a good integrator. I don't say, come to us, however, get a good integrator that works as a partner. Within this segment, one of the things that people often get wrong is that they think they only need to integrate it for the implementation project. However, get a good integrator that works as a partner and keeps focused on your business needs. 

Often we see integrators that are only focused on getting the project done, getting it signed off, and getting their bills paid and they don't really care about what they leave behind and neither does the customer themselves. Everyone is just trying to get their project done.
That's where enterprise software fails in general. That type of implementation will cost you a lot of money.

I'd rate the solution at a nine out of ten.

I use IBM Maximo for work and asset management.

IBM Maximo has increased our efficiency by 65%.

I have found Work Order management the most valuable feature. Additionally, it is a very robust and powerful solution.

This solution could improve by integrating or embedding finances, charts of accounts, and invoicing.

I have been using IBM Maximo for approximately 20 years.

IBM Maximo is stable.

The scalability of IBM Maximo is easy.

We have approximately 2,000 administrators and supervisors using this solution.

We are extensively using this solution, it is across our whole company.

The technical support is excellent. IBM provides very good support.

I have used solutions previously. However, this solution has many more features.

The initial setup is sometimes complex and other times not. IBM Maximo requires deep knowledge of the product and the platform to do the configuration. It's not straightforward for somebody who is not knowledgeable in IT.

The deployment can take three to six months.

We have approximately five developers, administrators, reporters, and integrators that support this solution.

Within three years you can recover the costs of this solution.

I rate IBM Maximo an eight out of ten.

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.

We developed our own manufacturing distribution system and management system. We also have experience with AI and machine learning. So, you can imagine, as a company with a manufacturing distribution system and with an asset management system in place, we are very thankful to have IBM integrated with our own Legacy, cloud-based system. We have big customers around the world and we integrate them with many solutions, including IBM Maximo.

We mostly integrate with anything manufacturing related, but we also work closely within administration and banking. So, we have to know these solutions, inside and out, in order to properly integrate them and keep our customers satisfied.

We use IBM Maximo to enhance an asset's lifecycle in an attempt to get the most out of it, but of course, it depends on what you're doing. If you run a bank, you're going to want to maintain certain assets. If you have an inductive environment, then your main assets will often be your greatest concern. So, it all depends on what you're going to use it for, but, at the end of the day, our primary use case is to enhance the lifecycle of the asset we're using. 

By enhancing an asset's lifecycle, you're maintaining the term and reducing costs. You can control your work team, but you can't control their skill level; everything that is good revolves around the lifecycle of an element, even if we're talking in terms relating directly to economic gains.

IBM Maximo is similar to an ARP. Because it's so massive, you can easily get lost using the application. You need to focus on training the partners and channeling the structure in order to enhance the user experience for the final customers. Deploying IBM Maximo can be really exhausting because, as I mentioned earlier, it's as big as an ARP.

Most of the time, the people working in those environments (even if they don't know how to read data, etc) are trained to focus on maintaining elements and solutions. You cannot give them 25,000 screens with 25 teams and expect them to do everything, even if that would give you plenty of information for further analysis. We're talking about the best asset management solution in the world, so this needs to be taken into practice somehow.

I think the biggest problem is that the application is too big. The solution has plenty of different capabilities, but a lot of the time their partners are not capable enough when it comes to deploying it for their customers; they'll simply just deduce the best they need to. In terms of size, Maximo is a beast, a monster, it's not IBM's fault, I have nothing bad to say about them.

However, there are a few problems that are IBM's fault, but not directly their fault as the solutions are not deployed directly by IBM, they're deployed by the public network. In the end, the partners are the ones working with the final customer, the final customer is the one who inherits that lack of user experience. I think it's more of the partner's fault than IBM's.

Being able to talk to people and understand what they need and adapt their solution in terms of what they need would enhance IBM Maximo. Integrating software, such as Cortana and Google Now would also make the solution more intelligent and easy-to-use. I would also like to see an option to integrate with a new generation architectural modeling solution of your choice, as that would be a good way to enhance the personal experience. People today, are accustomed to seeing graphs and details, so that would go directly to the final user base — directly to the customer. 

In regards to the difficulty of use, I think it would be beneficial to have a lightweight solution for smaller companies. Also, better material capabilities relating to prediction would be a good adjustment, because currently, Maximo controls both the corrective maintenance and preventative maintenance; they even control configuration-based maintenance with integration with larger systems, and management systems as well, but maybe they could even go further. The cloud could solve that issue, including any capability issues as well. To be clear, it's already included, but it should be integrated. 

I have been using this solution since the creation of our company, even before the product was called IBM Maximo. We were familiar with it before IBM even purchased it. It was developed by another company, but currently, it's IBM's solution and they have been developing it for the past 25 years. So, we have been using this solution for at least 25 years. 

In regards to the cloud, I believe there are some scalability issues, but I am not certain. In the end, you're paying for a private or public cloud, so most of the time the problems could be solved with more CPUs, more ram, more space, better connections, better vacancy, and so on. Again, it's not IBM's fault, this is just something that happens when you have a large application. 

Eventually, those applications will form a need for everything: for communication, processing, moving, and to retire. So, there could be an issue there, but I am no certain. I don't have separate photographs in front of me depicting 300, 3,000 and 10,000 people using it so that I can evaluate the real output of the consumption and sources.

On a scale of one to ten, I would give IBM Maximo an eight.