Mobile GIS

Ted WadzinskiRuth HandsJason LinleyNoam Arbel

ESRI Electric & Gas User ConferenceOctober, 20002

Alliant-Energy UtilitiesOver 1,000 Community’s in Iowa, Wisconsin, Minnesota and Illinois.Customers:

Electric - 940,000Gas - 400,000Water - 20,000

FacilitiesElectric

43,000 miles of distribution10,000 miles of transmission

Gas8,800 miles distribution500 miles transmission

Alliant Energy Enterprise GIS

Work Management SystemSevern Trent STORMS

Outage Management

CES

Customer Service

System

System PlanningStoner Synergee

ArcFM Viewer

Reports/Infomaker

Corporate ERPPeopleSoft

Distributed GIS

SolutionsArcFM Viewer

ArcIMS

ArcReader

Standard Maps

Business

SolutionsEnvironmental

Economic Dev.

System Analysis

Shared Facilities

Gas Inspection Management

GISArcGIS/ArcFM

GIS Goal

To provide direct access to GIS to as many employees as possible

ArcFM Viewer on WAN - 700+ Users Mobile GIS – 200 Installations

Expected to grow to 450+Paper Maps – Reduce dependancyArcIMS – Future Direction

Emergency Response Crews

Line Construction Crews

Gas and Electric Inspection Crews

Contract Locating Crews

Alliant Has Extensive Mobile GIS Program

Challenge: Upgrade Mobile GIS to ArcGIS 8 TechnologyOld Environment

ArcFM Viewer V2.3Shapefiles and CoveragesCustom built extractionUpdates distributed on CD’s every 6 mo.No Editing with field units

ArcGIS 8 SolutionArcFM Viewer 8.2 and Arc ReaderPersonal GDBSMiner and Miner GDB extraction toolsTadpole-Cartesia GeoSync for updatesExplore GeoSync for editing in field

SoftwareArcFM Viewer 8.2

Used primarily for internal employeesSimilar configuration as dispatch center and engineering groupCustomizableExpensiveLarger computing requirementsMore functionality than required by most

Arc ReaderUsed by contract locators and some internal employeesFile are published using the ArcFM Viewer configurationCan not add custom functionsFreeSmaller computing requirements

Setting Up A Geodatabase Extract

SDE GDB

Pers GDB

Pers GDB

Pers GDB

Pers GDB

Extracts

The ArcFM Geodatabase Extract Tool

Allows for the (partial) export of a Geodatabase to a personal Geodatabase Can be used to produce multiple databases based on a polygon layerCan be run as an Arc Catalog tool

(Or through Arc Catalogue in the UK)

Can also be run as a command line toolUse in a batch file through cron/atCan be attached to a daily/periodic process

Extractor User InterfaceThe tool uses a template to define what to extractDefines a layer and field used to designate an area to extractThe resulting database may or may not contain a network.

For example, if using ArcReader, a network is not useful

All this (and more) can also be specified on the command line

The Template Database

The template database is used to define the schema to export

Contains empty tables for each table that needs to be extractedFor each table, the columns that are needed are defined

So for example, underground service locators will only need a database with underground features, with minimal attributes

Tables that seldom change, and do not need to be exported can be placed here as well

For example, landbase data

Differences from ArcGIS CheckoutSome benefits of the ArcFM Extraction:

Allows partial schema extractAllows different extracts based on modelnamesMultiple, predefined polygons to be extracted *Command line option *Creation of a non-networked PGDB

Benefits of the ArcGIS checkout tool:Allows checkin of data backNo template necessary

* Can be done using the ArcGIS CO but some custom coding is needed

Performance

While the extraction is not cheap, it is performed in reasonable timeframe

Extraction of a large metropolitan electric network, with ~100K services took ~45 minHalf of the Alliant Wisconsin Electric territory is extracted in 3 hours (~1.3 million records)Runs off a version, so can be done at any time without problems

Modify existing UML to create an extract template.

Only include feature classes and attributes that are pertinent to mobile users. I.e., delete data fields and feature classes you do NOT want to be extracted.

Add a new data field to all feature classes and objects called “GlobalObjectID”.

Change relationship classes that have ObjectID as the Primary Key to reference the new field, GlobalObjectID, rather than ObjectID.

Break up templates by facility class to minimize file size. Alliant created 4 templates:

Electric TemplateGas TemplateFacilities Land TemplateCommon Land Template

Modified UML

Create extract template geodatabase.

• Export the UML into a repository.

Create a template geodatabase in ArcCatalog.

Create the MM tables in your template and import any domains or properties from the production database.

Rebuild the network in the empty template database.

Assign the model name, ServerOID, to the new field added to the template, GlobalObjectId. (This model name tells the extract program where to copy the Production ObjectID in the extract database.)

Template Example

Create extract polygons.

Break up GDB’s by geographic zones to minimize file size. Alliant created two extract polygon feature classes:

Divided the service territory into zones for extracting electric, gas, and facility landbase features.

Created a single polygon which covers the service territory plus a buffer for extracting the common land data.

Assign the Object Model Name of GDBExtraction to the feature class that contains the extract polygons.

Assign the Field Model Name of GDBExtraction to the field within the feature class that will be used to indicate which polygon to use to extract the data.

Extract Polygon

Create Extract.

• Run the extract program.

When extract is complete, be sure to compress the mdb file. It usually compresses to half the original extract size.

SDE Database14GB

Multiple Personal

GDB’s3GB

Miner & Miner GDB Extract Tool Multiple

Personal GDB’s3GB

Multiple Personal

GDB’s3GB

Multiple Personal

GDB’s3GB totalTadpole Cartesia

GeoSync Updates

Data Maintenance Challenge

SDE GDB

Pers GDB

Pers GDB

Pers GDB

Pers GDB

Many Editors and Viewers

Extracts and Updates

Edits from the field?

GeoSync

Design considerationsKey concepts Implementation advantages

GeoSync’s fundamental designconsiderations:

1. Support of operational field use of GISWidespread useLarge number of users

2. Maintain ArcGIS integrityMaintain investment in developmentMaintain investment in data

Implications

Large enterprise-level deployment of dataOccasionally connected usersNeed for secure and reliable data transport

GeoSync BasicsBuilt on ArcObjectsSupports geodatabases (SDE or PGDB)Leverages ArcGIS versioning systemIncorporates Magi P2P technology

GeoSync

Design considerationsKey concepts Implementation advantages

The Big Picture

MagiMagi SDE or PGDB

Main SDE or PGDB

ArcGISArcGISArcGIS

ArcObjectsArcObjectsArcObjectsArcGISArcGISArcGIS

ArcObjectsArcObjectsArcObjects

Changes

GeoSyncGeoSyncGeoSync GeoSyncGeoSyncGeoSync

Foundation

• Built on ArcObjects• User interface in Visual Basic 6• Synchronization Engine in Visual C++ 6

• Designed to function properly within any customization that usesArcObjects

Synchronization Process

• Changes are written into a change packet• Options: proprietary binary format or XML

• Transportation via Magi P2P component• Secure / Reliable • LAN / WAN • Wired / Wireless

• Encoded in the packet is the sequence number• Packets sequence managed and ensured arrive

Change Management

• Leverage ESRI’s version management• Automate conflict handling• Manual conflict handling• Customized conflict handling

SDE – SDE

Default

V1 Shared

V2 V3 V4

SDE Database

Magi

Default(2)

Shared V5

V6 V7 V8

SDE Database

SDE – Personal GeoDB

Default

V1 Field

V2 V3 V4

ArcView

(PGDB)

SDE Database

Magi

ArcMap

(PGDB)

SDE – ArcReader

Default

V1 Field

V2 V3 V4

ArcReader

(PGDB)

SDE Database

Magi

GeoSync

Design considerationsKey concepts Implementation advantages

GeoSync Features

Multiple UsesSDE to SDESDE to PGDBPGDB to PGDB

Transfer changes by LAN, Internet, Wireless, Email…Site can operate as host and clientEach host can have many clients

Generic – built on ArcObjects

Supports all key data elements.

Network topologyRelationshipsComplex objectsEtc.

Incremental bi-direction synchronization of dataWorks in the back-ground of existing systems

GeoSync helps ….

Leverage GIS to the operational field force

Production GISDisconnected usersField friendly software

GeoSync Update ResultsTesting on 400 records affected by a feeder reconfiguration, a change packet of 117 KB was produced.

So…. if 10% of the GIS was similarly altered, the resultant change packet is ~ 40MB.

SDE Database14GB

Multiple Personal

GDB’s3GB

Miner & Miner GDB Extract Tool

Multiple Personal

GDB’s3GB

Multiple Personal

GDB’s3GB

Multiple Personal

GDB’s3GB total

Tadpole Cartesia GeoSync

~40 MB

Alliant Energy’s Challenge:

Deploying a production GIS to its field forceCapitalize on Software Advances to Improve Solution

The Results

Establish current goals and vision for futureA three-way partnership

Alliant EnergyMiner and MinerTadpole Cartesia

More effective solution with future opportunities

The End

Questions????