Sustainability - High Performance Buildings - Knowledge-based Building Information Modeling Systems - BIM - 3D 4D 5D BIM

BIM and Collaborative Construction Delivery Methods Legislation Proposed

pcholakis — Mon, 23 Jan 2012 21:42:51 +0000

It appears that Capitol Hill is beginning to recognize the linkage between BIM and efficient project delivery methods such as IPD (Integrated Project Delivery) and JOC (Job Order Contracting), the latter a version of IPD targeting facility renovation, repair, and sustainability construction projects.

H.R.3371, introduced by Russ Carnahan (D-M0.) call for the GAO to study BIM and integrated project delivery methods relative to use for Federal Buildings.

Specifically the bill calls for constraints relative BIM and IPD adoption and usage, potential impacts of expanded usage in association with procurement and budgeting, information requirements for life-cycle BIM usage, and the creation of an associated directorship.

BIM-CLOUD Convergence

via www.4Clicks.com – premier software for efficient project delivery, JOC, SABER, IPD, SATOC, MATOC, MACC, POCA, IDIQ, BOA.

BIM and Cloud Computing – Get Beyond 3D Visualization and Focus Upon the “I”

pcholakis — Tue, 17 Jan 2012 20:08:46 +0000

BIM and the Cloud – SAME 2012 – 4Clicks Solutions LLC – PDF

BIM - CLOUD COMPUTING

BIM (Building Information Technology) and THE CLOUD (Cloud Computing) are disruptive technologies converging to significantly alter traditional construction and facility management practices.

Both technologies also embed associated business process rules and components which will enable enhanced life-cycle management of the built environment, alignment of structures with organizational mission, and better consideration of general community impacts.

The ever increasing competitive financial and environmental landscape are requiring public and private institutions to further maximize facility planning and management.

Leading organizations are already investing in the formalized definition and creation of robust business process frameworks, cultures, workflows, and capabilities to support collaboration, continuous improvement and/or LEAN practices needed to achieve higher productivity within the Architecture, Engineering, Construction, Owner and Operator (AECOO) sector.

BIM and THE CLOUD provide the digital backbone to support the cost effective, scalable development and deployment of adaptive and efficient facility life-cycle management practices.

Definition of BIM

Building Information Management (BIM) is the life-cycle management of facilities[1] supported by digital technology.

BIM can be applied at various levels. Current the most common being use of proprietary 3D visualization software for the purpose of supporting the design and construction phases of the facility life-cycle. At this level BIM’s value is primarily to Architects, Architectural Engineers and Business Development Professionals, as well as Owners working to design, market, and construct new facilities. Case studies have documented the cost and time savings offered at this level of BIM application, however, BIM’s ability to support the fully facility life-cycle – planning, design, procurement, construction, operations, repair, renovation, sustainability, adaptation, and

deconstruction – is where the highest value of BIM will be achieved. Attainment of this advanced life-cycle implementation of BIM on a widespread basis however the will require the following to occur:

1. Major cultural change within the AECOO sector,

2. Standardized taxonomies and data architectures, and

3. The availability and integration of secure technology to promote collaboration and

the Integration of currently disparate business processes and knowledge domain specific software applications such as; Capital Planning and Management Systems (CPMS), Computer-Aided Facility Management (CAFM), Cost Estimating and Project Management, Efficient Construction Delivery Methods (IPD-Integrated Project Delivery, JOC-Job Order Contraction), Computerized Maintenance Management Systems (CMMS), Geographic Information Systems (GIS), and Building Automation Systems (BAS). A view of how these components pertain to an overall BIM strategy and facility life-cycle is represented in Figure #1.

BIM holds many of the keys to restructuring and dramatically improving overall performance and productivity within our industry, however, cloud computing is equally important.

Definition of THE CLOUD

Cloud computing and/or cloud technology (THE CLOUD) is “a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.”[2]

THE CLOUD allows users to access parts of virtually limitless application and computing resources on-demand. Access is faster and easier than traditional “client-server” or “web-based” applications. While some software vendors may host their legacy applications on the cloud, and call them “cloud apps”, a practice known as “cloud-washing”, true cloud applications offer all of the following elements:

• On-demand self-service: a user to can sign up and receive services without delay.

• Broad network access: ability to access the service via multiple platforms; desktop,

laptop, mobile/handheld.

• Rapid elasticity/scalability: computing resources are available to meet requisite

demand.

• Measured Service: Metered and/or time based billing based upon computing resource

levels and/or storage levels vs. time.

There are several levels of cloud computing, which may appear distinct and tend to blend and even become transparent based upon the type of usage:

- Software as a Service (Saas): SaaS is the “end-user” level of cloud computing. Access to software application, such as Microsoft Excel for example, is provided on an on-demand basis via a web browser. Applications are available via the Internet on a “right to use” and “pay-as-you-go” subscription model. There is no additional annual fee for software maintenance, or any need to worry about upgrades or patches, etc. Users simply pay a monthly or annual fee for access and use based upon time and/or usage.

- Platform as a Service (PaaS): PaaS is the set of tools and services designed to make coding and deploying SaaS applications efficient. While transparent to most end-users, it is the power to create and deploy applications exponentially faster within a standardized, secure environment that is driving the adoption of THE CLOUD.

- Infrastructure as a Service (IaaS): IaaS represents all the associated hardware and software infrastructure – servers, storage, networks, and operating systems.

BIM and CLOUD Convergence

To better understand the explosive power of mixing BIM and CLOUD relative to removal of the traditional process and technology silos within the AECOO sector that have held back productivity improvement for decades, it’s important to look at cloud computing in a bit more detail.

SaaS is tailor made for applications where there is significant interplay between the user organization and the outside world. Applications that have a significant need for web or mobile access. Software where usage may be intermittent, and or demand spike occurs frequents.

All of these are common within all phases of construction, repair, renovation, or sustainability projects.

PaaS, platform as a service, also offers several key capabilities. Tools and services to test, deploy, host, and maintain applications are provided within one integrated development environment. Brower and/or web graphical user interface (GUIs) creation tools are also a part of PaaS platforms to speed the ability to create, modify, test and deploy client-specific applications.

All of the above is accomplished within a “multi-tenant architecture” within which concurrent developers work within the application.

This translates into the ability to build and deploy massively scalable, secure applications at a fraction of the time it would have taken for traditional software deployments.

Additionally, this is all accomplished within a set of common standards, assuring the ability to “talk” to virtually any other application. Multiple developers can be working on a development project and/or other external parties can easily become part of development process. This ability is critical where multiple professionals have existing data sources – cost data bases, project information, contract information, etc. and need to enhance the ability to pull and maintain knowledge from these sources. A notable example of a PaaS platform is Microsoft Azure^TM.

From a facility life-cycle perspective, imagine the following within a BIM environment.

Again, please keep in mind that BIM is not “just” 3D model-centric visualization or rendering of building information, but rather collaborative access and ongoing use of a wide range of building information throughout its life-cycle: cost data, physical or functional conditions, utilization, life/safety, sustainability, etc.

Cloud computing allows facility stakeholders throughout the world to work concurrently upon the same data. For example, let’s us take the creation of cost estimate for a major facility renovation. The renovation is located in a foreign country, however, part of a large real property portfolio owned and managed by an Owner based in the United States.

Anyone that is proposed to participate or participates in the project and simple by invited by the Owner, and or the Owner’s representative. The invite is sent directly from the SaaS cost estimating and project estimating program, and/or adaptive construction project delivery / adaptive construction management system (ACM^TM, APD^TM,). The invites can be sent in any language automatically. Invites allow access to information to a specified level of granularity and/or to a domain Once invited, and upon acceptance and confirmation, the invitee will see only the subset of information enabled by the “host”. Perhaps the Owner is providing full access to a general contractor, or the general contractor may be providing limited access to a sub-contractor. Invited parted may be allowed to conduct work on the information, such as prepare a construction cost estimate, and/or work jointly upon an existing cost estimate.

Regardless, changes can be made at any time, and at any level, as defined by the account administrator. Each change can be done in locate language, currency, etc. Each change is automatically recorded and tracked right down to time and user, with full “undo” and “redo” capability. This is real-time collaboration and transparency. This is BIM.

The above only begins to relate the enablement provided by the BIM/CLOUD convergence.

All aspects of a BIM strategy or BIM framework, as portrayed in the Figure #1, can be cost effectively implemented and supported by a digital BIM/CLOUD framework.

As the technology solution provided by cloud computing enters the AECOO sector, standardized life-cycle process definitions and associated exchanges of information take front stage to insure that various domain-specific meanings are consistent and apparent at all levels of granularity.

Robust, proven business process, such as efficient project delivery methods such as IPD-Integrated Project Delivery and JOC-Job Order Contract[3] will be easily and cost-effectively implemented and consistently deployed throughout organizations regardless of type or location.

Owners, AEs. Contractors, and Subcontractors will be empowered to access and use these and other methods to significantly improve collaboration and productivity. Furthermore, changes can readily be made to both processes and technology to adapt to specific localized requirements and/or to keep paces with dynamic conditions.

That fact that business process and workflows of these efficient project delivery methods, and all other components of a BIM Framework, are embedded into the cloud technology is central to the empowerment and success of all built environment stakeholders. Using traditional technology and methods, these capabilities would be limited to organizations that could afford the associated “front end” implementation and ongoing technology and process management costs. And even then, success would not be assured as collaborative and “real-time” monitoring, as well as adaptive response are not readily available.

Conclusion

Cloud computing technology enables the rapid development, deployment, and ongoing adaptation of proven, robust BIM processes. It is the consistent, collaborative creation and ongoing use of facility life-cycle information for both new and existing buildings, spanning design, procurement, construction, renovation, repair, adaptation, and deconstruction that defines BIM. Cloud technology is the framework upon which BIM processes will be created, deployed and maintained.

BIM and Cloud Computing together will significantly expand the ability of all stakeholders to more efficiently better the built environment on a widespread basis.

Once sequestered in silos – Owners, Real Property Managers, Facility Managers, Architects, Engineers, Contractors, Sub-contractors, Operations and Maintenance, Financiers, Safety and Security, Business Product Manufacturers, and Oversight Groups – will now have the ability to base their decisions upon transparent, common information.

[1] The terms “facility” or “facilities” are used to define vertical (buildings) and horizontal (bridges, roadways, utilities…) built structures.

[2] National Institute of Standards and Technology (NIST)

[3] Job Order Contracting (JOC) is an form of Integrated Project Delivery for facility renovation, repair, and sustainability construction projects. Both IPD and JOC are decades old and proven to be effective at improving productivity and mitigating both change orders and litigation.

COBIE and BAMie Specifications Released

pcholakis — Tue, 10 Jan 2012 14:51:22 +0000

Formal release of two Industry Foundation Class Model View Definitions for consideration by the international AECOO community. Below is an introduction, source is E. William (Bill) East, PhD, PE. F.ASCE, Research Civil Engineer, Engineer Research and Development Center, 2902 Newmark Drive, Champaign, IL 61826..

FM Handover 2011

——————————————————————————–

Facilities Management Handover for data sharing in the construction and facility management industries

Scope

ISO 16739 specifies a conceptual data schema and an exchange file format for Building Information Modeling BIM data. The conceptual schema is defined in EXPRESS data specification language (EXPRESS) as specified in ISO 10303-11.

ISO 16739 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.

ISO 16739 consists of the data schema, represented as an EXPRESS schema specification, and reference data, represented as definitions of properties and quantities.

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.

The document represents a model view definition for facilities management.

The following are within the scope of this MVD:
■Building Information Model exchange format definitions that are required during the life cycle phases of buildings:

◦coordinated design;
◦procurement and full financial authority;
◦production information;
◦construction;
◦operation and maintenance.

■Building Information Model exchange format definitions that are required by the various disciplines involved within the life cycle phases: ◦procurement;
◦construction planning;
◦facility management;
◦project management;
◦client requirement management;
◦building authority for permits and approval.

■Building Information Model exchange format definitions including: ◦project structure;
◦physical components;
◦spatial components;
◦processes;
◦resources;
◦controls;
◦actors;
◦context definition.

The following are outside the scope of this MVD:
■exchange format definitions outside of the domain of construction and facility maintenance;
■project structure and component breakdown structures outside of building engineering;
■behavioral aspects of components and other information items.

Introduction

The Facilities Management Handover Model View contains information information describing the operations, maintenance, and assets in capital facilities.

The authoritative sources for this information include designers, builders, installers, and manufacturers. On the design side of the exchange, BIM-based design tools may be used to capture such data. From construction, information about approved submittals are included in data exchanges. Builders identify products to be installed. Manufacturers provide operating and maintenance information. Installers provide serial and tag numbers. Quality Control/Assurance staff provide test and certification reports. All these parties can capture building handover data through this standard, tying their diverse set of software together for the purpose of providing a consistent data set of operations, maintenance, and asset management to building staff.

Normative references

The following referenced documents are indispensable for the application of this document. For dated references, only the 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 integration — Product data representation and exchange — Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas
ISO 16739, Industry Foundation Classes (IFC) for data sharing in the construction and facilities management industries
ISO 29500, Information technology — Document description and processing languages — Office Open XML File Formats

Terms, definitions and abbreviated terms

Terms and definitions

For the purpose of this document, the following definitions apply.

attribute

A unit of information within an entity, defined by a particular type or reference to a particular entity. There are three kinds of attributes: direct attributes, inverse attributes and derived attributes.

direct attribute

Scalar values or collections including Set (unordered, unique), List (ordered), or Array (ordered, sparse) as defined in ISO 10303-11.

Note Similar to the term “field” in common programming languages.

inverse attribute

A unit of information defining queries for obtaining related data and enforcing referential integrity.

Note Similar to the term “navigation property” in entity-relational programming frameworks.

derived attribute

A unit of information computed from other attributes using an expression defined in the schema.

constraints on attributes

Data type restricting the values of attributes.

Note The most general constraint is about the existence of attribute values. There are basically two types: mandatory and optional attributes. Values of mandatory attributes must be provided whereas values of optional attributes may be omitted.
Note For aggregation data types such as Set, List, or Array, the existence constraint is often refined by a minimal and maximal number of elements, which is also known as cardinality.

entity

A class of information defined by common attributes and constraints as defined in ISO 10303-11.

Note Similar to the term “class” in common programming languages but describing data structure only (not behavior such as methods).

identification

Capability to find, retrieve, report, change, or delete specific instances without ambiguity.

instance

Occurrence of an entity.

Note Similar to the term “instance of a class” in object oriented programming.

object

Anything perceivable or conceivable that has a distinct existence, albeit not material.

type

A basic information construct derived from a primitive, an enumeration, or a select of entities.

Note Similar to the “Type” construct as defined in ISO 10303-11.
Note Similar in concept to “typedef” or “value type” in common programming languages.

select

A construct that allows an attribute value to be one of multiple types or entities.

Note Similar to the “Select” construct as defined in ISO 10303-11.
Note Similar to a “marker interface” in common programming languages.

enumeration

A construct that allows an attribute value to be one of multiple predefined values identified by name.

Note Similar to the “Enumeration” construct as defined in ISO 10303-11.
Note Similar in concept to “enum” in common programming languages.

actor

A person, an organization, or person acting on behalf of an organization.

Note A specialization of the general term object.

classification

A categorization, the act of distributing things into classes or categories of the same type.

constraint

A restriction for a specified reason.

Note A specialization of the general term control.

control

A directive to meet specified requirements such as for scope, time, and/or cost.

Note A specialization of the general term object.

dictionary

A 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

An element’s position within the project coordinate system and its containment within the spatial structure.

external reference

A link to information outside the IFC file, with direct relevance to the specific information the link originates from inside the IFC file.

feature

Parametric information and additional property information modifiying the shape representation of an

element to which it applies.

group

A collection of information that fulfills a specified purpose.

Note A specialization of the general term object.

library

A catalogue, database or holder of data, that is relevant to information in IFC files, but not meant to live in IFC files themselves, just referenced.

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-occurrences.

Note Similar to “class”, “template”, “type” in other publications.

process

object-occurrence located in time, indicating “when”.

process occurrence

A conceptual object that may occur at a particular time.

process type

Common characteristics shared by multiple process occurrences.

product

A is physical or conceptual object that occurs in space.

Note a specialization of the general term object.

product occurrence

A physical or conceptual object that may have a location in space and shape characteristics.

product type

Common characteristics shared by multiple product occurrences.

project

Encapsulation of related information for a particular purpose providing context for information contained within such as default measurement units.

property

A 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

A unit of information providing a value for a property identified by name.

property template

Metadata for a property including name, description, and data type.

Note Similar in concept to “extension property” in common programming languages.

property set occurrence

A unit of information containing a set of property occurrences, each having a unique name within the property set.

property set template

A set of property templates serving a common purpose and having applicability to objects of a particular entity.

Note Similar in concept to “extension class” in common programming languages.

proxy

An object that does not hold a specific object type information.

Note a specialization of object occurrence.

quantity

A measurement of a scope-based metric, specifically length, area, volume, weight, count, or time.

quantity occurrence

A unit of information providing a value for a quantity.

quantity set

A unit of information containing a set of quantity occurrences, each having a unique name within the quantity set.

relationship

A unit of information describing an interaction between items.

representation

A unit of information describing how an object is displayed, such as physical shape or topology.

resource

An entity with limited availability such as materials, labor, or equipment.

Note a specialization of the general term object.
Note the “resource definition data schemas” section is unrelated to this concept.

resource occurrence

An entity with inherent financial cost, which may be passed onto processes, products, and controls to which it is assigned.

resource type

Common characteristics shared by multiple resource occurrences.

space

A volume bounded by the top of a slab below, the bottom of slab(s) above, and by the surrounding walls, excluding coverings.

Note a specialization of the general term product.

room

A volume bounded by the top of a slab and floor covering below, the bottom of ceiling covering(s) above, and by the coverings of the surrounding walls.

Abbreviated terms

For the purpose of this document, the following abbreviated terms apply:

GUID	Globally Unique Identifier
IFC	Industry Foundation Classes
IFD	International Framework for Dictionaries
SPF	STEP Physical File
STEP	STandard for the Exchange of Product data
URI	Uniform Resource Identifier

Exchange requirements

Various exchange scenarios are identified spanning the lifecycle of information exchange for facilities management. Such scenarios are partitioned by user role and project stage.

The diagram below shows each exchange scenario in order of process sequence proceeding left-to-right over time, and in order of control sequence proceeding top-to-bottom over authorizing role, where higher roles generally commission and/or regulate lower roles. Communication is indicated by arrows, where the start point (circle) indicates the origination of information and the end point (triangle) indicates the destination of information. Arrows connected in sequence indicate intermediate passing of information for approval and forwarding.

NOTE Roles and exchanges are provided for illustration, and may be adapted according to requirements and contract conditions for specific projects.

PROCESS

All data is based on the schema defined by ISO 16739 (Industry Foundation Classes, Version 4). Data may be encoded in any of the following formats, including:

IFC-SPF: The ISO-10303-21 text format lists each data instance on a line, having an instance number, the type name, and direct attributes in order.
IFC-XML: The ISO-10303-28 text format lists data instances within hierarchical tags using the type name, with direct and inverse attributes contained in tags.
OOXML: The Open Office XML format organizes data into a spreadsheet, where data may be stored using pages for object types, columns for attributes, and rows for instances.

All data is based on the schema defined by ISO 16739 (Industry Foundation Classes, Version 4). Data may be encoded in any of the following formats, including:

IFC-SPF: The ISO-10303-21 text format lists each data instance on a line, having an instance number, the type name, and direct attributes in order.
IFC-XML: The ISO-10303-28 text format lists data instances within hierarchical tags using the type name, with direct and inverse attributes contained in tags.
OOXML: The Open Office XML format organizes data into a spreadsheet, where data may be stored using pages for object types, columns for attributes, and rows for instances.

Start

Project Definition

This exchange includes initial project information to describe a project and its contents.

Entities exported for this exchange include the following:

IfcProject: Directory and context of data is provided.
IfcActor: Project participants, roles, and contact information is provided.
IfcSite: Site (General) information must be provided to identify the site upon which the the facility is placed.
IfcBuilding: Facility (General) information must be provided to identify the facilities in which floors and spaces may be found.

Requirements

Space Program

This exchange includes requirements for the spatial layout of a building.

Entities exported for this exchange include the following:

IfcBuildingStorey: Provide the name of each conceptual/physical vertical level of each of the facilities identified in the project wrapper, elevation value and units above local project datum, floor to floor height and units.
IfcSpace: Provide the name and floor for each space.
IfcSpatialZone: Identify conceptual zones within the building that have a similar or grouped pattern of use. For example, zones my refer to mechanical heating zones, alarm systems zones, or groups of spaces to be used for specific clients.
IfcRelAssociatesClassification: Classifications may be applied to categorize spaces by function.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Product Program

This exchange includes requirements for physical components of a building.

Entities exported for this exchange include the following:

IfcElement: Identify general requirements of products to be used within the building.
IfcRelAssociatesClassification: Classifications may be applied to categorize products by function.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Design

Design Early

This exchange includes building layout information and allocation of products without regard for placement.

Entities exported for this exchange include the following:

IfcBuildingStorey: Provide the name of each conceptual/physical vertical level of each of the facilities identified in the project wrapper, elevation value and units above local project datum, floor to Floor height and units.
IfcSpace: Provide the name and floor for each space.
IfcElement: Identify general requirements of elements within the building.
IfcElementType: Identify specific product model types to be considered for use.
IfcSystem: System name for each system must be identified before it can be associated with specific products and zones.
IfcRelAssociatesClassification: Classifications may be applied to categorize spaces by function.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Design Schematic

This exchange includes building layout information and allocation of products with placement and connectivity.

Entities exported for this exchange include the following:

IfcSpace: Provide the name and floor for each space.
IfcElement: Identify general requirements of elements within the building.
IfcElementType: Identify specific product model types to be considered for use.
IfcSystem: System name for each system must be identified before it can be associated with specific products and zones.
IfcRelConnectsElements: Indicate mounting connections between elements.
IfcRelConnectsPorts: Indicate port connections between elements.
IfcRelAssociatesClassification: Classifications may be applied to categorize products by function.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Design Coordinated

This exchange includes building layout information and allocation of products with placement, connectivity, and assignment to systems and project participants.

In IFC4, zones may be indicated spatially with functional designation, material constituents are supported to identify multiple materials and properties.

Entities exported for this exchange include the following:

IfcSpace: Provide the name and floor for each space.
IfcElement: Identify general requirements of elements within the building.
IfcElementType: Identify specific product model types to be considered for use.
IfcSystem: Design building systems, structural systems, and distribution systems.
IfcSpatialZone: Design zones for distribution systems.
IfcRelConnectsElements: Indicate mounting connections between elements.
IfcRelConnectsPorts: Indicate port connections between elements.
IfcRelAssociatesMaterial: Indicate materials, layers, and profiles of elements.
IfcRelAssignsToActor: Indicate project participants responsible for systems and elements.
IfcRelAssignsToGroup: Indicate partioning of building elements to systems.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.
IfcRelAssociatesClassification: Classifications may be applied to categorize products and systems by function.
IfcElementQuantity: Quantities may be indicates on building elements and spatial structures.

Design Issue

This exchange includes final design information with formal documents, and amended with design issue requests and responses.

Entities exported for this exchange include the following:

IfcActionRequest: Indicate reported issues and resolutions.
IfcRelAssociatesDocument: Indicate external documents.

Product Type Template

This exchange includes definitions of properties to be captured by product templates.

Property templates are now supported in IFC4. Project composition excluded (no placeholder building is necessary).

Entities exported for this exchange include the following:

IfcRelAssociatesClassification: Classifications may be applied to categorize properties by common definitions.
IfcPropertySetTemplate: Property set templates may be specified to indicate information to be provided for product types.
IfcSimplePropertyTemplate: Property templates may be specified to describe each property within a property set.

Product Template

This exchange includes product type information for specific product models provided by manufacturers.

Product types may be declared within a project without having any occurrences in IFC4. Project composition excluded (no placeholder building is necessary). Project libraries added (to provide link to originating property set templates).

Entities exported for this exchange include the following:

IfcProjectLibrary: Referenced libraries of property set templates are indicated.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.
IfcElementType: Identify specific product model types to be considered for use.
IfcRelAssociatesClassification: Classifications may be applied to categorize product types.
IfcRelAssociatesMaterial: Identify material constituents and material properties.

Construction

Bid Issue

This exchange includes bid submission information with formal documents, and amended with bid issue requests and responses.

The IfcActionRequest entity captures all reported issues (or requests to do something), for which tasks may be assigned to carry out work to address an issue.

Entities exported for this exchange include the following:

IfcActionRequest: Indicate reported issues and resolutions.
IfcRelAssociatesDocument: Indicate external documents.

Product Type Selection

This exchange includes product type information for product models selected to be used, without regard for particular placement.

Product types may be declared within a project without having any occurrences in IFC4. Project composition excluded (no placeholder building is necessary). Project libraries added (to provide link to originating property set templates).

Entities exported for this exchange include the following:

IfcProjectLibrary: Referenced libraries of product types are indicated.
IfcElementType: Identify specific product model types to be considered for use.
IfcRelDefinesByType: Indicate product types to be used at specific occurrences.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

System Layout

This exchange includes detailed system connectivity information for building systems and distribution systems.

Entities exported for this exchange include the following:

IfcElement: Indicate specific element placement within the building.
IfcSystem: Indicate system design and topology.
IfcRelConnectsElements: Indicate general connections between elements.
IfcRelConnectsPorts: Indicate port connections between elements.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Product Installation

This exchange includes product placement information, including serial numbers at specific installations.

Entities exported for this exchange include the following:

IfcElement: Identify general requirements of elements within the building.
IfcPropertySet: Properties may be specified to indicate requirements at particular objects.

Product Inspection

This exchange includes product inspection issues reported, which may require replacement of installed products.

Entities exported for this exchange include the following:

IfcActionRequest: Report issues related to products.

Construction Issue

This exchange includes construction issues reported, which may require additional labor.

Entities exported for this exchange include the following:

IfcActionRequest: Report issues related to construction.

Product Type Parts

This exchange includes product part information, which may be used for addressing components for connectivity or replacement.

IFC4 allows product types to have assigned process types and resource types, which may indicate standard processes (i.e. manufacturer-defined) for servicing or replacing parts.

Entities exported for this exchange include the following:

IfcTaskType: Indicate product part replacement processes.
IfcConstructionProductResourceType: Indicate available resources and costs for part replacement.

Product Type Warranty

This exchange includes product warranty information for parts and labor.

Entities exported for this exchange include the following:

IfcTaskType: Indicate warranty periods.
IfcSubContractResourceType: Indicate warranty contracts.
IfcRelAssociatesDocument: Indicate external documents for warranties.

Product Type Maintenance

This exchange includes product maintenance information, including expected maintenance tasks and procedures.

Entities exported for this exchange include the following:

IfcTask: Schedule product maintanence processes.
IfcConstructionResource: Schedule product maintenance resources.
IfcRelAssociatesDocument: Indicate external documents for maintenance.

System Operation

This exchange includes system operation information, including system operation procedures and events.

Entities exported for this exchange include the following:

IfcTask: Schedule system operation processes.
IfcConstructionResource: Schedule system operation resources.

Operations & Maintenance

Space Condition

This exchange includes reporting on the condition of spaces over time.

In IFC4, all time-phased information is captured using performance-based properties on IfcPerformanceHistory. This allows for data to be recorded for multiple time periods (avoiding the single property set restriction), and to provide a uniform way of accessing and rendering time-phased data such that software applications need not be aware of particular properites. A property set should be defined for recording space conditions over time.

Entities exported for this exchange include the following:

IfcPropertySet: Properties may be specified to indicate condition details.

Product Parts Replacement

This exchange includes reporting on the replacement of product parts over time.

In IFC4, the process and resource model has been formalized, such that replacement of parts may be considered as a MAINTENANCE task with assigned resources for materials, labor, equipment, products, crews, subcontracts.

Entities exported for this exchange include the following:

IfcTask: Report parts replacement over time.
IfcConstructionResource: Report parts replacement resources.
IfcPropertySet: Properties may be specified to indicate details.

Space Occupancy

This exchange includes scheduling occupancy of spaces over time.

IfcOccupant: Indicate occupants.
IfcTask: Indicate scheduled occupancy periods.
IfcSubContractResource: Indicate leases for space occupancy.
IfcRelAssignsToActor: Indicate current owner(s) and/or occupant(s) of a space.
IfcRelAssignsToProduct: Indicate occupancy periods of spaces.
IfcRelAssignsToProcess: Indicate resources assigned to space occupancy periods.
IfcPropertySet: Properties may be specified to indicate details.

Space Activity Renovation

This exchange includes scheduling reconfiguration of spaces over time.

Entities exported for this exchange include the following:

IfcTask: Indicate renovation tasks.
IfcConstructionResource: Indicate renovation resources.
IfcRelAssignsToProduct: Indicate elements to be renovated.
IfcRelAssignsToProcess: Indicate resources assigned to tasks.
IfcPropertySet: Properties may be specified to indicate details.

Recycle

Remodel

This exchange includes changing the building layout of an existing structure.

Entities exported for this exchange include the following:

IfcTask: Indicate renovation tasks.
IfcConstructionResource: Indicate renovation resources.
IfcRelAssignsToProduct: Indicate elements to be renovated.
IfcRelAssignsToProcess: Indicate resources assigned to tasks.
IfcPropertySet: Properties may be specified to indicate details.

Expand

This exchange includes expanding the building layout of an existing structure.

Entities exported for this exchange include the following:

IfcTask: Indicate renovation tasks.
IfcConstructionResource: Indicate renovation resources.
IfcRelAssignsToProduct: Indicate elements to be renovated.
IfcRelAssignsToProcess: Indicate resources assigned to tasks.
IfcPropertySet: Properties may be specified to indicate details.

Demolish

This exchange includes demolishing an existing structure partially or in full.

Entities exported for this exchange include the following:

IfcTask: Indicate renovation tasks.
IfcConstructionResource: Indicate renovation resources.
IfcRelAssignsToProduct: Indicate elements to be renovated.
IfcRelAssignsToProcess: Indicate resources assigned to tasks.
IfcPropertySet: Properties may be specified to indicate details

Core data schemas

Figure 1 — Core data schema map

The core data schemas establish the most general layer within the IFC schema architecture as shown in Figure 1. Entities defined in this layer can be referenced and specialized by all entities in the shared element layer and the domain specific layer. 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 layer and above derive from IfcRoot, having unique identification, name, description, and change control information.

5.1 IfcKernel
5.2 IfcProcessExtension
5.3 IfcProductExtension

Shared Element Data Schemas

Figure 21 — Shared element data schema map

The shared element data schemas contain intermediate specializations of entities as shown in Figure 21. Entities defined in this layer can be referenced and specialized by all entities in the domain specific layer. The shared element layer provides more specialized objects and relationships shared by multiple domains.

6.1 IfcSharedFacilitiesElements
6.2 IfcSharedMgmtElements

Domain Specific Data Schemas

Figure 26 — Domain specific data schema map

The domain specific data schemas contain final specializations of entities as shown in Figure 26. 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 IfcConstructionMgmtDomain

Resource Definition Data Schemas

Figure 40 — Resource definition data schema map

The resource definition data schemas consist of supporting data structures as shown in Figure 40. Entities and types defined in this layer can be referenced by all entities in the core layer, shared element layer, and the domain specific layer.

Unlike entities in other layers, resource definition data structures cannot exist independently, but can only exist if referenced (directly or indirectly) by one or more entities deriving from IfcRoot. As resource definitions do not have a concept of identity (such as a GUID), multiple objects referencing 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.

The resource definition layer should not be confused with construction resource entities (IfcResource subtypes). While the terms are similar, they are unrelated concepts.

8.1 IfcActorResource
8.2 IfcCostResource
8.3 IfcDateTimeResource
8.4 IfcExternalReferenceResource
8.5 IfcMaterialResource
8.6 IfcMeasureResource
8.7 IfcPropertyResource
8.8 IfcQuantityResource
8.9 IfcRepresentationResource
8.10 IfcUtilityResource

Annex A

(normative)

Computer interpretable listings

This annex contains a listing of the complete MVD-XML view definition of the schema combining definitions of clauses 5, 6, 7, and 8 without comments or other explanatory text. These listings are available in computer-interpretable form that may be parsed by computer.

The following permission notice and disclaimer shall be included in all copies of these files (“the Schema”), and derivations of the Schema:

Permission is hereby granted, free of charge in perpetuity, to any person obtaining a copy of the Schema, to use, copy, modify, merge and distribute free of charge, copies of the Schema for the purposes of developing, implementing, installing and using software based on the Schema, and to permit persons to whom the Schema is furnished to do so, subject to the following conditions:

THE SCHEMA IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SCHEMA OR THE USE OR OTHER DEALINGS IN THE SCHEMA.

Table A.1 — File listings

Description	File
COBie MVD-XML listing describing model view scope and documentation.	COBie.mvdxml
COBie IFC-SPF listing describing property set templates.	COBie.ifc

Annex B

(informative)

EXPRESS-G diagrams

B.1 General

This annex provides graphical diagrams of definitions in accordance with the graphical representation of EXPRESS as specified in annex D of ISO 10303-11. The figures correspond to the EXPRESS definitions in clauses 5, 6, 7, and 8.

B.2 Core data schemas

B.2.1 IfcKernel

B.2.2 IfcProcessExtension

B.2.3 IfcProductExtension

B.3 Shared element data schemas

B.3.1 IfcSharedFacilitiesElements

B.3.2 IfcSharedMgmtElements

B.4 Domain schemas

B.4.1 IfcConstructionMgmtDomain

B.5 Resource definition data schemas

B.5.1 IfcActorResource

B.5.2 IfcCostResource

B.5.3 IfcDateTimeResource

B.5.4 IfcExternalReferenceResource

B.5.5 IfcMaterialResource

B.5.6 IfcMeasureResource

B.5.7 IfcPropertyResource

B.5.8 IfcQuantityResource

B.5.9 IfcRepresentationResource

B.5.10 IfcUtilityResource

Annex C

(informative)

Exchange rules

IfcActionRequest

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SheetName1′ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.HasAssignments[*].RelatingObject\’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘RowName1′ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.HasAssignments[*].RelatingObject’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SheetName2′ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.Controls[*].RelatedObjects[*]\’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘RowName2′ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.Controls[*].RelatedObjects[*]‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Mitigation’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActionRequest.IsDefinedBy['Pset_ActionRequest']\.RelatingPropertyDefinition\IfcPropertySet.HasProperties['PreventiveMeasures']‘

RelatedObjects[0:?] > ‘IfcElement’

IfcActor

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Email’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Company’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.TheOrganization.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Phone’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcTelecomAddress.TelephoneNumbers[*]‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘TheActor.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘TheActor’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘TheActor.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Department’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.TheOrganization.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘OrganizationCode’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.TheOrganization.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘GivenName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.GivenName’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘FamilyName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.FamilyName’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Street’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.Street’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘PostalBox’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘ IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.PostalBox’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Town’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.Town’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘StateRegion’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.Region’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘PostalCode’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.PostalCode’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Country’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcActor.TheActor\IfcPersonAndOrganization.ThePerson.Addresses[*]\IfcPostalAddress.Country’

RelatedObjects[0:?] = ‘IfcActor’

RelatedObjects[0:?] = ‘IfcActionRequest’
RelatedObjects[0:?] = ‘IfcPermit’
RelatedObjects[0:?] = ‘IfcProjectOrder’

IfcAsset

RelatedObjects[0:?] > ‘IfcElement’

IfcBuilding

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’11-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’12-00 00 00′

RelatedObjects[0:?] = ‘IfcBuildingStorey’

RelatedObjects[0:?] = ‘IfcSpatialZone’

IfcBuildingStorey

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey\’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Elevation’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.Elevation’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Height’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcBuildingStorey.IsDefinedBy['Qto_BuildingStoreyBaseQuantities']\RelatingPropertyDefinition\IfcElementQuantity.Quantities['NetHeight']\IfcQuantityLength.LengthValue’

RelatedObjects[0:?] = ‘IfcSpace’

.ConnectedTo = ‘IfcRelContainedInSpatialStructure’
.ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcElement’

IfcConstructionEquipmentResource

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’34-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’35-00 00 00′

IfcConstructionMaterialResource

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’41-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’42-00 00 00′

IfcConstructionResource

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResource.Description’

RelatedObjects[0:?] > ‘IfcConstructionResource’

RelatedObjects[0:?] >= ‘IfcActor’
RelatedObjects[0:?] >= ‘IfcProduct’

IfcConstructionResourceType

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘TypeName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.HasAssignments[*]\IfcRelAssignsToProduct.RelatingProduct’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Suppliers’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.OperatesOn[*].RelatedObjects’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SetNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘PartNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcConstructionResourceType.OperatesOn[*].RelatedObjects\IfcElementType.Tag’

RelatedObjects[0:?] > ‘IfcConstructionResource’

IfcCrewResource

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’33-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’34-00 00 00′

IfcDocumentInformation

Name <> ‘*\IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Name’

IfcElement

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘TypeName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsTypedBy[*].RelatingType’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Space’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.ContainedInStructure[*].RelatingStructure’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SerialNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsDefinedBy['Pset_ManufacturerOccurrence']\IfcPropertySet.HasProperties['SerialNumber']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘InstallationDate’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsDefinedBy['Pset_ManufacturerOccurrence']\IfcPropertySet.HasProperties['AquisitionDate']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyStartDate’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsDefinedBy['Pset_Warranty']\IfcPropertySet.HasProperties['WarrantyStartDate']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘TagNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.Tag’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘BarCode’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsDefinedBy['Pset_ManufacturerOccurrence']\.RelatingPropertyDefinition\IfcPropertySet.HasProperties['BarCode']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘AssetIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElement.IsDefinedBy['Pset_ManufacturerOccurrence']\.RelatingPropertyDefinition\IfcPropertySet.HasProperties['BatchReference']‘

IsDefinedBy[1:1] = ‘IfcRelDefinesByType’ AND .IsTypedBy\IfcRelDefinesByType.RelatingType <> ‘IfcProxyType’ AND .IsTypedBy\IfcRelDefinesByType.RelatingType <> ‘IfcBuildingElementProxyType’

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’22-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’23-00 00 00′

RelatedObjects[0:?] > ‘IfcElement’

RelatedObjects[0:?] > ‘IfcDistributionPort’

RelatedObjects[0:?] = ‘IfcTask’

.ConnectedTo = ‘IfcRelContainedInSpatialStructure’ AND .ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcSpatialStructureElement’
.ConnectedTo = ‘IfcRelConnectsElements’ AND .ConnectedTo\IfcRelConnects.RelatedElement > ‘IfcElement’

IfcElementType

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘AssetType’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['AssetType']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Manufacturer’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_ManufacturerTypeInformation']\IfcPropertySet.HasProperties['Manufacturer']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ModelNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_ManufacturerTypeInformation']\IfcPropertySet.HasProperties['ModelNumber']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyGuarantorParts’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_Warranty']\IfcPropertySet.HasProperties['PointOfContact']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyDurationParts’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_Warranty']\IfcPropertySet.HasProperties['WarrantyPeriod']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyGuarantorLabor’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssignments[*]\IfcProcedureType.HasPropertySets['Pset_Warranty']\IfcPropertySet.HasProperties['PointOfContact']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyDurationLabor’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssignments[*]\IfcProcedureType.HasPropertySets['Pset_Warranty']\IfcPropertySet.HasProperties['PointOfContact']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ReplacementCost’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.ReferencedBy[*].RelatedObjects[*]\IfcProcess.OperatesOn[*].RelatedObjects\IfcConstructionProductResource.CostRatesConsumed[*].AppliedValue\IfcMonetaryMeasure’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExpectedLife’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_ServiceLife']\IfcPropertySet.HasProperties['ServiceLifeDuration']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘WarrantyDescription’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_Warranty']\IfcPropertySet.HasProperties['WarrantyContent']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ReplacementCost’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.ReferencedBy[*].RelatedObjects[*]\IfcProcess.OperatesOn[*].RelatedObjects\IfcConstructionProductResource.CostRatesConsumed[*].AppliedValue\IfcMonetaryMeasure’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘NominalLength’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.RepresentationMaps[*].MappedRepresentation(‘Box’).Items[*]\IfcBoundingBox.XDim’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘NominalWidth’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.RepresentationMaps[*].MappedRepresentation(‘Box’).Items[*]\IfcBoundingBox.YDim’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘NominalHeight’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.RepresentationMaps[*].MappedRepresentation(‘Box’).Items[*]\IfcBoundingBox.ZDim’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ModelReference’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['Pset_ManufacturerTypeInformation']\IfcPropertySet.HasProperties['ModelReference']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Shape’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['Shape']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Size’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['Size']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Color’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['Color']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Finish’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['Finish']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Grade’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssociations[*]\IfcRelAssociatesMaterial.RelatingMaterial\IfcMaterial.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Material’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssociations[*]\IfcRelAssociatesMaterial.RelatingMaterial\IfcMaterial.Category’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Constituents’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasAssociations[*]\IfcRelAssociatesMaterial.RelatingMaterial\IfcMaterialConstiuentSet.MaterialConstituents’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Features’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['Features']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘AccessibilityPerformance’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['AccessibilityPerformance']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CodePerformance’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['CodePerformance']‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SustainabilityPerformance’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcElementType.HasPropertySets['COBie_ElementType']\IfcPropertySet.HasProperties['SustainabilityPerformance']‘

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’23-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’24-00 00 00′

RelatedObjects[0:?] = ‘IfcDistributionPort’

RelatedObjects[0:?] = ‘IfcTaskType’

IfcInventory

RelatedObjects[0:?] > ‘IfcElement’

IfcObjectDefinition

Name <> ‘*\IfcObjectDefinition.Name’

IfcOccupant

RelatedObjects[0:?] > ‘IfcSpatialStructureElement’

IfcPort

.ConnectedTo = ‘IfcRelConnectsPorts’ AND .ConnectedTo\IfcRelConnects.RelatedElement > ‘IfcPort’

IfcProject

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.IsDecomposedBy[*]\IfcBuilding.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.IsDecomposedBy[*]\IfcBuilding.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ProjectName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SiteName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘LinearUnits’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.UnitsInContext\IfcUnitAssignment.Units[LENGTHUNIT]\IfcConversionBasedUnit.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘AreaUnits’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.UnitsInContext\IfcUnitAssignment.Units[AREAUNIT]\IfcConversionBasedUnit.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘VolumeUnits’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.UnitsInContext\IfcUnitAssignment.Units[VOLUMEUNIT]\IfcConversionBasedUnit.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CurrencyUnits’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.UnitsInContext\IfcUnitAssignment.Units[*]\IfcMonetaryUnit.Currency’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSiteObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSiteIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtFacilityObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.IsDecomposedBy[*]\IfcBuilding’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtFacilityIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.IsDecomposedBy[*]\IfcBuilding.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.IsDecomposedBy[*]\IfcBuilding.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ProjectDescription’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SiteDescription’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.IsDecomposedBy[*]\IfcSite.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Phase’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcProject.Phase’

.HasAssociations\IfcRelAssociatesLibrary.RelatingLibrary = ‘IfcLibraryInformation’

RelatedDefinitions[0:?] = ‘IfcActor’
RelatedDefinitions[0:?] = ‘IfcControl’
RelatedDefinitions[0:?] = ‘IfcGroup’
RelatedDefinitions[0:?] = ‘IfcTask’
RelatedDefinitions[0:?] = ‘IfcConstructionResource’
RelatedDefinitions[0:?] = ‘IfcElementType’
RelatedDefinitions[0:?] = ‘IfcTaskType’
RelatedDefinitions[0:?] = ‘IfcConstructionResourceType’
RelatedDefinitions[0:?] = ‘IfcProjectLibrary’

RelatedObjects[0:1] = ‘IfcSite’

IfcProjectLibrary

.HasAssociations\IfcRelAssociatesLibrary.RelatingLibrary = ‘IfcLibraryInformation’

RelatingDefinitions[0:?] = ‘IfcElementType’
RelatingDefinitions[0:?] = ‘IfcTaskType’
RelatingDefinitions[0:?] = ‘IfcConstructionResourceType’
RelatingDefinitions[0:?] = ‘IfcProjectLibrary’

IfcPropertySetTemplate

.HasAssociations\IfcRelAssociatesLibrary.RelatingLibrary = ‘IfcLibraryReference’

IfcRelAssociatesDocument

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Purpose’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ApprovalBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumenformation.IntendedUse’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Stage’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Status’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SheetName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatedObjects[*]\’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘RowName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatedObjects[*]‘
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Directory’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Location’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘File’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Location’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Reference’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.DocumentId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Source’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcRelAssociatesDocument.RelatingDocument\IfcDocumentInformation.Location’

IfcSimplePropertyTemplate

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’49-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’50-00 00 00′

.HasAssociations\IfcRelAssociatesLibrary.RelatingLibrary = ‘IfcLibraryReference’

IfcSite

RelatedObjects[0:1] = ‘IfcBuilding’

IfcSpace

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘FloorName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.Aggregates[*].RelatingObject’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘RoomTag’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.LongName’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘UsableHeight’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.IsDefinedBy['Qto_SpaceBaseQuantities']\RelatingPropertyDefinition\IfcElementQuantity.Quantities['NetHeight']\IfcQuantityLength.LengthValue’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘GrossArea’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.IsDefinedBy['Qto_SpaceBaseQuantities']\RelatingPropertyDefinition\IfcElementQuantity.Quantities['GrossArea']\IfcQuantityArea.AreaValue’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘NetArea’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpace.IsDefinedBy['Qto_SpaceBaseQuantities']\RelatingPropertyDefinition\IfcElementQuantity.Quantities['NetArea']\IfcQuantityArea.AreaValue’

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’13-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’14-00 00 00′

.ConnectedTo = ‘IfcRelContainedInSpatialStructure’ AND .ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcFurnishingElement’
.ConnectedTo = ‘IfcRelCoversSpaces’ AND .ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcCovering’
.ConnectedTo = ‘IfcRelSpaceBoundary’ AND .ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcBuildingElement’

ObjectPlacement\IfcLocalPlacement.RelativePlacement\IfcAxis2Placement3D.Location\IfcCartesianPoint.Coordinates[3] = ‘ProvidesBoundaries[1:1]\IfcRelSpaceBoundary.RelatedBuildingElement\IfcSlabStandardCase.Representation\IfcProductDefinitionShape.Representations[1:1]\IfcShapeRepresentation.Items[1:1]\IfcExtrudedAreaSolid.Depth’

IfcSpatialZone

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘SpaceNames’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.ReferencesElements.RelatedElements’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSpatialZone.Description’

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’14-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’15-00 00 00′

RelatedObjects[0:?] = ‘IfcSpatialZone’

.ConnectedTo = ‘IfcRelReferencedInSpatialStructure’ AND .ConnectedTo\IfcRelConnects.RelatedElement = ‘IfcSpatialStructureElement’
.ConnectedTo = ‘IfcRelServicesBuildings’ AND ObjecType = ‘IfcSystem’

IfcSubContractResource

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’32-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’32-00 00 00′

IfcSystem

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ComponentNames’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.IsGroupedBy[*].RelatedObjects’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcSystem.Description’

RelatedObjects[0:?] > ‘IfcElement’

RelatedObjects[0:?] > ‘IfcSystem’

IfcTask

.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Name’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.Name’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedBy’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.OwnerHistory.OwningUser.ThePerson.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘CreatedOn’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.OwnerHistory.CreationDate’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Category’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.HasAssociations[*]\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Status’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.Status’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘TypeName’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.HasAssignments[*]\IfcRelAssignedToProduct.RelatingProduct’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Description’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.Description’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Duration’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.TaskTime\IfcTaskTimeRecurring.ScheduleDuration’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Start’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.TaskTime\IfcTaskTimeRecurring.ScheduleStart’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Frequency’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.TaskTime\IfcTaskTimeRecurring.Recurrence\IfcRecurrencePattern.Occurrences’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Frequency’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.TaskTime\IfcTaskTimeRecurring.Recurrence\IfcRecurrencePattern.RecurrenceType’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtSystem’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.OwnerHistory.OwningApplication.ApplicationIdentifier’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtObject’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ExtIdentifier’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.GlobalId’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘TaskNumber’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.Identification’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘Priors’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.IsSuccessorTo’
.HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Name = ‘ResourceNames’ AND .HasAssociations\IfcRelAssociatesConstraint.RelatingConstraint\IfcObjective.Benchmarks\IfcMetric.DataValue\IfcTable.Columns\IfcTableColumn.Identification = ‘IfcTask.OperatesOn[*].RelatedObjects’

.HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Source = ‘OmniClass’ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification > ’31-00 00 00′ AND .HasAssociations\IfcRelAssociatesClassification.RelatingClassification\IfcClassificationReference.Identification < ’32-00 00 00′

RelatedObjects[0:?] = ‘IfcTask’

RelatedObjects[0:?] > ‘IfcConstructionResource’

.IsConnectedTo = ‘IfcRelSequence’ AND .IsConnectedTo\IfcRelConnects.RelatedElement = ‘IfcTask’

IfcTaskType

RelatedObjects[0:?] > ‘IfcConstructionResourceType’

IfcUnitAssignment

Units[1:1]\IfcNamedUnit.UnitType = ‘LENGTHUNIT’
Units[1:1]\IfcNamedUnit.UnitType = ‘AREAUNIT’
Units[1:1]\IfcNamedUnit.UnitType = ‘VOLUMEUNIT’
Units[1:1]\IfcNamedUnit.UnitType = ‘MASSUNIT’
Units[1:1]\IfcNamedUnit.UnitType = ‘PLANEANGLEUNIT’

Annex D

(informative)

External mappings

Annex D.1 General mappings

Data within this specification may be mapped to tables found in databases, spreadsheets, or comma-delimited files.

Such spreadsheets may be imported or exported from any IFC format (IFC-SPF, IFC-XML, IFC-ZIP), containing the subset of data described within this MVD.

Standard mappings of IFC objects and attributes to tables and columns are specified at each included entity. These mappings may be encoded within IFC files as constraints related to an external association (document or library), such that application software may import, export, or synchronize content with such files or databases by understanding the mappings alone.

Annex D.2 Spreadsheet mappings

Spreadsheets in Office Open XML format (such as Microsoft Excel) may contain content described in this specification using the following conventions:

Each worksheet within a spreadsheet may contain objects of particular types or subtypes.
Each column within a worksheet may indicate a particular attribute (either direct, inverse, and/or along a graph).
Each row within a worksheet (except for the first header row) may indicate an object instance.
Each cell may indicate an attribute value.

Values for object references within a specific worksheet identify the referenced object by Name; therefore, it is required that each object have a unique name.

Values for object collections identify each by name and are separated by comma (commas are not allowed in names).

Values for object references of arbitrary types use two cells: one indicating the name of the worksheet, and another indicating the Name of the object instance.

Several columns are used throughout to provide standard behavior:

Name: This indicates the unique text identifier of an object corresponding to its Name attribute, with characters restricted as described herein.
ExtIdentifier: This provides the unique GUID identifier of an object in IfcGloballyUniqueId format.
ExtObject: This indicates the type of an object using the IFC entity name such as ‘IfcSensorType’.

The association of an IFC file to a spreadsheet may be indicated by IfcRelAssociatesDocument and IfcDocumentInformation, with mappings described by IfcResourceConstraintRelationship, IfcObjective, IfcMetric, IfcTable, and IfcTableColumn.

Annex D.3 Database mappings

Relational databases may contain content described in this specification using the following conventions:

Each table within a database may contain objects of particular types or subtypes.
Each column within a table may indicate a particular attribute (either direct, inverse, and/or along a graph).
Each row within a table may indicate an object instance.
Each cell may indicate an attribute value.

Values for rooted object references (deriving from IfcRoot) within a specific table identify the referenced object by GUID. Values for rooted object references of arbitrary types use two cells: one indicating the name of the table, and another indicating the GUID of the object instance.

Values for object collections (SET or LIST) identify each by GUID and are included in separate tables named in the form ‘{Entity}_{Attribute}’ with the GUID column ‘Value’ (and additional one-based integer column ‘Position’ for lists).

Values for non-rooted object references (not deriving from IfcRoot) and the graph of all referenced objects are serialized as XML using IFC-XML encodings. This affords efficient localized retrieval of data graphs such as geometry.

Values for STRING, BINARY, INTEGER, REAL, BOOLEAN, and LOGICAL use equivalent native database types.

Values for ENUM use strings.

The association of an IFC file to a database may be indicated by IfcRelAssociatesLibrary and IfcLibraryInformation, with mappings described by IfcResourceConstraintRelationship, IfcObjective, IfcMetric, IfcTable, and IfcTableColumn.

Annex E

(informative)

Examples

Example files are available at http://buildingsmartalliance.org/index.php/projects/commonbimfiles/.

E.1 Duplex

The duplex apartment model was originally created by a student who developed this building as part of a design competition. This model was first used at the Dec 2009 COBie Challenge event. The model provided here is the second version of this model completed by designers at Kristine Fallon and Associates.

E.2 Office

The two story office building model was developed based on the published sample floor plans for a specific type of mid-size office building built in the United States.

E.3 Clinic

The Clinic Model was developed based on an actual federal medical and dental clinic building at a location in the South-West United States. The model also comes with a set of redacted design drawings. A full set of operations and maintenance manuals are also available but have not yet been redacted, so cannot yet, be posted to this public repository.

Annex F

(informative)

Validation

F.1 Overview of mvdXML

Model View Definition XML (mvdXML) is a file format defined by buildingSMART International for describing and enforcing information exchanged using Industry Foundation Classes (IFC).

An mvdXML file is intended to be used for the following purposes:

Test servers for validating IFC files exported by applications;
Certification of software applications conforming to scope and requirements;
Software applications for enforcing valid data;
Documentation generation.

Using encoded business rules, most if not all requirements can be electronically validated.

F.2 Details of mvdXML

The following data structures are defined within mvdXML:

mvdXML: The mvdXML element comprises the scope of the mvdXML document, it includes zero-to-many model views and one-to-many concept templates (as a minimum, all concept templates that are referenced on the included model view(s)).
ModelView: The Model View Definition (MVD) that represents a subset of the IFC schema to cover the exchange requirements.
ConceptTemplate: The concept template holds the common definitions of a concept, that are independent of its use within a root concept. Concept nodes and concept leaf nodes reference a concept template to share the common description.
ConceptRoot: The root concept (called variable concept in MVD V2.0 documentation). It defines the main and independent entity that is part of a Model View Definition and also provides the root for all path information. Examples are IfcWall, IfcSpace.
Concept: The concept assigned to the root concept. It is an abstract element that can either be a concept node (called adapter concept in MVD V2.0 documentation), or a concept leaf node (called static concept in MVD V2.0 documentation). The concept is specific to the root concept and may reference a concept template for common descriptions.
ConceptNode: The ConceptNode element is an MVD specific concept, already assigned via a root concept to a model view. It has a reference to a concept template from which it re-uses the definition, it may add a specific definition that only relates to its particular usage for the root element. It has sub concepts, i.e. the information of whether it is required/optional is aggregated from its sub components.
ConceptLeafNode: The ConceptLeafNode is an MVD specific concept, already assigned via a root concept to a model view either directly, or via one or several concept nodes. It has a reference to a concept template from which it re-uses the definition, it may add a specific definition that only relates to its particular usage for the root element. It does not have any more sub contexts (it represents the leaf node).
ExchangeRequirement: The ExchangeRequirement element indicates a particular exchange for which a set of requirements at various entities may apply.
Definition: The Definition element indicates a human-readable description of the concept, with optional diagrams and external links.
Requirement: The Requirement element indicates how a concept applies to a particular exchange for import and/or export, and whether it is required, optional, prohibited, or not applicable.
AttributeRule: The AttributeRule element identifies an attribute relative to an entity, which may be either a direct attribute or an inverse attribute.
EntityRule: The EntityRule element identifies a type of entity that may be referenced by an attribute, either as a single object or within a collection.
TemplateRule: The TemplateRule element identifies parameters to be used for rules defined at re-usable templates.
Constraint: The Constraint element indicates an expression to be validated at a particular attribute.

F.3 Template Usage

Rules can be defined explicitly at concept leaf nodes (using AttributeRule), or parametrically (using TemplateRule) by using the defined template (containing AttributeRule).

The “TemplateRule.RuleID” attribute refers to an EntityRule defined on the template which is to be instantiated.

The “TemplateRule.Parameters” attribute indicates the set of parameters and values to be applied to referenced rules, each delimited by semicolon (same convention as HTML styles) or logical operator.

Each parameter-value component consists of the RuleID followed by a Constraint Expression. The RuleID identifies an AttributeRule and optional index delimiter for which the ConstraintExpression is applied.

The Constraint Expression contains an operator followed by a literal value or reference value (identified by RuleID).

The following logical operators are supported, corresponding to the IFC constraint model:

“AND”: All operands are true, alternatively a semicolon may be used as abbreviation (“;”);
“OR”: At least one operand is true;
“XOR”: Exactly one operand is true;
“NAND”: At least one operand is false;
“NOR”: All operands are false;

The following attribute index delimiters are supported:

“[0:1]”: For a SET or LIST, must be zero or exactly one instance meeting the rule.
“[1:1]”: For a SET or LIST, must be exactly one instance meeting the rule.
“[0:?]”: For a SET or LIST, must be zero or all instances meeting the rule.
“[1:?]”: For a SET or LIST, must be one or all instances meeting the rule.
“[1]”: For a LIST, the instance at the first index must meet the rule.
“[2]”: For a LIST, the instance at the second index must meet the rule (and so on).

The following comparison operators are supported, corresponding to the IFC constraint model:

“=”: equal;
“<>”: not equal;
“>”: greater than;
“>=”: greater than or equal;
“<”: less than;
“<=”: less than or equal.

The syntax of literal values varies according to the EXPRESS attribute type and follows ISO-10303-28 format:

INTEGER: The integer value; all operators supported.
REAL: The real value which must include a decimal point; all operators supported.
BOOLEAN: The boolean value as “true” or “false”; equality operators supported.
LOGICAL: The logical value as “true”, “false”, or “unknown”; equality operators supported.
ENUMERATION: The enumeration value by case-insensitive name; equality operators supported.
STRING: The string value, which may optionally be enclosed by single quotes (if escaping required); all operators supported, where comparison operators indicate alphabetical sorting (e.g. “>=” can indicate “must start with” such as the scope of a classification reference, or earliest date/time).
BINARY: The binary value encoded as hexadecimal prefixed by “%” and number of unused bits; all operators supported, where comparison operators indicate binary sorting.
ENTITY: The name of the entity type (e.g. “IfcWall”). Equality means exact type match; “>” means subtype of; “>=” means same type or subtype; “<” means supertype of; “<=” means same type or supertype.

Parameter values are indicated by specifying “#” followed by an arbitrary identifier of a shared instance. For example, a rule could indicate for IfcBeamStandardCase that an IfcProfile for an IfcExtrudedAreaSolid must match the profile defined within an associated IfcMaterialProfile, where they each equal the same value referenced as “#MP”.

E.4 Template Example

The following example illustrates the enforcement of an IfcSite object containing at least one IfcBuilding through the IfcRelAggregates relationship.

An aggregation template is defined to specify the graph of attribute and entities, where the RelatedObjects attribute has a RuleID indicated to enable referencing at leaf nodes:
The object may be aggregated into components using IfcRelAggregates where RelatingObject refers to the enclosing object and RelatedObjects contains one or more components.]]

The above template is then instantiated at IfcSite. The ConceptLeafNode identifies the template by UUID. The particular exchange where the concept applies is identified by the Requirement element. The TemplateRule element contains the expression “RelatedObjects[1:1]=IfcBuilding” which indicates that the rule having RuleID of “RelatedObjects” on the ConceptTemplate is to have a constraint of “=IfcBuilding”, where the “=” operator means the type must match exactly to “IfcBuilding”. Here, RelatedObjects refers to the IfcRelAggregates.RelatedObjects attribute, though the RuleID does not necessarily match the attribute name. As this attribute is a SET and the indexer is set to “[1:1]” there must be exactly one instance.
A site is a defined area of land, possibly covered with water, on which the project construction is to be completed. A site may contain zero, one or more buildings.

The template may be applied to IFC files with sample data. The following data conforms to the rule (note that required attributes are omitted for brevity).

The following data DOES NOT conform to the rule, as it contains multiple buildings.

The following data DOES NOT conform to the rule, as it contains the wrong type of object.

The following data DOES NOT conform to the rule, as one object is the correct type, and an additional object is of the wrong type.

The following data DOES NOT conform to the rule, as it does not contain any IfcBuilding.

What is BIM – Strategy, Process, or Technology ?

pcholakis — Mon, 02 Jan 2012 19:03:18 +0000

BIM is an integration of process and technology to enable the efficient life-cycle management of facilities (the latter including vertical and horizontal physical infrastructure… buildings, roadways, utilities, landscapes, etc.). BIM is a digital integration of previously disparate processes and technologies to allow organization to better link the built environment to support physical and functional requirements, while at the same time optimizing return on investment and associated impacts upon the environment. Considerations include design, procurement, construction delivery methods, construction management, condition assessment, repair, renovation, adaptation, utilization, capital planning and budgeting, life/safety, security, and sustainability.

BIM is divergent from the traditional antagonistic and inefficient architectural, design, engineering, construction, and operations management process which have been responsibility for the lack of overall productivity in these sectors. BIM is a collaborative process involving all stakeholders/shareholders and is supported by an integral digital framework. The latter enables rapid, scalable deployment and consistent/transparent deployment and management.

BIM - Integration of Process and Technology to Enable Efficient Facility Life-Cycle Management

BIM requires a structured approach relative to terms, definitions, data architectures across multi-disciplinary knowledge domains to allow for efficient, transparent data sharing and re-use. Some of the associated, currently silo-based competencies and activities are shown in the below graphic.

BIM requires the integration of currently disparate processes and technologies

BIM and Sustainability Require Efficient Project Delivery Methods for Success

pcholakis — Mon, 19 Dec 2011 14:52:58 +0000

The interest and demand for BIM (building information modeling) sustainable buildings in the United States is fueled by climate change, natural resource depletion, and associated worldwide environmental and economic issues.

In order to deploy solutions enhanced Project Delivery Methods must be employed to achieved required productivity levels and timelines. Traditional design-bid-build and even the “newer” design-bid methods are not up to the tasks a hand. Integrated project delivery (IPD) and job order contracting (JOC), the latter a form of IPD specifically for facility renovation, repair, and sustainability, are needs to improve team/stakeholder integration and project outcomes. While both IPD and JOC are not “new”, having been used for decades, they require a shift in
“culture” within the Architecture, Engineering, Construction, Operations, and Owners (AECOO) sectors.

While technologies now exist to support these new methods (BIM, advanced cost estimating and project delivery software, and Cloud Computing), overcoming cultural issues is non-trivial. Despite clear data that supports the ability to achieve higher productivity with enhanced owner/contractor/architect/community integration via integrated project delivery and JOC, the “status quo” driven by a culture of “change orders”, “spreadsheets”, and “short term relationships” appears a significant barrier to change.

via www.4Clicks.com – Premier software for efficient project delivery – JOC, SABER, IPD, SATOC, MATOC, IDIQ, MATOC, MACC, POCA, BOA

Contractors, Owners – Create 200,000+ Jobs – Buy Made in America Products

pcholakis — Fri, 16 Dec 2011 14:38:18 +0000

A recent report by ABC News notes that if every construction job used 5% more products that are Made in America over 200,000 jobs would be created.

Do you part and start today!!!!!

Here’s the initial list:

Product Manufacturer/Supplier State
Windows Amsco Windows UT
J bolts/foundation S.C. Prototypes MT
J bolts/foundation/stock Pacific Steel UT
Gorilla Duct tape The Gorilla Glue Co OH
4″ perforated pipe, radon Northern Pipe Co. ND
4″ pvc fittings GPK ND
pvc glue Oatey OH
8d ring shank nails True Spec CA
16d sinkers Griptite WI
1/2″ foundation nuts CAT IL
gun nails Maze IL
damp proofing Mulseal/Tremco OH
Rebar Nucor UT
Concrete CMI MT
Concrete Portland Ash Grove MT
Concrete aggregate CMC. Beglade MT
Concrete sand CMC. Beglade MT
Hangers, straps, H clips Simpson Strong-Tie CA
TJI’s I-Level Truss Joist OR
2×4′s and 2×6′s RY Lumber MT
Plywood Potlatch ID
2×4′s and 2×6′s F.H. Stoltze MT
2×4′s and 2×6′s Idaho Forest ID
PL 400 sub floor adhesive Loctite CT
MiraTEC fascia CMI Corp PA
treated plate McFarland Cascade WA
T braces/framing Appleton Supply WI
sill seal Reflectix IN
powder actuated pins TW Ramset/Redhead IL
foam board Dow IL
Spray paint Rustoleum IL
Spray insulation JM Corbond MT, TX
Screws Por Pac CO, CT
Wire joint Thomas & Betts TN
Spray paint ACE IL
paint Sherwin Williams OH
Window foam Touch n Seal MO
Caulking White Lightning OH
Plastic elect. Straps Handy Straps WI
meter base Eaton/Cutler Hammer PA
electric panel Eaton/Cutler Hammer PA
Breakers Eaton/Cutler Hammer PA
PVC pipe/fittings Ridgeline Pipe OR
2″ Romex connectors Bridgeport CT
Boxes Allied OH
Wire-service, romex Southwire GA
staples Sturgeon Bay WI
4/0 SER straps Sturgeon Bay WI
Telephone wire 3M MN
wire connectors/crimp sleeves Ideal IL
wire staples Sturgeon Bay WI
Furnace disconnect Eaton/Cutler Hammer PA
recessed cans Juno/Schneider Electric IL
recycled glass Livingston Landfill MT
Furnace Trane TX
Cooling Coil Trane TX
HRV Trane TX
Air Cleaner Trane TX
Zoning/Thermostats Trane TX
Ductwork Norwesco WA
Screws Brynolf Manufacturing IL
PVC Cresline-Northwest WA
Condensate Trap Airtec MA
Registers/Grilles Hart & Cooley MI
Allthread Rod Chicago Hardware IL
Pipe Brackets C&S Manufacturing WI
Conensate Pump Franklin Electric IN
Unistrut Cooper B-Line IL
Flexible Duct Atco TX
Duct Sealant Hardcast TX
Flex Duct Straps Source 1 OK
PVC Glue/Primer Oatey OH
Thermostat Wire Honeywell MS
Exhaust Fans Broan WI
Concentric Vent Source 1 OK
Exhaust Hoods Broan WI
Nuts/ Washers Perine Danforth WA
Dryer Box In O Vate Tech FL
Duct Liner Johns Manville CO
Duct Liner Pins Hardcast TX
Allthread Anchors ITW Buildex IL
Ductstrap Colombia Man WA
Manual Dampers Norwesco WA
Sill Sealer Reflectix, Inc. IN
PVC Primer and Cement Oatey OH
PVC Pipe Cresline-Northwest WA
Pex Pipe Viega KS
Kitchen Sink Moen PA
Kitchen Faucet Moen NC
Kitchen Basket strainer Dearborn Brass TX
Kitchen disposer In-Sink-Erator WI
Bathroom Pedestal Lav Mansfield OH
Bathroom Lav faucet Moen NC
Bathroom Lav sink Mansfield IL
Bathroom toilets Mansfield IL
Bathroom toilet seats Kohler AR
Master Shower Aquaglass OR
Master shower valve Moen NC
Master shower trim Moen NC
Master soaker tub Aquaglass OR
Master soaker tub trim Moen NC
Master soaker tub valve Moen NC
Bathtub waste and overflow Watco MO
Full Bath tub/shower Aquaglass OR
Full Bath tub/shower trim Moen NC
Full Bath tub/shower valve Moen NC
Water Heater Bradford White PA
Pex Fittings Zurn TX
PVC Fittings Sioux Chief MO
Hangers/pipe insulators Sioux Chief MO
Roof Jack Oatey OH
Plumber Putty Hercules NJ
Wax rings Hercules NJ
Thread Dope Hercules NJ
Plumber tape Smith/Cooper CA
Black pipe RJB Wholesale, Inc WA
Black pipe fittings Anvil International NV
Gastite pipe and fittings Gastite MA
Soulder Flux Rectorseal TX
Soulder Exeon Inc. IL
Copper Pipe Cerro Flow Products Inc. MO
Copper fittings Elkhart Products Corp. IL
Backflow preventor/PRV Watts ME
Expansion Tank Amtrol RI
Hose bibs Woodford CO
Chattahoochee Pencil Company Atlanta GA

Facility Management Process/Technology Roadmap – BIM, IPD, JOC, TCO, EVM, IWMS

pcholakis — Thu, 15 Dec 2011 20:34:21 +0000

If you believe Cloud Computing is “hype”, “unsecure”, “won’t be accepted as an enterprise-wide solution”…. WRONG.

Significant change is upon the AECOO (Architecture, Engineering, Construction, Operations, Owner) Sectors, and many are unprepared.

BIM… as a process (not as a 3D visualizuati0n tool) will be commonplace, in parallel with cloud computing, total cost of ownership, as well as efficient construction project delivery mechanisms such as IPD (integrated project delivery) and JOC (Job Order Contracting).

Currently used techologies and processes such as IWMS (Integrated Workplace Mangement Systems), EVM (earned value management), and LEAN are interim at best as they do not provide the level of domain-knowlege, ease-of-use, or scalability, collaboration and interoperability needed to be efficient.

IWMS systems, for example… like Maximo, TMA, Planon, etc. have roots in legacy applications and/or specfic knowledge-domains (such as CMMS-commuterized maintenance management, or CAFM-computer-aided facilities management/space planning/utilization). Despite attempts to provide equivalent levels of sophisitications across all requisite domains, they appear to struggle at best.

Similarly, processes sush as EVM or ” earn-valued management” are being applied to Construction Project Management. While this may represent a step forward for many construction firms and Owners, is far too simplistic to enable facility life-cycle management and/or total cost of ownership (TCO) level decision support.

The convergence of BIM as a process and Cloud Computing provides the enabling platform for facility life-cycle mangement. The future is now.

The Importance of Construction Cost Standards

pcholakis — Thu, 15 Dec 2011 14:13:02 +0000

Masterformat, Uniformat, and reference cost databases such as RS Means Construction Cost Data are important “best practices” for enabling facility Owners, Contractors, AE’s, and oversight groups to achieve higher productivity, accuracy, and transparency for all construction, renovation, repair, and sustainability projects.

-   MasterFormat is a standard for construction unit price line items for commercial and institutional ( JOC, SAB ER, IDIQ, SATOC, MATOC, MACC, POCA, BOA) building projects. MasterFormat was developed by the Construction Specifications Institute (CSI) and Construction Specifications Canada. In November 2004 MasterFormat expanded from 16 Divisions to 50 Division to keep pace with the construction industry. [2].
-   UniFormat, also a publication of CSI and CSC, is a method of arranging construction information based on functional elements, or parts of a facility characterized by their functions, These elements are often referred to as systems or assemblies. Uniformat II is the current version available.
-   RSMeans Cost Data adheres to, and expands upon the MasteFormat and Uniformat II standard, while 4Clicks provides an even further enhancement of RSMeans Cost Data, providing approximately 400,000 line items.

Green-Washing and Cloud-Washing – Terms you must know relative to BIM – Not to mention BIM-Washing

pcholakis — Tue, 13 Dec 2011 17:31:57 +0000

BIM is the life-cycle management of facilities supported by digital technology – NIBS. That said, BIM is critical to sustainability/green as is collaboration and cloud computing.

As BIM, Green/Sustainability, and Cloud Computing are considered “new” and not necessarily “mainstream”.. and all three are “hot topics”, it’s not surprising that some organizations are engaging in BIM-washing, Green-washing, and Cloud Computing-washing.

These issues are extremely important, thus worthy of discourse.

GREEN WASHING

Here’s an informal poll relative to Green-washing. The question, asked on Linked-In was “Labels + Certificates = Sustainability. Yes. No. Or?” The question and responses bring to mind “LEED”… a great marketing tool perhaps, but it’s value remains uncertain, especially when considering long-term/life-cycle aspects. Also what due labels really mean… who polices product labels? Is bamboo really green if you consider it is transported halfway around the world. Is mercury-based lighting sustainable? Oh and yes…. the Prius and other vehicles have the nasty little batter disposal problem to deals with…

GreenWashing

CLOUD COMPUTING WASHING

Cloud computing is NOT taking legacy applications and moving them to the cloud via a virtual server. Cloud computing consists of three tier technology.

Cloud Layers

Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS).

Cloud computing is viewed as a means to break down traditional data and process stovepipes. Cloud computing encompasses four different deployment models, and in these preliminary stages of cloud development, organizations are free to determine which model best serves their needs. The four models, as defined by the National Institute of Standards and Technology (“NIST”), include: (1) private clouds, for the use of a single agency; (2) community clouds, shared by multiple agencies; (3) public clouds, largely for the public’s use and benefit; and (4) hybrid clouds, facilitating the sharing of data and utilities across two or more unique clouds of any type.

(Peter Mell and Tim Grance, Nat’l Inst. of Standards and Tech., The NIST Definition of Cloud Computing – 2009)

Cloud computing will enable collaborative, secure, and transparent applications and the rapid deployment of robust business process.. both so sorely needed in the AECOO sector (architecture, engineering, construction, owner, operator).

Major Shifts in Information Technology

BIM WASHING

Ok folks. I’ve said it before, and I will say it again. 3D visualization is NOT BIM !!! The integration all aspects and processes of facility life-cycle management is BIM. Will all this occur in Revt, Archcad, or some IWMS system… absolutely NOT! Cloud computing, however, integrated with existng knowledge-domains such as CPMS, Construction Project Delivery (IPD, JOC), CMMS, CAFM, GIS, BAS, …. now that’s BIM!

BIM Strategy and Framework

$4B for Improved Building Energy Efficiency – Obama’s Better Buildings Initiative – Perfect for Job Order Contracting – JOC

pcholakis — Tue, 06 Dec 2011 14:39:38 +0000

Efficient construction project delivery is needed to meet building efficiency targets. While there have been several attempts to address sustainability and the built environment, the lack of efficient project delivery has impacted progress.

Job Order Contracting / JOC – is an efficient integrated project delivery methods that focuses upon collaboration and longer term relationships between Owners and Contracting, resulting in higher productivity and greater transparency. It’s time that JOC be implemented Agency-wide throughout the Federal Sector.

President Obama’s Better Buildings Initiative is part of a vision for winning the future by catalyzing a homegrown, clean energy economy in the United States. The Better Buildings Initiative set a national target of improving energy efficiency in commercial buildings by 20 percent by 2020.

Job Order Contracting Process - Deployed via Technology

Achieving the President’s goal will reduce energy bills for American businesses by approximately $40 billion per year. Improving energy efficiency in our nation’s buildings can create good paying jobs in the construction industry. The Political Economy Research Institute (PERI) at the University of Massachusetts Amherst supported by the Real Estate Roundtable and U.S. Green Buildings Council estimated a potential of 114,000 jobs associated with implementing the Better Buildings Initiative.

It is a trifecta, which is why you’ve got labor and business behind it. It could save our businesses up to $40 billion a year on their energy bills – money better spent growing and hiring new workers. It would boost manufacturing of energy-efficient materials. And when millions of construction workers have found themselves out of work since the housing bubble burst, it will put them back to work doing the work that America needs done. So this is an idea whose time has come. – President Obama

President Obama directed all Federal agencies to make at least $2 billion worth of energy efficiency upgrades over the next two months. Additionally, 60 private companies, hospitals, cities, states, colleges, and universities, among others, have collectively committed another $2 billion in energy efficiency retrofits to 1.6 billion square feet of property.

Goal of improving energy efficiency in commercial buildings by 20 percent by 2020. The initiative will reduce energy bills for businesses by $40 billion per year, and one report found it could create up to 114,000 jobs.
The Better Buildings Challenge is the public-private partnership component of President Obama’s Better Buildings Initiative. The Challenge seeks to catalyze private sector investment and has attracted business and community leaders who are committed to supporting innovative ideas with action, sharing their successes, and creating solutions for others to follow. TheClinton Global Initiative (CGI) America, former President Clinton, Secretary Chu and Laura Tyson from the President’s Jobs Council announced an initial set of commitments totaling 300+ million square feet and $500+ million in financing support. The President announced commitments totaling 1.6 billion square feet and nearly $2 billion in financing support for building energy upgrades. This includes: Commitments from [60] Major CEOs, Universities, Mayors, Labor Leaders and Others – corporations, hospitals, financial institutions, cities and states, colleges and universities.

Data from the Department of Energy reveals a tremendous potential for efficiency investment opportunities in Federal buildings with less than 10-year paybacks. The Presidential Memorandum also directs Federal agencies to complete evaluations to identify specific energy conservation measures, including estimated cost and return on investment to prioritize and implement those energy conservation measures with the best payback, and to provide transparency and accountability through public reporting of results.

via www.4Clicks.com, premier software for efficient construction project delivery – visual cost estimating and project management for JOC, IPD, SABER, SATOC, IDIQ, MATOC, MACC, POCA, BOA