Ivanti Neurons for ITSM offers the flexibility to deploy in the cloud, on-premises or a hybrid combination. It replaces the Ivanti Service Manager, powered by Heat.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
N/A
Pricing
Ivanti Neurons for ITSM
ServiceNow IT Service Management
Editions & Modules
No answers on this topic
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
Offerings
Pricing Offerings
Ivanti Neurons for ITSM
ServiceNow IT Service Management
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
—
ITSM Pro and ITSM Enterprise also are available with optional "Plus" add-ons. These include AI Agents, an AI Agent Studio, and other features that augment the capabilities of the platform using AI Virtual Agents to automate tasks.
Both products are very capable players in the Enterprise Service Management space, providing custom and secure environments which make it easy for multiple lines of business to co-exist on one common platform, with Ivanti Service Manager providing a more flexible concurrent …
Verified User
Manager
Chose Ivanti Neurons for ITSM
We went with the HEAT Service Management Product because we already had HEAT Voice in-house, and the advantages of integration were inherent with it. We were offered alternatives to evaluate but opted to remain under the HEAT/Ivanti umbrella because of this integration …
Most recently, BMC Remedy, ServiceNow. Remedy seems to be the most established and ServiceNow is even more complicated than ITSM. We operated but did not select ITSM, so there was no choice at the time.
ServiceNow IT Service Management
Verified User
Engineer
Chose ServiceNow IT Service Management
Both Heat and ManageEngine were convoluted, too complex and very hard to use, especially from the end-user perspective, and also from the support team. ServiceNow, on the other hand, is very intuitive and more user-focused than the other products making the users feel welcome …
ServiceNow leads the industry for a reason, they are simply the best in the space. The tool is modern, hosted, updated regularly, and has over 1000 out of the box connectors for other popular products. The tool really does it all and provides a ton of functionality to end users …
We have been able to integrate our ISM system with Active Directory using API calls to automate user account creation and user Moves, Adds, and Changes. This has helped us make the employee onboarding and offboarding process much more efficient and less error prone. We cut down on mundane work for the account creation team and freed them to do more tier 2 and 3 tasks. Where the system has been less appropriate for us is trying to integrate non-IT service processes. We haven't gotten a lot of buy-in from groups that aren't used to using an IT related system to receive tasks. It will take some time for us to make a more user friendly, non-IT, Support role.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Very good at allowing a service line to configure the product to suit its needs. This is important so as to not have to craft operations around the technology, but the other way around!
A high level of flexibility to implement a great deal of automation. The product gives end users access to pre-defined or custom business rules and workflows as well as the ability to implement other forms of time savers!
There is a very comprehensive Help guide for end users and administrators alike. Quite often I have found the most obscure 'How To's' in this guide rather than needing to call into support or search out information on the Ivanti site.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
There's two sides to answering this question. From an Agent/Admin perspective, it's great. You can do a lot of really cool things and have a lot of options and tools available to you. From a customer perspective, you're not quite as spoilt for choice. Ivanti has been working on and improving their new mobile-responsive customer interface but in doing so have really limited the features they allow admins to configure. We've found this limiting but not unworkable. I hope this continues to improve.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
Support has been amazing. They are knowledgeable, respectful, efficient, and friendly. When something doesn't go according to plan, they go above and beyond to make sure your issues are resolved. I have come to think of them as an extension of my team!
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Ivanti is far more user friendly than ManageEngine, and has more features than Jira Service Management. It takes longer to get used to Ivanti because of the extra features, but once you're on board with how it works and how to make changes, the possibilities and configuration options are almost endless
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
There are many companies for you to choose from. Many have expertise in specific areas. I highly recommend making sure you find one that can work for your specific project needs and then be willing to go in a different direction if needed. There are a few companies that have the personnel to cover everyone's basis but truthfully not many.
In the Classroom Support department, this has provided a quick access system available via tablet for technicians on the go and has improved response time.
In the Helpdesk, this has assisted in the automation of repetitive tasks and assisted with providing better accountability for the completion of an assigned task.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
