IBM Maximo Application Suite is an enterprise asset management (EAM) platform.
N/A
Jira Service Management
Score 8.0 out of 10
N/A
Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
IBM Maximo Application Suite is well suited for organizations looking for an application to track their end-to-end procurement and supply chain process. It can also be used for billing services, but that would mainly be for services provided as part of a work order, not voluminous customer billing. IBM Maximo Application Suite allows us to have one application where someone from procurement can input contracts and details, someone from any various department can create a requisition and superiors can use automated workflow to approve a purchase order, and someone at an operations location can receive and store materials. Subsequently, someone in the field can submit their hours and material used and it be approved via automated workflow for an invoice to be created. Payment functionality is possible, but we did not implement this aspect of IBM Maximo Application Suite. To note, throughout the process, interfacing can be set up to send transactions to your general ledger. As far as interfacing, IBM Maximo Application Suite also offers tools and configuration to set up endpoints. We have been able to set up REST APIs and request/responses without heavy involvement from developers. This is a nice bonus if integrating with multiple applications.
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Delivers Out-of-Box solutions for various industries without the need for customization and configuration
Modules and Applications are well developed and linked in an orderly way, with proper documentation and help guides that allow end users to start using the system with ease
Powerful Work Management, Contracts, Inventory, and Purchasing applications and features that are a better match to other ERP applications today
Hard to implement. A high number of resources and manpower is necessary to implement and upgrade IBM Maximo due to its robustness and number of functionalities.
Version fragmentation. Due to the challenge imposed by a version upgrade, it is common to find systems relying on legacy versions of Maximo which might become a challenge for the support team.
Unfriendly UI. The excess of functionalities and services available might become a challenge for a starting user. Although it is possible to customize the UI to fit the exact needs of each user, it is important to map exactly what each user needs.
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
The versatility, strength, and value that IBM Maximo adds to our company's asset management procedures. The platform has greatly increased operational efficiency and asset performance by streamlining jobs, automating procedures, and offering customizable solutions. Furthermore, IBM's constant assistance and updates have been crucial in meeting changing company requirements. Though there's always potential for improvement.
The gui screens in IBM Maximo Application Suite are not overly cluttered with options to click and navigate to new areas. That is, the display is more of a layout of fields that the user can either input data or just interpret what is on the screen. For those in IT, there is even a feature (press Alt+F1) that will show you the exact table and column of any field selected.
I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
I have regularly contacted IBM Support to report issues and raise requests for issues we face during project implementations. The response from them has overall been good and to the point, and they get back to us within a day or 2 and guide us through the process of fixing it or providing an interim fix of the product
I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
As a computerized maintenance management system i do not have experience of any other system. The only experience I have is for Maximo and it works excellent for me. I am using many modules available in Maximo and all of these modules are almost fulfilling all of my business needs.
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
