The DAQS Platform

Your models carry the data.
We make sure it reaches the
systems that need it.

Construction projects generate enormous amounts of model data. Most of it never reaches the systems that depend on it — or reaches them wrong. DAQS is the intelligence layer between your BIM models and your operational systems.

How it works

Validate. Transform. Connect.

Three stages. One continuous pipeline. Each stage is independent — you can start with validation alone — but together they eliminate the entire manual cycle between model and system.

Validate
Rules defined for the project are applied automatically to every element, by every engineer, in real time — inside Revit, before IFC export. Issues surface where they can still be fixed.
DAQS AssistDAQS Dashboard

At-source, rule-based validation

DAQS Assist runs inside Revit as a live feedback layer. Rules are defined once by the BIM coordinator and distributed to all engineers on the project. Every element is checked against classification requirements, parameter completeness, naming conventions, and downstream system constraints.

  • Rules managed centrally via DAQS Dashboard
  • Real-time feedback per element, per engineer
  • Validation runs before IFC export — not after
  • Connects to Autodesk Platform Services (APS)
  • Supports NL-SfB, ETIM, Uniclass, OmniClass, MasterFormat, COBie, and custom classification schemes
Transform
Validated IFC data is structured into the exact format each downstream system requires. No manual reformatting. No export templates. The output is production-ready before it leaves the platform.
Format mappingClassification

Structured output from validated IFC

Once an IFC passes validation, DAQS transforms the relevant elements into the data format each connected system expects. Mapping logic is configured per system — a manufacturer ordering platform has different field requirements than an ERP or a construction OS.

  • Reads element properties, type data, spatial context
  • Applies system-specific output schemas
  • Handles unit conversion, field mapping, deduplication
  • Output is deterministic — same input, same output
  • New system mappings can be added without re-engineering
Connect
Structured data is delivered directly to operational systems — order platforms, planning tools, ERP, construction OS, AI engines. No email. No re-entry. No validation work on the receiving end.
DAQS ElementsAPI

Direct delivery to operational systems

DAQS Elements is the first live implementation of the Connect stage — delivering validated door data directly to manufacturer order systems. The same pattern applies to any downstream system with a defined data interface.

  • Live connection to order platforms (production)
  • Order file generation from validated IFC door elements
  • REST API for connecting additional systems
  • Webhook support for event-driven delivery
  • Expandable to staircases, window frames, ERP, construction OS
Products

Three products. One pipeline.

Each product addresses a specific point in the Validate → Transform → Connect pipeline. Together, they cover the full path from model to operational system.

DAQS Assist

Live validation inside Revit

A plugin that gives engineers real-time data quality feedback as they model. Rules are defined centrally by the BIM coordinator and applied automatically — to every engineer, every element, every session.

For: BIM coordinators, engineers, project managers who need to enforce data standards without a manual review cycle.

DAQS Dashboard

Quality overview across all models

A coordinator dashboard that shows data quality status across all models, all disciplines, and all engineers on a project. Rule management, issue tracking, and project-level reporting in one place.

For: BIM coordinators and project leads who need a reliable, real-time view of model quality across the full project team.

DAQS Elements

From validated IFC to production orders

Takes validated IFC data and generates production-ready order files for manufacturers. Currently live for door ordering. The same pipeline is being extended to staircases, window frames, and beyond.

For: Contractors and manufacturers who want to eliminate manual order preparation and the validation work it generates on both sides.

Where DAQS fits

Built to work with your existing tools,
not replace them

DAQS and coordination tools

Tools like Solibri check what has been delivered. DAQS validates while engineers build. The two are complementary — DAQS reduces the number and severity of issues that reach coordination review. Your coordination workflow stays exactly as it is. It now receives the data you specified.

DAQS and downstream systems

DAQS does not replace ERP systems, order platforms, or construction operating systems. It makes data from BIM models available to them in a form they can actually use — without manual extraction, reformatting, or re-entry. The connection is governed, repeatable, and auditable.

DAQS and engineers

DAQS does not fix data — engineers do. DAQS surfaces issues at the point where they can still be corrected: inside Revit, while the model is being built. The result is fewer issues reaching review, and fewer corrections needed before data can move downstream.

DAQS and the broader platform

DAQS Elements is the first live proof of the Validate → Transform → Connect pipeline applied to supply chain. The same architecture extends to any operational system with a defined data interface — ERP, construction OS, AI engines, digital twins. The intelligence layer scales to however many systems need reliable model data.

Questions

Common questions about the platform

Does DAQS require changes to how engineers work in Revit?
+

No significant changes. DAQS Assist runs as a plugin inside Revit and provides feedback in the existing modeling environment. Engineers do not need to learn a new tool or change their modeling process — they receive quality feedback as they work, in context, without leaving Revit.

Rules are defined and managed by the BIM coordinator. Engineers see what is required and whether their elements meet those requirements. The validation logic lives in the platform, not in each engineer's workflow.

At what point in the project workflow does DAQS operate?
+

DAQS operates upstream — inside Revit, before IFC export. This is the key distinction from post-export coordination tools. By the time a model reaches a coordination review or is exported to a downstream system, the cost of fixing data quality issues has increased significantly.

DAQS moves that quality check to the earliest possible moment: when an engineer is actively modeling an element and a correction takes seconds, not days.

Which downstream systems can DAQS connect to?
+

Currently in production: manufacturer order systems (live with Svedex for door ordering via DAQS Elements). The Connect stage of the pipeline is designed to be extensible — any system with a defined data interface can be connected via the DAQS API.

Systems we are actively working toward include ERP platforms, construction operating systems, and AI-driven project management tools. If you have a specific system in mind, the introduction call is the right place to discuss what a connection would require.

How is DAQS different from validation built into Revit or other authoring tools?
+

Revit has basic parameter checking, but no concept of project-specific governance rules, downstream system requirements, or classification standards. DAQS Assist adds a rule layer on top of Revit that is defined per project, managed centrally by the BIM coordinator, and enforced consistently across every engineer on the team.

The rules can reference classification schemes (NL-SfB, ETIM), parameter completeness requirements, and the specific data fields that each connected downstream system needs. That context does not exist in any authoring tool by default.

Can DAQS be used for a single project, or does it require platform-level adoption?
+

DAQS can be adopted at the project level. Many organisations start with a single project — typically one where the cost of poor data quality is visible and the downstream connection (to a manufacturer or planning system) is already a pain point.

Platform-level adoption — where validation rules and system connections are standardised across all projects — typically follows once the value has been demonstrated in a specific context. The introduction call is designed to help identify the right starting point for your situation.

See how the pipeline applies to your situation

A 30-minute conversation. We start with your context, not a product demo.

The intelligence layer between your models and your systems. Privacy policyTerms and conditionsDisclaimerSources © 2026 DAQS.IO — The Netherlands