Skip to main content
Cartegraph Campus

Set Building and Floor Asset Management Properties

You must have administrator rights to access this feature.

Every standard and custom asset type can be managed by per building and floor. The Building Context field has four values and each value triggers a set of actions:

  • None: no structure changes or asset relationships are created.
  • Building: These assets can be containers to floor assets. 
  • Floor: When set to floor the recordset, the Floor Name, Level, and Building fields are automatically added and the floor can become a container to Floor Aware assets and a component of a Building asset.
  • Floor Aware: This indicates an asset that is placed on a specific floor and can be set as a container to the floor asset. The Floor and Building fields are automatically added to the recordset.

 For example, the Facility domain uses the Building Context field like this:


The Building Context value can be edited in Structure Manager and is located in the Properties General section. When changing the building context, the Floor and Building fields are automatically recalculated and populated if the asset is part of a container/component relationship. 

If a recordset has existing fields with the same name as any of the above fields, then an error message displays letting you know that you must rename existing fields before changing the Building Context value.

Conflict Errors

When Cartegraph cannot determine a Floor asset's Building value or a Floor Aware asset's Building or Floor value, an error tile displays next to the Building selector. Click on the tile to review the message.


The message displays a list of records with conflicts or problems in the container/component hierarchy. Here are some examples of conflicts:

Assets with a Building Context of Floor can only be a component of one asset with a Building Context of Building anywhere in its container/component hierarchy. This can happen when the Floor or any asset above it in the hierarchy is a component of more than one Building assets. For example, if Building A has Floor A as a component below it, Building B cannot also have Floor A as a component, or else there is a conflict.

Assets with a Building Context value of Floor Aware could have similar conflicts if they have either two different Building records or two different Floor records in their hierarchy.

To resolve a conflict, make sure that each Floor is a component to one Building and each Floor Aware asset is a component to one Floor, and that Floor is a component of one Building. To add a new Container relationship, the existing connection to the Building, Floor, or Floor Aware Container must first be removed. See this for more information on removing container connections.

Container/Component Edit Error

As you edit container/component relationships the system checks for and prevents hierarchy conflicts. An error message displays if an asset breaks this rule; at any time, an asset may only be a component of one container with a Building Context of Building, Floor, or Floor Aware. For example, if you are trying to relate the HVAC Equipment A record as a component to a container called City Facility Floor 1, but HVAC Equipment A is already related to City Facility. The following message would display:

Cannot Edit the HVAC Equipment

HVAC Equipment A is already related to another container. If you want to make this connection, you must first change the existing container connection.

To resolve the issue, first break the relationship between HVAC Equipment A and City Facility. Then you can make create a relationship where City Facility Floor 1 is the container for HVAC Equipment 1.