Leveraging Cartegraph Data for the Management of Public Works Assets for the City of Grapevine

Size: px

Start display at page:

Download "Leveraging Cartegraph Data for the Management of Public Works Assets for the City of Grapevine"

Avis Tate
8 years ago
Views:

1 Leveraging Cartegraph Data for the Management of Public Works Assets for the City of Grapevine Presented By: Suja Joseph & Julie Paine Public Works City of Grapevine

2 Overview of Cartegraph System for the City of Grapevine s Public Works Department Running 3 software environments: Local desktop install: (for administrators) Cartegraph virtual server via remote desktop Laptop access via WIFI/aircard through VPN and remote desktop 7 departments: Administration, Engineering, Utilities, Streets, Storm, Traffic and Environmental 44 users of Cartegraph server 12 modules: Call Requests, WorkDirector, SewerView, WaterView, StormView, SignView, SignalView, PavementView, Construction Plans, STW Workorders, Liftstations/Pumps, Parking Lots

3 Leveraging Information for use with the Cartegraph system: Working with existing GIS assets The Cartegraph system was built specifically to address the needs of each individual department in Public Works. Since the City's GIS feature classes were a primary focus in using our new asset management system, existing water, sewer and storm datasets were imported into the Cartegraph system. Once imported into the applicable asset management module: WaterView, SewerView, and StormView; geodatabase connections were setup to maintain connection between Cartegraph and ArcGIS features Leveraging the geodatabase connection allows work orders to use applicable asset ids to designate work done in the field; thereby, allowing intranet maps to represent work history of specific assets

4 Leveraging Information for use with the Cartegraph system: Creating GIS assets For some departments, however, no GIS feature classes existed at the time of implementation. Therefore, the creation of several feature classes were tailored for the workforce and end user needs. Various methodologies were used in the creation of these new datasets. signs were GPSed signals were placed via a map by isolating intersections paving segments were generated from a centerline file and field verified and measured, parking lots were visually inspected with records and feature classes created after all field work was finished. STW work orders, construction projects and environmental work orders, contained address or XY fields which were used to create spatial point features.

5 How WorkDirector Works with GIS Call Requests and Work Director work off a street name list for work orders The street name list is set up to geocode on entry if a viable address is input into the work request and/or work order Some departments, such as Streets and Traffic input intersection locations Work orders and requests entered have an XY coordinate input into each record based upon a designated locator file XY fields are used for the intranet map to depict locations of requests and work orders

6 How the PavementView Works with GIS PavementView works from a segment file: An existing centerline file was taken and used to make a segment file The segments were broken at intersections (or material change,or width change) Once all segments were created, the geodatabase connection was made. Each segment was given a unique Cartegraph ID Each segment was field verified and measured Measurements were input in the PavementView module Geodatabase connections, along with the measurements and eventual inspection information allow the creation of spatial views

7 How the SignView Module Works with GIS SignView works off a point feature class: The original sign feature class has been a work in progress over the years Signs were first created to gather information about stop sign locations Over the years additional signs have been gps ed, for example: guide signs and other warning signs A decision was made to take the incomplete signs asset set and create a geodatabase connection into the Cartegraph environment This decision and implementation allows us to set the groundwork for inputting sign inspection data into the Cartegraph software, for eventual viewing in the mapping environment

8 How the SignalView Module Works with GIS SignalView also works off a point feature class: This feature class was created specifically to work with the Cartegraph asset module Signal points were created from spatial identification from aerial raster files Then, the signal feature class was connected into the module with a geodatabase connection This decision and implementation allows us to set the groundwork for inputting signal work orders into the Cartegraph software, for eventual viewing in the mapping environment

9 How the Parking Lots Module Was Integrated A parking lots module was created in Cartegraph to assess City maintained parking lots Parking lots were identified via a printed map Each parking lot was inspected and measured Once data was gathered, it was input into Cartegraph A parking lots feature class was created from the Cartegraph data, and now has a geodatabase connection in SDE

10 Setting Up Future Integration: STW Module STW Work Order system is the Utility Billing work order system: There was a need to see STW work orders in Cartegraph: A SSIS procedure was created to get the STW work orders These work orders are then imported into its own Cartegraph module An address field has been created in Cartegraph for the purpose of geocoding after import

11 How Integration Works: Creating the SQL View Create a Sql Svr view that joins Cartegraph asset information with work order information Leverage views to create map (spatial views) and read only data views Data views can be used in Microsoft Access or Excel Analysis and summary may be set up with pivot tables

12 Work Director Asset Designation Example: Cartegraph Data & Report Utilities - High Pressure Cleaning

13 Example of Pivot Table: Utilities - High Pressure Cleaning

14 Mapping Cartegraph Work Extend this same SQL Svr view by adding a spatial component Joins GIS geometry to Cartegraph asset information Maps Cartegraph Work Order & Inspection data Users can view & query the data in a spatial context via desktop ArcView or Intranet website

15 Advantages of a Spatial View Picture worth 1000 words Access all attributes from both sources Available to users as a SDE feature class Always current Users can perform queries and selections on the data Requires SQL Server & ArcSDE admin privileges to create or change

16 Example Spatial View in ArcServer: Utilities -High Pressure Cleaning

17 Organize the GIS Spatial View Joins GIS geometry to Cartegraph asset information Cartegraph Table View + GIS Asset SDE Spatial view

18 Example Spatial View in ArcServer: Utilities -High Pressure Cleaning

19 Example Spatial View in ArcServer: Streets Concrete Joint Seal Damage

20 Final Thoughts With a little planning and collaboration, GIS data can be viewable for work order and asset information No matter what stage of GIS implementation, there is a process that can help the transition between geodatabase connection and asset management When done correctly, the transition and geodatabase connection is seamless and transparent to the end user

ESRI and Xplore Technologies 2008 Mobile Government Demonstration Project Grant Program Final Report

ESRI and Xplore Technologies 2008 Mobile Government Demonstration Project Grant Program Final Report Introduction and Project Purpose The ESRI and Xplore Technologies Mobile Government Demonstration Project