Computing Webinar Also known as: in Research Informatics

Transcription

1 Life Science Cloud Computing Webinar Also known as: SaaS in Research Informatics Louis J. Culot Vice President, Enterprise Applications CambridgeSoft Corporation

2 SaaS - Overview SaaS Some basics Tenancy models single tenant vs. multi-tenant and Network effects. Support models research informatics support, I.T. infrastructure support. Business Models personnel staffing efficiencies In practice Some examples The questions Security Reliability Flexibility (business and technical) SaaS 2.0 network effect, service-levels, man nagement by objectives. SaaS Performance US/ Japan / China test and results for E-Notebook and Inventory

3 CS SaaS The Business Model " many customers are eager for the shift because they're frustrated by the traditional cycle of buying a software license,,paying for a service contract and then having to buy upgrades. Many customers believe they would have more control over the relationship if they simply paid monthly fees that could be switched to another vendor if the first failed to perform." - Opinion piece ComputerWorld by two McKinsey & Co. Consultants

4 CS SaaS The Business Model " many customers are eager for the shift because they're frustrated by the traditional cycle of buying a software license,,paying for a service contract and then having to buy upgrades. Many customers believe they would have more control over the relationship if they simply paid monthly fees that could be switched to another vendor if the first failed to perform." - Opinion piece ComputerWorld by two McKinsey & Co. Consultants Let s add to this running Informatics software, learning the ins-and-outs of a vendor s platform, are not core to discovery. We distinguish setting the objectives for such systems (such as data mining, or creating reports for insight), from the day-to-day back office operations.

5 SaaS Overview the Basics SaaS = Software as a Service Somewhat synonymous y with cloud computing. What is the cloud? It is not something ethereal, but technically can appear that way. But since it s a real thing (i.e., a server sitting somewhere on the network), there are practical considerations: Network bandwidth/latency. The realities of the actual hardware and data center. Maintenance of network interfaces / data exchange / etc. i.e., the nuts & bolts of your particularr cloud matter. On top of Infrastructure, there is a platform (i.e., PaaS), and, lastly, software than and end-user can conn nect to and use a.k.a. a SaaS. Horizontal market examples: Salesforce.com / gmail / itunes.

6 SaaS Overview the Basics major hurdles *Source : Forrester Research, Inc, Q Report (release Q1 2009)

7 SaaS Adoption SMB & Large Enterprises *Source : Eric Tsai, March 2009 Outsource I.T.: The Trend Continues

8 SaaS Overview the Basics tenancy models Tenancy Models: Multi Tenant (e.g., Gmail) One instance for all users / across companies, geographies, etc. Data are walled between entities. Single Tenant One instance per account entity (usually multi-user / one company) Application instances and data are walled between entitites. Some claim that only multi-tenancy models yield the needed economic benefits. However, we ve found that both singl le-tenancy and hybrid models are often more appropriate, if executed with appropriate sensitivities.

9 SaaS Overview Multi-tenant model Advantages / Disadvantages: Multi-Tenant + Larger shared infrastructure. + One instance to back-up, maintain, upgrade, provide failover, etc. + One software development platform m. + Software is configurable by user / entity. + Network effect (SaaS 2.0 more on this later). - Configurable, but not entirely customizable. - Rely on software implementation fo or data security between entities. - System integration with non-compliant systems difficult, if not impossible.

10 SaaS Overview Single-tenant model Advantages / Disadvantages: Single-Tenant + Fully customizable implementations. + Separate infrastructure for data security, etc. +Fl Flexible system integration ti (e.g., LD DAP integration). ti - Each entity has more of its own infrastructure. - Each instance - back-up, maintain, upgrade, provide failover, etc. - Can sprout multiple software branches. +/- Network effect (SaaS 2.0 mor re on this later).

11 SaaS CS Single Tenant Enterprise Service End-User clients CambridgeSoft Enterprise Instance Application tier end-user interfaces, APIs Dedicated Support Enterprise support service Shared Services (SOA) Content Services, authentication, security Shared Processes OS maintenance, data backup Infrastructure ESX Servers, VMWare, Ora acle, Server OS, Database OS

12 SaaS CS Single Tenant Enterprise Service End-User clients Software Dedicated CambridgeSoft Enterprise Instance Application tier end-user interfaces, APIs Shared Shared Services (SOA) Content Services, authentication, security Personnel Dedicated Support Enterprise support service Shared Processes OS maintenance, data backup Infrastructure ESX Servers, VMWare, Ora acle, Server OS, Database OS

13 SaaS CS Multi-Tenant Enterprise Service Software End-User clients Personnel Dedicated d Ddi Dedicated tdsupport Enterprise support service Shared Cambri Shared idgesoft Enterprise Application tier end-user interfaces, APIs Shared Services (SOA) Content Services, authentication, security Shared Processes OS maintenance, data backup Infrastructure ESX Servers, VMWare, Ora acle, Server OS, Database OS

14 CS SaaS Support model CS SaaS Support (personnel) Cost Model: - Partial/FullFTEs FTEs (employees can be full-time, but available as-needed per account). - On-shore, off-shore, or blended model. (opportunity to reduce cos sts while providing 24x7 support). - Blended coverage by expertise. (certain key skills enlisted on an as-needed basis). - Support has full access to CS deve elopment / management staff. - CS metrics based on reference status and renewal rate (%).

15 CS SaaS Support model CS SaaS Scientific Support Tasks (typical / dedicated staff): - SAR report design. - End user hand-holding. -E-Notebook configuration (UI design) - BioAssay protocol building. - Bulk registration (SDFile loading - Registration services (data curatorr services). SaaS I.T. Support Tasks (typical / shared processes): - User account creation. - Data back-up, server maintenance. / registration). -Application of security patches, OS upgrades, etc.

16 CS IaaS, PaaS, SaaS Integrating with large, installed platforms sometimes goes the other way, where the PaaS provides SOA applications to pull cost out of in-house discovery yplatforms. SaaS (Software) PaaS (Platform) IaaS (Infrastructure) CS Provides Enterprise/E-Notebook/Inventory ChemACX, Registration (SOA) X

17 CS SaaS Questions and Answers Are small businesses right to steer clear of SaaS? - Risks around business critical / sensiti ive data. - Total cost concerns. - Security - Performance concerns - Locked-in to one solution - Lack of customization

18 CS SaaS Key advances (here are six ) Focus on business processes SLAs (more robust) Rapidly achieve business objectiv ves Value-added services Network Effect SaaS Integration Platforms Phil Wainewright, SaaS 2.0 will change your business, May 2006

19 CS SaaS 2.0 Blending personnel with solution; costs can move to utilization, rather than usage (i.e., business objectives). SLAs (more robust) Rapidly achieve business objectiv ves Value-added services

20 CS SaaS 2.0 Blending personnel with solution; costs can move to utilization, rather than usage (i.e., business objectives). SLAs (more robust) Rapidly achieve business objectiv ves Value-added services Define the SLA the way you d definee an employee s objectives.. Building protocols, registry quality, SAR reports, etc.

21 CS SaaS 2.0 Consider Inventory or E-Notebook: Inventory global recycling of reagents and intermediates E-Notebook cross-organization sharing of pre-competitive knowledge Network Effect

22 CS SaaS 2.0 Consider Inventory or E-Notebook: Inventory global recycling of reagents and intermediates E-Notebook cross-organization sharing of pre-competitive knowledge Network Effect myth you need multi-tenancy to exploit the network effect. Although multi-tenancy makes it technologically easier, it is not essent tial.

23 Conclusions and Q&A SaaS for Informatics: The technology is here today / in production and in use. Vertical market suppliers startt at the PaaS level in order to be competitive. Personnel and staffing models amplify the value. Focus on true complete solution, with SLAs oriented towards business objectives. SaaS 2.0 (or what people call it) is largely here. Network effect is limited by the industry s desire to adopt. Questions??

24 CambridgeSoft Data Center Status of CambridgeSoft Scientific Cloud Operational 24 x 7 x 365. Follow the sun support mod del almost fully in place (some open weekend hours). Live monitoring and routing of all servers/instancs. Dedicated and shared instances. >10 customers in production, including: Large pharma, government, academic, and mid-market. Enterprise Suite, E-No otebook, Inventory, Data Services are current primary usages. Providing informatics support, as well as I.T. support. (e.g., registerin ing compounds, building protocols).

25 CambridgeSoft Data Center SaaS Type II facility dedicated I. T. staff monitors servers, applies security patches, upgrades. Local back-up with off-site storage (according to CS and customer SOP). Located in U.S. East Coast: SaS 70 audited. Physical security (limited access biometric security) Logical security (CambridgeSoft + customer SOPs for access) Multiple provider Internet connectivity. *coming soon live mirror to second facility. Deciding on asia and Europe mirror sites (primary access probably still through a single centralized site with data mirroring).