This section of the standard specifies requirements and rules for naming object files, properties, property sets, materials, views, and material image files.

2.1 General naming requirements

This subsection of the standard specifies the general nomenclature requirements applicable to all discussed situations under this standard.

2.1.1 Naming Fields: Object files, materials, and material image files shall be named using the naming fields in Table 2A, arranged according to the appropriate naming clauses below. Field Description Example <Type> Identifies the type of object or material. Door <Subtype> Should be used to identify the subtype of an object or material. Interior <Source> Identification of the manufacturer of the product. Should be used for reserved objects. SupaDoors <Product / scope identifier> The identifier for the manufacturer's product or assortment. Let it be used for restricted objects. D130ST <Differentiator> May be used to provide additional information required to identify an item or material. 760 W. <Originator> A 3 to 6 character code may be used to identify the provider of the facility. Should be used for objects shared by an object library. ABC Table 2A - Naming Fields 2.1.2 Characters The names and naming fields only contain the following characters: • Uppercase letters (A through Z) from the ISO basic Latin alphabet. • Lowercase letters (a to z) of the ISO basic Latin alphabet. • Numbers (0 to 9). • An underscore (_), used only to separate fields in the name. • Single period (.), Used only to separate the filename from the extension. Names and naming fields must not contain any of the following characters: • Mathematical symbols or operators, including but not limited to (! ",% $ ^ ^ & * {} [] + - = <>? | \ / @ '~ # ¬ ``). • Spaces. Avoid using the hyphen as it can cause errors when name (or property) is used in formulas, as the hyphen also represents a mathematical subtraction operator.

2.1.3 Naming Rules: PascalCase is used to concatenate separate words in naming fields and for naming properties. Separate the fields in the name with an underscore (_). Shortcuts can be used as needed. Recognized industry abbreviations are used where they exist, e.g. PVC,

2.2 Object file naming requirements

This subsection of the standard specifies the naming requirements for object files. Including proprietary / general / Project Object Naming, Parametric Object Naming, and Dimensional Information in File Names.

2.2.1 File naming rules: An object file name must be a unique, human-readable description of the object. The object file name must comply with clause 2.1. Relevant dimensional information can be included in the field identifier and should include the unit of measurement. For example, 300 x 700mm, 400mm x 30m, 1200mm.

2.2.2 File naming of parametric objects: The subtype of a field with a parametric object filename should be Pascal case combination of variants represented by the object. For example, RectangularSquare.

2.2.3 File name structure: The object file name is structured as follows, unless local requirements specify otherwise: <Type> _ <Subtype> _ <Source> _ <Product / scope identifier> _ <Differentiator> _ <Originator>

2.3 Real estate naming requirements

This subsection of the standard specifies the property naming requirements (also known as attributes or parameters) associated with BIM objects. BIM properties are variables that store data about an object. Property nomenclature must provide a human-readable description of the properties they require, and adopt conventions and methodologies used in modern programming language techniques to automatically use the data they contain.

2.3.1 Unique Properties: Each unique concept describing information about an object should have a unique property name.

2.3.2 Property naming rules: Properties shall be named according to clause 2.1. Properties should be named in a consistent and logical manner to increase clarity and usability. Each property name must be a unique, human-readable description of the property value requirements.

2.3.3 Boolean properties: Properties that require completion of values ​​with a Yes / No or True / False enumerator will be named indicate such requirement, for example "IsExternal".

2.3.4 Suffix: If user edited / created property sets are not supported in your BIM authoring system (see clause 4.10), a 3- to 6-character suffix may be added to the end of each property name, separated by an underscore (_). to identify the source of the property. For example, DoorPanelHeight_ANZRS. Note: The suffix cannot be added to the end of property names from defined data schemas, such as IFC (Industry Foundation Classes) or COBie. Property names from any defined data schema may not be changed or changed in any way.

2.4 Property set naming requirements

This subsection of the standard specifies the naming requirements for property sets associated with BIM items.This is to facilitate the metadata in an IFC compliant format. Not all BIM proprietary systems fully support the concept of property sets for BIM objects, for example Revit only allows you to assign a user object properties for hardcoded groups, however, the shared parameter file assigns each property to a group, which is a concept equivalent to property sets

2.4.1 Property sets: Object properties should be grouped into logical sets, see section 4.10.

2.4.2 Rules for naming a property set: Property sets shall be named according to clause 2.1. Property set names should contain the descriptive context for grouping. Property set names have a prefix followed by an underscore to indicate the origin of the property set, for example OBOS_, COBie_, ANZRS_. IFC property sets should be named with the appropriate IFC property set name (Pset_). For properties specified in this standard, the property set name should be in italics in the table title. For example, for the properties in "Table 4A - OBOS_Admin Properties", the property set name will be OBOS_Admin.

2.5 Requirements for the naming of materials

This subsection of the standard specifies the material naming requirements for BIM-related items

2.5.1 Material naming rules: Materials shall be named in accordance with clause 2.1. Material names should be unique, human-readable descriptions of the material.

2.5.2 Material name structure: The material name has the following structure: <Type> _ <Subtype> _ <Differentiator>

2.6 See control naming requirements

This subsection of the standard specifies the naming requirements for view controls related to BIM items. BIM authoring systems control the display of objects in various ways, such as layers and subcategories. If views can be named by the user and shared with objects, it is important to name them consistently to avoid propagation.

2.6.1 See Control Naming Rules: If your BIM authoring system supports user-defined view control, the views should be named as follows: • As per clause 2 .1. • in the plural. • Be consistent and logical to increase transparency and usability.

2.6.2 View the structure of the control names: The name of the view control is structured as follows, using the fields from table 2B: <UsageGroup> _ <UsageSubGroup> _ <Differentiator> Field Description <UsageGroup> Can be used to name the main target of a group or use it for plumber example. <UsageSubGroup> Should be used to name a subgroup target or use if the usage group spans multiple concepts, for example Plumbing_Sanitary. <Differentiator> Can be used to further differentiate a subgroup, for example Sanitary fittings. Table 2B - Display of control naming fields

2.7 Material image file naming requirements

This subsection of the standard specifies the naming requirements for material-related image files.

2.7.1 Rules for naming material image files: Image files shall be named according to clause 2.1.

2.7.2 Material image file name structure: The image files should be named identically to the corresponding materials (see section 2.5), with the addition of the .bmp or .jpg file format extension.

This section of the standard specifies the requirements for classifying an object and assigning it the correct IFC marking.

3.1 IFC Object Designation

This subsection of the standard specifies the object tagging requirements in IFC to aid the interoperability of a BIM object between different BIM applications. The available information is in Annex A. IfcElementTypes and PredefinedTypes in the IFC4 schema.

3.1.1 IFC Type: The BIM Object shall be marked as appropriate IfcElementType and PredefinedType, see clause 4 .3 .2.

3.2 Object classification

This subsection of the standard specifies requirements for the classification of a BIM object. Due to the proliferation of systems used, an object may need to support multiple classifications (addressed) in section 4 of this standard).

3.2.1 Classification System: The facility should be classified using a system (s) that reflect the systems of the jurisdiction in which the facility to be used is located. The classification code should be as specific as possible for the type of facility, see section 4.6.1.

3.2.2 Classification Permanently: BIM items can be classified using the BIM authoring system 'S coded ensemble code (or cost code) and guiding code.

This section of the standard specifies the properties that should be assigned to a BIM object. It also covers grouping properties and assigning properties to object types or instance objects.

4.1 General requirements for object properties

This subsection of the standard sets out general rules for properties associated with BIM objects, including requirements for using nonconforming coded properties in BIM applications.

4.1.1 Provision of properties: Properties can be embedded in the object or linked via a unique link to an external database.

4.1.2 Property Scope: Only those properties deemed necessary to adequately define an object for its intended BIM use (s) and to ensure the interoperability of the objects between BIM applications should be ensured.

4.1.3 Duplicating a property: An object does not contain duplicate property instances. Where an identical property exists in multiple sources by name or description / value requirement (for example, IFC and COBie), it only covers one instance of that property. IFC properties take precedence over properties from other sources.

4.1.4 Hard-coded properties: Use hard-coded properties in the BIM authoring system. Hard-coded properties shall be mapped to corresponding IFC properties during export if required, see clause 7 .2.

4.1.5 Own and general object properties: Reserved objects should have at least the same properties as generic objects of the same object type and subtype.

4.1.6 Property values: Property values ​​should be completed if known. Reserved objects should have all Type property values ​​filled, see section 4.2 .1. Property values ​​can be supplemented with: • A constant value for which only one value is available or it has been decided which value is required, for example 6000. • A range of values ​​for which a limited range of values ​​is available and no decision has been made which value is required. The lower and upper limits of the available range should be separated by a sign and a hyphen, for example 100 - 600. • A computed value where multiple values ​​are available from a defined list of enumerators and it has not been decided which value is required. Each available enumerator should be separated by a comma, such as X, Y, Z. • Formula if the value depends on the value of another property. • Property values ​​cannot: • End with a period (.). • Include units unless specifically required in the property description.

4.1.7 Ownership Units: Units should be metric unless local requirements state otherwise

4.1.8 Property data type: Properties should have a data type defined using ANSI SQL data types selected from the following list: • Character (text, string) - for fields requiring alphanumeric or text values. • Integer - For fields that require integers. • Decimal (number, currency) - for fields requiring decimal numbers. • Date - for fields that require a date in the year-month-day (YYYY-MM-DD) format. • Boolean (Yes / No, True / False) - for fields requiring selection from two options. • Hyperlink (URL) - a string field in which the values ​​are links represented by www. Web page . domain / path. If the data type listed above is not available or a more specific hardcoded data type is available, the BIM authoring system used should use the most appropriate hardcoded data type. For example, if there is no Date Data Type, use a character type and enter the date in the correct format.

4.1.9 Assembly properties: Teams should not have properties assigned to the assembly itself. All properties will be assigned to the objects included in the assembly.

4.2 The type of the object or property of the instance

This subsection of the standard covers the concept of properties that are properties of a property type or instance. Objects of type represent defined specifications of physical elements. The type information contained in an object is common to all instances of the object. An instance of an object is the unique placement of a type object in the model. The instance object can contain unique information such as serial numbers and installation or commissioning information.

4.2.1 Type properties: A property that has a constant value for all instances of this type of object will be treated as a Type property. The library object type property values ​​can be pre-completed.

4.2.2 Instance Properties: A property that requires a value that is specific to an instance of that object type should be treated as an instance property. Library object instance property values ​​cannot be pre-populated.

4.3 Properties of IFC

This subsection of the standard defines the IFC properties to be assigned to the BIM object.

4.3.1 IFC for interoperability: To ensure greater object and model interoperability between different BIM applications, all objects should contain IFC4 buildingSMART properties (Addendum 2) that directly correspond to this type of object.

4.3.2 Marking properties of IFC objects: The object contains a property named "IfcExportAs", the value of which is completed with the corresponding IfcElementType from IFC4 (Add 2). For example, "IfcPile" for a pile foundation. The object should contain a property named "IfcExportType", the value of which is completed with the appropriate PredefinedType, selected from the calculated list available for the designated IfcElementType. For example, "DRIVEN", for a driven pile foundation. Note: BIM authoring applications can automatically assign the "IfcExportAs" and "IfcExportType" properties, based on built-in tools or templates used to model the object, see section 5 .2 .1

4.3.3 IFC proxy object designation: If the corresponding IfcElementType model does not exist in IFC4 (Add2), for the modeled object, then "IfcExportAs" should be completed with the "IfcBuildingElementProxy" property, and the "IfcExportType" property should be supplemented with "USERDEFINED". After IfcBuildingElementProxy is designated, the object should contain an additional property "ElementType", with the value padded with a descriptive name to define the object type.

4.3.4 Common IFC properties: If there is a common IFC property set (Pset_XXXCommon) for an object type, the properties from that property set should be included. If there is no common IFC property set for the object type, properties from IFC Include the Pset_BuildingElementProxyCommon property set.

4.3.5 Additional IFC properties: Additional properties and property sets from the IFC schema can be included, such as quantity sets (Qto_) and environmental impacts. If a property in the IFC4 schema (Add2) relates to the same concept as the property proposed for when included, use the IFC property.

4.4 Administrative properties

This subsection of the standard defines the properties to be assigned to a BIM object related to object administration and management.

4.4.1 Object administrator properties: The property set from Table 4A should be taken into account for all objects. property Description Data type Example Type / Instance Created By Name of the person, organization or library the vendor who created the object. SupaObjects form Type CreatedByURL URL hyperlink to the website of the creator of the object. Www. Hyperlink. SupaObjects. com Type Modified problem To register the last release date (version or version) of an object in the object library. Value to be completed in the following format <yyyy-mm-dd.no>. The suffix "no" can be used if the object is issued multiple times that day. Date 16.03.2018 .02 Type - Table 4A - OBOS_Admin properties

4.5 Object's own properties

This subsection of the standard specifies the properties to be assigned to the reserved object.

4.5.1 Producer / Product Identification Properties: The property sets in Tables 4B and 4C should be considered for all objects owned by the manufacturer's product (or may be used in the future). property Description Data type Example Type / Instance Manufacturer Organization that manufactured and / or assembled the product. Form SupaObjects Type Model label A descriptive product model name, the model (or product line) assigned by the manufacturer. Form Solid door type Type Reference Model Model number or product designation Model (or product line) assigned by the manufacturer. Form D130ST Type Article number The article number or reference applied to the configured product according to the standard scheme for the article number, definition defined by the manufacturer. It is often used as a purchase number. Form D130ST2100X800 Type Global Trade Item Number The Global Trade Item Number (GTIN) is a trade item identifier developed by GS1 (www .gs1 .org). Integer number 00012345600012 Type Year of production Year of production of the manufactured product. Integer 2018 Enter or Instance Assembly Location Calculate where the assembly to be carried out at the factory or on the construction site is located. Character FACTORY, OFFSITE, SITE, OTHER UNKNOWN, UNSET * Enter or Instance * Allowed enumerators Table 4B - Production type information for property set property Description Data type Example Type / Instance ManufacturerURL URL hyperlink to manufacturer's website. Www. Hyperlink. SupaDoors. com Type Product URL A URL hyperlink to further information about the product, such as technical documentation or installation instructions. Www. Hyperlink. SupaDoors. com / D130ST Type Table 4C - OBOS_Producent Properties

4.6 Classification properties

This subsection of the standard defines the properties that must be assigned to an object in order to classify an object type. Just as there is no generally accepted classification system, this subsection allows the use of multiple classification systems.

4.6.1 Classification System Properties Multiple classification systems can be assigned to a system, including a set of properties into 4D Table for each classification being required. NOTE: Provide <ClassificationSystemName> in the property name of the required classification system and the table designation, if applicable. For example, OmniclassTable23. The examples in table 4D use Omniclass. Table 23 property Description Data type Example Type / Instance Code <Classification system name> Classification code required. Form 23-17-11-00 Type <Name of the classification system> Title Classification title required. Form Door Type <Name of classification system> Version Published version Classification system. Appearance 05/16/2012 Type Table 4D - Classification properties OBOS_Classification

4.7 Design specification properties

This subsection of the standard defines the properties to be assigned to an object in order to associate the object with the appropriate build specification information.

4.7.1 Specification linkage properties: To enable object linkage with design specification information, the property set in Table 4E may be included. NOTE: Replace <SpecificationSystem> in the property name of the required specification system or project specification. property Description Data type Example Type / Instance Code <Classification system name> Specification clause or code / reference section. Form 0453 Type <Name of classification system> Title Specification clause or title section. Character Door and access panels Type Version <Specification System> Published version Classification system. Figure 18 October Type Table 4E - OBOS_Specification properties.

4.8 Asset / facility management properties

This subsection of the standard defines the properties to be assigned to an object for the current resource or management objectives.

4.8.1 Asset properties: If asset data recording is required for asset / facility management purposes, the sets should include the properties in Tables 4F, 4G and 4H Acquisition date Date of manufacture of the manufactured product purchased. Date 16.03.2018 Instance Barcode Barcode assigned to the product instance. Integer 9781119060055 Instance Serial Number The serial number assigned to the product event. Form P345 Instance BatchReference Identity of the batch number from which the product instance is taken. Form P345-20180214 InstanceTable 4F - Properties Pset _ Production instance property Description Data type Example Type / Instance Guarantee ID Identifier assigned to the guarantee. Figure D130ST5135 Enter or Instance Warranty Start Date Warranty Start Date. Date 3/18/2018 Instance Warranty End date Warranty expiration date. Date 03/18/2020 Instance Extended Warranty Issue Indication if it is an extended warranty the duration of which is longer than that normally assigned to the product. Boolean TRUE or FALSE * Instance Warranty period Duration during which the manufacturer's or supplier's warranty or product performance is guaranteed. Integer 2) Type Warranty text Warranty text. Character Product and Installation Enter or Instance Contact Point Organization to contact operating under warranty conditions. Character SupaDoors Type Exceptions Items, conditions or actions that may be excluded from warranty or may void warranty. Character Vandalism Type or Instance * Allowed enumerators Table 4G - Properties Pset_Warranty property Description Data type Example Type / Instance ServiceLifeDuration Length or duration of use. The lower limit indicates a pessimistic useful life, the upper limit indicates an optimistic lifetime, and one value indicates the typical lifetime. Suggested units = Years Integer 2) Enter or Instance Mean Time Between Failures Mean time between occurrences of product failure. Suggested units = years. Integer 3) Type or Table 4H - Pset_ServiceLife Properties

4.8.2 COBie Properties: You can enable COBie properties in 4J and 4K tables if COBie data recording is required. Do not include any duplicate properties from tables 4J and 4K if you are also using properties from tables 4F, 4G, and 4H. property Description Data type Example Type / Instance Name Unique, human-readable object name type. Character Door Type Category A unique identifier for an object within an external source (classification, document or library). It may be human readable (eg classification code) or not (eg GUID) depending on the context of its use (which must be determined by local agreement). Character 23-17-11-00 Type Description A brief description of the object. Character Solid Pinewood Door Type Resource Type Specifies the predefined resource types from which the required type can be set. Character FIXED or Mobile * Type Manufacturer Email address of the organization that manufactured and / or assembled the product. Character Information @ SupaDoors .FRP Type Model Number Model number or product model designator (or product line) as assigned by the manufacturer. Form D130ST Type Warranty Parts The email address for the organization responsible for the parts warranty. Character Info @ SupaDoors.com Type Warranty Duration Parts Warranty period for parts. Integer 3) Type Warranty Warranty Warranty The email address for the organization responsible for the warranty of work. Character information @ SupaDoors .com Type Warranty Duration Labor Warranty period of work. Integer 3) Type Warranty Duration Unit Units used to record warranty duration. Suggested units = years. Form Years Type Replacement cost Cost of product replacement. Decimal 1000 .00 Type Life expectancy The expected life of the product. Integer 15 Type Time Unit Units used to record life expectancy. Duration. Suggested units = years. Form Years Type Warranty Description A brief description of the warranty, content and any items, conditions or actions that are excluded from the warranty or will result in the warranty becoming void. Appearance Product and installation Type Nominal length Usually basic or greater with two orthogonal horizontal product dimensions. Integer 800 Type Nominal Width Usually minor or less of two orthogonal horizontal product dimensions. Integer number 40 Type Nominal height Typically vertical characteristics product dimension. Integer 2100 Type Model Reference The descriptive model name of the product model (or product line) as assigned by the manufacturer. Appearance Solid pine wood Door Type Shape Characteristic shape of the product. Prost character diagonal Type Size Characteristic size of the product. Form Large Type Color Characteristic color of the product. White form Type of end Surface finish specification. Form Glossy paint Type Grade Standard grades for which: the product corresponds. Appearance Internal Type Material Characteristic material the product is made of. Form Pine Type Ingredients Details of the various parts of the product. Appearance Solid panel door Type Function Basic features or important characteristics of the product. Character Single leaf Type Availability Performance The problems with the availability of this product meet. Form Automated Type Code performance Code compliance requirements that the product meets. Form Fire resistance Type Sustainability Sustainability problem (s) for this product meets Form Recycled wood Type * Acceptable counts Table 4J - COBie_Type properties Serial number Serial number assigned to the product instance. Character D130ST2100X800 Instance Install Date Date when the manufactured product was created installed. Date 3/18/2018 Instance Warranty Start date Warranty start date. Date 2018-03-18 Instance Tag number The tag identifier (number or label) for the product or device instance in the installation. Character D456 Instance Bar code The bar code assigned to the product instance. Integer 9781119060055 Instance Resource ID Alternate identifier for a specific component, used by contract. Character D456-C Instance Table 4K - COBie_Component Properties.

4.9 Product performance properties

This subsection of the standard specifies the product performance or compliance properties assigned to the object.

4.9.1 Product declaration / certification properties: Where a product declaration / certification template (PDT), technical product declaration (PTS), evaluation, certification or similar physical element exists, the object should cover the set of properties contained in Table 4L NOTE: Instead of the name of the technical document replace <TechnicalDocument> with the name of the technical document, CodeMark example. property Description Data type Example Type / Instance <Technical Specification 1> URL URL hyperlink to technical page document. Www. Hyperlink. code mark. com / 1234 Type <Technical Specification 2> URL URL hyperlink to technical page document. Www. Hyperlink. product data. com / 1234 Type Table 4L - OBOS_ technical properties

4.9.2 Technical performance properties: The object may contain the properties of the items planned in the technical documents listed in Table 4L if required for the intended use of the object by BIM

4.10 Property Grouping (Property Sets)

This subsection of the standard specifies the requirements for grouping properties into property sets and the use of property sets. This is to facilitate the metadata in an IFC compliant format. Not all BIM authoring systems fully support the concept of property sets in their BIM objects, for example only Revit allows this the user assigns object properties to hardcoded groups. However, in Revit's shared parameter file, assign a group to each property that is equivalent to property sets.

4.10.1 Property Grouping Requirements: Properties should be grouped into property sets (groups) to facilitate property management, navigation and display. Property sets shall be named as specified in clause 2.4. Properties should be logically and consistently grouped across all objects, based on their source and purpose use / function. If user edited / created property sets are not supported in your BIM authoring system, the properties will be assigned to the most appropriate coded property group in the BIM authoring system.

4.10.2 IFC property sets: The IFC properties will be grouped in the appropriate IFC property sets (Pset_ and Qto_). 4.10.3 Property Source: Properties from any non-IFC source will be grouped in a property set named for uniquely identifying the property source. For example, COBie_, ANZRS_. If user edited / created property sets are not supported in your BIM authoring system, then a suffix may be added to the name of each property to identify its source, see clause 2.3.

This section of the standard defines the general modeling requirements for the graphic element of a BIM object.

5.1 Detailed graphics of the facility

This subsection of the standard covers the graphic requirements for general and restricted facilities.

5.1.1 General Objects: Generic objects must be visually recognizable as the type of object they represent, and the dimensions represent the extent of the object and its connectivity. Generic objects can contain sufficient geometric detail for coordination purposes or to visualize the object and anticipate its operation and use.

5.1.2 Restricted Items: Ownership items must be visually identifiable as a physical element they represent and are critical dimensions must be accurate for coordination purposes. Custom objects can contain sufficient geometric detail to visualize an object and predict its operation and use.

5.2 Requirements for geometric modeling

This subsection of the standard covers the requirements for creating a geometric BIM object, including the requirements for the insertion point, units, scale, tools used, dimensioning, and labeling.

5.2.1 Modeling tools: The object should be modeled using an appropriate or the most appropriate tool / template from within the BIM authoring system. The selected tool / template should be taken into account for the IFC Tag to be assigned to the site, see clause 3.1.

5.2.2 Object start point: The object start point (or base point) must be set for a BIM object from which all object geometry will be determined. The origins of the object must be consistent for identical or similar object types to allow simple substitution of alternative BIM objects. The starting point of the object may correspond to the insertion point of the object, see point 5 .2 .3.

5.2.3 Insertion Points: An insertion point is established for the BIM object that logically represents the position of the object in the design model. The insertion points must be consistent for identical or similar object types to allow simple substitution of alternative BIM objects. The insertion point should be within the scope of the object. Particular attention should be paid to objects with parametric geometry to allow the geometry of the object to change in the model environment and the position of the object to maintain correctness. For example, the column insertion point should be on the centerline so that you can resize the column if necessary without changing the position of the column centerline. NOTE: BIM content authoring systems typically require the structural members to have an insertion point at the center of gravity, this element supports any analytical calculations to which the model can be applied.

5.2.4 Scale: The object is modeled on a scale of 1: 1.

5.2.5 Units: Metric geometry in millimeters shall be used, unless local requirements state otherwise or if the scale is the modeled object would fit better in meters or kilometers.

5.2.6 Fixed geometry: Fixed geometry should be used when the object modification is not intended. For example, a reserved object that is only available in one size.

5.2.7 Dimensioning: All dimensions should be limited to reference elements such as planes, lines, or points and not directly to geometry. Dimensions are calculated automatically using associative dimensioning functions in the BIM authoring system. Dimensions should be outside the geometry of the object. The dimensions should not coincide and should be legible.

5.2.8 Labels: All labels should be limited to datums such as planes, lines, or points and not directly to geometry. Labels reflecting the information contained in the object's metadata must match that data.

5.2.9 Object Color: The default gray color can be applied to objects representing physical elements available in more than one color. Alternatively, a representative color can be used for the physical item.

5.2.10 Editorial conventions: Use visual drawing conventions, such as linetypes, hatches, and fills, with the appropriate tools available in the BIM content authoring system to distinguish between different parts of an object and show surface depth differences in different views. Hatch should be assigned to the appropriate materials or part description for the body, not added as 2D Information. Use symbolic lines in plan views, not a geometric solid. The use of arrays, patterns and voids when modeling an object should be kept to a minimum. 2D lines and symbols can be used to indicate elements that cannot be modeled or to supplement 3D geometric information such as to indicate the direction of flow or the direction of the faucet.

5.2.11 Material Assignment: For Restricted Objects, appropriate materials must be assigned to represent the physical elements of the constituent materials. Materials can be assigned to general objects.

5.3 What to model

This subsection of the standard specifies what should and should not be included in the geometric model of the object, such as maintenance zones, hidden content, and other spatial requirements.

5.3.1 Pre-planning: The geometrical modeling of the facility should be planned, including any parametric relationships, to: consider what graphic details are required / necessary and what information will be visible in the different views. Note: Small items or non-critical items of an object may not require modeling as they may impact model performance.

5.3.2 Detail: An object represents the form of the outer boundary of a physical item without providing excessive or unnecessary detail. Details that would not be visible (or hidden) should not be modeled unless required for the intended BIM application. For example, the surface of the dresser only needs to show the surface of each drawer, the drawer itself must not be modeled.

5.3.3 Connection points: Items that are required to connect to other objects such as a fan assembly to a duct should have the relative position of their connection points accurately modeled.

5.3.4 Spatial requirements: Objects representing physical elements that have spatial requirements such as clearance zones, operation zone or maintenance zones should also have the spatial requirements that have been modeled. In modeled spatial requirements, their visibility should be controlled, but the default is spatiality, zones are not visible.

This part of the standard discusses the requirements for improving the functionality and performance of BIM objects so that they do not adversely affect the performance of the model in which they can be placed.

6.1 Facility performance

In this subsection of the standard details, steps should be taken to reduce the size of the BIM object file to improve the performance and reliability of the model.

6.1.1 Cleanup: All unused or temporary modeling content such as unused line types, reference items, images, line construction, or CAD content will be cleared or removed from the object after modeling is completed.

6.1.2 Save and Compress: After completing the modeling of the object, the file should be saved using the "Save As" function with another name used when creating it to remove the temporary history data attached to the original file. Where supported by the BIM build system, the resulting file must also be compressed to minimize its size.

6.1.3 Testing: Objects are tested according to the intended function of the object to ensure that they function as intended.

6.2 Object Relationships: This subsection of the standard covers requirements for assemblies, nested objects, and objects that depend on other objects to function as expected.

6.2.1 Reliance: Objects are modeled not to be dependent on other objects, unless it is a specific requirement of the object type that requires a host object, such as a wall-mounted light fixture, that would be wall-dependent object Objects with parametric behavior may depend on other types of objects, see point 6 .4.

6.2.2 Assemblies: Assemblies should only be created where it may be necessary or advantageous to represent a group of component bodies collectively in an assembly, and not as individual component bodies. Assemblies can contain multiple features.

6.2.3 Nested Objects: Nested objects (objects embedded in objects) should only be created where it may be necessary or advantageous to represent the component objects in the nested object individually from the nested object itself. Nested objects will be limited to two levels (ie, Object on Object within Object).

6.3 Visibility / Views

This subsection of the standard covers the requirements for the visibility of objects and their display views. BIM content authoring systems control the display of objects in various ways, such as layers and subcategories that need it, avoiding the multiplication of views in models.

6.3.1 Thumbnails and Previews: The thumbnail previews should be set to a clear, appropriate and consistent view orientation, and appropriate size and resolution. All reference elements and dimensions will not be visible in these images.

6.3.2 Object resolution: It shall be possible to change the resolution of the object when viewing the object at different scales and the displayed graphical information shall be controlled. The three resolution scales should be sufficient and should be given for each feature as follows: • Coarse: typically used for low detail and low fidelity views, typically at a scale greater than 1: 100. Visible geometry should indicate only a physical feature and may contain symbolic 2D lines. • Medium: Typically used for views on a scale of 1:20 to 1: 100. The visible geometry should be sufficient to represent a physical element. • Fine: Typically used for very detailed views, usually on a scale of 1: 1 to 1:20. The visible geometry may reflect the detailed geometry of a physical item.

6.3.3 View control: Views shall be named according to clause 2.6. Objects are assigned the appropriate view or views in a consistent and logical manner.

6.4 Parametric behavior

This subsection of the standard covers the requirements for creating objects with parametric behavior.

6.4.1 Functional Behavior: Parametric objects that depend on the host objects on / on which they are placed should be created using specific functionality to manipulate the host object or vice versa as required. For example, a parametric window object that needs to be modeled to create a corresponding void in the wall object to which it would be placed, or alternatively, if the wall thickness changed, the suit window size would adjust.

6.4.2 Geometric behavior: Parametric objects are created when an object can represent geometric variants of the object type. The parametric capacity of the object should be limited to the available variants of the physical element it represents. For example, if a physical element is available in 4 different lengths, limit the parametric length of the object function to these 4 available lengths.

6.4.3 Multiple IFC types: Objects cannot be created with a parametric function to allow an object to represent multiple IfcElementType. For example, don't create one object that can represent a bathtub as well as a sink, as these objects are represented by different IfcElementType. In this situation, duplicate the parametric objects and assign them an appropriate IfcElementType, one to represent each required IfcElementType. For example, one to represent a parametric bath and one to represent a parametric sink.

6.4.4 Reference Positions: When modeling objects with parametric geometry, the parametric behavior should be controlled by referencing elements such as planes, lines or points.

6.4.5 Limitations of use: The use of parametric behavior should be limited to what is deemed necessary or required to avoid unduly restricting the functionality of the facility.

This part of the standard covers methods for importing properties and content into a BIM object, as well as any requirements for preparing a BIM object for export.

7.1 Importing information

This subsection of the standards discusses the requirements and recommendations for importing information (graphical or non-graphical) into a BIM object. Imported geometry can limit functionality and parametric possibilities, increase the possibility of file corruption, and increase the size of object files.

7.1.1 Geometric information: Where possible, use native geometry in the BIM content authoring system. Geometry can be imported from other authoring systems or sources, but should only be used temporarily for modeling purposes and removed when no longer required, see section 6 .1 .1.

7.1.2 External datasets: Datasets (properties and property sets) can be imported into objects. Imported datasets must comply with the data requirements of this standard.

7.2 Exporting BIM Objects

This subsection of the standard covers the requirements and recommendations for preparing BIM objects for export to other BIM applications, such as the requirements for mapping a non-compliant property code from the BIM authoring system to the correct IFC property.

7.2.1 IFC Assignment: Check the "IfcExportAs" and "IfcExportType" properties and fill in the values ​​before the export object, see section 4 .3 .2.

7.2.2 Mapping hard-encoded properties: Where the hard-coded property is identical in description / value to the specified IFC property but does not match the name of the corresponding IFC property identically, the hard-coded property will be mapped to the corresponding IFC property during export. Note: Some BIM authoring systems automatically map hardcoded properties to the corresponding IFC of the property.

7.2.3 External datasets: The object can be linked to external datasets. Any properties required by downstream BIM applications / applications are natively stored on the facility at the time of export or prior to export, unless such downstream BIM applications are also able to access the relevant datasets.

7.2.4 Test export: Objects should be tested to ensure that the export results are as intended.

8.0 Definitions and dictionary

This section of the standard contains the definitions and terms used in the standard. For the purposes of this Standard, the following definitions apply:

ANSI SQL: Specification that describes the official characteristics of the SQL database language. Each variant of SQL relational databases implements an ANSI SQL subset.

Assemblies: A named aggregation of BIM objects that form another object or functional unit.

Associative dimensioning: A feature of the BIM authoring system that automatically updates the dimension value when there are changes to the geometry of an object.

BIM Content Creation System: Application used to generate data for many applications including 3D Geometry Information. EXAMPLES: Autodesk® Revit®, Bentley® AECOsim®, Graphisoft® ArchiCAD®, Nemetschek® Vectorworks® and Tekla® Structures.

COBie: Construction work. Exchange of information about buildings. Representation of an IFC schema transfer view, usually viewed as a spreadsheet. (ISO 15686-4)

Field: The data field is where the data is stored. Commonly used for a column in a database or field in a data entry or web form. Overall, it is the smallest component at which data is captured. This standard applies the concept of fields to components of a name (property / file / view) that holds a specific piece of Information.

Generic Object: A general representation of common features and properties of a physical item, intended for use in the early design stages or when the object is not decoupled into product.

Strongly coded: Field coded in the software interface where the user is unable to change the field name

IFC: Industrial Foundation grades (ISO 16739). An open file format developed and maintained by buildingSMART for the exchange of improved information models.

Insertion point: The point on an object used to place it in the model.

Layered objects: An object usually constructed of one or more layers of materials to form a building system. Typically these are "system" objects provided by a BIM content authoring system with no fixed geometry where the user can modify the layers and thickness, but the geometry is created when placed in the model.

Library: A collection of reusable BIM objects stored as separate files that are used to facilitate the use of standardized designed or manufactured elements and objects in a project or a series of projects.

Metadata: A term for collecting properties, names, or data related to an object, item, or file. (May also be known as Attributes, Parameters, and Properties.)

Start point: A fixed reference point for the geometry of the surrounding space defined by X, Y, and Z. Objects have a start point that all other points in the object reference. The model has a starting point and objects placed in the model relate to it.

Parametric: Using pre-programmed rules or algorithms to provide the user with the ability to change or configure objects during modeling.

property: A characteristic, feature, or measurable factor related to an object that can help define the object (or system). (May also be known as an Attribute, Parameter, or Metadata.)

Property set: Grouping of properties that belong together based on some principle, e.g. point of view, Life cycle stage. (ISO 15686-4)

Reserved object: Representation of the common features and properties of the obtainable product.

View Control: A function in a BIM content authoring system that controls which objects or parts of objects are visible at any point in the model. BIM authoring systems control the preview of objects in different ways, such as layers or subcategories.

This OBOS add-on contains the IfcElement Type list and an associated list of Predefined Type Enumerators, from the IFC4 schema (Add 2). The following list can be used to designate a BIM object in IFC as per clause 3 .1 .1 and clause 4 .3 .2 OBOS. The IfcElementType S ”listed in bold formatted text below, immediately followed by the available PredefinedType enumerator for that IfcElementType in CAPITAL letters. IfcElementType is used as the value for the "IfcExportAs property" and PredefinedType is used for the "IfcExportType" property. For example, for a Steam boiler, the value for "IfcExportAs" would be "IfcBoiler" and the value for "IfcExportType" would be "STEAM".

Ifc actuator: ELECTRIC ACTUATOR MANUAL ACTUATOR HYDRAULIC ACTUATOR PNEUMATIC ACTUATOR THERMOSTATIC ACTUATOR NOT SPECIFIED USER DEFINED

Ifc airport terminal: CONSTANT FLOW VARIABLE PRESSURE FLOW VARIABLE PRESSURE FLOW NOT SPECIFIED USER-DEFINED

Ifc airport terminal: GRILLE DIFFUSER BLIND REGISTER NOT SPECIFIED USER-DEFINED

Heat recovery air-to-air Ifc: NAPRAWIONOPLATECOUNTERFLOWEXCHANGER NAPRAWIONYPLATECROSSFLOWEXCHANGER NAPRAWIONYPLATEPALALNYPŁYWNIK EXCHANGER HEATPIPE rotating wheel RUNAROUNDCOILLOOP HEAT TERMOSIPONU THERMOSIPHONSEALEDTUBEHEATEXCHANGER TWINTOWERENTHALPYRECOVERYLOOPS NOT DETERMINED USER DEFINED

Ifc Alarm: BELL BREAKGLASS BUTTON LIGHT MANUALPULLBOX SIREN HOOK NOT SPECIFIED USER-DEFINED

Audiovisual device Ifc: AMPLIFIER CAMERA SHOW MICROPHONE PLAYER MEDIA VIEWER RECEIVER SPEAKER SWITCH PHONE TUNER USER DEFINED, NOT SPECIFIED

Ifc Beam: BEAM EMPTY CORE LOCK OVERRUN PACHA T_BEAM NOT SPECIFIED USER-DEFINED

Ifc Boiler: STEAM WATER NOT SPECIFIED BY THE USER

Building element part Ifc: PRECASTPANEL INSULATION NOT SPECIFIED USER-DEFINED

Ifc Building Element Proxy: PROVISIONFORVOID SPACE RULES NOT SPECIFIED USER-DEFINED

Ifc Building System: FENESTRATION LOADBEARING FOUNDATION OUTDOOR COAT SHADING TRANSPORT NOT SPECIFIED USER-DEFINED

Ifc Burner: NOT SPECIFIED USER-DEFINED

Ifc Cable clamp assembly: TURN CROSS REDUCER TEE NOT SPECIFIED USER-DEFINED

Ifc Cable carrier segment: CABLELADDERSEGMENT CABLETRAYSEGMENT SEGMENT CABLETRUNKING CONDUITSEGMENT NOT SPECIFIED USER-DEFINED

IfcCableFitting: CONNECTOR INPUT OUTPUT NODE GATEWAY NOT SPECIFIED USER-DEFINED

IfcCableSegment: CARBON SEGMENT CABLESEGMENT CONDUCTORSEGMENT CORESEGMENT NOT SPECIFIED USER-DEFINED

IfcChiller: AIRCOOLED WATER-COOLED HEAT RECOVERY NOT SPECIFIED USER-DEFINED

IfcChimney: NOT USER-DEFINED

IfcCoil: DXCOOLINGCOIL ELECTRIC COIL GASHEATINGCOIL HYDRONICCOIL STEAM COIL WATER COIL WATER COIL NOT SPECIFIED USER-DEFINED

IfcColumn: PILASTER COLUMN NOT SPECIFIED USER-DEFINED

IfcCommunicationsAppliance: ANTENNA COMPUTER FAX MODEM TRANSMISSION NETWORKBRIDGE NETWORKHUB PRINTER RELAY ROUTER SCANNER NOT SPECIFIED USER-DEFINED

IfcCompressor: HERMETIC DYNAMIC AMPLIFIER OPEN TYPE RECIPROCATING ROTARY STAMP ROTARYVANE SINGLESCRE SEMI-HERMETIC SCREW SINGLE SCENE TROCHOIDAL TWINSCREW WELDEDSHELLNON-DEFINERMETNIKA UDEFINERMETICOWO

IfcCondenser: AIRCOOLED EVAPORATIVECOOLED WATER COOLED WATERCOOLED BRAZEDPLATE WATER COOLER WATER COOLED HELLTUBE WATERCOOLED TUBEINTUBE NOT SPECIFIED BY THE USER

IfcController: MOBILE MULTIPLAYER PROGRAMMABLE PROPORTIONAL TOPOSITION NOT SPECIFIED USER-DEFINED

IfcCooledBeam: ACTIVE PASSIVE NOT SPECIFIED USER-DEFINED

IfcCoolingTower: MECHANICAL DESIGN MECHANICAL DESIGN NATURALDRAFT NOT SPECIFIED USER-DEFINED

IfcCovering: CEILING CLOTHING FLOORING MEMBRANE INSULATION CASTING NOT SPECIFIED ROOFING SKIRTING SLEEVE WRAPING DEFINED BY THE USER

IfcCurtainWall: NOT SPECIFIED USER-DEFINED

IfcDamper: BACKDRAFTDAMPER BALANCINGDAMPER BLASTDAMPER CONTROLDAMPER FIREDAMPER FIRESMOKEDAMPER FUMEHOODEXHAUST GRAVITYDAMPER GRAVITYRELIEFDAMPER SMOKEDAMPER RELEASE NOT SPECIFICALLY DEFINED BY

IfcDiscreteAccessory: ANCHORPLATE BRACKET BUT NOT SPECIFIED USER-DEFINED

IfcDistributionChamberElement: FORMEDDUCT INSPECTION CHAMBER INSPECTIONPIT MANHOLE METERCHAMBER OIL PAN RIV VALVECHAMBER NOT SPECIFIED USER-DEFINED

IfcDistributionPort: CABLECARRIER CABLE CHANNEL PIPE NOT SPECIFIED USER-DEFINED

IfcDistributionSystem: AUDIOVISUAL AIR CONDITIONING CHEMICAL MICZNY CHILLED WATER COMMUNICATION COMPRESSED AIR WATER CONDENSER CONTROL TRANSFER DETAILS SALE OF WATER HOME DOMESTICHOTWATER DRAINAGE EARTH ELECTRICAL electroacoustic EXHAUST FIRE FUEL GAS DANGEROUS HEAT LIGHTING lightning protection WASTE URBAN OIL OPERATING POWER GENERATION WATER RAIN COOLING SAFETY WASTE SIGNAL STORM MOBILE TV vacuum ventilation grille Ventilation Waste WATER DELIVERY NOT SPECIFIED BY THE USER

IfcDoor: DOOR GATE FLAP IN FLOOR NOT SPECIFIED

IfcDuctFitting: TURN CONNECTOR INPUT OUTPUT JUNTION OBSTACLE PASSING NOT SPECIFIED USER-DEFINED

IfcDuctSegment: FLEXIBLE SEGMENT RIGIDSEGMENT NOT SPECIFIED USER-DEFINED

IfcDuctSilencer: FLATOVAL RECTANGULAR ROUND NOT SPECIFIED USER-DEFINED

IfcElectricAppliance: DISHWASHER OVEN ELECTRIC FAN STANDING FREESTANDINGELECTRICHEATER COOLER STANDING WATER STANDING WATER HEATER FREEZER FRIDGE_FREEZER HAND DRYER KITCHEN MICROWAVE OVEN REFRIGERATOR FOTOKOPIER CLOTHES DRYER WASHING MACHINE FOR SALE was plotted NOT DEFINED BY USER

IfcElectricDistributionBoard: CONSUMERUNIT DASHBOARD MOTORCONTROLCENTRE DASHBOARD NOT SPECIFIED USER-DEFINED

IfcElectricFlowStorageDevice: BATTERY CAPACITORBANK HARMONIC FILTER INDUCTORBANK UPS NOT SPECIFIED USER-DEFINED

IfcElectricGenerator: CHP ENGINEGENERATOR STAND-ALONE ENGINE NOT SPECIFIED USER-DEFINED

IfcElectricMotor: DC INDUCTION POLIFA RELUCTANCESYNCHRONOUS SYNCHRONOUS NOT SPECIFIED USER-DEFINED

IfcElectricTimeControl: RELAY CLOCK DELAY NOT SPECIFIED USER-DEFINED

IfcEngine: OUTDOOR COMPLEX INTERNAL COMBUSTION NOT SPECIFIED USER-DEFINED

IfcEvaporativeCooler: DIRECTEVAPORATIVEAIRWASHER DIRECTEVAPORATIVEPACKAGEDROTARYAIRCOOLER DIRECTEVAPORATIVERANDOMMEDIAAIRCOOLER DIRECTEVAPORATIVERIGIDMEDIAAIRCOOLER DIRECTEVAPORATIVESLINGERSPACKAGEDAIRCOOLER CONNECTION INDIRECT INDIRECT PARAPOLACYJNE WIEŻARKA COOLING COOLER COVER PACKAGE POŚREDNIEGOAPALNEGO INDIRECTEVAPORATIVEWETCOIL NOT SPECIFIED USER DEFINED

IfcEvaporator: DIRECTEXPANSION DIRECTEXPANSIONBRAZEDPLATE DIRECTEXPANSIONSHELLANDTUBE DIRECTEXPANSIONTUBEINTUBE FLOODEDSHELLANDTUBE SHELLANDCOIL NOT SPECIFIED BY THE USER

IfcFan: CENTRIFUGALAIRFOIL CENTRIFUGALBACKWARDINCLINEDCURVED CENTRIFUGALRADIAL PROPELLORAXIAL TUBEAXIAL VANEAXIAL NOT SPECIFIED BY THE USER

IfcFastener: GLUE MORTAR WELD NOT SPECIFIED USER-DEFINED

IfcFilter: AIR FILTER COMPRESSEDAIRFILTER ODORFILTER OIL FILTER FILTER WATER FILTER NOT SPECIFIED USER-DEFINED

IfcFireSuppressionTerminal: BREECHINGINLET HYDRANT HOLE SPRINKLER SPRINKLERDEFLECTOR NOT SPECIFIED USER-DEFINED

IfcFlowInstrument: AMMETER FREQUENCY PHASEANGLEMETER POWERFACTORMETER PRESSURE THERMOMETER VOLTMETER_PEAK VOLTMETER_RMS NOT SPECIFIED USER-DEFINED

IfcFlowMeter: ENERGY METER GAS METER OILMETER WATER CONSUMPTION METER NOT SPECIFIED USER-DEFINED

IfcFooting: CAISSON_FOUNDATION FOOTING_BEAM PAD_FOOTING PILE_CAP STRIP_FOOTING NOT SPECIFIED USER-DEFINED

IfcFurniture: BED CHAIR DESK FILE CABINET SHELF SOFA TABLE NOT SPECIFIED USER-DEFINED

IfcGeographicElement: TERRAIN NOT SPECIFIED USER-DEFINED

IfcHeatExchanger: SHELLANDTUBE NOT SPECIFIED USER-DEFINED

IfcHumidifier: WASHER ADIABATICA ADIABATICATOMIZING ADIABATICCOMPRESSEDAIRNOZZLE ADIABATICPAN ADIABATICRIGIDMEDIA ADIABATICULTRASONIC ADIABATICWETTEDELEMENT ASSISTEDBUTANE ASSISTEDELECTRIGIDAIRNOZZLE ADIABATICCOMPRESSEDAIRNOZZLE

IfcInterceptor: CYCLONIC GREASE OIL GASOLINE NOT SPECIFIED USER-DEFINED

IfcJunctionBox: POWER DATA NOT SPECIFIED BY THE USER

IfcLamp: COMPACT FLUORESCENT FLUORESCENT HIGH PRESSURE HIGH PRESSURE LED METALHALID METALHALID OLED TUNGSTEN FILE NOT SPECIFIED BY DEFINED

IfcLightFixture: DIRECTIONSOURCE SOURCE POINT SAFETY LIGHTING NOT SPECIFIED USER-DEFINED

IfcMechanicalFastener: ANCHOR SCREW PLUG NAIL NAIL PLATE SCREW FASTENER KNIVES STAPLE CONNECTOR STUDSHEARCONNECTOR NOT SPECIFIED USER-DEFINED

IfcMedicalDevice: AIRSTATION FEEDAIRUNIT OXYGENGENERATOR OXYGEN VACUUM CLEANING NOT SPECIFIED USER-DEFINED

IfcMember: BUCKLE CHORD FLANGE MULLION MEMBER PLATE POST FLAT STEEL LONGBER STEEL STRUT NOT SPECIFIED USER-DEFINED

IfcMotorConnection: BELTDRIVE COUPLING DIRECT DRIVE DO NOT SPECIFY IT IS DEFINED BY THE USER

IfcOutlet: AUDIOVISUALOUTLET COMMUNICATION CONNECTION DATAOUTLET POWER SOCKET TELEPHONE UUTLET NOT SPECIFIED USER-DEFINED

IfcPile: BORED CONSISTENCY DRIVEN FRICTION JETGROUTING SUPPORT NOT SPECIFIED USER-DEFINED

IfcPipeFitting: TURN CONNECTOR INPUT OUTPUT NODE OBSTACLE PASSAGE NOT SPECIFIED USER-DEFINED

IfcPipeSegment: FLEXIBLE CABLE SEGMENT GUTTER RIGIDS SEGMENT SPOOL NOT SPECIFIED USER-DEFINED

IfcPlate: CURTAIN_PANEL SHEET NOT SPECIFIED USER-DEFINED

IfcProtectiveDeviceTrippingUnit: ELECTROMAGNETIC ELECTRONIC THERMAL RESIDUAL CURRENT NOT SPECIFIED USER-DEFINED

IfcProtectiveDevice: CIRCUIT BREAKER LEAKAGE SWITCH FUSEDISCONNECTOR GROUNDING SWITCH FUSEDISCONNECTOR RESIDUAL CURRENT SWITCH VARISTOR CURRENT SWITCH NOT SPECIFIED BY THE USER

IfcPump: SWEATER END SPLITCASE SUBMERSIBLE PUMP SUMPPUMP VERTICALINLINE VERTICAL TURBINE NOT SPECIFIED USER DEFINED

IfcRailing: RAILING RAILING HANDRAILING NOT SPECIFIED USER DEFINED

IfcRampFlight: SIMPLE SPIRAL NOT SPECIFIED USER-DEFINED

IfcRamp: HALF_TURN_RAMP QUARTER_TURN_RAMP SPIRAL_RAMP STRAIGHT_RUN_RAMP TWO_QUARTER_TURN_RAMP TWO_STRAIGHT_RUN_RAMP NOT SPECIFIED BY THE USER

IfcReinforcingBar: ANCHORING EDGE TIEING MAIN FLAT PUNCHING RING SHEAR STAD TEXTURED NOT SPECIFIED USER-DEFINED

IfcReinforcingElement: BAR MESH HEADPHONE FOR PUNCHING TENDON TENDONANCHOR TENDONSHEATH NOT SPECIFIED USER-DEFINED

IfcReinforcingMesh: NOT SPECIFIED USER-DEFINED

IfcRoof: BARREL_ROOF BUTTERFLY_ROOF DOME_ROOF FLAT ROOF ANY FORM DOUBLE SLIP ROOF GAMBREL_ROOF HIP_ROOF HIPPED_GABLE_ROOF MANSARD_ROOF PAVILION_ROOF RAINBOW_ROOWOF ZOYOF SHEDFREIN_ROOWOF SHED

IfcSanitaryTerminal: BATH BIDET TANK SANITARY FOUNTAIN SHOWER DRINK TOILETPAN WRITER Sink NOT SPECIFIED USER-DEFINED

IfcSensor: CO2 SENSOR CONDUCTANCESENSOR KONTAKTOR COSENSOR FIRESENSOR FREEZING SENSOR FLOW SENSOR HUMIDITY SENSOR HEATER GASSENSOR ID IONCONCENTRATIONSENSOR LEVEL SENSOR LIGHT SENSOR MOTION SENSOR WILGOTNIK PHSENSOR SENSOR PRESSURE SENSOR RADIATION RADIOACTIVITY DETECTOR SMOKE DETECTOR SENSOR SOUNDDSENSOR WINDSENSOR NOT SPECIFIED USER DEFINED

IfcShadingDevice: AWNING BLIND SHUTTER NOT SPECIFIED USER-DEFINED

IfcSlab: BASESLAB FLOOR LANDING ROOF NOT SPECIFIED USER-DEFINED

IfcSolarDevice: SOLAR COLLECTOR SOLAR PANEL NOT SPECIFIED USER-DEFINED

IfcSpaceHeater: CONVECTOR CAR COOLER NOT SPECIFIED USER-DEFINED

IfcSpace: OUTDOOR GFA INDOOR PARKING SPACE NOT SPECIFIED USER-DEFINED

IfcSpatialZone: CONSTRUCTION SAFETY LIGHTING OCCUPATION THERMAL SAFETY TRANSPORT VENTILATION NOT SPECIFIED USER-DEFINED

IfcStackTerminal: RAINWATERHOPPER HOOD CAGE NOT SPECIFIED USER-DEFINED

IfcStairFlight: CURVED ANY FORM SPIRAL STRAIGHT WINDER NOT SPECIFIED USER-DEFINED

IfcStair: CURVED_RUN_STAIR DOUBLE_RETURN_STAIR POŁOWA_TURN_STAIR POŁOWA_WINDING_STAIR QUARTER_TURN_STAIR QUARTER_WINDING_STAIR SPIRAL_STAIR STRAIGHT_RUN_STAIR THREE_QUARTER_TURN_STAIR THREE_QUARTER_WINDING_STAIR TWO_CURVED_RUN_STAIR TWO_QUARTER_TURN_STAIR TWO_QUARTER_WINDING_STAIR TWO_STRAIGHT_RUN_STAIR NOT SPECIFIED USER DEFINED

IfcSwitchingDevice: CONTACT DIMMER SWITCH EMERGENCY STOP KEYBOARD SWITCH TORQUE SWITCH SELECTION SWITCH STARTER SWITCHDISCONNECTOR SWITCH NOT SPECIFIED USER-DEFINED

IfcSystemFurnitureElement: PLATE WORKSHOP NOT SPECIFIED USER-DEFINED

IfcTank: SWIMMING POOL PRESSURE EXPANSION FEEDANDEXPANSION PRESSURE TANK STORAGE POT NOT SPECIFIED USER-DEFINED

IfcTendonAnchor: HUB FIXED_END TENSIONING_END NOT SPECIFIED USER-DEFINED

IfcTendon: BAR COATED BAND WIRE NOT SPECIFIED USER-DEFINED

IfcTransformer: CURRENT FREQUENCY INVERTER VOLTAGE NOT SPECIFIED USER-DEFINED

IfcTransportElement: CRANE LIFT MOVING STAIRS LIFT MOVINGWALKWAY NOT SPECIFIED USER DEFINED

IfcTubeBundle: RIBBON NOT SPECIFIED USER-DEFINED

IfcUnitaryControlElement: ALARMPANEL CONTROL PANEL GASDETECTION PANEL HUMIDISTAT INDICATOR PANEL MIMICPANEL THERMOSTAT WEATHER STATION NOT SPECIFIED USER-DEFINED

IfcUnitaryEquipment: AIR CONDITIONING AIRHANDLER AIR DRYER ROOFTOPUNIT SPLITSYSTEM NOT SPECIFIED USER-DEFINED

IfcValve: AIR RELEASE ANTI-VEHICLE CHANGEOVER CHANGE UMOVEMENT DIVERTING DOUBLE CHECK DOUBLEREGULATING DRAWOFFCOCK TAP RINSING GASCOCK GASTAP INSULATION MIXING PRESSURE RELEASE PRESSURE EXTENSION ADJUSTMENT SAFETY STEAMTRAP CLOSED CONFIGURED TAPE

IfcVibrationIsolator: SPRING COMPRESSION NOT SPECIFIED USER-DEFINED

IfcWall: MOVING SILL PARTITIONING PLUMBINGWALL POLYGONAL SHEAR SOLIDWALL NOT SPECIFIED USER-DEFINED

IfcWasteTerminal: FLOORWASTE TRAP GULLYSUMP GULLYTRAP ROOF LEAKAGE WASTEDISPOSALUNIT WASTETRAP NOT SPECIFIED USER-DEFINED

IfcWindow: LIGHT SIDE SKYLIGHT WINDOW NOT SPECIFIED USER-DEFINED

First publication 2018 v1.0: Publisher of Construction Information Systems Limited, Sydney, Australia (ABN 20 117 574 606) and Construction Information Ltd, Auckland, New Zealand. We welcome comments or suggestions for improvements to the Open BIM Object Standard and encourage readers to notify us immediately of any apparent inaccuracies or ambiguities. Contact us by email at bim @ natspec .com .au or bim @ masterspec .co .nz. Copyright: Its document is copyright © 2018. You may use this document for your own purposes. You can distribute this Document to other people, as long as you assign the Document as generated by NATSPEC and Masterspec and that the document is available free of charge.

"OBOS is a free BIM object creation resource for use by all construction professionals - from designers and specifiers to BIM producers and content creators. NATSPEC collaborated with Masterspec (New Zealand) to develop an object-oriented BIM standard. The result is an open object-oriented BIM standard. (OBOS) designed for use by all construction professionals - from designers and specifiers to manufacturers and BIM content creators, to help create standardized generic, BIM, and project-specific BIM objects. Having standardized BIM creation in Australia, New Zealand and other countries It will ensure object authors and, importantly, product manufacturers that their BIM objects will be accepted by the end users of objects, enabling them to manage their BIM content in a consistent and orderly manner.Standard content means authors and manufacturers do not risk wasting time, money, and resources to create content BIM that may not be accepted by the industry. In order to harmonize BIM practices internationally, a comprehensive review of existing global guides, standards and protocols related to BIM content creation in research and preparation was completed. OBOS complements and interacts with the recently released NATSPEC BIM Property Generator - both are mutually supportive tools. The first one specifies the rules for applying properties to objects, specifies their format and the requirements for graphic modeling and BIM object functionality. The latter is a compendium of properties - conforming to the standard - for typical architectural and construction objects. "Bim.natspec.org

Document available free of charge at: Source: https://bim.natspec.org/documents/open-bim-object-standard