IBM Maximo Reviews

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.

We are able to organize, track, and report on all of the jobs/tasks/routine work/preventive maintenance that we perform daily, and report to management the status of these activities at any time.

The large range of configurability of the product is great, since everyone has a different way of doing things. I also like the interface mechanisms built into the tool. With these, we can talk to just about any external system.

Revision management of file attachments.

The product is very stable (when configured properly).

The product scales very very well.

Seven out of 10. There are lots of consultants and third-party developers that can help with this product. IBM is not the only choice.

(By the way, in my opinion nothing is perfect).

We used a home-grown solution. We wanted to take advantage of advances in technology without having to build out or enhance our home-grown solution, so we switched.

This depends the ROI you expect. I recommend you implement the most important functions and then add capabilities as you get more familiar with the product.

Explore the possibility of using DB2. You will avoid the cost of SQL Server or Oracle licenses.

MP2, SAP.

There are add-ons for calibration, scheduler, transportation, service provider, government, oil and gas, asset management configuration, and linear assets.

It is a very solid J2EE product with great middleware and webserver; scales very well, and can use one of three RDBMS systems.

Refine your maintenance processes, do not skimp on hardware.

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

It is a software specialized in asset management, but nowadays, it is more than this.

With Maximo, we can manage, organize, and track incidents, claims, jobs, tasks, preventive and corrective maintenance, locations, and assets. Also, we can correlate all these items in order to obtain reports, such as how many incidents per locations, when was the last preventive maintenance in a location, who was the technician that did the job, or what was the spare part that he used, etc.

The main feature of Maximo is the capabilities of recording, tracking, and correlating. These are important items in the management of a company. These capabilities let us organize our work.

The mobile solution has a lot of room for improvement, especially in geopositioning capabilities, tracking capabilities, and configuration capabilities, in order to let the tech operate online and offline.

Maximo is very stable. We really do not have problem with stability.

We were able to scale perfectly.

Technical support is a seven on scale of one to 10.

We did not have a previous solution.

Maximo is a big system, so the initial setup is complex. I would recommend that you implement it in parts according with your most important processes.

Explore internal processes in order to evaluate the correct number of users in each Maximo module, then evaluate the different offers of pricing and licensing.

I did not participate in the evaluation.

My recommendations:

• Before starting, review your internal processes. It is a good opportunity to update them.
• Explore Maximo's add-ons. There are a lot specialized, different industries.
• Implement Maximo in parts.

• Ease of use
• The ability to configure and integrate it with other solutions for ERP.

It allows my clients to manage and maintain assets to save costs and keep safety a high priority while maximizing production time.

Industry specific solutions are always a game changer.

It gets more stable with every release.

Maximo is made to be a worldwide enterprise app and can scale easily.

IBM has great support.

No.

The initial setup was complex, because it is a complex product.

You pay for what you get. There are lots of options depending on how you would like to implement Maximo.

No.

Plan out the implementation and involve all levels from users to management. 

I have used versions 4 through the most current version 7.6, and it keeps getting better. I have been working with Maximo for twelve years. This is the Cadillac of asset management applications. 

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.