Geometric Requirements in Specifications

The catalogs & specifications on LastBIM already take care of information requirements. A logical next step would be to make it possible to also add geometric informations (images + text) to specifications. This geometric information could then be viewed on the platform, viewed directly inside our plugins for authoring softwares and also be included in some of our exports.

Ensure compatibility of IFC classes and IFC properties in specifications

Currently, users can add every IFC standard property to every specification regardless of the IFC entity of the specification, meaning you could add the property "ExtendToStructure" (PsetWallCommon) to an IfcBoiler which would not be schema conform. Option 1: When adding a property to a specification, filter the IFC catalog for properties that match the IFC entity of the specification - if the specification is mapped on an IFC entity Option 2: Show a warning in the property table of the specification, when the property that is mapped on an IFC schema property does not match the IFC classification of the specification. This would help to use the IFC standard correctly in your catalog and avoid assignments that are not intended by the schema.

IFC Model Cleanup

The LastBIM catalogs already contain clear requirements for the information to be included in delivered IFC models. However, many authoring software programs produce far more alphanumeric information than is actually required. It would be possible to provide an 'IFC Model Cleanup' tool that filters out all properties not required by the current project stage (information level).

Assign default information levels to properties (not in specification)

Often, it's sufficient to define the information levels on the properties independently from the specification. For this, it should be possible to define default information levels on the properties once, instead of going through all the specifications and defining them there for every specification individually.

Scripting / automations for attribution

Allow user to create own scripts to automate the attribution. This could come in form of… Option 1: a node editor similar to Dynamo for Revit Option 2: a code editor similar to the scripts in Desite Let us know which option you prefer!

Assign properties to specifications via the property settings instead in the specification

Work from the property overview instead from the specifications to assign properties to specifications. You can use this feature to add one property to different specifications at once.

Improved Property Values

Currently the property values are simple lists of values, but often additional information like a description or tags on the values, would help the user in choosing the right value. This feature will add: A way to edit existing property values (this will also update all references to the value everywhere) Support for tags on property values (which will also enable you to filter out values in the plugin / IDS export) An optional description for each property value, to give the user additional information during the attribution.

Data Templates for Specifications

Often elements are partially filled with the same information. With data templates it would be possible to save and edit a template of property values for a specification on the platform or inside the plugins. During attribution, in our plugins or IFC-Studio, these templates could then be applied to the selected elements in a single click. This could further speed-up the attribution process, especially for data which is reoccurring. To make it easier to create data templates, they could be created directly from the plugin from already filled-out elements.

Rules for property names and values for consistency

Having a consistent spelling and naming characterizes a high quality catalog. By defining rules for property names and values, you can e.g. specify whether umlauts are allowed or should be written out in full ("ae", "oe", "ue").

Archicad Integration

The integration for Archicad will support the attribution process within Archicad similar to the plugin for Revit. It will help with the managing of the properties, filling in the relevant values and checking if anything was missed.

Dynamic Selections & Filters

Getting the right elements selected in models is sometimes harder than it should be. We already have all necessary information on LastBIM to make selecting & filtering faster in all software for which we offer plugins. What kind of selections and filters will you be able to access? A history of the your last N selections Dynamic filters by specifications and properties. Examples would be: Select all Wall & Window elements in a model Select all elements with isExternal = true Select all Wall elements which also are Reinforced Concrete elements Select all elements where the property storey > 1 What will you be able to do with the selections and filters? Show / Hide / Focus => Show / Hide / Focus all elements in the selection / filter Color => Assign one of our predefined colors to all element in the selection / filter Validate => Run our validation only on the selection / filter Attribute => Add missing attributes to all elements in the selection / filter Our main goal here is to speed up the interactions with the authoring software to save time during attribution & quality checks.

Cross-Catalog Property Mappings

When two or more parties are working together on LastBIM and have their own catalogs, you might want to map them on each other. E.g. the BIM management provides a catalog with the properties that are required for this project. The planners have their own standard. The planners want to map the the properties required of the BIM management on their own properties, to work e.g. in Revit as usual and only add properties that are not covered by their own catalog. While you can already define how a required property is handled in Revit, this feature would allow you to map the properties of two catalogs at once, by selecting the corresponding property from the other catalog.

Catalog Versions

Catalogs which are used in multiple projects are often used with different "version" at the same time. Currently with LastBIM you can always only use the latest version of a catalog (for attribution, IDS-Export…). With catalog versions you'll be able to freeze a catalog and assign a specific version name to it. Then users will be able clone, view, export and attribute with the frozen catalog version, while you work on on the latest version of the catalog.

Document Requirements

Should work similar to specification properties Specify which elements / specifications need to have specific documents linked Specify in which information levels / phases of the project the documents are needed, equal to the checkbox loin management of the properties Central list of required documents Documents are inherited, just like properties Each document can have the following metadata attached Name Description (optional) File Format (optional) Tags according to tag groups

Comments & Threads on Catalog Content

Sometimes property and component requirements need to be discussed. While currently these discussions happen in regular communication tools (Teams, Slack, …) they often provide great context for the requirements. With this feature it will be possible to: Leave comments on properties & specifications Reply to comments to start a thread about a specific topic Resolve a thread once all questions have been cleared View all discussions in a central page in the catalog / project

Plugin Data-Sync

Import, export, save and synchronize data from and into your models via the plugins (and IFC-Studio). Workflows covered by this feature: Change data in an IFC-Model (e.g. Desite / IFC-Studio) and synchronize the changes back into your native model (for example Revit). Export data (on its own or with validation results), hand it off to a third party and re-import the data after it has been updated into your model. Bulk edit data in your model via tables. Possible adjacent future workflows: Request data-changes from third-parties via a web user interface. Create a selection in your model and request-data for a all (or a subset) of its properties. Share a link with a third-party, which can then fill out the requested data in a view similar to our plugin. If the model is in IFC and uploaded, it'd be possible to highlight the elements

Filter Options for Excel Export of Requirements

Filter options for: Domains Tags Information Levels -> E.g. get one Excel file for every domain so that everyone only receives the requirements that apply to them.

Excel Import of Catalogs

In most projects and companies, some information requirements already exist in the form of an Excel file. With the import function, you can transfer these requirements to the platform automatically, so you do not have to enter everything manually. We try to make the import process as flexible as possible, so you are not restricted to using a very specific format dictated by us.

IFC Studio

In LastBIM 1.0 we had an IFC Studio which made it possible to edit smaller IFC files directly inside the browser with all functionalities our plugins had to offer. We're currently waiting for an update of an external software-component we're using to implement the IFC Studio. Once that took place we'll reimplement the previous functionality we had, while also supporting way larger models than before. What will be new inside the IFC-Studio? Better performance with larger IFC files. Better model navigation - e.g. with the IFC tree. What was already possible in the old IFC-Studio? Validate the model against the selected requirements. Attribute the model based on the requirements. View the model and all of the data inside.

Bulk Edit of Properties & Specifications

The bulk edit feature allows you to select multiple specifications or properties and edit the following information for all of them simultaneously: Specifications: Parent Specification Domain Tags Deletion Properties: Data Type Domain Property Set Tags Deletion

Manage project information in Revit with LastBIM

Not only objects need properties, also the project itself usually gets some general information on project level. By managing the project information also via LastBIM you can manage all your information in one place.

Export validation results as BCF

Export validation results as Excel

Exporting the validation results as Excel will give you a comprehensive tabular overview of the status of the attribution in the model. The Excel format allows you to bring the data in any form that you need, e.g. to create diagrams or to analyse it with Power BI.

Auto-Narrow Property Values for Classifying Properties

Hierarchical specification trees often require to narrow down the value of classifying property values to a subset which is equal to the child-specifications of the parent. Example Classifying Properties: ID-1, ID-2 Specification Hierarchy Wall [ ID-1: Wall] Interior Wall [ ID-2: Interior_Wall ] Exterior Wall [ ID-2: Exterior_Wall ] Door [ ID-1: Door] Two-Wing Door [ ID-2: TwoWingDoor ] Single-Wing Door [ ID-2: SingleWingDoor ] In this example ID-2 can have 4 different values, but if the specification is Wall the values of ID-2 would automatically be narrowed down the Interior_Wall & Exterior_Wall.

IFC Attribute Support

Define requirements for the IFC attributes like “Name” and “Description”, that don’t live in property sets but are built into the IFC schema itself. Next to defining the requirements, it will be possible to check these requirements in the IFC studio and to edit the attributes with the Revit plugin (limited to the attributes that can be overwritten in Revit).

Microsoft Login (EntraID)

Log into LastBIM without any additional credentials and use your already existing Microsoft Account.

Tags in Catalogs

Often content in a catalog must be separated for different use-cases, projects or stakeholders. By offering tags we want to make it possible to add custom metadata to specifications and properties, which can be used to filter and organize your catalogs. Some use-cases for tags would be: Tag your specifications and properties with a custom typology to differentiate between different project kinds (hospital, infrastructure, etc.) Tag your properties with a status to mark which properties are ready to use and which are still work in progress.