-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fire protection - missing classes #923
Comments
We are currently collaborating in a project "FireBIM" (ITEA) with EU partners from Belgium, Netherlands, Denmark and Portugal and are also looking at the best possible alignment of Fire Safety concepts to the IFC schema. While basic stuff such as FireRating is foreseen, there are others where we have various options. And also basic equipment like a Fire Extinguisher is often wrongly mapped as a Terminal, due to lack of better entities in the scheme. Would be nice to exchange some approaches, so we could suggest schema improvements with buildingSMART. |
Yeah it's always pretty embarassing when I talk to the fire engineer and say "uh, about extinguishers..." :) "... oh, yeah fire blankets too ..." :) |
@stefkeB: We would be very interested in learning more about the "FireBIM" project and exchanging approaches. I am currently also part of the reference group for a project in Sweden which aims to set some national industry standard for how fire protection information is relayed parametrically and visually in models. We would be happy to help push the needle toward a more better fire ifc in whatever way we can. |
Hi,
I work as a fire protection engineer developing 3D fire models. I would like to request IFC classes for objects representing fire protection requirements.
I think it's a real issue that there are no suitable classes for objects that are representative of fire protection requirements. Instead we are using a variety of other classes that end up adding our representative components to the same classes as actual building components which is far from ideal.
The fire model is quickly becoming a natural part of the modeling package in projects and currently the lack of appropriate ifc classes is creating a situation where projects are opting to filter out fire information in different ways when the ifc is the primary information model. This creates quality risks and it is certainly not a wanted outcome that the fire model becomes a problem for the project as we are trying to ramp up the ways in which it can be helpful for projects.
I realize there is no standard for how these elements should be categorized, but we need to move forward with something. I see this as a real quality issue in our models.
KR
Rebecca Hedberg
The text was updated successfully, but these errors were encountered: