37

Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Embed Size (px)

Citation preview

Page 1: Spatial Master Data Management: Enterprise-level Spatial Information Architectures
Page 2: Spatial Master Data Management: Enterprise-level Spatial Information Architectures
Page 3: Spatial Master Data Management: Enterprise-level Spatial Information Architectures
Page 4: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Spatial Master Data Management

Dennis F. Beck, PEPresident/CEO

Page 5: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Topics

• Introductions– SBS– Master Data Management

• FME and Spatially Enabled Master Data Management

• Examples

• Getting started

• Value Proposition

Page 6: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

About SBSDelivering the power of spatial information

Proprietary and Confidential

Utilities Telecommunications Government

Lakewood, CO Melbourne, AU

Integration Data Solutions Strategic Consulting

Page 7: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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)

Page 8: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 9: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Utility Asset Management ExampleNumerous, disparate islands of data created during the asset lifecycle

Initiate Plan Schedule Execute Close

CAD GIS OMSWork Mgmt. Accounting InspectionRecords

Others

Operate

Page 10: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Transportation Data Management ExampleMultiple systems that all use spatial information

Vegetation

Right-of-Way

Asset Management

ManagedMaintenance

Environmental Planning

UtilityOperations

Page 11: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 12: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

Conceptual Spatial MDM Architecture

GIS

CAD

Others

Asset Management

Planning

Operations

Reporting

Analytics

Mobile

Spatial Data Sources Enterprise Applications

Validation

Operational Data Store

Data Integration

Transformation

Page 13: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 14: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 15: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 16: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Data Transformation: Internals

Substation cartographic plan (GIS)

Floor plan (CAD)

Schematic representation (DMS)

Page 17: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Page 18: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Page 19: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Page 20: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Page 21: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 22: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Spatial MDM Architecture

Page 23: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Spatial MDM Architecture – ODS

Page 24: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 25: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Page 26: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

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

Image Source: http://www.districtoffuture.eu/

Page 27: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

Spatial MDM: Asset Analytics

Page 28: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

Asset Analytic Case Studies

Asset intensive industries leverage master data management for strategic analysis

Page 29: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 30: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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…

Page 31: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 32: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

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

Page 33: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Proprietary and Confidential

Spatial MDM Value Proposition

Flexible ArchitectureTo respond and deploy faster

Streamlined Workflows Improved Productivity

Platform for Advanced Applications

Reduce Custom Applications

Improved Financial Performance

Page 34: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

For Further Information…

• Please contact us with further questions, or about how to get started in the following areas: – Strategic planning

– Consultancy

– Training

– Implementation

[email protected]

or…[email protected]

Page 35: Spatial Master Data Management: Enterprise-level Spatial Information Architectures

Questions / Discussion

Page 36: Spatial Master Data Management: Enterprise-level Spatial Information Architectures
Page 37: Spatial Master Data Management: Enterprise-level Spatial Information Architectures