Delivering Business Outcomeswith Information and Service Governance
danholmehttp://itunity.com/dan-holmedan.holme@itunity.com
Business Needs 
Technical Capabilities
Business Needs 
Technical Capabilities
Business Needs 
Technical Capabilities 
Supported Information Classes 
Information Architecture 
Information Management Policies 
Information Management Architecture 
Service Management Policies 
Service Management Architecture 
DEFINE 
DESIGN
Farm 
Web App 
Service App 
Zone 
Content DB 
Site collection 
Site 
List / Library 
[Folder] 
Item / Document 
Tenancy
http://intranet 
HR 
Finance 
Team 
Vacation Tracking 
Financial Performance 
Benefits 
Marketing 
Logos 
Expense Reports 
Team 
Team
People 
Process 
Policy 
Technology
Many components 
Together deliver
Business needs 
Technical considerations 
Cost 
Risk 
Risk 
Cost 
Tech 
Architecture = (Technical Expertise, Process, Compromise!) 
Architecture
Simple, Familiar ExampleEstablish Foundation
Define business needs 
Enumerate solution requirements 
Determine management options
Farm 
Web App 
Content DB 
Site collection 
Site 
List / Library 
[Folder] 
Item / Document 
Policy 
People 
Process 
Guideline
Farm 
Web App 
Content DB 
Site collection 
Site 
List / Library 
[Folder] 
Item / Document 
[Folder] 
Item / Document 
Policy 
People 
Process 
Technology 
Policy
Define business needs 
Enumerate solution requirements 
Determine management options 
Translate management polices to architecture
Guidance: Management & Architecture 
Establish policy 
Identify scope and control that supports enforcement 
Measure cost of enforcement vs. risk of non-enforcement: The Two (or More) ROI’s™ 
Return on Investment 
Risk of Inaction 
Risk of Inertia 
Risk of Inadequate Investment (ROI2)
SLAs
Geo-distributed performance 
Geo-distributed availability
Technical DetailsArchitecture Scenarios
Farm 
TEAMS 
Content DB 
Site collection 
Departments 
Engineering 
HR 
Scope(Site) 
Control
Farm 
TEAMS 
Content DB 
Site collection 
Departments 
Engineering 
Marketing 
Finance 
HR
Farm 
TEAMS 
Content DB 
Site collection 
Departments 
Engineering 
Marketing 
Finance 
Site collection 
HR
Farm 
TEAMS 
Content DB 
Site collection 
Departments 
Marketing 
Finance 
Site collection 
HR 
Site collection 
Engineering
Farm 
TEAMS 
Content DB 
Site collection 
HR 
Site collection 
Engineering 
Site collection 
Finance 
Site collection 
Marketing
Information Management Controls 
Service Management Controls 
Ownership 
Quotas 
Administration 
Sandbox Solutions 
Audit settings 
Device Channels 
Locks 
Features 
Search settings 
Other Controls 
User & group management 
DNSnamespace (HSNC) 
Sitecollection term sets 
SharePoint Designer restrictions 
Settings that enable policy-based management and therefore impact architectural decisions
Guidance: Policies & Settings 
Consider all possible policies and all available settings 
You must consider all possible policies and all available settings to make an informed decision about architecture for a particular workload or solution. 
It is unlikely you will be able to consider all policies and settings, and highly unlikely you will be able to manage to all policies. 
Do your best, make mistakes, and do better next time. 
Architecture = (Technical Expertise, Process, Compromise!)
Information Management Controls 
Service Management Controls 
Ownership 
Quotas 
Administration 
Sandbox Solutions 
Audit settings 
Device Channels 
Locks 
Features 
Search settings 
Other Controls 
User & group management 
DNSnamespace (HSNC) 
Sitecollection term sets 
SharePoint Designer restrictions 
Settings that enable policy-based management and therefore impact architectural decisions
Farm 
TEAMS 
Content DB 
Site collection 
HR 
Site collection 
Engineering 
Site collection 
Finance 
Site collection 
Marketing
Guidance: Site Collections 
In the COLLABORATION workload, separate site collections for each business unit, department, team, function or project support diverse requirements
Farm 
TEAMS 
Content DB 
Site collection 
Function 
Site collection 
Business 
Site collection 
Department 
Site collection 
Project
Farm 
TEAMS 
Content DB 
Site collection 
Work 
Site collection 
Each 
Site collection 
Unit 
Site collection 
Of
Guidance: Scalability Limits 
Be aware of limits and boundaries 
2010: http://technet.microsoft.com/en-us/library/cc262787.aspx 
2013: http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx 
Online: https://support.office.com/en-us/article/SharePoint-Online-software- boundaries-and-limits-8f34ff47-b749-408b-abc0-b605e1f6d498?ui=en-US&rs=en- US&ad=US
Farm 
TEAMS 
Content DB 
Site collection 
Function 
Site collection 
Business 
Site collection 
Department 
Site collection 
Project 
Farm 
TEAMS 
Content DB 
Site collection 
Top 
Business 
Project 
Department 
Function
Challenge 
Addressed By 
Navigation 
Custom or 2013 Managed Navigation 
Content Types 
2010 ContentType Hub 
Metadata 
2010Term Store 
ContentRoll-Ups 
2013 Analytics and Content by Search 
Content Publication 
2013Content by Search 
Administration 
PowerShell, Third-Party Tools
Guidance: Address the Challenges of a Distributed Architecture 
Challenges start with your second site collection 
Determine how to solve them early in your implementation
Farm 
TEAMS 
Content DB 
Site collection 
Function 
Site collection 
Business 
Site collection 
Department 
Site collection 
Project
SharePoint 2013Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET 
O365 Farm 
Critical Farm 
2010Farm 
LOB Farm 
SharePoint 2013 Clean Service Farm 
PROFILE 
SEARCH 
BCS 
METADATA 
DEV 
DevFarm 
BRANCH 
RemoteFarm
http://intranet 
HR 
Finance 
Team 
Vacation Tracking 
Financial Performance 
Benefits 
Marketing 
Logos 
Expense Reports 
Team 
Team
Farm 
TEAMS 
Content DB 
Site collection 
Function 
Site collection 
Business 
Site collection 
Department 
Site collection 
Project
Guidance: Content Databases 
Architect content databases based on STORAGE MANAGENT considerations: 
•Database size 
•Database management (backup, replication, etc.) 
•Performance (SQL instance) 
•Update (downtime during patching)
Farm 
TEAMS 
Site collection 
HR 
Site collection 
Engineering 
Site collection 
Finance 
Site collection 
Marketing 
Content DB 
Content DB 
Content DB
Information Management Controls 
Service Management Controls 
Backup and Restore SLAs 
Redundancy:mirroring, AlwaysOn 
Performance (SQLresources) 
Update Availability
Farm 
TEAMS 
Content DB 
Site collection 
HR 
Site collection 
Engineering 
Site collection 
Finance 
Site collection 
Marketing
Information Management Controls 
Service Management Controls 
Service Application Connections
Farm 
TEAMS 
Site collection 
Engineering 
Site collection 
Finance 
Enterprise Metadata 
EXTRANET 
ExtranetMetadata 
Site collection 
Clients
Information Management Controls 
Service Management Controls 
Service Application Connections 
DNS Isolation 
IISApplication Pool Isolation 
IISServer Assignment
Farm 
INTRANET 
TEAMS 
EXTRANET 
PEOPLE 
INTRANET 
INTRANET 
INTRANET 
TEAMS 
TEAMS 
TEAMS 
PEOPLE 
PEOPLE 
PEOPLE 
EXTRANET 
EXTRANET 
EXTRANET
Information Management Controls 
Service Management Controls 
Service Application Connections 
DNS Isolation 
IISApplication Pool Isolation 
IISServer Assignment 
Portability
Farm 
INTRANET 
PEOPLE 
TEAMS 
EXTRANET 
APPS
Farm 
TEAMS 
Content DB 
Site collection 
HR 
Site collection 
Engineering 
Site collection 
Finance 
Site collection 
Marketing 
TEAMS* 
Content DB
Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET
Guidance: Web Apps 
Within scalability limits (10-20 web apps per farm, 5-10 app pools per server), design to policies that are managed at the web app (and IIS site) scope. 
INTRANET 
COLLABORATION 
Gold / Locked Down / Clean 
Silver 
Bronze / Wild WildWest / Dirty 
EXTRANET 
SOCIAL 
APPS (all functional business apps) 
One for eachLINE OF BUSINESS APP 
Architecture = (Technical Expertise, Process, Compromise!)
Information Management Controls 
Service Management Controls 
Information Isolation 
Service Isolation 
Service Application Availability 
Code Isolation (Customizations) 
AccessIsolation 
SLAs
Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET 
O365 Farm 
Critical Farm 
LOBFarm
Information Management Controls 
Service Management Controls 
Information Isolation 
Service Isolation 
Service Application Availability 
Code Isolation (Customizations) 
AccessIsolation 
SLAs(and Easy Chargeback) 
Update & Upgrade
SharePoint 2013Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET 
O365 Farm 
Critical Farm 
2010Farm 
LOB Farm 
SharePoint 2013 Clean Service Farm 
PROFILE 
SEARCH 
BCS 
METADATA
Information Management Controls 
Service Management Controls 
Information Isolation 
Service Isolation 
Service Application Availability 
Code Isolation (Customizations) 
AccessIsolation 
SLAs(and Easy Chargeback) 
Update & Upgrade 
Licensing & Support 
Geo-Availability 
Geo-Performance
SharePoint 2013Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET 
O365 Farm 
Critical Farm 
2010Farm 
LOB Farm 
SharePoint 2013 Clean Service Farm 
PROFILE 
SEARCH 
BCS 
METADATA 
DEV 
DevFarm 
BRANCH 
RemoteFarm
Guidance: Farms 
Don’t ignore policies that are managed with settings scoped at the farm level. As resources allow, scale out farms. Document riskwhere you determine you can not manage to policies. 
Dev, Test, Staging, Production 
Extranet 
Public facing website 
Enterprise SharePoint services farm 
Clean, SharePoint 2013 
Search, Metadata, Social (User Profiles, My Sites), BCS 
Farm(s) for critical workloads 
Compliant, protected, available 
Premium farms for premium workloads 
LOB apps, BI, Project Management 
Remote locations 
Architecture = (Technical Expertise, Process, Compromise!)
Challenge 
Addressed By 
Navigation 
Custom or 2013 Managed Navigation 
Content Types 
2010 ContentType Hub 
Metadata 
2010Term Store 
ContentRoll-Ups 
2013 Analytics and Content by Search 
Content Publication 
2013Content by Search 
Administration 
PowerShell, Third-Party Tools 
Service Management 
PowerShell, Third-Party Tools 
Hard Costs 
Money
SharePoint 2013Farm 
INTRANET 
PEOPLE 
APPS 
<LOB> 
TEAMS 
TEAMS* 
EXTRANET 
O365 Farm 
Critical Farm 
2010Farm 
LOB Farm 
SharePoint 2013 Clean Service Farm 
PROFILE 
SEARCH 
BCS 
METADATA
Farms for service management 
Web applications for security isolation & management 
Site collections for content and solution management
One farm, one web application, one zone 
Flat topology with multiple site collections 
Use Host Named Site Collections (HNSC) 
Office 365: fewer site collections
Distributed Topology 
Farms & web apps 
Typical on-premise / hybrid 
Provides rich service portfolio 
Requires more resources 
Consolidated Topology 
One web app, HSNC 
Office 365 
Scalability 
Alignment with SP Online
Build SharePoint on-premiselike Office 365
In Sum
Business Needs 
Technical Capabilities 
Supported Information Classes 
Information Architecture 
Information Management Policies 
Information Management Architecture 
Service Management Policies 
Service Management Architecture 
DEFINE 
DESIGN
FOLLOW-UP SLIDES & MATERIALS 
Q&A AND DISCUSSIONLIVE ONLINE OFFICE HOURS 
MY ARTICLES & BLOG 
MY WEBINARS 
ITUNITY01 
dan.holme 
danholme▪ITUNITY01 
http://itunity.com/dan-holme 
dan.holme@itunity.com

Spca2014 holme outcomes with governance

  • 1.
    Delivering Business OutcomeswithInformation and Service Governance
  • 2.
  • 4.
  • 5.
  • 6.
    Business Needs TechnicalCapabilities Supported Information Classes Information Architecture Information Management Policies Information Management Architecture Service Management Policies Service Management Architecture DEFINE DESIGN
  • 10.
    Farm Web App Service App Zone Content DB Site collection Site List / Library [Folder] Item / Document Tenancy
  • 11.
    http://intranet HR Finance Team Vacation Tracking Financial Performance Benefits Marketing Logos Expense Reports Team Team
  • 12.
  • 14.
  • 15.
    Business needs Technicalconsiderations Cost Risk Risk Cost Tech Architecture = (Technical Expertise, Process, Compromise!) Architecture
  • 16.
  • 17.
    Define business needs Enumerate solution requirements Determine management options
  • 18.
    Farm Web App Content DB Site collection Site List / Library [Folder] Item / Document Policy People Process Guideline
  • 19.
    Farm Web App Content DB Site collection Site List / Library [Folder] Item / Document [Folder] Item / Document Policy People Process Technology Policy
  • 20.
    Define business needs Enumerate solution requirements Determine management options Translate management polices to architecture
  • 21.
    Guidance: Management &Architecture Establish policy Identify scope and control that supports enforcement Measure cost of enforcement vs. risk of non-enforcement: The Two (or More) ROI’s™ Return on Investment Risk of Inaction Risk of Inertia Risk of Inadequate Investment (ROI2)
  • 22.
  • 23.
  • 24.
  • 25.
    Farm TEAMS ContentDB Site collection Departments Engineering HR Scope(Site) Control
  • 26.
    Farm TEAMS ContentDB Site collection Departments Engineering Marketing Finance HR
  • 27.
    Farm TEAMS ContentDB Site collection Departments Engineering Marketing Finance Site collection HR
  • 28.
    Farm TEAMS ContentDB Site collection Departments Marketing Finance Site collection HR Site collection Engineering
  • 29.
    Farm TEAMS ContentDB Site collection HR Site collection Engineering Site collection Finance Site collection Marketing
  • 30.
    Information Management Controls Service Management Controls Ownership Quotas Administration Sandbox Solutions Audit settings Device Channels Locks Features Search settings Other Controls User & group management DNSnamespace (HSNC) Sitecollection term sets SharePoint Designer restrictions Settings that enable policy-based management and therefore impact architectural decisions
  • 31.
    Guidance: Policies &Settings Consider all possible policies and all available settings You must consider all possible policies and all available settings to make an informed decision about architecture for a particular workload or solution. It is unlikely you will be able to consider all policies and settings, and highly unlikely you will be able to manage to all policies. Do your best, make mistakes, and do better next time. Architecture = (Technical Expertise, Process, Compromise!)
  • 32.
    Information Management Controls Service Management Controls Ownership Quotas Administration Sandbox Solutions Audit settings Device Channels Locks Features Search settings Other Controls User & group management DNSnamespace (HSNC) Sitecollection term sets SharePoint Designer restrictions Settings that enable policy-based management and therefore impact architectural decisions
  • 33.
    Farm TEAMS ContentDB Site collection HR Site collection Engineering Site collection Finance Site collection Marketing
  • 34.
    Guidance: Site Collections In the COLLABORATION workload, separate site collections for each business unit, department, team, function or project support diverse requirements
  • 35.
    Farm TEAMS ContentDB Site collection Function Site collection Business Site collection Department Site collection Project
  • 36.
    Farm TEAMS ContentDB Site collection Work Site collection Each Site collection Unit Site collection Of
  • 37.
    Guidance: Scalability Limits Be aware of limits and boundaries 2010: http://technet.microsoft.com/en-us/library/cc262787.aspx 2013: http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx Online: https://support.office.com/en-us/article/SharePoint-Online-software- boundaries-and-limits-8f34ff47-b749-408b-abc0-b605e1f6d498?ui=en-US&rs=en- US&ad=US
  • 38.
    Farm TEAMS ContentDB Site collection Function Site collection Business Site collection Department Site collection Project Farm TEAMS Content DB Site collection Top Business Project Department Function
  • 39.
    Challenge Addressed By Navigation Custom or 2013 Managed Navigation Content Types 2010 ContentType Hub Metadata 2010Term Store ContentRoll-Ups 2013 Analytics and Content by Search Content Publication 2013Content by Search Administration PowerShell, Third-Party Tools
  • 40.
    Guidance: Address theChallenges of a Distributed Architecture Challenges start with your second site collection Determine how to solve them early in your implementation
  • 41.
    Farm TEAMS ContentDB Site collection Function Site collection Business Site collection Department Site collection Project
  • 42.
    SharePoint 2013Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET O365 Farm Critical Farm 2010Farm LOB Farm SharePoint 2013 Clean Service Farm PROFILE SEARCH BCS METADATA DEV DevFarm BRANCH RemoteFarm
  • 43.
    http://intranet HR Finance Team Vacation Tracking Financial Performance Benefits Marketing Logos Expense Reports Team Team
  • 44.
    Farm TEAMS ContentDB Site collection Function Site collection Business Site collection Department Site collection Project
  • 45.
    Guidance: Content Databases Architect content databases based on STORAGE MANAGENT considerations: •Database size •Database management (backup, replication, etc.) •Performance (SQL instance) •Update (downtime during patching)
  • 46.
    Farm TEAMS Sitecollection HR Site collection Engineering Site collection Finance Site collection Marketing Content DB Content DB Content DB
  • 47.
    Information Management Controls Service Management Controls Backup and Restore SLAs Redundancy:mirroring, AlwaysOn Performance (SQLresources) Update Availability
  • 48.
    Farm TEAMS ContentDB Site collection HR Site collection Engineering Site collection Finance Site collection Marketing
  • 49.
    Information Management Controls Service Management Controls Service Application Connections
  • 50.
    Farm TEAMS Sitecollection Engineering Site collection Finance Enterprise Metadata EXTRANET ExtranetMetadata Site collection Clients
  • 51.
    Information Management Controls Service Management Controls Service Application Connections DNS Isolation IISApplication Pool Isolation IISServer Assignment
  • 52.
    Farm INTRANET TEAMS EXTRANET PEOPLE INTRANET INTRANET INTRANET TEAMS TEAMS TEAMS PEOPLE PEOPLE PEOPLE EXTRANET EXTRANET EXTRANET
  • 53.
    Information Management Controls Service Management Controls Service Application Connections DNS Isolation IISApplication Pool Isolation IISServer Assignment Portability
  • 54.
    Farm INTRANET PEOPLE TEAMS EXTRANET APPS
  • 55.
    Farm TEAMS ContentDB Site collection HR Site collection Engineering Site collection Finance Site collection Marketing TEAMS* Content DB
  • 56.
    Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET
  • 57.
    Guidance: Web Apps Within scalability limits (10-20 web apps per farm, 5-10 app pools per server), design to policies that are managed at the web app (and IIS site) scope. INTRANET COLLABORATION Gold / Locked Down / Clean Silver Bronze / Wild WildWest / Dirty EXTRANET SOCIAL APPS (all functional business apps) One for eachLINE OF BUSINESS APP Architecture = (Technical Expertise, Process, Compromise!)
  • 58.
    Information Management Controls Service Management Controls Information Isolation Service Isolation Service Application Availability Code Isolation (Customizations) AccessIsolation SLAs
  • 59.
    Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET O365 Farm Critical Farm LOBFarm
  • 60.
    Information Management Controls Service Management Controls Information Isolation Service Isolation Service Application Availability Code Isolation (Customizations) AccessIsolation SLAs(and Easy Chargeback) Update & Upgrade
  • 61.
    SharePoint 2013Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET O365 Farm Critical Farm 2010Farm LOB Farm SharePoint 2013 Clean Service Farm PROFILE SEARCH BCS METADATA
  • 62.
    Information Management Controls Service Management Controls Information Isolation Service Isolation Service Application Availability Code Isolation (Customizations) AccessIsolation SLAs(and Easy Chargeback) Update & Upgrade Licensing & Support Geo-Availability Geo-Performance
  • 63.
    SharePoint 2013Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET O365 Farm Critical Farm 2010Farm LOB Farm SharePoint 2013 Clean Service Farm PROFILE SEARCH BCS METADATA DEV DevFarm BRANCH RemoteFarm
  • 64.
    Guidance: Farms Don’tignore policies that are managed with settings scoped at the farm level. As resources allow, scale out farms. Document riskwhere you determine you can not manage to policies. Dev, Test, Staging, Production Extranet Public facing website Enterprise SharePoint services farm Clean, SharePoint 2013 Search, Metadata, Social (User Profiles, My Sites), BCS Farm(s) for critical workloads Compliant, protected, available Premium farms for premium workloads LOB apps, BI, Project Management Remote locations Architecture = (Technical Expertise, Process, Compromise!)
  • 65.
    Challenge Addressed By Navigation Custom or 2013 Managed Navigation Content Types 2010 ContentType Hub Metadata 2010Term Store ContentRoll-Ups 2013 Analytics and Content by Search Content Publication 2013Content by Search Administration PowerShell, Third-Party Tools Service Management PowerShell, Third-Party Tools Hard Costs Money
  • 67.
    SharePoint 2013Farm INTRANET PEOPLE APPS <LOB> TEAMS TEAMS* EXTRANET O365 Farm Critical Farm 2010Farm LOB Farm SharePoint 2013 Clean Service Farm PROFILE SEARCH BCS METADATA
  • 68.
    Farms for servicemanagement Web applications for security isolation & management Site collections for content and solution management
  • 69.
    One farm, oneweb application, one zone Flat topology with multiple site collections Use Host Named Site Collections (HNSC) Office 365: fewer site collections
  • 70.
    Distributed Topology Farms& web apps Typical on-premise / hybrid Provides rich service portfolio Requires more resources Consolidated Topology One web app, HSNC Office 365 Scalability Alignment with SP Online
  • 71.
  • 72.
  • 74.
    Business Needs TechnicalCapabilities Supported Information Classes Information Architecture Information Management Policies Information Management Architecture Service Management Policies Service Management Architecture DEFINE DESIGN
  • 77.
    FOLLOW-UP SLIDES &MATERIALS Q&A AND DISCUSSIONLIVE ONLINE OFFICE HOURS MY ARTICLES & BLOG MY WEBINARS ITUNITY01 dan.holme danholme▪ITUNITY01 http://itunity.com/dan-holme dan.holme@itunity.com