AEIS
Connected Engineering Software
Connect AEIS to engineering software.
AEIS coordinates configured CSI SAFE, CSI ETABS, and Bentley PLAXIS stages on a licensed Windows worker. RC Beam Design and Concrete Column & Wall Design also export directly to PROKON C01 and C13 formats from their AEIS cases.
One controlled sequence
Keep the worker run connected to the case.
External software remains in the licensed desktop environment where required. AEIS also produces controlled exports from its browser-design cases.
- Source and scope
Prepare the case
Start with an approved BIM source or engineer-reviewed model and named assumptions.
- Execution or export
Configure the stage
Confirm whether the selected stage uses a licensed worker and API or a controlled export format.
- Connected run or export
Execute or export
Run the external engineering software through its configured API or generate the selected controlled export while AEIS records the case state and artifacts.
- Evidence and acceptance
Review the outcome
Review extracted results, checks, reports, and decisions against the same engineering record.
Configured integrations
Use the right external tool for the stage.
Choose the software stage or export format that matches the engineering task, then move into its AEIS delivery product.
CSI SAFE API
AEIS builds supported foundation inputs, coordinates the configured SAFE run, and keeps results, checks, logs, and reports tied to the same source record.
CSI ETABS API
AEIS coordinates configured ETABS analysis stages and can use reviewed ETABS models for superstructure delivery and column-and-wall load schedules.
Bentley PLAXIS Remote Scripting API
AEIS connects staged excavation inputs and engineering checks to PLAXIS execution through the configured remote-scripting API.
PROKON C01 and C13 exports
RC Beam Design exports PROKON C01 files, and Concrete Column & Wall Design exports PROKON C13 files. Each export remains tied to its AEIS design case and engineer-reviewed inputs.
Operating boundary
Configured software and export workflows, engineer-owned decisions.
Worker availability, API readiness, and export compatibility are implementation requirements, not background infrastructure.
- SAFE, ETABS, and PLAXIS must be installed, licensed, and configured on the Windows worker before the corresponding stage can run.
- PROKON C01 and C13 exports are generated from the corresponding AEIS browser-design case; opening and reviewing them in PROKON remain engineer-controlled.
- AEIS records the selected source, execution state, logs, results, and generated artifacts around the external-software stage.
- The qualified engineer remains responsible for model setup, assumptions, result interpretation, design decisions, and final acceptance.
- AEIS does not claim a vendor partnership, certification, or replacement for the connected engineering software.
Evaluate one connected engineering case.
Bring one source, one intended software stage, and one reviewable output. AEIS will confirm the worker, licensing, execution, and engineer-review requirements.