The “I” for Information if Building Information Modeling or Life-cycle Facility Management

While articles and discussions continue about Facility Management and BIM, in reality they are virtual synonyms.

Facility management is a profession that encompasses multiple disciplines to ensure functionality of the built environment by integrating people, place, process and technology. – Definition of Facility Management – IFMA

Building Information Modeling (BIM) is a digital representation of physical and functional characteristics of a facility.  A BIM is a shared knowledge resource for information about a facility forming a reliable basis for decisions during its life-cycle; defined as existing from earliest conception to demolition. – NIBS

In order to achieve either efficiently I argue that Information and Process must be shared in a consistent, mutually understood format among all stakeholders of the built environment: Owners, AEs, Contractors, Sub-contractors, Business Product Manufacturers, Building Users, and Oversight Groups.

The problem remains, however, that many don’t understand the multiple knowledge domains or competencies associated with the life-cycle management of the built environment, nor how to integrated them.  What is even worse, is that some of those that do understand are unwilling to share that information due to perceived issues with doing so.

NBIMS and similar efforts are steps in the right direction.  NBIMS attempts to consolidate and communicate information requirements, models, and associated usage processes, with an “open industry” approach.

Owners must clearly push for BIM and Life-cycle Facility Management.  Why?  Simple…they pay the bills and it is in their best interests to optimize their return on investment (ROI).  That said, Owners can’t do it alone.  By the very nature of the industry, all stakeholders must collaborate.  Unlike an airplane, or car… buildings are around for 50-100 years, have multiple uses, and can be adapted to changing situations.. also a far greater number of suppliers and service providers are involved, as well as a virtually infinite number of configurations.

 

Here’s are quick graphic of just a few of the areas, competencies, and technologies involved:

 

via http://www.4Clicks.com – Premier cost estimating and efficient project delivery software featuring an exclusively enhanced 400,000+ RSMeans Cost database and support for JOC, SABER, IDIQ, SATOC, MATOC, MACC, POCA, BOA, BOS, and more!

Construction Disruption – BIM, Cloud Computing, and Efficient Project Delivery Methods

By Peter Cholakis
Published in the March 2013 issue of Today’s Facility Manager

Emergent disruptive technologies and construction delivery methods are altering both the culture and day-to-day practices of the construction, renovation, repair, and sustainability of the built environment. Meanwhile, a shifting economic and environmental landscape dictates significantly improved efficiencies relative to these facility related activities. This is especially important to any organization dependent upon its facilities and infrastructure to support and maintain its core mission.

The disruptive digital technologies of building information modeling (BIM) and cloud computing, combined with emergent collaborative construction delivery methods are poised to alter the status quo, ushering in increased levels of collaboration and transparency. A disruptive technology is one that alters the very fabric of a business process or way of life, displacing whatever previously stood in its place. BIM and cloud computing fit the profile of disruptive technologies, individually, and when combined these stand to create a tidal wave of change.

BIM is the life cycle management of the built environment, supported by digital technology. While a great deal of emphasis has been placed upon 3D visualization, this is just a component of BIM. The shift from a “first cost mentality” to a life cycle cost or total cost of ownership is a huge change for many. Improving decision making practices and applying standardized terms, metrics, and cost data can also prove challenging. An understanding and integration of the associated knowledge domains important to life cycle management is required, resulting in what is now being referred to as “big data.”

Cloud computing is also a disruptive technology, and it’s one that impacts several areas. The National Institute of Standards and Technology (NIST) definition of cloud computing is as follows, “Cloud computing is a model for enabling ubiquitous, convenient, on demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. The cloud model is composed of five essential characteristics, three service models, and four deployment models.”

It is perhaps helpful to define cloud computing in terms of its benefits. Cloud computing enables far greater levels of collaboration, transparency, and information access previously unavailable by traditional client/server, database, or even prior generation web applications. Multiple users can work on the same data set with anyone, anywhere, anytime, in multicurrency, multilanguage environments. All changes can be tracked to “who did what” within seconds (potentially the best form of security available), and information is never deleted.

The disruptive technologies of BIM and cloud computing will accelerate the adoption of emergent construction delivery methods and foster new frameworks. Design-bid-build, the traditional construction delivery method for decades, is inherently flawed. As a lowest bid deployment it immediately sets up adversarial relationships for involved parties. Owners prepare a solicitation for construction projects based on their understanding of them¹, with or without third-party A/E assistance, and in most cases they go out in search of the lowest bidder. Then without a thorough understanding of the owner’s facility, bidders base their responses on the owner’s solicitation, plans, and specifications. Owners typically allow a period of time for bidders’ questions and clarifications; but the quality of this interchange is at best questionable if based solely on a written scope, plans and specifications, and/or a meeting with suppliers.

Design-build, arguably a step in right direction, falls short of bringing all stakeholders together. More responsibility of design and construction is shifted to the contractor and/or A/E. However, the dual level participation structure doesn’t assure the interests of all parties are equally addressed. Furthermore, the design-build process is typically reserved for major new construction projects versus the numerous sustainability, repair, renovation projects, and minor new construction projects typically encountered by facility managers (fms).

Because BIM brings together previously disparate information into a framework that enables decision support, using the technology requires a collaborative construction delivery method. The integration of the domain knowledge and robust processes required to allow fms, A/Es, and other stakeholders to achieve heightened levels of information sharing and collaboration is enabled by methods that include Integrated Project Delivery (IPD) and Job Order Contracting (JOC).

Key characteristics of these emergent construction delivery methods include: choices based on best value; some form of pricing transparency; early and ongoing information sharing among project stakeholders; appropriate distribution of risk; and some form of financial incentive to drive performance.

Both IPD and JOC allow, if not require, owner cost estimators and project managers to “partner” with contractors, subcontractors, and A/Es to conceptualize, create, cost, prioritize, start, and report upon projects—in the very early phases of construction.

IPD, JOC, and Simplified Acquisition of Base Civil Engineering Requirements (SABER)—the U.S. Air Force term for applying JOC practices—are practiced simultaneously by a growing number of organizations and supported by digital technologies. These construction delivery processes are embedded within software to allow for rapid, cost-effective, and consistent deployment as well as the associated level of collaboration and transparency.

BIM and cloud computing are disruptive technologies that will accelerate the adoption of emergent construction delivery methods such as IPD and JOC. Construction delivery methods set the tone and level of interaction among project participants and can be viewed as the management process framework. When supported by BIM and cloud computing, the life cycle management of the built environment, and the associated management of big data, can be expected to become commonplace for many construction projects.

Cholakis

Cholakis is chief marketing officer for 4Clicks Solutions, LLC, a Colorado Springs, CO provider of cost estimating and project management software. With expertise in facilities life cycle costs and total cost of ownership in various market segments, he is involved in numerous industry associations and committees including the American Society of Safety Engineers, Association for the Advancement of Cost Engineering, Society of American Military Engineers, BIM Library Committee-National Institute for Building Sciences (NIBS), and National Building Information Model Standard Project Committee.

¹ “The Art of Thinking Outside the Box;” Vince Duobinis; 2008.

BIM for FM – What is COBie – A Section of Roadmap for Life-cycle Management of the Built Environment

(Source:A report for the Government Construction Client Group Building Information Modelling (BIM) Working Party Strategy Paper March 2011)

via http://www.4Clicks.com – Premier technology solutions for cost estimating and efficient project delivery method implementation – JOC, SABER, IPD, IDIQ, SATOC, MATOC, MACC, POCA, BOA …

What is COBie?

COBie is a vehicle for sharing predominantly non-graphic data about a facility. The primary motivation for the use of COBie is to ensure that the Client as Owner, Operator and Occupier receives the information about the facility in as complete and as useful form as possible. Wherever possible, data should be recorded within COBie. The COBie dataset can additionally act as a guided index to the supplementary documentation, including 2D and 3D information.

 COBie2  was created to provide a means for the faculties industry to communicate information about facilities so that the client can immediately take full and responsible ownership.  It arose from the collaboration of the US Department of State, US Army Corps of Engineers, NASA, and the Veterans Association. In 2008 it was revised as COBie to ensure that it was relevant to facilities  worldwide  and  was  fully  compatible  with  international  standards  for  data  and classification. Adopters of the COBie approach also include public and private owners, University of Indiana, University Southern California, in the UK Vinci Construction Ltd, and in Germany, The State of Bavaria.

 COBie is a non-proprietary format based on a multiple page spread sheet. It is designed to be easily managed by organisations of any size and at any level of IT capability, allowing each of them to contribute efficiently to a single representation of the asset. It requires only information that is (or should be) available anyway, so it does not represent a change in the expected content, only in its usefulness and accessibility. The intent is to not create information that is not already available or produced as part of the existing processes. The aim is to structure and rationalise the information for re-purposing and use downstream.   COBie also acts as an index to other documents. Overall COBie provides traceability and visibility of design, construction and handover decisions to all supply and client side stakeholders.

 

COBie is used for communication, as a means of information exchange between parties, particularly to the customer.  Where automation is not in use, such as in the lower tiers of the supply chain, COBie information can be captured using direct entry into the spread sheet, often using cut-and-paste from existing schedules and documents. Parties including the client can use the COBie format as a primary document for managing the asset. Design development, construction management and asset management applications have had no difficulty in interfacing with the format.

 

COBie comprises sheets that document the facility, the levels (or sectors), spaces and zones that make up the function of the facility. These are then filled with the actual manageable systems and assets and details of their product types.  During construction and installation these are amplified with information about the spares, warranties, and maintenance requirements. Throughout the process additional attributes, issues and documents can be associated to all these items.

 

2 COBie (Construction Operations Building information exchange) was developed by a number of US public agencies to improve the handover process to building owner-operators.

 

 

 

COBie data is accumulated throughout the life cycle

COBie transfers the information needed by the owner/operator to manage their asset efficiently. The principal use-case is therefore the handover of a facility after commissioning of the owner/operator. Typical questions answered by COBie include:

• What is the design performance of my asset? Energy, rental, quality measures,

• What is the amount of floor space of estate? Classified by building type.

• What is the occupancy level of my estate/per building?

• What is the required plant and equipment maintenance scheduling – preventative and reactive?

• What is my operational cost expected to be?
• What is my as-designed energy use cost expected to be? What is my actual energy use? The  use of

COBie in practice has shown that it is not limited and has a more general role of communicating the key information in a structured format. COBie has been found to be useful and efficient in many scenarios, including documenting existing facilities.

1.  The handover of a facility to the owner/operator.

2.  The capture of commissioning and survey information.

3.  The reporting of the designed project ready for tendering.

4.  The coordination of maintenance records of existing infrastructure.

5.  The documentation of issues discovered throughout the life cycle.

6.  The delivery of product data.

7.  The reporting of design intent at the early design stage.

8.  The comparison of briefing requirements against the designed and as built

COBie documents the asset in 16 consistent and linked sheets

We anticipate that our application of COBie will develop as the various technologies in the market mature, broadly in line with our “maturity levels model” described in appendix 3. For the majority of the five years of the life of this strategy we anticipate that most of the market will be engaged in or around level 2.  For all deliveries at this level, COBie will be adequate as a transport mechanism but may well require additional development to cope with additional attached data, which some clients may start to wish for collection. There will also be a need to have a more robust system for processing the information as our understanding and needs grow.    For this reason we have identified a stage where we would hold all delivered data in a database to enable these processes. This will need additional guidance as there would be a need to synchronise data, COBie, calculations and proprietary information at the same point in time.

 Our final vision for the delivery of this information will be a fully web enabled transparent (to the user) scenario, based on the Building Smart IFC/IDM and IFD standards.

The model below illustrates this progression, with respect to maturity level.

Why BIM is in trouble.

Read this post and please comment.  It is part of discussion on linked-in.  To me it is very telling of the educational and cultural issues that are preventing the widespread adoption of BIM.

I still don’t understand what FM has to do with it. As architects we get enormous benefits from using BIM, from being able to do more complicated and therefore better designed buildings to doing more with less staff. Engineers can do the same.  Contractors benefit from accurate documents and schedules, and more certainty over clash detection. All this can be done with NO consideration of FM.
So “BIM can not be leveraged without the input and consideration of FM” is simply not true, and a great misunderstanding in the AEC industry.

So, the author believes that BIM can be practiced without the input and consideration of FM?  I think NOT.   Certainly components of BIM can be practiced separately, with the ultimate goal of integration.  That said, the above statement not only shows a lack of understanding of the meaning and major value of BIM, but also demonstrates a lack of appreciation for the role of FM professionals.

It is my hope that organizations like IFMA, APPA, NIBS, buildingSMART, CEFPI, et al, rapidly address the pervasive lack of understanding relative to FM.  Failure to address this core issue stands to place BIM in silos…. exactly what we all don’t need.

BIM vs Information Silos

 BIM is not about software or technology but about CULTURE CHANGE and CHANGE MANAGEMENT.

BIM is about simplifying and adding visibility to the life-cycle management of the built environment.  You are either “on-board” or “not”.  It’s up to you.

BIM and FM are synonymous.  Unfortunately there are very few instances of BIM.

The biggest mistake made by most people new to BIM is to assume that BIM is all about technology, and so focus all their efforts on mastering the technology rather than considering the impact that the application of this technology will have on the processes among Owners, AEs, Contractors, Subs, Business Product and Service Providers.

IFMA BIM Lifecycle Operations Community of Practice (BIMLO COP) Kickoff Meeting Video – http://www.gosee.tv/bimlco/

BIM requirements:

1. Organizational Commitment
2. Collaborative, Efficient Project Delivery Methods (IPD- Integrated Project Delivery, JOC – Job Order Contracting …)
3. Standards (OMNICLASS, COBie, IFC), Common Terms, Definitions, Metrics, Cost Data (Standardized Cost Data, example-RSMeans)
4.  Life-cycle Information
5.  Open digital technology supporting the above
6.  Continuous Training and Improvement

via http://www.4Clicks.com – Premier software and services for construction cost estimating and efficient project delivery – IPD, JOC, SABER, IDIQ, SATOC, MATOC, MACC, POCA, BOA…featuring the best representation of RSMeans Cost Data, exclusively enhanced 400,000 line item database.

BIG DATA, BIM, Life-cycle Management of the Built Environment

BIM for Owners = BIM for FM, Building Information Modeling for Facility Managment

Ok, so we get that 3D visualization is a component of BIM.  Design concepts can be beautifully illustrated, and one can relatively easily make a change to the model and the output documents update. Clash detection and the ability to eliminate clashes prior to the construction work starting is also a big “plus” for BIM.  Now it is time to focus on the information in BIM.

It’s time to focus on the true value of BIM for Owners (as well as Contractors, Oversight Groups, the general Community, etc.), the efficient life-cycle management of the built environment.

There are major challenges to attaining BIM, the most significant being change management.  For example, the traditional culture of the AECOO sector (Architecture, Engineering, Construction, Operations, Owner) has been based upon adversarial, non-collaborative ways of conducting day to day business.  As a result, sharing information, consistency, and standardized efficient practices have been difficult at best.

Cloud computing, as well as major market drivers may force change.   That said, when information   becomes more widespread, what standards will it be authored to?  How are things and/or objects defined?  How and when will information be updated?  What specifics and/or parameters are required to define or redefined and object.  For example take a door -  physical configuration (accessibility, dimensions, weight, materials, manufacturer, year built/age), functional aspects(acoustic rating, fire rating, thermal transmittance, security, self-closing, condition, cost, replacement cost, life-cycle), maintenance requirements, warranties?

Also the above, and more, must be considered for the “I” in BIM, in order to fulfill the definition of BIM.

A shared digital representation of physical and functional
characteristics of any built object including buildings,
bridges, roads, process plants etc. forming a reliable basis
for decisions. – ISO

Building Information Modelling (BIM) is the process of generating and managing data about the building, during its life cycle. Typically BIM uses three-dimensional, real-time, dynamic building modelling software to increase productivity in the design and construction stages. – NBS

Building Information Modelling (BIM) is a new approach to being able to describe and display the information required for the design, construction and operation of constructed facilities. It is able to bring together the different threads of information used in construction into a single operating environment thus reducing, and often eliminating, the need for the many different types of paper document currently in use. To use BIM effectively however, and for the benefits of its use to be released, the quality of communication between the different participants in the construction process needs to be improved.
If the information needed is available when it is needed, and the quality of that information is appropriate, then the construction process can be improved. For this to happen, there must be a common understanding of building processes and of the information that is needed for and results from their execution. The Industry Foundation Classes (IFC) provides a comprehensive reference to the totality of information within the lifecycle of a constructed facility. It has been created as an integrated whole in response to the identification of business needs expressed by the international building construction community. It does not contain a comprehensive reference to individual processes within building construction.
The case for a comprehensive reference to processes in building construction is clear and compelling. By integrating information with the process, the value of such a reference is greatly enhanced and it becomes a key tool in really delivering the benefits of BIM.  – buildingSMART, NIBS

The future of BIM modeling is to expand the information model to include more of the life cycle phases (ie: real property commerce, maintenance and operations, environmental simulation, etc.), to standardize life cycle process definitions and associated exchanges of information, and to standardize information content so that meanings and granularity are clear and consistent. This expanded scope definition will make BIM useful to a wider community including, for example, real property managers, appraisers, brokers, mortgage bankers, facility assessors, facility managers, maintenance and operations engineers, safety and security personnel as incident responders, landscape architects, infrastructure engineers and operators, and others outside the business verticals associated with new building design and construction. – BIM Initiative – NIBS

BIM in US lagging UK

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

 

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

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.

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

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

1. 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.
2. 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.

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

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

1. Note Similar to the “Type” construct as defined in ISO 10303-11.
2. 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.

1. Note Similar to the “Select” construct as defined in ISO 10303-11.
2. 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.

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

actor

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

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

1. Note A specialization of the general term control.

control

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

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

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

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

1. Note Similar to “object”, “instance”, “individual” in other publications.

object type

Common characteristics shared by multiple object-occurrences.

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

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

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

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

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

proxy

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

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

1. Note a specialization of the general term object.
2. 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.

1. 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:
<mvd:ConceptTemplate uuid="02eefcc6-b26c-4f20-9c7c-c30ae74eb9a9" name="Aggregation" applicableSchema="IFC4" applicableEntities="IfcObjectDefinition">
<mvd:Definitions>
<mvd:Definition>
<mvd:Body>The object may be aggregated into components using IfcRelAggregates where RelatingObject refers to the enclosing object and RelatedObjects contains one or more components.]]</mvd:Body>
</mvd:Definition>
</mvd:Definitions>
<mvd:Rules>
<mvd:AttributeRule AttributeName="IsDecomposedBy">
<mvd:EntityRules>
<mvd:EntityRule EntityName="IfcRelAggregates">
<mvd:AttributeRules>
<mvd:AttributeRule AttributeName="RelatedObjects" CardinalityTypeEnum="OneToMany" RuleID="RelatedObjects" />
</mvd:AttributeRules>
</mvd:EntityRule>
</mvd:EntityRules>
</mvd:AttributeRule>
</mvd:Rules>
</mvd:ConceptTemplate>


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.
<mvd:ConceptRoot uuid="3a75b425-a9fb-47a3-88ed-9ab3149d7263" name="Site" applicableRootEntity="IfcSite">
<mvd:Definitions>
<mvd:Definition>
<mvd:Body>A site is a defined area of land, possibly covered with water, on which the project construction is to be completed.</mvd:Body>
</mvd:Definition>
</mvd:Definitions>
<mvd:Concepts>
<mvd:ConceptLeafNode uuid="8a3e49b3-f8f7-4734-9b1f-3388442cc49b" name="Aggregation">
<mvd:Template ref="02eefcc6-b26c-4f20-9c7c-c30ae74eb9a9"/>
<mvd:Definitions>
<mvd:Definition>
<mvd:Body>A site may contain zero, one or more buildings.</mvd:Body>
</mvd:Definition>
</mvd:Definitions>
<mvd:Requirements>
<mvd:Requirement applicability="export" requirement="mandatory" exchangeRequirement="00000003-0001-4ac1-b901-da651988243c" />
</mvd:Requirements>
<mvd:Rules>
<mvd:TemplateRule Parameters="RelatedObjects[1:1]=IfcBuilding"/>
</mvd:Rules>
</mvd:ConceptLeafNode>
</mvd:Concepts>
<mvd:ConceptRoot>


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).
<IfcSite>
<IsDecomposedBy>
<IfcRelAggregates>
<RelatedObjects>
<IfcBuilding />
</RelatedObjects>
</IfcRelAggregates>
</IsDecomposedBy>
</IfcSite>


The following data DOES NOT conform to the rule, as it contains multiple buildings.
<IfcSite>
<IsDecomposedBy>
<IfcRelAggregates>
<RelatedObjects>
<IfcBuilding />
<IfcBuilding />
</RelatedObjects>
</IfcRelAggregates>
</IsDecomposedBy>
</IfcSite>


The following data DOES NOT conform to the rule, as it contains the wrong type of object.
<IfcSite>
<IsDecomposedBy>
<IfcRelAggregates>
<RelatedObjects>
<IfcWall />
</RelatedObjects>
</IfcRelAggregates>
</IsDecomposedBy>
</IfcSite>


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.
<IfcSite>
<IsDecomposedBy>
<IfcRelAggregates>
<RelatedObjects>
<IfcBuilding />
<IfcWall />
</RelatedObjects>
</IfcRelAggregates>
</IsDecomposedBy>
</IfcSite>


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


 

 

Who is the recognized “expert” for BIM? For example, if you want to learn about LEED you go to the USGBC. If you want to learn more about BIM where should you go?

The  question, ” Who is the recognized “experts” in BIM? If you want to learn about LEED you go to the USGBC. If you want to learn more about BIM where should you go? “  was recently posted on Linked-In.

While there is no single point source, my best answer, is NIBS/bSa – buildingSMARTalliance.   NIBS/bSa has taken a clear lead in compiling information relative to life-cycle building management…. aka big BIM.

Since life-cycle building management requires several domains of expertise, other organizations/initiatives are also important.  For example,   APPA, NASFA, FFC, and IFMA for facility management aspects,  the real “heart” of BIM.  IFMA is partnering with NIBS to get a “big BIM” effort going.  H APPA, NASFA, and FFC are the places to go relative to “big BIM”  core informational components, strategic business processes, cutting-edge initiatives, etc., while IFMA tends to take a more “broad brush” approach to things.

Cloud technology and efficient cost estimating and project delivery methods (IPD, JOC) are also critical to BIM.  Here take a look at innovative smaller companies including ONUMA and yours truly, 4Clicks, for renovation, repair, sustainability… aka FM.

GIS, BAS are also important components.

Also look at COBIE, OMNICLASS, IFC, and IFD/Data dictionary….   all also important relative to “big BIM”.

” … BIM to me is 10% Technology and 90% Sociology. BIM Technology is the tools that make the BIM Business Practices work, regardless of what portion of the industry you represent. However, if you do not have the right culture / people adopting and implementing BIM, throughout the building lifecyle, the value of BIM will not fully be realized. ” – bSa member

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