Why implementation decides how Greendocs performs
A well-chosen EDMS can still fail because of how it is implemented. The software arrives, but documents stay scattered across network folders, a legacy system and email. Document types are created without a standard. Approval workflows copy the paper process instead of improving it. Six months later, half of engineering still works outside the system.
In engineering document management, implementation is the work of turning software into a trusted master repository. That takes three things the software does not ship with: an organized and migrated archive, a metadata and numbering standard, and workflows that make sense to the people who issue, review and approve documents.
That is what 29docs does in a Greendocs implementation. For multinationals with sites in Brazil and Latin America, the project can be run in English, Portuguese or Spanish, so corporate engineering standards and local teams work from the same configuration.
What Greendocs is, according to W3K
Greendocs is cloud-based document and process management software developed in Brazil by W3K. W3K describes Greendocs as a platform that combines ECM and BPM with low-code engines, configurable to each business model. For engineering, W3K positions Greendocs as an EDMS for technical documents and industrial projects.
The table lists the features W3K publishes and what each one solves in a plant. Feature descriptions are the vendor’s; the right-hand column is the typical engineering use.
| Feature published by W3K | What it does in the plant |
|---|---|
| Master repository with versioning and revision history | Everyone works on the current revision of drawings, data sheets and procedures |
| Configurable approval workflows with digital signature | Paperless issue, review and approval, with a record of who approved |
| Audit trail | Who did what, and when, on every document |
| Access control by user and permission | In-house teams and third parties see only what they need |
| Document exchange with vendors and EPC contractors | Traceable submission and return of project documents |
| 2D and 3D CAD viewer, redlines and automatic 2D revision comparison | Review drawings in the platform, without external software |
| “Google-style” search with built-in OCR | Find documents, including scanned ones, by their content |
| Management of change (MOC) and shutdown management | Link the approved change to the revised document and follow the turnaround |
| Integration with SAP PM and IBM Maximo | Link documents to equipment in the maintenance system |
| Mobile app and electronic databook | Look up documents during field inspections |
For a fuller view of the tool, see the Greendocs platform page.
Greendocs implementation with 29docs, a W3K Value Added partner
29docs is a W3K Value Added partner. It is the only vendor partnership 29docs has, and it is disclosed openly. Details are on the W3K partnership page.
The split of roles is simple. W3K develops Greendocs, runs the platform and licenses it to the client. 29docs does not sell licenses: it provides the service that turns a license into a working environment, with your engineering archive, standards and workflows.
29docs also knows the systems documents usually come from. 29docs works with Accruent Meridian, Bentley ProjectWise, Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, Construtivo and E-clic. That matters when the implementation begins with a migration.
How 29docs implements Greendocs
The implementation follows the 29docs four-step method, the same one used in every document management project.
1. Assess
It starts with a free 30-minute review. In the project, 29docs surveys systems, vaults, network folders and paper: what exists, where it is, who uses it and what is missing. The output is an archive inventory and the list of document types, workflows and integrations Greendocs will receive.
2. Organize
29docs brings the archives into one environment. When there is a source system, the migration follows the 29docs pipeline: extraction of metadata and files, transformation and normalization, validation of every document against quality rules, loading into Greendocs, and validation and comparison reports between source and target. Only batches that meet the agreed quality thresholds move on to loading. The migration is planned so operations are not interrupted.
3. Standardize
29docs works with your team on metadata, document numbering, document types and review and approval workflows. The goal is that every document can be found by the equipment, area or project it belongs to. Access profiles for in-house teams, contractors and vendors are defined here too.
4. Make available
29docs grants role-based access, trains administrators and users, and goes live with assisted operation. After go-live, 29docs can continue with ongoing support and improvement of the environment.
Common pitfalls in EDMS implementation
Some failures repeat across EDMS implementations, whatever the platform. 29docs designs the project to avoid them from day one.
- Migrating everything blindly. Moving whole folders with duplicates and unrevised files into the new system just relocates the mess. Batch validation exists to stop that.
- Too much metadata. A document type with 40 mandatory fields makes users give up. The metadata model should hold the minimum needed to find and control a document.
- Workflows that copy paper. If paper approval had five signatures out of habit, the digital workflow will inherit all five. Implementation is the time to review who really needs to approve.
- Forgetting third parties. Contractors and vendors produce much of a plant’s documentation. Leave them out and email becomes the repository again.
- Training only at go-live. Users trained once, without help in the following weeks, drift back to network folders. That is why 29docs goes live with assisted operation.
What you get
- An inventory of the current archive, by system, folder and document type.
- A metadata model and document numbering rule approved with engineering.
- Configured document types, folder or area structure and access profiles.
- Review and approval workflows designed, configured and tested with users.
- Archive migration with validation and source-to-target comparison reports.
- A definition of the integrations needed, such as the link to the maintenance system.
- Training for administrators and key users, with reference material.
- Go-live with assisted operation and a support plan.
Where Greendocs projects usually start
Implementation projects tend to begin in one of these situations:
- Scattered documents. Engineering lives in network folders, email and paper, and nobody knows which revision is current.
- A legacy system at the end of the road. The current EDMS is outdated or unsupported and the company has decided to replace it. If the source is Meridian, see Meridian to Greendocs migration.
- Several sites. Each plant stores documents its own way and the group wants one standard.
- An audit or inspection. The company had to prove who approved what, in which revision, and it took days to pull the evidence together.
In fertilizer plants, for example, Greendocs organizes NR-13 pressure vessel records, turnaround documents and plant changes. See Greendocs in fertilizer plants.
How it starts
The first step is the free 30-minute review. 29docs learns about your archive, your current systems and the goal of the implementation. If Greendocs fits your case, you leave with an implementation path. If it does not, 29docs will say so and point to the alternative.
Updated on .