Engineering Data Management & Integration Hub
A shared source of asset data. PBS, GBS, and FBS structures, master data, and integrations.
Start with a priority workflow. Connect data, documents and project controls — then expand as your project evolves.
Twelve modules across four capability groups. Explore the scope and build a shortlist for your project discussion.
12 solutions
Add modules to your project scopeA shared source of asset data. PBS, GBS, and FBS structures, master data, and integrations.
Revisions, approvals, and attribute search. Current documentation for the whole team.
Contractual and regulatory requirements, RACI roles, and RTM traceability matrices.
Project baselines, revisions, and releases. Asset configuration at a selected date.
ECR/ECN tracking and change impact on design, schedule, and cost.
BIM model synchronisation, browser-based 3D viewing, and multidisciplinary clashes.
Connect model and time: work progress and the critical path in 3D.
Planned, actual, and forecast costs linked to the asset structure and physical progress.
ITP inspections, mobile checks, and defects linked to the 3D model.
Track purchase orders through FAT/SAT. Vendor surveillance and digital quality dossiers.
NCR registration, corrective actions, and root cause analysis.
Official correspondence, claims, meeting minutes, and interface requests.
Try another term or reset the filters.
Module scope and AI capabilities follow IMECO, pp. 7–10. Readiness and commercial terms are confirmed separately.
The IMECO reference architecture combines modular services, an embedded AI layer and FDSE-led integration.
C# (.NET Core) and Node.js (TypeScript), with Microsoft SQL Server and PostgreSQL support.
Bentley iTwin.js for BIM, IFC and point-cloud navigation. Telerik UI on ASP.NET / Blazor for enterprise portal interactions.
Internal AI services API using Large Language Models and Retrieval-Augmented Generation for cross-module intelligence.
This is the stack described in IMECO, not a live integration status or the frontend stack of this website.
The presentation describes three adoption phases — from an individual priority module to the full ecosystem.
Choose a high-priority standalone module: DocM for technical documentation or RM for requirements and regulatory compliance.
Add BIM Twin, 4D Schedule or Site QC as the project advances from design into construction.
Integrate all twelve modules into a single data-centric environment for asset lifecycle control.
These controls only add modules to your local enquiry scope. They do not purchase software or define a commercial package.
Explore consulting, FDE and FDSE — the delivery models described alongside the platform.
Yes. The presentation explicitly allows clients to purchase and deploy individual modules without acquiring the full suite. A specific deployment scope and commercial proposal still require confirmation.
No. Module descriptions reproduce the AI capabilities in the IMECO presentation. The website provides a catalogue, an illustrative model and a local scope builder; it does not call those AI services.
Selected modules are kept in this page’s memory only. You can review them, download the scope as a text file or include it in a local enquiry. No order is placed, no personal data is submitted and no price is calculated.
Describe the workflow, current systems and project stage you want to connect.
Solution scope: IMECO (2).pdf, pp. 7–11 and 13. Reference architecture; module readiness and availability under REBARIO require confirmation.