Anaplan is a scenario planning and analysis platform designed to optimize decision-making in complex business environments so that enterprises can outpace their competition and the market. By building connections and collaboration across organizational silos, the Anaplan platform surfaces key insights.
N/A
ServiceNow IT Service Management
Score 8.5 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. 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, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
Anaplan is a great tool for complex modeling of the future. When you are planning your actions for the future, have multiple, disparate datasets to interact with, have dozens if not hundreds of stakeholders who must contribute and need to be guided via a streamlined workflow engine, require complex logic that can grow with your org, require real-time reporting, and you need it all in less than 6 months.
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.
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.
Ability to decide if to apply the formula or a manual input on front end for each line item
Real Time Data Transfer across models. Currently Data is transferred using Processes across different models. Having a functionality to access data from any model in real time would be great
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!
Anaplan is a very strong multi-dimensional modeling tool that provides a calculation engine to empower a complex planning process. It is fairly easy to learn for those with experience in similar tools, or excel. It forces structure and auditability that spread sheets do not have, along with extensive security capabilities
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.
Anaplan's usability is very good. Users can customize reports and make adjustments with very little training. They can quickly plan and collaborate very easily. Making large adjustments or creating complex functionality may require more experience or training but a lot of tasks can be completed by users with very little experience
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.
There are very few outages. Maintenance is scheduled on two or three Saturdays per month, so as not to affect businesses. When there is an outage, users are kept informed of progress to restore the platform and typically this takes no more than an hour. Anaplan customer support is very responsive if we ever have questions about platform issues
Everything is calculated in memory in the cloud. It's nearly instantaneous updates when you make changes. The only time things get a little slow is when you have a massive model with very intricate calculations...but "slow" for Anaplan is not what I would call "slow" for something like Hyperion. We used to have Hyperion calcs that ran for 60 mins before you could use data. The equivalent would be 60 seconds in Anaplan.
Support quality has dropped since Thoma Bravo has taken over. I think some serious re-focus needs to happen here -- part of the beauty of being in the Anaplan community was how involved you felt in it before. Before I didn't dread sending a support ticket, now I am starting to.
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.
In my opinion, in-person training is always the best if you have the option to do so. This allows real-time interactions with the instructions, whereas the online training I took required me to write-down questions, email them, and wait for responses. This slows down the process, as you can imagine. That said, in-person training is an extra cost and it likely isn't needed for everyone. I would suggest selecting a small number of people to take in-person training and then having them act as mentors to the rest of your team. That way, as the rest of the team takes the online training, they have a resource to help them in real time.
Anaplan training materials are clear, simple, easy to understand and to follow. Visuals are excellent. The vendor is good at updating training materials in a timely manner and encouraging users and administrators to keep coming back to Academy site for refresher courses or new feature courses. I really like their interactive diagrams
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.
The platform allows a flexible implementation mechanic to be put in place, since the possibilities and functionalities are vast and there are very few things the tool cannot do well. The solutions for the financial planning and the integrated business planning we put in place were easily adopted by the end users and their day-to-day work was made easier.
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.
Compared to OneStream and Venna Anaplan offers a more modern look and feel of the platform. It is better situated and maintained in regards of platform updates as it's a full SaaS software there are never any issues with the system version as it's always automatically up to date with no backward compatibility issues. Due to the flexible nature of the modelling engine, it is also better suited to perform larger multi-department use cases, like IBP (Integrated Business Planning)
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.
We have managed to leverage Anaplan for financial planning and forecasting across the business. It is now used by almost every department, with more than 50 users (but I know of companies that have hundreds of users) and still the platform is quick and reliable. It is easy to make changes to divisions and departments or add users and apply different user settings - the core part of the model is not affected and end users can continue their work without any disruption
We've typically seen an average of 40% removal of time from processes using Anaplan an enabler
Though difficult to quantify, we consistently find our processes less error prone than in the past. Essentially, we've removed a previously "hidden cost" of risk due to poor data quality that was buried in our processes.
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.
