What is AVEVA AIM?
AVEVA AIM, or AVEVA Asset Information Management, is AVEVA’s solution that aggregates information from multiple sources and in varying formats, so teams can access, visualize, validate and collaborate on trusted asset data. AVEVA says AIM integrates validated data across engineering, operations and maintenance to power the digital twin, and that it creates one common location for documents, 3D models, reporting and laser scans.
The points AVEVA’s product page highlights are:
- Aggregation of data from many sources and formats, linking documents, tags and models.
- Milestone handovers between EPC and owner, to speed up operational readiness.
- Reports on data quality, consistency and completeness, for compliance and handover.
- Information standards such as CFIHOS, ISO 15926 and ISO 14224, applied through AVEVA Information Standards Manager.
- Integration with Assai document control, which handles revision flows.
- Cloud, hybrid or on-premises deployment under AVEVA Flex, with sharing through the CONNECT platform.
AVEVA announced a partnership with Assai, with API integration, in March 2022. According to AVEVA, the Assai system offers strong revision control, transmittal-based distribution, web redlining and digital signatures, and links documents to asset tags.
AVEVA AIM belongs to the category often called ALIM (asset lifecycle information management): managing asset information from project through operation. It is a different layer from classic engineering document management, but it depends on it to work.
Where AVEVA AIM fits next to an EDMS and an ECM
An EDMS answers “what is the current revision of this document?”. AVEVA AIM answers “what do we know about this equipment, and where is each piece of information about it?”. Both questions matter, but they call for different data models.
| Aspect | EDMS: Meridian, ProjectWise, Greendocs | AVEVA AIM, asset information | Corporate ECM / DMS |
|---|---|---|---|
| Central unit | Document and revision | Tag and its links to documents, models and data | Business document |
| Revision control | Native, the core purpose | Through integration, per AVEVA with Assai | Native, different focus |
| Typical standards | Owner’s numbering and procedures | CFIHOS, ISO 15926, ISO 14224 | File plan, retention schedule |
| Strongest phase | Project and operations | Handover and operations | Company-wide |
| Main users | Engineering and document control | Engineering, operations, maintenance, reliability | Business functions |
The category differences are covered in EDMS vs ECM vs DMS. For tools side by side, see the EDMS comparison for engineering. Octave’s asset information platform, formerly part of Hexagon, is covered on the Hexagon SDx page.
The standards behind AVEVA AIM: CFIHOS, ISO 15926 and ISO 14224
AVEVA cites three references. It is worth knowing what each covers, because they define what the owner should require from EPCs.
| Standard | Maintained by | What it covers | Why it matters at handover |
|---|---|---|---|
| CFIHOS | JIP36, under IOGP | Standardized information handover specifications for anyone who designs, operates, maintains or decommissions industrial facilities | Defines classes, attributes and documents the EPC must deliver |
| ISO 15926 | ISO | Integration of life-cycle data for process plants, including oil and gas production facilities | Provides reference data for exchanging information between systems |
| ISO 14224 | ISO | Collection and exchange of reliability and maintenance data for equipment in petroleum, natural gas and petrochemicals | Organizes the equipment taxonomy maintenance will use |
None of these standards requires a particular software. The owner picks what to adopt and writes it into the EPC contract. When the requirement is clear, AIM can measure the completeness of the delivery. When it is not, the platform only shows how big the gap is.
What is AVEVA AIM used for in engineering?
Based on AVEVA’s descriptions, the main uses are:
- Progressive handover on capital projects. The EPC delivers validated data and documents at milestones, and the owner tracks completeness before commissioning.
- A single source for operations and maintenance. Drawings, P&IDs, data sheets and vendor documents linked to the equipment tag.
- A base for the digital twin. Documents, 3D models and laser scans in the same context.
- Information quality control. Consistency and completeness reports against the chosen standard.
AVEVA cites users in oil and gas, energy and manufacturing, with EPCs and owner-operators as the two main profiles.
Common pitfalls in an AIM handover
Handover problems repeat from project to project, whatever the platform. The most frequent ones, in 29docs’ experience:
- Documents without tags and tags without documents. The EPC delivers the data sheet, but with no equipment tag in the metadata. Or the tag is on the list, but no document points to it.
- Different tag standards between EPCs. Two contractors on the same site write the same equipment type in different ways. The platform treats them as two objects.
- Free-text attributes. Units, manufacturer and model typed by hand, each in its own way, with no value list.
- The wrong revision. The delivered document is the issue for comment, not the approved-for-construction or as-built revision.
- Non-compliant vendor documentation. Manuals and certificates arrive in bulk, with no owner code and no link to the purchase package.
All of these are cheaper to prevent in the EPC contract than to fix afterwards. That is why the information requirement should be written before the project starts, with examples and with validation rules the EPC can run before it delivers.
What 29docs does around AVEVA AIM
29docs is a Brazilian, platform-agnostic consultancy in engineering document and asset information management. It works with AVEVA AIM among other platforms, does not sell licenses and is not an AVEVA partner. Its work sits in processes and data:
- Document control process design that feeds AIM: numbering, document types, statuses and the document-to-tag rule. See the engineering document numbering guide.
- Handover requirements for EPCs, based on the standard the owner chooses, such as CFIHOS.
- Record migration from an EDMS such as Meridian or ProjectWise into the AIM ecosystem, or from AIM into another system. See EDMS migration.
- Independent consulting to define each system’s role and the integration between them. See independent consulting.
- Traceability and compliance, with evidence of where each document came from.
How 29docs prepares data for AIM
The 29docs migration pipeline has five stages, each with evidence:
- Extraction of metadata, files and tag lists from the source.
- Transformation and normalization to the destination’s numbering standard and classes.
- Validation of every document against quality rules, including mandatory attributes and the tag link. Only a batch that meets the agreed thresholds goes on to loading.
- Load into the destination.
- Validation and comparison reports between source and destination.
It starts with a free 30-minute assessment. Then organize, standardize and make available, with support after go-live. For the sector view, see engineering document management in oil and gas and energy.
Trademark note
AVEVA and AVEVA product names are trademarks of AVEVA or its affiliates. Assai belongs to its respective owner. CFIHOS is a JIP36 / IOGP specification. Other names belong to their owners. 29docs has no commercial relationship with AVEVA. Descriptions come from AVEVA’s public pages, accessed on 14 October 2026.
Updated on .