This document discusses spatial master data management. It begins by introducing master data management and how the spatial dimension adds complexity. It then provides examples of utility asset management and transportation data management to illustrate spatial MDM challenges. The document outlines key elements of a spatial MDM solution using FME for data transformation and validation. It also provides examples of spatial MDM implementations and discusses getting started with a spatial MDM initiative.

4. Spatial Master Data Management
Dennis F. Beck, PE
President/CEO

5. Topics
• Introductions
– SBS
– Master Data Management
• FME and Spatially Enabled Master Data
Management
• Examples
• Getting started
• Value Proposition

6. About SBS
Delivering the power of spatial information
Proprietary and Confidential
Utilities Telecommunications Government
Lakewood, CO Melbourne, AU
Integration Data Solutions Strategic Consulting

7. What is Master Data Management?
• An architectural approach that supports consistent,
common and uniform data management across an
enterprise
• A non-trivial effort to implement across a large, complex
enterprise
• The spatial dimension adds even more complexity
• Perhaps best described as a “single version of truth” (or
a single reference point)

8. Why MDM? (Customer Domain Example)
• Multiple internal systems manage customer data
– Accounting
– CRM
– Call center
– Marketing
• Common problems can occur
– Sending “new customer” offers to existing customers
– Payment issues, multiple accounts
– Ultimately, dissatisfied customers and lost opportunities

9. Utility Asset Management Example
Numerous, disparate islands of data created during the asset lifecycle
Initiate Plan Schedule Execute Close
CAD GIS OMSWork Mgmt. Accounting Inspection
Records
Others
Operate

10. Transportation Data Management Example
Multiple systems that all use spatial information
Vegetation
Right-of-Way
Asset
Management
Managed
Maintenance
Environmental
Planning
Utility
Operations

11. Spatial Master Data Management Drivers
• Legacy GIS “center-of-universe” environments
– Extensive point-to-point interfaces
– Data models based on legacy product constraints
– Expensive upgrades
• Duplicate data entry
• Data integrity issues
• Lack of flexibility
• Limited functionality
• Not positioned for advanced applications, analytics and
the proliferation of IoT-based assets

12. Conceptual Spatial MDM Architecture
Proprietary and Confidential
GIS
CAD
Others
Asset Management
Planning
Operations
Reporting
Analytics
Mobile
Spatial Data Sources Enterprise Applications
Validation
Operational
Data Store
Data Integration
Transformation

13. Spatial MDM Solution Elements
• Software components
– Safe Software FME
– Data Transformation Framework
– Data Validation Framework
– Operational Datastore
• Consulting / services expertise
– Strategic consulting
– Data analysis
– Implementation expertise
FME
Transformation
Strategy
ODS Validation
Implementation
Analysis

14. FME Plays a Key Role in Spatial MDM
• Advanced data transformation
– Canonical model support
– Attribute modification / feature merging and splitting
– De-duplication (conflation)
– Relationship generation
– Network data model migration
• Difference management / interoperability
• Format support
• Validation

15. Data Transformation: Synchronization
• Geometric fidelity between platforms
– e.g. Bezier curves, NURBs and polylines
• Two-way transformations
– Advanced object configurations between different models
• Advanced topology support
– To/from vs node/link and extended network models
– Foundation for a network model of truth

16. Data Transformation: Internals
Substation cartographic plan (GIS)
Floor plan (CAD)
Schematic representation (DMS)

17. Data Transformation – Network Model
• Network-based organizations (e.g. utilities, pipeline,
telecoms and DOT) have multiple consumers of network
information
• Network modelling approach varies between systems
– Link / Node models
– To/From models
– Linear referencing
• Requires establishing common “network model of truth”
– Common, comprehensive network model
– Potentially requires inter-network transitions
• Opens up opportunities for network tracing to be a
service
Proprietary and Confidential

18. Data Validation: Example Cases
• The validation framework supports overall data integrity
for the ODS broad categories include:
– Intra-facility validation examples
• Attribute values in prescribed range
• Attribute combinations
• Relationship keys
• Geometric definitions
• Connectivity
– Inter-Facility validation examples
• Attribute look-up
• Parent-child evaluation
• Trace validation
• Peer relationship validation
Proprietary and Confidential

19. Data Integration via Job Management
• Different spatial systems enforce varying levels of control
over data
– Influenced by product / tools and implementation approach
– Culture can also be a major factor
– This can cause pervasive data management challenges if not
properly addressed
• The Job Manager is a mechanism to provide controlled
data stewardship
• Can be considered user-assisted data integration
• Works in conjunction with the data validation framework
Proprietary and Confidential

20. Job Management Overview
• Playback mechanism for
external projects
• Flags validation errors for
GIS data steward
• Goals of job management
– Ensure valid data is entered
into the system
– Minimize redrawing of data
• Particularly important for
CAD-based data
Proprietary and Confidential

21. Data Integration: Global IDs
21
• Global IDs provide an enterprise-wide identification
system that spans across specific products
• The Global ID serves as a look-up, linking the different
source features
• FME can be used as the notification framework during
the data synchronization process

22. Spatial MDM Architecture

23. Spatial MDM Architecture – ODS

24. Spatial MDM Example (1)
• 5 million customer US electric utility
• Existing Smallworld, Autodesk and Esri environments
• High profile business issues impacting safety, reliability and
compliance
• Key Activities
– Strategic consulting to address data management and conversion
approaches
– Implementation of FME Server and SBS software framework
– Population of conversion and production databases
– Data validation framework
• Key Benefits: Enabling source of new applications and interfaces
– Mobile
– Web
– Distribution Management
– Common Network Model from generation source to the customer

25. Spatial MDM Example (2)
• 7 million customer combined electric and gas utility
• Existing Smallworld, Bentley, Autodesk, Esri and IBM Maximo
environments.
• Issues related to data integration, duplication and system upgrades
• Key Activities
– Consulting to address process integration issues and define future state
architecture
– Design and implementation of spatial data store
– Population and validation of data store via use of FME server
– Job Manager integration framework underway
– New round of data consolidation underway
• Key Benefits: Application and interface enablement
– Mobile
– Web
– Vegetation management
– Integration to streamline asset management processes
Proprietary and Confidential

26. Spatial MDM: Smart Cities
• Local governments all over the world
• Wide variety of existing data sources.
• Issues related to data integration, duplication and
validation
• Key Activities
– Delivering data for third parties
– Data analysis for policy making
• Key Benefits: Application and interface enablement
– Mobile
– Web
– Integration to streamline city management processes
Proprietary and Confidential
Image Source: http://www.districtoffuture.eu/

27. Spatial MDM: Asset Analytics
Proprietary and Confidential

28. Asset Analytic Case Studies
Asset intensive industries leverage master data management
for strategic analysis
Proprietary and Confidential

29. Getting Started with Spatial MDM
• Establish a vision
– Yes, MDM is about the data, but…
– It’s really about the business
• Managing growth
• Streamlining processes
• Optimizing investments
• Reducing costs…
• Turn the vision into a roadmap
– Keep it strategic
– And measurable

30. Getting Started (2)
• Solve a practical, visible problem
– Don’t try to do everything at once
– Don’t overinflate
• Remember, MDM is not a product. It requires:
– People
– Processes
– Technologies
– Expertise
– Change management
– Governance
– And more…

31. Getting Started (3)
• Define your architecture, knowing it may evolve
• Engage senior stakeholders along the way
– They will retain interest when they see the opportunities
• Include MDM initiatives in the multi-year budgeting
process
• Keep it flexible – things will change
– FME can help with this

32. Why FME is Critical to Your MDM Efforts
• Robust support for spatial information
• Rich library of tools
• Flexible, customizable environment
• Highly cost-effective relative to many commercially
available MDM solutions

33. Spatial MDM Value Proposition
Proprietary and Confidential
Flexible Architecture
To respond and deploy faster
Streamlined Workflows Improved Productivity
Platform for Advanced
Applications
Reduce Custom
Applications
Improved Financial
Performance

34. For Further Information…
• Please contact us with further questions, or about how to
get started in the following areas:
– Strategic planning
– Consultancy
– Training
– Implementation
– Support
Dennis.Beck@spatialbiz.com
or…
Info@spatialbiz.com

35. Questions / Discussion