Keep every machine's full history on its own record: scan the asset's QR code and discover everything that has happened to it.

No, and it's worth being clear about it: Solved doesn't track spare parts stock, costs, or labor hours. It tracks the operational detail of the equipment: who reported it, which record detected it, what action was left open, and when it was closed. If you already have a CMMS, Solved integrates with it; if you don't, Solved builds the equipment's history from the work the plant is already doing. Details in CMMS and maintenance.

By asset type. Each type — machinery, facilities, measuring equipment — defines its own attributes: criticality, status, manufacturer, model, type and location are the usual ones, configured according to what each plant needs to track. Assets are loaded once and from then on are available in incidents, records and actions.

Every asset has its own code. You download or print it from its record and stick it on the machine. Scanning it opens that asset's record: what has happened to it, what is open and the place from which anything new is logged, with no searching through a list.

Yes, with the records module. The plan is scheduled as a record with its frequency, its owner and its date, and the system warns before it falls due. A check that comes back KO opens the incident automatically, attached to the asset and to the record it came from.

Yes. An asset is anything whose history you want to track: a line, a tank, a cold room, a measuring instrument, a vehicle or a facility. What changes from case to case is the asset type and the attributes it carries.

Yes. Each asset's incidents and actions feed the same KPIs as the rest of the system, so repeat failures stop being viewed only by area and can be viewed by asset: which machine concentrates the breakdowns and which one recurs after being marked closed.