Project Sharing ‘the ArchiCAD way‘. VW is 23 years behind

[Amorphous - Julian]

Way back in 1997, ArchiCAD introduced Teamwork, a file-based project sharing method, like how we have it in Vectorworks today.

 

In 2009, ArchiCAD ditched Teamwork and introduced BIMserver, a server-side project sharing management tool, allowing fast and simultaneous syncing.

In 2014, ArchiCAD introduced BIMcloud, which allows remote collaboration.
 

In 2019, ArchiCAD retired BIMserver, supporting only BIMcloud.

In contrast for us, it is year 2020, Vectorworks still ’project shares’ with the technology of Teamwork, Archicad ditched this method 11 years ago because of its problems.

 

Problems with file-based Project Sharing: Entire file needs to be synced (takes a long time, processing); Other team members are locked out during the sync process (waste of staff time); Constant file corruption and information loss (waste of time and soul destroying). This has been my experience, and I also verified this with someone who professionally maintains ArchiCAD systems for architects and saw through its ‘file-based project sharing’ era.

 

As both ArchiCAD and Vectorworks are Nemetschek brands, surely Vectorworks engineers can learn from the experiences of ArchiCAD engineers and implement BIMserver into Vectoworks quickly?

 

@Tolu @Julian Carr @JuanP @Biplab please close this 23-year technology gap with ArchiCAD on Project Sharing. We need to end project delivery disruptions due to the current method of Project Sharing.

 

Below is a video on ArchiCAD BIMserver and BIMcloud. Note time code 5:45 in the video:

‘BIMserver’s mulitherading architecture allows any number of clients to simultaneous sync....’

 

That’s really music my ears. With this feature, it would make Vectorworks scaleable for any offices and project size.

 

 

Following is my post documenting our office’s struggles with Vectorworks file-based Project sharing that began 6 months ago. The disruption caused by Project Sharing to our office has became unacceptable, and must change fast.

 

Thank you for your attention to this.

 

 

[Christiaan]

On 3/14/2020 at 4:52 AM, Amorphous - Julian said:

Problems with file-based Project Sharing: Entire file needs to be synced

 

This is true for Workgroup Referencing but Project Sharing offers delta-based syncing in most cases.

Edited March 15, 2020 by Christiaan

[Matt Overton]

ArchiCAD teamwork was built off fundamentally bad assumption - the sort that make you question if they ever were for Architects/Designers and really just for engineers (software ones) all along.  I see nothing that makes me think BIMCloud has reversed this.

 

That said would still love Vectorworks to make Workgroup Referencing and General files work with a proper collaboration/ versioning system like GIT. OK project sharing as well.

 

Either way get away from the bad assumptions, get back to understanding why drawings for all there inefficiencies worked contractually.  Then we can talk online collaboration.

[Amorphous - Julian]

Teamwork was file-based collaboration. BIMserver and BIMcloud are server-managed. 

 

Being able to do simultaneous syncing (saves time) and cut out data losses (saves even more time) is very important to us right now.

 

As it is, Project Sharing is slow, and is prone to data loss (we lose data through Project Sharing on a weekly basis).

As for 'bad assumptions', I do feel that when using Vectorworks as a 'Documentation Tool' (ie using it to create contract drawings), it feels like the people creating Vectorworks don't have much idea of how this process works, or have themselves been documenters.

 

These are some of our major gripes with documenting in Vectorworks:

 

- Elevation and Section viewports are SLOW (hinders documentation efficiency)
- Basic documentation tools like titleblock is SLOW (hinders document issuing time)

- Advanced Text Editing functionalities is LACKING (we would like to do all specifications in Vectorworks)

- Ability to add images to 'record formats' is LACKING (we would like to do all schedules in Vectorworks)

- Understanding of how a drawing should look is LACKING (take for example any 3D objects, and how it appears as wireframe in Top/Plan view) 

- Understanding of construction concepts is LACKING (take for example wall, skirting boards, and floor styles)

 

We throw resource (people) at documentation phase to mitigate the above problems. And therefore Project Sharing is important to us. 

 

So, back to the issue of Project Sharing:

With Project Sharing performing so poorly, it compounds the inefficiencies of Vectorworks as a documentation tool.

 

We, too, don't need online collaboration, we just need Vectorworks Project Sharing to not cause us constant data loss.

 

Hence, we ask for a more efficient and stable way to conduct Project Sharing, something like BIMserver. 

 

[Christiaan]

4 hours ago, Amorphous - Julian said:

Being able to do simultaneous syncing (saves time) and cut out data losses (saves even more time) is very important to us right now.

 

I have no experience with BIMserver but this capability would be priceless.

 

4 hours ago, Amorphous - Julian said:

As it is, Project Sharing is slow, and is prone to data loss (we lose data through Project Sharing on a weekly basis).

 

We're a bit better, roughly bi-monthly we'll lose something because of a project sharing glitch that also screws with the backups.

Edited March 18, 2020 by Christiaan

[Amorphous - Julian]

By way of a quick by update, @Tolu has been working with me in the background on this issue, they are aware of it and now working on solutions

[elepp]

@Amorphous - Julian Glad to hear that and seeing forward to your report on its success. We would like to tip our toes as well into those waters, but are a bit scared.

[Amorphous - Julian]

I have faith in the Vectorworks engineers and see a promising future.