AVEVA Everything3D to E3D Design: What Plant Teams Must Verify

If an old project specification asks for “AVEVA Everything3D,” the first buying decision is which present-day product and delivery model that requirement actually implies. AVEVA now presents E3D Design as a capability within Unified Engineering, rather than a standalone purchase. This historical/legacy profile follows the older name into the current offering using official material checked on November 7, 2026; we did not independently install or test the software.

The official E3D Design product page identifies the former Everything3D name, while AVEVA’s transition notice states explicitly that E3D Design is no longer sold as a standalone product and its capabilities are available within Unified Engineering. This is a change in packaging and architecture, not evidence that 3D plant design has been abandoned. AVEVA remains the developer and supplier; its January 18, 2023 acquisition announcement records its becoming wholly owned by Schneider Electric.

What needs to survive a project migration

For an engineering manager maintaining an existing plant model, opening geometry is only part of a useful migration. The decision should also cover component catalogs, project rules, access rights, drawing definitions and custom routines. AVEVA says most customers can open projects in the latest E3D Design provided through Unified Engineering, but directs customers with project-data concerns to an AVEVA representative. Treat that statement as vendor migration guidance, not an independently demonstrated guarantee for every historical database or customization.

The current E3D Design datasheet describes configuration of data structures, access rights, design status controls, checking rules and drawing/report formats. It also documents PML and a .NET API for customization. Those are reasons to inventory the project’s extensions before choosing a target environment: ask which interfaces and custom routines remain supported, then require an acceptance exercise on copies of actual project data. The existence of an API does not establish compatibility with a particular in-house extension.

Follow one design change through to its deliverables

Consider a hypothetical brownfield piping modification. The inputs would include the existing model, approved component specifications, the design change and registered scan data covering the tie-in area. AVEVA documents laser-scan use within the design space, clash detection across disciplines, and generation of drawings, reports and bills of materials from the project model. For this workflow, the relevant output is a coordinated set of changed objects and issue-ready deliverables, rather than simply an attractive 3D view. These are documented capabilities; the project still needs its own acceptance criteria for the model and issued documents.

The datasheet explains that scan capabilities work with AVEVA Point Cloud Manager datasets. Our Point Cloud Manager article provides related reading on that preparation layer. A buyer should demonstrate the scan-to-model workflow with the intended dataset, its coordinate system and the required drawing output. Scanner compatibility alone cannot establish that a survey has sufficient coverage or that a tie-in location is suitable for construction.

The product documentation also describes integration with AVEVA schematic tools and third-party gateways. A useful acceptance exercise would change a defined item, check which discipline sees the change, resolve a deliberate conflict, and regenerate the affected deliverable. That tests the handover the project needs without assuming “integrated” means every attribute moves automatically. Our Unified Engineering overview covers the broader suite; this article focuses on the consequences for the older Everything3D project requirement.

Separate the old installation from the new subscription

AVEVA’s documentation catalogue separates Everything E3D 2.0, E3D Design 3.1 and E3D Design within Unified Engineering. Those labels identify documentation families, not proof of the latest supported maintenance build. The existing draft’s “4.3” was not corroborated by the official sources reviewed. Obtain the precise target release, upgrade path and support lifecycle in the quote instead of purchasing against an unverified version number.

The current product page describes cloud collaboration and AVEVA Flex credits-based subscriptions, and the transition notice describes browser access within Unified Engineering. Separately, the Unified Engineering hardware guidance lists Windows 11 23H2/24H2 client configurations, 32 GB RAM and DirectX 12-capable graphics, with server requirements listed separately. These requirements belong to that documented Unified Engineering environment; they should not be substituted for an old standalone Everything3D installation or assumed to describe every browser-access configuration. Have AVEVA confirm the applicable client, hosting, graphics and network requirements for the proposed deployment.

Public transition material does not establish your old license’s conversion rights, a project-specific credit consumption rate, migration services, or the final support entitlement. The E3D Design manual points technical support questions to AVEVA Customer Support and assumes appropriate licensing. Before moving a live project, agree how external contractors are licensed, who administers permissions, how project data is backed up and exported, and what happens when the subscription or contractor relationship ends.

When to evaluate another plant design environment

Bentley OpenPlant Modeler is a relevant alternative for a new multidisciplinary plant-modeling workflow. Bentley’s product page documents specification-driven piping, parametric equipment, iModel exchange, multiple CAD formats and model-derived material reporting. Compare the required owner deliverables, catalog reuse, information retained during exchange and contractor environment against the E3D/Unified Engineering proposal. A format appearing on an import list is not evidence of a lossless conversion of an intelligent project.

For an established Everything3D project, continuity of catalogs, customizations and approved deliverables may make the AVEVA migration route worth prioritizing. For a new project without that dependency, the receiving owner’s data requirements and a representative exchange exercise should shape the shortlist. Evidence confidence is high for the product transition and documented workflow scope, but limited for any particular legacy project’s migration effort or performance. Before committing, make AVEVA demonstrate one real project change from model input through a checked drawing and material report in the exact environment being offered.