This document covers two presentations on SharePoint as an Enterprise Platform 1. SharePoint Strategic Implementation Planning: Content, Taxonomy & Governance 2. SharePoint Platform Architecture: Defining Inputs, Outputs and Accountability

1. Elevating SharePoint to an
Enterprise Platform
April 2011

2. Today’s Agenda
8:00am Registration and breakfast served
8:30am Welcome and speaker introductions
8:40am SharePoint Strategic Implementation Planning:
Content, Taxonomy and Governance—Arthur
Savage, Perficient
9:25am Break
9:30am Unleashing SharePoint’s Full Business Potential
with DocAve—Mike Shine, AvePoint
10:15am Break
10:20am Platform Architecture: Defining Inputs, Outputs
and Accountability—Micah Swigert, Perficient
11:05am Break
11:10am Proven Practices for Seamless SharePoint 2010
Migration—Mike Shine, AvePoint
11:55am Drawing and closing remarks

3. About Perficient
• Founded in 1997
• Public, NASDAQ: PRFT
• 2010 Revenue of $215 million
• 18 major market locations throughout North America
– Atlanta, Charlotte, Chicago, Cincinnati, Cleveland,
Columbus, Dallas, Denver, Detroit, Fairfax,
Houston, Indianapolis, Minneapolis, New Orleans,
Philadelphia, San Jose, St. Louis and Toronto
• Solution and Industry Based National Practices
• 1,500+ colleagues
• ~490 enterprise clients (2010), 85% repeat business
rate
• Alliance partnerships with major technology vendors
• Multiple vendor/industry technology and growth awards

4. Perficient Microsoft Relationship
• Microsoft NSI Gold Partner with competencies in
– SharePoint – Content Governance, UX, Technical Architecture
– Business Intelligence – Data Architecture, Information Visualization &
Governance
– Digital Marketing – FIS, FAST
– Cloud – Azure, Office 365
– Data Management/Custom Development Solutions
– Business Process and Integration
– Mobility Solutions
– Top 10 Microsoft NSI Partner
– Ranked in top 1% in terms of Performance and Readiness
– Direct Delta Force team engagement
• SharePoint Expertise
– Over 200 SharePoint 2007 (MOSS) implementations completed
– Over 60 SharePoint 2010 implementations completed or in progress
– Over 450 consultants with deep experience with full SharePoint solution life cycle
including: Envisioning Governance, Business Analysis, User Experience, Technical
Architecture, Construction, Testing and Deployment
– Microsoft MVP certified architects & Business Principals that present to industry
conferences, user groups and “SharePoint Saturdays” on a monthly basis

5. Today’s Presenters
Arthur Savage, Perficient
Arthur is a Senior Solution Architect at Perficient. He has 20 years of experience in the
professional information technology services field with extensive experience in concept design,
architecture, documentation, and delivery of SharePoint solutions. His primary focus has been in
the Manufacturing, Food Processing, Sports Entertainment and Pharmaceutical sectors.
His broad knowledge and experience designing and deploying SharePoint technologies covers
multiple aspects of Information Systems including; collaboration, electronic content management,
electronic document management, data records management, security, development and
administration. For the past 10 years he has been focused almost exclusively delivering Microsoft
Office SharePoint Server technologies.
Micah Swigert, Perficient
Micah is a Technical Director for Perficient. In this role he is responsible for solution architecture,
delivery satisfaction, team management and sales team alignment for all Microsoft-based
technology engagements in the Chicago area. Micah comes from a technical background, focused
on engaging with clients in enterprise architect, Microsoft subject matter expert, application
architect, and lead developer roles. Clients have typically been in the Chicago area and are
typically financial services, manufacturing, professional services, and health care firms. Micah has
presented at various user groups and other technical groups over the past fifteen years on a
variety of Microsoft technical subjects: rich client user experience, layered .NET application
architectures, service orientation and .NET capabilities, and integrating SharePoint technologies in
custom application development methodologies and best practices.

6. Today’s Presenters
Michael Shine, AvePoint
Michael Shine is a Systems Engineer, based in AvePoint’s Chicago
office, with extensive experience in implementing AvePoint
solutions into complex, enterprise-level SharePoint deployments
within organizations across numerous verticals. With several
years of experience in implementing administration, storage
optimization and migration solutions for SharePoint, his
contributions to the SharePoint community have earned him
speaking opportunities at technical conferences, symposiums and
user groups throughout North America.

7. SharePoint Strategic Implementation Planning: Content,
Taxonomy & Governance
Arthur Savage, Senior Solution Architect
Perficient

8. Agenda
• The Need for Governance
• Defining a Governance Model
• Implementing the Governance Model
• Information Architecture, Taxonomy and
Planning
• Q&A

9. The Need for Governance
• Align SharePoint strategy with business
objectives
• Oversee business & organizational
transformation
• Establish clear decision-making authority and
escalation procedures
• Build organizational commitment & sponsorship
• Create continuous and measurable
improvements processes
• Monitor SharePoint investments and the value
that is delivered

10. Governance
• Structured approach
• Involve Business and IT
• Create infrastructure
– Governance board
– Technical liaison
– Standards
– Technical infrastructure
• Planning
• Prioritizing

11. Governance Setup
• Organizational structure
– Current state
– Candidate structures
Models
– Structure and responsibilities
• Governance
• Project roadmap
• Project initiation
Relative Value
Relative Value
• Architecture standards and review
• Platform operations and support
• Service offerings
• Definitions and use cases
• Engagement and funding
• Competency planning
• Roles and job descriptions
• Training plans

12. SharePoint Program Governance /
Roles and Responsibilities
Composed of affected Business and IT associates
(Board exists for length of project, but membership
can change); responsible for:
SharePoint Driving initiative team – Project-level governance,
key decisions, and issue resolution
Governance
Approving designs, plans, and results
Board
Creating business requirements, standards, and
governance
Recommending enforcement policies
Responsible for:
Develops technical solution based on business
requirements
SharePoint
Executing deployment plans and handling day-to-
Implementation day project management
– Project plans
Team – Budget tracking
– Project Reviews

13. Detailed Roles and Responsibilities
Team Individuals
Role Responsibilities
Executive Executive Sponsor
Owner - Executive responsibility for the project
Exec - Budget and Scope Management
Owner - Project Representation to the Executive
Team
Governance Business Leadership
Governance Board - Vision, Design, Plans, and Results
Board - Policy, Procedure, and Issue Resolution
- Governance and Key Decisions
- Layout and Structure
Content Site and sub-site Leadership
Content Owner - Determine Membership
Owner - Police Content
- Provision Sub-site (team site)
Contributor Create, Update, and Delete Content
Contributor
Reader Access Content but Cannot Update
Users
Reader Technical Technical Administration of:
Administrator - Configuration
- Standards and Security
Technical Administration - Policies and Procedures
- Provisioning
- Maintenance and Backup

14. Strategic - Example
App Communicati
Service
CEO CIO
Delivery
Prod Mgmt Development ons 2-4 hours
per quarter
Technical Svcs HR/ Lega Strategy Finance
Governance Board
2-4
Vision & John Smith Joe Davis
Linda
Baum
Beth Smith
Alan
MacDonald
Sridhar Gregg hours
Goals Gupta Smith
per
Content Owners month
SharePoint Approved
SharePoint Technology Team Program Mgt Projects
SharePoint
Strategy
??
Technology Lead
SharePoint
Roadmap
?? ?? X Project Y Project Z Project
Technical Architect Information Architect Sponsor Sponsor Sponsor
Standards
Document &
Development Security Taxonomy
Management Guidelines
X Project Y Project Z Project
Development
Teams

15. Implementation
• Governance should be part of an overall Roadmap
• Governance should be included in the Foundation
and in all phases
• Governance IS an ongoing effort
– Departments may change depending on project mix
– Key roles will not changes
– Best practices will not change

16. Taxonomy
The creation of a taxonomy provides
• A way to categorize content, allowing access to corporate
content through simple and complex keyword searches
• A key initial step in an overall enterprise content
management strategy
• A system architecture, document definitions and document
relationships are developed right the first time

17. Content Taxonomy
Content Types and Attributes
Content Types
Content Type Parent Content Type
Content Columns
Vendor Contract CBE First Source
Content Types Type Lessee Vendor Meeting Type
Type Type Type

18. Site Architecture
Site
Content Types Security
Architecture
Document
Site Name Site Type Sub-Site Webparts Folder
Library

19. Project Team Structure
G overnan ce
E x e c u t iv e
B o a rd
S po nso r
P r o g ra m C ore
O f f ic e T eam
E x te n d e d
T eam
S e n io r
T e c h n ic a l
B u s in e s s A r c h it e c t
A na ly s t
Bu s/ UX D e v e lo p e r s
A n a l ys ts

20. Information Architecture

21. Upgrade Cycle Overview

22. Minimum Software Requirements

23. Minimum Hardware Requirements

24. SharePoint 2010 Upgrade Tool
Visibility into upgrade process and potential problems

25. SharePoint 2010 Upgrade Methods
• In-place upgrade
– Previous version is overwritten
– Sites are unavailable
– Same URLs after upgrade
• Database attach
– Content DBs supported
– Config and search cannot be attached
• Hybrid approach
– Detach DBs
– Upgrade to 2010 in-place
– DB Attach Content DBs
• Visual upgrade
– A feature that seperates data upgrade from UI upgrade
• Third-party migration tools
– Quest, etc.

26. Q&A

27. SharePoint Platform Architecture: Defining Inputs,
Outputs and Accountability
Micah Swigert, Director, Microsoft Chicago Delivery
Perficient

28. Agenda
• Considering SharePoint as a platform
• Defining inputs to technical architecture
• Creating outputs using models
• Defining outputs

29. What is SharePoint
• It’s a set of products and frameworks built on
ASP.NET and SQL Server
• It’s a horizontal portal solution
• It’s that pie thing
• It’s a platform for web-based
business applications
– Out-of-box sites
– Created by end users
– Created by developers/IT
– Purchased from a third party and implemented

30. How It Starts
• Typical:
– Got it with EA, wanted to use it because we
already paid for it
– End users wanted to collaborate on
documents, calendar, tasks, etc.
– Bought a product that needed it
• Then:
– A “point solution” gets implemented
– It succeeds or it doesn’t

31. How It Starts
• If it succeeds
– “What else can we do with this”
– “How do we manage it?”
• If it doesn’t
– Lack of interest – moving on
Desert Jungle

32. Inputs
• Information architecture
– Site hierarchy
– Taxonomy
• Governance plan
– Who, how
– Strategic growth plans, vision
• Requirements visualization
• Specific application requirements

33. Defining Meta-Models
• As architects, we build models
• To guide us, we use
– Templates—reuse successful models
– Platforms—reduce parameters/options, provide features
– Models
• Meta-models are models we can use as architects
to create our output: models

34. “SharePoint makes 80% of what you need to do
easy… it makes the 20% [almost] impossible”
• Treat SharePoint as a platform, not as a
framework for custom ASP.NET applications
• How do you architect for platforms vs.
applications?

35. The Driver-Constraint Model
• Define the “driver”
Business, Technical, Organizational
– What is it that the stakeholders want to do?
– What is the expected lifetime?
– Who are the constituents?
• Define the “constraints”
Business, Technical, Organizational
– Who is going to maintain?
– What level of customization?
– Existing infrastructure, limitations

36. The Driver-Constraint Model
Drivers Constraints
• Be able to quickly spin up • No one on staff to
simple team sites administer SharePoint
• Be able to share quotes • Business owners may not
and invoices with select want to do site owner
customers tasks
• Have a place for basic • Limited SQL backup
forms, policies, capabilities
procedures, company • SharePoint sizing rules
news, etc.

37. Functional Map
Foundation Publishing Search Social Customized (Assembled)
Site Site (Blogs / Applications
(Doc Libs, Wiki / BI Web Form /
Calendars, MySites) Databases Workflow
Tasks)
Intranet
Team
Sites
Extranet
Public
Sites

38. Consensus Before Planning
• http://technet.microsoft.com/en-
us/library/cc261834.aspx
• ONCE you have completed:
– Driver/constraint
– Functional map
– And gotten consensus

39. Outputs
• Plan for
– Browser support, client
– Sites and solutions
– Security (authentication, authorization)
– Availability and scalability
– Performance and load
– Contingency / disaster recovery
• Technet has great examples

40. Outputs
Individual partners Remote employees Internal employees Customers
Users https://partnerweb.fabrikam.com https://intranet.fabrikam.com http://fabrikam http://www.fabrikam.com
https://team.fabrikam.com http://team
https://my.fabrikam.com http://my
https://remotepartnerweb.fabrikam.com http://partnerweb
https://fabrikamsite.fabrikam.com (authoring) http://fabrikamsite (authoring)
Extranet Default Intranet Internet
Zones and Directory — Corporate directory Directory — Active Directory Domain Services (AD DS) Directory — AD DS Anonymous authentication
authentication Authentication type: Authentication type: Authentication — Integrated Windows (Kerberos or NTLM)
UAG, TMG, or ISA — Forms-based authentication UAG, TMG, or ISA — Forms-based authentication
SharePoint — NTLM or Kerberos SharePoint — NTLM or Kerberos (same as internal employee)
Load Balancer Load Balancer
Server farm
Application Pool 1
Front-end Application Pool 1
Front-end
Web Servers Web servers
Web application: Web application:
Admin site Central Administration Site Central Administration Site
Application Application
server server
Clustered or mirrored Clustered or mirrored
database servers database servers
running SQL Server running SQL Server
IIS Web Site—“SharePoint Web Services”
Services IIS Web Site—“SharePoint Web Services”
Application Pool 2
Unpartitioned services Partitioned Unpartitioned
Application Pool B
services
Search
Search Managed User Profile Excel Access Visio Web Subscription Managed Managed
Metadata Calculation Service Graphics Analytics Settings Metadata Metadata
Services Service
Web Secure Store Business Data Word Word PowerPoint Partitioned by Search Unpartitioned
Analytics Service Connectivity Services Viewing project in the instance for the
Partner Web published
site collection content
Default group Default group
Custom group
App pools Application Pool 3 Application Pool 4 Application Pool 5 Application Pool 6
Web applications Web application: Published Intranet Content Web application: Team Sites Web application: My Sites Web application: Partner Web Web application: Company Internet Site
http://fabrikam http://teams http://my http://partnerweb/sites
Site collections Production site http://www.fabrikam.com
HR Facilities Purchasing Authoring site collection
Team1 Team2 Team3 http://my/personal/<site_name> Project1 Project2 Project3
collection
Products Services Support
Sites
Content
databases Database settings:
Target size per database = 200 gigabytes (GB)
Database settings:
Target size per database = 200 gigabytes (GB)
Database settings:
Target size per database = 175 gigabytes (GB) Database settings:
Site size limits per site = 1 GB Target size per database = 200 GB Content deployment
Site size limits per site = 30 GB
Reserved for second-stage recycle bin = 15% Storage quota per site = 5 GB
Reserved for second-stage recycle bin = 10%
Maximum number of sites = 180 Maximum number of sites = 40
Maximum number of sites = 6
Site level warning = 150 Authoring and Staging site collections hosted in dedicated databases
Site level warning = 5
Zone Load-Balanced URL Zone Load-Balanced URL Zone Load-Balanced URL Zone Load-Balanced URL Zone Load-Balanced URL
Zones and Intranet http://fabrikam Intranet http://teams Intranet http://my Intranet http://partnerweb Internet http://www.fabrikam.com
URLs
Default https://intranet.fabrikam.com Default https://teams.fabrikam.com Default https://my.fabrikam.com Default https://remotepartnerweb.fabrikam.com
Extranet https://partnerweb.fabrikam.com
Zone Team Sites Zone Self-Service Sites
Zone Published Intranet Sites Zone Load-balanced URL— Administrative
Intranet http://teams/sites/Team1 Intranet http://my/personal/User1 Zone Partner Web Sites
Intranet http://fabrikam http://teams/sites/Team2 http://my/personal/User2 Intranet http://fabrikamsite
http://fabrikam/hr http://teams/sites/Team3 http://my/personal/User3 Intranet http://partnerweb/sites/Project1
http://fabrikam/facilities http://partnerweb/sites/Project2
http://fabrikam/purchasing Default https://teams.fabrikam.com/sites/Team1 https://my.fabrikam.com/personal/User1
http://partnerweb/sites/Project3
Default Default https://fabrikamsite.fabrikam.com
Default https://intranet.fabrikam.com https://teams.fabrikam.com/sites/Team2 https://my.fabrikam.com/personal/User2
Default https://remotepartnerweb.fabrikam.com/sites/Project1
https://intranet.fabrikam.com/hr https://teams.fabrikam.com/sites/Team3 https://my.fabrikam.com/personal/User3
https://remotepartnerweb.fabrikam.com/sites/Project2
https://intranet.fabrikam.com/facilities
https://remotepartnerweb.fabrikam.com/sites/Project3
https://intranet.fabrikam.com/purchasing
Extranet https://partnerweb.fabrikam.com/sites/Project1
https://partnerweb.fabrikam.com/sites/Project2
https://partnerweb.fabrikam.com/sites/Project3
Zone Policies Zone Policies Zone Policies Zone Policies
Policies Intranet Partner accounts = Deny All Intranet Partner accounts = Deny All Intranet Partner accounts = Deny All Zone Policies Internet All users = Deny Write
None
Intranet Authors = Full Control
Default Partner accounts = Deny All Default Partner accounts = Deny All Default Partner accounts = Deny All Testers = Deny Write
Default Authors = Full Control
Testers = Deny Write
© 2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.

41. Strive for Accountability
• Technical architecture depends on the quality of
its inputs
• We can use the drivers/constraints model and
functional map to elicit inputs (along with
governance, etc.)
• If you get consensus, you need to be able to
deliver
• Accountability through ability to maintain SLAs

42. Thoughts
• Be deliberate with constraints
– Your constraints may prescribe a different model
– May open up alternative deployment scenarios
• Hosting
• Office 365
• Limit customizations
• Push for clear drivers, watch for driver creep
• Push for a clear governance plan

43. General Technical Guidelines
• Avoid multiple content databases per application
– Unless you have a solid strategy for site collection
partitioning
– Unless you have a high-capacity storage scenario
• Consider multiple applications (process isolation),
especially for heavily customized applications
• Use a dedicated SQL Server environment
• Consider dedicated, fault-tolerant load balancing
early—both internal and external

44. Contact Information
Arthur Savage
Arthur.savage@perficient.com
Micah Swigert
micah.swigert@perficient.com
twitter: @micahswigert