Field Asset Data Collection and Integration with the Enterprise Database

Transcription

1 Incorporated Field Asset Data Collection and Integration with the Enterprise Database Marc Kratzschmar & Ian Martin 2011 GIS-T

2 Overview British Columbia asked for help Needed asset data collection application We developed a product extension Supports multiple instruments (GPS and DMI) Supports multiple, simultaneous edit streams Supports any Exor asset data model 2

3 Updating the Enterprise Asset Database Enterprise data maintenance challenge Update centerline geometry Update linear referencing routes Update assets along network Keep these synchronized New data collection is easy Existing data much harder to check out and update 3

4 Survey Approaches High Speed Survey Image collection and hand editing Software based collection, batch loading & location correction Windshield Survey Paper based collection and hand editing Paper based collection and batch loading Software based collection and batch loading Software based collection & automatic synchronization 4

5 British Columbia Big Province Small DOT: British Columbia Ministry of Transportation and Infrastructure Outsourced business model 24 Network Maintenance Contracts 5

6 Business Problem Enterprise asset database out of date: data and software District offices with different priorities and capabilities 2012 deadline 6

7 Solution Project to refresh enterprise database technology (Exor) Easy To Use Field Data Collection Software (GO! Sync Mapbook) Proven Commercial Product GIS User Interface Designed for Field Use Interface with GPS MoT enhancements Seamless Integration with Exor Check-out and check-in process Distance Measuring Instrument Support Network Editing Capability 7

8 Agile Development Process Driven by MoT District Staff Series of sprints Short timeline Discrete scope Focus on working software Iterative development Separated by scrums Review Revise Refocus 8

9 Field Data Collection Process Take Exor data into the field Update asset records Add network elements Check changed data into Exor database 9

10 Field Data Collection Process Flow Define a Project: Select area of interest and Assets 10

11 Field Data Collection Process Flow Define a Project: Select area of interest and Assets Download the map and asset data to the field computer 11

12 Field Data Collection Process Flow Define a Project: Select area of interest and Assets Download the map and asset data to the field computer Conduct the field survey: Update asset and route data 12

13 Field Data Collection Process Flow Define a Project: Select area of interest and Assets Download the map and asset data to the field computer Conduct the field survey: Update asset and route data Connect to the network and upload data 13

14 First step: set up in your office (or hotel or Starbucks) Then you select a route or area Then the assets you want to include in the inventory User defined project setup. Established projects can be reused or used as a template Secure access, adheres to Exor admin/security settings 14

15 Field Data Collection User Interface 15

16 Adding and Editing Asset Records Asset inventory maintenance begins with selection of an asset type 16

17 Adding and Editing Asset Records Existing assets can be selected from a list of nearby (within the proximity buffer) assets 17

18 Adding and Editing Asset Records Asset meta data and domain values inherited directly from TransInfo 18

19 Adding New Roads New routes or updated alignments can be captured via existing geometry or GPS location 19

20 Oregon Deployment Oregon DOT Implementing Exor Also Needs Field Data Collection Software Tested FDCU Business process differences Asked for enhancements 20

21 Summary Field data collection and asset inventory can be automated You can t replace experienced staff going into the field Process improvement is possible using asynchronous asset editing tools 21

22 Contact Us Marc Kratzschmar Bentley Systems, Inc Ian Martin TC Technology