Facilitating the BIM coordinator and empowering the suppliers with Automated BIM data checking. Presentation on ECPPM conference 2016, Cyprus

1. AUTOMATED DATA COMPLIANCE
CHECKING
Facilitating the BIM coordinator and empowering the suppliers
Léon van Berlo, Eleni Papadonikolaki

2. HTTP://WWW.SLIDESHARE.NET/BERLOTTI/
LEON.VANBERLO@TNO.NL
ELENI.PAPADONIKOLAKI@GMAIL.COM

5. © Berlo, Papadonikolaki 2016

6. © Berlo, Papadonikolaki 2016
Three types of data checks:
Data compliance
Data aggregation
Design/engineering coordination

7. © Berlo, Papadonikolaki 2016
Three types of data checks:
Data compliance
Data aggregation
Design/engineering coordination
Suppliers
Contractor

8. © Berlo, Papadonikolaki 2016

9. © Berlo, Papadonikolaki 2016
HYPOTHESES
Automated data check at data transfer will create:
Higher quality data (gatekeeper)
Coordinator to have more focus on actual coordination

10. EXPERIMENT
1. Research: most common data checks
2. Plug-in in BIMserver
3. Tested on three projects
4. Go to Cyprus!

11. COMMON REQUIREMENTS
There should be only one IfcProject object per file (no more, no less);
There should be only one IfcSite object per file;
All objects should be linked to an IfcBuildingStorey object;
There should be at least one IfcBuilding object in the dataset;
There should be at least one IfcBuildingStorey in the dataset;
The naming of the building storeys should be consistent and in order, i.e. floor-numbers;
The length unit should be millimeters; The area unit in m2; The volume unit m3;
The objects should be ‘close’ to the origin point (0,0,0) of the dataset;
Objects found across multiple ‘aspect/reference models’ should have the same position and
orientation point;
There should be no intersections in the individual ‘aspect models’;
There should be no duplicate objects in the entire dataset.

12. OTHER REQUIREMENTS
Typical “EXTRA” requirements from client:
The dataset should have the true North set;
The site elevation should be set;
The site latitude and longitude coordinates should be set;
The site cadaster ID should be available.

13. OUR EXPERIMENT:
1. Is there one (and only one) IfcProject object?
2. Is there one (and only one) IfcSite object?
3. Are all objects linked to an IfcBuildingStorey object?
4. Is there at least one IfcBuilding object?
5. Is there at least one IfcBuildingStorey?
6. Is the naming of the building storeys in order (numbers)?
7. Is the length unit in millimeters?
8. Is the area unit in square meters?
9. Is the volume unit in cubic meters?
10.Does the dataset have the true North set?
11.Is the site elevation set?
12.Are the site latitude and longitude coordinates set?
13.Is the site cadaster ID available?

14. WHAT TECHNOLOGY FOR CHECKING?
Several…
2016, T. Krijnen and L.A.H.M. van Berlo;
“Methodologies for requirement checking on building models”
DDSS 2016 (pdf)
Automated data compliance checking

15. THREE PROJECTS
Schependomlaan
https://github.com/openBIMstandards/DataSetSchependomlaan
Other two anonymous
Case A (schependomlaan), B en C

16. PROTOTYPE

17. PROTOTYPE

18. BIG DIFFERENCE
Used to share data:
Via e-mail/dropbox/sharepoint/whatever
Now:
Upload to website, and don’t have your data accepted when there are data
compliance errors.

20. 1. Is there a IfcProject object?
2. Is there one IfcSite object?
3. Are all objects linked to an
IfcBuildingStorey object?
4. Is there at least one
IfcBuilding?
5. Is there at least one
IfcBuildingStorey?
6. Is the naming of the building
storeys in order (numbers)?
7. Is the length unit in millimeters?
8. Is the area unit in m2?
9. Is the volume unit in m3?
10. Does the dataset have the true
North set?
11. Is the site elevation set?
12. Are the site latitude and
longitude coordinates set?
13. Is the site cadaster ID
available?

21. 1. Is there a IfcProject object?
2. Is there one IfcSite object?
3. Are all objects linked to an
IfcBuildingStorey object?
4. Is there at least one
IfcBuilding?
5. Is there at least one
IfcBuildingStorey?
6. Is the naming of the building
storeys in order (numbers)?
7. Is the length unit in millimeters?
8. Is the area unit in m2?
9. Is the volume unit in m3?
10. Does the dataset have the true
North set?
11. Is the site elevation set?
12. Are the site latitude and
longitude coordinates set?
13. Is the site cadaster ID
available?

22. 1. Is there a IfcProject object?
2. Is there one IfcSite object?
3. Are all objects linked to an
IfcBuildingStorey object?
4. Is there at least one
IfcBuilding?
5. Is there at least one
IfcBuildingStorey?
6. Is the naming of the building
storeys in order (numbers)?
7. Is the length unit in millimeters?
8. Is the area unit in m2?
9. Is the volume unit in m3?
10. Does the dataset have the true
North set?
11. Is the site elevation set?
12. Are the site latitude and
longitude coordinates set?
13. Is the site cadaster ID
available?

23. 1. Is there a IfcProject object?
2. Is there one IfcSite object?
3. Are all objects linked to an
IfcBuildingStorey object?
4. Is there at least one
IfcBuilding?
5. Is there at least one
IfcBuildingStorey?
6. Is the naming of the building
storeys in order (numbers)?
7. Is the length unit in millimeters?
8. Is the area unit in m2?
9. Is the volume unit in m3?
10. Does the dataset have the true
North set?
11. Is the site elevation set?
12. Are the site latitude and
longitude coordinates set?
13. Is the site cadaster ID
available?

25. CONCLUSION & DISCUSSION
Pretty good data
Not everything can be tested (naming of building storey)
Still no insight in potential
“Whereas this study has shown the potential of online automated compliance checking, there is
no clear evidence that the quality of models will improve in the process. Further research would
be required across multiple projects to validate this hypothesis.“
Maybe adding an extra threshold will limit the data from suppliers?

26. FAQ
Yes, source code is available on github.com/opensourcebim
(of course it is, otherwise it wouldn’t be verifiable research)
No, these 3 cases are not representing the whole sector
Yes, this might also work on other parts in the collaboration process (not only
between suppliers and contracters)

27. THANK YOU FOR YOUR ATTENTION