01 / 05 · openBIM, in the browser
ZEROBiE: openBIM in the browser. Your IFC, open on any screen.
Your IFC, open on any screen.
Keep scrolling and watch a real 343 MB model put itself together, right here in your browser. That's the whole idea: the heavy file is converted once, so nobody on your team installs a thing.
Now building
±0.0 m
Two minutes · every module
One building. One identity. Every app.
The whole platform in one take: files, checks, requirements and the model, all talking about the same element.
01 · The context
Six reasons BIM work is harder than it should be.
Turn a card over to see what ZEROBiE does about it - today, not on a roadmap.
- Problem 01Locked formatsProject data gets stuck in proprietary files.What ZEROBiE does todayIFC is the working format here, not an export. What you upload is what you download.See how
- Problem 02Licences everywhereEvery collaborator needs the right software just to look.What ZEROBiE does todayAnyone you share a project with opens the model in a browser. No install, no plugin.See how
- Problem 03Workstation-boundBig models need big machines, so the site and the tablet get left out.What ZEROBiE does todayThe heavy conversion happens once on our servers. The 343 MB tower at the top of this page runs in your browser.See how
- Problem 04Twelve toolsViewing, checking, requirements and files all live in different apps.What ZEROBiE does todayViewer, CDE, checks, requirements and element history share one project and one record.See how
- Problem 05Version by emailFiles travel by email and shared drives, and nobody is sure which is current.What ZEROBiE does todayEvery revision is kept, every state change is recorded, and the record is sealed so edits after the fact show.See how
- Problem 06Open standards, unusedIFC is an international standard (ISO 16739), yet it is treated as an afterthought.What ZEROBiE does todayIFC2X3, IFC4 and IFC4X3 are read natively, requirements travel as IDS, and checks follow buildingSMART's published rules.See how
02 · The drawing set
One place for the model, and everything said about it.
Six tools that share one project, one set of files and one record of who did what. Every sheet is drawn from the same real building - move over one and the print comes to life.
3D Viewer
Open the model. Not a screenshot of it.
- Section, measure and isolate in the browser
- Click any element for its properties
- Nothing to install, ever
CDE
One home for files, revisions and the people who touch them.
- WIP → Shared → Published → Archived
- Every revision kept, every change recorded
- Roles per project, previews for everyday files
Assure
Find the problems before your client does.
- Quality rules, grouped by severity
- IFC checks against buildingSMART's published rules
- Each result dated and kept in History
IDS Ruler
Write your requirements once. Check every model against them.
- Rules without hand-written XML
- Import and export standard IDS files
- Results that name the element
Element history
Every wall remembers where it has been.
- One element across every model version
- Its findings, resolved ones included
- Who changed what, and when
ZI assistant
Ask how, get the page that explains it.
- Answers quote the handbook, with sources
- Project data only if you switch it on
- Off by default. Your call.
03 · Try to cheat
Go on. Quietly change the record.
Every recorded event in a ZEROBiE project is sealed together with the one before it. Change one word in any link and watch what happens to everything after it.
Chain status
INTACT
An illustration running in your browser with made-up events. The real record is sealed inside the database as each event is written; the application never computes a seal, so it can't forge one.
09:02
#1
Anna (architect)
prevgenesis
b9024d30…013asealed09:40
#2
Anna (architect)
prevb9024d30…013a
683028f7…1d53sealed11:15
#3
Tom (structures)
prev683028f7…1d53
0790a022…69c8sealed14:30
#4
Priya (info manager)
prev0790a022…69c8
6a35f1ff…37fasealed16:05
#5
Priya (info manager)
prev6a35f1ff…37fa
674956e4…94e8sealed
04 · Straight talk
What we say about ISO 19650. And what we won't.
Plenty of software says it's certified. Here's the honest version, so you can quote us in a tender without a lawyer wincing.
State 1 · WIP
Work in progress
Still being worked on. Not for anyone to rely on yet.
State 2 · S
Shared
Out for coordination. Others can look and comment.
State 3 · P
Published
Approved for use. This is the one to build from.
State 4 · A
Archived
Kept for the record. Never quietly deleted.
- S-01
Designed to support information management in accordance with BS EN ISO 19650-2.
- S-02
A CDE with an ISO 19650-shaped workflow: WIP, Shared, Published, Archived.
- S-03
Models are checked against buildingSMART's published IFC rules, reported in four separate layers.
- S-04
IFC-native: IFC2X3, IFC4 and IFC4X3. Open formats in, open formats out.
- “Certified to ISO 19650”
NoteISO writes standards and certifies nothing, so that badge can't exist - whoever offers it.
- “Fully compliant CDE”
NoteConformity belongs to the appointing and appointed parties and their own processes. Software can help; it can't hold it for you.
- A score with no date
NoteA check result means little without the ruleset it used and when it ran. Ours always carry both.
05 · Open by default
Your data was never ours to lock up.
openBIM isn't a badge we add at the end. Open formats go in, open results come out, and nothing in between holds your information hostage.
IFC2X3
Read natively
IFC4
Read natively
IFC4X3
Read natively
IDS
Your requirements, imported
Your files
Byte for byte, as uploaded
IDS
Exported in the open format
4-layer report
Never averaged into one number
The model
Light enough for any browser
06 · The vision
One core. Everything else in orbit.
Every capability works from the same model and the same record. The inner ring is live today; the outer ring is where ZEROBiE is heading.
Planned
07 · Who it's for
Built around the people in an appointment, not around a feature list.
Pick a role. Illustrative scenarios - not customer case studies or measured results.
Information managers
Set the rules once. Let every model meet them.
- 1Write the project's information requirements in the IDS Ruler - no XML by hand.
- 2Every model that arrives is checked against them, and against buildingSMART's published IFC rules.
- 3Files move WIP → Shared → Published with each decision recorded, by whom and when.
08 · Your turn