Assets, Parts, and Vendors

Assets are the backbone of the workspace

The more accurate your asset records are, the better your reporting, PM coverage, downtime review, and downstream intelligence become.

Each important asset should feel like a durable operational record, not a temporary spreadsheet row.

Use parts to support real maintenance work

Parts become useful when they help answer practical questions:

• what was consumed
• what should be reordered
• what work depends on this stock
• which assets regularly consume the same components

Use vendors as an operational directory

Vendor records should save time when something fails.

A good vendor record includes:

• company name
• service type
• primary contact
• phone and email
• rates if you track them
• compliance or insurance context if needed

Connect the records together

The app gets more useful when these records are linked:

• asset to vendor
• asset to document
• work order to part usage
• work order to vendor involvement

That turns Rivolq into a usable operating memory instead of a set of disconnected tables.

What to avoid

• generic vendor records with no contact information
• part lists with no clear units or naming standards
• critical assets that have no supporting documents or service context
• keeping maintenance history in email while asset records stay empty