What modules GMAO Cloud has

A list of modules says little on its own, because every system in this market uses the same words. What’s actually worth explaining is what each part solves and how it connects to the rest, because it’s in the connections that a CMMS sets itself apart from a pile of tools.

Here’s the tour.

The core: assets and orders

Asset management. Each piece of equipment’s record, with its model, serial number, installation date, cost, warranty end date, location, priority and any custom fields it needs with their unit. Grouped by system, family and model, with a QR code and a counter where it applies.

Work orders. The unit everything revolves around: target time, estimated time and deviation, cause of downtime, warranty status, materials consumed, checklist, photos and signature.

Everything else hangs off these two.

How work comes in

Incidents. With their type and subtype, priority, client, address and affected equipment. They come in from the backend, from client access with a photo, or from a mailbox the system turns into requests. Statuses carry their own maximum time and associated email.

Preventive maintenance. The checklist attached to the asset, its model or its family, with its frequency — several at once if needed. It checks holidays and availability before generating. And it supports triggering by counter: once the configured threshold is crossed, the order generates on its own.

Checklists. The report templates, with their fields, their minimum and maximum values and their anomalies, resolved in a cascade by asset, model, subfamily and family.

Where it gets executed

Technician app. The day’s orders, sorted by route using GPS, timer, material consumption, checklist, photos and signature. It works without coverage and syncs once signal is back.

Client access. The client opens incidents, tracks their orders, downloads reports and sees their upcoming preventive visits on a calendar. They can’t change statuses — a product decision — and it doesn’t work offline.

Calendar. Load per technician, unassigned work that stands out visually, and rescheduling by dragging.

What gets consumed and purchased

Warehouses and items. Several warehouses — including the van — each with its own valuation method; items with cost, sale price, minimum stock and original reference; batches with expiration dates; transfers with request and approval; rates and prices per supplier.

Purchasing. Orders with their supplier, destination warehouse, status, lines and amounts.

Budgets. Created from an order and generating another one when accepted, with their own PDF and email templates.

What backs up the proof

Document manager. Documents attached to almost any entity, with visibility by role and expiration alerts. Certificates with their number, scope, issuer and holder.

Legal maintenance. Worth repeating: it isn’t a module. It’s achieved through preventive maintenance, the checklist the regulation requires and its frequency, and the proof comes from the history, the checklists and the documentation.

People and resources

Staff management. Shifts, working hours, vacation, holidays, teams with a supervisor, and PPE with expiration dates. It isn’t HR software: it’s what’s needed to be able to plan.

Notification system. Push and email alerts, email tied to status changes, document expiration alerts, and the option to mark which ones shouldn’t notify.

Projects and works

Projects and works for work that isn’t recurring. It’s worth knowing their real scope: a work project distributes daily reports between two dates so workers can log their work, but there are no work items, measurements, or partial certifications. It isn’t a construction project management program.

What comes out of all of it

Reports. More than sixty, with filters and export, plus a dashboard. And if you need your own dashboards, your BI tool connects via REST API or SQL.

Integrations. Production connectors with Business Central and Navision, SAP, Sage X3, Holded, Factura Directa, QuickBooks, STEL Order and niche systems, plus REST API, SOAP, SQL, CSV and FTP. The scope of each one isn’t the same.

And artificial intelligence

Scoped features: an assistant over your assets and history — also in the app —, document reading, help writing order text, and translation of your catalogs. It proposes, it doesn’t execute, and every feature has its own toggle, most of them off by default. Covered in detail in AI in GMAO Cloud.

Where the connections that matter are

The list above makes more sense once you look at what connects to what, which is what sets a system apart from a pile of tools.

The order connects almost everything. It receives the asset — and feeds its history and cost —, deducts from the warehouse, charges hours to the technician, originates from an incident or from preventive maintenance, and travels, closed, to the ERP.

The asset connects backward. Its family determines which checklist applies to it, its counter can trigger preventive maintenance, its warranty end date avoids paying for covered repairs, and its accumulated cost decides whether it gets replaced.

The document connects with permissions. Its visibility by role is what makes the client portal work without supervision.

When one of those connections goes unused — orders without an asset, documents without visibility, assets without a family — the system keeps working but loses exactly what made it useful two years down the line.

Three product decisions that shape everything else

More than the list of modules, this is what determines how the system gets used.

It’s cloud-based. No server to maintain, no per-seat installation, and it’s accessed from a browser, phone or tablet with each person’s own permissions.

It isn’t priced per user. Licenses are unlimited across all three plans. This matters more than it looks: when every new account costs money, accounts get shared, and at that point the history stops being valid as evidence and permissions become decorative.

Each role enters through its own door. Backend for whoever plans, app for whoever executes, dedicated access for the client. It’s not the same screen with things hidden: it’s three interfaces for three needs that don’t look alike.

What you don’t need to turn on day one

Almost none of the above. You start with critical assets, checklists, frequencies and field logging. Warehouse, purchasing, budgets and the client portal come in once the first part has been running smoothly for weeks.

If you want to see which part fits your case, you can request a demo.