Document management in a CMMS

In almost every maintenance department, the documentation exists, but it isn’t controlled by the department itself. Part of it sits in the company’s general archive — sometimes at another site — part of it is on paper inside a cabinet, part of it is in shared folders with three versions of the same file, and a good part of it isn’t written down anywhere at all: it lives in the operators’ heads and gets passed from one to the next.

The result is well known. Every lookup costs a trip or a phone call, documentation for machines that no longer exist keeps taking up space, and documentation for the machine that does exist is missing or wrong — very common when the equipment was bought secondhand from a company that closed and nobody handed over its technical documentation.

The two types of maintenance documentation

It’s worth separating them because they have different problems and get solved in different ways.

Technical documentation. This describes the facilities, machines, systems, and services: manuals, drawings, schematics, manufacturer spec sheets, certificates, specifications, and recommended maintenance frequencies. It answers “what is this and how often does it need attention.” It’s the worst controlled, the one most often stuck on paper only, and the one most likely to be lost when someone retires.

Management documentation. This splits into two. Maintenance management documentation covers work orders, inventories, and incident records: they get filled in, handed over, and archived for good within days, which means no real control over breakdowns is kept. The financial side is the spending, and it’s almost always the only part that’s fully documented and computerized, because maintenance is viewed as a cost, and costs get watched.

That asymmetry explains a lot: we know how much we’ve spent and we don’t know what condition the machine is in.

Why there’s no traceability without documentation

Reconstructing the history of a piece of equipment — let alone of a specific component within it — is practically impossible when everything has been managed on paper and the old stuff has been archived away to avoid piling up. Without that history, you can’t know what condition the machine is in or how it’s evolved over the years, and so you can’t go beyond generic preventive maintenance: there’s no reliable data to base a better decision on.

Traceability isn’t a bureaucratic requirement. It’s what lets you answer whether this machine should be repaired again or replaced, whether its inspection frequency is set correctly, and whether today’s failure had already given warning before.

How it’s organized inside a CMMS

The difference between a generic document manager and a CMMS’s is where the document hangs. On a shared drive, a manual sits in a folder; in GMAO Cloud it hangs off the asset, and it appears when someone opens that asset.

Documents can be attached to almost any entity in the system: customer, supplier, address, machine, system, incident, quote, work order, machine model, family, vehicle, technician, purchase order, project, maintenance task, tool, and personal protective equipment. That list matters because it’s what removes the usual question — where do I save this? — you save it where it will be looked for.

Each document also carries its visibility: whether the client sees it, whether the technician sees it, whether the supplier sees it, whether it requires validation. That way, nobody has to manually decide what to show every time someone asks for something, and a supplier who stops working with you loses access without anyone having to move a single file.

Certificates get their own handling, with their number, scope, issuer, holder, and fingerprint, because a certificate isn’t just any PDF: it’s proof that something was done in compliance with something.

Expiration, which is what people appreciate most

Some documentation doesn’t last forever: official inspection certificates, contracts, insurance policies, authorizations, waste management records, approvals. In GMAO Cloud a document can carry an expiration date, and there’s a daily check for what’s about to expire that generates the corresponding alert.

The same applies to staff personal protective equipment, which also expires and whose renewal tends to be discovered too late.

This turns document management into something active. The difference between having the certificate on file and having the system warn you a month before it expires is the difference between staying on top of things and finding out during an inspection.

Where it gets consulted

The place where technical documentation is needed isn’t the office: it’s in front of the machine. In the technician app the operator has the equipment history and its associated documentation without calling anyone, and the app stores those documents on the device, so they stay available in a basement with no signal.

On the other side, the client portal lets clients download the report for each intervention themselves and upload any documents they want to attach, instead of requesting them by phone.

The history as proof

There’s a use of documentation that’s only appreciated the day it’s needed: defense. Facing a client complaint, an incident, or an inspection, what gets asked for isn’t an explanation — it’s a record.

A valid record has a date, an author, what was checked, and, when relevant, who signed off. That can’t be manufactured after the fact. In a CMMS it comes straight out of the normal work flow: the closed work order with its times, materials, photos, and completed checklist, plus the documentation attached to the asset with its dates.

Legal maintenance rests on that, and in GMAO Cloud it isn’t a separate module: it’s done with the preventive maintenance mechanism, by attaching the checklist the standard requires to the asset, its model, or its family, and defining the frequency. It’s worth stating precisely: the software records and proves; the company is the one that complies with the standard.

What to do with what’s already on paper

Migration is the part that scares most people off, and almost always because it’s approached backwards. Digitizing twenty years of archives before starting is a project that never finishes.

What works is the opposite: start with the documentation for critical assets — the ones that halt production or service — and for anything with an expiration date, since that’s what generates real risk. The rest gets added as it’s needed: the first time someone looks for a manual and it isn’t there, it gets scanned and hung off the asset. After a few months, what gets consulted is digitized, and what never gets consulted stays in the cabinet, which is exactly where it should be.

If you’d like to see how your equipment documentation would look organized this way, you can request a demo.