The generic 'Proxy' mechanism in the IFC model allows us to define objects that we need, but that are not yet included in the IFC model. A proxy can have geometry and attached properties. With the geometry support the proxy can be used to represent 'stupid' (=no specific behavior in programs) objects that can be displayed in the receiving system. With the ability to attach properties to the proxy they can be made 'intelligent', but this intelligence is only enabled if there is agreement between implementers what those properties are and how they are used. This would in effect be a extension to the IFC model that was made through agreement by implementers. No such public and documented agreements exists today, not in the BLIS project or elsewhere.
The concept of 'Proxy [product with geometry]' defines a proxy that can be used to exchange products with geometry. It does not have support for attached properties. More intelligent use of the Proxy mechanism requires agreements and documentation about the attached properties.
Geometry
BoundingBox Brep 2D Geometry
- Proxy objects do not have any geometry use definitions, and consequently the geometry does not have any semantics. The geometry is purely for representation purposes.
- As the basic representation the bounding box should be provided.
- Brep geometry may be used for the 3D representation
- 2D geometry may be used for the symbolic 2D representation.
Used by views
- Arch. design >> Thermal load calculations / HVAC system design
- CAD / visualization
IfcProxy
GlobalId
OwnerHistory
Owner history [all]
Label
PartOfGroups
IfcProxyEnum
Product
LocalPlacement
Representations
Items
Uses concepts
Used by concepts
Copyright © 2000-2002 BLIS-Project [BLIS, Registered Organization]
Author: Jiri Hietanen (jiri.hietanen@qpartner.com)
All rights reserved.
