So you want to move to cloud? Why? When? How? All very legitimate questions but as introduced before you should really take a step back and look at the drivers for your cloud strategy. We all know the reasons for the move to cloud in terms of cost, performance, scalability, up-time, security etc etc but these are not just headline flashing light agendas. They are, of course, important drivers for the overall strategy but they should be considered in line with the overall business objectives. The analyses of the business processes in terms of the 'business roadmap' and not the 'technology roadmap' are critical in ensuring the end result is a success and not just a blind trend following project. After all, an enterprise level application will not solve your problems and will actually introduce constraints but it will introduce repeatability and this leads to efficiency in the right environment. By aligning your global business processes, again where possible, you can really gain from these efficiencies.
Now consider you have done all of the analysis on your business processes and you're happy with the plan for implementing the system. Then comes the regulatory piece, or if you're particularly diligent, you will of course have considered this during the analyses phase. However it is all too common in our experience that the regulatory aspects of enterprise applications is considered as a 'must be regulatory compliant' line item in a requirements document whereas it can fundamentally impact the business processes themselves. We are very happy to call this out in terms of not only the cloud strategy but the technology and engineering support services to make it a reality as this is exactly what we do as a company. Too many consultancy companies will put a document together and expect you to execute and then there are hosting companies who portray themselves as compliant 'destinations' but the journey to get there is all on you. Regulatory GxP Cloud is not a destination, it is a journey and it's extremely important to understand where that journey starts. It doesn't start with a procurement vendor analysis or a vendor audit. It starts with a whiteboard or a blank sheet of paper with the appropriate stakeholders exchanging ideas and OdysseyVC can initiate, contribute to, and deliver on those ideas.