Why EDMS selection goes wrong
EDMS selection often starts at the wrong end. One vendor gives a great demo, another shows up at a trade fair, a third already serves a sister company. The team compares screens and license prices, decides, and only later finds that the platform does not handle engineering revisions the way the plant needs, or that the maintenance system integration is a project of its own.
The root problem is structural. In document management, many consultancies also resell the platform they implement. When the adviser also sells the license, the assessment is rarely neutral, even in good faith.
In engineering document management, a wrong choice is expensive for years: licenses, customization, migration, training and, in the worst case, a second replacement.
Independent EDMS consulting: what changes
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.
29docs works with Accruent Meridian, Bentley ProjectWise, Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, W3K Greendocs, Construtivo and E-clic. Knowing several platforms from the inside means comparing them on how each one solves the client’s problem, not on marketing material.
The disclosed exception
29docs is a Value Added partner of W3K, the developer of Greendocs. It is the only vendor partnership, and it is stated from the first conversation. When Greendocs is a candidate in a selection, criteria and weights are set before proposals arrive and the client knows about the partnership. The Portuguese-language article on why platform-agnostic consulting protects your investment explains this stance.
What independent consulting covers
The service has three parts, which can be contracted together or in sequence.
1. Document management assessment
The assessment maps how the company creates, reviews, approves, stores and finds engineering documents today. It covers systems, vaults, network folders, paper, approval workflows, numbering standards, roles and owners. It also covers sector requirements: NR-13 pressure vessel records in a Brazilian plant, Good Manufacturing Practice in pharma, dam safety plans in mining.
The result is a picture of gaps, risks and priorities. Often the assessment shows that the problem is not the platform but the process or the configuration.
2. Platform selection and RFP support
When a replacement or a first EDMS purchase makes sense, 29docs runs the selection with a method:
- Requirements. Gathered with engineering, operations, maintenance, quality and IT. Functional requirements cover document types, revisions, workflows, numbering, transmittals and CAD; technical ones cover cloud or on-premises, integrations, security and performance.
- Criteria and weights. Set before any demo, so the evaluation does not follow the best presentation.
- RFP. A document with company context, requirements, a proposal template and the demo script.
- Scripted demos. Every vendor shows the same cases, using real plant documents.
- Levelling. Proposals compared on the same basis: license, infrastructure, implementation, migration and support over the years.
- Recommendation. A report with each candidate’s score, risks and a reasoned recommendation.
For operations in Brazil, a useful public reference for general requirements is e-ARQ Brasil, from the national archives council (CONARQ). It sets minimum requirements for a computerized archival document management system, regardless of the technology platform. Engineering-specific requirements are added by the project.
3. Process design
The best platform will not fix a poorly designed process. 29docs designs the document control process with your team: numbering, revision cycle, master document register, transmittals to and from vendors, management of change and how as-built information returns to the archive. The process design works for the current platform and for the next one. It also gives the RFP something concrete to test: vendors demonstrate your process, with your numbering and your approval steps, instead of a generic one.
Criteria that usually matter when choosing an EDMS
Every case has its own weights, but some criteria show up in almost every engineering EDMS selection.
| Criterion | What to ask |
|---|---|
| Revision control | Does the platform separate engineering revisions, such as Rev 0 or Rev A, from file versions? |
| Approval workflows | Can your team configure workflows, or do they need development? |
| CAD | Does it open, compare and manage references for the formats engineering uses? |
| Third parties | How do vendors and EPC contractors submit and receive documents? |
| Integrations | Does it connect to the maintenance system and the ERP? |
| Traceability | Does it record who did what, and when, on every document? |
| Infrastructure | Cloud, on-premises or hybrid, and who looks after each part? |
| Total cost | License, infrastructure, implementation, migration and support added up over time |
| Exit | How do you export metadata, files and history if you ever need to switch? |
To understand the system categories before a selection, see what is an EDMS and the EDMS comparison.
When to bring in an independent consultant
Some moments call for a neutral view before committing to any vendor:
- The current EDMS is at the end of the road. The version is out of support, the maintenance contract is ending, or IT wants off the on-premises server. Before replacing, check whether an upgrade solves it.
- The company has never had an EDMS. Engineering lives in network folders and email, and the first purchase needs to be the right size.
- A merger or acquisition. Two or more sites arrive with different platforms and the group must decide which one stays.
- A capital project begins. An expansion or a new plant will generate thousands of documents from EPC contractors and vendors, and the environment must be ready first.
- An audit found gaps. The finding showed that the process, the platform or both need to change.
Pitfalls in EDMS selection
- Comparing screens instead of cases. A free-form demo shows the best of each product. A script with real documents shows how it solves your problem.
- Looking only at the license. Implementation, migration and support over the years often weigh as much as the license.
- Forgetting the exit. Every EDMS is replaced one day. Knowing how to export metadata, revisions and history keeps you from being locked in.
- Leaving engineering out. A choice made only by IT or procurement ignores how technical documents really flow.
What you get
- A document management assessment report with gaps, risks and priorities.
- A functional and technical requirements book, validated with each department.
- A criteria and weighting matrix for the evaluation.
- An RFP ready to send, with a demo script.
- A proposal levelling sheet and a recommendation report.
- A document control process design, when contracted.
- A roadmap of next steps: organize, migrate, implement or upgrade.
How it starts
The first step is a free 30-minute review. 29docs learns where the company stands: whether an EDMS is in use, whether the decision is to replace, upgrade or buy a first one, and which requirements weigh in your sector. At the end you know which consulting format makes sense.
After the choice, 29docs can continue with EDMS migration, implementation or support on the chosen platform. Or it can stop there. Independent consulting stands on its own.
Updated on .