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.

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.

I am a consultant. I make use of everything. I was a consultant, and I worked for a variety of companies who were asking for different things to be done, and I did everything, for them. I can't say that there is something, that I didn't do. I was also traveling to the US, and working for IBM in the US.

IBM Maximo is the best software for assets management.

There are always ways to improve and make things better. It is what I've grown accustomed to. I am taking advantage of everything Maximo has to offer. I'm making use of whatever I can, and if I need to do anything else, I write a custom code.

Every company has specific needs, and you can't generalize for everyone. That is how my work is. I'm working specifically for the company, and when they require something else in addition, that is when I do the customization. Sometimes it could be a Java class, other times it could be an automation script, and it could be just the configuration, it just depends.

My experience with IBM Maximo has been since 2004. I have been familiar with this solution for approximately 17 years.

I always work with the latest version of this solution, as well as WebSphere.

IBM Maximo is the most stable solution that I have ever seen.

I didn't have to deal with technical support. As a consultant, what I was doing was notifying the user that I was working for, sending the description, what log files and description I was sending, and giving them. They were also dealing with technical support. I don't believe they ever had a problem with IBM's technical support.

Everything was fine, but as I was gathering information and delivering it to them. I would always advise them and say, "Okay, this is not something for the first and second levels. It is the third level. You must proceed to the third level, to some developer, and inform him that something is wrong." And, in most cases, they return to resolve the problem. I actually had a conversation with IBM US tech support once. At the time, I was working for an American company with a Canadian office. And, yes, it was fantastic.

I'm mostly using WebSphere. I also use Web Logic at times. I can set up Web Logic for Maximo. It's the same for me. I always use the advanced configuration.

Maximo is an application, and if you want to have it on the web, you need to run it through a web server. WebSphere is a web server, and also an IBM product.

When you purchase Maximo, you get WebSphere for free.

In terms of the initial setup, I have seen some other guys, and what they're doing is not straightforward for them, but everything is straightforward for me. I know exactly, what I am doing.

Everything you need can be found in IBM's documentation on their website.

I didn't get involved with the pricing. I don't know the prices, or how it works. I know how to use licenses in Maximo and check the licenses to ensure that we have not gone over, but I did this for every company for which I worked. 

IBM Maximo offers a licensing application, and you have to comply with the license. Otherwise, I have no idea about prices or anything else. I'm not sure how much it costs. I'm not the one looking for prices. I know the software is good, and when something is good, I believe you should pay what it costs.

I would rate IBM Maximo a ten 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.

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. 

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.

The most valuable feature is asset management maintenance as well as asset management overall.

Areas for improvement would be the user interface and support for Arabic. They could also be more customer-oriented.

I've been using this solution for four months.

This solution is stable, we have had no problems with it.

The initial setup is straightforward. Deployment took between nine and twelve months to complete.

The on-premise license does not need to be renewed, only the EMC, which is 5-8% on the contract value.

This is a really good enterprise solution but check before implementing if you require a solution of this size. I would give this solution a score of nine out of ten.

Our primary use is logging our help desk requests. It is essential for incident management and request management.

The incident management feature is good because it allows you to keep track of and classify issues. 

I feel that the interface is a little too complicated with a large number of fields to enter. People don't want to enter a lot of information. Rather, they would like to enter the minimum amount of information required to get the work done. Making it more user-friendly may help in this regard.

I have been using IBM Maximo for about two years.

I feel that it is a stable solution.

I have not looked into scalability. Our network team would evaluate scalability if it became an issue. About 60 people are supposed to be using it, although because of the large amount of data entry, I think that many people are just not completing the task.

I have not been in contact with technical support.

I have been looking at Azure as a comparison and I feel that it is a little bit simpler to use.

My advice for anybody who is considering Maximo is that it is very comprehensive, provided you like to fill in a lot of information. It collects a lot of data and a lot of analysis can be done. However, in our experience, we find that people don't want to do it. If they are grouping jobs then they don't want to enter a lot of information. In this case, entering the minimum is better.

This is the biggest problem that we are facing. There is a lot of work to do and following all of the processes and procedures is time-consuming because of the data entry. 

I would rate this solution a five out of ten.