CurNext · Product
BIM-linked curing insights: IFC surfaces to live CurNext readiness
CurNext maps curing telemetry to IFC rooms and surfaces so readiness, alerts, and QA packs speak the language of the building model - not orphan device IDs.
Spatial context is the product
A green "ready" badge is useless if nobody knows which deck it refers to. Spreadsheet IoT tools often stop at device lists. CurNext is built around buildings, floors, rooms, and surfaces imported from BIM (IFC) or maintained as a structured site model.
That design choice changes how GCs, owners, and trade partners use curing data. Filters, alerts, and exports inherit the same hierarchy as coordination meetings.
From IFC to instrumented surfaces
Typical CurNext BIM flow:
- Import or attach the building model for the pilot site.
- Resolve floors, rooms, and surfaces that will receive concrete or protection decisions.
- Assign CN-CC devices to those surfaces during install.
- Stream telemetry and maturity against the surface record.
- Drive dashboards, alerts, and handover packs from the same objects.
When the model evolves, associations stay auditable. Soft deletes and project membership rules keep clients scoped to their buildings while CurNext employees retain fleet oversight.
Coordination workflows that actually get used
In practice, teams use CurNext spatial views to answer:
- Which Level 2 slabs are blocking facade access?
- Which walls still need protection overnight?
- Which probe cluster belongs to Building 1 versus Building 2 on a multi-building site?
Alerts can target zone owners instead of flooding a shared inbox. That is how maturity data escapes the "engineering curiosity" shelf and becomes a site operations tool.
Predictions and inspections in one twin
CurNext keeps curing telemetry next to related project objects: inspections, compliance documents, device lifecycle, and readiness status. The goal is a twin that stays honest - geometry plus live physics - so predictions and QA notes refer to the same surface IDs the field used at 6 a.m.
Implementation tips for CurNext projects
- Name surfaces the way supers already speak (deck B west, core wall grid C).
- Instrument critical-path surfaces first; expand coverage after the workflow sticks.
- Train both desktop and mobile users - morning decisions happen on phones in the yard.
- Keep BIM imports clean enough that room filters remain meaningful.
BIM linkage is not decoration. It is how CurNext turns sensor science into construction language.
- BIM
- IoT
- Site operations
0 comment
Sign in to interact
Like, comment, and reply require a CurNext account. Sign in on dash.curnext.app, then return to this post.
Open dashboard