## 4 Discussion
### The Management Field
\begin{table}
\begin{tabular}{l c c c c c c c c} \hline \hline
**Duties** & & & & & & & & & & \\ \hline CDE consulting & Z & I & & & & & K & O & \\ \hline CDE provision & O & I & I & I & I & I & I & I \\ \hline CDE configuration & Z & K & K & K & K & K & K & K \\ \hline CDE maintenance & & K & & I & K & K & O & \\ \hline Downloading/uploading the entire information design to/from & O & O & O & O & O & O & O & O \\ the CDE & \multicolumn{6}{c}{Quality and control assurance} \\ \hline Compliance with procedures included in the BIM model standard & & & O & O & & & O \\ \hline Report on budget changes, cost and design & Z & & O & & & & O \\ \hline Testing and coordination of virtual model, including full clash & I & & K & O & & O \\ detection as featured in relevant BIM software & & I & & K & O & & O \\ \hline Report on the overall model quality in terms of geometry, essentials & I & & & & & O \\ and data & & I & & & & & & \\ \hline Report on BEP compliance in terms of LOD, completeness and BIM model standards & I & & & I & O & \\ \hline Report on 4D and 5D model functionality, as used by other designers & I & K & & & O & K & \\ \hline Review of data received for compliance with the EIR & & & O & O & & O & O \\ \hline Risk assessment report filing & I & & K & K & & I & K \\ \hline Support for the lead designer by the team in 3D model coordination. & I & K & O & & & K \\ \multicolumn{6}{c}{Clash detection} \\ \hline \hline \end{tabular}  
* duty and function symbols: O—responsible; performs task; Z—approves; K—consults; I—informed.  
\end{table} 
Table 4: Fragment of an appendix to the EIR of the Copernican Revolution Studio on scopes of responsibility. In construction projects executed with the use of BIM, persons with BIM process qualifications should be present on both sides, namely on the developer's side so as to properly verify the information delivered, and on the contractor's side  
In a study on construction wastefulness, Polish contractors typically indicated design documentation errors and inconsistencies as having the greatest impact on project cost and completion time [55], which is why coordinating this documentation is so important. Process stages associated with model coordination can be defined in an EIR. Certain clashes, prior to their removal, should be consulted with the developer. For instance, a revision proposed by the developer can lead to changes in a different, preapproved component, a change in the aesthetics of a room in which said element is to be located, a change in project cost and completion time, etc. In such a situation, the developer should know the consequences of the revision and thus make an informed decision. Such situations should be planned for in a EIR document, with relevant procedures laid out, or it should feature an annotation that such a procedure is to be proposed by the contractor after the developer's acceptance, and included in the BEP, which is a part of the contract. In light of the above, the designer submits coordinated models with any clashes that do not need to be approved by the developer removed, as well as a clash report, while clashes that require Ordering Party approval are clearly presented for discussion. After the final version's acceptance, relevant changes are applied to the models, after which a new clash report is generated and submitted to the developer. In the field under discussion, expectations concerning the models supplied were referenced, with an indication of the PUWG PL2000 zone 7 coordinate system, with a point of reference specified in the BEP. Only the necessary information was to be sent, with models divided by specialization and the possible geometric division of the integrated multi-specialization model, should the file be too large (in the CRS EIR, a specific stipulation states that files in excess of 100 MB were to be divided into smaller ones).