Editability and Design Intent
IFC Editability in BIM: Reference Use or Destination-Native Conversion
Decide whether an IFC reference supports the next BIM task or receiver-native objects are needed, then test edits and source revisions.
Taxonomy / Tag
IFC Tag
Reference notes in the Tag taxonomy for IFC.
Spatial Context and BIM Exchange
Define an IFC Exchange Scope: Release, Model View, and Purpose
Turn “send an IFC” into a scoped request naming the release, model view, recipient task, and required information.
Formats, Profiles, and Translators
Schemas, Application Protocols, Model Views, and Extensions: The Scope Inside the Format
A familiar format can contain several schemas, profiles, views, or extensions. Learn what scope and status a receiver must understand.
Validation, Exchange Control, and Long-Term Reuse
Check IFC Information Requirements with IDS
Turn project-specific IFC information needs into a machine-readable IDS specification, then distinguish specification checks from model and geometric acceptance.
Spatial Context and BIM Exchange
Turn BIM Information Needs into Exchange Requirements with IDS
Use IDS to state required BIM objects, classifications, properties, values, and units within a defined IFC exchange scope.
Ecosystem Routes and Collaborative Exchange
BIM and Civil Exchange Routes: IFC, Data Exchanges, and LandXML
Choose a bounded BIM or civil-data exchange route by the information needed, recipient, export settings, cloud dependencies, and acceptance checks.
Ecosystem Routes and Collaborative Exchange
BCF Issues and Viewpoints: Sharing BIM Review Context
Use BCF to exchange model-based issue and viewpoint context alongside a separately managed IFC model, with clear file, server, and receiver checks.
Formats, Profiles, and Translators
Choosing an IFC Serialization: SPF, XML, ZIP, and Other Formats
Compare IFC-SPF, ifcXML, IFCZIP, and other listed forms by status and trade-offs before checking support in the receiving software.