Wednesday
- last edited
Thursday
by
Laszlo Nagy
Thursday
Hi @Davor P,
This is so fun and effective. We shared it with some of our teams and people love it 🙂 Thanks for sharing!
Gordana Radonić
Community Manager
Thursday
hmmmm... fun... but for every rule "never ever under any circumstances", there's the "except when you are..." excuse
Friday - last edited Friday
@Gordana Radonic Glad you like it!
@Patrick M Yes, true but that is where it gets interesting!
Its a gag now but it could be something far more powerful.
Limit archicad layer blocking to only plan database.
Add SEO count check - allow say 50 or 100 interactions, anything beyond in the project either blocked or need admin approval.
Add polygon count - same as with SEO - if project already over polygon budget, put the brakes on adding more.
Exploding elements, creating too many sections, elevations - anything that can degrade performance should be flagged early.
Someone creates a section - log who so review later is easier.
Step further - have budgets and company standards set in a database outside Archicad where they can be assigned per company / project basis.
And we are working on an automated audit tool that runs from users Archicad every x days and pushes critical info to online database.
This is a system to detect and prevent issues before they spin out of control.