Presentation is loading. Please wait.

Presentation is loading. Please wait.

{Customer} Divisions Plan {Date} – {Version}

Similar presentations

Presentation on theme: "{Customer} Divisions Plan {Date} – {Version}"— Presentation transcript:

1 {Customer} Divisions Plan {Date} – {Version}

2 Meeting Goals Provide Baseline Overview of Divisions Review Divisions Plan & Testing To Date Sign-off from {Customer} on Divisions Plan

3 Topics Covered in this Plan Divisions –What are Divisions –Core Concepts –Affected Areas –Best Practices –Implementation Considerations Divisions for {Customer} –Strategy & Approach –Partitioning & Capacity Planning –Impact Assessment for End Users –Testing & Use Cases –Next Steps/Action Items

4 What are Divisions? Divisions allows organizations with large data sets to segment data into logical sections, delivering more optimal performance and usability to end users. The Divisions feature was released during the Winter 05 Release and is currently in deployment for some of salesforce.coms largest customers. Divisions is part of the VLO (Very Large Organization) product feature. Divisions is designed to scale up to 100,000 users from one organization based on data segmentation in the 1m range. Divisions will improve the search queries and results returned back to the users because the search will be limited to the end users division. Fundamentals: –Ability to create multiple divisions within one organization to increase performance and system management –Allows for searches, reports and list views to be more meaningful to end users. –Flexible user interface for setting up, transferring data and managing divisions.

5 Partitioned System with Divisions 1m1m 1m1m 1m1m 1m1m 1m1m 1m Global Organization Division A 2500 Users 8 Tabs 5 Administrators Division B 5000 Users 10 Tabs 10 Administrators Division C 500 Users 3 Tabs 4 Administrators Division D 2000 Users 15 Tabs 3 Administrators 500,000 records1 million records

6 Best Practices Partition Data into Logical Data Sets - Data should be divided into logical data sets that are meaningful to the end users. For example, if you organization has a North American sales team, the divisions could be partitioned into four divisions: East, Central, Midwest, West. Data Volume and Capacity Planning - Each division should be limited to 1 million records at the Account or Lead level, and capacity planning should be considered prior to the implementation of divisions. Testing and Rollout – Divisions should be initially deployed in the Sandbox environment and the implementation should be performed during non-business hours to minimize end user impact. Communication & End User Training – Communication plans should be established to communicate the changes to the user interface and end user training should be modified to educate users on best practices for optimizing their search results.

7 Implementation Considerations Once Divisions are enabled, the feature cannot be turned off for your organization. When divisions are enabled, one global division is automatically created for your organization and all records are assigned to that division by default. The default name for this division is "Global," which you may customize if you wish (e.g. All). Currently, an organization can create a maximum of 100 divisions, including any inactive ones. When you transfer divisions for accounts, all records related to a particular account, such as contacts and opportunities, inherit the division of that account. Page layouts and field-level security must be setup as appropriate. A users default division determines the division assigned to all new accounts and leads he or she creates, unless the user explicitly sets a different division. When users create records related to an account or other record that already has a division, the new record is assigned to the existing records division; the default division is not used. Remember to set the default division for all users, even those without the "Affected by Divisions" permission. Records created by users without that permission are still assigned to a division.

8 Divisions for {Customer}

9 Strategy & Approach Strategy: Organize data in the most logical format that minimizes user impact and enhances the users search experience –Provide flexibility for the long term, capacity planning, expansion –Ease of administration, management of divisions –Complies w/ Best Practices and recommendations Approach: –Partition and Organize Data: Divisions will be based on {Customer} Markets groups. This includes 32 - 35 groups, or {Customer} Markets. –Capacity Planning: Plan for growth and capacity w/in divisions. –Impact Assessment: Outline impact areas for end users. –Develop Process: Determine process for transferring divisions. –Testing: Test process and perform use case testing, comparing test cases in Sandbox against Production. –Training & Rollout: Develop communication plan, training and rollout divisions to the organization.

10 Capacity Planning Model

11 Capacity Planning Summary Model based on current data in {Customer} production org. Initial assumption for Model 1 is based on the average of each user having 300 Clients/Prospects and 5x Activities. Model 2 and 3 assume that data increases 2x and 3x, respectively. Users and divisions remain evenly distributed. In all 3 models, the data volume after divisions for each is within the recommended best practices. There are no cases in which Account Tab (or {Customer} Client/Prospects) records are greater than 1m for any division based on the original assumptions. If a division grows to data volume above the threshold, {Customer} will have the ability to break a division into 2 divisions. For example, New York Metro Market can be divided into NY Metro 1 and NY Metro 2.

12 {Customer} User x Market Breakdown Markets – {Customer} markets identified in Column 1 are the proposed divisions for the SFDC {Customer} production org. Active in Production - Data from {Customer} HR system provided TRUE – Active # of users in the SFDC {Customer} production org. Note: This does not match exactly due to inactive, test, etc. users. Grand Total – Estimated # of users (future state) in production with rollout to entire {Customer} user base. –13 markets > 1K users; may result in further partitioning in based on data projections. Note: #NA users moved into Other Category; need to determine who these users are.

13 Impact Assessment for End Users Home Page - Divisions drop box will appear on the Home Page for all users. Reports –When adding and/or modifying reports, the users will see and added step to specify division. –After opening a report, in the Report Options area, the user will see a drop box for divisions that should be defaulted to Current. List Views – When adding and/or modifying list views, the users will see and added step to specify division.

14 Divisions Setup Process Sandbox (Test Environment) 1.Refresh Sandbox (Test) Instance 2.Setup Divisions in Sandbox 3.Use DataLoader to perform mass update via API in Sandbox 4.Validate and test use cases Production 1.Contact to enable Divisions 2.Setup Divisions in Production 3.Communicate plan to end users 4.Use DataLoader to perform mass update via API 5.Validate and re-test use cases 6.End user communication and training

15 Testing Summary Developed 16 Test Cases. All Test Cases Passed. Compared Sandbox (with Divisions ON) vs. Production (with Divisions OFF). Tests Scenarios: –Creating Accounts –Search –User Lookups –Creating Activity Records –Reports –List Views –Data Loading 1 Feature Request for User Lookups

16 Testing Cases {Insert Test Cases – see Test Case example}

17 Next Steps/Action Items Validate Markets for Divisions including Users (HR Data File) Approval of Divisions Plan Develop Communication Plan for end users Modify Training Materials Set Launch Date & Finalize Rollout Plan

Download ppt "{Customer} Divisions Plan {Date} – {Version}"

Similar presentations

Ads by Google