Skip to main content

​
Overview

Components are parts that are installed into assets. Unlike accessories (which are checked out to users) or consumables (which are used up), components become a permanent part of another asset until removed.

​
What Are Components?

Common examples:
  • RAM modules - Installed in laptops or servers
  • Hard drives / SSDs - Storage upgrades
  • Network cards - Ethernet or WiFi adapters
  • Video cards - GPU upgrades
  • Power supplies - Replacement PSUs
  • Processors - CPU upgrades
  • Batteries - Replacement batteries
Components are tracked by quantity but assigned to specific assets with a quantity per assignment.

​
Key Characteristics

Asset-Installed

Components are checked out to assets, not users or locations.

Quantity Tracking

Track total quantity and how many are assigned to each asset.

Asset History

Full history of where components were installed.

Cost Tracking

Component costs add to total asset value.

​
Creating Components

1

Basic Information

  • Component name (e.g., “16GB DDR4-3200 RAM”)
  • Category (components category)
  • Total quantity on hand
  • Model number (optional)
  • Serial number (optional, for specific tracking)
2

Purchase Details

  • Supplier
  • Purchase cost per unit
  • Purchase date
  • Order number
3

Inventory Settings

  • Minimum quantity alert threshold
  • Default storage location
  • Manufacturer
  • Company assignment
4

Additional Info

  • Upload component image
  • Add technical specifications
  • Internal notes

​
Checkout Process

​
Assigning Components to Assets

1

Navigate to Component

Find the component you want to install
2

Click Check Out

Select “Check Out” from component details
3

Select Asset

Choose which asset to install component into
4

Specify Quantity

Enter how many units to install (defaults to 1)
5

Add Notes

Optional installation notes (e.g., “Upgraded from 8GB”)
6

Confirm

System records:
  • Which asset received the component
  • Quantity assigned
  • Date of installation
  • Who performed the installation
You can only check out components to assets - not to users, locations, or other entity types.

​
Check-In Process

​
Removing Components from Assets

When a component is removed:
  1. Find the asset with the component
  2. View installed components
  3. Click “Check In” on the component
  4. Quantity returns to available pool
  5. History preserved in audit log
Partial check-ins are supported - you can remove some but not all units if multiple were installed.

​
Quantity Management

​
Available vs. Assigned

Total Quantity = 50 units
Assigned to assets = 35 units
Available = 15 units

​
Viewing Assignments

See which assets have which components:
  • Asset name and tag
  • Quantity installed
  • Installation date
  • Who installed it
  • Installation notes

​
Minimum Quantity Alerts

Set thresholds to trigger alerts:
  • Get notified when stock is low
  • Plan component purchases
  • Prevent upgrade delays
  • Email notifications

​
Asset Value Impact

Components add to asset value: 
Asset Purchase Cost: $1,200
+ 32GB RAM (2×16GB): $120
+ 1TB SSD Upgrade: $150
= Total Asset Value: $1,470
The getComponentCost() method calculates total component value per asset.

​
Component Categories

Organize by component type:
  • DDR3/DDR4/DDR5 RAM
  • SODIMM vs. DIMM
  • Different capacities
  • ECC vs. non-ECC
  • Hard drives
  • SSDs (SATA, NVMe, M.2)
  • Storage controllers
  • RAID cards
  • Ethernet cards
  • WiFi adapters
  • Bluetooth modules
  • Fiber cards
  • Power supplies
  • UPS batteries
  • Power cables
  • Battery packs
  • Video cards
  • Graphics processors
  • Display adapters

​
Custom Fields

Track component-specific data:
  • Specifications - Speed, capacity, voltage
  • Compatibility - Which models it works with
  • Warranty - Component-specific warranty
  • Part Numbers - OEM and aftermarket
  • Technical Details - Form factor, interface

​
Reporting

​
Inventory Reports

Stock Levels

Current quantity, assigned, and available for each component type.

Low Stock

Components below minimum quantity needing reorder.

Asset Components

What components are installed in each asset.

Component Value

Total inventory value and cost per asset.

​
Usage Analysis

  • Component checkout history
  • Most frequently installed components
  • Upgrade trends over time
  • Cost analysis for upgrades
  • Supplier performance

​
Multi-Company Support

For organizations with multiple companies:
  • Assign components to companies
  • Company-scoped inventory
  • Prevent cross-company assignments
  • Independent reporting per company
  • Shared or dedicated component pools
The CompanyableScope ensures components are only visible and assignable within their company context.

​
Location Tracking

Manage component storage:
  • Default storage location
  • Track where unassigned components are kept
  • Multi-location inventory
  • Easier physical audits
  • Location-based access

​
Acceptance Requirements

Components can require acceptance:
  • Set at category level
  • User (of assigned asset) must accept
  • Email notification sent
  • Track acceptance status
  • Declined components returned

​
Cost Tracking

​
Per-Component Cost

Unit Cost: $75
Quantity: 20
Total Value: $1,500

​
Total Asset Cost

Assets can calculate total component cost: 
$asset->getComponentCost()
// Returns sum of all installed component costs

​
Financial Reporting

  • Track component spend
  • Upgrade costs per asset
  • Budget for replacements
  • Supplier cost comparison

​
Checkout Notes

Document installations:
  • Why component was installed
  • What it replaced
  • Configuration changes
  • Performance improvements
  • Issues encountered
Use checkout notes to create an upgrade history for each asset.

​
Best Practices

Include specifications in the name: “Crucial 16GB DDR4-3200 SODIMM” instead of just “RAM”.
Use custom fields or notes to document which asset models components work with.
For high-value components, include serial numbers for warranty tracking.
Always document what was replaced and any configuration changes made.
Verify component inventory matches physical stock, especially before ordering.
Set minimums based on:
  • Common failure rates
  • Supplier lead times
  • Standard upgrade quantities
  • Emergency replacement needs

​
Common Workflows

​
RAM Upgrade

  1. User requests more memory
  2. Check available RAM components
  3. Check out 2× 16GB to user’s laptop
  4. Note: “Upgraded from 2×8GB to 2×16GB”
  5. Old RAM returned to stock (if kept)
  6. Asset value automatically updated

​
Hard Drive Replacement

  1. Hard drive fails in server
  2. Check out replacement drive to asset
  3. Document: “Replaced failed drive in RAID array”
  4. Failed drive marked as disposed
  5. Component history shows all drive changes

​
New Build

  1. Create new asset (computer)
  2. Check out components:
    • Motherboard
    • CPU
    • RAM (multiple units)
    • Storage drives
    • Power supply
  3. Total component cost added to asset value
  4. Complete build documentation in notes

​
Limitations & Considerations

Components use a caching mechanism for checkout counts. When modifying component quantities programmatically, use numCheckedOut(true) to recalculate.

​
Cannot Do

  • Check out to users or locations
  • Track individual serial numbers per unit (without custom fields)
  • Depreciate separately from assets
  • Have maintenance records

​
Can Do

  • Track which assets have which components
  • Maintain complete installation history
  • Calculate total component cost per asset
  • Alert on low stock
  • Support multi-company deployments

Build docs developers (and LLMs) love

Get started for freeTalk to us