20 old computers stacked in a warehouse corner, 5 company cars parked in the basement, a projector in the 5th-floor meeting room unused for a year — idle assets tie up net value and still accrue depreciation. Status analysis auto-identifies "long-idle" by usage frequency and offers activation suggestions.
See clearly which assets are creating value and which are tying up resources
The count and net-value share of requisitioned assets — the normal operating state and the organization's main asset value
Assets with no usage record for 30 / 60 / 90 / 180 days are identified as idle, tallied by tier
Counted separately during repair; analyze whether the under-repair share is too high (hinting at aging or insufficient servicing)
Assets with disposal requested but not completed — a long disposal cycle is a source of compliance risk
A trend curve of the four-state share over the last 12 months, to see whether the idle rate keeps rising
For long-idle assets, the system suggests an action: "transfer to a department in need / sell for residual value / scrap and clear out"
Judging idle only by "whether requisitioned" is too coarse — requisitioned but not scanned/checked in for 6 months also counts as idle. The system comprehensively analyzes "last scan time / last repair / last servicing / last checkout" to judge "actually in use vs nominally requisitioned" across multiple dimensions.
20 idle PCs stuck for 1 year ≈ ¥48,000 loss
How much do 20 idle computers sitting in a warehouse lose in a year? At an average monthly depreciation of 200 each, that's 48K. Status analysis computes "holding cost vs disposal benefit" for each idle asset and gives a specific suggestion: transfer to Dept X / sell at an estimated X / scrap and dispose.
At the start of each quarter, admin clears last quarter's idle assets, batch-launching transfers / disposals per the system's suggestions, raising asset turnover by 20%.
A branch is short 5 projectors while HQ's warehouse has 8 idle; the system auto-matches and admin launches a cross-company transfer, sparing a new purchase.
For year-end fixed-asset impairment, finance accrues impairment provisions from the status analysis's "long-idle + long-under-repair" detail.
The IT manager finds laptops' "under repair" share above 8% for 3 straight months, and combines it with repair cost data to decide a bulk replacement of a model.
Status is the result, a cross-section of all kinds of business actions
Slice the distribution by "which department has a high idle rate" / "which category has a high repair rate"
Status is the coarse classification, utilization efficiency the fine data — best analyzed together
The execution entry for the "transfer" action in activation suggestions
The execution entry for the "dispose" action in activation suggestions
Sign up to experience the full asset management suite for free, or book a consultant demo