UPLOADED
The browser received the selected file and computed its identity.
Upload says nothing about format validity, geometry, coordinates or approval.
DesignStudio
LIVE9 live / 13 roadmapPlace and compare locality-aware building shells
Continue from a LandIntel parcel and swap regional shell studies in a live rendered view.
Every model is INDICATIVE until planning and professional verification. Unknown site conditions stay marked UNKNOWN.
Try itTest-fit massingLIVE
Live massing forecast
LiveINDICATIVE
Plot width: 20 m / 65.62 ft · uniform setback: 3.08 m / 10.1 ft
Floor area
1,320 m²
14,208 sq ft
Achieved FSI
2.2
Diagram variant 1/3
INDICATIVE — the existing test-fit engine runs on a fixed 20 × 30 m (65.62 × 98.43 ft) sample plot. Style changes diagram treatment only; S3 owns buildable style parameters. Verify all local controls.
Shared project · live recompute
INDICATIVE- Shared gross area
- 1,248 m² · 13,433.4 sq ft
- Shared floors
- 3
No parcel context — resolve a lookup in LandIntel.
One browser-local project state feeds every product lens. Monetary rates remain blank unless independently verified; Invest uses a normalized area index, not currency.
DesignStudio cockpit preview
Live deterministic plan and massing workspace
Loading 3D view…
Choose an option or describe a change above.
Exports stay on this device.Site context (real OSM):Site location not set: the current project has no coordinates, so no surrounding buildings or roads can be fetched.
INDICATIVE deterministic geometry; verify site, code, and authority constraints.
DesignStudio · building-template suitability
Suitability across seven evidence-linked dimensions
Physical fit, planning, environmental, structural, geotechnical, supply and delivery each resolve SUPPORTED, CONDITIONAL, BLOCKED, UNKNOWN or STALE from recorded evidence. The single weakest dimension governs the overall result. Nothing here infers legal, structural or regulatory compliance.
Sample fixture
Bengaluru Urban, Karnataka
Climate-adaptive neutral shell
SAMPLE FIXTURE - INDICATIVE. No LandIntel parcel is loaded into Project Context; every value below is synthetic demonstration data, not a real project evaluation.
Overall
BLOCKEDGoverned by Structural, the weakest of the seven dimensions.
Physical fit
CONDITIONAL · INDICATIVERequired action: Physical envelope fit is geometry-only; it does not confirm setbacks, coverage ratio or authority-approved plot boundaries.
Evidence (2)
- Template parametric envelope CATALOGUE REVIEWED
- Plot 80 m² · 861 sq ft – 12,000 m² · 1,29,167 sq ft, floors 1-8.
- Selected parcel INDICATIVE
- 320 m² · 3,444.5 sq ft, Ferrum sample fixture - not a real project.
Planning
CONDITIONAL · INDICATIVE- Jurisdiction pack "India jurisdiction pack" is available; this assessment does not infer planning compliance from that alone.
Required action: A qualified planning professional must confirm compliance for this specific parcel; this dimension only confirms an applicable rule pack exists.
Evidence (1)
- India jurisdiction pack AVAILABLE
- Applies only after the governing authority, source version and effective date are identified.
Environmental
UNKNOWN- No connected source for: terrain, osm-context (confidence UNAVAILABLE); this is never treated as a conditional pass without a recorded contract rationale and supporting evidence, neither of which is present.
- One or more environmental layers are indicative or sample-fixture data, not verified site survey.
Missing: terrain, osm-context
Required action: Connect a verified source for each UNAVAILABLE required layer, or record the specific contract rationale and evidence that justifies proceeding without it.
Evidence (5)
- Parcel selection extent INDICATIVE
- Indicative extent only, sized from the parcel's recorded area (320 m² · 3,444.5 sq ft) around its recorded coordinate. This controls data extent and scene size for clipping - it is not a surveyed cadastral polygon and never implies survey accuracy. Provenance: Ferrum sample fixture - not a real project (INDICATIVE, 2026-09-19).
- Terrain UNAVAILABLE
- NO TERRAIN SOURCE CONNECTED. No slope, drainage, cut/fill or elevation conclusion is asserted.
- OSM contextual buildings & roads UNAVAILABLE
- UNAVAILABLE. Site location not set: the current project has no coordinates, so no surrounding buildings or roads can be fetched. Nothing is substituted.
- Photorealistic visual context (optional) UNAVAILABLE
- GATED UNAVAILABLE pending verified API terms, key availability, attribution and quota/cost handling. Never used for dimensions, setbacks, levels or structural decisions, even once connected.
- Proposed design AUTHOR-CONTROLLED
- The only layer editable through Studio Parameters; never overwritten by terrain, OSM or photoreal context data.
Structural
BLOCKED- No precomputed structural analysis envelope is attached to this template.
- JURISDICTION differs from, or is outside, the recorded analysis envelope.
Missing: soil, wind, seismic, snow
Required action: No precomputed structural analysis envelope exists for this template; a structural engineer must establish one before use.
Evidence (1)
- Precomputed analysis envelope NOT PRECOMPUTED
- Current catalogue shells are architectural massing studies and have no reusable structural verification.
Geotechnical
UNKNOWN- Project investigation evidence required: Soil classification and properties, Groundwater, Boreholes, CPT and SPT, Laboratory testing, Bearing and settlement inputs, Foundation constraints.
Missing: project-geotechnical-investigation
Required action: Project investigation evidence required: Soil classification and properties, Groundwater, Boreholes, CPT and SPT, Laboratory testing, Bearing and settlement inputs, Foundation constraints.
Evidence (8)
- Terrain and slope UNKNOWN
- No source-qualified evidence loaded
- Regional geology and lithology UNKNOWN
- No source-qualified evidence loaded
- Soil classification and properties UNKNOWN
- No source-qualified evidence loaded
- Groundwater UNKNOWN
- No source-qualified evidence loaded
- Flood and drainage UNKNOWN
- No source-qualified evidence loaded
- Seismic hazard UNKNOWN
- No source-qualified evidence loaded
- Landslide UNKNOWN
- No source-qualified evidence loaded
- Subsidence UNKNOWN
- No source-qualified evidence loaded
Supply
UNKNOWN- No supply context was provided.
Missing: supply-context
Required action: Provide material availability and procurement-hold data for this project.
Delivery
UNKNOWN- No delivery context was provided.
Missing: delivery-context
Required action: Provide site-access and delivery-window information.
Evidence reused
Physical fit, Planning
Recheck required
None
Recomputation required
JURISDICTION, MATERIALS, LOADS
Professional review required
Planning, Structural, Geotechnical
Missing inputs: terrain, osm-context, soil, wind, seismic, snow, project-geotechnical-investigation, supply-context, delivery-context
INDICATIVE — not a legal, structural or regulatory compliance determination. A named professional review remains required wherever this summary marks one.
DesignStudio · OpenBIM intake
Local browser processingKnow what entered the project before using the model
Select an IFC, DXF or STAAD .std file to compute its SHA-256 and see exactly what was read and what was not. The file stays in this browser session. Geometry viewing, CRS verification and engineering acceptance remain separate controls.
Your file never leaves this browser: it is read and parsed on your device, not uploaded.
Current intake status
NO MODEL INGESTED
No file has been parsed, previewed, validated or approved.
1 · Identify the revision
Maximum 50 MB. Revision, source and responsible party are recorded for IFC only. It does not upload, retain, render or approve the model.
Accepted cross-brand formats
IFC · AVAILABLEDXF · AVAILABLESTAAD .std · AVAILABLELandXML / XML · ROADMAP
Closed native files (DWG, RVT, RFA, Tekla .db1, ArchiCAD .pln, SketchUp .skp) are not read. Export an interchange format from the software you already use.
How to export from your software
- Revit: File > Export > IFC, then upload the .ifc file.Source: Autodesk Revit help, "Export a Model to IFC". Menu labels can differ between versions.
- ArchiCAD: File > Save As, choose IFC as the file type, then upload the .ifc file.Source: Graphisoft help, "Export IFC Model". Menu labels can differ between versions.
- Tekla Structures: File > Export > IFC, then upload the .ifc file.Source: Trimble User Assistance, "Export in IFC format". Menu labels can differ between versions.
- AutoCAD: Save Drawing As, pick a DXF format under "Files of type", then upload the .dxf file.Source: Autodesk AutoCAD help, "To Export a Drawing to a DXF File". Menu labels can differ between versions.
- SketchUp Pro: File > Export > 3D Model, choose DXF (3D or 2D), then upload the .dxf file. IFC export from SketchUp: UNKNOWN.Source: SketchUp Help, "Importing and Exporting CAD Files". Menu labels can differ between versions.
- STAAD.Pro: The .std file is the STAAD input file itself; upload it directly. Menu path to save or locate it: UNKNOWN.Source: Bentley STAAD.Pro Technical Reference, "STAAD Input Files". Menu labels can differ between versions.
2 · Intake report
Awaiting a model file
The report will expose file identity, importer and version, units, what was read, and a visible list of everything that was not imported.
Controlled release states
PREVIEWED
A visual preview was created for a specific checksum.
Rendering success does not establish geographic, dimensional or engineering validity.
VALIDATION REQUIRED
Parsing completed, but required evidence or professional checks remain open.
Downstream release remains blocked.
VALIDATED
Required intake checks passed against project control and warnings were reviewed.
Validation records reviewer, evidence, date, tolerance and limitations.
APPROVED FOR MACHINE
A named authority approved a validated revision for a stated machine workflow.
Approval is revision-specific and revoked by affecting changes.
REJECTED
The file failed intake or was rejected by a reviewer.
Rejected revisions cannot supply downstream work.
Machine release
BLOCKED · 0 / 6
- Exact model revision and checksum selected
- Units, CRS, vertical datum and project control validated
- Geometry warnings accepted or closed
- Previous-revision differences reviewed
- Machine/export compatibility validated
- Named approver, scope and audit evidence recorded
A PARSE OR RENDER DOES NOT MEAN GEOGRAPHICALLY, DIMENSIONALLY OR ENGINEERING VALIDATED. Plan, 3D and cross-section synchronization, geometry bounds, measurements, revision overlays and machine export remain roadmap work.
DesignStudio · environmental context
Keep context visible without turning it into design evidence
Each source remains a separate layer with its own coordinate system, date, licence, confidence and known gaps. Context layers cannot supply dimensions, setbacks, levels or structural decisions.
Project Context
No parcel selected
No parcel with coordinates is loaded in Project Context, so there is no real site to anchor context layers to. Nothing is drawn around a substitute location.
- UNAVAILABLE
Parcel selection extent
No authoritative parcel is loaded from Project Context. No boundary is rendered or implied.
- CRS
- UNKNOWN
- Units
- metres
- Horizontal datum
- UNKNOWN
- Vertical datum
- UNKNOWN - no elevation reference is attached to this boundary
- Source date
- UNKNOWN
- Licence
- UNKNOWN
- Coverage
- None
- Resolution
- UNKNOWN
- Attribution
- No parcel selected
- Completeness
- No surveyed boundary ring exists in Project Context today; this layer shows an area-derived indicative extent, never a cadastral polygon.
- UNAVAILABLE
Terrain
NO TERRAIN SOURCE CONNECTED. No slope, drainage, cut/fill or elevation conclusion is asserted.
- UNAVAILABLE
OSM contextual buildings & roads
UNAVAILABLE. Site location not set: the current project has no coordinates, so no surrounding buildings or roads can be fetched. Nothing is substituted.
- UNAVAILABLE
Photorealistic visual context (optional)
GATED UNAVAILABLE pending verified API terms, key availability, attribution and quota/cost handling. Never used for dimensions, setbacks, levels or structural decisions, even once connected.
- AUTHOR CONTROLLED
Proposed design
The only layer editable through Studio Parameters; never overwritten by terrain, OSM or photoreal context data.
INDICATIVE — CONTEXT ONLY. Survey/cadastral geometry, terrain analytics and provider permissions must be independently verified before measurable use.
Context twin source priority
Project survey / cadastral evidence
CONTROLBoundary, control points, levels and measured existing geometry
Must be supplied and accepted for the project; no global map source can replace it.
Overture Maps Buildings
CONTEXTGlobal building footprints and parts, with height, floor and roof attributes where present
Coverage and attributes vary. Missing height, floors, facade and roof fields remain UNKNOWN.
OpenStreetMap direct
CONTEXTBuildings, roads, access and community-authored feature tags
Community coverage is uneven and is not survey evidence.
Qualified DTM / DSM / LiDAR
ANALYTICALTerrain, obstruction, slope, drainage and level context
Usability depends on capture date, classification, CRS, vertical datum, resolution and accuracy.
Google Photorealistic 3D Tiles
VISUAL-ONLYHigh-fidelity visual urban context where provider coverage exists
Not survey-grade; cannot control dimensions, setbacks, levels or window placement.
Evidence-linked design analysis
India pack · BEE Eco Niwas Samhita
CHECKIndian residential envelope, daylight potential and natural-ventilation checks
Radiance / Honeybee
SIMULATIONDaylight, luminance, glare and facade-opening option simulation
EnergyPlus / OpenStudio
SIMULATIONThermal, envelope and whole-building energy option simulation
OpenFOAM
SPECIALIST-REVIEWBounded wind and outdoor/indoor airflow studies where justified
SUTRA may compare and explain window, shading and massing options. Every recommendation remains a proposal until the controlling geometry, local rules and required professional review are complete.
International jurisdiction architecture
Ferrum uses one worldwide project kernel and independently versioned country, state and city rule packs. India is the first deep pack, not the product boundary.
Global project kernel
AVAILABLEWorldwide
Stores geometry, evidence, provenance and approvals without assuming a country-specific planning or building rule.
India jurisdiction pack
AVAILABLEIndia, resolved further by state, urban local body and development authority
Applies only after the governing authority, source version and effective date are identified.
United States jurisdiction adapter
ADAPTER-READYCountry, state, county and city/AHJ
Model codes are never treated as locally adopted law without the AHJ, edition and amendments.
European jurisdiction adapters
ADAPTER-READYEU framework plus member-state and municipal rules
Country and municipality packs remain independent; EU-level policy does not substitute for local planning control.
Additional country pack
RESEARCH-REQUIREDAny country and its subnational authorities
Until a reviewed pack exists, SUTRA provides design analysis with regulatory fields marked UNKNOWN.
DesignStudio · site-analysis context
Qualified site evidence from LandIntel
Read-only. Only records that were reviewed and qualified in LandIntel appear here; inferred, stale, invalid and low-confidence records are held back. This is context, not a design recommendation, and nothing here changes the model — design intent still goes through SUTRA.
UNKNOWN — no site-analysis context has been handed off. Record, review and send evidence in LandIntel's Site analysis tab.
Features
What is live, and what is next
Open a row for its limits.
Live now9
Regional building-shell catalogueLIVE
Swap original, typology-derived outer shells directly in the rendered cockpit. The starter catalogue covers Indian regional and climate responses, records provenance and copyright boundaries, and labels every model INDICATIVE. It does not reproduce an architect project or establish planning approval, engineering validity or constructability.
Parcel-aware SUTRA shell recommendationLIVE
When a LandIntel parcel is locked, DesignStudio ranks shell studies from recorded state, plot area and land use, explains the match and preserves UNKNOWN planning, orientation, access, terrain and adjoining conditions. With no locked parcel it fails to a neutral comparative shell rather than inventing locality data.
Open rendering stackLIVE
Three.js provides the live browser PBR viewport, Three GPU Path Tracer provides an optional progressive beauty preview, and web-ifc preserves IFC geometry and properties. A controlled Blender Cycles worker is the next high-resolution render stage. D5 and V-Ray are optional user-installed export plugins only and receive no Ferrum project write access.
Parametric openings (INDICATIVE)LIVE
Select generated doors and windows and adjust bounded dimensions and configuration in the deterministic preview.
Test-fit massingLIVE
Enter plot dimensions and floor count to generate a deterministic, indicative massing preview.
Interior wall moves (INDICATIVE)LIVE
In the plan view, select an interior partition wall and drag it, nudge it, or type an exact position; rooms re-derive around it, moves are clamped so rooms keep a minimum width, and every move can be undone, redone or reset. Exterior walls stay fixed and the plan remains an INDICATIVE deterministic preview, not a drawing for approval or construction.
DXF preview exportLIVE
Export indicative plot, room, door, and window geometry into DXF layers for further review.
Model preview on ingestionLIVE
The available first slice selects an IFC revision locally in the browser, computes its SHA-256, and uses web-ifc to report schema, declared length unit, coordination origin and parsed entity counts. The file is not uploaded or retained. A future successful render will remain PREVIEWED only; geometry viewing, bounds, CRS, vertical datum, revision comparison, validation and machine release remain blocked and are stated as unresolved in the report.
IFC metadata intakeLIVE
A local browser pass computes SHA-256 and uses web-ifc to read schema and entity counts without uploading the file.
Roadmap13
Browser-native prompt geometryROADMAP
Create and revise editable architectural geometry through SUTRA inside the Ferrum web workspace, with no Rhino or other desktop CAD dependency. The target workflow keeps prompting, direct manipulation, validation, drawings, quantities, and export in one governed project context; it is not built yet.
Constraint-preserving concept visualizationROADMAP
Generate selectable presentation styles only after verified site, CAD, or GIS geometry is loaded and spatial constraints are locked. The target workflow keeps parcel boundaries, roads, dimensions, north orientation, and scale traceable; compares source and generated views side by side; records model, prompt, seed, and source revision; and exports every result as INDICATIVE — NOT FOR CONSTRUCTION OR APPROVAL. It is not built yet.
AI plan generationROADMAP
Floor plans and elevations generated from a natural-language brief are not yet built.
General plan editingROADMAP
Room dragging, exterior wall moves, freehand drafting, and broader CAD controls are not available. Moving interior partition walls is available separately.
Issue setsROADMAP
PDF issue sets and collaborative issue workflows are not available.
Combined project modelROADMAP
Inspect compatible building, road, utility and site models in one browser scene while preserving each source model and revision. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Hierarchy & visibilityROADMAP
Browse a model tree, toggle sources and categories, and isolate selected objects without deleting project context. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Plan, 3D & cross-section viewsROADMAP
Keep top, front, side, isometric and cross-section views synchronized to the same selected object and coordinates. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Surface, wireframe & pointsROADMAP
Switch representation to expose topology, point density and geometry that a shaded surface may conceal. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Alignment & centreline inspectionROADMAP
Inspect alignments, centrelines and their relationship to surfaces and project control. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Measurements & coordinate readoutROADMAP
Interrogate distances, elevations and coordinates with units, CRS, datum and precision visible beside every result. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Revision overlaysROADMAP
Compare current and previous revisions and prevent superseded geometry from silently reaching downstream work. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
Design-versus-survey comparisonROADMAP
Compare design geometry with survey or as-built evidence and report deviations against stated tolerances. This capability remains roadmap work and is not connected to the current metadata-only IFC intake.
How it works
- 01Continue from LandIntelUse the locked parcel context, or enter plot dimensions when no parcel is available.
- 02Swap a regional shellCompare original typology-derived outer shells while the rendered view remains visible.
- 03Review the evidenceInspect SUTRA's reasons, UNKNOWN items, provenance and the INDICATIVE status before export.
Integrations
Works with
- LandIntelA locked LandIntel parcel feeds the shell recommendation; with none, a neutral comparative shell is used.
- BOQ ProThe BOQ Pro take-off tool measures the DesignStudio plan saved in this browser (early).
- StructuraStructural model import is on the roadmap.
Pricing
Plans for DesignStudio
The same three plans apply across every Ferrum OS product — see the full breakdown on the pricing page.
FAQ
DesignStudio questions
No. It remains on the roadmap. The workspace is an INDICATIVE deterministic preview with bounded parametric door and window editing.