archive-org.com » ORG » B » BUILDINGSMART-TECH.ORG

Total: 303

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Scope
    release of IFC represents an open international standard for BIM data that is exchanged and shared among software applications used by the various participants in a building construction or facility management project This release of IFC consists of the data schema represented as an EXPRESS schema specification and alternatively as an XML schema specification and reference data represented as definitions of property and quantity names and descriptions A subset of the data schema and referenced data is referred to as a model view definition A particular model view definition is defined to support one or many recognized workflows in the building construction and facility management industry sector Each workflow identifies data exchange requirements for software applications Conforming software applications need to identity the model view definition they conform to The following are within the scope of this release of IFC BIM exchange format definitions that are required during the life cycle phases of buildings demonstrating the need conception of need outline feasibility substantive feasibility study and outline financial authority outline conceptual design full conceptual design coordinated design procurement and full financial authority production information construction operation and maintenance BIM exchange format definitions that are required by the various disciplines involved

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-1.htm (2016-02-12)
    Open archived version from archive


  • Normative references
    edition cited applies For undated references the latest edition of the referenced document including any amendments applies ISO 10303 11 Industrial automation systems and integration Product data representation and exchange Part 11 description methods The EXPRESS Language Reference Manual ISO 10303 21 Industrial automation systems and integration Product data representation and exchange Part 21 Implementation methods Clear text encoding of the exchange structure ISO 10303 28 Industrial automation systems and

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-2.htm (2016-02-12)
    Open archived version from archive

  • Terms, definitions and abbreviated terms
    the Type construct as defined in ISO 10303 11 NOTE 2 Similar in concept to typedef or value type in common programming languages select construct that allows an attribute value to be one of multiple types or entities NOTE 1 Similar to the Select construct as defined in ISO 10303 11 NOTE 2 Similar to a marker interface in common programming languages enumeration construct that allows an attribute value to be one of multiple predefined values identified by name NOTE 1 Similar to the Enumeration construct as defined in ISO 10303 11 NOTE 2 Similar in concept to enum in common programming languages actor person an organization or person acting on behalf of an organization NOTE A specialization of the general term object classification categorization the act of distributing things into classes or categories of the same type constraint restriction for a specified reason NOTE A specialization of the general term control control directive to meet specified requirements such as for scope time and or cost NOTE A specialization of the general term object dictionary collection of words terms or concepts with their definition element tangible physical product that can be described by its shape representation material representations and other properties NOTE A specialization of the general term product element occurrence element s position within the project coordinate system and its containment within the spatial structure external reference link to information outside the data set with direct relevance to the specific information the link originates from inside the data set feature parametric information and additional property information modifiying the shape representation of an element to which it applies group collection of information that fulfills a specified purpose NOTE A specialization of the general term object library catalogue database or holder of data that is relevant to information in the data set NOTE It is information referenced from an external source that is not copied into the data set object occurrence characteristics of an object as an individual NOTE Similar to object instance individual in other publications object type common characteristics shared by multiple object occurrence s NOTE Similar to class template type in other publications process object occurrence located in time indicating when process occurrence conceptual object that may occur at a particular time process type common characteristics shared by multiple process occurrence s product physical or conceptual object that occurs in space NOTE It is specialization of the general term object product occurrence physical or conceptual object that may have a location in space and shape characteristics product type common characteristics shared by multiple product occurrence s project encapsulation of related information for a particular purpose providing context for information contained within NOTE Context information may include default measurement units or representation context and precision property unit of information that is dynamically defined as a particular entity instance NOTE Similar to late bound or run time in programming terminology property occurrence unit of information providing a value for a property identified by name property template metadata for a property

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-3.htm (2016-02-12)
    Open archived version from archive

  • Fundamental concepts and assumptions
    specific use Such concepts also form the basis of Model View Definitions which are supplementary specifications that adapt the scope and rules of this schema for targeted domains within the building industry Each concept template defines a graph of entities and attributes with constraints and parameters set for particular attributes and instance types Various entities within this schema reference such concept templates and adapt them for particular use according to

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-4.htm (2016-02-12)
    Open archived version from archive

  • Core data schemas
    can be referenced and specialized by all entities above in the hierarchy The core layer provides the basic structure the fundamental relationships and the common concepts for all further specializations in aspect specific models All entities defined in the core

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-5.htm (2016-02-12)
    Open archived version from archive

  • Shared Element Data Schemas
    of entities as shown highlighted in blue Entities defined in this layer can be referenced and specialized by all entities above in the hierarchy The shared element layer provides more specialized objects and relationships shared by multiple domains 6 1

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-6.htm (2016-02-12)
    Open archived version from archive

  • Domain Specific Data Schemas
    as shown highlighted in blue Entities defined in this layer are self contained and cannot be referenced by any other layer The domain specific layer organizes definitions according to industry discipline 7 1 IfcArchitectureDomain 7 2 IfcBuildingControlsDomain 7 3 IfcConstructionMgmtDomain

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-7.htm (2016-02-12)
    Open archived version from archive

  • Resource Definition Data Schemas
    the same instance of a resource entity does not imply a relationship For example two polylines IfcPolyline sharing the same instance for a point IfcCartesianPoint and two polylines using different instances for identical points such as both having cordinates 0 0 0 are semantically equivalent It is recommended but not required for applications to minimize file size by sharing identical resource definition instances where possible NOTE The resource definition layer

    Original URL path: http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/chapter-8.htm (2016-02-12)
    Open archived version from archive



  •