4 out of 5.0, Reviewed Oct 17, 2016
We drew upon a broad and deep base of expertiise to assist with implementation, and the migration from the on-premise to cloud based version of the solution - while not without its challenges - was predictive and ultimately sucessful.
Engage business users in process mapping early and often in the process.
Ariba ASM is a mature product which has retained it's underlying, core fuctional and UI experience, so folks are immediately familiar with the product and are accordingly more productive.
The converse of above - the product UI is dated, and it's principally geared towards commoditized sourding.
Additional process expertise in indirect sourcing categories would have been helpful.
A lot of funcitonal configuration changes were incorporated at the final stages of implementation. We would have employed a "freeze" earlier to avoid delays to go-live date.
Service orgnization retains many heritage Ariba resources with a combination of backline expertise and functional knowledge.
3 out of 5.0, Reviewed Sep 19, 2016
The migration and the creating interfaces to other SAP modules were complex, especially that we didn't have access to highly expert consultants that can work with us on premises in our campus.
Good contract planning and resourcing
Easy to access and use
Support in planning Plan and allocate and deploy the resources for the implementation of the project within a set timeframe
Have the migration planned ahead of time and be part of the same contract
we didn't get the required qualified resource
Some data didn't get into the new system
2 out of 5.0, Reviewed May 25, 2016
We were encouraged to sign the agreement by the pre-sales function on the basis of integrations and features that we were told already existed. They were actually on a development roadmap some years into the future.
It may sound obvious, but do not trust what the salesmen are saying and if they promise something, get it in writing as part of your commercial agreement. If you're in the Mining industry, ARIBA is not the same as Quadrem.
Fortunately, I don't have to use the system a great deal.
The UI is very hard to navigate and the terminology for different areas or concepts is not particularly intuitive. The configuration of creating the common question and response sets for vendors participating in RFI/P/Q/T is cumbersome and not easily reused. Scoring, weighting and other value based calculations are also not terribly flexible (Using Excel is still easier). The integration into SAP ECC is custom (as there is no out of the box option) which is particularly annoying which regards to creating outline agreements for execution and management.
Better transparency on the adoption levels of the tools locally and nationally. More honesty around when features and integrations are actually likely to be available. Offer improved training and guidance on system configuration and what constitutes good or common practice.
We would get upfront commercially agreed on terms of the features and integrations that are actually available in the product at the date of signing. We would not be pushed into signing early (to achieve upfront discounts) without a full feature and cost evaluation. We would perform more investigation into the adoption of ARIBA by customers and suppliers with which we do business.
In theory it is a highly functional product. In practice, it requires a huge amount of effort to either configure to best support your process, or modify your process to suit how the system operates. It is my belief that 12 months on, we are barely using 20% of what the tools are capable of.
There is no application managed support included as standard. You get basic service desk like support, but you have to pay again if you want to have consistently the same support personnel who understand your configuraiton, deployment, and integration.
It was a fixed price (and fixed duration) implementation, which did not deliver by the due date. We were led by the vendor to assume that given their experience they had allowed adequate time for implementation. They hadn't.