Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries — Part 1: Data schema
ISO 16739-1 specifies the IFC data schema and exchange structure for construction and facility-management information.
What the authority record establishes
ISO 16739-1 specifies the IFC data schema and exchange structure for construction and facility-management information.
Voluntary unless adopted through contract or another authority
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
It helps buyers ask which schema, model view, entities, properties, classifications, geometry, relationships, validation, and exchange evidence a construction product actually supports.
Affected operating stages
- Authoring
- Coordination
- Exchange
- Validation
- Delivery
- Operations
Capabilities to examine
BIM Coordination Model Review And Issue Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for BIM coordination model review and issue management.
Drawing And Specification Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for drawing and specification management.
Document Control Versioning And Transmittals
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for document control versioning and transmittals.
Asset Data Handover And Operations Transition
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset data handover and operations transition.
API Data Export And Integration Framework
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for API data export and integration framework.
Affected buyer audiences
- designers
- contractors
- owners
- BIM managers
- software developers
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
IFC support does not establish complete exchange, model quality, configured interoperability, or suitability for a particular project use.