Typical Floor: When 22 Floors Are Marked in One Pass
In PDP, we improved the UX for repetitive structures: if floors 3–24 in a 25-story building are identical, why should an inspector do the same thing 22 times? No need — now there’s a typical floor.
In PDP, we improved the UX for repetitive structures: if floors 3–24 in a 25-story building are identical, why should an inspector do the same thing 22 times? Spoiler: they shouldn’t
We built a typical floor flow: a specialist marks rooms, issue markers, and axes on one floor once — and the system applies it to all identical floors. In practice, it’s like DRY in development, only for building markup.
What this gives us:
• saves dozens of hours of manual work • less routine work and fewer chances for human error • cascading updates: change the template — all related floors are updated
This is the kind of UX that doesn’t make noise, but does save deadlines. Especially now, when everyone in IT is chasing automation and an AI-first approach: sometimes the best “smart” tool is simply removing pointless repetition.
We like features like this ourselves: less copy-paste, more real value