1. EMEA Jürgen Pfeifer Architect, MCA Microsoft EMEA HQ http://blogs.msdn.com/juergenp SaaS in the Enterprise

2. EMEA WHY SAAS: LANDSCAPE AND VALUE PROPOSITION TO THE ENTERPRISE

3. EMEA Context: “SaaS ecosystem”

4. EMEA SaaS Impacts the Entire Consumption Cycle : In particular in the L.O.B. application space Purchase From: Long Eval Process To: Try before you buy Deployment Deployment From: Customization To: Configuration Management Management From: Reliance on internal IT To: SLAs Enterprise

5. EMEA Value Prop Hardware Cost at Provider People Cost at Provider Economy of scale

6. EMEA But, it‘s not only about consumption  In certain enterprise scenarios becoming a SaaS provider is an option  Services to Franchisers  Services to a Dealer network  …

7. EMEA PRACTICAL CONSIDERATIONS

8. EMEA On Premise or in the “Cloud” ? TECHNICAL POLITICAL FINANCIAL LEGAL

9. EMEA Examples of considerations ExamplesTFLP Boss said sox Data securityxx Regulatory requirementsxx Required features/solution not available out therex Business differentiator/core assetsx Requires deep integration with in house systemsx No incentive to optimize – what’s the ROI to migrate?x Unique SLA requirementsx Availability of credible SaaS providersxx

10. EMEA Identity management  Need to cater for multi-tiered authentication and authorisation models  Each client needs administrators / “super users” and regular users  Integration with enterprise identity management systems  Need to provide single sign-on from within the enterprise to SaaS application(s)  Extend user provisioning process from enterprise into SaaS domains  Access to audit logs generated by SaaS application(s)  Consolidated reporting for compliance, etc

11. EMEA Management integration  A chain is only as strong as its weakest link!  But in a world of SaaS what you care about is much broader than what you can control directly  Need to be able to gain insight into operational health and performance of SaaS applications  Benchmark against SLAs  Need to be able to integrate own systems management information with information emitted from SaaS providers  What happens if your systems management environment uncovers a problem with the SaaS system? Integration needs to be two-way

12. EMEA Data ownership  Cultural issues  Concern about and fear of loss of control  Compliance / Security  Legal/regulatory issues e.g. data privacy limit options to host data externally or impose additional constraints e.g. testing using live data  Need to extend risk management and security strategies to the SaaS provider  Compliance demands end-to-end controls – but one end may be in the SaaS provider  Backup/recovery, disaster recovery  Data protection approaches must extend to externally hosted data  Disaster recovery must incorporate the SaaS solution e.g. can a disaster recovery site still connect? Is the data accessible?

13. EMEA Now that you’ve decided on SaaS  Not all CRM SaaS are created equal. Due diligence check list:  Data security standards  SLA guarantees – also check what action is promised when SLA is violated.  Provider migration strategy: Availability of data and code escrow services  Compliance with vertical regulations  In house integration requirements  Composition features: Web services interfaces  Additional reporting services on hosted data (to support ongoing BI activities)

14. EMEA IMPACT ON YOUR ARCHITECTURE

15. EMEA Integration

16. Composition

17. Office Business Application Services Critical mass as a solutions platform Build people ready applications Use clients and servers create end-user applications Custom Ribbon and task panes Open XML file formats for file manipulation Web part framework integrated with ASP.NET 2.0 Unify your business platform Single infrastructure for UC&C, ECM, BI Extensible workflow based on Workflow Foundation Business Data Catalog for data integration Extensible search across content types and repositories More agile development Reusable client & server components Single framework for all types of web sites Tools for all types of developers

18. EMEA 18 LOB Apps, data warehouse, trading partners, etc The 2007 Microsoft Office System Critical Mass as a Solutions Platform Tools SharePoint Designer Visual Stuidio Tools for Office Tools SharePoint Designer Visual Stuidio Tools for Office BizTalk Adaptors XML Web services 2007 Office system clients Office SharePoint Server 2007 Office Business Applications Microsoft Office System Dynamics SAP Content Management Unified Communication & Collaboration Business Intelligence Exchange Server 2007 Office Communications Server 2007 Web Services / BizTalk Adaptor Packs Search Workflow Business Data Catalog Website & Security Framework Open XML File FormatsExtensible User Interface Siebel LOB Dynamics Duet ISV OBAs Custom OBAs

19. EMEA Extending Enterprise SOA Off-premise services Integration + Composition Platform On Premise Services Internal Edge Cloud

20. EMEA The role of the „EDGE“  SaaS is just one new way to use the „WEB as a place“  Your WEB functions need to meet future expectations of your customers,partners and employees  The „Web 2.0“ wave  Your internal users expect that their own IT enables this new world of work  e.g. User provided content, Rich Content, Discovery (Search), Collaboration

21. EMEA Users & Experiences  The center of gravity shifts back to the User  It is the age of access  The experience economy  Wisdom of crowds  Democratization, of innovation, of content, community and commerce

22. EMEA Next wave of „Consumerization“  Why not using consumer grade WEB applications in the enterprise?  Email  Search  Be carefull: One size does not fit all requirements  E.g. Email records for compliancy  Deep LOB integration necessary to do the job  Complex internal rights management

23. EMEA Differentiate IT  Functionality has precedence over deployment model  Find the right mix for your organisation

24. EMEA 24 Drivers  Business  Social  Technical  Technological

25. EMEA Business Drivers  Changing business models (“Long-tail”)  Monetization  Free / indirect / bundling  Ad based revenue  Transaction based pricing  Subscription  Mini / micro transactions  Long tail  Business aggregation  Consumer to enterprise movement

26. EMEA Social Drivers  Changing social models (“Gen U”)  User generated content  Power of numbers  Search and discovery  Community  “Folksonomies”  Personalization and responsiveness  Rich content (voice / image / video)  Ranking / rating

27. EMEA Technical Drivers  Software + Services (“Live” era)  High levels of bandwidth and connectivity  Edge power (phone, ipod, PC)  Peer to peer  Mesh networks  Instant deployment / permanent beta  Rich content support (ipod, MP4, VOIP)  Lightweight tools  Channel filtering and aggregation  Application aggregation (mashups)  Services based

28. EMEA Technologies  Lightweight technologies  REST  AJAX / Atlas  RSS  ROR  Wikis  IM / Bots

29. EMEA EDGE Definition  Provider and consumer model  Provider edge: Enterprises / SOA  Consumer edge: Consumers / Web 2.0 Is Web 2.0 the global SOA? No they are two Edges We need an architecture which covers both

30. EMEA EDGE Characteristics Async. / SOAP Async. / REST Communication Small (servers) Very Large No of types of devices Enterprise Edge Consumer Edge SOA/ESB P2P/Web 2.0 Name CentralizedDecentralized Control LargeHuge Total Demand SlowFast Rate of change LargeHuge Total Power Medium In the web 2.0 cloud Connectivity Large Very Large No of devices ManagedUnmanaged Organization

31. EMEA EDGE Common Capabilities  Relationship management  Rich content  Collaboration  Discovery

32. EMEA EDGE Architecture Web 2.0 SOA RelationshipManagementRichContentCollaborationDiscovery

33. EMEA EDGE Architecture Web 2.0 SOA RelationshipManagement Identity management Friends, Family, Group management Access management Personalization Tribes and “Folksonomies”

34. EMEA EDGE Architecture Web 2.0 SOA RichContent Video TV Image Audio Geo Movie

35. EMEA EDGE Architecture Web 2.0 SOA Collaboration Blogs Wikis IM Email Discussion boards Conferencing (audio, video) Back channeling Bots Wikipedia

36. EMEA EDGE Architecture Web 2.0 SOA Discovery Search Tagging Ranking and rating Clouding

37. EMEA EDGE Architecture Web 2.0 SOA RelationshipManagementRichContentCollaborationDiscovery

38. EMEA EDGE Architecture RelationshipManagementRichContentCollaborationDiscovery Interaction/CompositeApplicationServices/MessagingWorkflow/Process Identity & AccessManagementFederatedData

39. EMEA Patterns on the EDGE  Peer to peer (XBox Live, Napster, Skype)  Centralized (MSN Spaces, Google)  Asynchronous (Fremont, Flickr, Housingmaps)  Hybrid  …

40. EMEA People Relationships Customers Products/Services Operations

41. Software Architecture at the EDGE Web 2.0 SOA Put the User back into SOA

42. EMEA Software Architecture at the EDGE Web 2.0 SOA User/ExperiencesArchitecture

43. © 2006,2007 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.