Skip to content

Accruent Meridian: consulting, support and migration

Accruent Meridian is an engineering document management system (EDMS) that owner-operators use to control drawings and technical documents over the life of a facility. 29docs provides independent Meridian consulting: support under a support-hours agreement, version upgrades, server migration and migration to other platforms.

Short answer

Accruent Meridian is Accruent's engineering document management platform. It comes in two forms: Meridian Enterprise Server, installed on the customer's own servers, and Meridian Cloud, a multi-tenant SaaS hosted on Microsoft Azure. Meridian manages versions, revisions, approval workflows and audit trails for drawings and technical documents.

What is Accruent Meridian?

Accruent Meridian is an EDMS, an engineering document management system. Accruent presents Meridian as a hybrid engineering document management solution that manages technical documents and drawings throughout their lifecycle, with a central repository to store, organize and control engineering documentation. Meridian is a typical example of an EDMS and part of the wider discipline of engineering document management.

On the product page, Accruent lists these capabilities:

  • version management, secure printing and configurable workflows;
  • markup tools for commenting on drawings;
  • real-time visibility into document revisions;
  • full audit trails and electronic signatures for compliance;
  • integration with EAM, ERP, ECM, Office and CAD applications;
  • SAML single sign-on and multi-factor authentication.

The same page says Meridian is used in more than 75 countries, in industries such as manufacturing, mining, oil and gas, utilities, life sciences, healthcare and higher education.

Meridian Enterprise vs Meridian Cloud: what is the difference?

Accruent publishes two ways to deliver Meridian. The table summarizes what the official documentation says about each.

Meridian Enterprise ServerMeridian Cloud
DeploymentOn-premises, on the customer’s serversMulti-tenant SaaS managed by Accruent, hosted on Microsoft Azure
Applications named by AccruentPowerWeb to create and modify data; Explorer to search and retrieve; Configurator, Administrator and Administration ConsolePower, Cloud Explorer and Classic Explorer; Portal for external collaboration; and APIs
Subscription levelsNot applicableProject for collaboration with contractors; Business for engineering data, documents and asset information; and Life Sciences for life sciences regulations
Who runs the infrastructureThe customer’s IT teamAccruent

Sources: Meridian documentation and Meridian Cloud Product Definition, both by Accruent.

The two worlds connect. Accruent’s documentation describes sending documents from Meridian Enterprise project folders to Meridian Portal projects for revision, review, approval and handover back to Meridian Enterprise. It is the usual path to exchange documents with a contractor without opening the internal server.

How do engineering teams use Meridian?

Meridian is most often found at owner-operators: companies that run a plant, a mine or a network for decades. In those environments the EDMS holds the as-built engineering and keeps it current during operations. Common uses are:

  • Facility archive. Drawings, data sheets, design reports and lists, each with its current revision and the history of earlier ones.
  • Modification projects. A revision is checked out of the archive, goes to the design firm, comes back with changes and is approved. The approval workflow and the audit trail record who did what.
  • Contractor exchange. Document packages go out for external review and come back into the controlled archive.
  • Maintenance support. Integration with EAM, ERP and CMMS systems, which Accruent cites, lets a technician reach the right document from the equipment record.
  • Compliance. In regulated sectors such as pharmaceuticals and oil and gas, electronic signatures and audit trails weigh on the decision.

In industries such as fertilizers, mining and oil and gas, Meridian usually lives alongside in-house numbering standards, master document registers and transmittal practices that predate the system itself.

Meridian support and consulting: what 29docs does

29docs does not sell Meridian licenses and does not represent Accruent. We work on the environment you already have, across four services.

ServiceWhen it makes senseWhat you get
Ongoing support on a block of hoursThe environment is in production and there is no dedicated in-house specialistHelp for users and administrators, configuration changes, support for modification projects
Version upgradeMeridian is on an old version and you want to updateUpgrade planning, testing and execution, with a post-upgrade check
Server migrationHardware or the operating system must be replaced, or the environment is moving to a new data centerNew server configured and archive transferred, with a source-to-target comparison
Migration to another platformYou have decided to leave MeridianArchive migrated to ProjectWise, Greendocs or another target, with validation reports

Ongoing Meridian support

Ongoing support is for teams that already run Meridian and need someone who knows the system from the inside. Hours are used on demand: administration questions, property and workflow changes, help when a large document package comes in. Details are on the EDMS upgrade and support page.

Version upgrade and server migration

Upgrades and server moves look like IT tasks, but they touch the engineering archive. 29docs treats both as document projects: we survey what exists in the current environment, carry out the change and compare the result with the source before users go back in.

Migration to ProjectWise or Greendocs

When the decision is to leave Meridian, 29docs runs the archive migration. The two most requested targets are Bentley ProjectWise and W3K Greendocs. The Meridian to ProjectWise migration and Meridian to Greendocs migration pages describe each path.

How does a migration out of Meridian work?

29docs migrates through a staged pipeline. Each stage has a result you can check.

  1. Extract. Metadata and files are pulled out of the source Meridian environment.
  2. Transform. Data is normalized to the target model: document numbers, revisions, disciplines, statuses.
  3. Validate. Every document is checked against quality rules. Only a batch that meets the quality thresholds agreed for the project goes on to loading.
  4. Load. Validated documents are loaded into the target platform.
  5. Report. Validation reports and source-to-target comparison reports show what went in, what was held back and why.

Before extraction, it pays to answer a few questions about the Meridian environment:

  • How many vaults exist, and which are still in use?
  • Which properties are actually filled in, and which have been empty for years?
  • Will Meridian’s approval workflows be reproduced in the target or redesigned?
  • What happens to old revisions: do all of them migrate, or only the current one with history archived?

Signs your Meridian environment needs attention

Many Meridian environments run for years without anyone looking at them. These signs usually mean it is time for closer Meridian support, an upgrade or a migration decision:

  • The server or operating system is out of the vendor’s support period.
  • Only one person in the company knows how to administer Meridian, and that person is about to leave.
  • Users keep copies on network drives because they do not trust what is in the vault.
  • Metadata fields were created for a process that has changed, and nobody fills them in anymore.
  • Modification projects take a long time to return revisions to the archive.
  • The company is considering another platform but does not know the real size of the archive.

Each sign has a different answer. Sometimes a configuration clean-up is enough. Other times the right move is to plan the exit.

Petrobras: three plants in a single Meridian environment

29docs organized, standardized and published in a single, fully approved Accruent Meridian environment the engineering of three Petrobras fertilizer plants: ANSA, FAFEN-BA and FAFEN-SE. The case is described on the fertilizer industry page.

How to get started

The first step is a free 30-minute review. 29docs learns your Meridian version, the size of the archive and what the team needs to solve: keep, upgrade or migrate. Then comes the usual method: organize, standardize and publish, with ongoing support after go-live.

Trademark note

Accruent and Meridian are trademarks of Accruent. ProjectWise is a trademark of Bentley Systems. Greendocs is a trademark of W3K. Names are used on this page only to identify the products. 29docs is not a partner, reseller or representative of Accruent or Bentley. Descriptions of Meridian come from the official Accruent pages listed under sources.

Updated on .

Frequently asked questions

Is 29docs an Accruent partner or reseller?

No. 29docs is an independent consultancy and sells no licenses. We work on Meridian environments the customer already licenses: support, upgrades, server migration and archive migration. The only formal partnership 29docs holds is with W3K, the maker of Greendocs.

What is the difference between Meridian Enterprise and Meridian Cloud?

According to Accruent's documentation, Meridian Enterprise Server is an on-premises product suite that includes PowerWeb and Explorer. Meridian Cloud is a multi-tenant SaaS managed by Accruent and hosted on Microsoft Azure, offered at the Project, Business and Life Sciences levels.

Can you move Meridian to a new server without losing history?

Server migration is one of 29docs' services. Work starts with a review of the current environment and ends with a comparison between source and target to confirm that documents, revisions and metadata arrived complete. See EDMS upgrade and support.

Where can a Meridian archive be migrated to?

29docs migrates Meridian archives to Bentley ProjectWise and to W3K Greendocs, among other targets. The right target depends on your process. See Meridian to ProjectWise migration and Meridian to Greendocs migration.

How much does Meridian support from 29docs cost?

It depends on the size of the environment and the number of hours. Support is contracted as a block of hours. The first step is a free 30-minute review.

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.