Distributed Collaboration: Sharing Data with ArcGIS Enterprise

Caroline Wright & Hilary Curtis

Product Management and Engineering

Quick poll

• Using collaboration now?

• Familiar but haven’t implemented it?

• Completely new?

Agenda

• Overview of collaboration & examples

• Key terminology

• Demo: setting up a collaboration (administrative)

• Demo: sharing data (end user)

• Release highlights & roadmap

• Tips and tricks

Questions? Catch us after the session & at the showcase

Overview and examples

Problem statements:

• I need to work with other organizations on a project but I have no access to their data.

• I’m supposed to be helping other departments but I can’t see what information they’re working with.

• I have data in one environment but I need to be able to access it in another one.

What is distributed collaboration?

• Establishes a trusted connection with other ArcGIS Enterprise environments and ArcGIS Online

• Allows you to quickly and easily share data and information across systems

• Helps to provide a common operational picture of data and make it visible and usable across environments

With ArcGIS Online

Sharing to ArcGIS Online:

- Benefit from the scalability of a SaaS environment

- Manage data and items in ArcGIS Enterprise and keep it in sync with Online

- Example end users: contractors, seasonal staff, public access

ArcGIS Enterprise

ArcGIS Online

external, public sharing

internal,data management

and creation

With ArcGIS Online

Sharing from ArcGIS Online:

- Copy data collected using field apps, public surveys, etc.

- Send to Enterprise for QA

- Or just reference the data across environments for awareness

- Additional support for this coming in future releases

ArcGIS Enterprise

ArcGIS Online

field data collection

quality assurance and management

Between ArcGIS Enterprise

From many to one:

- Create an ongoing, centralized view of data in one environment

- Examples: corporate HQ or central office, project lead or organizer, state and national agencies

Central Office

Toronto

San Diego

London

SydneyCentralized view of data

Between ArcGIS Enterprise

From one to many:

- Distribute data from a central source to many satellite deployments

- Each can use the data copy in their own maps and apps

- Examples: during emergency management and response, to satellite offices

StateGIS Office

Planning

Police

Sanitation

Fire

Copy of data

Copy of data

Copy of data

Copy of data

Success stories

Three Rivers Park District

Challenge –Keeping data in sync between ArcGIS Enterprise and ArcGIS Online without duplicating efforts in both environments.

Solution –Distributed collaboration to support field data collection and public maps and applications. Data is managed in ArcGIS Enterprise and regularly syncs to ArcGIS Online.

One source of truth, multiple access points

State of Maryland

Challenge –Lack of centralized, authoritative datasets between state agencies; lots of interpretations of data.

Solution –Distributed collaboration to facilitate sharing data from the authoritative source (e.g. DoT) to other city agencies to ensure data accuracy, quality, and overall efficiency .

Reduces redundancy and erroneous data

Agency A

Agency B

Agency C

Agency D

Key concepts

Setting up a collaboration

• Creates the collaboration• Adds the guests

- Determines if guests can send, receive, or both

- Sends invitation file to connect

Host Guest

• Accepts the invitation file• Sends the response file• If sending on a schedule, determines

the interval (1 – 24 hours)

Both:

Link a group to share data

Determine if feature layers are copied or referenced

Trusted Collaboration

Convention Center

Department of Transportation

Convention Center

DoT

Group

Trusted Collaboration

Group

Workspace:Road Closures

Architecture of a collaboration

Convention Center

Department of Transportation

Convention Center

DoT

Group

Collaboration• Who is participating• Can we connect

Trusted Collaboration

Workspace• Can guests send, receive or both• Will items be shared immediately or on a schedule• Will feature layers be copied or referenced

Group

Workspace:Road Closures

Group• Transfers content• 1:1 with workspace

Group• Transfers content• 1:1 with workspace

Options for sharing feature layers

Convention Center

DoT

Group Group

Copy

• Creates a full copy

• Updates are synced on a schedule (1 – 24 hours)

Reference

• References the data in place

• Data is always current

• Requires login

Editing copied data

Convention Center

DoT

Initial share(copy all data)

Sync interval(deltas only)

Edit

Group Group

• Sync interval between 1 – 24 hours• New options to pause, resume, sync now

What items can I share using collaboration?

• Hosted feature layers

• Feature layers published by reference

from an enterprise geodatabase

• CSVs, Word documents, Excel files

• Shapefiles

• Tile packages, vector tile packages

• Web maps

• Web scenes

• Map services (by reference)

• Web AppBuilder apps

• Apps created from Esri templates

• New: Insights items (workbooks, pages, models, themes)

• New: Hosted feature layer views (copy)

• + more

Need to share other item types? Let us know!

Demo: setting up a collaborationAdministrative

Demo: sharing dataEnd user

Release highlights

Release highlights

10.7.x

(Released at 10.5; 10.5.1 with ArcGIS Online)

Subject to change

Roadmap10.5 – 10.6.1

• Share feature layers as copies

• Share web apps

• Content delete policy

• Sync status reporting for administrators

• Ability to sync now (on demand)

• Collaborate Insights items

• Copy hosted feature layer views

• Pause & resume sync

• Better identification of collaborated

content (badge, filter)

• Custom admin role for managing

collaborations

• Two-way editing

• Retain metadata & content categories

• Collaborate Operations Dashboards

Note: you will only have the features available to you at your release, regardless of the release other collaborators are using.

Tips and tricks

Who will be sharing data?

What data will be shared?

When should updates be scheduled?

Which organizations will be participating?

How will we manage content once we start sharing?

What are everyone’s goals?

Planning

Don’t be afraid to whiteboard!

Get administrators and users in each organization on the same page about goals & approach

Create an architecture that meets your needs

Agree on policies and data governance:

- Who can share

- Who can edit

- Who can access

- The end use and audience

Know what version of the software everyone is on

Understand the features & functionality available

- (Example: One Online organization at a time)

Review the technical documentation

Implementing

Using

Name your groups

something relevant

Take advantage of

badges and filters

Using

Before sharing:

• Fill out all item details

• Set your data up correctly (symbology, sync, etc)

After sharing:

• Monitor what has been added to groups (webhooks!)

• Keep an eye on sync processes

• Check delete protection on the item if desired

Resources

Resources

• Blogs

• Documentation

• Case study

• Whitepaper

• Showcase

Thank you!distributedcollaboration@esri.com