1 / 8

Cloud Computing at Lundbeck

Cloud Computing at Lundbeck. Use Cases and Lessons Learned SIG Forum May 2010. Lundbeck and Lundbeck IT. Corporate IT: 120 employees in HQ Move towards global services Outsourced IT operations. Lundbeck: Founded in 1915 HQ in Copenhagen, Denmark 5900 employees in 56 countries

markemartin
Download Presentation

Cloud Computing at Lundbeck

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cloud Computing at Lundbeck Use Cases and Lessons Learned SIG Forum May 2010

  2. Lundbeck and Lundbeck IT Corporate IT: • 120 employees in HQ • Move towards global services • Outsourced IT operations Lundbeck: • Founded in 1915 • HQ in Copenhagen, Denmark • 5900 employees in 56 countries • Specializing in CNS • Revenue 2.6 billion/USD (2009)

  3. In production Solution: Google Message and Web Security Usage: Global security for all e-mail and web traffic Owner: Corporate IT Driver Lessons Learned • Trust is important • Flexible regarding pricing/licenses • Very inflexible regarding terms in contract • Knowledgeable local employees • Very satisfied with functionality and stability Cost reductions Simplify infrastructure by decommissioning internal solutions Free internal IT resources for other tasks/projects

  4. Decided Solution: Combined hosted source code control and social collaboration Usage: Host own code andParticipate/Monitor relevant projects Owner: Research Informatics Driver Lessons Learned Works well (tests) Quick to get started Was rather geeky Lacked windows clients Many big projects have moved The windows clients are ready Plan to execute before summer Move to GIT (from SVN) as version control system Easier to fork and merge projects Cheap and reliable solution Fast and global access to code

  5. In production Solution: Rave Usage: Electronic Data Capture Owner: Drug Development Driver Lessons Learned • Undergo knowledge transfer FIRST • Plan, Pilot, Assess, then implement • Vendor is always happy to do work, but at a price • Over-reliance on Vendor for consulting work, very expensive (time and money) • Data Transfers can be a challenge Replacement of existing Data Capture tools with Web Based eCRF (electronic Case Report Form) Ease of study deployment to sites Increased oversight of data during clinical trials

  6. Decided Solution: Office Communications Online and Office Live Meeting Usage: Global solution for communication and web conferencing Owner: Corporate IT Driver Lessons Learned Local sales force not very knowledgeable yet – especially concerning roadmaps for the service Online solution not functionally equal to on-premise solution License agreement with Microsoft becomes even more complex as we have Enterprise Agreement for on-premise solutions Fast to market with service Up front investment not required Better business case than on-premise solution

  7. Cloud Storage/Archiving Under evaluation Solution: None yet Usage: Long term storage/archiving Owner: Corporate IT Driver Lessons Learned • Currently not a good business case (looked only at list prices) • Amazon • Microsoft • Some locals • Amazon seems most mature • Still early days for Microsoft (at least for local account team) • Increased demand for long term storage (archiving) – especially from Research • Current estimates will triple our storage needs • Also requests from other business areas – e.g. Drug Development

  8. Private Cloud Building Solution: Server as a Service Usage: Global service architected as Cloud a service Owner: Corporate IT Driver Lessons Learned • Verify intended service is fit for a cloud style delivery • Should have started earlier with service definition and description • Infrastructure services seems as a good place to start with private cloud • Private cloud will exist together with public cloud and non-cloud architectures Cost reductions Much faster server delivery Enables charge back/cost transparency Easier to use to public cloud services at a later stage

More Related