IBM Maximo Reviews

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.

It can be particularly useful for power line operations, enabling linemen in the field to gather information and send it across the country as well as different parts of the world.

With IBM Maximo, we were able to input the pole information for different poles and lighting, not only for us as power technologists to know what needed to be placed on a pole but also for the linemen in the field. It provided an easy way to share information with them, ensuring they were aware of our actions. Likewise, we could understand their activities and use of different tools.

Though I liked it a lot, I think it was lagging a lot. It was very slow due to the lagging issues. So that was kind of frustrating, considering how slow it was while functioning. The aforementioned area can be considered for improvement.

Particularly related to compliance management, Maximo has been configured to provide a warning of compliance activities coming up and enables us to report on exceptions.

Maximo is a platform where apps can be created to support special processes. It is configurable, where you can add extra fields to screens and to the database.  

With that said, our biggest use of Maximo focuses on work and compliance management, and we have configured Maximo to help us manage our compliance activities. In addition, some pockets of the company utilize Maximo for managing work, failures, inventory, etc. beyond just compliance.

We have fully used Maximo for maintenance and inventory and purchasing management to manage cement factory operations and maintenance for more than 11 years. We have implemented Maximo at seven sites and are still adding sites. All our sites are hosted in one environment using multi-organization and multi-site configurations. We integrate Maximo with a financial system (Navision), and we built dashboards on top of the Maximo database using its business intelligence tool. We have upgraded Maximo twice: once from 6.4 to 7.5, and more recently, from 7.5 to 7.6.

It keeps the history of the transactions, so we can anticipate the asset behavior and costs in the future. It enables management to be able to tape the session.

Maximo has been suitable for businesses as it expands and shrinks according to market needs and operational conditions.

The solution is used for a variety of industries like manufacturing, pharmaceuticals, and transportation.

Work management, optimization, and maintenance indicators are some of the valuable features of the solution.

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. 

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

We are a telco provider in Pakistan with a customer base of around 75 million. We use this solution for incident management, port management, and problem management across various functions. We use it for process digitization across different areas, mainly within our technology but also outside. We are IBM customers and I'm a system admin. 

The most valuable aspect is the level of flexibility Maximo provides because it is more code-based and more Java-based, so our development team and support partners are able to customize and relatively easily tailor it to our needs.