© 2012 Autodesk

GS 440 - It’s Not Just a Smallworld® Anymore

Pat ReidSpatial Business Systems Autodesk Business Unit Director

Dennis BeckSpatial 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! Technically Organizationally

Different approaches to the work 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

Year 1 Year 2 Year 3 Year 4 Year 5

-$500,000

$0

$500,000

$1,000,000

$1,500,000

$2,000,000

$2,500,000

$3,000,000

-$339,773

$329,436

$722,656$840,823 $870,656

-$339,773

-$10,337

$712,319

$1,553,142

$2,423,798

Annual Net Savings Cumulative Net Savings

© 2012 Autodesk

Data Accuracy

CAD GIS

Accurate GIS Data reducesNeed for field validation

Accurate CAD Data increases GIS accuracy

© 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• Theme• Layer• User Selection• Trace, Query, ScrapbookWhat• Grid• New Activity• Existing Design• User DefinedHow• Connected• Detached• eTransmitWhere• On Demand• Scheduled• Job Server TaskWhen• Direct• Job Manager

Write

© 2012 Autodesk

Smallworld FDO Provider

AutoCAD Map 3DAutoCAD Utility Design

AutoCAD Topobase•Retrieve data•Analysis•Publish to MapGuide

DESKTOP

Browser

WEB

GE Smallworld

APPLICATION SERVER

DATABASE

MapGuide Enterprise

PublishingDistribution

•Browse•Search

MG Studio

•Add Layout•Tools•Additional data•Queries/FiltersSWConnectorConnectivity API

FDO Provider

FDO Provider

© 2012 Autodesk

SWConnector Architecture

AUDClient

Server

VMDS VMDSWMS

SpatialDatasets

SWConnector ServerMagik code,75+ supported API calls

Server image

TICS ACPT

SWConnector Client(C++, .NET, Java API)

Smallworld FDO Provider

AutoCADMap Platform API

Autodesk Utility Design

SOM

© 2012 Autodesk

FME Overview

FMEExtract,TranslateLoad

Data Store

Data Store

Data Store

Data Store

Autodesk AutoCADAutodesk AutoCAD Civil 3DAutodesk AutoCAD Map 3DAutodesk MapGuideAutodesk TopobaseBentley MapBentley MicroStationERDAS IMAGINEEsri ArcGISGoogle Earth/MapsInformatica PowerCenterIntergraph GeoMedia ProfessionalIntergraph GeoMedia WebMapIntergraph G/TechnologyMapInfo ProfessionalMicrosoft Azure/OGDIOpenSpiritOpenStreetMapSmallworldTrimbleOver 200 supported formats

© 2012 Autodesk

SBS Smallworld Plug-in for FME

Smallworld GIS

SBS Plug-in

Smallworld support:• Smallworld geometry

model• Smallworld dimensions• Annotation• Multiple geometries• Multiple worlds• Version management• Complex features

Scalability via FME Server

Stability

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 multi-GIS / 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 Databases used to support specific applications, e.g. Smallworld, Autodesk’s North American Data

Model, Esri, SAP, others Operational datastore

The operational database that includes staging models, metadata models, administration tables and the canonical data store.

Canonical datastore 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.