{"id":2752,"date":"2017-11-21T09:06:55","date_gmt":"2017-11-21T09:06:55","guid":{"rendered":"http:\/\/biblus.accasoftware.com\/en\/?p=2752"},"modified":"2024-08-21T15:27:56","modified_gmt":"2024-08-21T13:27:56","slug":"the-bim-information-workflow","status":"publish","type":"post","link":"https:\/\/biblus.accasoftware.com\/en\/the-bim-information-workflow\/","title":{"rendered":"The BIM information workflow: BS 1192 and Pas 1192-2 standards (part 1)"},"content":{"rendered":"

BIM and the virtual model: development and BIM information workflow within the Common Data Environment (CDE) according to the BS 1192 and Pas 1192-2 standards. Shared and WIP (Work in Progress) blocks<\/p>\n

<\/p>\n

When building a virtual BIM model it is crucial to establish what is the correct information workflow<\/strong>.<\/p>\n

The purpose of secure data sharing and design choices among different professional teams is achieved by sharing virtual building models that can interact with each other.
\nThis possibility is technically guaranteed by shared data formats among different software: the most well-known and diffused certainly is the IFC format (See. art. \u201cWhat is IFC and What does link it to the BIM?<\/a>\u201d).<\/p>\n

We thus realize the virtual model of the building, which consists of a “federation” of virtual models, each one relating to the main application areas: architectural, structural, system engineering, etc. (See art. \u201cEvolution of the BIM and virtual building model<\/a>\u201d).<\/p>\n

Common Data Environment (CDE) according to BS 1192 e le Pas 1192-2<\/h2>\n

Pas 1192-2:2013<\/strong>, published by the British Standard Institution<\/a> <\/strong>body, are part of a large body of organically designed guidelines. The following graphic representation clarifies these two aspects.<\/p>\n

\"Pas1192-2\"

This representation is achieved overlapping the 2 following graphs:<\/p>\n

 <\/p>\n

\"Project

 <\/p>\n

\"CDE

The implementation stages of the virtual building prototype (creation, development and interrelation between models) take place within an area defined as Common Data Environment<\/strong> (CDE). Discover a Common Data Environment software<\/a> such as usBIM.platform.<\/p>\n

The CDE<\/strong> needs to describe the processes and procedures for defining forms and modes, roles and responsibilities able to develop collaborative relationships among the various technical teams involved.<\/p>\n

The numerous guidelines and the need for pilot projects are, as a matter of facts, born in support of the vast casework that can be found everyday.<\/p>\n

The UK regulatory body offers a potential well-structured organization of this common data area.
\nAll operating modes are then formalized: from the name to give to the files, to the organization of the archives, to the data exchange methods.<\/p>\n

The \u201cheart\u201d of the CDE consists of 4 sub-areas<\/strong> interconnected by the flow of information, starting from the Work In Progress areas to end up with the Archive area.<\/p>\n

\"Collaborative-Working\"

The four sub-areas of Common Data Environment<\/h2>\n

Work in Progress<\/strong>: here are the areas “in progress” related to various application areas such as the area of architectural design, structural design, etc. The relevant part of the project is developed in each area together with documentation output. This will remain within this area until it reaches a certain level of development, so it will become available to other project teams.<\/p>\n

Before reaching the target all the documentation will be available only by the area’s technical team.<\/p>\n

Shared<\/strong>: this is the area where several design teams share the progress of their work at various stages of development. At this stage the project is still under construction. The various teams\u2019 cyclically deposited and withdrawn documentation allows everyone to align themselves quickly with any changes and improvements made.<\/p>\n

Published Documentation<\/strong>: it is where the project documentation is completed and shared by the various design teams and approved by the client. The filed documentation is intended for the implementation phase.<\/p>\n

Archive<\/strong>: it is the area where the design information of the product is stored with all the relevant information, including design, regulatory and legal requirements.<\/p>\n

 <\/p>\n

\"edificius\"