where would my firms documents end up (on whos servers) to do this checking? I dont know how any firm would just hand out their cd's just like that?
Or is being that lax normal these days?
Aside: this field is insanely frustrating, the chasm between clash detection and resolution is a right ball ache...between acc, revizto, and aconex clash detection (and the like)..the defacto standard is pretty much telling me x is touching y....great...can you group this crap intelligently to get my hi rise clashes per discipline from 2000 down to 10?
Can you navigate me there in revit (yes switchback in revizto is great) but revizto itself could improve.
Yes one of the biggest values of our system is reducing “noise.” Instead of surfacing 2,000 micro-clashes, we cluster findings into higher-order issues (e.g., “all conflicts caused by this duct run” or “all lighting mismatches tied to this dimming spec”). We’re not a BIM viewer yet, but we do map issues back to sheet locations, callouts, and detail references so teams can navigate directly to the real source of the problem.
Today the workflow is simple: users just drag-and-drop the full drawing/spec set (ZIP or PDFs) for whatever phase they want reviewed. The system automatically splits sheets by discipline, reconstructs callout relationships, and runs the checks. We’ll be adding integrations with ACC/Procore/Revit exports so this becomes even more automated.
Yes today users simply gather the sheets for whatever phase they want reviewed (DD, 80% CDs, 100% CDs, etc.), ZIP them or upload PDFs directly, and the system handles the rest. It auto-detects disciplines, reconstructs callout graphs, and runs checks across the full set. We're also adding integrations with ACC/Procore/Revit so sheet aggregation becomes automatic.
We store files securely on AWS with strict access controls, encryption in transit and at rest, and zero sharing outside the file owner’s account. Only our engineers can access a project for debugging and only if the customer explicitly allows it. We can also offer an enterprise option with private cloud/VPC deployment for firms that require even tighter controls. Users can delete all files permanently at any time.
Documents are stored on AWS with strict access controls, meaning they are only accessible to the file owner and, if necessary, our engineers for debugging purposes. After the check, users can delete the project and optionally permanently delete the files from our S3 buckets on AWS.
> I agree, can these scientists seriously go and do some real work?
This can be said about a lot of individual studies, but it leads to missing the wood for the trees. We need seemingly trivial studies because they accumulate towards a greater understanding of our world and ourselves.
Also you can’t have the big interesting surprise results unless you are testing something where the answer seems obvious. This study seems fine.
In same industry, our head of customer relations was asked recently, why did we award the job to x company? His reply hilatiously was: "i had lunch with him last, thats really how it works", made me chuckle. You must grease the wheels...always.
Interesting. I guess the loud music and high temperature in some clothing stores is meant to achieve the same. They look like methofs law inforcement would use in an hostage situation.
In my case it gives me the urge of leaving as soon as possible. I could see how it could create impulse buy but most of the time I go to a shopping mall, it is to be able to try out clothing before buying and I will just lose patience and go away if it doesn't fit well. I tend to avoid them as much as I can anyway.
Take this with a grain of salt as I'm in academia now, outside everyday software implementation in AEC, but I think that's changed / changing. My background is in the profession, and I'm a self-taught computational designer. Before going academic I built a lot of tools for small architecture firms, implemented BIM workflows for them, etc. So I talked to but didn't work with the tech tooling people at large AE or C firms. That said any time I look at the kind of software and tools being built at those companies, it seems like they've become increasingly comfortable with needing relatively full stack development.
Just one of many examples is how EHDD's EPIC [0]was successful enough to spin out [1]. There are a lot of others.
Or is being that lax normal these days?
Aside: this field is insanely frustrating, the chasm between clash detection and resolution is a right ball ache...between acc, revizto, and aconex clash detection (and the like)..the defacto standard is pretty much telling me x is touching y....great...can you group this crap intelligently to get my hi rise clashes per discipline from 2000 down to 10? Can you navigate me there in revit (yes switchback in revizto is great) but revizto itself could improve.