2016 urisa track: challenges to implementing an enterprise landbase maintenance program by patrick noonan
•Download as PPTX, PDF•
1 like•183 views
This document discusses challenges and strategies for implementing and maintaining an enterprise GIS landbase program. It covers organizational structure, data content and quality, processes, technology considerations, and governance. Key points include determining the appropriate organizational structure for landbase maintenance, establishing data content requirements and sources, developing workflows for inputting and quality checking edits, selecting applications to support editing and viewing, and setting up governance committees to oversee the program.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to 2016 urisa track: challenges to implementing an enterprise landbase maintenance program by patrick noonan
Similar to 2016 urisa track: challenges to implementing an enterprise landbase maintenance program by patrick noonan (20)
More from GIS in the Rockies
More from GIS in the Rockies (20)
Recently uploaded
Recently uploaded (20)
2016 urisa track: challenges to implementing an enterprise landbase maintenance program by patrick noonan
- 1. Challenges to Implementing an Enterprise GIS Landbase Maintenance Program September 21-22, 2016
- 2. • Introduction • Challenges & Mitigation Strategies – Organization – Data Content – Processes – Data Quality – Data Presentation – Technology – Governance – Lessons Learned Excergy Corporation Proprietary and Confidential 2 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 Excergy Corporation Proprietary and Confidential 3 Introduction
- 4. Utility Conflation Project Example Consolidated GIS Oracle Spatial Data Repository Data Consolidation & Conflation Process (Tools – TruShift, IGEMS) Michael Baker Landbase (parcel, Imagery) Landbase Solution Utility GIS Data Model Facility Inventory Maps (FIM) Sanders Maps Quad Maps Transmission Circuit Maps Tower Data Sheets Transmission Plot Plan One Line (Hi & Low) Substation Real Properties GIS Data Set SAP Asset Reference Data LIDAR Data
- 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 Excergy Corporation Proprietary and Confidential 5 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 Excergy Corporation Proprietary and Confidential 6 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 7 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 Excergy Corporation Proprietary and Confidential 8 Data Content
- 9. • Landbase Categorization – Enterprise vs project data vs business data – Types • Cadastral • Administrative • 3rd Party Subscription • Imagery Excergy Corporation Proprietary and Confidential 9 Data Content
- 10. Excergy Corporation Proprietary and Confidential 10 Landbase Layers Example Utility Company Landbase Features COTS / Base Utility Specific 3rd Party Subscription County Polygons Easement Polygons Landmark Polygons Landmark Point Municipal Polygons Parcel Centroids Parcel Polygons PLSS Section Polygons PLSS Section Tics PLSS Special Survey PLSS Township Polygons Railroads Rights-of-Way (ROW) Polygons Streets Street Surfaces State Polygons Tax District Polygons Waterbody Watersegment Zip Codes Baseline Regions Districts PWRD Divisions PWRD Regions PWRD Sectors Service Territory Service Center Locations Troublemen Grids Work Location Grids Sanders Map Index High Fire Hazard Area Utility Mapping Grid Grid Operation Zone Access Roads Transmission ROW Trans ROW Annotation Drafting Text Drafting Point Drafting Polygon Street Width Callouts Utility Buildings Sub Parcel Occupation Curb Line Underground Ordinance Boundary Utility Right-of-Way CEC Climate Zones BLM National Forest Boundary BLM Public Land Ownership BLM Wilderness Area Farmlands SCAG General Plan SCAG Land Use US Census Blocks US Census Tracts US Census Metropolitan Area Liquifaction Areas Fault Lines AP Fault Lines CA Fault Lines RivCo Fault Lines VenturaCo FRAP Fire Threat Map FEMA Flood Zones USGS Topo Quad Index 24K Thomas 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 Excergy Corporation Proprietary and Confidential 11 Challenge – Base Land Layers County Polygons Easement Polygons Landmark Polygons Landmark Point Municipal Polygons Parcel Centroids Parcel Polygons PLSS Section Polygons PLSS Section Tics PLSS Special Survey PLSS Township Polygons Railroads Rights-of-Way (ROW) Polygons Streets Street Surfaces State Polygons Tax District Polygons Waterbody Watersegment Zip 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 grids Excergy Corporation Proprietary and Confidential 12 Challenge – Org. Specific Baseline Regions Districts PWRD Divisions PWRD Regions PWRD Sectors Service Territory Service Center Locations Troublemen Grids Work Location Grids Sanders Map Index High Fire Hazard Area Utility Mapping Grid Grid Operation Zone Access Roads Transmission ROW Trans ROW Annotation Drafting Text Drafting Point Drafting Polygon Street Width Callouts Utility Buildings Sub Parcel Occupation Curb Line Underground Ordinance Boundary Utility 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 Excergy Corporation Proprietary and Confidential 13 Challenge – Org. Specific CEC Climate Zones BLM National Forest Boundary BLM Public Land Ownership BLM Wilderness Area Farmlands SCAG General Plan SCAG Land Use US Census Blocks US Census Tracts US Census Metropolitan Area Liquifaction Areas Fault Lines AP Fault Lines CA Fault Lines RivCo Fault Lines VenturaCo FRAP Fire Threat Map FEMA Flood Zones USGS Topo Quad Index 24K Thomas Brothers Page Grid
- 14. Landbase Change Process Inputs Utility Land COTS Base 3rd Party
- 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 15 Maintenance Processes
- 16. Landbase Inputs and Outputs Inputs Data Prep. Prod. Edits Data QC Outputs Missing/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
- 17. • 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 Excergy Corporation Proprietary and Confidential 18 Data Quality
- 18. • 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 Excergy Corporation Proprietary and Confidential 19 Data Presentation
- 19. • 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 Excergy Corporation Proprietary and Confidential 20 Technology - Applications
- 20. • 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 Excergy Corporation Proprietary and Confidential 21 Technology - Data
- 21. • 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 Excergy Corporation Proprietary and Confidential 22 Technology – Database
- 22. Technology - Integration Excergy Corporation Proprietary and Confidential 23
- 23. • 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 approval Excergy Corporation Proprietary and Confidential 26 Governance
- 24. • 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 placement Excergy Corporation Proprietary and Confidential 27 Lessons Learned
- 25. • 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 Excergy Corporation Proprietary and Confidential 28 Lessons Learned
- 26. Questions 29 29
- 27. Thank You! Patrick J. Noonan, GISP Principal Consultant Excergy Corporation pnoonan@excergy.com Ph: 303-349-4267 Excergy Corporation Proprietary and Confidential 30
Editor's Notes
- Importance of landbase maintenance as pertains to GIS Enterprise GIS emphasis as this is how landbase maintenance program will have greatest impact As I present, you might compare with your own landbase maintenance program to take stock of how far along you are with enterprise GIS maturity
- Shown to represent typical example of type of project I would work on to establish enterprise GIS landbase program. Conflation to capture, correct, fix data and then becomes important to establish new/updated maintenance processes to avoid another reconflate in 10 years or to plan for one in “x” number of years by design
- It is a challenge pulling data together to be part of a single consolidated landbase with different accuracy, vintages, coverage area, completeness, etc. On a large GIS project, it is common to develop what are called data conversion specifications to provide clarity. The specs will lay out data preparation procedures to ready the data, a data source matrix to show order for use if consolidating to single landbase, a problem area resolution process, and QA/QC procedures for accepting the data to the client environment. It is also common to see some level of ongoing maintenance support offered while the client gets its landbase organization up to speed.
- Requirements recognition important in defining purpose for landbase program – i.e. why you have an enterprise landbase program
- One of first challenges is in defining what is truly landbase from enterprise standpoint. I find it helpful to categorize the different landbase types as precursor to better discuss maintenance strategies
- Example from a utility company’s perspective
- Biggest challenge is keeping up with various inputs and land use processes that require parcel and street centerline changes (base map updates) Have looked at planning process for design tool CAD to GIS interoperability Change detection to prioritize areas needing error correction over others or as means to highlight focus areas Some programs do best they can and budget to uplift landbase to new vintage every 5,10,15 years Trick is ensuring timing for basemap creation/updates meets need of capital project and ongoing O&M less they find basemap alternatives (silo’s) Choice is empowering many staff with edit rights vs. having few specialists
- These layers are driven by project needs and typically are maintained (or inputs for derive from) by a number of organizations A challenge may be a desire to update on different GIS platforms. I find this difficult unless no conflation dependencies. SLA’s can be developed in time to set turnaround expectations for applying updates. This will expose other flaws in current process. There are conflation dependencies between layers – see reference spreadsheet showing an example
- Who will initiate service order to refresh if not triggered by internal project? Who will have responsibility to collect, preprocess (clip, aggregate like values, etc.) apply, QA, update metadata and publish changes to users. Since these layers are sourced externally, metadata needed to address user questions
- Interdependencies exist between landbase layers at some level. To better organize, after categorizing and addressing maintenance issues by grouping I start to look a layer specific dependencies using attached artifact.
- There are several types of maintenance work types, processes should be developed to acknowledge each separately. Each have different inputs and expected turnaround times Maintenance processes can be applied by many (minor change) vs major. Data type (land only, land/asset combinations)
- When moving from department to enterprise focused landbase, it is important to account for new customers and users that will be part of the enterprise. This diagram shows possible inputs, preparation, editing, QC, and outputs that in their entirety comprise the landbase maintenance processes.
- One process in particular that is difficult is when uplifting an entire new landbase data set, should this option be selected for select layers like parcels or street centerlines. An uplift is a project onto itself for a entity that has conflated multiple data sets (assets) to its existing landbase. It is important to understand the changes to gauge the level of effort that will be needed to update other dependent data, map products, application views, etc.
- Common complaint is inconsistency of work inputs that arrive to base mapping team are incomplete. To mitigate, formalize using some type of work request form. Can be paper, online, or via the work management system. Will help ensure minimum change source input criteria are met, can offer turnaround time based on criteria and can vary depending on work type. Will need to manage relative vs absolute accuracy as common theme. Relative position of feature to feature found to be more important than true position on ground. Survey will never be replaced using GIS data. Consideration to various metadata types depending on maintenance application and need.
- In time content consistency of landbase data will prove to help with data error and update requests. To this end, layer ordering and grouping consistency between applications with landbase maintenance team and user input is recommended. Layer naming conventions are important for consistency, especially if you deploy multiple vintages of the same data, etc. For performance, usability, view display scale thresholds are recommended for when the data appear as well as for best plotting, etc. Data presentation standards can also be enforced by default if you can have users consume landbase data using web services for example.
- Editing landbase in multiple applications is difficult unless done at layer level using system of record to denote which application can edit each. Still difficult for landbase though given likely conflation dependencies that may exist. Also juggling short/long transaction jobs/versions/alternatives can be challenging if intermingling systems. Other data maintenance applications can be plugged in as services called out from within or outside your organization. For example, geocoding, reverse geocoding, and address mapping services can be utilized to eliminate having to maintain data to support these functions. If you do this, know that you may need to explore performance and accuracy using various services for linear interpolation of addresses, parcel centroids, etc. against your own data to understand differences and confirm they are acceptable. Other landbase consuming applications include viewing and report analysis type applications which may be best served using services to render real time versus using replication.
- Do you need snapshots of the data at end of year, etc.? Support for project audit, reporting, and other time stamp events. Configuration management can cover a range of landbase elements – relate tables, tool tip preferences, metadata access (portal, via apps), etc.
- There may be change control considerations for schema changes, new data layer creation, data layer removal. Spatial indices may need to be rebuilt periodically for optimal performance, and capture of common simple and complex or nested queries can be helpful to standardize data interrogation activities within applications – point in poly, etc. Landbase layers should be referenced in any Create, Read, Update, Delete, Distribute type matrix as well. It may be possible to bundle the landbase layers by broad category in some cases (Base, 3rd party). As landbase becomes consumed as services, it will be important to pay attention to disaster recovery SLA alignment of the GIS and source DB with these consuming applications.
- In an enterprise GIS, the landbase can impact GIS interfaces used in which landbase is referenced with other data. These interfaces may need to be monitored as part of change control process for ongoing landbase changes. They also are part of SLA’s for data access.
- The enterprise GIS landbase team may maintain but not be data stewards. For an enterprise GIS, the landbase team should be included in ongoing strategic planning and have visibility for any organizational GIS user groups, as well as for user education, and training
- The organization GIS advisory or steering committee may have input on significant landbase change management – separating or consolidating transmission and distribution right-of-way, introducing new easement types, etc. Special projects to introduce access roads from recent capital projects, etc. and adjusting against a new imagery source within Transmission ROW. Another role may be to endorse or advocate concepts, usage, or maintenance that directly impacts landbase – guidelines for new layer inclusion, best practice for map output, and standards for metadata, etc.
- Have found introducing to organizations used to CAD based map making using tile areas have some significant change management considerations
- Special challenges should you decide to enlist vendor partners to assist with ongoing maintenance. If they are not onsite,…