About
Bentley's digital-twin platform and cloud services (the engine behind Bentley Infrastructure Cloud). Federates infrastructure engineering data into iModels via the Synchronization API; Bentley design apps like MicroStation publish/sync DGN design models into an iTwin for validation, clash detection, and digital-twin deliverables.
How teams use it
By audience
- BIM Manager
- Federates DGN, IFC and RVT models from several design teams into one iModel, so coordination runs against a single versioned container rather than a folder of exports.
- Runs geometry clash detection through the Validation API instead of round-tripping models into a separate coordination tool.
- Changesets between milestones show exactly which elements moved and in whose model, which is the audit trail model coordination usually lacks.
- Civil Engineering
- Publishes OpenRoads and OpenBridge design models into an iTwin for corridor and structure review without leaving the Bentley toolchain.
- Combines survey, reality-capture and design data in one twin so design intent can be checked against existing site conditions.
- IT & Systems Administration
- Provisions users, projects and organisation membership through the Administration API instead of per-application admin consoles.
- Reporting & Insights API feeds iTwin data into the firm's own BI stack, so infrastructure metrics do not have to live in Bentley dashboards.
- Workflow Automation API publishes iTwin events, which is how internal systems get notified of model changes without polling.
- Owner/Developer
- Carries a maintained digital twin past handover so asset data stays queryable through the operations phase.
- Reviews issues and design changes in a browser, with no Bentley desktop licence needed for stakeholders who only need to look.
By phase
- Design
- Design teams sync in-progress models continuously, so clash and rules checking happens between milestones rather than only at them.
- Reality Capture APIs bring scan and photogrammetry data alongside the design model during option development.
- Construction
- Schedule data attaches to the twin through the Project Scheduling API, giving 4D comparison of built progress against the plan.
- Field issues raised through the Review APIs resolve against the specific model element rather than a drawing reference.
- Closeout & Operations
- The as-built twin becomes the operations record, with reality capture re-synced over time to track asset condition.
- Asset data federated during design and construction stays addressable by the owner's maintenance systems instead of being flattened into PDFs at handover.
Integrations (3)
| Integrates with | Connection | Details |
|---|---|---|
| NativeiTwin Viewer (CupixWorks SiteView) | ||
| NativeiTwin Synchronization (DGN → iModel) | ||
| NativeVIKTOR OAuth 2.0 integration against a registered Bentley Web App (itwin-platform scope) |
Only partners listed on AECi appear here. If one is missing, suggest a correction.
Reviews
No reviews yet — be the first to review this product.
Directory updates
Know when new tools and reviews land
AEC Integrations is live and still growing. Add your email for occasional updates as we expand the directory with new tools, integrations, and reviews.