GS 440 - It s Not Just a Smallworld Anymore Pat Reid Spatial Business Systems Autodesk Business Unit Director Dennis Beck Spatial Business System CEO
Class Summary Overview of integration issue Solutions for Smallworld to Autodesk Demonstration Spatial Gateway for enterprise-level environments
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
Why Integrate GIS and CAD?
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
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
ROI Study Integrating CAD and Smallworld
Five Year Cost Savings $3,000,000 $2,500,000 $2,423,798 $2,000,000 $1,500,000 $1,553,142 $1,000,000 $500,000 $329,436 $722,656 $712,319 $840,823 $870,656 $0 -$500,000 -$10,337 Year 1 Year 2 Year 3 Year 4 Year 5 -$339,773 Annual Net Savings Cumulative Net Savings
Data Accuracy Accurate CAD Data increases GIS accuracy CAD GIS Accurate GIS Data reduces Need for field validation
SBS Smallworld Integration
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
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
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
Process Flow What Theme Layer User Selection Trace, Query, Scrapbook How Grid New Activity Existing Design User Defined Where Connected Detached etransmit When On Demand Scheduled Job Server Task Write Direct Job Manager
Smallworld FDO Provider AutoCAD Map 3D AutoCAD Utility Design AutoCAD Topobase Retrieve data Analysis Publish to MapGuide WEB Browser Browse Search MG Studio Publishing Distribution DESKTOP MapGuide Enterprise APPLICATION SERVER Add Layout Tools Additional data Queries/Filters GE Smallworld DATABASE
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 Server image ACPT SOM VMDS VMDS WMS Spatial Datasets
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
SBS Smallworld Plug-in for FME SBS Plug-in Smallworld support: Smallworld geometry model Smallworld dimensions Annotation Multiple geometries Multiple worlds Version management Complex features Scalability via FME Server Stability Smallworld GIS Advanced application support Data synchronization Dynamic data access
DEMO FDO FME
Enterprise-Level Spatial Integration
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
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
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
High Level Architecture ODS, CDS, SDW 24
ODS Architecture 25
SDW Architecture 26
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
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., Inc. All rights reserved.