Concepts modeled in the Core layer schemas

Model structuring objects - Project, site, building, building storey, space, building element: all of these fundamental objects, which are shared across all domains in an AEC project are defined in the IFC core model.

Fundamental properties - Costs, classification, placement, shape, materials and documents: all of these concepts are related to most of the objects used by architects through the object supertypes at in the IFC core model. See notes in the class definitions of this schema for examples where these should be considered.

Actors - people and/or organizations involved in the project. Actors are important in the IFC model as they concepts such as ownership, responsibility, approval and workflow.

Assemblies -of elements. This concept is modeled using the objectified relationship IfcRelAggregates. Examples in architecture include stairs, ramps, curtain walls and roofs. The distinction from Nesting is that elements in an assembly can be of various types.

Connections - between elements in a project. This concept is modeled in IFC using the objectified relationship IfcRelConnectsElements. Architects are interested many different types of connections because they must design construction details for them. Examples include wall to wall, wall to floor, wall to ceiling and column to beam connections. See IfcRelConnectsElements, its subtypes, the referenced IfcConnectionGeometry, its subtypes for more discussion on this subject.

Containment in spatial structure - elements that are contained in any level of the spatial project structure (site, building, building story, space). This concept is modeled using the objectified relationship IfcRelContainedInSpatialStructure.

Controls - conceptual objects that determine or constrain other objects. IFC includes several examples of such controls (constraints, budgets, design program). These are related to the objects which they 'control' through the IfcRelAssignsToControl objectified relationship. Examples that are of interest to architects include budgets, building code constraints, geometric alignment constraints and space programs (client brief information).

Groups - of objects, related for some group purpose. Object collections are related to a group object (which defines the purpose) through the IfcRelAssignsToGroup objectified relationship.

Grids - the design grid objects are provided through IfcGrid and IfcGridPlacement. It is used to place objects relative to virtual grid intersections.

Nesting - elements that contain other, like elements. This concept is modeled in IFC using the objectified relationship, IfcRelNests. This relationship requires that both, nested and nesting object are of the same object type.

Processes and resources - which process products (building elements), resulting in other products (assembly, refined or modified building elements, etc.). The most common examples of are construction processes.

Proxy objects - surrogates for types of objects that are not yet included in IFC. Proxies are included in IFC in the recognition that IFC will never fully elaborate all of the objects, concepts and processes in the AEC industry. This surrogate allows enables a basic representation of the 'foreign object type' so that the project model is a complete (if not totally accurate) representation. Architects will be most interested in product proxies. Surrogates for real world, physical objects. A shape representation and placement are included for such proxies. This allows architects to understand the shape, location and orientation of the real world object represented by the proxy.

Dynamically assigned properties - properties that are attached to objects and may be taylored by mutual agreements on the property names. This concept is handled through use of the objectified relationship IfcRelDefinedByProperties.

Type objects - allow the assignment of a type (or specific object) to all occurrencies of that type. This concept is handled through use of the objectified relationship IfcRelDefinedByType.

Space Boundaries - both physical and virtual elements which bound a space. Architects deal extensively with finishes in spaces and often specify such 'interior finishes' for the walls, floor(s) and ceilings that bound a space. IFC includes a special list of relationships from spaces to space boundaries. See IfcSpace and IfcSpaceBoundary in the IfcProductExtension schema.

Concepts modeled in IfcSharedBldgElements

Walls, doors, windows, columns, beams, floors, roofs: All of these objects types, essential to architectural design are defined in the shared building elements schema because other disciplines also deal with them. Most of these allow specification of 'types' and association of more detailed properties associated with those types. Coverings: that cover other building elements. These objects have a special relationship (IfcRelCoversBldgElements) to other building elements which they 'cover'. Examples include floor and wall coverings, protective coverings (base molding, chair railing) and ceilings. There is also a special relationship (IfcRelAttachesToBoundaries) to space boundaries, which allows specification of finishes by space.

Concepts modeled in IfcSharedSpatialElements

Compartments - this new subtype of IfcZone allows architects to compartmentize buildings in order to meet requirements of e. g., fire codes.

Occupant and Occupancy - architects deal with these concepts in the design and permit phases of projects. Facilities managers use them through the operations phase.

Concepts modeled in IfcSharedBldgServiceElements

Distribution systems (e.g., ducting, piping, sanitary, etc.), equipment, electrical appliances many types of these concepts are available in this release of IFC.

Concepts modeled in IfcFacilitiesMgmtDomain

Furniture: both standalone and systems furniture are available in this release of IFC.