Case study: Helsinki pilot cuts idle formwork days with CurNext maturity

Pilot context

The Helsinki pilot exercised CurNext end to end across two buildings: wireless CN-CC curing probes, gateway coverage, BIM-linked surfaces, role-based dashboards for owner and GC stakeholders, and QA exports for major pours. The site faced cold-weather risk and critical-path decks that gated follow-on access.

This was not a lab demo. It was an operating project with real crews, real weather, and real formwork costs.

Approach

Scope first. The team instrumented pours that blocked facade and access milestones before expanding coverage.

Agree thresholds early. Maturity and readiness criteria were locked with the structural engineer before the first pour so field decisions did not invent policy at 6 a.m.

Install with commissioning discipline. Probe positions were planned mid-depth and near exposed faces where needed. Gateways were verified before concrete. Devices were scanned into CurNext surfaces for Building 1 and Building 2 so handlers and clients saw the correct scope.

Operate from one twin. Supers used CurNext views for overnight stalls and morning go/no-go calls. Office stakeholders watched the same readiness state without chasing WhatsApp photos of thermometers.

Results observed on the pilot pattern

• Earlier visibility when cold snaps slowed hydration.
• Fewer "wait and see" mornings for formwork crews on instrumented decks.
• Traceable QA packs linking device identity, timestamps, and surfaces.
• Clearer ownership split between Building 1 and Building 2 handlers.

Exact commercial savings vary by programme, but the operational pattern is consistent: uncertainty is expensive; CurNext reduces it on the pours that matter.

Lessons for the next CurNext deployment

1. Instrument the critical path first - do not dilute attention across every slab on day one.
2. Train the mobile workflow supers will actually open in the yard.
3. Keep RF and battery health visible in operations views; silent devices destroy trust faster than missing features.
4. Export QA in the same vocabulary as the owner numbering scheme.
5. Expand coverage after the morning decision loop is habitual.

Why this story belongs to CurNext

Hardware alone does not cut idle days. CurNext combines CN-CC sensing, LoRaWAN connectivity, project RBAC, BIM surfaces, alerts, and compliance-ready lineage. The Helsinki pilot showed that stack working as one product for concrete curing operations.