With advanced tools to automate manual processes and support close collaboration with suppliers, SAP Ariba helps streamline source-to-pay processes across organizations.
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.
SAP Ariba is more suited for Sourcing and Procurement using the Ariba Supplier network. Wherein once the RFQ document is approved, PR is generated, and on approval, we have a PO created, which goes to the vendor, who then corresponding to the PO, confirms it and creates ASN to the company as a mark to sending delivery confirmation. It generated Inbound delivery on SAP EEP side and on Goods receipt, Invoice document is generated on Ariba supplier network. Which completes the Procurement step. So for external procurement process, where vendor uses Ariba it is better to use SAP Ariba. With connectivity and integration with SAP ERP.
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.
SAP Ariba offers robust analytics and reporting features that allow users to track and analyze procurement data
The platform helps organizations adhere to regulatory compliance and mitigate risks. It provides tools for monitoring supplier performance, ensuring ethical sourcing practices, and managing compliance with internal and external policies
The platform automates the procure-to-pay process, reducing manual intervention and improving overall efficiency
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.
While its great at usability. I would love ut have it more simplified. I would like to advocate for some personas who are non tech savvy or who have less or no experience in procurement. I sometimes feel that the valley of user learning fir such personas is quite steep and it may take them long time of learning to get adept to the platform.
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.
Customer support has always been top notch. From small configuration changes to overall process changes, support has the teammates in place with excellent knowledge and is able to provide solutions based on business challenges quickly. Their customer support through their Account teams continues to be hands on and very responsive to needs in a timely fashion.
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.
It improves over all vendor management system of an organization by providing less costly ways of procurement and making business simple. AribaSAP Ariba digitally transforms your supply chain, procurement and contract management process. acts as supply chain, procurement service to do business globally In today’s world, there is a need to control your supply chain and to collaborate with your suppliers in an efficient way. To enable healthy supply chain, you need to have suppliers with visibility to every part of procurement process so that they can maintain an efficient supply chain and help organizations to grow their and own business..
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.
Improving Broadspectrum's PIFOT for suppliers who have migrated to invoicing through Ariba.
Provided a simple end-user interface to support PO creation, which has improved internal business process. This has led to good quality PO's being created upfront, which has reduced unnecessary re-work to ensure invoices are paid on time, and improved the businesses capability to report on real time commitment.
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.
