Cross-Site BIM Collaboration

Jeff Herr, VP Sales

(310) 429-2000

jherr@panzura.com

www.panzura.com

One Project Team per Office

Complete set of skills required at each site

Collaboration works fine at each office

No collaboration between offices

Collaboration Challenge

Store project files at one site • Poor performance for remote users

• Simple to manage

Mirror project files between multiple sites • Manually reconcile versions of files

• Files get overwritten

• Lost productivity

Panzura Global File System

Centralized Storage + Global File System

• Single copy of project files available to all sites

• NO mirrors and NO waiting

• Simple to manage

• BONUS = DR + backups + archiving in the cloud

CAD Challenges (Civil3D, AutoCAD)

TIME…

Opening, Closing, and Saving Projects:

The “File Open Problem”

Reduced Productivity and Increased Costs

The Main Culprit

LATENCY…

File System Operations, Opens, Closes and

Saves, require Direct Contact to the Central

Storage

Enhancing Bandwidth Does Not Address

the File System Challenges

Project Size = 1.5MB

• Smallest File Chosen To Illustrate Problem

Round Trip Time 86ms

File Open and Lock Packets

4,508 (6.46min)

File Close and Unlock Packets

4,206 (6.03min)

File Look Up Packets

5,385 (7.72min)

Read Data Packets

1,004 (1.44min)

43ms

43ms

Civil3D Project with WAN Opt.

Total Time: 22 min

Civil3D Project With Panzura

Project Size = 1.5MB

Round Trip Time 0.56ms

File Open and Lock Packets

4,508 (2.52sec)

File Close and Unlock Packets

4,206 (2.36sec)

File Look Up Packets

5,385 (3.02sec)

Read Data Packets

1,004 (0.56sec) 0.28ms

0.28ms

Bonuses • Continuous Data

Replication and

Protection

• Bandwidth

Optimization

&Savings

One More Thing… • Consistent Multi-Site

Global Access

Total Time: 8 sec

Item CA to NY AZ to NY

File Size 1.5 MB 1.5 MB

Round Trip Latency 86 msec 66 msec

WAN Bandwidth 10 Mbps 9 Mbps

BEFORE

Time to Open Directly 22 min 16 min

Open Over Cold WAN Optimized Link 24 min 17 min

Open Over Hot WAN Optimized Link 20 min 15 min

AFTER

Open With Panzura 8 sec 8 sec

A 6Mbps link could move a 1.5MB file in 2 seconds, therefore

bandwidth is not the problem.

Panzura removed latency.

Example – Opening a Civil3D file

Test:

• 170MB File (Syracuse Airport)

• Revit Workshare

• Florida To New York

• 60msec latency

Results:

• 15-20 min Sync With Central

• Frequent Failed Sync With Central

• The More Users The Worse It Got

• Submittal Weeks: Full Of Failed Sync With Central

Side Effects:

• Local Copies And Conflicts

• Shadow IT

• BIM Coordination Nightmare

Revit Problem

User Edits

170MB

170MB

170MB

Up to 260 files

170MB

User Edits

User Edits

User

Edits

170MB

User

Edits

CENTRAL

SHARE

Sync With Central: 8 sec Write Always Local

Centrally Managed with Panzura

Continuous Data Protection

Revit Project with Panzura

CENTRALLY

MANAGED STORAGE

“Revit With Panzura Crazy Fast” Eric Wing, Author of “Autodesk 2013 Revit Architecture”, Autodesk Official Training Guide

Item FL to NY

File Size 170 MB

Round Trip Latency 60 msec

WAN Bandwidth 8 Mbps

Time For Sync With Central 16 min - never

Time For Sync With Central & WanOpt 18 min - never

Time For Sync With Central & WanOpt, 2 users 32 min - never

Time For Sync With Central & Panzura 8 sec

Time For Sync With Central & Panzura, 50

users 8 sec

Example – Sync With Central

Millions of Files

Panzura Secret Sauce

CIFS

NFS

AUTHORITATIVE STORAGE

\\CloudFS

\London\

\New York\

\Paris\

Millions

of Files

\\CloudFS

\London\

\New York\

\Paris\

\\CloudFS

\London\

\New York\

\Paris\

\New York\

\\CloudFS

\London\

\Paris\

META

META META

Global Locking

Reads And Writes Local

Q&A