leaDE is versatile!

Here you can find information about the individual functions in the leaDE frontend

Safety first

True to the motto of not reinventing the wheel unnecessarily and using systems that already work, we decided to use Auth0 as the authorization system. This allows us to provide system security that has been perfected over the years and guarantees the highest level of safety. This is where the variability of Auth0 proves useful. This allows you to verify yourself with different accounts.

Configure a project

Simple and complex projects can be mapped in leaDE. These can cascade, meaning they can contain sub-projects, but let’s start simple.

The project configuration is divided into five parts:

1. a project name
First, a name must be given to their project so that everyone is talking about the same thing.

2. a phase definition
First of all, the project phases should now be created. Whether HOAI, SIA, ÖNORM or International: Your decision.

3. specification of the use cases
BIM consists of use cases. No matter how many there are, leaDE supports you.

4. indication of the subprojects
If your project is divided into several subprojects, they will now be created here.

5. inserting the AIA guidelinesspan,
The foundation of your planning provides a guideline.
Here we continue in the next video.

Project setup AIA defaults

leaDE requires a policy that contains AIA parameters. This can be created from BIMQ, BIM profiles from CAFM-Connect or your own profiles.

Thus, information is provided for the respective applicable objects, which leaDE processes.

The project configuration follows. This process is very easy and takes only a few moments.

In the example, a project configuration is created and transferred to the server. Configurations can also be reused for similar projects.

Simple rights management

One of the essential features of leaDE is the administration of rights. From the Home screen, this model makes it easy to set an authorization for each authority role. This role is initially assigned and eventually managed in Auth0 (the authentication system). It is thus possible to assign different roles such as Writer, Reader or Undetermined to different people in different use cases.

This way you always keep control for individual properties.

In the video shown, this process is performed with a mass assignment.

The daily work

Select a project in the viewer

After login we start the viewer and select a project and the use case.

Edit a component

The viewer represents the components of the use case. Then a selected element can be edited in the properties – of course only according to the AIA policy and the set rights.