Earlier in the year
I blogged about the UK BIM Alliance's guidance document for the concepts behind the BS EN ISO 19650 standards.
I thought it probably a good thing to do a little post about the part two of this guidance series that was published a month or two ago. Again, this is a free download, and is available below:
-
https://ukbimframework.org/standards-guidance/
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRP-7XcZDQKpScU5O5hSgV-qKLcTtEcYKxivsLlRAWqb4V8RuxHpnoz7GSotHZratPFJeoOqfwivRMOa9iDYu8HRxyoB_DyzJVOjCblDwQcTJrjsiDCXHRAzPHcFJpfcaiG-JLj94-5B8m/s1600/001.png) |
19650 guidance - part 2 |
Whereas the first guide looked at the concepts, this second guide gives some really practical support with respect to the actual process of information management. Some screenshots below, from section 2 of the guide, to give a bit of an overview.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEguJAKGNpBBCAbnH8WImESedU_br1GudjrPEhHQ1ApXqbvXN-d3CA42B0hAwnWDxD_jd8fwvpDpe1550twwa4Caahqv3m_tfU6vbZ0toHfSATrk-7V63GG2oipNPpZEADBS14yxS270ya_B/s400/001.png) |
The workflow process as information is developed and approved/authorized |
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSVm6a151hXWQ6q5DorjLjVOfC0gt0lJ97YL0qbx-U_c0zdzbJC09XNgoYFXkv70H0-Ht7j8an3HeQBv34si0AJYvR7lG5-SV5k97ajYEYYlyo7jCMp2p9_fzf8H9oZgtdzvtibYQraoUP/s640/002.png) |
An agreed naming convention for all information containers that are issued to the team |
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEii8VsqIs4hwekIT9TFfadqrUr4Z8rUXNZ0Tl2ch5sH3qrL-Dq_3Yvu7bCkenzLzLfttyoBHFqPggA2KFt5nkIaHkY5EpD8glmRu0axMWqGMdU6D-eHmQi9qXangh35H4NgccaK0H8XmsiG/s640/003.png) |
An agreed approach to revision codes for the information |
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDwtRROsc4EM7ZcgCHLcrseZ8gERua2qd8SX9ZrEC1SILYhFCXt3yc7pepTzRTIfPIpq9eaNbkilklE0LfqQ-1vZYQIv-zpWpE-Rau6qQzezpiI_wAIN9ZtjgbpLA6DpKv3qkAVA4w_qt5/s640/004.png) |
The first section of a worked example showing how the suitability should be indicated using status codes |
Finally, a shout out to the team who worked on this and put in lots of 'volunteer hours' to share knowledge and best practice around this...
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqpowXOWyxo_HP4iaiKAmoH4VLtA_pJIVxbLz4ZTBj6I9ez3wXWLMPvqGSUGqPOYmStHCOZ-e3gg747srUJ9ijxMdXFShZR5oF-vpxEgMJGHwx_OU9dqr6SJQ-744AdM2OMpzHK0MnygQU/s1600/001.png) |
Acknowledgements |
No comments:
Post a Comment