Skip to content

Oracle Aconex: consulting, document control and handover

Oracle Aconex is the project collaboration system many EPC contractors and asset owners use to exchange documents, correspondence and approvals during a capital project. This page explains what Aconex is, in Oracle's own terms, where it sits next to the owner's EDMS, and how 29docs works as an independent Aconex consultant on document control processes and on the handover of Aconex records into the owner's system.

What is Oracle Aconex?

Oracle Aconex is, in Oracle’s words, a cloud-based project collaboration system built for construction, infrastructure and engineering projects. It brings project information, communications and processes into one system, so that owners, contractors, engineers, designers, suppliers and other participants can work together throughout the project lifecycle.

The feature Oracle stresses most is its data ownership model. Every organization on the project has its own private workspace in Aconex and decides what it shares, with whom and when. Oracle describes the product as purpose-built for contractual collaboration across multiple independent organizations, not for a single company.

For anyone working in engineering document management, these are the Aconex functions that matter most, according to Oracle’s product page:

  • a single document register with version control;
  • configurable workflows for review and approval, with templates and sub-workflows;
  • comment management and an automated review matrix: the right approval flow starts from the document’s metadata;
  • formal correspondence, called mail in Aconex, with threaded history, in place of email;
  • supplier documentation management, with due dates and statuses calculated per package;
  • an unalterable audit trail: Oracle states that nothing can be deleted or edited;
  • work packages, BIM model coordination, RFIs, inspection and test plans, cost and field processes;
  • project archives at the end, online or downloaded to a local server.

Oracle also presents Aconex as part of its common data environment (CDE). The CDE concept comes from the ISO 19650 series on information management for built assets.

Where Aconex fits: project CDE, EDMS and ECM

A lot of friction on capital projects comes from treating Aconex as the company EDMS, or the other way round. The two solve different problems at different stages of an asset’s life. The table sums up the difference as 29docs sees it on projects.

AspectOracle Aconex, project CDEOwner’s EDMSCorporate ECM / DMS
PurposeContractual collaboration between many companies during deliveryHold and control the asset’s engineering during operationAdministrative and business documents
Time horizonThe project, with an archive at the endDecades, as long as the asset existsPer the retention schedule
Who works in itOwner, EPC, designers, suppliersEngineering, maintenance, operations, safetyBusiness functions
Unit of controlDocument, transmittal, correspondence, packageTechnical document tied to area, system, equipmentDocument and business process
ExamplesAconexMeridian, ProjectWise, GreendocsECM platforms

The category differences are covered in EDMS vs ECM vs DMS. For a side-by-side look at tools, with no brand recommendation, see the EDMS comparison for engineering.

The practical result: Aconex is usually the source of the project record, and the owner’s EDMS is the destination. The quality of that transfer decides whether operations finds the right drawing on the day it needs it.

What is Aconex used for on engineering projects?

Oracle lists construction, infrastructure, engineering, energy, industrial and government as user sectors. Typical projects it cites include roads, bridges, tunnels, airports, rail, energy and utilities, mining and resources, manufacturing facilities and industrial plants. Oracle says the system is particularly suited to large, complex projects where many organizations must collaborate, distribute information and keep a project record through handover.

From a document control point of view, the most common uses are:

  1. Issuing and receiving design documents. The designer issues, the owner reviews and returns comments. Aconex records every submission and every response.
  2. Supplier and vendor documentation, VDR and SDR. Equipment vendors submit drawings, data sheets and manuals. Aconex tracks due dates and status per package.
  3. Contractual correspondence. Letters, RFIs and notices are threaded and auditable, which matters in claims and disputes.
  4. Handover packages. Documents, drawings and correspondence grouped by area or system for completion and sign-off.
  5. Schedule integration. Oracle cites links between packages and Oracle Primavera Cloud.

In each case the project defines the numbering, statuses and attributes. If the project does not follow the owner’s engineering document numbering standard, the cost shows up at handover.

What happens to Aconex documents at the end of the project?

According to Oracle, Aconex keeps the project record from design through commissioning and handover, and the record can be preserved in a read-only archive. There are three archive options:

  • Online Archive: full access to project data stored in the cloud;
  • Project Archive: an on-premises application that downloads your organization’s data;
  • Scheduled Archive: an on-premises application that downloads it on a chosen routine.

The archive solves retention of the record. On its own, it does not make those documents usable in operations. Maintenance does not want the transmittal history. It wants the current revision of the drawing, linked to the equipment, findable by the tag it already knows. That is why handover into the owner’s EDMS is a project of its own.

What usually migrates and what needs a decision

Aconex itemUsual destination in the owner’s EDMSDecision needed
Current revision of each documentMigrates as an active documentWhich status counts as “approved for operation”
Superseded revisionsMigrate as history or stay in the archiveVolume, retention period, storage cost
Register metadataMapped to EDMS attributesField-by-field mapping table
Comments and markupsUsually stay in the project archiveWhether any comment carries technical value for operations
Correspondence and transmittalsStay in the project archiveContractual and legal requirements
Vendor documentationMigrates linked to the equipment tagTag standard and folder structure

What 29docs does around Aconex

29docs is a Brazilian, platform-agnostic consultancy. It does not sell Aconex licenses or licenses for any other tool, and it is not an Oracle partner. Its work sits in the processes and data that flow through Aconex:

  • Document control process design for the project: numbering, statuses, review matrix, acceptance criteria and the register format the owner wants at the end.
  • Handover requirements written before the project starts, so Aconex is set up with the attributes the owner’s EDMS will need.
  • Migration of Aconex records into the owner’s EDMS, such as Meridian, ProjectWise or Greendocs, or from another system into Aconex when a project already has history. See EDMS migration.
  • Independent consulting when a company has to decide which tool to use at which stage. See independent consulting.
  • Traceability and compliance, so the origin of each migrated document can be shown in an audit.

How 29docs runs an Aconex-to-EDMS handover

29docs migrates records with a staged pipeline. Each stage leaves evidence the owner can check.

  1. Extraction of metadata and files from the project export or archive.
  2. Transformation and normalization: codes, statuses, disciplines and revisions converted to the owner’s standard.
  3. Validation of every document against quality rules. Only a batch that meets the agreed quality thresholds goes on to loading.
  4. Load into the destination, with the agreed structure and attributes.
  5. Validation and comparison reports between source and destination, document by document.

The overall method is the same as for other services: a free 30-minute assessment, then organize, standardize and make available, with support after go-live. Companies such as Petrobras, CBMM, ArcelorMittal and Evonik trust 29docs. For the sector view, see engineering document management in oil and gas.

Trademark note

Oracle and Aconex are registered trademarks of Oracle Corporation and its affiliates. Other names belong to their owners. 29docs has no commercial relationship with Oracle. Product descriptions on this page come from Oracle’s public pages, accessed on 14 October 2026.

Updated on .

Frequently asked questions

Is Oracle Aconex an EDMS?

Aconex manages documents, but Oracle describes it as a project collaboration system and a common data environment shared by many organizations. A corporate EDMS holds the engineering of an asset for its whole operating life. In practice, Aconex serves the project and the EDMS serves operations. See EDMS vs ECM vs DMS.

What happens to Aconex documents when the project ends?

Oracle offers project archives: an online archive in the cloud and on-premises applications that download your organization's data once or on a schedule. The archive preserves the project record. It does not replace loading those documents, with correct metadata and revisions, into the EDMS operations will use.

Can Aconex records be migrated to ProjectWise, Meridian or Greendocs?

Yes, as a migration project with metadata mapping, a rule for the current revision and document-by-document validation. 29docs runs this kind of work with an extract, transform, validate and load pipeline. See EDMS migration.

Is 29docs an Oracle partner or reseller?

No. 29docs is an independent consultancy and does not sell licenses. Licensing, product support and account setup sit with Oracle or its channels. 29docs works on processes, data and moving records into other systems.

Who uses Aconex on a project?

According to Oracle: asset owners, general contractors, EPC firms, designers, suppliers and other participants. The roles Oracle lists include project directors, project managers, document controllers, design managers, project controls, quality and safety teams.

Does Aconex replace the master document register?

Aconex keeps a single document register with version control, which plays the MDR role during the project. The owner still has to define the numbering, statuses and attributes it wants to receive, so that the register makes sense in its own EDMS later. See the master document register guide.

Where should we start if the project is already in Aconex and handover is close?

Start from the handover requirement: which documents, in which status, with which attributes and into which system. That measures the gap between what is in Aconex and what operations needs. 29docs runs a free 30-minute assessment to scope it.

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.