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
Which IFC version is the Qonic data schema based on? Can this be selected per project? For example, could I add a QSet to an IFC file missing quantities in one action?
Qonic’s data schema is based on IFC and can be adapted to various versions (IFC2x3, IFC4, and IFC4x3). This ensures you can always work with the correct attributes and properties in your Qonic projects and models.
Is “Keynote” data from materials and objects (important for tenders and as-built dossiers) readable in Qonic?
Yes, such metadata can be read in Qonic as long as it’s present in the IFC file.
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.
Which other packages/kernels are in the pipeline for import support? Vectorworks? Archicad? Are there technical limitations?
We are continuously exploring additional integrations. Currently, there are no technical blockers, but prioritisation depends on user demand and format complexity.
Can GIS data be imported? If yes, which formats?
Currently, importing GIS data is not yet supported. However, API-based integration with applications that can supply this data is possible in the future.
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).
Drawings
Will it be possible to verify whether 2D output still matches the 3D model, e.g. via QR code?
We’re working on a solution for automatic 2D drawing generation (including annotations, dimensions, etc.) from the 3D model. It will support custom templates and configurations to comply with your drawing standards.
Can objects (based on IFC type or classification) be mapped to CAD layers during DWG export? Our GIS system needs this for plan ingestion.
Layer mapping based on classification or IFC type is on our roadmap. We’re aware of this need for integrations with external systems like GIS.
API
Is there an integration with CDE platforms like ACC?
This is not yet available, but it’s on our radar as we expand our ecosystem integrations.
What is the architecture of the API? Is it a REST API? Is there documentation available for exploration?
Yes, the API is a REST API for model data, allowing you to interact with IFC/RVT models. You can read data (such as properties, materials, etc.) and write data back to Qonic.
We plan to expand API capabilities in the coming months, including APIs for libraries, user management, and organization/project/model management.
Example Python and Excel use cases: Qonic GitHub
Full API documentation: Qonic Swagger API Docs
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.
Performance
Collaboration
Data & Geometry editing
Modelling