GeoWorld

GeoWorld August 2013

Issue link: https://read.dmtmag.com/i/154401

Contents of this Issue

Navigation

Page 27 of 31

Public Lands consisted of two Esri products: Parcel Fabric and the Production Mapping suite of applications and tools. Esri's Parcel Fabric fit the specifications of the ROW as well as SLO business requirements. It offers tools and implicit spatial rules to create and maintain polygon data as a connected fabric of parcels (for more information on Parcel Fabric, see goo.gl/luTT6). Figure 3 shows an example ROW in the Parcel Fabric model. SLO decided to keep data maintenance in the same business department originally responsible, but operation staff there had little experience with creating GIS data. To overcome this knowledge gap as well as enable consistent and accurate data maintenance through time, Timmons Group implemented Esri's Production Mapping tools, allowing organizations with unique requirements to design workflows at business and GIS-editing levels. "The tools and processes developed as part of this pilot project will help us leverage our existing data and provide better business information to our clients and staff as we roll this out to a statewide effort," says Bill Baillargeon, SLO GIS manager. This eased the transition for SLO operations and IT staff into the new system, and it provided needed flexibility to adjust to changes in workflows or data through simple configuration changes. Workflow Manager for ArcGIS Server was deployed to assist with consistent and organized statewide field data flow and work-processes management. SLO District Resource Managers (DRMs), spread across the state, are responsible for field-data collection, analysis and reporting. This allows DRMs to access any workflows or processes, review all ROW notes and GIS data, create maps, and associate reports with data. The Workflows Timmons Group identified 10 unique ROW business workflows (e.g., new leases, amendments on existing leases and conveyances, etc.), and all these workflows had consistent elements. For example, every new ROW lease must include a field inspection. However, not every new ROW has the same GIS editing workflow. There are many variations on how to create the ROW based on available source data from the legal survey. For example, one road ROW may include only straight segments, while the next may include curves and a pipeline within the same corridor. Production Mapping tools were used to develop and manage all aspects of the ROW workflows. Business workflows were developed into Workflow Manager jobs and steps, while ROW data creation and editing workflows were developed in Task Assistant Manager. Data Reviewer batch jobs were developed to manage the data quality-control aspects of an ROW. Each ROW application submitted to SLO is created as a job within Workflow Manager and assigned to a Resource employee. Execution of the job workflow opens a specific map document and particular Task Assistant Manager that guides the georectification of the survey plat and ROW creation. Depending on the type of ROW application, the job may be reassigned to the DRMs for field verification and reporting accessed through Workflow Manager for ArcGIS Server. Afterward, the job continues through the rest of the GIS and business processes, such as quality analysis and quality control (QA/QC), manager approval, and ROW finalization. Integration Figure 2. The light-blue squares represent feature data derived from the ONGARD record, and dark-blue lines show the actual geometry from the legal description. Blue stars represent oil and natural-gas well locations. 28 G E O W O R L D / A U G U S T 2 O 1 3 The following five steps describe how an organization can logically design and implement processes using Esri's Production Mapping Suite. It's of utmost importance to develop these workflows and systems in a test and (if available) staging environment before deploying into an actual production. 1. Identify workflow origin. Pinpoint when the work actually starts and all the individuals and departments that interact with the workflow. For New Mexico, an ROW is started when lessees submit applications, which go through SLO's accounting department for fee collection/posting. The information then is sent to the ROW department for scanning. This application includes information about the lessee and land usage as well as a legal description and typically a survey or map of the ROW. Timmons Group created a Python script to check for new scanned documents at a predetermined interval. At this point in the process, the application programmatically becomes a job within the Workflow Manager system and is assigned to a Resource technician.

Articles in this issue

Links on this page

Archives of this issue

view archives of GeoWorld - GeoWorld August 2013