AEISImplementation
Implementation Options
AEIS engagements are scoped around engineering inputs, supported products, execution requirements, deliverables, and the team responsible for review. Prices are quoted after technical scoping rather than published as generic seat rates.
Engagement models
Choose the support your team needs.
Compare a focused evaluation, a team implementation, and an enterprise rollout. Licensed tools, Windows workers, reporting depth, and onboarding vary by engineering case.
| Engagement | Best for | Expected deliverables | Implementation shape |
|---|---|---|---|
| Evaluation | A technical lead or design engineer testing one defined BIM-driven case against real project evidence before wider rollout. | Source assessment, product fit map, supported check and execution scope, evaluation findings, and a clear go / no-go boundary. | One approved source, one module or delivery path, and one expected engineering outcome a qualified engineer can inspect. |
| Team Implementation | A delivery team standardizing a repeatable source → check → run → report sequence across shared project work. | Product configuration, report alignment, team onboarding, operating guidance, and agreed acceptance criteria for the first production case. | Configured products and worker stages for an agreed team process, with named execution and review responsibilities. |
| Enterprise | An organization coordinating multiple disciplines, licensed tools, governance requirements, and phased adoption across teams. | Multi-product implementation, governance model, operational controls, support model, and staged rollout plan. | Phased adoption across agreed teams, modules, execution environments, and reporting standards. |
Package includes
What each option includes.
Each option describes what is included in scope, not a public price list. Final commercial terms follow the products, execution environment, and support required.
Evaluation
Prove fit on one approved BIM source, one defined engineering case, and one deliverable a qualified engineer can inspect.
- Source assessment for one IFC/BIM or design case
- Product fit map (browser service vs Windows worker)
- Code-check and execution scope for the chosen path
- Access scoping before any workspace invite
Team Implementation
Configure AEIS around a delivery team that needs repeatable source → check → run → report sequences.
- Product configuration for the selected engineering tasks
- Report and artifact alignment to team standards
- Team onboarding on engineer control boundaries
- Repeatable run and review sequence for the delivery unit
Enterprise
Coordinate multiple engineering processes, governance expectations, licensed external tools, and support across delivery units.
- Multi-product implementation across design and delivery
- Governance model for approvals and protected actions
- SAFE / ETABS / PLAXIS worker coordination where required
- Support model matched to rollout depth
Qualification
Define success before implementation.
Technical scoping starts with an approved source, a defined engineering task, a required deliverable, and the execution environment needed to produce it.
Choose the product
Start with BIM Source, Browser Design, Connected Delivery, or AI Assistance.
Provide source context
Use an IFC/BIM source, design question, sample report, or current analysis target.
Identify execution requirements
Identify whether the engineering case uses SAFE, ETABS, PLAXIS, browser design, or AI assistance.
Set implementation scope
Implementation scope follows source context, product requirements, reporting needs, and team responsibilities.
FAQ
Common commercial questions.
Honest answers about why prices are not listed, what Evaluation needs, how Team Implementation differs, and where engineer approval stays mandatory.
Why are plan prices not listed?
Licensed tools, Windows worker deployment, reporting depth, and implementation support vary by engineering case. AEIS quotes after technical scoping, not seat-count estimates.
What do you need for Evaluation?
One approved BIM or IFC source (or a clear design case), one engineering question, and one expected output a qualified engineer can inspect.
How does Evaluation differ from Team Implementation?
Evaluation proves fit on one defined engineering case. Team Implementation configures a repeatable source-to-report process for a delivery team.
Does AEIS replace engineer approval?
No. AEIS is a tool-only platform. Qualified engineers remain responsible for inputs, assumptions, calculations, outputs, and final deliverables.
Discuss your AEIS implementation.
Provide one approved source and one required deliverable. AEIS will identify the relevant products, execution requirements, review boundary, and implementation option.