Implementation of BIM 360's custom attributes in accordance to the ISO 19650 mindset

[kelvin_law]

Hello all.

In my current project, I am trying to align the ISO 19650 workflow to the project's information delivery process.

Metadata assignment, such as revision and suitability, is required as a function of CDE by clause 5.1.7c of the ISO 19650-2:2018 standard. Extra guidance provided inside the UK National Annex of BS EN ISO 19650-2:2018 provided a list of 'suitability codes' and the details of the mechanism in assigning 'Revision' to information containers (e.g. model files, drawing files).

I understand that permitted BIM 360 users can add custom attribute fields to files inside a Project Folder. This allows the metadata to be inputted to describe the concerned information containers. Also, BIM 360 has another fascinating feature that enable users to restore previous file versions.

From my understanding, ISO 19650 allows better traceability and accountability on the delivery of project information. However, I am a little bit confused on how the operating mechanism of these features (i.e. custom attributes & past versions restoration) embody the spirit of ISO 19650.

The fact that I was able to change the custom attribute of previous version file is worrying. This leads to multiple entries of the same version (image below) which themselves can have different custom attributes .

I understand one can trace the attribute change record by looking into the 'Document Log' and eventually dig out the very first values of the custom attribute, but I believe this may cause trouble in project management.

Please advise whether I have overlooked any other features of BIM 360 that can clear this ambiguity. Many thanks.

[múinteoir]

You have not, attributes can be changed in previous versions. BIM 360 lends itself to having the metadata that aligns with 19650 but it lacks the security diligence around the editing of the metadata. 

[gareth.spencer1]

Hi @kelvin_law,

I would consider a few things here when you're setting up your project in BIM 360 Docs to ISO 19650.

Is BIM 360 Docs to be used as CDE on the project for all (i.e. project managers, consultants, contractors, sub-contractors, etc) to store their information for one or all the following; Work in Progress (WIP), Shared or Published. Also, when the information is shared with the client, is it in BIM 360 or another CDE? 

If it is being used for those states then you need to consider what permissions you are going to give to those working on the project in BIM 360 Docs. e.g. if it's in the WIP area then only that organisation will access that information. So they permission levels can be view/download/upload/edit. Then when the information is shared to the shared or published area they will only have view/download/upload permission levels. Which will not allow them to restore the version only add new versions. The version number will increase every time someone saves the file into BIM 360 Docs. So if you save it ten times in the hour it still could be status SO in the WIP area but the revision could be P01.01. If you used the two digital numeric value at the end then it could go higher than 99 very quickly inside Docs as some users may save every five minutes. If that makes sense?

When setting up the permission think about how you are going to set them. Don't give everyone the same. e.g. Technician only needs to view/download/upload, but the BIM Manager view/download/upload/edit. 

Don't forget the in the project files area you need to add the attributes so the container metadata can be added as it can't be taken from the drawings like in the plans area.

On projects where you are just using it internally ie. your own organisations it would be good practises following the same approach. 

You could use documents sets to help with the status codes by assigning the files to a set which is named to match those in the National Annex to BS EN ISO 19650-2. 

I would recommend downloading the UK BIM Frameworks guidance document Information management according to BS EN ISO 19650 Part 2 - Processes for Project Delivery. This should help when your implementing a CDE according to ISO 19650. It is free along with all the other guidance documentation.

I trust the above makes sense. 

[kelvin_law]

Thanks @múinteoir,

I guess this requires in-house self discipline and integrity to manage this point of breakthrough. 

[kelvin_law]

@gareth.spencer1 , 

Thank you very much for the guidance, I am new to BIM 360 and definitely I still have lots to learn 🙂

Please allow me to brief you the project background.

The project is a Design-and-Build project. The contractor, the contractor-appointed design consultants and sub-contractors are using different CDE solutions. The WIP area is located in each individual's CDE or local drive (as some parties have not got their CDE/EDMS solution yet).

I understand the concept of CDE in ISO 19650 does not confine project to the usage of one single CDE solution. So, as long as structured workflow and approval process are defined clearly and traceable, I believe this delivery environment of information can honor the ISO 19650 principles.

The current practice we are having, is to ask different parties to contribute their model geometries file periodically to the "Shared" area inside Client's hosted BIM 360 environment, the file upload is done manually by respective parties. It is expected that each respective party to internally quality control their deliverable before uploading to the "Shared" area, I believe this is some sort of gate approval process required in ISO 19650.

I agree it is fundamental to assign role-specific permissions, such that parties/individuals are only able to operate in BIM 360 specified in EIR, contractual documents and in-house assigned roles. However, I am worried that once an individual is assigned with permission, either "View + Download + Upload + Edit" or "Folder Control", they can forever change BIM 360's custom attribute value (i.e. the metadata). I believe allowing such changes (even the purpose of change is to fix incorrect / mistaken input) is not desirable.

Desirably, if BIM 360 only allows user to assign attributes the first time that specific version of file is uploaded and prohibits any further changes to that same version of file, it will definitely serve the accountability required in an information delivery of a project.

To be honest, such metadata can be incorporated into file name to act as some sort of workaround, but all the filename-based linkage (nwf, rvt etc.) previously set will be in trouble, plus the naming conventions of the information container will be suitability/status dependent which are variables in the course of a project.

---------------------------

For the file revision issue, I am not really clear about the description "The version number will increase every time someone saves the file into BIM 360 Docs" you made in the last reply. Does "save" mean synchronising changes to the BIM 360 Central cloud model file? Since I have not yet tried Revit worksharing in BIM 360 Design, I have no idea whether each synchronisation communication with the BIM 360 Central cloud model will step up the "Version" of the file. If that is the case, then I believe the version will indeed skyrocket.

However, I believe we can still keep the Revision metadata (a custom attribute) as P01.01 unless there is considerable changes made (for example, after one full-day of collaboration). After a full-day of works, I believe we can initiate the archiving of P01.01 file into the "Archived" repository, and the working file in WIP can then be assigned a new Revision metadata, P01.02. So if the collaboration is for example, loop in a three-week cycle, the Revision metadata will only get as high as P01.21, at which the file must then be shared with Revision "P01" in the "Shared" repository and the new WIP file will then have Revision metadata P02.01.

Our project has not yet progressed that much in WIP collaboration, but we would like to eventually migrate all parties' WIP activities into the client host BIM 360 in near future. This version & revision issue definitely will be a major area of study.