Skip to content
AEIS
Sign inRequest access

Contact

Talk to AEIS about product fit, security, or support.

Describe the approved source, engineering task, required deliverable, and any Revit, SAFE, ETABS, or PLAXIS dependency. No project file is required for the first conversation.

Contact paths

Choose the right contact path.

A useful first message names the source, engineering task, required deliverable, and any external engineering tool involved. Choose the contact path that matches your need.

Workspace access

Use the structured intake when you have a BIM or IFC source, engineering question, or representative deliverable. Access remains invite-only after technical scoping.

Request access

Product questions

Ask which product fits your source, engineering task, external tool, and required deliverable, including browser or Windows worker requirements.

Ask a product question

Product support

Report an access, session, product, worker, output, or implementation issue with enough context to reproduce it.

Contact product support

Before you write

Send enough evidence to act.

Include a source revision, screenshot or error reference, product name, expected result, and whether a local engineering tool is required. Never send passwords or verification codes.

  • The approved BIM/IFC source revision, design case, or current report you want to improve.
  • The engineering task: check, analysis run, handoff, or deliverable your team needs.
  • Whether Revit, SAFE, ETABS, PLAXIS, or browser-only products are part of the case.
  • The expected output a qualified engineer would inspect and accept.
  • For support: module name, screenshot or error reference, and steps to reproduce.

Response expectations

Clear scope leads to a useful response.

AEIS workspace access is invite-only. Evaluation requests go through technical scoping before any licensed-email invite. Product and support messages are answered once there is enough context to act.

Security and data questions

For deployment, session, worker, or data-handling review, start with the Security & Data Handling page, then email a specific boundary question. Do not attach confidential project files or credentials.