---
title: Test Study for a Parcel Management System (SQL Server)
description: Test study for a Parcel Management System in Azure on SQL Server
content_type: test-studies
source_url: "https://architecture.arcgis.com/en/architectures/parcel-management-sqlserver/tested-workflows.html"
md_url: "https://architecture.arcgis.com/en/architectures/parcel-management-sqlserver/tested-workflows.md"
---
# Tested workflows

To ensure that workflows are useful for system design purposes, they need to represent real user experiences, and the actual steps that users will take in interacting with the system. These workflows represent some of the foundational activities required to maintain and access parcel and cadastral data. The contents of the workflows were defined by working with experienced staff and Esri customers to identify the specific steps, sequencing and type of activities involved in each workflow.

Developing workflows as detailed, stand-alone sets of steps allows them to be repeated, iterated on, or adjusted to improve performance or user experience. Once each workflow is clearly defined, it is used consistently throughout the remainder of testing to establish the performance baseline and conduct load tests.

We worked with real customers and Esri experts to define these workflows to make sure they portrayed parcel information management tasks realistically. However, your organization’s workflows may have different or additional steps, like running a [Least Squares Analysis](https://pro.arcgis.com/en/pro-app/latest/tool-reference/parcel/analyze-parcels-by-least-squares-adjustment.htm).

If your organization does not have clearly documented, standard workflows with individual steps defined, consider using these workflows as a starting point that can be adjusted based on your needs. To learn more about documenting your systems’ workflows, see the blogpost describing how to [Unlock your ArcGIS system's ROI through workflow-centered design](https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/unlocking-your-arcgis-systems-roi-through-workflow-centered-design).

This implementation of the Land Information Management System’s reference architecture was load tested for the following eight (8) workflows:
- [Merge parcels](/en/architectures/parcel-management-sqlserver/tested-workflows.md#merge-parcels)
- [Split by metes and bounds](/en/architectures/parcel-management-sqlserver/tested-workflows.md#split-parcel)
- [Adjust boundary](/en/architectures/parcel-management-sqlserver/tested-workflows.md#adjust-boundary)
- [Import subdivision](/en/architectures/parcel-management-sqlserver/tested-workflows.md#import-subdivision)
- [Shrink to seeds](/en/architectures/parcel-management-sqlserver/tested-workflows.md#shrink-to-seeds)
- [Move parcels](/en/architectures/parcel-management-sqlserver/tested-workflows.md#move-parcels)
- [Summarize parcels](/en/architectures/parcel-management-sqlserver/tested-workflows.md#summarize-parcels)
- [View parcels](/en/architectures/parcel-management-sqlserver/tested-workflows.md#view-parcels)

These workflows support both editor and general [user personas](/en/framework/system-patterns/data-editing-and-management/overview.md#user-personas-and-workflows).

# Editor workflows

Editors maintain the geometry and attributes of the land parcels. Editors may range in expertise and overall comfort with technology, so having the steps documented can have a positive impact on their work. These workflows represent the work done to maintain parcel information.

### Merge parcels

Represents the set of steps an editor persona performs to combine two or more parcels into one.

1. Open Project
2. Locate tax name
3. Zoom to selection
4. Create and change version
5. Create record
6. Merge parcels
7. Toggle historic
8. Save
9. Reconcile
10. Post
11. Change version to default

### Split parcel

Represents the set of steps an editor persona performs to split a parcel using metes-and-bounds descriptions. 

1. Open Project
2. Locate Tax Name
3. Zoom to selection
4. Create and change version
5. Create Record 
6. Traverse edit
7. Create seeds
8. Build extent
9. Align Parcel
10. Clip Parcel
11. Update attributes
12. Validate topology
13. Error inspector
14. Save edits
15. Reconcile
16. Post
17. Change version to default

### Adjust boundary

Represents the set of steps an editor persona performs to adjust adjacent parcel boundaries.
1. Open Project
2. Locate tax name
3. Zoom to selection
4. Create and change version
5. Create record
6. Copy lines to record
7. Copy parallel
8. Delete old line
9. Validate topology
10. Save 
11. Reconcile
12. Post
13. Change version to default

### Import subdivision

Represents the set of steps an editor persona performs to import subdivision layout into the existing fabric.

1. Open Project
2. Create and change version
3. Locate
4. Zoom to parcel
5. Create record
6. Import subs
7. Copy lines to
8. Build active
9. Align parcels
10. Clip
11. Sequential numbering
12. Highlight
13. Validate topology
14. Save
15. Reconcile
16. Post
17. Change version to default

### Shrink to seeds

Represents the set of steps an editor persona performs to reduce complex polygons to their core “seed” points, making it easier to modify the lines that define parcels.
1. Open Project
2. Locate
3. Zoom to parcel
4. Create and change version
5. Select parcel
6. Activate record
7. Shrink to seeds
8. Select line
9. Delete line segment
10. Create parcel line
11. Reconstruct from seed
12. Validate topology
13. Save
14. Reconcile
15. Post
16. Change version to default

### Move parcels

Represents the set of steps an editor persona performs to shift several parcels to better align to a control network or aerial imagery.
1. Open Project
2. Manage record
3. Zoom to record
4. Create and change version
5. Select polygons
6. Move parcels
7. Build extent
8. Save
9. Reconcile
10. Post
11. Change version to default

# General user workflows

General users are typically considered “viewers” within the system and primarily discover and use content created by others within the organization. These workflows represent those that users perform to access and view parcel information to get answers to their questions and make decisions in their work.

### Summarize parcels

These steps represent a use case where an ArcGIS Dashboard is open on a screen and refreshes every 30 seconds.
1. Sign in to ArcGIS Enterprise
2. Open dashboard
 - Keep dashboard running for test duration
 - Layers are set to refresh every 30 seconds

### View parcels

Represents the set of steps a general user persona performs to query parcel information to find lots that match certain criteria.

1. Sign in to ArcGIS Enterprise
2. Open web application
3. Enter tax name in search
4. Zoom to tax parcel