Skip to content
AEIS

Design leads and technical engineers

Choose the right AEIS product

Choose an AEIS product by engineering input, supported task, required deliverable, and execution boundary, including whether the work runs in the browser or on a licensed Windows worker.

Choose by task and deliverable

Select the AEIS product by the engineering input you control, the task you need completed, the deliverable a qualified engineer will review, and the required execution environment.

Prefer the smallest surface that can prove value against a real source. A focused technical case is usually a better first loop than a full delivery pipeline.

  • Name the source: IFC, Revit-prepared export, design case, or ETABS model.
  • Name the output: check result, schedule, SAFE/ETABS/PLAXIS stage, or report package.
  • Confirm whether the work is browser-only or needs a licensed Windows worker.

BIM Source products

Use BIM Source Review (IFC Viewer) to inspect model geometry, properties, and validation context before calculation begins. It is the right first step when the question is whether the BIM source is fit for another AEIS product.

Use Revit Data Preparation (AEIS Revit Plugin) to prepare Revit 2026+ data, shared parameters, exchanges, and IFC exports. It is a workstation integration, and the engineer still reviews the exported IFC before it becomes the source of truth.

  • IFC Viewer: browser workspace for inspection and validation findings.
  • Revit Plugin: Revit 2026+ workstation preparation and IFC export path.
  • Neither surface replaces engineer approval of the issued source.

Browser Design products

Use the Browser Design family for focused structural cases with explicit inputs and supported checks: Subframe Analysis & Design, Concrete Column & Wall Design, 3D Structural Analysis, Reinforced Concrete Beam Design, Steel Member Design, or Reinforced Concrete Joint Design.

Start from the input the engineer already controls—geometry, actions, reinforcement, member data, or batch cases—and confirm the implemented code or analysis scope before treating results as review evidence.

  • Subframe: editable structural cases, analysis diagrams, and design exports.
  • Pillar: column and wall checks with NM analysis and report exports.
  • 3D FEA: model build, validation, analysis views, and result artifacts.
  • RC Beam, Steel Design, Beam Column Joint Design: scoped member or joint checks with batch and export evidence.

Connected Delivery products

Foundation Analysis & Design, Excavation & Lateral Support Design, Superstructure Analysis & Design, and Column & Wall Load Scheduling coordinate multi-stage delivery. They connect inputs, licensed external-tool runs, checks, logs, and reports in one engineering record.

SAFE, ETABS, and PLAXIS stages cannot execute in the browser alone. They depend on a configured Windows worker and the licensed desktop engineering environment. Plan worker availability, run identity, and review gates before promising a delivery timeline.

  • Foundation Design: IFC build → SAFE run → checks, logs, and reports.
  • ELS Design: staged excavation data → PLAXIS run → design checks and calculations.
  • Superstructure Design: IFC build → ETABS run → C13 design and reports.
  • ETABS Load Schedule: ETABS models → load mapping → column and wall loading schedule.

Engineering AI Assistant

Engineering AI Assistant (AEIS Agent) helps engineers structure context, draft scoped plans, ask for missing inputs, and trace tool activity to artifacts. It uses the active engineering context and is not an autonomous designer.

The Agent does not approve, certify, or silently execute protected engineering actions. Protected desktop steps still require licensed worker availability and qualified engineer approval.

  • Use Agent to frame questions, surface missing inputs, and organize evidence.
  • Inspect the proposed plan before authorizing tool execution.
  • Keep acceptance, revision, and certification with the qualified engineer.

Browser workspace versus Windows worker

Browser modules—IFC Viewer and the technical design surfaces—run in the AEIS web workspace and are suitable when the engineer can complete the loop without launching SAFE, ETABS, or PLAXIS.

Worker-backed modules need the local Windows worker and the configured licensed applications. Treat worker connectivity, license state, cancellation, and failure handling as part of the engineering plan, not as IT afterthoughts.

  • Browser-first: IFC Viewer, Subframe, Pillar, 3D FEA, RC Beam, Steel Design, Beam Column Joint Design, Agent planning.
  • Worker-required stages: Foundation SAFE, Superstructure ETABS, ELS PLAXIS, ETABS Load Schedule generation.
  • If the first proof must avoid desktop tool coupling, pick a browser design module.

Define the first engineering case

Choose the smallest product that can prove value against a real source and a reviewable deliverable. A validated IFC inspection, one column or beam design case, or one foundation build-and-review sequence is stronger evidence than a broad automation claim.

Write the selection as a one-page brief: source revision, engineering task, product, execution boundary, acceptance artifact, and the engineer who will decide. That brief defines the controlled evaluation.

  • Prefer one source, one module, one acceptance artifact.
  • Match the module to the input you already trust.
  • Defer multi-module pipelines until the first loop is reviewable end to end.

All engineering guides

Apply this guide to your engineering case.

Use this to identify the product, source inputs, execution requirements, and review questions for a defined evaluation case.

Request a demo