DigiPara – El formato de archivo LDBIM admite ahora el nivel de información (LOI) que necesita el arquitecto


DigiPara Liftdesigner 2020 comes with strong improved BIM features. Major enhancements also happened to the DigiPara LDBIM file format. It has been improved to support Level of Information (LOI) which is needed by the architect. New is also the option to load the LDBIM file into a Revit Family (*.rfa).

LOI: Perfect BIM Properties

Select BIM Properties from predefined property sets like COBie and IFC4.

Many of the properties are preconfigured: For example, values like door width and door height are automatically filled in.

If the BIM execution plan requires specific BIM property names, these can easily be added on a per project basis. This allows to complete the BIM model in DigiPara Liftdesigner before it gets exported as IFC.

Image: Determine which elevator component types require BIM properties

The LDBIM file

When the LDBIM file is exported from DigiPara Liftdesigner it contains all BIM Properties as defined in the project file.

The Level of Development (LOD) for LDBIM and IFC is determined by the content of the current view frame. Predefined sheet templates help to comfortably select the desired LOD.

Image: All elevator components like doors contain the required Level of Information (LOI)

Autodesk Revit: DigiPara Elevatorarchitect Update required

On the Autodesk Revit side, the LDBIM file will be imported by the free DigiPara Elevatorarchitect Plugin. Make sure you update the Plugin

The new LOI functionality is available for Autodesk Revit 2017 and later. Earlier Version can also import the LDBIM file, but the LOI will not be available.

Image: Make sure you have a product version 20.0.213 or higher. You may use “Force Update” to execute the update next time.

LOI: Shared Instance and Type Parameters

All parameters shown in DigiPara Liftdesigner are also available in Autodesk Revit. The parameters are all Shared Parameters, making sure that these can be properly scheduled with other elements in the building.

The parameters are defined as Instance parameters, in case the parameter is different at each component (like a builder ID code). If the parameter value is same, e.g. the door width for all front doors of one elevator, a shared type parameter is used.

Image: LOI is automatically filled in shared Instance and Type parameter.

LDBIM: Import the file into a Revit family (rfa)

A new feature of DigiPara Elevatorarchitect is, that the LDBIM file can be imported into a new revit family file (.rfa).

The architect requires a Revit Family file

Frequently architects request a Revit family file from the elevator company. The best process is to send the LDBIM file, and the architect imports it himself. Unfortunately, some of them have no permission (from a company policy perspective) to install DigiPara Elevatorarchitect, even it is a free tool.

In this case the elevator company can create a new family file in Revit and import the LDBIM file. Finally, you share the completed family file (*.rfa) with the architect.

IFC 4.0 might also be an option

In case your architect does not use Autodesk Revit, you might also consider to send an IFC 4.0 file. Read this interesting article: “DigiPara Liftdesigner 2020 with groundbreaking new BIM features“

Image: LDBIM file imported into a Revit family defintion file. The first floor is aligned to the base level

Autodesk Revit Version:
Make sure you use the same or lower Revit version as your architect uses, otherwise the architect can not open it.

Important installation note:

If you want to use the feature, and you had a previous version installed, you must uninstall the previous package from the control panel first. Then install the latest setup from this page “DigiPara Elevatorarchitect“.

Important feature note:

At this time, the LDBIM was successfully imported into the Revit family, but some warnings in DigiPara Elevatorarchitect were shown up, and finally the LOI was not added. We talked to the DigiPara Development team and a DigiPara Elevatorarchitect fix for that is expected in Autumn 2019.