Why does an EDMS stop evolving after go-live?
An EDMS usually starts life as a well-funded project, with a team, a schedule and a sponsor. After go-live the project closes and the system depends on whoever is left: an IT analyst who splits time across ten other applications, and a key user in engineering who learned to configure it on the job.
Over the years the environment ages in layers. The EDMS falls two or three versions behind. The server runs a Windows Server or SQL Server release that is out of vendor support. Engineering moves to a new CAD version and the integration breaks. The approval workflow was designed for an organization that has since changed. Nobody remembers why a certain attribute exists.
In engineering document management this wear is expensive. The EDMS holds the drawings, data sheets, pressure vessel records and procedures that operations, maintenance and inspection use every day. An environment frozen in time becomes an information security, availability and audit risk.
Common warning signs
- The production version no longer receives vendor fixes.
- The server operating system or database is out of support.
- Engineering upgraded CAD and the EDMS integration fails.
- Tickets stall because nobody knows the configuration.
- The environment has undocumented customizations built by people who have left.
- Backups exist, but nobody has tested a restore.
EDMS upgrade and support with 29docs
29docs is a Brazilian, platform-agnostic consultancy in engineering and asset document management for capital-intensive industries in Brazil and Latin America. 29docs does not sell licenses. That changes the nature of support: recommendations start from your environment, not from a sales target. Its only commercial partnership is with W3K, for Greendocs, and it is disclosed.
The service has three parts. You can contract them together or separately.
1. EDMS version upgrade
An upgrade brings Meridian, ProjectWise or another EDMS to a version the vendor supports. 29docs follows what each vendor publishes for the target version. Accruent, for example, recommends performing and troubleshooting the Meridian upgrade first on a test server with a current copy of production, and running user acceptance testing before upgrading production. Accruent also states that it does not provide technical support for production environments that run different Meridian Enterprise versions on servers and clients. So the upgrade plan covers the engineering workstations, not just the server.
For ProjectWise, Bentley’s documentation points to each version’s readme for supported operating systems and requirements, and describes steps such as uninstalling the previous Design Integration Server before installing the new one. Each version has its own rules, and the plan starts from them.
2. Server migration
Sometimes the EDMS version is acceptable but the infrastructure is not. According to Microsoft’s published lifecycle, extended support for SQL Server 2016 ended in July 2026 and extended support for Windows Server 2016 ends in January 2027. Servers in that situation stop receiving regular security updates.
Server migration moves the EDMS to a new operating system, database, hardware or virtualized environment while keeping vaults, datasources, files, permissions and integrations intact. When a version change and a server change coincide, 29docs plans them together so there is a single cutover.
An upgrade is also a good moment for housekeeping. Unused attributes, abandoned project areas, orphaned workflow states and generic user accounts tend to pile up over the years. Cleaning them up during the rehearsal, with engineering’s sign-off, means the new version starts lighter and easier to support.
3. Hours-based support retainer
Ongoing support keeps the environment running and improving after an upgrade, or after an EDMS migration. You contract a block of hours and use it as needed. Scope, volume, channels and response times are defined in the contract.
Typical requests include:
- user and administrator tickets;
- configuration changes: attributes, document types, workflows, profiles and permissions;
- new vaults, datasources and project areas;
- opening and following up cases with the vendor;
- small improvements, such as a new report or a new workflow state;
- preparing evidence for audits and inspections;
- periodic health checks: storage, performance, backup and logs.
Vendor support or 29docs support?
They are different and complementary. The table shows who looks after what.
| Topic | Vendor support | 29docs support |
|---|---|---|
| Product defect | Fixes it and ships the release | Identifies, reproduces and follows up the case |
| Licenses and maintenance contract | Vendor or reseller | Does not sell licenses |
| Your environment’s configuration | Usually out of scope | Configures and documents it |
| Workflows, profiles and permissions | Usually out of scope | Designs and adjusts them with engineering |
| Upgrade and server migration | Publishes requirements and installers | Plans, rehearses and executes |
| Audit evidence | Usually out of scope | Prepares it with the quality team |
Where Meridian and ProjectWise support matters
Meridian and ProjectWise environments in industrial plants tend to accumulate years of documents, customizations made by different projects, and integrations with CAD and maintenance systems. In these environments the vendor documentation alone is not enough: someone needs to know how that vault or datasource was built and why.
29docs supports these environments in English, Portuguese and Spanish, which helps multinationals running sites in Brazil and across Latin America. The same applies to the other platforms 29docs works with: Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, W3K Greendocs, Construtivo and E-clic. See the Meridian platform page and the ProjectWise platform page for context on each.
Industries
The work is the same in any plant with an engineering archive, but each sector adds its own requirements. In fertilizer plants and chemical sites in Brazil, regulatory standard NR-13 requires each pressure vessel’s records to be kept current and available on site. In mining, the dam safety plan must be available at the site. An unsupported EDMS puts those obligations at risk.
What you get
Each part has its own deliverables.
For upgrades and server migration:
- an inventory of the current environment: version, servers, database, vaults or datasources, customizations and integrations;
- a compatibility matrix for the target version, based on the vendor’s published requirements;
- an upgrade plan with a test-server rehearsal, a test script and acceptance criteria;
- a cutover and rollback plan, with a window agreed with operations;
- a post-cutover check report: documents, permissions, workflows and integrations;
- documentation of the final environment, for IT and for the next audit.
For the support retainer:
- a log of every request, with what was done and the hours used;
- a periodic report on hours and main topics;
- documentation of every configuration change;
- improvement recommendations with priority and estimated effort.
How it starts
The first step is a free 30-minute review. 29docs learns which EDMS you run, which version, on what infrastructure and with which pain points. At the end you know whether the path is an upgrade, a server migration, a support retainer or a platform change.
After the review, the work follows the 29docs method: organize, standardize and make available, with support after go-live. In an upgrade, organizing means inventorying the environment, standardizing means cleaning up and documenting the configuration, and making available is the cutover and team acceptance.
If the review shows your current EDMS no longer fits, 29docs will recommend a change with the same neutrality. That is the role of independent consulting.
Updated on .