# US 2017/0286982 A1 · System and method for territory assignment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286982 A1
- Document ID: US20170286982A1
- Status: Published application
- Kind: A1
- Application number: 15/091,347
- Filed: 2016-04-05
- Published: 2017-10-05
- Earliest claimed: 2016-04-05
- Assignees: Veeva Systems Inc.
- Applicants: Veeva Systems Inc.
- Inventors: John Howard; Elie Challita; Gregory Barker; Alan Wang
- Web page: https://patentgrep.com/patent/US20170286982A1

## CPC

- G06Q 30/0205: {based on location or geographical consideration}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/29: Geographical information databases
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for managing territory assignment for a CRM system. Customer data may be loaded from the CRM system to a memory device and mapped to data fields of the memory device. Rides may be received and executed to process customer data to determine territory of each account in the customer data. The territory information may then be stored in a territory management database and synchronized to the CRM system and other CRM systems.

## Claims

### Claim 1

A method for managing territory assignment for a customer relationship management (“CRM”) system, the method comprising:
loading customer data from the CRM system to a memory device, wherein the customer data comprises account information and wherein the account information comprises names and addresses of a first account and a second account;
receiving a first rule for territory assignment for a first territory, wherein the first rule comprises a first rule criterion for defining accounts in the first territory;
receiving a request for executing the first Me to process the customer data;
processing the customer data with the frit rule to determine that the first account belongs to the first territory according to account information of the first account and the first rule criterion;
assigning the first account to the first territory; and
storing the first territory as the first account's territory information in a territory management database.

### Claim 2 (depends on 1)

The method of claim 1, further comprising: associating a first user with the first territory.

### Claim 3 (depends on 2)

The method of claim 2, further comprising: creating a user group for the first territory; and adding the first user to the user group for the first territory.

### Claim 4 (depends on 1)

The method of claim 1, further comprising: updating the CRM system with the first account's territory information from the territory management database.

### Claim 5 (depends on 4)

The method of claim 4, further comprising: updating a second CRM system with the first account's territory information from the territory management database.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first rule comprises a second rule criterion for defining accounts in the first territory.

### Claim 7 (depends on 6)

The method of claim 6, wherein the second rule criterion comprises a specialty of the account,

### Claim 8 (depends on 7)

The method of claim 7, wherein the first rule criterion and the second rule criteria are joined together to define the first rule.

### Claim 9 (depends on 1)

The method of claim 1, wherein the first rule comprises a third merle criterion for defining accounts in the first territory.

### Claim 10 (depends on 9)

The method of claim 9, wherein the third rule criterion comprises an affiliation of the account.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first rule criterion is defined by a first object.

### Claim 12 (depends on 1)

The method of claim 1, further comprising: displaying the first territory as the first account's territory information in a preview user interface before storing such information in the territory management database.

### Claim 13 (depends on 1)

The method of claim 1, further comprising: displaying a CRM synchronization history which includes data exchange history between the territory management database and the CRM system.

### Claim 14 (depends on 1)

The method of claim 1, further comprising: mapping data fields in the customer data to data fields in the memory device.

### Claim 15 (depends on 1)

The method of claim 1, further comprising: receiving a second de for territory assignment fur a second territory.

### Claim 16 (depends on 15)

The method of claim 15, further comprising: processing the customer data with the second rule to determine that the second account belongs to the second territory.

### Claim 17 (depends on 16)

The method of claim 16, further comprising: assigning the second account to the second territory.

### Claim 18 (depends on 17)

The method of claim 17, further comprising: storing the second territory as the second account's territory information in the territory management database.

### Claim 19

A territory assignment system for a customer relationship management (“CRM”) systm, the territory assignment system comprising a territory management controller for:
loading customer data from the CRM system to a memory device, wherein the customer data comprises account information and wherein the account information comprises names and addresses of a first account and a second account;
receiving a first rule for territory assignment for a first territory and a second rule for territory assignment for a second territory, wherein the first and second rules are used to process the account information in the customer data;
processing the customer data with the first rule to determine that the first account belongs to the first territory;
assigning the first account to the first territory;
storing the first territory as the first account's territory information in a territory management database;
processing the customer data with the second rule to determine that the second account belongs to the second territory;
assigning the second account to the second territory; and
storing the second territory as the second account's territory information in the territory management database.

### Claim 20 (depends on 19)

The territory assignment system of claim 19, wherein the territory controller runs on an elastic computing platform.