IFC Model to ETTV Submission
The calculation was never the slow part
Areas, orientations and component types come straight out of the IFC, so nobody is scaling off elevation drawings or retyping numbers into a spreadsheet.
Mullions, thermal breaks and curved panels are calculated discretely instead of being simplified into a flat box, so you report the ETTV result without an excessive margin in the glazing spec.
One export gives you the Excel ETTV report plus annotated plan and elevation PDFs, so the drawing mark-up that used to be its own job is already done.
Every result traces back to the instances behind it and the shadow view shows what's shading each panel, which matters when the calculation goes out under your licence.
Turn your model into an ETTV report.
What NimbleFaçade computes for you
NimbleFaçade turns your BIM model into a submission-ready ETTV report, so proving your facade meets code stops being a manual job.
Every facade module carries a value, not just the building as a whole.
Options tested before they are drawn, against the same set of assemblies.
Output formatted for submission, so the paperwork stops eating the design time.
Questions about NimbleFaçade
Two modules are live today, and they share one index of your project data:
- NimbleFaçade, for ETTV reporting and envelope compliance.
- DocuMentor, for automated audits across document sets.
- Both read the files your team already produces.
- Further modules build on the same data layer.
You can start with one and add the other without re-indexing anything.
Sid reads the model and document set you already produce. There is no migration:
- Point Sid at a collection and it indexes the files.
- It runs the audits you choose.
- Results trace back to the source document.
- Your data stays in your environment.
Nothing about how your team models or documents has to change.
Work that used to take a fortnight of someone's time now runs in an afternoon:
- ETTV computed per orientation.
- Every facade module carries a value.
- One assembly library across studies.
- Output formatted ready for submission.
The time saved goes back into the design rather than the paperwork.
You do. Sid processes your project data, it does not acquire it:
- Files stay inside your environment.
- Nothing is used to train shared models.
- Access follows your existing permissions.
- Results are exportable at any time.
If you stop using Sid, your data and your outputs remain yours.
Placeholder answer. Most teams are running their first audit inside a day, because Sid indexes the files where they already sit.
Placeholder answer. No. Sid reads the model and document set your team already produces.
Placeholder answer. Envelope compliance is computed to the code set for the project market.
Placeholder answer. Inside your own environment. Sid processes your project data, it does not take custody of it.
Placeholder answer. Pricing is per project, and scales with the number of modules you run.
Placeholder answer. Yes. We run a pilot on one of your live projects before any commitment.
