Welcome To The Foreman Knowledge Base

Module 5: Managing Assets and Inventory within Tickets

The Tickets tool in Foreman is more than just a place to log and resolve issues—it’s also the central hub for tracking assets and inventory throughout their lifecycle. Whether you’re performing repairs, moving equipment, or replacing components, assets and inventory integrate directly with tickets to give technicians a full operational picture of what’s being used, where, and when.

This section explains how assets and inventory tie into ticket workflows, helping teams maintain accurate records, streamline maintenance, and prevent downtime caused by misplaced or unavailable equipment.

Goal: Assets and inventory are integrated into ticket workflows for full traceability.

unchecked Created test ticket with linked assets

unchecked Added inventory to a ticket and verified quantity decreased

unchecked Viewed ticket history and confirmed asset/inventory activity logged

unchecked Printed a sample ticket to verify format

unchecked Reviewed asset history from ticket linkage

unchecked Confirmed team understands how to link items to tickets

 

Complete Ticket Workflow: From Issue to Resolution

Understanding how Assets and Inventory integrate into the complete ticket lifecycle helps your team maximize traceability and efficiency. Here's how a typical maintenance ticket flows from start to finish:

Workflow Example: Replacing a Failed Cooling Fan

1. Ticket Creation

  • A monitoring alert detects high temperatures on Miner "SN-67890."
  • Technician opens a new ticket: "High Temp Alert – Miner SN-67890."
  • In the ticket form, the technician:
    • Links the affected Asset (Miner SN-67890) in the Device Details section
    • Adds a description: "Temperature exceeding 85°C, suspected fan failure."
    • Assigns to: Maintenance Team

2. Diagnosis and Inventory Check

  • The technician inspects the miner and confirms Fan #2 has failed
  • From within the ticket, the technician checks the inventory:
    • Searches for "120mm Cooling Fan" in the Inventory field
    • Sees current quantity: 47 fans available in Warehouse-A-Shelf-12
    • Adds "120mm Cooling Fan" (Quantity: 1) to the ticket

3. Inventory Assignment  Automatic Update

  • When the technician saves the ticket with inventory attached, Foreman automatically:
    • Reduces available inventory: 47 → 46 fans remaining
    • Marks 1 fan as "Assigned" to this ticket
    • If the new quantity (46) falls below the notification threshold (e.g., 50), send a low-inventory alert to procurement

4. Repair Completion

  • The technician replaces the failed fan
  • Updates ticket with resolution notes: "Replaced Fan #2, temps now normal at 62°C."
  • Mark's ticket as "Resolved."
  • Optionally: Adds the old, failed fan to inventory as "Defective – Warranty Claim" for RMA tracking

5. Asset History Update Automatic Logging

  • The Asset record for Miner SN-67890 now shows:
    • Ticket #12345 is linked to its history
    • Timestamp of the repair
    • Component replaced (120mm Cooling Fan)
    • The technician who performed the work

6. Reporting and Analysis

  • Operations Manager exports Asset History Report
  • Identifies that Miner SN-67890 has had 3 fan replacements in 6 months
  • Decision: Move this miner to a location with better airflow, or replace it entirely

Key Workflow Benefits

  • No double data entry: Inventory quantities update automatically when assigned to tickets 
  • Complete audit trail: Every part used is tracked to a specific ticket, asset, technician, and timestamp 
  • Proactive alerts: Low inventory notifications trigger before you run out of critical parts 
  • Performance insights: Asset history reveals patterns (e.g., which miners require frequent repairs)  
  • Accountability: Clear record of who performed work, when, and what parts were used

 

How Inventory Updates Work in Tickets

Automatic Inventory Reduction: When you add an inventory item to a ticket and save, Foreman automatically marks that quantity as "Assigned." The item remains assigned until the ticket is resolved or closed. Once resolved:

  • The assigned quantity is deducted from the total available inventory
  • The part is permanently logged in the ticket's history
  • Asset records reflect the component replacement

Manual Inventory Adjustments: If you need to return unused parts to inventory:

  1. Open the ticket
  2. Click the Actions menu next to the inventory item
  3. Select "Remove" or reduce the quantity
  4. The inventory count automatically increases to reflect the return

Verifying Inventory Was Reduced: To confirm inventory updated correctly after assigning to a ticket:

  1. Navigate to Operations → Inventory
  2. Search for the item you assigned
  3. Check the "Assigned" column—it should show the quantity currently attached to open tickets
  4. Check the "Quantity" column—it should reflect total available stock minus assigned items

If inventory doesn't update: Verify the ticket was saved, check that the inventory item was added in the Inventory section (not just mentioned in notes), and refresh the Inventory page.

 

Accessing and Viewing Ticket History

From the left-hand menu, select Tickets, then click View History in the upper-right corner.
This opens a log of all ticket activity, allowing technicians to trace how assets and inventory have moved across the facility over time.

Each entry shows actions taken on assets—such as replacements, transfers, or repairs—providing a clear chain of custody for every part. This visibility helps prevent duplication, ensures accountability, and supports long-term performance analysis.

You can export all ticket history from the modal, or click the ellipses menu → History on an individual ticket to see the detailed timeline for that specific case.

 

Tracking Asset and Inventory Activity through Tickets

Each ticket acts as a record of both the operational issue and the physical resources involved. When technicians log a maintenance ticket, they can associate one or more assets (e.g., miners, control boards, power supplies) and link related inventory items (e.g., fans, cables, replacement hashboards).

This connection ensures that all parts used or affected during the ticket’s lifecycle are documented in one place—making audits, repairs, and resource tracking much simpler.

For example:

  • If a technician replaces a faulty fan, they can attach the fan inventory item to the ticket, automatically reducing the inventory count.
  • If an entire miner is swapped out, the asset record will reflect the replacement and update its operational history.

This integration minimizes manual data entry and keeps your system synchronized in real time.

 

Using Inventory Lists within Tickets

Within a ticket, click into the Inventory field to search, add, or remove items from your facility’s inventory. Each item displays its current quantity and threshold status, so technicians can confirm availability before starting work.

If the stock of a particular part (for example, replacement fans or cables) reaches its low threshold, a notification can automatically alert the team—helping prevent shortages that delay maintenance.

For more detailed setup guidance, refer to the Inventory Threshold Alerts section.

 

Viewing and Managing Assets Linked to Tickets

From the Ticket Details Page, scroll to the Device Details Table to view all devices connected to the ticket.

Here, you can:

  • See the linked Assets, Miners, or Infrastructure
  • Add or remove assets as needed
  • Click asset names to open their full record (in a new tab), showing detailed operational and repair history.

This linkage creates a direct bridge between ticket activity and asset management, ensuring that performance data and maintenance history are always aligned.

For example, when a technician marks an asset as In-Repair through the ticket, its miner state automatically updates—keeping the broader system consistent without requiring extra manual updates.

 

Printing Tickets for Maintenance and Asset Tracking

If you need a physical record of work performed or a paper checklist for field technicians, you can generate a PDF of any ticket. From the ellipses menu next to a ticket, click Print to open the printable version. This printed form can include linked assets, inventory items used, timestamps, and comments—making it ideal for internal documentation or compliance reviews.

Asset and Inventory History

To view asset-level activity, go to Assets from the left-hand menu, then click View History. This shows every recorded change—such as repairs, movement, or replacements—associated with that asset. Similarly, inventory usage tied to tickets will reflect in your Inventory List, ensuring your stock levels stay accurate over time.

Together, these views provide full traceability from inventory stock → ticket resolution, → asset performance, creating a transparent operational ecosystem.

Why It Matters

Integrating assets and inventory with tickets provides more than just convenience—it creates a unified system of record across operations. By tying every repair, replacement, and movement to a specific ticket, teams gain:

  • Complete traceability for compliance and accountability
  • Accurate stock levels that reflect real usage
  • Reduced downtime, since parts availability and asset states are always up-to-date
  • Actionable insights into maintenance patterns and performance trends

This end-to-end visibility ensures every technician, manager, and system stays aligned—so the right assets and parts are always in the right place, at the right time.

 

Step Complete :tada:

At this point, your Assets, Inventory, and Tickets are fully integrated. You can now:

  • Track every maintenance or repair event from start to finish
  • Automatically update inventory levels as parts are used
  • Maintain an accurate, auditable record of asset history and status

     

With your tickets connected to your operational data, you’ve built the foundation for data-driven facility management—where every movement, replacement, and repair is traceable and actionable.

Next, we’ll move on to  Cycle Counts, where we’ll connect these systems directly to live operational data for real-time monitoring and automation.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.