Ativos instalados

A customer may have six elevators in the same building, and each one has its own record, history and inspection report. Registering the equipment — and not just the address — is what lets you answer "how many times did this machine stop this year" without opening a spreadsheet.

The equipment located at the customer: elevator, extinguisher, lightning rod, split air conditioner. Each asset lives at a site, belongs to a contract and carries its plan, its inspection history and its reports. — this is the role of the "Installed assets" screen within the platform.

In the tabs you'll find the maintenance plan, the service history, the reports issued and the open pending items. It's the screen the manager opens when the customer calls asking about a specific machine.

First register the customer's site (the building, the warehouse, the store). Then choose the equipment type — the type brings the inspection checklist and the report's validity period. Finally, fill in the record and create the maintenance plan. From the plan onward, preventive jobs start being generated on their own.

The Import button, in this list's toolbar, accepts a CSV file with the complete installed base — someone with 2,000 extinguishers in a spreadsheet does not register them one by one. First download the template (the header is the file's contract); after the upload, the review appears: what will be created, what will be changed and what was rejected, with the reason for each rejection written on the line. Nothing is saved before you confirm — and if nothing changes, the screen says so.

The Label tab only appears when the equipment already has a QR generated. It shows the label ready in the 60×40 mm thermal size — with the QR, the identification and the location printed together, so whoever sticks a hundred labels knows which goes on which machine before scanning. The Print button opens the PDF; below it is the address the QR points to, in a field you copy with one click. Useful for testing the scan before sticking it.

Without a maintenance plan, no preventive job is generated for that equipment. It does not disappear from the list, but it disappears from the schedule — and the difference only shows up when the customer asks about the visit nobody scheduled. The installed base dashboard counts how many are in this situation.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

The label is already stuck on the machine, and a label that points to the wrong equipment is worse than no label at all. That's why the code is not regenerated on saving.

History, Reports, Nonconformities and Plan are read-only tabs: the history comes from the executed work orders, the reports from issuance and the pending items from the inspection — none of them is entered in the record. Each tab has its own paginated table, and an expired report appears with its validity highlighted in red. If the Plan tab is empty, the button in its footer goes straight to the maintenance plans screen to create one.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

"What equipment do I maintain, and where?" — when this question comes up, this is the screen that answers it.

This list is built on the standard engine: it exports Excel, PDF and CSV of the entire set (not just the visible page), keeps saved views per user, has a recycle bin (add ?excluidas=1 to the URL) and column preferences per user. It also accepts filtering directly through the URL — ?q=texto searches, and ?fd_=valor filters by a dictionary field —, which is how the totals on the compliance dashboard open this list already filtered to the same set.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".

Each piece of equipment gets its own code, and the record shows the full address it opens. Print that address as a QR on a label and stick it on the machine: the phone's own camera recognizes it and opens the inspection already on the right equipment, without picking anything from a list. In a machine room with six identical elevators, choosing the wrong one is the easiest mistake to make and the hardest to discover later. The platform doesn't print the label yet — it provides the address, and any QR generator completes the path.