2016 urisa track: challenges to implementing an enterprise landbase maintenance program by patrick...

Challenges to Implementing an Enterprise GIS Landbase Maintenance ProgramSeptember 21-22, 2016

2

• Introduction• Challenges & Mitigation Strategies

– Organization– Data Content– Processes– Data Quality– Data Presentation– Technology– Governance– Lessons Learned

Excergy CorporationProprietary and Confidential

Overview

3

• Enterprise GIS Landbase Context– GIS data backbone

• Define• Establish• Maintain• Utilize

– Essential component of GIS Project and/or Enterprise GIS Program

– Techniques and strategies used in support of landbase maintenance program


Introduction

-4-

Utility Conflation Project Example

Consolidated GIS

Oracle SpatialData Repository

Data Consolidation & Conflation Process(Tools – TruShift, IGEMS)

Michael BakerLandbase

(parcel, Imagery)

Landbase Solution

Utility GISData Model

Facility Inventory

Maps(FIM)

Sanders Maps Quad Maps

TransmissionCircuit Maps

Tower DataSheets

Transmission

Plot Plan

One Line(Hi & Low)

Substation

RealProperties

GISData Set

SAPAsset

ReferenceData

LIDARData

5

• Source Selection Criteria– Completeness– Geographic Coverage– Vintage– Accuracy– Resolution

• Data Conversion Specifications– Data Source Matrix– Scrub Procedures– Problem Area Resolution (PAR) – Quality Assurance / Quality Control


Landbase Source Selection

6

• Landbase Program Positioning– Option 1 – within information technology (IT)– Option 2 – part of business unit– Option 3 – component of stand-alone group– Option 4 – external agency


Organization

7

• Resource Utilization– Centralized vs decentralized maintenance– Use of 3rd party resource– Use of contractor/temporary resources

• Regardless of Structure- Single instance of truth- Discourage and avoid separate silo’s

High Summit Partners Proprietary and Confidential

Other Considerations

August 10, 2012

8

• Enterprise Land Data Requirements– Contiguous coverage of service territory

– Support map product creation (rendering)

– As location reference to support facility placement

– Base and/or content for taxation reporting

– Support data analysis and viewing

– Geocoding and address matching

– Minimal security and access restrictions

– Imagery and derived products

– Applicable to multiple user groups within and outside organization


Data Content

9

• Landbase Categorization– Enterprise vs project data vs business data– Types

• Cadastral• Administrative• 3rd Party Subscription• Imagery


Data Content

10Excergy CorporationProprietary and Confidential

Landbase Layers ExampleUtility Company Landbase Features

COTS / Base Utility Specific 3rd Party Subscription

County PolygonsEasement PolygonsLandmark PolygonsLandmark PointMunicipal PolygonsParcel CentroidsParcel PolygonsPLSS Section PolygonsPLSS Section TicsPLSS Special SurveyPLSS Township PolygonsRailroadsRights-of-Way (ROW) PolygonsStreetsStreet SurfacesState PolygonsTax District PolygonsWaterbodyWatersegmentZip Codes

Baseline RegionsDistrictsPWRD DivisionsPWRD RegionsPWRD SectorsService TerritoryService Center LocationsTroublemen GridsWork Location GridsSanders Map IndexHigh Fire Hazard AreaUtility Mapping GridGrid Operation ZoneAccess RoadsTransmission ROWTrans ROW AnnotationDrafting TextDrafting PointDrafting PolygonStreet Width CalloutsUtility BuildingsSub Parcel OccupationCurb LineUnderground Ordinance BoundaryUtility Right-of-Way

CEC Climate ZonesBLM National Forest BoundaryBLM Public Land OwnershipBLM Wilderness AreaFarmlandsSCAG General PlanSCAG Land UseUS Census BlocksUS Census TractsUS Census Metropolitan AreaLiquifaction AreasFault Lines APFault Lines CAFault Lines RivCoFault Lines VenturaCoFRAP Fire Threat MapFEMA Flood ZonesUSGS Topo Quad Index 24KThomas Brothers Page Grid

Frequency of Change

Annually or less

Quarterly or Bi-Annually

Monthly or Project Driven

Daily or Weekly

11

• How to keep up with parcel and street maintenance for large service territory?

– CAD – GIS interoperability to streamline inputs

– Change detection for global vs. localized uplifts

– Capitalize uplift every “x” number of years

– Timing in support of capital project and operation & maintenance activities


Challenge – Base Land Layers

County PolygonsEasement PolygonsLandmark PolygonsLandmark PointMunicipal PolygonsParcel CentroidsParcel PolygonsPLSS Section PolygonsPLSS Section TicsPLSS Special SurveyPLSS Township PolygonsRailroadsRights-of-Way (ROW) PolygonsStreetsStreet SurfacesState PolygonsTax District PolygonsWaterbodyWatersegmentZip Codes

12

• Business driven landbase layer maintenance?

– Same or different GIS platform used

– Conflation dependency mitigation– Service level agreement (SLA)

expectations for dependent layer updates

– Similar or related layer consolidation

– Unnecessary map gridsExcergy CorporationProprietary and Confidential

Challenge – Org. SpecificBaseline RegionsDistrictsPWRD DivisionsPWRD RegionsPWRD SectorsService TerritoryService Center LocationsTroublemen GridsWork Location GridsSanders Map IndexHigh Fire Hazard AreaUtility Mapping GridGrid Operation ZoneAccess RoadsTransmission ROWTrans ROW AnnotationDrafting TextDrafting PointDrafting PolygonStreet Width CalloutsUtility BuildingsSub Parcel OccupationCurb LineUnderground Ordinance BoundaryUtility Right-of-Way

13

• 3rd party reference layer refresh?

– Entire layer, no partial edit updates

– Schedule for refresh– Responsibility – IT vs Bus.– Clipping, dissolving, aggregation,

generalization, rasterization methodologies and responsibilities

– Metadata refresh


Challenge – Org. Specific

CEC Climate ZonesBLM National Forest BoundaryBLM Public Land OwnershipBLM Wilderness AreaFarmlandsSCAG General PlanSCAG Land UseUS Census BlocksUS Census TractsUS Census Metropolitan AreaLiquifaction AreasFault Lines APFault Lines CAFault Lines RivCoFault Lines VenturaCoFRAP Fire Threat MapFEMA Flood ZonesUSGS Topo Quad Index 24KThomas Brothers Page Grid

Landbase Change Process Inputs

Utility

Land

COTS

Base

3rd

Party

Microsoft Excel Worksheet

15

• Project or Data Based Approach– Mapper applies both asset/land edits– Separate mappers for land and asset edits

• Maintenance Work Types– Major or minor landbase change– Capital project driven edits– O&M corrections– Emergent work– Special projects– Accuracy and quality improvements– Special event – landbase parcel/street centerline

uplift

Maintenance Processes

Landbase Inputs and OutputsInputs

Data Prep.

Prod. Edits

Data QC

OutputsMissing/private

roads

Removed/relocated roads

Landbase Specification & SLA

Landbase Business Processes

Missing street names

New tract designs

Capital project land edits

Land correction requests (E2)

Annexations

Adhoc Updates to SCE Boundaries

SCE Access Road Edits

Trans ROW edits

Land Rights Check / Easements

3rd Party Sub. Layer Updates

Circuit Mapping

GEDM

Real Prop

Michael Baker

Enterprise GIS Landbase Team

(Infotech (R1/R2), SCE (R3)

GEDM

Real Prop

Other?

Updated SCE MB Landbase

Updated SCE Managed Landbase

MB COTS Refresh

Updated 3rd Party Sub. Landbase

SCE MB COTS Landbase Refresh

18

• Managing Editing Inputs– Work request form (paper, online, via WMS)– Minimum change source input criteria– Turnaround time (SLA’s)– Assessing related layer impacts– Updating metadata

• Feature specific – when feature last changed• Layer specific – when layer last edited• Job specific – what changed as part of job number


Data Quality

19

• Landbase Usage Quality Control– Content Presentation Guidelines

• Layer ordering and grouping• Layer naming conventions

– Best Practices for • Viewing – display scales• Plotting – map scale/paper sizes• Annotation – text display


Data Presentation

20

• Maintenance Applications– System of record– Topology dependencies– Long vs. short transaction management

• Viewing & Analysis Applications– Content delivery strategies using web services

(WFS, WCS, WMS)– Render real time versus providing static data


Technology - Applications

21

• Archival and Temporal Requirements– Lineage analysis (parcel mapping)– Support for project audit, reporting, and other time

stamp events• Configuration Management

– Relate table management (i.e. parcel number to parcel ownership)

– Tool tip labels– Metadata access and presentation– Layer name and attribute aliasing– Attribute filtering


Technology - Data

22

• Configuration Management (cont.)– Spatial indices maintenance– Layer grouping, ordering, display scales– Simple and complex query optimization– CRUD matrix (application by data layer)– Security and disaster recovery


Technology – Database

23

Technology - Integration


26

• Advisory and Steering Committee– Significant landbase change management

– Improvement optimization

– Layer consolidations and additions

– Special projects prioritization

– Guidelines, best practices, and standards

• Change Control Board– Artifact system of record

– New data layer creation

– Data layer removal

– Schema change approvalExcergy CorporationProprietary and Confidential

Governance

27

• New Landbase Team Struggles– CAD vs GIS Maintenance

• White space managed annotation layers vs dynamic labels derived from GIS feature attributes

• Making edits to copy in CAD and then uplifting replacement layer to GIS

– Seamless vs Tiled Landbase• Transaction editing by feature instead of map tile

– Time to Edit and Feature Accuracy • Data layer dependencies requires additional steps

to maintain topology • Relative vs. absolute accuracy for feature

placementExcergy CorporationProprietary and Confidential

Lessons Learned

28

• Vendor Assisted Edits– Difficult to coordinate with same layer edit

processes– Do not recognize related feature dependencies

unless edits made with data as reference– Edits made offshore require ongoing level of

QA/QC as additional process– Edits made by vendor with secure connection

(VPN, etc.) require coordination for providing source inputs


Lessons Learned

Questions

29 29

30

Thank You!

Patrick J. Noonan, GISP

Principal ConsultantExcergy [email protected]: 303-349-4267


mailto:[email protected]