Data Collaboration Guide

Esri User ConferenceOctober 16, 2013

Debra Kelloway, York RegionSteve Grise, Vertex 3 Inc.

YorkInfo PartnershipA Guide for Data CollaborationQ&A

Overview

Pooling resources to reduce costs Decision-making on common source of information Working together to build GIS capacity Enabling access through technology

Valued relationships support broad information access

3

4

2014

Data sharing Framework

5

Challenge Solution

Cumbersome agreements

No self-serve environment

Non-standardized business data

Duplication

Enhancing a culture of collaboration

Draft

All Pipes single, integrated and shared

water and wastewater GIS database

faster, better, more consistent decisions and reporting

less expensive service delivery

Shared business data for joint service delivery

6

A draft guidebook for sustainable data sharing

Simple process Deliverables at each step 7 checkpoints

Looking for feedback and advice!

A Guide for Data Collaboration

7

Successful GIS Data Sharing

8

Operating Model Example Incentives

By-product of existing business processes

Region of Waterloo Roads and Addresses

Make it easy for partners to share data

Tool or application-driven

Arc Hydro Tools and data model

Meet business needs with tools and applications

Legal or Policy enforcement

US Critical Infrastructure Locations coordinated by US States

Legal compliance

Data Aggregation Business

Ontario Road Network and National Road Network

Provincial contract, Federal coordination

An increasing need for consistent, authoritative data from multiple partners

Regional data sharing Open Data programs Shared web applications

We are at a Turning Point

9Link: G8 2013 Official Documents

You are already good at sharing data

Maps/Location bring data together in new ways

Tools, culture , partnerships exist

Theory: GIS Professionals will lead the way

10

Fields Description Type Required ValuesRoadID Road Identifier Integer Yes Unique by

agencyName Road Name String Yes Concatenated

name, type, direction

RoadType Type of Road String Yes RoadType domain of values

LeftFrom Left From Address Integer No Not always present

LeftTo Left To Address Integer No Not always present

RightFrom Right From Address Integer No Not always present

RightTo Right To Address Integer No Not always present

… … … … …

Starting a Data Sharing Project

11

Burning Issues

Champions

Purpose

Readiness

Existing Best Practices

Team

Access and Use Constraints

Technology

Sustainability

Funding

Leadership Motivation Reducing data duplication and costs Providing relevant data from authoritative sources Moving towards Open Data Improving transparency Making fact-based decisions Avoiding embarrassment from conflicting decisions based

on different data Building applications that use common data models to

reduce costs expand the usefulness of applications Mandate or mission for change

Motivations

12

Staff Motivation Pain relief and/or improved satisfaction in daily work Applications and tools that will make tasks easier and more

efficient every day A clear indication of additional workload and a personal

understanding of costs and benefits Recognition and workload balancing from managers when

additional work is required Is this a by-product of existing work or is it new work? Understanding how work contributes to strategic goals of

the organization(s) Learning opportunities and personal growth

Motivations

13

Operational Manager Motivation Finding a practical balance Implementation Navigation

Motivations

14

Draft in 1 month Partner projects 6 months Final Model 1 year

Process

15

Draft Model

Projects Final Model

Project Leader/Coordinator Project Manager Project Sponsor

Subject Matter Expert(s) Technical Lead(s)

External Facilitator Project Teams/Partners Review Team Authors, Support

Team

16

Producers

Consumers

GAPSolutions

Define the Purpose – Initial Meetings Develop the Draft Design Conduct Your First Group Review Publish Draft Design Review Period Final Publication

Design Steps

17

Meets the essential information needs of stakeholders

Supports current and future needs Performs well Is simple to understand and easy to manage

A Good Shared Design

18

Draft Design Process

19

Information Products Information Needs

 Data Sharing

Model

MapsBasemapsOperational Layers

ReportsRequiredAdvanced/Novel

ToolsApplicationsFunctions

ServicesLayersFields

TablesFeature ClassesFieldsRules

A Guide for Data Collaboration available in draft form Request from Deb (debra.kelloway@york.ca) Commit to provide feedback in October

Documentation includes several project examples/templates Small/internal to one organization Medium scope, multi participants Larger scope, many stakeholders

Approach

20

Q&A

21

Data Collaboration Guide

Debra KellowayManager, GIS Partnerships

York Regiondebra.kelloway@york.ca

Steve GriséSolution Architect, President

Vertex3 Inc.steve@vertex3.com