A clearer path to your first model.

Get to know the workflow, the model handoff, and the role of engineering review. Search by a topic, tool, or question.

14 questions

The platform

What does NodeSnap do?

NodeSnap prepares LIRA-SAPR analytical models from ArchiCAD architectural exports, compares converted elements with their source, and keeps the model connected to design revisions. Its three core capabilities are automatic conversion, revision sync, and element-level verification.

Which tools does NodeSnap connect?

The core workflow connects ArchiCAD to LIRA-SAPR through SAF and IFC exchange. If your team uses another tool, contact NodeSnap to discuss the workflow rather than assuming it is a supported integration.

Which file formats can I start with?

NodeSnap’s stated input formats are SAF and IFC exported from ArchiCAD. For a particular file version or project setup, discuss your export workflow with the team during a demo.

Do I need an extra ArchiCAD plugin?

The workflow is designed around SAF and IFC exports without an extra plugin or special modelling rules. The source still needs to represent the architectural project you intend to hand over.

Conversion and review

What information is carried into the analytical model?

NodeSnap reads geometry, sections, materials, and supports, then prepares the analytical skeleton. Junction resolution, node snapping, and member alignment help connect the model before engineering review.

What does element verification check?

Converted elements are compared with the source for geometry, axis alignment, section, and material. Discrepancies are flagged for review before analysis.

Does NodeSnap run structural analysis for me?

No. NodeSnap prepares and checks the analytical model for the LIRA-SAPR workflow. The engineer continues the analysis and remains responsible for assumptions, review, and final design decisions.

Does source verification prove code compliance?

No. Source verification compares the model with the architectural information behind it. Code-specific analysis, design checks, and project requirements still need to be addressed by the responsible engineer.

Revisions and design context

What happens when the architect changes the design?

NodeSnap compares the revised upload with the previous source, identifies changed elements, and updates those elements instead of rebuilding the entire analytical model.

What happens to my loads and assumptions?

Revision sync is designed to preserve existing loads and assumptions while updating changed elements. The engineer should still review whether a design change affects those assumptions.

Which design-code contexts are listed?

NodeSnap is built first for engineers working across Eurocode 2, Eurocode 8, and Georgian seismic norms PN 01.01-09, with SNiP-compatible documentation also listed as a design context.

Getting started

How do I arrange a demo?

Open Book a demo and describe your team and workflow. The page prepares an email draft to contact@nodesnap.tech for you to review and send. The request is a conversation starter, not an automatically confirmed booking.

What should I include in a demo request?

Your role, the tools you use, whether you usually exchange SAF or IFC, and the part of the workflow you want to improve. A short explanation of your modelling and revision process is enough to start.

Where can I discuss pricing or project requirements?

Contact the NodeSnap team at contact@nodesnap.tech. Describe your team’s workflow and project requirements so the discussion is grounded in your use case.

FROM DESIGN TO ANALYSIS

Your question is more specific?

Tell us about the project and workflow you have in mind.

Contact the team