Attribute mapping

Attribute mapping

In this sub step the attributes that come with the BIM elements can be mapped over to some attributes that are registered in MainManager (and the system therefore knows). This might for example be creation date, type of the element, identification, area, volume, name or other technical information. 

When this sub step is selected the area divides to two. On the left there are all the attributes which exist in the model (selected in the filter) and a number is visible behind each attribute indicating how many BIM elements have this attribute. The left tree is hierarchical. That is, all attributes that belong to the BaseQuantities group, will be grouped under a folder with the name BaseQuantities.

On the right side there is the mapping list registered in MainManager. Mapping of attributes in the BIM model is demanded for at least object type code (Main manager type code*) so it will be possible to create objects in MainManager from the code. It is possible, that for other mapping sets (chosen in the filter), there might be other attributes demanded such as identification, product number and unit. The mapping list on right side is grouped by location attributes, organization attributes and system attributes. 

It is possible to see what elements (in the selected BIM model) have any given attribute. That is done by right clicking an attribute node, in the left tree, and opening <Show elements with attribute>.

Then a list of all elements with this attribute (<GrossArea> in the above example) will be listed up.

What the user does here:

Define a mapping set

First, the BIM project and model needs to be selected in the filter so that the attributes from the model can be viewed on the left side. 

Then the user can look at if some of the existing mapping sets (if any) are fitting the model that this now being processed. Then the mapping set is selected from the filter and then it is shown in the right tree how the mapping is defined for that set. If a model is already connected to a mapping set, then that is automatically selected in the filter. If the user wants to have another mapping set for the BIM model, then the user must open the registration window for the BIM model and change it.

The attributes that belong the BIM models can be very different from one model to another so it is very likely that a new mapping set must be created. That is done by pressing the action menu above the mapping set selection (in the filter), open <Show data in popup list> and then click <Register new mapping>. 

Purpose:

Here it is possible to register a new mapping set. The set is made to define how the attributes that are connected to BIM elements should be converted to some values that MainManager knows and can be used to register information on objects.

To start with, the mapping set is given a name and a number. After that the property box is divided into two sections, one for location element settings and the other for system element settings.

Location element settings

Identification required

Coding for location structure (IfcBuilding, IfcBuildingStorey and IfcSpace) assumes optionally that locator is in an attribute for buildings, floors and spaces. The benefit of registering locators on location elements is for instance if the location structure already exists (partially or fully) in MainManager. Then, the import checks if for instance a building space already exists in MM and if so, does not make a double registration of the same space. An option to this is not to demand a locator in the model, but instead with drag and drop in sub step <Processing of location elements> to connect location BIM elements to existing location structure in MainManager (recommended approach).

It is possible to add ownership to an element. This means that certain locations within the BIM model can be registered to users by for example a social security number.

All symbols are allowed for each of these identifications except the dot (.) sign because in the example above the FM system recognizes the building space uniquely through a combined locator.

An example for site number 3261 the identification for the space could be:

3261.B1.E3.10 (Site 3261, building B1, floor E3, space 10).

Overwrite room name in reimport

If this is checked then room name will be overwritten when updating the location structure (for example when BIM model is re-imported after changes).

Use element name for room number

If this is checked then the name of the BIM element will be used as the room name in MainManager. This applies both when creating rooms or when rooms are being updated.

System element settings.

Start by selecting which type the systems in the model are. Four different kinds of systems are supported:

• SfB (Danish standard)
• CCS (Danish standard)
• NS (Norwegian standard)
• Uniclass (UK standard)

The mapping set also needs to know the format of the type codes. The current allowed code formats are supported:

• SfB type without parentheses (e.g. 332)
• SfB type with parentheses (e.g. (33)2)
• SfB type without parentheses and with product number (e.g. 332.1111)
• SfB type with parentheses and with product number (e.g. (33)2.1111)
• SfB type with parentheses and point (e.g. (33).2)
• SfB type with parentheses, point with product number (e.g. (33).2.1111)
• CCS type without product number (e.g. %AB or % A.AB)
• CCS type with product number (e.g. %AB1111 or %A.AB1111)
• NS TFM code with product number (e.g. +0010=244.001-DI001T)
• Uniclass code
  1. Mapping is done to EF, Pr and Ss numbers specifically

In some cases, the product number is not a part of the type code but is in a separate attribute, then it can be mapped like other attributes.

The mapping set also defines if <Product number> and/or <Quantity unit> is required from BIM model. This is necessary if the data is supposed to be used to calculate environmental impact (EPD).

Drag the attributes of BIM elements over to right MainManager values 

When the mapping set that should be used for this model, has been selected in the filter, it is possible to start defining how the mapping should be. This is done by dragging from left to right or vice versa. To take an example it is possible to drag the attributes from the model on the left over to some node in the mapping list on the right. Many attributes on the left can belong to the same mapping attribute on the right side. Each attribute on the left (from the BIM model) can as well belong to many mapping attributes on the right.

When there are multiple BIM attributes mapped to a single mapping attribute then it is possible to define the priority of each mapping. The priority is attached automatically in the mapping order but it is possible to change it manually by right clicking the mapping node and opening the property box for the mapping. The priority is used in the following manner:

• If mapping has value then higher priority is used
• Else next mapping is used until a mapping has value
• Example (based on below picture): 
  1. LongName mapping has <Priority 1> but does not have any value for building space, then the Name mapping is used

The registration of the mapping set controls which attributes are demanded from the model. It is always required to drag the <MainManager type code> over to some attribute, but there could be other requirements and they will be identified with a star (*) in the right tree.

Additionally, location elements should include additional attributes as defined in the guidelines. An example of attributes is: 

• For building floor
  1. Gross area
  2. Gross volume
• For building space
  1. Net area
  2. Space usage

When doing the mapping the user decides if an attribute should overwrite existing values by left clicking on the mapping node (default is on). For instance, if a room number is already registered on the room in MainManager, the room number is not overwritten when processed from the BIM model unless this checkbox is marked.

Below a description of the various mapping attributes is shown.

Location attributes

• Identification: Mapped to <Locator> in building, building floor and building space registration
• Room number: Mapped to <Usage space number> in building space registration
• Room number 1: Mapped to <Operation space number> in building space registration
• Room number 2: Mapped to <Geographical space number> in building space registration
• Space usage: Mapped to <Space usage> in building space registration. It searches for predefined Space usage name in the MainManager database. If it is not found then nothing is registered.
• Space type: Mapped to <Space type> in building space registration. It searches for predefined Space type name in the MainManager database. If it is not found then nothing is registered.
• Gross area: Mapped to building floors and building spaces
• Net area: Is mapped to <Net area>, <Cleaning area> and <BRA> in building space registration

Organisation attributes

• Object owner identification: An organization that uses (leases) the building space can be connected to the building space through the BIM processing. When that is used, the organization identification must exist in the MainManager database.

System attributes

• Name: If this is mapped, then the BIM element gets this name instead of the usual BIM element name.
• Main manager type code*: As mentioned above, this is the system identification number of the BIM element.
• Product number: As mentioned above, if the product number is not part of the Main manager type code, it is fetched from this attribute.
• Main manager subtype name: If used, this same definition must exist in the subtype definition for the system identification in the MainManager database.

Other mapping attributes are based on the data structure that you are using. For example, if you use the<Date installed> field on <Technical systems>, then it will be possible for you to map any BIM attribute to that mapping attribute.

When working with mapping sets you can see where they are used by opening the registration window and select <BIM models>.

When the mapping has been defined for the model, the process for creating locations and systems can start.