We are currently working on a restoration operation of a historical project, and we are requested to provide a 3D model of the final status of the project in an IFC and native format.
The operation is done using ArchiCAD 21, and I would like to know how to attach PDF documents and sheets to the model and exporting them together as IFC file, so that we can visualize the model with the documents attached in the viewer.
What viewer are you talking about?
I'm not sure if I know an IFC viewer that handles PDF documentation like BIMx does for instance (I pictured it like that what you described).
If native format is already requested, why not just publish a BIMx model and call it a day? The drawback: only the mobile version is capable of displaying the 2D documentation.
The barefoot solution could be to create an IfcLabel that has the document URL attached to it (if you publish the to the same folder relative paths might work - I'm not sure). You could create host elements just for this purpose - it's tedious and not so automated, I hope someone else has a better idea.
Thanks for your reply @furtnob,
The viewer I am talking about and that I use is Tekla BIMsight and for the required model, it is required that we deliver it in IFC 2x3 and in its native format (which is .pln). How about the creation of an IFC label that attaches a URL to it, how to do it in ArchiCAD ?
I don't have Tekla BIMSight, so I don't know exactly where/how to check in that (click on the red objects and look for a Pset_URL property set).
I put the assumed deliveries in a folder (some random .txt to make it small and a GS guide about the Profiler which was like 104kb) and the .ifc file(s) go to the same level, but really, it's up to you - the sample is the attached .zip file.
You can create "dummy" geometry that refers to a certain view (like planes for sections, floor plans, details), or you can put the paths directly in the desired object itself (I think you posted this to another forum where you mentioned vaults).
To create the label, you can do it in several ways:
1. You can use the IFC Project Manager if you like editing IFC properties directly: you could attach an IFCLabel to the project (create a custom Pset or find the "appropriate" place for it), or you can put it at an object level. I'm not sure which one would be "correct", but I'm not familiar with your deliverables at all.
2. A more structured approach would be to use the IFC Property mapping: first you need to create a "regular" ARCHICAD property (make it a 'String' and available for the desired classifications), that you can map to the IfcLabel. If you use morphs only, for instance, you could put the Pset to the IfcBuildingElementProxy class, which is otherwise not used (ideally). This last option has the benefit to export a schedule with your placeholder geometry, fill up the necessary paths, and import back.
The benefits of this approach: as low-tech as possible, they can use whatever PDF/spreadsheet viewer they like. You can also link to images, as-built or before the project state, etc.
The disadvantages: if you/they break the file hieararchy, the links break too. To make it crossplatform, you can always create a File path - Win and File path - macOS/Linux field. It's also not that fancy looking.
This is what I have in mind right now. Something like this could work? (I created it on Windows, so \ and / can cause a problem with macOS - let me know.)
actively using: AC22-25 INT | Rhino6-7 | macOS / win10