Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/TerrModeling.htm

## Modeling in Align

Align operational users can refine and optimize the alignment hierarchy without impacting production data. Using dedicated modeling records representing territories, field forces, and assignments, users can try out a variety of scenarios, assignment rules and criteria, or product and geography assignments to determine which ones best suit their business’s goals. This could be as simple as renaming territories or as extensive as rewriting an entire hierarchy’s Account Assignment Rule logic.

For example, an organization launching a new product in the next quarter can build out a model of their territories, assignment rules, and field forces in preparation for launch. Users can do this without affecting current production data or introducing an unapproved product to the sales team.

**Who can use this feature?**

* Align Operational Users – Browser
* [Managing Modeling Projects](#Managing)
* [Managing Model Territories and Field Forces](#Managing2)
* [Creating and Managing Model Assignments](#Creating)
* [Managing and Running Model Assignment Rules](#Managing3)
* [Publishing a Model](#Publishi)
* Users require an Align License

### Configuring Modeling in Align for

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

To configure this feature:

1. Ensure [Configuring Align](Configuration/ConfiguringAlign.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | aln\_account\_exclusion\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_account\_rule\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_account\_rule\_criteria\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_account\_search\_rule\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_account\_search\_rule\_criteria\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_account\_search\_rule\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_account\_search\_rule\_criteria\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_account\_territory\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_align\_settings\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_mapping\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_mapping\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_rule\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_rule\_criteria\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_rule\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_approval\_rule\_criteria\_model\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_field\_force\_group\_\_v | CRED | n/a | All Fields | Edit |
   | aln\_field\_force\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_field\_force\_product\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_footprint\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_footprint\_geography\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_geography\_territory\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_roster\_member\_territory\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_territory\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_territory\_footprint\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_territory\_product\_model\_\_v | CRE | n/a | All Fields | Edit |
   | aln\_project\_\_v | CRE | n/a | All Fields | Edit |
   | product\_group\_\_v | R | n/a | All Fields | Read |
6. Navigate to the **Tabs** section.
7. Grant access to the following tabs:

   * aln\_modeling\_\_v
   * aln\_settings\_modeling\_\_v

### Managing Modeling Projects as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

All modeling related actions and processes are accessed via the Modeling tab.

![](../../Resources/Images/Align/TerrModeling/TerrModeling.png)

Any page within this tab displays the text Modeling in a banner at the top of the page, ensuring users are always aware when they are viewing a modeling record.

From the Projects homepage in the Modeling tab, Align operational users can view, search, and sort all modeling projects.

From a specific project's All Actions menu, users can perform the following processes:

* Clone – Creates a copy of the project and its associated modeling records, including territories, field forces, rules, and manual assignments
* Delete – Deletes the project and all associated modeling records
* Change Lifecycle State – Manages the project’s state. Available values are:
* Draft – The default state
* Feedback Review – Indicates the project is in review
* Approved – Locks the project and all associated modeling records
* Published – Indicates the project is published to production. See [Publishing a Model](#Publishi) for more information.

### Managing Model Territories and Field Forces as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Within a project, users can create and manage model territories and field forces from their respective related lists.

#### Creating New Model Territories or Field Forces

To create a new model territory or field force:

1. Navigate to the **Model Territories** or **Model Field Forces** related list on the appropriate project.
2. Select **Create**.
3. Select either **Add a new territory to this model** or **Add a new field force to this model**.

   ![](../../Resources/Images/Align/TerrModeling/TerrModeling1.png)
4. Select **Continue**.
5. Populate all appropriate fields.
6. Select **Save**.

#### Importing Model Territories and Field Forces from Production

Alternatively, users can also create modeling records by importing existing production records:

1. Navigate to the appropriate related list on the aln\_project\_\_v record.
2. Select **Create**.
3. Select **Import territories from production**.

   ![](../../Resources/Images/Align/TerrModeling/TerrModeling2.png)
4. Select **Continue**.
5. Select the appropriate production territory or field force. The number of records to be imported displays.

   ![](../../Resources/Images/Align/TerrModeling/TerrModeling3.png)
6. Select either Yes or No for the **Import entire Division?** option. This option only displays if the selected territory or field force has descendants and enables importing the entire corresponding hierarchy as opposed to the individual territory or field force.
7. Select **Continue**.

#### Deleting a Model Territory or Field Force

To delete a model territory or field force:

1. Navigate to the appropriate modeling record.
2. Select the **All Actions** menu.
3. Select **Delete**.
4. Select **Continue** in the confirmation modal. The modeling record, along with all other associated modeling records, are deleted.

### Creating and Managing Model Assignments as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Users can create and manage the following types of assignments for their model territories and field forces using the same process as creating these assignments on production territories and field forces:

* Model Geography Assignments – Users can assign one or more model geographies directly to a model territory. See [Managing Geographies in Align](TerrAssignment/ManageGeo/Geography.htm) for more information.
* Model Footprint Assignments – Users can create model footprints from the corresponding aln\_project\_\_v record, then assign model territories or model geographies to the model footprint. See [Assigning Geographies to Footprints](TerrAssignment/ManageGeo/Footprints.htm#Assignin) and [Assigning Footprints to Territories](TerrAssignment/ManageGeo/Footprints.htm#Assignin2) for more information.
* Product Assignments – Users can assign products to model field forces or territories. See [Assigning Products to a Field Force](TerrAssignment/ProductAssignment/ProductAssignment.htm#Assignin) and [Assigning Products to a Territory](TerrAssignment/ProductAssignment/ProductAssignment.htm#Assignin2) for more information.
* Roster Member Assignments – Users can create aln\_roster\_member\_territory\_model\_\_v records to manually assign roster members to a model territory, including defining a primary model territory. See [Managing Roster Member Assignments](TerrAssignment/RosterMemberAssignment/RosterMember.htm#Managing) for more information.
* Model Explicit Account Assignments – Users can directly assign accounts to model territories by creating explicit account assignments. See [Creating Explicit Account Assignments](TerrAssignment/AccountAssignment/ManualAssignment.htm#Creating) for more information.
* Model Account Exclusions – Users can explicitly prevent a certain account from ever being assigned to a particular model territory or field force. See [Creating Account Exclusions](TerrAssignment/AccountAssignment/ManualAssignment.htm#Creating2) for more information.

### Managing and Running Model Assignment Rules as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Similar to [using Account Assignment Rules](TerrAssignment/AccountAssignment/AcctAssignmentRule.htm) on production Align records, users can create model account rules that automatically assign accounts to model territories or field forces:

1. Navigate to the **Model Account Rules** of the appropriate model territory or field force.
2. Select **Create**.
3. Populate all rule details and criteria using the same process as defining rule details and criteria on production Account Assignment Rules. See [Creating Account Assignment Rules](TerrAssignment/AccountAssignment/AcctAssignmentRule.htm#Creating) for more information.

#### Previewing Model Assignment Rule Results

To run model assignment rules and preview results:

1. Navigate to the appropriate model territory or field force.
2. Select the **All Actions** menu.
3. Select **Preview Account Assignments**.
4. Enter the following information:

   * Select the scope of territories – The scope of the preview. Available values are:
   * Territory + Subordinates – The preview runs against the selected model territory as well as all subordinate model territories
   * Territory Only – The preview runs exclusively against the selected model territory
   * Select the types of rules to process – Determines whether rules with a send\_to\_crm\_\_v field of yes\_\_v or no\_\_v are run by the preview
   * Select a date for which the assignment preview will be calculated – Determines the date used when generating assignments. Available values are:
   * Planned Publish Date – Assignments generate based on the associated aln\_project\_\_v record’s publish date
   * Current Date – Assignments generate based on the current date
5. Select **Continue**.
6. Select **View Results** from the resulting process task when the task completes. The Model Account Alignment Results page displays a preview of the assignments.

#### Committing Model Assignment Rule Results

To commit assignment results from the Model Account Alignment Results page, select Commit to Align. This process updates the aln\_account\_territory\_model\_\_v records to reflect the new alignment based on the preview.

### Publishing a Model as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Once modeled changes are approved, including all model records and assignments, user can then publish the model to the production alignment structure:

1. Navigate to the **aln\_project\_\_v** record.
2. Select the **All Actions** menu.
3. Select **Change Lifecycle State**.
4. Select **Approved**.
5. Select **Continue**.
6. Select **Confirm** on the confirmation modal. This locks the project and all its related model records from being edited.
7. Select the **All Actions** menu.
8. Select **Publish**. A confirmation modal displays with counts of each type of record affected by the publication.
9. Select **Continue**.

A Publish Project process task begins, which upserts the modeling records associated with the project into corresponding production records. These records can then be pushed to Vault CRM. Once pushed to Vault CRM, account, territory, and geography assignments as defined in the modeling project are applied to the main territory hierarchy in Vault CRM.

### Related Topics

[Using Account Assignment Rules in Align](TerrAssignment/AccountAssignment/AcctAssignmentRule.htm)

[Managing Geographies in Align](TerrAssignment/ManageGeo/Geography.htm)

[Assigning Roster Members in Align](TerrAssignment/RosterMemberAssignment/RosterMember.htm)