Asset tag

The sticker you put on the machine: its code in large type, where it is and a QR code to reach its history.

etiqueta-de-equipo, with the estandar design: a 100 × 50 mm label, not a sheet of paper.

"asset": {
  "codigo": "EQ-PE-002",                                          // required
  "nombre": "Planta eléctrica de emergencia",
  "ubicacion": "Cuarto técnico, sótano 2",
  "marca": "Cummins", "serie": "C150D5-2019-884"
},
"yourCompany": { "name": "Piensa IT S.A.S." },                    // who maintains the asset
"qr": "EQ-PE-002|…|https://…",                                    // optional
"nota": "No retirar esta etiqueta · Mantenimiento: 3125655293"

• It carries the asset and little else, on purpose. The more data it carries, the sooner it goes stale stuck to a machine: the latest work order changes every week and the owner every year; the code, the name and the location last as long as the equipment does. What changes is looked up through the QR, which is exactly what it is for.
• The QR is drawn with the content you send, never with a URL built here. Without qr, the asset code is encoded; without a code there is no QR either.
• The only required field is asset.codigo: a tag that doesn’t identify the equipment is good for nothing. Without it, 400.
• The paper is the label itself: 283 × 142 points (100 × 50 mm), ready to print on adhesive stock.
• In four more colours, with plantilla: corporativa (blue), profesional (green), minimalista (violet) and basica (orange). They tint the label and the code, not the rest: the tag is printed on adhesive and sometimes on a thermal printer. It is meant to be told apart from a distance —by area, by criticality, by whatever you decide—; with estandar it comes out in black, as before.

Example: etiqueta-de-equipo.json.