Aeion Construction + BIM / CAD
Aeion Spatial's importer parses glTF, GLB, OBJ, STL, PLY, DAE, USD/USDZ, FBX, and 3DS models with real geometry decoding — and construction's clash detection turns overlapping model geometry into a numbered RFI automatically. Two things this page is blunt about: IFC is something Aeion *authors and exports* from your floor plans, not something it imports; and Revit (.rvt), DWG, and Navisworks are credential-storage stubs today, not a live import pipeline. Here is exactly what is parsed and what is not.
Format Support — The Honest Table
`
IFC — Authored and Exported, Not Imported
This is the single most-misread claim about Aeion + BIM, so it gets its own section.
Revit, DWG, and Navisworks — Credential Plumbing Only
The construction module stores Autodesk Forge/APS credentials (client ID, secret, region) and exposes a settings collection and routes for them. Be clear about what that does and does not mean.
Clash Detection → Auto-RFI (Live) — and What Feeds It
Clash detection is real and useful, and it is worth being precise about its input.
Drone Photogrammetry + Gaussian Splats (Live — Captured in Spatial, Linked in Construction)
`
FAQ
No. Aeion generates/exports IFC from its own floor plans (the Parametric Architecture Forge, ISO-10303-21 STEP). There is no IFC import parser today — uploading a third-party .ifc does not parse its geometry.
Roadmap. The module stores Autodesk APS credentials and has a format enum that includes "rvt"/"nwd", but there is no translation or viewer pipeline wired, and stored credentials are never verified. Do not scope a deployment assuming live Revit/DWG import.
glTF/.glb, OBJ, STL, PLY (mesh), DAE, USD/USDA/USDC, USDZ, FBX, and 3DS — all parsed by Aeion Spatial's importer. glTF/.glb is the fully-processed path (decimation + LODs). See the Spatial glTF/USD page for details.
Yes — a real axis-aligned bounding-box overlap test that auto-creates a numbered, BIM-flagged RFI with the clash location and a resolution suggestion. It runs on bounding volumes you provide, not on geometry auto-extracted from an unparsed IFC/Revit file.
Aeion Spatial produces the Gaussian-splat/mesh assets; construction's viewer service listens for `spatial.scan.completed`, matches the scan to a project, and links the asset IDs (idempotently). Then it is viewable in-browser via WebXR.
The holographic viewer targets WebXR with Apple Vision Pro / visionOS as the headline device; splat files render as point clouds and mesh files route through USD/USDZ to RealityKit, with a WebXR fallback for non-Apple hardware.
Real mesh import, real clash-to-RFI, and no fiction about IFC.
glTF/USD/OBJ/FBX/STL mesh import via Spatial, bounding-box clash detection that opens RFIs automatically, drone-splat capture linked to projects — all live. IFC is authored/exported (not imported); Revit and DWG import are roadmap. We label every one.