SAP S/4HANA Cloud is a modular cloud ERP software designed for every business need – powered by AI and analytics. SAP S/4HANA Cloud enables users to run mission-critical operations in real time from anywhere, introduce new business models in an industry, and expand globally. It can be deployed either on premise, in the cloud, or in a hybrid combination for quicker time-to-value.
$0
per month FUE users*
ServiceNow IT Service Management
Score 8.4 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.
$10,000
per year
Pricing
SAP S/4HANA Cloud
ServiceNow IT Service Management
Editions & Modules
SAP S/4HANA Cloud
Custom Pricing
per month FUE users*
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
SAP S/4HANA Cloud
ServiceNow IT Service Management
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
* FUE = Full user equivalent, which allows flexible customer choice among: 1 Advanced user, 3 Core-users, or 30 self-service users per FUE. Minimum purchase is 35 FUEs.
SAP S/4HANA Cloud leverages an in-memory database, allowing for real-time data processing and analytics. This enables organizations to make informed decisions based on up-to-the-minute information S/4HANA Cloud integrates various business modules, including finance, procurement, sales, manufacturing, and supply chain. This integration facilitates seamless data flow across different functional areas
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.
The complex integration we have with ERPs make it difficult to move or upgrade to SAP S4 HANA. Reimplementing all integrations and not impact business is a challenge
Requires a lot of tedious testing so that no role or function is impacted
Very time consuming to implement or upgrade. For large corporations it would take years to slowly migrate to S4HANA
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!
The cost of SAP as an ERP is quite high and the switching costs associated with ERP systems are even higher. That being said moving from one ERP to another only happens once in a great while for large organizations. Those switching costs include retraining, IT hardware requirements, outside consultants and more
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.
The system features a contemporary and visually appealing interface, promoting a more engaging user experience.
Role-Based Access:
Users access role-specific dashboards and functionalities, ensuring a personalized experience tailored to their responsibilities.
Intuitive Navigation:
Streamlined menus and navigation paths contribute to an intuitive user experience, reducing the learning curve for new users.
Responsive Design:
The platform is designed to be responsive across various devices, allowing users to access information and perform tasks on desktops, tablets, or mobile devices
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.
The technical support received by the ITT design teams and OS implementation team has been very useful in ensuring that the SAP ERP is well-tailored to our company's specific needs and operations. This coupled with the training materials, business process maps, and concept demos (sand-box demos) makes adoption easy on end-users.
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.
Implementation was as expected. We had minor issues with our Z* transactions, but nothing special. Some tables were extended and needed regeneration. Overall satisfactions is good.
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.
In our quest for an ERP solution, we evaluated alternatives such as Oracle ERP Cloud and Microsoft Dynamics 365. However, SAP S/4HANA Cloud's reputation for advanced analytics, scalability, and seamless integration with other SAP solutions made it the natural choice for our organization's digital journey.
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.
Cost Savings and Lower Total Cost of Ownership (TCO):
While the initial implementation costs might be significant, the centralized data management and automation features can lead to cost savings over time. This might be achieved through reduced manual labor, better inventory control, optimized procurement processes, and streamlined operations, resulting in a lower TCO.
Better Visibility and Compliance:
The system's ability to offer comprehensive data visibility can enhance compliance efforts, mitigating risks and ensuring adherence to regulatory requirements. This can lead to reduced fines or penalties related to non-compliance issues.
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.
