Moving from on-premise to next generation cloud technology what you need to think about to adapt successfully.

Transcription

1 Moving from on-premise to next generation cloud technology what you need to think about to adapt successfully

2 Xoomworks overview 6 offices serving EMEA We selected Xoomworks because of their in-depth procurement knowledge and expertise, and their experience in building sustainable stakeholder relationships. Tim Richardson, Head of Procurement, British Airways Team members Xoomworks really listened to our questions and took the time to understand our business, which in turn ensured that we delivered solutions in a way which best worked for us. Mel Jeffrey, Head of Purchasing, Bourne Leisure years established 1 Xoomworks Centre of Excellence ITIL-based knowledge, training & resolution centre coordinated from Romania languages When it comes to understanding what needs to be done, Xoomworks are the experts. This is not a company that will tolerate anything less than great service, and Xoomworks delivered everything we wanted. We wouldn t have been able to get it all done without them. Head of Procurement, UK Broadcasting over 230 projects across 100+ clients in over 40 countries

3 Our Clients

4 Procurement, transformed from sourcing to invoicing Implement Optimise Operate Sell and implement procurement solutions Transform procurement functions Support and run procurement operations electronic invoices, with optimised AP and working capital spend under management of millions in category savings

5 Overview Changing trend from On-Premise to Cloud 5 key differences between On-Premise and Cloud

6 Changing trend from On-Premise to Cloud (from Xoomworks experience) On-premise implementations Cloud implementations

7 Ovreview Changing trend from On-Premise to Cloud 5 key differences between On-Premise and Cloud

8 On-premise vs Cloud Key Differences #1 Cloud solutions are already built

9 On-premise vs Cloud Key Differences #1 Cloud solutions are already built Cloud solutions are already built True cloud solutions are multi-tenanted which typically means a more relevant, responsive and usable experience, implemented far faster, BUT maybe with less flexibility Defined scope of functionality BUT flexibility provided through Configuration so it is easier to implement but will need compromise around existing business processes traditional DESIGN & BUILD phases are replaced by this configuration phase which seeks to align your business process to a ready built application In some cases some business processes have to be Revised to suit the application functionality Dealt with a workaround in the solution This is typically a very hands on functional oriented phase No need for large capital expenditure only need a web browser and url!

10 On-premise vs Cloud Key Differences #2 Teams need to be different

11 On-premise vs Cloud Key Differences #2 Teams need to be different Teams need to be different The team should have focus on business involvement to get to know and understand the functionality and therefore make more informed decisions on how to apply the solution within the context of the business Smaller teams that have a good understanding of the whole process tend to work better More hands-on (if done well, this is the best covert change management that exists!) The initial phase results in key design decisions being made. Then this is typically followed by iterative phases during the build phase where configurations are fine tuned quick turnaround of days not weeks! - not suited to large teams with a complex decision making process

12 On-premise vs Cloud Key Differences #3 Things happen faster and more frequently

13 On-premise vs Cloud Key Differences #3 Things happen faster and more frequently Things happen faster and more frequently Implementation is more rapid: Design & Build is in essence understanding functionality and scope of configuration All clouds solutions have some element of integration with an existing ERP (or other applications) and tends to be the area which requires specific attention and expertise - knowledge in this area is key New releases as often as once a quarter mean a more up-to-date experience and more chance of customers involvement in solution functionality Updates have a lower risk but still need to be fully tested Minor on going changes can be made through configuration screens by application administrators

14 On-premise vs Cloud Key Differences #4 IT support changes dramatically

15 On-premise vs Cloud Key Differences #4 IT support changes dramatically IT support changes dramatically More emphasis on 1 st /2 nd line to solve user queries less technical support so need good functional and configuration knowledge Support more focussed on managing integration between Cloud application and the ERP (error handling & monitoring). 3rd line support is now with application owner: Run & Maintain most of this done by the cloud provider. Incident Management generally less incidents and where there are, they tend to be more data or config related (resolved 2nd line) Change Requests are not possible cannot customise Disaster recovery More emphasis on relationship with cloud provider as they have control of the evolution of the application - if you want any new features you need to make sure your voice is heard

16 Cloud vs On-premise Key Differences #5 Some things won t change but change is inevitable

17 Cloud vs On-premise Key Differences #5 Some things won t change but change is inevitable A lot of things will not change Fundamentally there are a number of aspects which will always be required, for example; Content/Master Data - forms that backbone on you apply the cloud based functionality within the scope allowable Testing - a key aspects and typically all usual test phases are required (integration test, UAT) Change Management critical in the success of a cloud based application Training tends to be easier as the UI is geared toward making it intuitive and user friendly For P2P solutions, Supplier Enablement is a key to success

18 Cloud vs On-premise Key Differences Summary Cloud solutions are already built Teams need to be different Things happen faster and more frequently IT support changes dramatically Some things won t change but change is inevitable

19 Cloud vs On-premise Key Differences #5 Some things won t change but change is inevitable Any Questions?

20 Cloud vs On-premise How these differences affect pre, during, and post implementation Pre-Implementation: More business involvement (understand their problems) Take a fresh approach to reviewing solutions have an app mentality Greater due diligence on product and vendor roadmap Invest time in SOW workshops and be crystal clear on what is expected of you Vision and stakeholder engagement is just as critical to success

21 Cloud vs On-premise How these differences affect pre, during, and post implementation During Implementation: More business involvement (hands-on configuration and testing) Have more iterations of the solution to check-in with all the stakeholders Have a SaaS mentality challenge current working and don t design for exceptions Create smaller teams that are more hands-on Remember that many things are still the same data, processes, content, users, suppliers, communications, training etc are all still as relevant now as they were before

22 Cloud vs On-premise How these differences affect pre, during, and post implementation Post-Implementation: More business involvement (feedback and tweaking) Measure, measure, measure - performance management and continuous improvement should be the focus Prepare for new releases and what these could offer the business as new features tend to be introduced at each release More time is freed up on technical support use it wisely! Stay focused on customer experience if there are more apps then how do people know where to go?