Categories:
-
3d 96 articles
-
animations 16 articles
-
architecture 47 articles
-
blender 98 articles
-
bédé 19 articles
-
techdrawing 24 articles
-
freecad 190 articles
-
gaming 1 articles
-
idsampa 8 articles
-
inthepress 8 articles
-
linux 57 articles
-
music 1 articles
-
nativeifc 31 articles
-
opensource 267 articles
-
orange 4 articles
-
photo 16 articles
-
projects 35 articles
-
receitas 176 articles
-
saopaulo 18 articles
-
sketches 163 articles
-
talks 25 articles
-
techdrawing 24 articles
-
textes 7 articles
-
trilhas 3 articles
-
urbanoids 1 articles
-
video 47 articles
-
webdesign 7 articles
-
works 151 articles
Archives:
-
2007 22 articles
-
2008 32 articles
-
2009 66 articles
-
2010 74 articles
-
2011 74 articles
-
2012 47 articles
-
2013 31 articles
-
2014 38 articles
-
2015 28 articles
-
2016 36 articles
-
2017 41 articles
-
2018 46 articles
-
2019 59 articles
-
2020 18 articles
-
2021 20 articles
-
2022 7 articles
-
2023 25 articles
-
2024 15 articles
Hey Yorik!
Commenting post 325: Hey Yorik! Thanks for that valueable blog post! I'm coming from the CAD side (worked with PTC Creo 2.0 in Engineering) and now touching the BIM-topic. As a product manufacturer our aim is to offer our products in BIM-formats, so that planners can use and integrate them in their planner-BIM-workflows. Therefore we want to use our engineering models (the geometry, CAD) and bring them together with technical data stored in IFC properties. Everyone in the market wants to have Revit models, even if they don't really know much about BIM and IFC, which uses the open standard of buildingSMART. In my opinion the right way is to provide the models in IFC-files. The content of the files should be usecase driven and depends also on the progress of the planned project. Therefore IFC is able to provide different views (MDV). For examples there will be a view for the start planning phase of a project where the planner needs rather raw geometry and information of the product, whereas he will need a nearly "asBuilt" model when project comes to an end and gets handed over to the facility management of the building owner. FreeCAD should be able to cover standardized ModelDataViews (MDVs) as they are published by different norm institutions like ISO, CEN, DIN etc. With such standard IFC-content you would be able to provide your product data to what the customer (planner) needs and he could import that into his own software (like Revit, ArchiCAD, etc.)
As a medicore python programmer I'm planning to use FreeCAD as a STEP-to-IFC converter by scripting. Therefore I want to use the STEP geometry and put Information from my database to the different IFC-properties according to a the standard "Reference View" from IFC for testing purposes.
Maybe you could support me if I get into trouble?
Greetings Phil