Warren reads the floor you have open — the rooms, the doors that truly join them, the walls that only touch — and draws the network six ways, metro map included. It audits what the plan cannot show: rooms with no way in, single points of access, doors that break your security cascade. Then it exports a page anyone can edit without Revit, and brings every change back under review.
A floor plan answers “where is it?”. It cannot answer “what does it connect to?”, “can this room be reached at all?”, or “does any door jump the security cascade?” — those live in the topology.
Reading and Analyse write nothing. The diagram, the page and the parameters all leave through named, gated writes — and everything that comes back is previewed, ticked and undoable.
Tap Input or Output to isolate a half — the other collapses.
Warren scans the active floor plan — or borrows the lowest one and says so. One window, one floor; “Whole building” rescans every floor joined by stairs, ramps and lift shafts.
The scan reads placed rooms, the doors that truly join them — phase-resolved — openings, shared-wall adjacencies and the vertical links. The footer always states its ground: level, view, phase, and the counts of rooms, doors, adjacencies and ways in. Caveats are amber and permanent, because a diagram missing edges that does not say so is worse than no diagram.
Six engines, one scan. Metro runs routes as parallel lanes, corridors as track rather than stations. Plan anchors every node to its room's real centroid, so the scheme still looks like the building. Spine hangs each room off the corridor it truly opens onto. Onion rings the most protected value at the centre, where a jumped door reads as a chord. Bubbles sizes rooms by area to weigh the brief. Section stacks floors and draws the stairs sewing them. All deterministic: add a door and nothing else moves.
Revit does not record which rooms are corridors, or which route a room is on — so Warren asks, once, with four honest modes: with a rule, by picking rooms, letting Warren guess, or nothing yet. The amber banner appears only while something is genuinely unsaid — “Warren is guessing which rooms are circulation.” — and creating the eight route parameters is a named transaction behind a consent dialog that says it plainly: Warren never syncs; you decide when this reaches the central file.
Telling Warren what a corridor is settles the meaning. This settles the extent. The default is every room at the same height as the plan Warren was opened on — all its blocks and wings, which is what a floor diagram usually means — but a tower with a podium, or a scheme split into phases, does not. So the room list is filterable by name, number, level or any shown column, it can take whatever you have selected in Revit right now, and it can show more parameters of each room so the choice is made with something better than a name.
Four kinds of line, and each says what it means before you style it: a door you can walk through, a free opening with no leaf, an adjacency where two rooms share a wall and nothing opens, a stair, ramp or shaft. Weight and pattern are per class, shown as the real line and counted — a class with none in this diagram says so. Colour belongs to the route, and the route's name is yours: relabel Patient as Airside and the parameter stays BIMIO_Route_Patient, so tagged models keep working.
A line only appears when the model says so. Change how each one looks and the drawing changes with it.
What you call this route. Only the label changes — the Revit parameter keeps its name, so models you have already tagged still work.
Analyse is pure graph arithmetic — no transaction, no Revit hop: rooms with no door at all, rooms whose doors no path from outside ever reaches, and choke points — “Close it and 4 rooms lose all access from outside.” The cascade rule — no door jumps more than one step of your ordered parameter — runs only once you have ordered the values with Order…; until then the summary says the cascade was NOT audited, instead of implying a pass.
Reading and Analyse write nothing. Everything Warren writes — the drawn diagram, the route parameters, the room values — leaves through a named, gated transaction; and room-parameter writes share one pipeline with a fresh-value guard that skips instead of overwrites.
The diagram lands in Revit where you decided before pressing. The page travels to people without Revit. And what returns is reviewed, not trusted.
The destination is picked before pressing: a drafting view Warren creates and owns, or a legend you already have. “BIMIO Warren — draw diagram” commits or reports the rollback, and stamps its provenance — so Check drawing can later compare every drawn view against today's model and answer plainly: 2 of 3 drawn views no longer match the model, with each view's verdict in the register's own words — out of date on the diagram, edits not written back, conflict, orphan.
A node is an editable cell. With a parameter chosen in Colour by, the selected room offers the values already in play on the floor and takes a new one; edits stack into a queue that states outright that nothing has been written. Write to model sends the batch through the same named transaction the import uses, with the same fresh-value guard inside it — anything skipped keeps its row and its reason instead of vanishing. The same card marks a room as circulation, redrawing it as a trunk.
Export HTML makes a self-contained page where only the on-screen parameter is editable; its “Download changes” file carries each value as it was when the page was made. Import re-reads the model first and refuses to compare against a stale scan; every change arrives with a verdict, conflicts arrive unticked, and a file that names another model demands the explicit tick — “Yes, this file is meant for the model open here.” The write is one named transaction with a fresh-value guard: 7 parameters written, 3 skipped says exactly what happened.
Every drawn region carries a stamp naming its room and the value it stands for, so repainting one in another value's style is a statement Warren can read. Check drawing turns it into a proposal, never a write, and names which side moved: the model, the drawing, or both to different things — a conflict it refuses to settle by recency. A style that maps to no single value is called untranslatable rather than guessed, and with a workset closed it declines to judge at all.
This is an actual HTML report Warren exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Warren ships on the Data panel of the BIMIO tab. Scan the floor, audit the connections, and let the scheme travel — with a review gate on the way home. Revit 2024–2027, full trial, no card.