Asset Management

1. Feature Overview

Assets in tamato represent the physical equipment, machines, or infrastructure that your organization owns, operates, or maintains. They act as the central reference point for maintenance activities, costs, and history.

This feature exists to give teams a single, reliable source of truth for asset data. By structuring assets correctly, organizations improve maintenance planning, traceability, and decision-making.

---

2. When to Use This Feature

Use the Assets feature whenever equipment or infrastructure needs to be tracked and maintained over its lifecycle.

Typical use cases include:

• Registering machines, vehicles, HVAC units, or production equipment

• Structuring asset hierarchies (e.g. machine → subcomponents)

• Linking work orders and preventive maintenance to equipment

• Tracking warranty, cost, and vendor information

Assets are typically used by:

• Maintenance managers managing asset portfolios

• Technicians executing work on specific equipment

• Operations teams needing visibility into asset status and history

---

3. Step-by-Step Instructions

To create an Asset in tamato:

1. Navigate to Assets in the main menu

2. Click Create Asset

3. Fill in the required fields:

   • Title (required)

   • Select Parent Asset (optional)

   • Upload picture or attachment (optional)

   • Criticality (required)

   • Select vendor or manufacturer (optional)

   • Serial number (optional)

   • Model (optional)

   • Year (optional)

   • Description (optional)

   • Assign the asset to a user or team (optional)

   • Price (optional)

   • Purchase date (optional)

   • Warranty expiry date (optional)

   • Label (optional)

   • Location (optional)

   • Files (optional)

4. Click Create

The asset is created and stored immediately.

---

4. Field Explanations

Title	The name of the asset	Required	Use a clear, standardized naming convention (e.g. “Cooling Unit – Warehouse A”).
Parent Asset	Defines hierarchical relationships between assets.	Optional	Use parent assets to model systems and subcomponents.
Picture / Attachment	Images or reference documents for the asset.	Optional	Upload photos or schematics for easier identification.
Criticality	Indicates how important the asset is to operations.	Required	Base criticality on safety, downtime impact, and replacement cost.
Vendor / Manufacturer	Company that supplied or produced the asset.	Optional	Useful for warranty claims and spare parts sourcing.
Serial Number	Unique identifier assigned by the manufacturer.	Optional	Always enter serial numbers for traceability.
Model / Year	Manufacturer model and production year.	Optional	Helps with documentation, manuals, and lifecycle planning.
Description	Additional details about the asset.	Optional	Include operating conditions or special characteristics.
Assigned User or Team	Responsible owner of the asset.	Optional	Improves accountability and response times.
Price / Purchase Date	Acquisition cost and date.	Optional	Useful for depreciation and cost analysis.
Warranty Expiry Date	Date when warranty coverage ends.	Optional	Track to avoid unnecessary repair costs.
Label	Tags for grouping or filtering assets.	Optional	Use labels consistently for reporting.
Location	Physical location of the asset.	Optional	Keep locations up to date to support field work.
Files	Additional documents such as manuals or certificates.	Optional	Store critical documentation directly on the asset.

---

5. What Happens After Submission

After submission:

• The asset becomes available across the system

• It can be selected in Work Orders, Preventive Maintenance, and Predictive Maintenance

• Asset history starts tracking all related maintenance activities

• No approvals are required unless configured by role settings

The asset becomes the central reference for all future maintenance work.

---

6. Permissions & Roles

Permissions depend on user roles:

• Maintenance Managers can create, edit, and delete assets

• Technicians can view assets and access related work orders

• Other users may have view-only access depending on configuration

Users without sufficient permissions cannot modify asset data.

---

7. Common Mistakes & Tips

• Avoid vague asset names like “Machine 1”

• Always set criticality for meaningful prioritization

• Use parent assets to avoid flat, unstructured asset lists

• Keep warranty dates up to date

• Attach manuals to reduce time spent searching for documentation

---

8. Short Summary

Assets are the foundation of maintenance management in tamato. They provide structure, history, and context for all maintenance activities.

Well-maintained asset data leads to better planning, faster execution, and more reliable operations.