What Is Asset Uptime?

Asset uptime is the percentage of scheduled operating time during which an asset is actually available and working. It is the simplest answer to the question “can we rely on this thing?” - and the headline number that planned and unplanned maintenance decisions are ultimately judged against.

The uptime formula

Uptime = (scheduled operating time - downtime) ÷ scheduled operating time × 100.

A worked example: a workshop compressor is scheduled to run 40 hours in a week. A blown hose stops it for 2 hours on Wednesday. It ran 38 of its 40 scheduled hours, so uptime for the week is 38 ÷ 40 = 95%.

The arithmetic is trivial; the definitions are where teams disagree. Decide up front what “scheduled time” means (24/7, or working hours only?) and whether planned servicing counts as downtime. The common convention is to exclude planned maintenance windows from scheduled time, so the figure isolates unexpected failures - the stoppages you can actually do something about.

Uptime vs availability vs reliability

The three words get used interchangeably, but they answer different questions:

• Uptime - was the asset running during the hours it was supposed to run?
• Availability - could the asset have been used whenever it was needed? This usually accounts for planned maintenance too, and exposes assets that are “up” but unusable - out of calibration, missing a part, or simply nowhere to be found.
• Reliability - how often does it fail? Two assets can post the same uptime, one with a single long outage and the other with a stoppage every shift. The second is far less reliable, and far more disruptive.

The distinction matters beyond machinery. Safety kit such as fall protection equipment that has missed its inspection date is effectively down even though nothing is broken - it cannot lawfully be used.

What drags uptime down

The usual suspects are unglamorous: skipped servicing that lets small wear become a breakdown, repairs that stall waiting for a part nobody stocked, and “mystery downtime” - the asset is fine but checked out to someone unknown, sitting in the wrong van, or waiting on a repair ticket no one is watching. For shared kit such as HVAC tools, time spent hunting for an instrument is downtime in every way that matters, even though the tool itself never failed.

Realistic uptime targets

IT teams talk in “nines” - 99.9% uptime allows roughly 8.8 hours of downtime across a year - but physical equipment rarely justifies that language. A sensible approach for everyday business assets is to baseline first: log every stoppage for a quarter, calculate the actual figure, then set a target one notch better and aim at the biggest single cause. A preventive maintenance schedule for the worst offenders usually moves the number more than any tooling change.

Tracking uptime in practice

You cannot improve a number you never record, and downtime rarely records itself. The habit that works is small: every stoppage becomes a logged event against the asset - when it failed, why, and when it came back. In AMPthilly, issue reports and repair tickets are tied to the asset record with statuses and a permanent history, so the downtime story for any item is already written when you come to count it. Review the log monthly, and the assets that deserve a maintenance plan - or retirement - identify themselves.

Related terms

• Planned vs Unplanned Maintenance - the split that decides whether downtime surprises you
• Preventive Maintenance - scheduled work that trades small planned stops for big unplanned ones
• Equipment Servicing - the routine care that keeps uptime high
• Spare Parts Management - stocking the parts that turn long outages into short ones
• Service Level Agreement (SLA) - the contract form uptime commitments usually take