Join this panel discussion to hear how Ariba customers are going beyond simple catalogs to obtain additional spend adoption and associated savings from their Ariba P2P/P2O solutions. This includes taking advantage of advanced functionality such as Invoicing against contracts, Collaborative requisitioning (3 bids and a buy), and supporting purchasing of Complex services (often done with Ariba Services Procurement).
This is a great session if you are just considering/starting your P2P/P2O deployment, or if you have already deployed P2P/P2O and are looking for more advanced steps to take.
One of the largest Career Education Companies in the USOwn and operate over 100 colleges across the US and Canada100,000 students and 8,000 employeesBrands include Wyotech, Heald, Everest and Quickstart
Does Ariba need some personal factoids for introductions?
Wiley has purchased the full suite of Ariba products including Sourcing, Contracts, Discount Pro, Spend Analytics, and P2P. At the conclusion of the implementation we will have employed the Consulting, Temp Labor and Generic drivers for the downstream solution.In an effort to automate processes and set a consistent global approval process Wiley has enabled non-PO invoice functionality. Included in this process is a custom e-form for new vendor set ups and payment requests.
Wiley went live with its P2P solution, eProcure, in August 2013. Two categories of spend were identified for the initial launch of the solution. IT Hardware/Software and Office Supplies were selected because they were SKU-based spend, had commodity owners who could be easily identified in the organization, contracted pricing and item lists were available, and there were several integrated suppliers in the categories.We scaled back our approach during the early months of the project. Integrated suppliers required more testing and work with catalogs, but they were experienced AN users with punch-out catalogs. Using integrated suppliers helped us because our supplier enablement lead was brought onboard late in the project time line and had to learn SE without the benefit of training. Wiley also did not have resources or processes in place to handle suppliers non AN-enabled. We were still able to capture close to 80% of the spend in each category using only integrated AN suppliers. We also limited our launch to the US. Having different versions of our ERP globally we needed to work with one set of accounts and suppliers for our initial implementation. This also helped us limit our audience to focus training and communications to an area our core team could work with directly.Data is a common theme for many organizations that implement a new system, and Wiley was no exception. Historically, we captured remit to information in our ERP system. When it came time to load suppliers into Ariba we discovered there was a need to build a supplier hierarchy. Wiley used a solution called MDM to build that hierarchy. This introduced a new data integration point in our process.Training users became an evolving process as we implemented categories and spend. Initially, we had a single trainer delivering demonstrations of the requisition to PO process. Our audience analysis was based on data we pulled from our ERP system and commodity owners. When we launched eProcure, particularly for office supplies, we created a process simple enough that many users who had never purchased for themselves were now doing so. This created a larger audience of users to train and support than originally anticipated.Prior to the implementation of a spend management solution Wiley’s authorized approvers were in the upper levels of management. As part of the change management process Wiley needed to empower its managers with authorization on purchases for nominal amounts to avoid long approval chains in the requisitions. This was a dramatic shift for some managers and required additional training and communications.Given that Wiley did not have an established Sourcing or Procurement organization at the outset of the program resources were limited during the initial implementation. Globally, Wiley is also in the process of restructuring its organization. These factors impacted the amount of change that had to be managed by the Core Team which factored into our decision to scale the initial launch back from its original scope.