IBM Maximo Reviews

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.

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.

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 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.

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. 

When we integrated the Maximo DB with the BI tool, we were able to track and manage the inventory levels in much more controllable way, and reduced the inventory levels significantly within one year.

• Preventive maintenance management
• Maintenance management

1. Inventory management, especially:

• item cards – I need to be able to track item balance and history back to a given date
• inventory financial reports need a lot of enhancement
• consignment stock management has an issue – raised with the vendor
• reorder process and define reorder levels
• inventory lead time recommendation, according to transaction history

2. Purchasing management

• Vendor management needs enhancement

3. Maintenance KPIs like OOE , Mean Time Between Failures (MTBF), Mean Time To Repair (MTTR) need more enhancement

4. Operating budget management (recently added in version 7.6 ) but it is late in coming.

Sometimes I have had issues with with the web server which we use (IBM WebSphere) but we solved it.

No issues, this software is very efficient regarding scalability.

I would give it an eight out of 10.

The data gathering and data engineering were complex, but once they are done the remaining steps were straightforward.

The concurrent user license is much more effective in management and cost-wise, as it is more suitable for maintenance management.

I was not involved in this process at my current company.

1. Defining your business processes is vital for the success of this product.
2. End-user training should be implemented according to your processes.
3. Using Agile methodology fits well with this product, to ensure fast response to business changes.

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.

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.