CONSTRUCTION PART CODE - Detailed description

Overview

Parameter:BAUTEILCODE
Category: FL (Space Management)
Default value: 0 (disabled - not taken into account)
Product: eTASK.FM Portal
New in: November 2025 release

What does this parameter do?

This parameter controls whether a building component code is included between the building and floor during room identification. In large building complexes, buildings can be subdivided into multiple building components (e.g., Wing A, New Building, Extension, North Wing). Use this parameter to enable or disable this additional hierarchical level in the room codes.

What is this parameter used for?

• Enabling an additional structural level for complex buildings with multiple building sections

• Management of properties with building wings, wings, or construction phases

• Unique room identification when multiple building components share the same floors

• Structured recording and filtering of rooms by building sections

• Consistent data structure when importing and exporting floor area data

Technical Details (for Administrators)

Format: Numeric value (0 or 1)
Default value: "-" (corresponds to 0 = disabled)

Valid values:

• 0 or "-" = Part code is NOT taken into account (default)

• 1 = Part code IS taken into account

Important notes:

• When the component code is enabled (value 1), an additional level is inserted into the room code

• The room structure expands from "Location-Building-Floor-Room" to "Location-Building-Component-Floor-Room"

• The component is located between the building and the floor

• Subsequent activation requires maintaining components for all affected floors

• Subsequent deactivation can lead to confusion if room codes are already in use

• The setting affects room filters, reports, and import/export functions

Interaction with other parameters:

When COMPONENT_CODE is enabled (value 1), it interacts with the ROOMDELIMITER parameter, which defines the separator for the room code hierarchy.

When should you change this value?

Set the value to 1 (enable component code) if:

• Your property includes large buildings with multiple components, wings, or sections

• A building is divided into multiple construction phases, each with its own floors

• You need a detailed breakdown of the building structure for analyses

• Your facility management concept includes a component level between the building and the floor

• You are migrating data from a system that uses building components

Leave the value set to 0 or "-" (component code deactivated) if:

• Your buildings have a simple structure without subdivision into building components

• The location, building, floor, and room levels are sufficient for your requirements

• You want to keep data maintenance as simple as possible

• There is no need for a component hierarchy

Important Notes

1. Change only before data maintenance
   Ideally, activate this parameter during project setup, before extensive room data is entered. Activating it later requires subsequent maintenance of building components for all floors.

2. Impact on data structure
   Activation adds an additional hierarchy level in the room code between building and floor.

3. Deactivate with caution
   If you deactivate the parameter after using component codes, the recorded component code information is not lost but is no longer displayed.

4. Consistent maintenance required
   When the component code is activated, you must maintain components for all relevant floors, even if some buildings have no components (in which case, for example, use the dummy value "-" or "00").

Security

Does changing this parameter affect security?

No, changing this parameter has no direct impact on security. It is a structural configuration of the room hierarchy.

Practical example

Initial situation: Your company operates a large administrative building divided into three wings (North, South, East). Each wing has its own floors (Ground Floor, 1st Floor, 2nd Floor, etc.). Without components, you cannot distinguish whether Floor 01 is located in the North, South, or East wing.

Configuration: COMPONENT_CODE = 1 (enabled)

After the change:

• Location: "HQ" (Headquarters)

• Building: "VW" (Administration)

• Building: "N" (North Wing) / "S" (South Wing) / "O" (East Wing)

• Floor: "01" (Ground Floor)

• Room: "101"

Result: You can now clearly distinguish between:
- Room HQ-VW-N-01-101 (North Wing, Ground Floor, Room 101)
- Room HQ-VW-S-01-101 (South Wing, Ground Floor, Room 101)
- Room HQ-VW-O-01-101 (East Wing, Ground Floor, Room 101)

Filters such as "all rooms in the North Wing" work without issues using HQ-VW-N--. Filters such as "all ground floor rooms in the South Wing" use HQ-VW-S-01-*. The filter for “all ground floor rooms” works with HG-VW-?-01.

Alternative scenarios:

Scenario A - Without component code (value 0):

• Simpler structure: HQ-VW-01-101

• Problem: No distinction between components possible

• Solution: Use different floor codes (N01, S01, O01)

Scenario B - Mixed use:

• Existing building without components: HQ-AB-00-01-101 (dummy component "00", ground floor, room 101)

• New building with components: HQ-NB-A-01-101 (New building, Wing A, Ground Floor, Room 101)

Recommended setting

For standard installations:0(disabled)

Reason:

• Simpler data structure for most use cases

• Less maintenance effort for room data entry

• Sufficient for buildings without subdivision into building components

• Lower risk of errors during data maintenance

Recommended for:

• Large buildings with multiple wings, sections, or construction phases

• Complex building structures that require a breakdown between building and floor

• Requirements from corporate standards or migration from legacy systems

• Each building component has its own floors that must be distinguished

Tip: Analyze your building structure before making a decision. If you are unsure, start without a building component code (value 0). Activation at a later date is possible, but requires subsequent data maintenance. Deactivation at a later date is more problematic.