Qonic Talks Gent 2025

[Barbra]

Recap: Qonic Talks Gent 2025

Last week, we gathered again in the heart of Ghent for a new edition of Qonic Talks. And yes, with the live demos you’ve come to expect from us. Because we don’t just talk about features, we show them!

This was Qonic Talks Gent 2025

Hosted at the beautiful Oude Vismijn, the event brought together a group of engaged AEC professionals. We took the opportunity to dive deeper: not just into what Qonic does, but how it’s evolving and how we’re tackling real-world pain points with practical, intelligent solutions.

What is & What’s next

Performance

The speed of Qonic has always been a differentiator and it’s only getting better. We showcased Qonic’s smooth navigation, the fast model loading and large scalable project handling.

Collaboration

From multi-user workflows to version comparison and issue tracking, we demonstrated how Qonic supports truly collaborative delivery. Jacob, Dieter and Jürgen showed how teams can now coordinate directly within Qonic from any device using:

• Real-time clash detection

• Intuitive issue tracking

• Version history & compare to manage evolving models

• Multi-user editing that doesn’t break your model or your process

Data & Geometry editing

Editing in Qonic is quick and flexible. We showed how you can make changes smoothly, even when working on complex, detailed models.

Modelling

With this release, Qonic takes a real step forward as a modelling tool. During the demo, we showed new features like filleting, smarter snapping, and more control over how you shape and adjust geometry.

What makes Qonic stand out is our focus on keeping things intuitive.
Instead of adding loads of separate commands, we’re making sure the same tools can be used in different ways. So you can push, pull, extend or reshape depending on what you’re doing. That keeps things fast, flexible and easy to learn.

Turning models into actionable output

Then we focussed on what comes after the model:

• More powerful quantities and reporting tools

• A preview of 2D drawing generation under development

• A preview of 4D planning features under development

This is where Qonic really shows its strength across the full project lifecycle.

Interoperability

Working across platforms is no longer a nice-to-have, we know it’s essential. We shared exciting progress on:

• SketchUp and Rhino imports

• Improved Revit interoperability

API & Plugins

Tiemen introduced the possibilities of building on top of Qonic. The API is opening up new doors for custom integrations such as a Power BI dashboard for visual project insights. But this also works for your own Excel plugin to connect familiar workflows to Qonic’s structured data. Whether you’re scripting something in Python , building a full C# application or automating tasks across tools, the flexibility is there.

Honest conversations, real interest

Throughout the session and especially during the Q&A, we were impressed by the depth of the questions. Attendees didn’t just want to see features. They wanted to understand how Qonic fits into their existing workflows, how the API could support automation and how we’re preparing for larger-scale collaboration.

This level of engagement tells us one thing clearly: our industry is ready for change and eager to build smarter.

Looking Ahead

In the final summary, Mark reiterated our mission: to remove the constraints of traditional BIM tools and build something that actually supports the full lifecycle of a building project.

Qonic Talks Gent was an energising moment for our team. Thank you to everyone who joined us and helped make this a meaningful afternoon. Your ideas and questions inspire what we do next. Let’s keep the conversation going.

Curious about what Qonic can do? Watch now the What is Qonic webinar!

[Barbra]

Below are some of the questions that were asked during the Q&A.

Company & Training
What does the Qonic logo stand for?
It’s threefold: a geometric base shape (the cone – hence the name Qonic), a nod to the iconic cuberdons from Ghent, and a reference to the city’s three medieval towers.
When will you organise a Qonic modelling training session?
We don’t have any concrete plans yet, but if there’s enough interest, we’ll definitely look into it.

Data & IFC Management
IFC Compatibility: Questions around supported IFC versions and data structure flexibility.
Data Enhancement: Interest in enriching or correcting IFC data, including quantity takeoff and metadata use.
Can objects be automatically linked to rooms, even if the IFC doesn’t include that relationship?
Not yet but this fits perfectly with our philosophy of driving automation based on geometric information. Definitely something we’re exploring!

Core Platform Features
Will Qonic support the Model Context Protocol for connecting AI/LLM tools?
This is actively in development and expected to be available in the short to medium term.
Which languages is Qonic available in?
Currently only in English.
Can I assign custom keyboard shortcuts?
Not at the moment. We are planning to add shortcuts for the most commonly used tools.
What’s the status of reality capture in Qonic – e.g. modelling from a point cloud?
Still in early development. We have the in-house expertise, but it’s a major task, so no concrete release timeline just yet.
Can objects be renumbered smartly – for example, by floor level or other logic?
Not natively in the Qonic interface, but this can easily be handled through our API. You could write a Python script or use our Excel plugin to manage numbering and send the updates back to Qonic.

Interoperability
Are there plans to integrate with mechanical design tools like SolidWorks or Inventor, or import STEP files?
No concrete plans yet, but if there’s enough demand, we’ll explore it. Since STEP is the base geometry format for IFC, direct STEP import would be quite feasible.
Software Integration: Interest in compatibility with mechanical CAD, GIS and BIM tools.

Collaboration & Version Control
Is there a backup system in case of a crash before changes are published?
All work happens in the cloud, so you won’t lose progress. If Qonic crashes, your personal draft version still exists, even if it hasn’t been published yet.
Can I generate an overview of changes made by users who aren’t responsible for those objects?
Technically, yes. We track all changes per object in the backend. There’s no user interface for it yet, but a detailed change log is possible.
Is there a “fork” option to start exploring design alternatives like in Git?
Not yet. The current version history is a simplified version. Forks, branches, and review workflows are definitely on our roadmap as demand grows.

Model Coordination
If a clash is acceptable (e.g. a pipe through a foundation beam), can it be ignored permanently?
Currently no, the clash detection tool is still in its first version. More advanced filtering and management options are planned based on user feedback.
Can clash results be prioritised so the most critical appear first?
Same answer as above – not yet, but valuable input like this helps shape future development.
Can issues be exported in BCF format to share with other tools?
Not yet, but it’s planned. At the moment, issues are internal to Qonic, but BCF export and interoperability are definitely on the roadmap.

Measurement & Quantities
Can you define how surface area is measured – e.g. horizontal projection vs. side face?
We use algorithms and heuristics: a floor slab gives horizontal projection, a wall gives its vertical face. This is being expanded to give you more control and visibility over measurements.
Can reports be linked to specific model versions?
Yes. When you export a report, it’s tied to a specific model version. You can maintain versioned reports accordingly.
How would you calculate formwork area – without explicitly modelling the formwork itself?
We’re prototyping ways to do this using geometric rules (e.g. ignoring top surfaces, identifying adjacent faces). These surfaces would remain linked to the model and manually editable if needed.
Does the quality of the imported model affect the accuracy of quantity takeoff (QTO)?
Qonic supports a wide range of geometry types, including tessellated geometry. Minimal cleanup should be needed, but we’re always improving based on your feedback.

Modelling Logic & Workflow
Is there a way to place a window and all its subcomponents in the correct configuration in one go?
Not yet – but you can easily copy/paste configurations to similar windows for now.
What happens when you stretch a balcony with a balustrade? More rails or wider gaps?
If there’s a clear repetition pattern (like Excel’s drag-to-extend logic), Qonic will preserve and extend that pattern.
Should I model all wall/floor layers as one object or separate structural and finish layers?
We recommend modelling them separately. This gives a more accurate built representation. You can still group them logically using assemblies (e.g. a Wall Assembly with multiple Parts and their own materials).

API & External Connections
API Availability: Architecture, documentation and integration options.
Platform Ecosystem: Linking to external platforms like CDEs and project management tools.

Drawing & Documentation
2D/3D Consistency: Ensuring alignment between model and drawing outputs.
Export Logic: Mapping elements correctly for downstream uses like GIS.

Planning & 4D Simulation
Can a crane be used to simulate the placement of elements at a certain distance on site?
Not yet, but this is something we’d love to explore further. The idea of simulating crane operations, factoring in reach and lifting capacity, fits well within our ambition to make construction simulation as realistic as possible. It’s not under development today, but it’s definitely a direction we’re thinking about.
Will it be possible to colour elements by phase or appearance in the 4D planning tool, and include a legend showing execution dates per colour in the output?
Yes, this is planned. Colouring elements based on planning data, by phase, contractor, or critical path, is a key part of our vision for visual planning. A legend tied to these visualisations is also something we aim to include as the feature matures.
Can you define productivity ratios to calculate task durations based on quantities for example, a certain amount of concrete placed per day?
This is something we plan to support. The goal is to use the quantities of the objects linked to planning tasks and combine them with user-defined ratios to automatically calculate durations. It’s not yet implemented, but it’s fully aligned with our vision.
Can quantities be derived automatically based on the planning?
Not for now, but we see clear potential here. In one of our next releases you’ll see all the accurate quantities belonging to the tasks.
Can you adjust the schedule to allow construction of Block A and Block B at the same time, for example, by manually overlapping tasks?
Not in the first version. But more complex relationships between tasks, like ‘start-start’ or ‘finish-finish’, are on our list. These will allow for more flexible, detailed planning over time like planning Blocks A & B in parallel.