How to track model revisions (not sheets) ?

[Anonymous]

Hi,

We are grappling with how to monitor and record model revisions for issue to other consultants on a full BIM project.

Revisions on sheets work well to identify specific cloud/tagged changes and highlight them.

But the BIM Protocols that we have developed require us to strip the sheets from the model before issuing (PAS1192) - this avoids the issue with having to update every sheet/revision for every issue of the model which is not desirable or practical - especially as we exchange model files fairly frequently.

So, we now have the issue of how best to summarise and track the model revisions since the last model issue.

We have a splash screen that notes the model revision (again following the PAS1192 standard: P1.1->P1.2->P1.3>P1->P2.1... etc) and a space for comments that allow for a summary of what has changed. But that feels like a very soft approach, and dependent upon the users recording and adequately explaining the changes made.

Surely there is a way of extracting/monitoring/recording model changes that is more accurate than this ?

We have looked at Dynamo, and I am just starting to use it on farily simple tasks, but can it extract the timestamp on when an element was last modified ? could we use that to say colour up a model view to highlight those elements that have been modified ?

What is everyone else doing to monitor model changes ?

Many thanks

Martin

[L.Maas]

What we always do in larger projects with multiple party is that we have a meeting and decide on a combined protocol.

Often, like you we have a splash screen with some explanations and revision information.

We upload intemediary releases (sometimes daily) with the latest changes. Periodically (more often in the beginning when lots of changes happen) we issue an official version accompanied with sheets with all the comments marked.

Usually we also have a channel (e.g. email, forum) were we can comment on the project. For example if we made changes that would have a (big) impact on some other parties.

[Anonymous]

Thanks Louis,

What you describe is similar to the approach that we currently take. But there is a weakness in that it relies on users recording the changes that have been made (the same as the traditional sheet revisions approach dating back to the time of hand drawings).

We are working on a couple of (for us) very large projects, and having the ability to automatically track and log changes would be great.

Copy/Monitoring is out, simply because of the number of elements involved (and we tend to restrict it to levels, grids and columns).

There is an advantage in the user summary for the revision in that it can describe changes in a more intuitive way, ie. "model updated following clash detection meeting" and a reference to an updated clash schedule. But the BIM part of me feels that there should be a way of automating a log for model revisions - with the ability to highlight critical changes - You can't beat lifting the phone and talking it through with the other consultants - after all, the changes shouldn't come as a complete surprise to them - but an accurate record would be extremely useful.

I suppose it would be useful to develop a schedule in Revit (perhaps using a proxy object - duplicated for each revision) so that revisions can be recorded as a parameter and then scheduled out - something similar to the View Revisions Schedule.

Thanks

Martin

[L.Maas]

I agree. But it is a weakness that basically can not be avoided. People are making the drawings, so mistakes wil be made.

Automatically logging will also be very difficult. What constitutes a change? If I (by accident) move an object 1 millimeter is that a change? If I slighlty change the appearance of a material, and so on before you know it you would have enormous logs.

We just instruct people how to work properly. Then we build in checks (spot checks, clash detection, model compare, model review) to look for

issues/mistakes/standards violations.

You can add dummy objects or add (mulit line) parameters to objects to have it scheduled (but still relies on people filling them)

[chrisplyler]

It is easy for me.

Once I issue for bids or for permit or for construction, that file gets locked down with an appropriate suffix on the file name. If I open it with the intention to make a change after that point, it gets a "save as" with another appropriate suffix before I do anything else.

Easy for me because nobody but me works in my files. I don't have to collaborate or workshare or any of that stuff.

[arunc]

Any acceptable solution found for this issue, it will be good to track Generic/Board changes to the model before issuing out to the consultants.

A change register on the splash screen with a Shared Parameter comes to my mind.