01
Model hub
IFC loading, future Fragments persistence, fast selection workflows, and BIM-specific visualization tools.
s2b
scan2bim
BIM workspace for models, plans, and review flows
First product shell for the BIM-native SaaS foundation
Models. Drawings. Decisions.
Turn fragmented building data into one operational BIM workspace.
scan2bim combines IFC models, PDFs, and project artefacts in a focused operating layer for coordination, QA, review topics, and future That Open viewer workflows.
- Primary artefacts
- IFC + PDF
- Core engine
- That Open
- Current base
- Rails 8.1
Command deck
Project North Yard
Model stream
Campus_A.ifc
Viewer frame
LOD 02
Topics
18
7 unresolved, 4 viewpoints
Sheets
42
linked to model zones
Validation
IDS checks
Run structured QA before release packages move to review.
Coordination
Issue loops
BCF topics connect screenshots, viewpoints, and accountable teams.
Documents
Plan overlays
Link drawings, PDFs, and derived artefacts to spatial context.
Workspace shell
A calm command layer for heavy building information.
The product surface is designed like an operations room: strong hierarchy, quiet panels, and fast access to the model, the plan set, the review backlog, and building metadata.
02
Document lane
Plan PDFs, derived exports, and artefact bundles live beside the model instead of in disconnected silos.
03
Review loops
IDS validation, BCF topics, viewpoints, and future approval flows form one traceable review chain.
04
Building memory
Structured metadata turns isolated deliverables into a searchable operational memory for each building.
Operational flow
Designed around the real BIM pipeline.
The first release does not pretend to solve every BIM problem. It focuses on a precise chain from ingest to review, so the viewer and document layer can mature on a stable backbone.
Step 1
Ingest
Bring IFC models, plan sets, and package context into a project workspace.
Step 2
Interpret
Parse geometry, expose metadata, and prepare future Fragments-backed runtime access.
Step 3
Review
Attach validation, viewpoints, and issues directly to model and document context.
Step 4
Operate
Turn reviewed data into a persistent building workspace for future delivery cycles.
Release modules
The initial product stack is already legible.
Viewer shell
Rails page foundation for the future That Open model viewer, selection tools, and measurement workflows.
Artefact registry
Structured storage for IFC, PDFs, and later derived Fragments or validation reports.
Review engine
BCF topics, IDS checks, viewpoints, and decision logs connected to geometry and sheets.
Next implementation move
Build the first authenticated workspace and mount the That Open viewer into this shell.
The visual system is now in place. The next logical slice is a real project workspace with uploaded sample assets, a viewer mount point, and the first artefact data model.