Parcel Management System

This reference architecture represents a foundational Parcel Management System for a local or state government, or any other organization that manages parcel and cadastral data. It is based upon the data management and editing system pattern and designed for deployment with ArcGIS Enterprise on Windows or Linux. It includes support for management of 3D and 4D parcel data, including strata and subsurface information, ownership records, and agricultural and natural resource rights, using the ArcGIS Parcel Fabric.

Note:

This reference architecture represents an example blueprint for this system type. The design does not reflect the needs of all Parcel Management Systems, including those that may combine multiple system patterns.

Successful system design involves the selection of workflows used to define requirements as well as design both logical and physical architectures. This reference architecture is based on a specific set of workflows identified for Parcel Management Systems, which are described in the intended workflows section.

Capabilities

A foundational Parcel Management System delivers all capabilities as defined in the data editing and management system pattern. It focuses on delivery of parcel management capabilities that include:

  • Service-based editing of structured relational data stored in an enterprise geodatabase, including geometry, attributes, and relationships.
  • Data collection workflows using forms and maps in ArcGIS Pro, optimized for productivity.
  • Complex parcel fabric management using the ArcGIS Parcel Fabric as an advanced data model.
  • 3D and 4D parcel data management, including strata and subsurface information, ownership records, agricultural, natural resource rights and time-based information like ownership changes.
  • Interacting with, querying, and viewing the parcel fabric through web applications and experiences.

Software components

This reference architecture has been constructed using recent versions of the following ArcGIS software components. The system also supports connections from and interactions with other Esri software or client applications, but the workflows and testing of this system were focused on these components:

The role of each of these components is further detailed in the logical architecture.

Top