"The incident management feature is good because it allows you to keep track of and classify issues."
"The most valuable feature is the ability to correct maintenance."
"The most valuable features are the ability to create work orders and preventative maintenance."
"It is configurable, where you can add extra fields to screens and to the database."
"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."
"IBM Maximo is the best software for assets management."
"There are not many enterprise asset management systems on the market and not many that have the categories that IBM Maximo has."
"I have found Work Order management the most valuable feature. Additionally, it is a very robust and powerful solution."
"The initial setup is easy and straightforward."
"We get software developed faster."
"It is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"It has improved our work in a number of ways. First, it has made everything much faster. Before Jira Service Management, it could take weeks to resolve a ticket."
"We can track, monitor, and get all the details we need from the end-user's point of view for any service request."
"In Jira Service Management, the most beneficial features are process improvement, workflows, and escalations."
"Developing processes is easy and user-friendly."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"Vendor management needs enhancement."
"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."
"Areas for improvement would be the user interface and support for Arabic. They could also be more customer-oriented."
"Initial setup is a longer process because Maximo is bigger and has more processes."
"It was very slow due to the lagging issues. So that was kind of frustrating, considering how slow it was while functioning."
"Coding can be complex when customization is required."
"The pricing model of the solution has room for improvement as well as the after-sales support."
"IBM Maximo can improve the financial support and financial application, to make it more similar to an ERP as opposed to an EAM. Overall they can improve the financial processes."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"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."
"We have tried exporting some of the test cases into Jira from Excel. The interface for that isn't very user-friendly."
"The initial setup is very complex."
"This solution lacks features for project management."
"It would be better if it had capabilities to connect to mobile applications (e.g., Whatsapp)"
"We have a lot of add-ons, however, instead of the add-ons, for example, cloning could be better."
"As a consultant, I have used the support. Some of the support I have received has been good and other times it could improve."
IBM Maximo is ranked 1st in Enterprise Asset Management with 6 reviews while JIRA Service Management is ranked 2nd in IT Service Management (ITSM) with 36 reviews. IBM Maximo is rated 8.0, while JIRA Service Management is rated 8.2. The top reviewer of IBM Maximo writes "Provides great flexibility although coding can be complex when customizing". On the other hand, the top reviewer of JIRA Service Management writes "It lets you configure workflows and manage requests; it has a dashboard for monitoring". IBM Maximo is most compared with ServiceNow, NetSuite ERP, ABB Ability Asset Suite EAM, IFS Cloud Platform and Oracle Enterprise Asset Management, whereas JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and Zoho Desk.
We monitor all Enterprise Asset Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.