Implementing SharePoint 2010 Projects
- 1. Implementing SharePoint 2010 ProjectsAndy HopkinsPartner / Principal [email protected]
- 2. Who Am I?Chrysalis | BTS - PartnerChrysalis BTS focuses on vision and strategy, development and deployment, and process management of Information Management solutions for our clientsMicrosoft – Technology Development ManagerAssisted global alliance partners in developing their solution strategies around SharePoint technologiesLexis-Nexis – Director Systems EngineeringPrior to Microsoft, 13 years at Lexis-Nexis years in various roles from developer of search solutions to Director of Systems Engineering
- 3. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 4. SharePoint Supports Wide Variety of ApplicationsExtranetPortalsBusiness ProcessComplexExtranetsDashboardsCollaborationSitesOfficeWorkflowsSimpleIntranets
- 5. Applications Range from Simple to Complex
- 6. Finding the Right BalanceComplexityIncreased Custom Development
- 8. Higher Maintenance CostsProductivityLow Customization
- 10. Lower Maintenance CostsInformation Workers and Task WorkersInformation WorkersTask WorkersCarry out strategyMonitored tasksGenerate dataDeliver goodsRepeatable value addDevelop strategySelf managedCreate knowledgeAnalyze dataUnique value add
- 11. Information Work and Task WorkInformation WorkTask WorkProcess boundManaged toolsForms based entryTransaction focusedHigh scaleCollaboratingAd hoc processesDocument creationData discoveryHighly personalized
- 12. SharePoint Products and TechnologiesApplication Platform for Information AND Task WorkersDocument collaborationInformation discoveryInformation ManagementSurface for business dataUser managedWidely accessibleBusiness Process ManagementSitesCommunitiesCompositesContentInsightsSearch
- 13. Line of Business Applications on SharePointApplications deployed worldwide Contract ManagementLegal Case ManagementReal Estate ManagementGrant ManagementPermitting & LicensingHealth & Human Services Case ManagementInsurance Claims ProcessingHR Self-ServiceInvestigation ManagementStudent Information Systems (SIS)Recruiting ManagementCall Center / 311Healthcare DashboardProduct Production Optimization DashboardSupply Chain ManagementProduct Lifecycle Management
- 14. SharePoint 2010 Minimizes Key 2007 RisksImprovements in integrationExpanded ECM capabilitiesExpanded search applicationsImprovements in application lifecycle managementImproved scalabilityLess coding for workflow apps
- 15. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 16. Solution Success goes well beyond TechnologyTrainingTechnology20%SupportPoliciesCommunicationDeploymentDocumentation
- 17. Common Implementation MistakesJumping into implementation without an enterprise strategy aligned to business objectivesNot treating SharePoint like an enterprise applicationNot defining policies on what to use SharePoint for (and what not to use it for)Empowering users without appropriate training and guidance (i.e. security management)Not planning for scale and/or growthNot providing SharePoint as a centralized service for the organizationNot testing the backup/recovery process
- 18. Implement a Governance ModelEnsure that the portal strategy is aligned with business objectives so that it continuously delivers business valueAvoid portal, team site, and content "sprawl"Many of SharePoint’s capabilities are not ‘required’ or ‘mandated’; users need to understand the value to get the benefitUsers can do a lot – we give them “great power” and need to ensure they accept their “great responsibility”Ensure that content quality is maintained for the life of the portalConsistently provide a high quality user experienceEstablish clear decision making authority and escalation procedures
- 19. Governance Model Top TenClear Vision – Defined Business Goals and OutcomesWell Defined Roles and Responsibilities – Strategic ChampionDeployment ModelNot all Governance Models are created Equal – Multiple Models is OKPolicies – Regulatory ComplianceGuiding PrinciplesLaunch and Roll-out (Adoption) StrategyContent Management PlanTraining PlanGovernance Model Document
- 20. SharePoint 2010 ConsiderationsSocial Computing ImplicationsIncreased emphasis and availability of social computing means more types of content to govern“Social Data”Tagging, bookmarks, ratingsWikisBlogsProfiles
- 21. SharePoint 2010 ConsiderationsManaged MetadataConsistent Terminology / Enterprise TaxonomyBetter Navigation / FilteringBetter Search ResultsEasier on UsersBut…potential for confusionWhat is Metadata?Managed Keywords vs. Managed TermsDocument Columns vs. Social Tags
- 22. SharePoint 2010 ConsiderationsRecords ManagementIn-Place Records vs. Records ArchiveYou’ll likely use both – need to decide which and whenHas effect on:Record retention rulesWhich users can view recordsEase of locating records (Collaborators vs. Records Managers)Maintaining each version as a recordRecords AuditingSite Organization (and number of sites used)E-DiscoverySecurityIf you are doing Records Archive, you need a records manager role!
- 23. SharePoint 2010 ConsiderationsContent OrganizerPartitioning MechanismDo you use it?“Where did my document go?”SharePoint CustomizationSharePoint Designer: Off or On?Partially Trusted vs. Fully Trusted CodeExcel and Access Solutions
- 24. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 25. Traditional ECM Project ChallengesA conservativefailure rate estimate of ECM projects within large organizations is 50%Source: Doculabs27% of ECM users are highly disappointed in their ECM implementationsSource : Jupiter Research
- 26. Why SharePoint Adoption Can Be HardWhat is SharePoint exactly?CollaborationPortalSearchContent ManagementApplicationsAbout 20 other things!New ways of working creates cultural shifts that take significant time to adopt
- 27. Adoption CurveThe Roll-out strategy must focus on most effective approach to driving employees to adoption over timeWhen adopting a new technology, users typically pass through five stages, each involving a progression of behaviors and needs100%AwarenessLearningTrialApplicationAdoptionAdoptionStage/Time
- 28. What Users WantConnecting SharePoint to Business GoalsUsers want to see the connectionOutcomes, not requirementsElegant Solution DesignDon’t make users go through five screens to do one taskWhat’s in it for me?Users want to understand what they get out of using the system (why they have to add metadata, for example)
- 29. Must-Have Elements to Adoption StrategyCommunication PlanTraining PlanContent Conversion PlanUser Support PlanIncentives and Reward Plan
- 30. Communication PlanLeverage Experts and ChampionsCEO MemosTown Hall MeetingsBreak Room PostersMake sure you have an ongoing plan for continuous communication
- 31. Training PlanTraining: Not just for Developers and ITAlso For:Power Users (Site Owners)VisitorsMembersWeb Content ContributorsWorkflow Approvers“just-in-time and just enough”
- 32. Content Conversion PlanIt’s critical that important information gets moved to the new systemSeveral Options:Clean and migrate everythingMigrate nothing; Index old contentNew content only in new systemClean and migrate recent content only.Migrate ALL content and cleanse later should NEVER be an option!
- 33. User Support PlanContact Person for Every PageUse pictures and contact infoInternal Site Owner User Groups/CommunitiesEmpower users to help each otherGet the IT Help Desk on boardGiving users power means more questionsEnd-User Feedback LoopGet feedback in two ways:Metrics-based (number of users, rating scale, etc)Anecdotes (good/bad experiences)End-User resources (guides, help, etc)
- 34. Incentives & Reward PlanAnswer “What’s in it for me?”Show (with real data) why something is usefulProvide Recognition for Content ContributionMoney talks; so do titles & certificatesHave a Fantastic User ExperienceInvest in an information architecture
- 35. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 36. SharePoint 2010 ArchitectureMore ScalableSignificant work invested in SQL (to eliminate locks, etc.)New Service model and Timer job affinity allows server “grouping”Extensive performance and reliability testingHighly scalable Search Architecture
- 37. SharePoint 2010 ArchitectureMore FlexibleServer number can now be much larger (Tens of servers in a single farm)Enterprises can write their own services that take advantage of the SharePoint infrastructureExample: Kodak Capture Service (coming end of summer)PowerShell scripting replacing STSADM
- 38. SharePoint 2010 ArchitectureTiersWFE Tiers – Some changes, some optimizationApp. Server Tiers – Many changesSQL Tiers – Some changes, heavy optimization
- 39. SharePoint 2010 ArchitectureWeb-Front-End Servers – HighlightsRibbon UIClaims-based identityThrottling features to handle peaks gracefullyMemory Optimization => less memory issuesNew Usage Logging APICaching improvements
- 40. SharePoint 2010 ArchitectureApplication Server ServicesList of services that can run on Application Servers:NativeAccessBDCExcel ServicesPerformance PointVisio ServicesWordPPTOffice Web ApplicationsProject ServerMore will come…Custom Applications
- 41. SharePoint 2010 ArchitectureSQL Tier ChangesMany more Databases to manageGranular Database Structure‘Service Application’ Database is split up =>many new features have their own Database Partial List of services with own database:SearchPeople / Profile ImportTaggingTaxonomyInfoPath (session state)Secure StoreLOBiWeb AnalyticsPerformance Point
- 42. SharePoint 2010 Architecture Farm-Level ChangesService Model - Paradigm Change: SSPs are no more!Reasoning:Unusual conceptHard to deploy and manageUnable to scale: too many services in one databaseNew concept is “Service Application” or “Service App”Shared services split out into separate servicesProfiles, Audiences => People Service AppSearch => Search Service AppExcel => Excel Service AppBDC => BCS Service AppThere are also many other new Service ApplicationsService Applications can be ‘Cross-Farm’ instead of ‘Parent-Child Farm’
- 43. A Universe of SharePoint DeploymentsYour StarNo Cookbook
- 44. What Differentiates SharePoint Deployments?Hardware, Setting and TopologyFacts: # of servers, HW spec, rolesTuning Options: Add WFE or App Server, tune settingsYour Star.DatasetFacts: #of Site collections, DBs, Web Apps, Data SizeTuning Options: Split Site Collections, Balance Content DBsWorkloadFacts: purpose, services, # of Total users, concurrency, RPSTuning Options: Split farms, disable services, block clientsHealth And Performance Score (The SLA) Availability, Latency, Throughput, Responsiveness, Failure Rate…
- 45. Choosing an ArchitectureConsider both logical and physical aspectsStart with a logical architectureBuild it out to a physical architectureLow scale -> Medium scale -> High-scaleScale out as needed
- 46. Logical Topology ConsiderationsBusiness NeedsOrganizations may need isolation between respective ServicesRegulatory RestrictionsGeo Political RegulatoryInformation ArchitectureArchitecture of Web Sites influence association to Services
- 47. Physical Topology ConsiderationsScaleScale-up vs. Scale-out approach influences physical topologyLink Latency Host Services close to Users and ContentDirectory ArchitectureHost Services close to Directory for better auth, profile sync etc.
- 48. Scaling Services – Step 1Scale within the farmScale-upScale-out on each tierAdd Web Front Ends for content serversAdd Application Servers for compute-intensive servicesScale SQL for data-centric services‘Affinitize’Specific Web apps to WFEs using NLBsServices on specific app servers
- 49. Scaling Services – Step 2Multiple content farmsSplit services into separate farmsSecurity boundary Usage/scale Political / organizational Patching flexibilityMultiple Services farmsGeo-distributedLoadStart by separating out Search
- 50. Sample TopologiesProof of Concept/Demo EnvironmentSmall OrganizationMedium EnterpriseLarge, Distributed EnterpriseThese are examples, not prescriptive guidance
- 51. Standard Architectures Schematic Diagram, not to be use as a recommendation for Server CountsLimited deployments minimum servicesup to 5000 users (~5 RPS)50-100 GB of dataDemos and Dev BoxesWFE & App ServersSingle ServerSQLSmall Farm
- 52. Standard Architectures Schematic Diagram, not to be use as a recommendation for Server CountsWFELarge EnterpriseUp to 500k users (~500 RPS)10-20 TB of dataFederated ServicesApp ServersCommon Enterprises10-50k users (~50 RPS)1-2 TB of dataWFESQLApp ServersLimited deployments minimum servicesup to 5000 users (~5 RPS)50-100 GB of dataSQLWFE & App ServersDemos and Dev BoxesSQLMedium FarmSingle ServerSmall FarmLarge Farm
- 53. SharePoint 2010 Guidance64-bit Servers only! Enabling 2010 features will require more power!Dedicate SQL power to Logging DB and Web AnalyticsRecommended Hardware Requirements*:WFE and Apps Servers** - Dual processor, 8 GB RAMSQL Server** - Quad Core, 16 GB RAM Recommended Software RequirementsClient – IE7 (IE8 preferred) / Fire Fox 3.5/ Safari for Mac browsers 64-bit Windows Server 2008 (or 2008 R2)64-bit SQL Server 2008 R2, 64-bit SQL Server 2008 or 64-bit SQL* These is initial guidance and is subject to change** Recommended requirements to hold a production deployment
- 54. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 56. InteroperabilityBusiness Connectivity ServiceExternal ListsWorkflowData Form Web PartsDesktop Application Integration (Excel, Access, Visio, InfoPath)Federated Search20102010
- 57. Features
- 59. Business Connectivity ServiceNo code connectivity to external data sourcesDirect item binding via External Content TypesFull CRUDQ support (read-write)SharePoint Designer integrationOffline access to external dataFully indexed and searchable2010201020102010
- 60. BCS Architecture
- 61. WCF – Windows Communication FoundationLegacy web services deprecated in favor of WCFCommon web services still availableNative WCF support built into platformNTLM, Basic, Forms Authentication and SSODirect binding of list items via External Content TypesService-scoped timer job infrastructureService management via Central Administration201020102010
- 62. AgendaHigh Value ApplicationsCapabilitiesPlanning Best PracticesGovernanceAdoptionDeployment Best PracticesArchitecture / CapacityData IntegrationNext Steps
- 63. Next StepsIdentify business drivers, pain points, barriersStart with low hanging fruitIdentify deployment challenges and risksDevelop a high-level view of the key features and benefits relating to business driversConduct Architecture Design SessionANDContact Chrysalis | BTS to assist in your SharePoint 2010 Strategy and Implementation plans!Thank you!
- 64. Appendix
- 65. Microsoft’s 2010 Dog-Food FarmDescription: Team Collaboration Portal & Social NetworkingDay to day work and internal experiments Data Set: Workload: Search Full Crawl generating ~75%
- 67. 7 WFEs/App Servers [8 Core, 16 GB, Win 2008 R2]
- 68. 1 SQL Servers [8 Core, 32 GB, SQL 2008]
- 69. 1 SQL Server for the Logging DB [8 Core, 16 GB, SQL 2008]
- 70. EMC SAN Storage (70 Disks)3 General WFE1 WFE dedicated to search crawl 1 App Server:Central AdminUser Profile ServiceMetadata Management ServiceWord Conversion Service2 App Servers:Excel Calc ServiceOffice Web Access ServiceWeb Analytics ServiceAccess ServiceVisio Graphics ServicePerformance Point ServicePowerPoint Broadcast ServiceSandboxed Code ServiceBusiness Connection ServiceHealth and Performance Score:Microsoft’s 2010 Dog-Food Farm
Editor's Notes
- #16: Social Computing ImplicationsGovernance planning is even more important in SharePoint 2010 because the increased emphasis and availability of social computing features means there are more types of content to govern.SharePoint 2010 offers users a far more participatory role in the solution information architecture through the use of “social data” such as tags, bookmarks and ratings. Users need to understand and internalize the value proposition for leveraging these features. Solution designers will likely need to provide both guidance and encouragement for their use.
- #25: Awareness - User achieves awareness of the new technology and begins forming perceptions around its importance and value.Learning - User obtains an understanding of the tool’s fundamental attributes, such as what it does, its value, how to use it, and how it integrates with existing work processes.Trial -User experiments with the tool on current projects to experience tangibly how it fits with current modes of working. Obtains real-time understanding of benefits and experience.Application - User applies the technology regularly and gains greater familiarity with it, specifically as it relates to fundamental tasks.Adoption - User incorporates the solution as an indispensable tool. As such, the solution is a formal element within specific stages of work processes.
- #54: Lists – external lists surface external data through external listsLots of interoperability components scattered through the pie that enhance SharePoint as an application dev platform
- #55: Does it HAVE to be custom dev or can it be built through no code customizations/configurations
- #59: Windows communication foundationReplaces legacy web services