Skip to content

AVEVA AIM and asset lifecycle information

AVEVA AIM (AVEVA Asset Information Management) is AVEVA's solution for bringing the engineering, operations and maintenance documents and data of an industrial asset into one place, governed by information standards such as CFIHOS, ISO 15926 and ISO 14224. This page explains what AVEVA AIM is according to AVEVA, where it sits next to an EDMS and an ECM, and how 29docs supports handover and data migration.

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.

AspectEDMS: Meridian, ProjectWise, GreendocsAVEVA AIM, asset informationCorporate ECM / DMS
Central unitDocument and revisionTag and its links to documents, models and dataBusiness document
Revision controlNative, the core purposeThrough integration, per AVEVA with AssaiNative, different focus
Typical standardsOwner’s numbering and proceduresCFIHOS, ISO 15926, ISO 14224File plan, retention schedule
Strongest phaseProject and operationsHandover and operationsCompany-wide
Main usersEngineering and document controlEngineering, operations, maintenance, reliabilityBusiness 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.

StandardMaintained byWhat it coversWhy it matters at handover
CFIHOSJIP36, under IOGPStandardized information handover specifications for anyone who designs, operates, maintains or decommissions industrial facilitiesDefines classes, attributes and documents the EPC must deliver
ISO 15926ISOIntegration of life-cycle data for process plants, including oil and gas production facilitiesProvides reference data for exchanging information between systems
ISO 14224ISOCollection and exchange of reliability and maintenance data for equipment in petroleum, natural gas and petrochemicalsOrganizes 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:

  1. Progressive handover on capital projects. The EPC delivers validated data and documents at milestones, and the owner tracks completeness before commissioning.
  2. A single source for operations and maintenance. Drawings, P&IDs, data sheets and vendor documents linked to the equipment tag.
  3. A base for the digital twin. Documents, 3D models and laser scans in the same context.
  4. 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:

  1. Extraction of metadata, files and tag lists from the source.
  2. Transformation and normalization to the destination’s numbering standard and classes.
  3. 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.
  4. Load into the destination.
  5. 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 .

Frequently asked questions

What does AVEVA AIM stand for?

AIM stands for Asset Information Management. AVEVA uses the name AVEVA Asset Information Management for the solution that aggregates documents and data from many sources and formats and links them to the asset's digital twin.

Is AVEVA AIM an EDMS?

Not exactly. AVEVA AIM links documents, tags, 3D models and operating data. For revision control, AVEVA cites integration with the Assai document control system. In practice, AIM gives the asset context and an EDMS controls revisions. See EDMS vs ECM vs DMS.

Which standards does AVEVA AIM support at handover?

AVEVA cites CFIHOS, ISO 15926 and ISO 14224, applied through AVEVA Information Standards Manager. CFIHOS is the information handover specification managed by JIP36 under IOGP. ISO 15926 covers life-cycle data integration for process plants. ISO 14224 covers reliability and maintenance data for equipment.

What is progressive handover?

It means delivering asset information at milestones during the project, not only at the end. AVEVA describes AIM as supporting milestone handovers between EPC and owner, with reports on the quality, consistency and completeness of the data.

Does 29docs migrate documents into AVEVA AIM?

29docs works with AVEVA AIM among the platforms it supports and migrates records with an extract, transform, validate and load pipeline. Each migration depends on the target data model and is scoped in the assessment. See EDMS migration.

Is 29docs an AVEVA partner?

No. 29docs is an independent consultancy, does not sell licenses and has no partnership with AVEVA. Its only partnership is with W3K, the maker of Greendocs.

What deployment options does AVEVA AIM have?

AVEVA cites cloud, hybrid and on-premises deployment under the AVEVA Flex subscription model, and information sharing through the CONNECT industrial cloud platform. The choice and licensing are handled with AVEVA.

Ready for your next audit?

A 30-minute conversation. No pitch. We want to understand your document reality before talking about any solution.

We reply within 1 business day. Your data is never shared.