E-stransmit - Best Practice on Workshared Models

E-stransmit - Best Practice on Workshared Models

Anonymous
Not applicable
1,183 Views
2 Replies
Message 1 of 3

E-stransmit - Best Practice on Workshared Models

Anonymous
Not applicable

What is the best practice for e-transmit on workshared models? Wether on BIM 360 or a network workshare.

 

1-I point at the central file for the extraction

2-Do user collaborating need to close their local file? Is there any danger if they don't? I am seeing conflicting data on this point.

 

Thanks!

0 Likes
1,184 Views
2 Replies
Replies (2)
Message 2 of 3

SteveKStafford
Mentor
Mentor

#2 - Yes, I'd recommend you use it when other users are not active in the model(s). If they are working on elements while you're doing this you might not capture changes they have not synchronized yet. Assuming the reason for using eTransmit is to archive the project you don't want to have different data than what was submitted at that point?

 

#1 - Yes, the central file since that represents the model has a whole. If you point to a local file there is no guarantee that it is up to date...unless you just created it and everyone else has closed theirs after syncing.

 

Using BIM 360 or Revit Server it's a bit more cumbersome because etransmit won't browse those locations. You'll have to download the files from those systems first and then fix paths to links etc. Then you can use etransmit on the local copy. There is something else I'm forgetting right now...long day. I'll post it if/when I remember it. Maybe someone else will chime in.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes
Message 3 of 3

SamuelAB
Advocate
Advocate

Thanks for the answer and sorry for the late reply.

 

#2 - Yes, I'd recommend you use it when other users are not active in the model(s). If they are working on elements while you're doing this you might not capture changes they have not synchronized yet. Assuming the reason for using eTransmit is to archive the project you don't want to have different data than what was submitted at that point?

 

In this case I'd don't care if some changes are not synchronized after they synch. I`m mostly concerned about not crashing or corrupting the model and I'd like to let the 5-6 people keep working (after telling them to synch). The files take about 30-40 minutes to package as an e-transmit, so it is a huge loss of productivity to tell 5-6 people to stop working during this time every week.

 

Is there such a risk if people are still working in their local files?

0 Likes