UPLOADED
The browser received the selected file and computed its identity.
Upload says nothing about format validity, geometry, coordinates or approval.
Ferrum Projects
LIVETell us about your project in five short steps. The team reviews it and contacts you.
An enquiry is not a quote or a contract.
Project enquiry
LIVEA five-step enquiry at /build/start sends your project details to the Ferrum team, who review it and contact you. An enquiry is not a quote or a contract, and no price is shown.
Start the enquiryFerrum Build website
LIVEPublic pages at /build describe the services, sectors, construction systems and delivery process the Ferrum team offers. They are information pages; the project workspace for signed-in project members is at /build/projects.
Visit Ferrum BuildDesignStudio · OpenBIM intake
Local browser processingSelect 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
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.
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
The browser received the selected file and computed its identity.
Upload says nothing about format validity, geometry, coordinates or approval.
A visual preview was created for a specific checksum.
Rendering success does not establish geographic, dimensional or engineering validity.
Parsing completed, but required evidence or professional checks remain open.
Downstream release remains blocked.
Required intake checks passed against project control and warnings were reviewed.
Validation records reviewer, evidence, date, tolerance and limitations.
A named authority approved a validated revision for a stated machine workflow.
Approval is revision-specific and revoked by affecting changes.
The file failed intake or was rejected by a reviewer.
Rejected revisions cannot supply downstream work.
Machine release
BLOCKED · 0 / 6
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.
Public pages at /build describe the services, sectors, construction systems and delivery process the Ferrum team offers. They are information pages; the project workspace for signed-in project members is at /build/projects.
A five-step enquiry at /build/start sends your project details to the Ferrum team, who review it and contact you. An enquiry is not a quote or a contract, and no price is shown.
Signed-in project members raise, assign, start, resolve, verify, close and reopen project issues in the issue register at /build/projects, and site work orders carry assignees. Sign-in and project membership are required. A general-purpose task list separate from issues and work orders is not built.
Signed-in project members record quality hold points with checklists, inspections and engineer sign-off in the Quality tab at /build/projects, keep daily site logs in the Site tab, and raise safety concerns as safety issues in the issue register. Sign-in and project membership are required. Dedicated HSE checklists, safety inspections and permit-to-work are not built.
Signed-in project members plan package stages and record actual starts and completions in the Schedule tab at /build/projects; a stage with a hold point completes only when its QC pass is linked, and clients see a client view of the same schedule. Sign-in and project membership are required. Automatic progress capture from photos, drones or sensors is not built.
Site engineers record measured work against work-order lines in the Site tab at /build/projects, and the Billing tab builds running-account (RA) bills only from those certified measurements, alongside milestone invoices and payments. Sign-in and project membership are required; measurements that cannot be billed exactly are listed as unbillable rather than rounded.
On the roadmap (26)
ROADMAPFive short steps at /build/start. No price is shown.
The Ferrum team reviews the enquiry and gets in touch.
Tasks, RFIs, QA/QC and billing in one workspace.
Pricing
The same three plans apply across every Ferrum OS product — see the full breakdown on the pricing page.