Skip to content
AEIS
Building foundation cutaway showing pile caps, deep piles, soil layers, and structural load paths

Connected Delivery / Foundation Design

Foundation Analysis & Design

Connect IFC foundation build data, SAFE runs on the Windows worker, foundation checks, logs, generated files, and reports into one delivery record from BIM source to design deliverable.

Best for
Foundation engineers coordinating IFC build data, SAFE execution, checks, and deliverables.
Outcome
A connected foundation record spanning IFC build artifacts, SAFE run state, checks, logs, and foundation design reports.
Runs in
Browser workspace + Windows worker - SAFE required for run stage
Requirements
Build and design use the AEIS worker; SAFE execution requires the configured licensed desktop environment.
AEIS Foundation workspace showing SAFE run controls and operation status
Controlled Windows worker evidenceA configured Windows worker handles licensed tool stages, with run state, logs, and outputs attached. Primary signal: Run state, logs, outputs.

Evidence surface

Inspect the working evidence.

Review the product capture, then use the checklist for what a qualified engineer can verify before handoff.

  • IFC Build stage for foundation geometry
  • SAFE Run on the licensed Windows worker
  • Foundation checks and logs
  • Design reports linked to the run
Engineer boundary

SAFE execution cannot run in the browser alone and depends on the licensed worker environment; soil assumptions, model setup, results, and foundation acceptance remain engineer-reviewed.

Product details

Inputs, steps, and deliverables.

Connect IFC foundation inputs, SAFE execution, checks, logs, and design reports.

Inputs

  • IFC foundation source
  • Optional soil-spring workbook
  • Build and design options
  • SAFE run configuration on the licensed worker

Steps

  1. Build foundation inputs from the IFC source
  2. Configure design options and optional soil-spring data
  3. Run the SAFE stage on the licensed Windows worker
  4. Review checks, logs, extracted results, and reports

Outputs

  • SAFE input files from the build stage
  • Run logs and extracted results
  • Foundation design reports
  • Checks and artifacts tied to the same record

Value and use

Why teams use Foundation Analysis & Design.

What this product is for in practice, and the engineering situations teams bring into AEIS first.

Value

  • Build foundation inputs from IFC before SAFE execution
  • Run SAFE on a licensed Windows worker with attached logs
  • Keep checks, reports, and artifacts on one engineering record

Use cases

  • Build a raft or pile-cap foundation model from IFC
  • Run SAFE with optional soil-spring inputs
  • Review foundation checks after the analysis stage
  • Issue reports tied to the producing run and source

FAQ

Before you evaluate this product.

Common questions about Foundation Analysis & Design, execution requirements, and engineer responsibility.

Can SAFE run in the browser?

No. SAFE execution requires the configured licensed desktop environment connected through the AEIS Windows worker. Build and design coordination use the AEIS workspace around that stage.

What stays engineer-reviewed?

Soil assumptions, model setup, results interpretation, and foundation acceptance remain with the qualified engineer.

What enters from BIM?

IFC foundation source data drives the build stage; optional soil-spring workbooks can supplement the run configuration.

Evaluate Foundation Analysis & Design on your engineering case.

Describe the foundation analysis & design inputs and required deliverable. AEIS will confirm product fit, execution requirements, and the engineer-owned acceptance point.

Request a demo