Transcript Class Summary

GS 440 - It’s Not Just a Smallworld® Anymore
Pat Reid
Spatial Business Systems
Autodesk Business Unit Director
Dennis Beck
Spatial Business System
CEO
© 2012 Autodesk
Class Summary

Overview of integration issue
 Solutions for Smallworld to Autodesk
 Demonstration
 Spatial Gateway for enterprise-level environments
© 2012 Autodesk
Learning Objectives
At the end of this class, you will be able to:
 Understand advantages of integrating CAD and GIS
 Understand difference of real-time integration vs. data translation
 Learn SBS/Autodesk solution for CAD/GIS integration
 Learn concepts of enterprise-level spatial integration
© 2012 Autodesk
Why Integrate GIS and CAD?
© 2012 Autodesk
Traditional Reason Not to Integrate

Too complicated!



Different approaches to the work



Technically
Organizationally
CAD operators utilize engineering precision to capture a single project
GIS captures broad concepts over large geographical areas
 GIS wants CAD accuracy, but hard to do over large areas
GIS/CAD systems have their own proprietary mechanisms for
interacting with product-specific application databases
© 2012 Autodesk
Impact of Non-Integration

Duplicate labor costs for double entry of data
 Backlog (or no) of As Built data
 Design and GIS data divergence




Impacts efficiency
Safety
Compliance
Potential exists for a major loss of data integrity
© 2012 Autodesk
ROI Study Integrating CAD and Smallworld
© 2012 Autodesk
Five Year Cost Savings
$3,000,000
$2,500,000
$2,423,798
$2,000,000
$1,553,142
$1,500,000
$1,000,000
$840,823
$870,656
$722,656
$712,319
$500,000
$329,436
$0
Year 1
-$10,337
Year 2
Year 3
Year 4
Year 5
-$339,773
-$500,000
Annual Net Savings
Cumulative Net Savings
© 2012 Autodesk
Data Accuracy
Accurate CAD
Data increases
GIS accuracy
CAD
GIS
Accurate GIS Data reduces
Need for field validation
© 2012 Autodesk
SBS Smallworld Integration
© 2012 Autodesk
Real Time Interaction versus Data Exporting

SBS has two solutions for integrating CAD and Smallworld GIS


FDO / SW Connector (Real-time)
FME / SBS Plug-in (Translation-based)

Both solutions allow for data translation on loading
 FDO supports Smallworld to Autodesk Map 3-D
 FME supports Smallworld to any source data
© 2012 Autodesk
Smallworld FDO Provider

Built on SBS SWConnector Technology


Uses C++ client library
Supports

Read/write access to feature data in a Smallworld VMDS data store

Describing schema and capabilities


Field types, Domains, Enumerators
Feature data editing
•
Select
•
Insert, Update, Delete

Coordinate System transformations

Disconnected processing

Long transactions
© 2012 Autodesk
SWConnector

Server Component

Built with Smallworld Magik

Supports Smallworld versions 3.1sp2->Current




Not all functionality supported at earlier releases
75+ Smallworld calls
Client Components

Delivered as C++ DLL, Managed C++ DLL (.Net) or Java (jar)

All clients use the same Server Component

Leverages Smallworld TICS protocol
Functionality

Full Read/Write capabilities for Smallworld data

Exposes vector VMDS and SOM geometry

Integrates with Schema, Authorization, Data, Topology, Styles, ACE etc.

Extensible by developers
© 2012 Autodesk
Process Flow
What
•
•
•
•
Theme
Layer
User Selection
Trace, Query, Scrapbook
How
•
•
•
•
Grid
New Activity
Existing Design
User Defined
Where
When
Write
• Connected
• Detached
• eTransmit
• On Demand
• Scheduled
• Job Server Task
• Direct
• Job Manager
© 2012 Autodesk
Smallworld FDO Provider
Browser
AutoCAD Map 3D
AutoCAD Utility Design
AutoCAD Topobase
•Browse
•Search
WEB
•Retrieve data
•Analysis
•Publish to MapGuide
MG Studio
Publishing
Distribution
MapGuide
Enterprise
DESKTOP
•Add Layout
•Tools
•Additional data
•Queries/Filters
APPLICATION SERVER
GE Smallworld
DATABASE
© 2012 Autodesk
SWConnector Architecture
AUD
Client
Autodesk
Utility Design
AutoCAD
Map Platform API
Smallworld
FDO Provider
SWConnector Client
(C++, .NET, Java API)
Server
SWConnector Server
Magik code,75+ supported API calls
TICS
ACPT
Server image
VMDS
VMDS
SOM
WMS
Spatial
Datasets
© 2012 Autodesk
FME Overview
Data Store
Data Store
FME
Extract,
Translate
Load
Data Store
Data Store
Autodesk AutoCAD
Autodesk AutoCAD Civil 3D
Autodesk AutoCAD Map 3D
Autodesk MapGuide
Autodesk Topobase
Bentley Map
Bentley MicroStation
ERDAS IMAGINE
Esri ArcGIS
Google Earth/Maps
Informatica PowerCenter
Intergraph GeoMedia
Professional
Intergraph GeoMedia WebMap
Intergraph G/Technology
MapInfo Professional
Microsoft Azure/OGDI
OpenSpirit
OpenStreetMap
Smallworld
Trimble
Over 200 supported formats
© 2012 Autodesk
SBS Smallworld Plug-in for FME
Smallworld support:
• Smallworld geometry
model
• Smallworld dimensions
• Annotation
• Multiple geometries
• Multiple worlds
• Version management
• Complex features
SBS Plug-in
Scalability via FME Server
Stability
Smallworld GIS
Advanced application
support
• Data synchronization
• Dynamic data access
© 2012 Autodesk
DEMO

FDO
 FME
© 2012 Autodesk
Enterprise-Level Spatial Integration
© 2012 Autodesk
Integrating Design in a Multi-GIS Environment

Large utility organizations often end up with multiple GIS solutions as
well as analysis and CAD packages

This is sometimes caused by mergers and acquisitions
 Sometimes it is just evolutionary
 Having multiple GIS solutions inhibits enterprise-level application deployment

Some of the key technical challenges





Cross-system integration
Conflict resolution, the “Long Transaction” problem
Data validation between systems
Global ID management
Amongst others
© 2012 Autodesk
Spatial Gateway: An Enterprise Approach

Spatial Gateway is a set of technologies designed to address the multiGIS / CAD integration issues for enterprise utility deployments
 “COTS” applications are leveraged to address many requirements




Oracle Spatial – common GIS repository
Workspace management – platform for
FME – spatial data extract-transform-load (ETL) capabilities
Specialty plug-ins and software extensions

Change detection
 Conflict resolution
 Common network modeling

Common application services, such as global ID management
© 2012 Autodesk
Terminology – Data bases

Application databases


Operational datastore


The operational database that includes staging models, metadata models, administration tables and the canonical
data store.
Canonical datastore


Databases used to support specific applications, e.g. Smallworld, Autodesk’s North American Data
Model, Esri, SAP, others
Application independent representation of the “Real World Objects” with mappings back to the application view of
the data
Spatial data warehouse

A consolidated view of the entire GIS database that is isolated from the changes occurring in the ODS. The
spatial data warehouse provides application specific data marts to support business requirements such as
analytics and temporal modeling
23
© 2012 Autodesk
High Level Architecture ODS, CDS, SDW
24
© 2012 Autodesk
ODS Architecture
25
© 2012 Autodesk
SDW Architecture
26
© 2012 Autodesk
ODS/CDS/SDW Design Considerations

Performance
 Data integrity
 Application independence
 Data isolation
 Architectural support for advanced applications



Network-based business requirements
Historical visualization
Meaningful analytics
27
© 2012 Autodesk
Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and
services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2012 Autodesk, Inc. All rights reserved.
© 2012 Autodesk