Qonic connector

Use your Qonic data for reporting, automation and AI.

Data Panda brings your Qonic projects, models and coordination data together with the rest of your construction stack. From one place, we turn it into dashboards, automations, AI workflows and custom apps your project leads, BIM coordinators, finance and procurement teams use every day.

About Qonic

The browser-native BIM platform that replaces the file handover with a live model.

Qonic is a cloud-based BIM modelling platform founded in 2021 in Ghent by Erik De Keyser, Mark Van Den Bergh, Tiemen Strobbe, Tjerk Gauderis and Sander Scheiris, all formerly from Bricsys (the BricsCAD team that Hexagon acquired in 2018). The product runs in the browser, on mobile and on desktop, and turns each BIM model into a database of assemblies, subassemblies and parts rather than a monolithic file. Architects, engineers, contractors and information managers create, enhance, coordinate and query the same model in real time, with open interoperability against Rhino, SketchUp, Revit and IFC.

For project leads and BIM coordinators in AEC, Qonic is the system of record for what is in the model: which elements exist, which revision they belong to, which discipline owns them and which coordination issues are still open. The in-product views cover the model-level question well. The harder questions sit across projects, disciplines and the financial side of the build: which change requests moved the project margin, how revision velocity per discipline tracks against the planned milestones, how element counts feed material orders in the ERP, and which coordination issues are dragging across submission cycles. Pulling Qonic into a warehouse is how those questions stop being a model someone has to open on a Friday afternoon to answer.

What your Qonic data is for

What you get once Qonic is connected.

Cross-project and cross-discipline reporting

Element counts, revision velocity and open-issue load across every project and discipline running on Qonic, in one place.

Element counts per discipline, per revision and per project phase
Revision velocity per discipline against the planned submission cycle
Coordination-issue ageing: how long issues sit open per project and assignee

Process automation

Turn change requests, revision events and element thresholds into the right action in your ERP, finance and procurement tools, without someone exporting a report each Friday.

Trigger material order drafts in the ERP when element counts cross the order threshold
Open a finance change-request workflow when an approved change exceeds a margin threshold
Notify procurement when a revision changes a long-lead element specification

AI workflows

Put model history, change requests and revision data behind AI that understands how each discipline moves through a project.

Slip-risk scoring on open coordination issues based on revision cadence and assignee load
AI summaries of change-request impact for the weekly project steerco
Submission-readiness checks that flag elements missing data before the next milestone

Custom apps on your data

Internal tools that sit on Qonic data instead of another viewer with its own export step.

Project-portfolio dashboard with element counts and revision velocity per project
Change-request impact tracker linking each approved change to its budget and schedule effect
Discipline-handover audit flagging models where the upstream discipline has not signed off

Use cases

Use cases we deliver with Qonic data.

A list of concrete reports, automations and AI features we have built on Qonic data. Pick the one that matches your situation.

Element count per disciplineWalls, slabs, beams and MEP element counts per discipline and revision.

Revision velocityRevisions committed per discipline per week against the planned cycle.

Change-request margin impactApproved change requests rolled up to the project margin and forecast.

Coordination-issue ageingMedian open-time per coordination issue, by project and assignee.

Submission driftModels behind on the next planned submission, per project and discipline.

Element-to-material mappingElement counts mapped to the material lines that need to be ordered.

Long-lead element watchElements with long-lead specs that changed in the latest revision.

Discipline workloadOpen elements and issues per discipline owner across active projects.

Project-portfolio viewElement, revision and issue load across the live project portfolio.

Model-data completenessElements missing data fields required for the next milestone.

Sign-off auditWhere an upstream discipline has not signed off before downstream work started.

Change-request cycle timeTime from change-request raised to approved or rejected, per project.

Real business questions

Answers you will finally get.

Which projects are losing margin to approved change requests?

Approved change requests rolled up to the project margin line, ranked by impact and broken down by discipline. Project leads and finance see which projects are quietly absorbing change cost before the next monthly review surfaces it.

Are any disciplines falling behind on revisions?

Revisions committed per discipline per week against the planned submission cycle, with the gap shown per project. Where structural or MEP has stopped delivering at cadence, it shows up as a number against the schedule rather than a surprise at the next coordination meeting.

Which coordination issues are ageing past acceptable?

Open coordination issues sorted by age, project and assignee, with the elements they touch attached. BIM coordinators see which issues have been parked too long before they trip a submission deadline.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Approved change-request impact and forecast slip next to the project margin line. You see which builds really consumed the quarter, instead of hearing about it when someone finally raises it in a steerco.

For sales leaders

Active-project status, milestone hit-rate per discipline and reference-ready completion data joined to the account record. Account managers and BD see which delivered projects are ready for the next conversation, instead of chasing the project lead for screenshots before a renewal.

For operations

Revision velocity per discipline, open coordination-issue load and submission-drift across the active project portfolio in one view. The weekly project sync runs on data that was there all week instead of a model someone reopened that morning.

Ideas

What you can automate with Qonic.

Pair with MS Dynamics 365 Business Central

Sync Qonic element counts to Business Central material orders

Element counts on the latest approved Qonic revision feed the procurement workflow in Business Central, so order drafts for walls, slabs, beams and MEP packages match what the model contains. When a revision changes the count for a long-lead element, the order draft updates and the project lead sees the delta against the budget instead of finding it in a supplier invoice three weeks later.

Pair with Exact Online

Roll Qonic change-request impact into the Exact Online project margin

Approved change requests in Qonic write through to the project ledger in Exact Online, with the cost and revenue impact mapped onto the project's margin line. Finance sees which builds are absorbing change cost in the live margin view, and project leads stop having to reconcile a separate change-request log against the monthly P&L.

Pair with monday.com

Turn Qonic coordination issues into monday action items

Open coordination issues in Qonic create the matching items on the project's monday board, with the discipline owner, target submission date and linked elements attached. The site team and the back-office track the same issue without opening the model viewer, and stale issues show up on the board before they hit a submission deadline.

Pair with Slack

Route Qonic revision and change-request events into the right Slack channel

New revisions, approved change requests and high-priority coordination issues post into the project's Slack channel, with the discipline, the elements touched and the assignee tagged. Project teams stop scrolling the Qonic notification inbox and get the events that belong on their channel, so a structural change does not sit unread until the next coordination call.

Pair with HubSpot

Link Qonic project delivery progress to the HubSpot account record

Active Qonic projects map to the HubSpot account, with milestone hit-rate, open-issue load and submission status visible on the company timeline. Account managers see how a build is running before the next renewal or follow-on conversation, and marketing pulls reference-ready projects from the same view.

Pair with Salesforce

Sync Qonic project-portfolio metrics to the Salesforce account view

Project-portfolio metrics from Qonic, including open change-request value, revision velocity and submission status per project, sync into the Salesforce account record. Sales and account leads see the live build picture next to the opportunity pipeline, and the next-step conversation starts from the project's actual status instead of a back-and-forth with the project lead.

Data model

Tables we make available.

These are the 12 tables we currently pull from Qonic into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Codification Library Items
Codifications
Custom Properties
Locations
Material Libraries
Material Library Items
Models
Products
Products Available Data
Products Dynamic Properties Available Data
Projects
Types

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Qonic data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Qonic to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Qonic connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Do elements, revisions and coordination issues all come across?

Yes. Projects, models, the element set per model, revision history and the open and resolved coordination issues land in the warehouse, so element counts, revision velocity and issue ageing become reportable next to the rest of the project data. Element-level fields stay attached, so a wall, slab, beam or MEP element keeps its discipline, type and parent assembly when you query it.

Does this work across architectural, structural and MEP disciplines?

Yes. The Qonic model holds elements from every discipline working on the project, so the warehouse view splits cleanly by discipline. You get the architectural revision view, the structural change-request view and the MEP coordination-issue view from the same dataset, instead of three discipline-specific exports stitched together by hand.

What about models that came in from Revit, Rhino or IFC?

Qonic supports open interoperability with Revit, Rhino, SketchUp and IFC, so models brought in from those tools become part of the same Qonic project once imported. The connector reads what is in the Qonic project, so any element, revision or issue tied to those imported models flows into the warehouse the same way as native Qonic content.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Qonic setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors