Sacramento Area Sewer District (SASD) chose AutoCAD Map 3D Enterprise as their solution for creating and editing their sewer assets. However, their Enterprise GIS is ESRI ArcSDE. Accordingly, they needed a solution for keeping these two disparate systems synchronized. In this presentation, you will learn how FME was used as the synchronization solution.
2. Summary
! Sacramento Area Sewer District (SASD) chose
AutoCAD® Map 3D Enterprise as the front-end
GIS application for creating and editing sewer
assets.
! However, SASD Enterprise GIS = ESRI® ArcSDE®.
! And, SASD Asset Management = Maximo.
! FME Desktop® was chosen as the solution for
synchronizing these disparate systems.
3. Synchronization Tasks
AutoCAD
Map
3D
Enterprise
(Oracle
DBMS)
ESRI
ArcSDE
(Sewer
Data)
ESRI
ArcSDE
(County
Base
Data)
Maximo
Asset
Management
Parcels,Roads, Cities,
etc.
Sewer Data
1 2
3
4. Synchronization Task 1
! Synchronize County Base data. Copy Edits
to AutoCAD® Map 3D Enterprise
! What do we have to work with?
! We neither know what has changed and
when it has changed
! Not as critical as sewer data.
! Full Table Comparison Required
5. Synchronization Task 1
! Solution
! UpdateDetector – Custom Transformer that
extends ChangeDetector
! Considerations
! Can take a long time.
! Geometry Comparison can be tricky.
! Attribute precision can create false positives.
! Comparing 100,000 features took minutes.
! Comparing 200,000 features took hours!?
! Split the data into chunks, run multiple
workspaces. WorkspaceRunner.
7. Synchronization Task 1
! It would be nice if…
! Feature edits are time
stamped via a trigger or
business rule.
! No need to compare for
edits.
! Editor Tracking easy to
turn on for ArcGIS
8. Synchronization Task 2
! Edits made in AutoCAD® Map 3D Enterprise must
be copied to ESRI® ArcSDE®
! Use Long Transaction Functionality
! Examples
! AutoCAD® Map 3D Jobs
! ESRI® ArcSDE® Versioning
! Using long transaction tables, we can query inserts,
deletes, and updates (IDU).
! Very fast. We are only querying the IDU’s in the
long transaction. No need to compare: we know
what’s changed.
9. Synchronization Task 2
! SQL Statements
and Where
Clauses
! Set long
transaction
current.
! Query inserts,
updates, and
deletes based on
long transaction
tables.
14. Batch Processing and Command Files
! User doesn’t need to open FME Workbench.
! Feed parameters (credentials, server names, db
names, job id, SDE version name) via command
files.
! Run workspaces in batch mode.
15. Null Attributes
! Prior to version 2014, FME Desktop® treated null
attribute values as non-existent attributes.
! This is problematic for synchronization. If a user
sets an attribute value to null, that change will
not be synchronized for an updated feature.
! My favorite new feature in FME Desktop® 2014?
Null Attribute Support!
16. Conclusion
! Synchronization
! Good – ChangeDetector
! Better – Use long transactions or editor tracking/
time stamping to query what’s changed
! Use 2014 for null attribute support
! Use command and batch files or FME Server to run
your synchronization tasks
17. Thank You!
! Questions?
! For more information:
! Drew Burgasser, P.E. (drew@cadmasters.com)
! CAD Masters, Inc.
! cadmasters.com (web site)
! thecadmasters.com (blog)
CONNECT. TRANSFORM. AUTOMATE.
18. Q/A Support: What is AutoCAD® Map
3D Enterprise?
! Product Name Evolution
! Autodesk® TopobaseTM <2011
! AutoCAD® Map 3D 2012 Enterprise
! AutoCAD® Map 3D 2013/2014
! Industry Model Functionality
! Enterprise GIS
! Uses FDO in AutoCAD®
19. Q/A Support: AutoCAD® Map 3D Job
Query Examples
! Query Inserted Features
! Query Updated Features
20. Q/A Support: Key Attribute for Sync
! Key Attribute required in both Systems