The model stays the source of truth.
HSIOS™ unpacks the semantic model into a queryable hierarchy, runs deterministic clash detection across six MEP systems, validates against a 26-rule design engine, and exports valid IFC4 back into your federated coordination workflow.
Built for model-driven execution.
Six concrete capabilities, each shipping today. None are roadmap promises.
MEP Clash Detection
Parametric segment-intersection across HVAC, plumbing, electrical, structural, sprinklers, and automation. Conflicts surfaced before site work begins — not on a clash-report PDF nobody opens.
AI Design Validation
Material, climate, ventilation, luxury, execution categories. Rule severity tunable from the admin console. Weighted risk score 0–100 with a remediation plan attached to every CRITICAL finding.
In-Browser IFC4 Export
Generates valid ISO-10303-21 IFC4 directly from the project hierarchy. No external library, no plugin, no licence wall. Round-trips into Revit and Navisworks for federated coordination.
5-Mode Digital Twin
Structural tree, Floor Plan with draggable rooms, 4D Timeline, Isometric stack, MEP Clash overlay. The model you build is the model the contractor executes against — not a frozen render.
Component Spatial Position
Every component carries spatial coordinates in the database. Drag a fixture on the Floor Plan, and the position persists. The twin matches the BOQ matches the site — by design, not by spreadsheet.
Decision Engine Learning
Conflict patterns from past projects inform the next one. Cost stress, delay stress, carbon stress, pattern confidence, and learning weight all combine into a single weighted decision score with full explainability.
Model → Validate → Resolve → Execute.
Four steps from a federated model to a validated execution-ready state.
Import the model
Upload GFC drawings or an IFC. The platform unpacks rooms, components, MEP routing, and material specifications into a queryable hierarchy.
Run validation + clash detection
The 26-rule engine runs deterministically across every room. MEP Clash detection scans the six systems for parametric intersections. CRITICAL findings escalate to the Gemini reasoning layer.
Resolve and re-validate
Each finding ships with a remediation suggestion. Re-run validation incrementally — only the touched rooms re-evaluate. Resolved findings are recorded against the project memory.
Hand off to execution
Sign off the model. Execution layer inherits the validated state. BOQ items inherit room context. QA checklist phases inherit the design intent. The model stays the source of truth.
BIM-Manager Questions
Does HSIOS™ replace Revit or Navisworks?
No. HSIOS™ is an execution intelligence layer that sits next to your BIM tools, not in place of them. We import IFC, run our validation and clash detection against the unpacked hierarchy, and export IFC4 back when you need to round-trip into Revit or Navisworks for federated coordination.
How is the clash detection different from Navisworks Clash Detective?
Navisworks runs on geometry. HSIOS™ runs on the unpacked semantic model: MEP route, room boundary, structural member, fixture position. The output is a list of decisions with cost and time impact, not 14,000 untriaged collisions. It is execution-grade clash detection, not coordination-grade.
Can I tune the design validation rules for my firm's standards?
Yes. The 26 rules ship with sensible defaults but are editable from the admin console — severity, message text, recommendation text, and active flag. Patches propagate to all projects in your tenant after a 5-minute cache TTL.
Does the IFC export include MEP routing?
It includes the spatial hierarchy (project → site → building → storey → space) plus components with their spatial positions. MEP routing is exported as a separate IfcPipeSegment / IfcCableSegment set, properly classified. The output validates against the IFC4 schema.
How does HSIOS™ handle versioning of the model?
Every Design Document gets a version field that is write-once after creation. To version a document, you create a new record — never overwrite. The Decision Engine tracks which version was active when a decision was made, so post-handover audits stay faithful to the timeline.
Is there a sandbox environment for evaluating the platform?
Yes. Request a demo and we will provision a tenant with sample geometry. The 26 validation rules and the clash detection engine run identically in the sandbox and in production — there is no "demo mode" with reduced fidelity.
See the platform under your model.
We provision sandbox tenants with your sample geometry. The 26-rule engine, the clash detection, and the IFC export all run at full fidelity. No demo-mode reductions.