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
Workday Adaptive Planning
Score 7.8 out of 10
Mid-Size Companies (51-1,000 employees)
Workday Adaptive Planning streamlines planning workflows, using AI and real-time data integration to improve collaboration and provide predictive forecasts for better strategic analysis.
N/A
Pricing
ServiceNow IT Service Management
Workday Adaptive Planning
Editions & Modules
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
No answers on this topic
Offerings
Pricing Offerings
ServiceNow IT Service Management
Workday Adaptive Planning
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
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.
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.
We're a mid-size organization working with a shoestring budget and an IT skeleton crew...not much room to dedicate resources to a platform like this fully. Having it SaaS based is helpful for system management through their Helpdesk system, and a single platform also helps streamline the knowledge needed by our developers when integrating other business aspects to Workday.
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 helps create dynamic plans for finances, operations and various functional units in an organization all under one platform
It helps in scenario modeling to help analyze various business events and report by any number of business dimensions including channel, customer or product
It can be integrated with any system including ERP, BI or CRM
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!
Dashboards are not the best for graphs/charts. However, I have heard of companies using the dashboards for forecasting/budgeting. I would like to see Workday Adaptive Planning demonstrate this part of the feature.
Better security or locks to prevent deleting Actuals data - you are literally one click away from doing this.
On the web-based reports, better functionality when needing to reverse the sign in calculations - right now it is only available for revenue vs. expenses.
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.
For one we're in way too deep to not move forward with Adaptive. We're integrated with Workday, we do a ton of reporting with Adaptive, and it's working very well for planning and forecasting. No reason to look back or change course.
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.
It is overwhelming at first, but once you really get to know it, you realize it is fairly simple and customizable, and then it has a lot more limitations than you first thought. Realizing those limitations and finding workarounds is when you know you've mastered the software.
There haven't been any lately. The only one issue I can think of is when there was an update in Adaptive that altered our reports. Before I realized there was an issue, Adaptive reached out to let me know, so that it could be fixed.
All aspects of Adaptive Insights perform well. One area that I wish was quicker was integration. When importing data from Intacct our accounting ERP platform, it can sometimes take 4 hours for the import to process. The earlier imports are done, the quicker they complete. My estimate for a quick upload is about two hours.
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.
Whenever we have had any questions, issues, or concerns, the support has been quick and thorough. [This] allow[s] us to be able to fully resolve any issues, or be connected with the right group quickly to attain the result we were after; be it from simple formatting to adding new detailed reporting.
This was extremely helpful so that they could walk you through the model and teach you more about the complexity of various areas. It is most helpful when it is specific to your organization's model. The larger in-person trainings were helpful but they tended to be more generic and entry level. The trainings that are more tailored to your specific needs are the most helpful.
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.
They often times tended to be way too generic or entry level. They would also become sales pitches to upgrade or get new Adaptive Planning products. The questions in the training would be very niche and specific to other organizations. They were rarely helpful to the group at large.
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.
Trust the expertise of very strong 3rd party implementers. Having deployed Adaptive at a separate company before, I thought I knew it all (hubris, I know). Fortunately, I began to (very quickly) trust the judgment of our Carlson implementation team, and they provided invaluable insights and best-in-class processes that have benefitted me and my team greatly.
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.
Workday became our choice because it is fully web-based and easily integrates with other systems. The learning curve for Workday was shorter than that of Dynamics. The reporting tools in Workday are more user-friendly than that of Dynamics. However Workday did not have Check Printing tools which are available in Dynamics. The organization started a project to digitize all financial transactions so it was not a priority feature. When it comes to scaling up the functionalities of Workday it was much easier than Dynamics.
We went from 2 users to 70+ users over a 2 year period of time. The application scaled wonderfully. 65 of those users were non-finance users so they were able to quickly learn the software and prepare budgets quickly and efficiently. That is the power of Adaptive and its ability to scale
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.
It's facilitated a better financial literacy and management by the non-financial managers in the company, giving them a much better ability to see what they're spending, control it, and plan better in the future.
It's hard to quantify the ease of model and version management, but we could never do what we're doing now with our current staff. It would take a small army to replicate anything close to what Adaptive pulls off using Excel, if it's even possible.