ServiceNow IT Service Management vs. Snow Atlas

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.

Assessing Compliance Assessing Renewal requirements

Incentivized

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

Incentivized

• Visibility of traditional desktop and web based applications
• Reminders when agreements and annual renewals are coming up in the next 90, 60, 30 days
• Helps us identify similar application types, where they are being used, so we can better understand the capabilities they provide businesses
• Provide usage trends over time to inform renewals and compliance
• Reclaim software that is note in active use

• 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!

Incentivized

• SaaS connectors are not always kept up to date usually when Publishers make changes to their Portal API's. Appears to be little active monitoring on Flexera/Snow Atlas' side unless a customer reports an issue with the data being returned. Fixes are normally implemented as as quickly as possible, depending on whether it is considered a Bug Fix or a Feature Enhancement.
• Users - Snow on SAM - No ability to add or bulk import manually. Completely reliant on AD Discovery or Entra ID Discovery
• Users - SaaS module - No ability for bulk update of Users for things line 'Online only' or 'Qualified' user accounts. This is an issue in larger companies where you have thousands of SaaS Users being reported through connectors like Microsoft E365.
• SaaS module Dashboard does not allow for filtering of insights to a specific Publisher.
• Not all Back end SMACC functionality form Snow License Manager have been exposed to the front-end access, as Snow Atlas does not allow customer Administrators access to the back end or SQL databases.
• If you are migrating from on-prem Snow License Manager to Atlas, migration tools have not been created by Snow and will require a Project to handle your migration. Without Migration tools, we had to use a Managed Service Partner who had to manually create a lot of their own scripts to retrieve data that cannot be downloaded via reports and imported into Atlas. Any attachments documentation on Agreement or License Records has to be manually re-attached/uploaded to the relevant Agreement/License records in Atlas as the migration was performed.

Incentivized

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.

Provides the much needed visibility to contain spend and rationalise software

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.

Atlas is easy to navigate, it looks reasonably similar to the on prem version we were using previously

Incentivized

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

For a massive system, page loads are reasonably quick, including searches.

Incentivized

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.

Incentivized

Front line support staff done always understand the issue you are explaining or the need to escalate to back end/higher up areas for resolutions and can often require use of the Escalate function or emailing to your Account/Customer Success Manager. That said, once an issue properly is understood, it is handled well.

Incentivized

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.

Incentivized

We should have spun up a Project to manage the implementation. Snow indicated to us the ease in which Snow Atlas could be implemented, however this did not factor in that we were migrating from their on-prem product Snow License Manager hosted through a Managed Servicer Partner. For a clean installation, your implementation can be quick and likely not require a Project. If you are migrating from another products or are a company that can have lots of stakeholders, fingers in the pie, hurdles/business processes that need to be adhered to, definitely use a Project to perform your implementation.

Incentivized

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.

Incentivized

This is my 1st software license tool that I've used.

Incentivized

ServiceNow works as an enterprise solution.

Incentivized

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

Incentivized

• Made it a lot easier to determine annual Microsoft renewal numbers and only renew what we needed reducing costs
• Helps us identify potential software that can be rationalised reducing costs
• Helps us identify unapproved software and people aware of the the risks