how to leverage fme in a master data management architecture
TRANSCRIPT
How to Leverage FME in a Master Data Management Architecture
Dennis F. BeckPresident, Spatial Business Systems, Inc.
What We Will Cover Today
Introductions
What is Master Data Management (MDM)?
Master Data Management and spatial information
How FME supports spatial Master Data Management
Summary / conclusions
About Spatial Business Systems
Spatial integration firm based in Lakewood, CO
Primary focus on infrastructure-related markets
FME Gold-level reseller
Developers of lots of cool stuff with FME
What is Master Data Management?
An architectural approach that supports consistent, common and uniform data management across an enterprise
Perhaps best described as a “single version of truth” (or a single reference point)
A non-trivial effort to implement across a large, complex enterprise
The spatial dimension adds even more complexity
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
Spatial Master Data Management
Different, proprietary systems and models
Duplicate data
Different attributes
Different quality
Advanced spatial constructs
Geometric representations
Network models
Temporal data
Asset degeneration
Utility Asset Management Example
Numerous, disparate islands of data created during the asset lifecycle
Problems caused…
Duplication of effort / Redundant data entry
Data integrity issues
Extensive use of GIS-based point-to-point interfaces
Expensive upgrade costs
Hindrance from doing advanced applications
E.g. analytics, planning
The Role of FME
Data transformation
Canonical model support
Attribute modification / feature merging and splitting
De-duplication (conflation)
Relationship generation
Data sharing between products
But much more…
The Role of FME
Neutralizing different vendor systems, formats and organizational change management issues
Example: GE Smallworld internal worlds
Support for advanced spatial constructs (network models)
Validation framework
Difference management
Interoperability
Global IDs
Example: Internal Worlds
Substation cartographic plan (GIS)
Floor plan (CAD)
Schematic representation (DMS)
Global ID Model
GUID_REGISTRY
Repository / Mapping for each instantiated GUID
ODS Feature: Operational Data Store object where this object acts as a Primary Key
Source Feature: Identifier for the specific feature this data is brought over from, in the source system.
Source System: System where this data existed previously
Key: Unique Identifier for this record in the Source System, for the Source Feature object (These 3 values combine with the specific ODS Feature to form a Unique Index on GUID_REG)
The Global ID API is designed to leverage stored procedures in the ODS wrapped with ETL transformers
12
Don’t Forget FME Server…
Error handling with notifications via email, tweets, services logs
Web-based initiation, interaction and resolution of synchronization processes
Scalability
Flexibility to support future requirements
Spatial MDM Client Example
Spatial MDM Client Example (2)
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 commercially available MDM solutions
Value of Spatial MDM
Reduced upgrade costs
Streamlined workflows
Improved information to support advanced applications
Ability to respond and deploy faster
Cost savings
Thank You!
Questions?
For more information:
Dennis Beck [[email protected]]
Spatial Business Systems, Inc.