No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Maximo vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Maximo
Average Rating
8.2
Number of Reviews
32
Ranking in other categories
Enterprise Asset Management (EAM) (1st), Billing Software (5th)
JIRA Service Management
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
88
Ranking in other categories
Help Desk Software (2nd), IT Service Management (ITSM) (2nd)
 

Mindshare comparison

IBM Maximo and JIRA Service Management aren’t in the same category and serve different purposes. IBM Maximo is designed for Enterprise Asset Management (EAM) and holds a mindshare of 15.2%, down 28.9% compared to last year.
JIRA Service Management, on the other hand, focuses on IT Service Management (ITSM), holds 7.3% mindshare, down 10.7% since last year.
Enterprise Asset Management (EAM) Mindshare Distribution
ProductMindshare (%)
IBM Maximo15.2%
Oracle Enterprise Asset Management8.5%
IFS Cloud Platform7.3%
Other69.0%
Enterprise Asset Management (EAM)
IT Service Management (ITSM) Mindshare Distribution
ProductMindshare (%)
JIRA Service Management7.3%
ServiceNow15.8%
BMC Helix ITSM5.7%
Other71.2%
IT Service Management (ITSM)
 

Featured Reviews

Antony Mishra - PeerSpot reviewer
Java Software Engineer at GPA
Asset management has become streamlined and decision-making is now driven by lifecycle data
The best features IBM Maximo offers are that it is very simple to deploy on OpenShift using Ansible playbooks. It also has excellent support for integration, is simple to configure, and the asset register is very straightforward. Work management and managing inventory are seamless. In terms of integration support, I have used preventive maintenance, work generation, accurate work execution planning, tracking actuals, and I can easily integrate with other tools and systems. IBM Maximo Suite gives me a single place where service cycles are standardized and tied to compliance. IBM Maximo has positively impacted my organization as it has been a very useful tool. It reduced human error by moving away from pen and paper-based scheduling. It saved cost by minimizing unexpected downtime of assets, with approximately 50% of time being saved. We have also reduced overwork among staff by removing redundant information and smoothing task flows. It helps us scale our team without micromanaging small issues.
Sohaib Ahmad - PeerSpot reviewer
Vice President Service Delivery at quixel
Comprehensive workflows and data views have supported complex teams but still need cost improvements
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, the detailed workflow editing and the kind of details that JIRA Service Management provides would be complex. For startups and smaller companies, JIRA Service Management would be complex. The cloud offering is easier because I don't have to manage the infrastructure. There are two templates of the project: company-managed and team-managed. Team-managed is a newer feature, which is good for startup-kind companies where they don't need control over data from multiple projects displaying in one dashboard. For startups, JIRA Service Management is somewhat complex with its schemes and everything. Capacity management should be improved in terms of additional features in the next release of JIRA Service Management.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Has a powerful audit combination that helps achieve high accuracy."
"The large range of configurability of the product is great, since everyone has a different way of doing things."
"Reliable, very configurable, and it's all integrated in the same database."
"Preventive maintenance management."
"Flexibility is one of the key components, along with ease of use."
"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, and additionally, it's an integrated solution and it has a lot of capabilities."
"When it comes to their reporting and analytics capabilities, I find them to be superb."
"IBM Maximo has positively impacted my organization as it has been a very useful tool, reducing human error by moving away from pen and paper-based scheduling, saving cost by minimizing unexpected downtime of assets with approximately 50% of time being saved, and reducing overwork among staff by removing redundant information and smoothing task flows."
"JIRA Service Management is much better than the normal JIRA software that we had, as it is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"It is one of the best tools in the market right now."
"Some of the most valuable features are simplicity, ease of configuration, and ease of customization."
"A good organizational tool."
"The customer portal with connection with our knowledge base has been most valuable."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"Customizations are most valuable. The customization of workflows is the main power of the Atlassian tools in general."
"One of the best things about JIRA is that it searches for answers while questions are being typed so some tickets do not need to be submitted."
 

Cons

"The interface is not very easy or user-friendly and is in need of improvement."
"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."
"IBM Maximo covers GL but only at a surface level. It doesn't provide deep account analysis."
"IBM Maximo is expensive, and it is not a very well-known product in India."
"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 work to get past that."
"It needs 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."
"This solution could improve by integrating or embedding finances, charts of accounts, and invoicing."
"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."
"I am not familiar if there's an integration with Visual Studio from Jira."
"The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time."
"It is pretty complex to move between the test environment and the production environment. There is potential for improvement."
"Jira Service Management should be more user-friendly."
"We faced challenges with integration for different frameworks like TestComplete."
"Currently lacks an asset management module that can affect deployment."
"Service Management currently lacks an asset management module that can make deployment more difficult."
"The customizations in Jira could be improved by being simplified. They are currently very complex."
 

Pricing and Cost Advice

"The concurrent user license is much more effective in management and cost-wise, as it is more suitable for maintenance management."
"Explore the possibility of using DB2. You will avoid the cost of SQL Server or Oracle licenses."
"IBM Maximo offers a licensing application, and you have to comply with the license."
"​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.​"
"The price of IBM Maximo could reduce, it is expensive."
"I do not know about the price of the solution. However, this has been an expensive project overall."
"You pay for what you get. There are lots of options depending on how you would like to implement Maximo."
"On a scale from one to ten, where one is low and ten is high, I rate the pricing a nine. The price is very high."
"Do not forget to calculate add-on costs. These cost a percentage of the JIRA purchasing costs and are based on the number of JIRA users."
"The cost has recently increased. It might be around $20 to $25 per user license."
"I rate Service Management four out of 10 for affordability. The price could be better, especially for companies using more than one Atlassian product. It's suitable for SMBs that can afford it. I don't think there's another tool that's both better and cheaper. All help desk tools are relatively expensive."
"We have paid $20,000 recently for a one-year license for our on-prem server."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"We need a license because we have a higher number than the free part."
"The price of the solution is becoming expensive and it should be reduced."
report
Use our free recommendation engine to learn which Enterprise Asset Management (EAM) solutions are best for your needs.
885,667 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Government
9%
Energy/Utilities Company
8%
Computer Software Company
6%
Financial Services Firm
9%
Manufacturing Company
9%
Computer Software Company
8%
Educational Organization
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise3
Large Enterprise22
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise24
Large Enterprise33
 

Questions from the Community

What needs improvement with IBM Maximo?
The only thing that I need from IBM Maximo is more simplicity. The application has been designed in a way that it is serving the enterprises. It needs to be simpler for the SMEs, or for the compani...
What is your primary use case for IBM Maximo?
There are different use cases for IBM Maximo that I work with mostly. We use it for complete asset management. Anything that comes into the asset repository, asset management, asset evaluation, any...
What advice do you have for others considering IBM Maximo?
AWS is more recommended for IBM Maximo. You can go into Microsoft as well, but AWS is preferred. IBM also has their own cloud as well.
What needs improvement with JIRA Service Management?
JIRA Service Management is costly. The pricing structure needs improvement. When I add some plugins, I have to pay the cost for every user whether they are using it or not. For smaller companies, t...
 

Also Known As

Maximo
JIRA Service Desk, Atlassian Jira Service Management
 

Overview

 

Sample Customers

Royal Boskalis Westminster N.V., DTE Energy, Swedish Match, Projetech, Fingrid, East Coast
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about IBM, Infor, Prometheus Group and others in Enterprise Asset Management (EAM). Updated: March 2026.
885,667 professionals have used our research since 2012.