What is Greendocs?
Greendocs is W3K’s document and process management software. On the product page, W3K presents it as software configurable to each customer’s business model, replicating processes and strategies the teams already use. In an article on engineering, W3K describes Greendocs as an integrated GED, BPMS and EDMS platform, flexible and scalable for technical documents and engineering processes. GED, short for gestão eletrônica de documentos, is the term Brazilian companies use for electronic document management.
In practice, Greendocs brings together two things that usually sit apart: the controlled document repository and the process workflow engine. That matters for engineering document management, because a technical document rarely travels alone. It comes with a transmittal, a review comment sheet, an approval and an audit record.
What does Greendocs do for engineering teams?
The table lists the functions W3K publishes for Greendocs and what each one means day to day in an engineering department.
| Function published by W3K | Typical engineering use |
|---|---|
| Integrated ECM and BPM | Document and approval workflow in the same system |
| Custom workflows | Review routes by discipline or by document type |
| Alerts and notifications | Warnings when a document is stuck in review or a return date is near |
| Standardized document transmittal | Controlled issue of packages to clients and suppliers |
| Collaboration workflow for EDMS | Comment cycle between design firm and client |
| CAD viewing | Opening drawings without the design software |
| Electronic annotations and comments | Markups stored with the document |
| Intelligent technical document search | Finding reports, records and evidence for audits |
| Cloud storage | Access for internal teams, suppliers and partners |
Sources: Greendocs product page and W3K article on EDMS, both in Portuguese.
In the same article, W3K notes that an engineering department spans industrial, electrical, civil and environmental work, each with its own demands, and that reaching several environments with a single login simplifies the team’s work.
When is Greendocs a good fit?
29docs is platform-neutral and does not claim one system is better than another in the abstract. Greendocs usually comes up in situations like these:
- You want documents and processes in one place. Approvals, review comments and transmittals depend on workflows that differ from company to company.
- The engineering archive is scattered. Network folders, spreadsheet registers and an old EDMS coexist without talking to each other.
- You want support and development in Latin America. W3K is a Brazilian company, and 29docs works across Brazil and Latin America.
- There is a Meridian to replace. Meridian to Greendocs migration is one of the paths 29docs delivers.
If the project needs deep integration with specific design applications, or if the owner-operator has already standardized on another platform, compare first. The EDMS comparison for engineering helps structure that decision.
What 29docs does on Greendocs
29docs is an official W3K Value Added partner. That means 29docs implements, configures and supports Greendocs in the customer’s environment, from the initial review to go-live and assisted operation. Partnership details are on the 29docs and W3K page.
| Stage | What 29docs delivers |
|---|---|
| Review | A free 30-minute conversation and a survey of the current archive and workflows |
| Organize | Archive inventory, deciding what goes in and what stays in storage |
| Standardize | Document numbering, attributes, document types and review workflows configured in Greendocs |
| Publish | Loading of the validated archive and release to the teams |
| Support | Ongoing support under a block of hours after go-live |
The full process is on the Greendocs implementation page.
What a Greendocs implementation for engineering looks like
Configuring Greendocs for an engineering department revolves around four document control artifacts. They exist before any system and have to be designed with the customer’s team.
Document numbering
The document number identifies a document without ambiguity: project, area, discipline, type and sequence. In Greendocs the numbering standard becomes a registration rule. That prevents duplicates and makes search easier.
Master document register
The master document register lists every document of a project or asset, with the current revision and status of each. Once the archive lives in Greendocs, the register stops being a hand-maintained spreadsheet and becomes a query on the system itself.
Review and approval workflow
Each document type has a route: preparation, checking, approval, issue. Greendocs custom workflows can model different routes per discipline, per client or per document type, with alerts when a document stalls.
Transmittals
A transmittal records what was sent, to whom, in which revision and for what purpose. W3K lists standardized document transmittal among Greendocs functions. During implementation, 29docs defines the transmittal template and the rules for numbering and for returning comments.
Questions to ask before implementing Greendocs
- Who are the users: only internal engineering, or also design firms, suppliers and clients?
- Does a numbering standard exist and is it followed, or does it need revising?
- How large is the legacy archive and where is it today?
- Which approval workflows are mandatory under internal rules or regulation?
- Which integrations with other company systems are required?
- Who will administer the environment after go-live?
The answers define the scope of the implementation and the size of the migration.
Greendocs in capital-intensive industries
29docs serves capital-intensive industries in Brazil and Latin America, such as mining, oil and gas, energy, fertilizers, steel, pulp and paper, chemicals and pharmaceuticals. In these sectors the engineering archive follows the asset for decades and goes through audits, maintenance shutdowns and expansion projects. That is why a Greendocs implementation does not end at go-live: the archive has to stay reliable with every new revision, and ongoing support exists for that. The same logic applies to any platform; what Greendocs adds is the option to bring the approval process into the same system where the document lives.
How 29docs migrates an archive into Greendocs
When there is a legacy archive, 29docs uses the same pipeline it applies to any migration:
- Extract metadata and files from the source, such as Meridian, network folders or another EDMS.
- Transform and normalize them to the document types and attributes configured in Greendocs.
- Validate every document against quality rules. Only a batch that meets the quality thresholds agreed for the project goes on to loading.
- Load into Greendocs.
- Report with validation and source-to-target comparison reports.
This design avoids the most common migration mistake: carrying the old system’s mess into the new one.
What the migration reports show
The reports are what let the engineering team sign off on a migration. 29docs delivers two kinds:
- Validation report. For each batch, it lists the documents that passed the quality rules and those that were held back, with the reason: missing number, inconsistent revision, missing file, duplicate, and so on. Held-back documents are fixed at the source or handled case by case before a new load.
- Comparison report. It sets the source against the target: documents, revisions and files in each, so the team can confirm that nothing was lost on the way into Greendocs.
With both reports in hand, the go-live decision is based on evidence rather than on a sample check.
Trademark note
Greendocs is a trademark of W3K. Meridian is a trademark of Accruent. Names are used on this page only to identify the products. 29docs is a W3K Value Added partner; descriptions of Greendocs come from the official W3K pages listed under sources. 29docs has no partnership with Accruent.
Updated on .