To ensure that the facility management functions for buildings—whose data has been imported from BIM models—work properly, these BIM models must meet certain basic requirements. We refer to these requirements as eTASK Model Requirements and abbreviate them as EMA.
Why did we choose the term “eTASK Model Requirements” and not, for example, “Client Information Requirements,” or AIA?
The EMA are requirements for the models (and thus for modelers), just as the AIA are. We used a different term because these are purely technical requirements of the eTASK software that eTASK needs to function properly. eTASK is neither a client in the BIM process, nor are these purely information requirements. Therefore, we decided to use a separate term to avoid further confusion. Of course, the EMAs can be part of the AIA that our customers define for their models if they also want to manage these models with eTASK.
The BIM models are created and maintained by modelers in a wide variety of modeling software systems. For example, our customers currently use systems such as Allplan (Nemetschek), Archicad (Graphisoft), and Revit (Autodesk). However, there are many more systems on the market, and eTASK does not influence the modeling software used by customers.
Modellers export building information models from the modeling software in the open IFC format and then import them into eTASK. To do this, the correct settings must be configured in the IFC export options of the modeling software being used. This allows the geometric and alphanumeric information to be transferred to eTASK and made available there in a unified user interface for CAFM users.
If the necessary settings are not configured, the IFC file may not be able to be imported into eTASK, or relevant information from the model required for executing CAFM processes may be missing.
Only models that meet all eTASK model requirements (EMA) can be imported into eTASK. If a model does not meet one or more EMA requirements during import, it will not be imported or important data will be missing. Users will then see a corresponding message that helps them resolve the errors and attempt a new import.
BIM Model Import Flowchart
To ensure a successful and smooth import, all modelers should be familiar with the EMA requirements and adhere to them during the modeling process in the original modeling software. Questions may arise during this process that must be clarified directly by the modelers with the manufacturer or supplier of the original modeling software.
Existing models may need to be revised before importing into eTASK to ensure they meet all EMA requirements.
The following table lists all current eTASK model requirements. These can be summarized under two main headings:
General Modeling Rules
Export settings in IFC
eTASK Model Requirement | Description | Date |
|---|---|---|
📄 EMA-001: Das Modell muss Standort, Gebäude, Etage und Räume haben IC2650 | The model must include location, building, floor, and rooms | July 4, 2022 |
📄 EMA-002: IFC des Modells muss Basismengen enthalten IC2651 | The model's IFC must contain base quantities | July 5, 2022 |
EMA-003: IFC version | 10/26/2022 | |
EMA-004: IFC file type | 10/26/2022 | |
EMA-005: 2D Top View Elements for Doors | 10/26/2022 | |
EMA-006: IFC file in the correct language | 10/26/2022 | |
📄 EMA-007: Pro Geschoss darf es nur ein IfcBuildingStorey geben IC2662 | EMA-007: There can only be one IfcBuildingStorey per floor | 10/26/2022 |
📄 EMA-008: BIM-Modelle müssen unterschiedliche IFC-GUIDs haben IC2663 | EMA-008: BIM models must have different IFC GUIDs | 10/26/2022 |
📄 EMA-009: IFC-Objekte müssen Anforderungen von kundenspezifischen BIM-Profilen erfüllen IC2664 | EMA-009: IFC objects must meet the requirements of client-specific BIM profiles | 10/26/2022 |
📄 EMA-010: Projektinformationen dürfen keine doppelten Parameter haben IC2665 | EMA-010: Project information must not contain duplicate parameters | 10/26/2022 |
📄 EMA-011: Die IFC-Datei darf nur ein IfcBuilding haben IC9456 | EMA-011: The IFC file may only contain one IfcBuilding | 10/26/2022 |
📄 EMA-012: Gebäude müssen Kostenstelle, Straße, Hausnummer, PLZ & Ort haben IC2667 | EMA-012: Buildings must have a cost center, street, house number, ZIP code, and city | 10/26/2022 |
📄 EMA-013: IFC-Modell darf keine Bruttogrundfläche als Räume beinhalten IC2669 | EMA-013: IFC model must not include gross floor area as rooms | 11/24/2022 |
EMA014 - Each floor (IfcBuildingStorey) must have a defined "Elevation" property value | November 6, 2023 |
The list will be expanded by eTASK as needed, which may result in maintenance work on existing models.
Note: This section contains non-binding tips and tricks that eTASK has learned through customer projects. eTASK employees do not have comprehensive knowledge of how to use the individual modeling tools; often, they do not even have access to these tools. If we cannot provide a tip for your tool here, please contact your vendor/service provider who supplies your modeling tool and ask them what you need to do to comply with this EMA.
Tip: You can find a complete overview of all versions and direct links to the official documentation at: IFC Schema Specifications - buildingSMART Technical