Change Visualization Fails on Name Change

[PaulFrancoisStorm]

I use a naming convention that I derived from the British standards. 

XXX-XXX-XX-XX-XX-XX-XXXXX-S0-P01_CLOUD

In my experience, to be able to view the changes in a model between one package and the next, the published file must:

• Maintain the same name
•  Stay in the folder to which publishing is done. 

It would therefore not be possible to perform Change Visualization on a file if one altered the name of the published file to indicate the following:

• Suitability (S0 to S1 or some other suitability code)
• Revisions (P01 to P02 reflecting some design decision)

The only indicator of the status of the file is the minor revision (version) and should the model be downloaded from the BIM 360 CDE there is no way to tell at a glance what the file is suitable for. 

Copying the file into an interim folder to change the name, and then into another folder so a package can be created, does not work. 

Does anyone else have the same experience and does it cause a change in the way which you have to name and use files after adopting Design Collaboration? Would one forego the Suitability Code and Major Revision entirely and keep the models named exactly the same as they progress through the building stages from conception to handover? What would be the implications when the models become contractually binding? 

[AdamPeter]

Thank you @PaulFrancoisStorm for this feedback.  You are correct with the current limitation to do the diff compare if the names of the files are not the same.  Have you considered using custom fields in the Document Management interface to track the progress of the files?  The limitation is that it would only show up in the Docs interface, but it would allow you to essentially tag the file with that information without changing the filename. 

I understand this may not be ideal.  If you have another way this could be enhanced we would also  welcome your ideas HERE.

Thanks!

[PaulFrancoisStorm]

Hi Adam, 

Thank you, that sounds like a good idea. Let me try this and let you know. The suitability Code can certainly be metadata. 

Kind Regards, 

Paul Storm

[jayson.sterba]

hi @PaulFrancoisStorm,

I wanted to check in on you and see if you had the opportunity to try out @AdamPeter's solution.

Please let us know if this resolves your issue or if you need more assistance!

Have a great day!

Please “Accept As Solution” if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[PaulFrancoisStorm]

Hi Jayson,

Using metadata to indicate the file suitability and revision does work as long as the files are in the common data environment (image 2). The change visualization does work (image 3). In this case I added one door, synchronized, published and then changed the Revision metadata from P02 to P03 before creating the new package. 

When I download the file, the Metadata is not in the file's properties (image 1). Could one perhaps allow the Metadata to port to the operating system? 

[AdamPeter · Accepted solution]

@PaulFrancoisStorm, unfortunately that metadata is maintained only in the web viewer, it's not actually written to the file properties.  This is a great request however.  Thanks for the feedback.  It would be great if you could post it on the BIM 360 Idea Station for others to review and make comments on.

[PaulFrancoisStorm]

Created the idea:

• https://forums.autodesk.com/t5/bim-360-ideas/include-bim-360-metadata-downloaded-file-properties/idi...

[Anonymous]

2 years later and every other CDE has this option: except BIM 360 Docs apparently?