---
title: "Monitor your fleet on the Assets page"
description: "The Assets page is the live view of every monitored machine in your organization. A KPI row totals uptime, downtime, utilization and how many machines are producing right now; a daily utilization trend sits beside it; and each machine gets a card carrying a status ring, an uptime gauge against its goal, hourly production against goal, and cycle time. Five view modes, saved to your account, trade detail against fleet size, and filters, grouping and a shift window decide what the page counts."
category: "See what machines are doing"
source_url: "https://www.iotflows.com/docs/monitoring/assets-overview/"
---
# Monitor your fleet on the Assets page

See what every machine is doing right now, and which ones need attention.

An *asset* is one monitored machine: a catalog model, your own name and identifier for it, and the sensor that reports on it. The Assets page draws every asset in the organization at once, updates as sensors publish, and is the page most operators and supervisors leave open all shift.

**Prerequisites.** Signed in, with at least one machine reporting. Contact IoTFlows to tie your sensors to an asset, see [Get support](/docs/get-started/get-support/).

## Open the Assets page
Go to **Assets**. The page opens at `/assets?select=overview`.

Machines you are not granted access to never appear here. So do machines hidden from the **Edit Assets** list, which stay editable but are drawn out of the fleet view.

How the fleet is drawn depends on the view mode you last chose, see [Choose a view mode](#views). Every mode shows the same machines and the same window; they differ in how much of each machine they draw.

![The Assets page in list view. A filter toolbar runs across the top, a utilization trend chart with Zoom buttons sits beside four KPI tiles reading 71:15h Uptime, 68.2% Utilization, 33:14h Downtime and 9 of 14 Machines Producing, and four machine rows below each carry a photo, hourly production bars, current operation, cycle time, a utilization donut and a full-width green and red status bar running 8AM to 5PM.](/images/monitoring/mon-assets-01.webp)

*The fleet in list view, with the shift status bar under each machine. Green is running and red is down.*

## Read the fleet KPIs
Four tiles across the top total the whole fleet for the window you have selected.

| Tile | Shows |
|---|---|
| **Uptime** | Total hours every machine spent running, as `71:15h` |
| **Utilization** | Running time as a percentage of running plus down time, green when it meets the goal and red when it does not |
| **Downtime** | Total hours every machine spent down |
| **Machines Producing** | How many machines are running right now, over the total, as `9/14` |

Two controls sit in the corner of the **Utilization** tile. **Adjust OEE Goal** sets the organization-wide goal that colors the number, see [Set uptime goals](/docs/monitoring/oee-goals/). **Adjust Status Colors** sets the two thresholds described in [Read a machine card](#cards).

Beside the tiles, a chart plots utilization over time so you can see whether this shift is normal. **Zoom** regroups it: **Day** plots the last month a day at a time, **Week** the last three months a week at a time, **Month** all your history a month at a time, and **All** every point ungrouped. Zoom changes only this chart, not the machine timelines below it.

Every figure on this page is defined in [Metrics](/docs/monitoring/metrics-reference/).

![The four fleet KPI tiles: 33:18h Uptime in green, 67.6% Utilization in red, 15:59h Downtime in red, and 8 of 14 Machines Producing. Two small icons in the top right corner of the Utilization tile are outlined in blue.](/images/monitoring/mon-assets-02.webp)

*The two controls in the corner of the Utilization tile: Adjust OEE Goal on the left, Adjust Status Colors on the right.*

## Read a machine card
Each card carries the machine's photo inside a colored status ring, its name and identifier, uptime and downtime for the window, an **Uptime** gauge against that machine's goal, hourly production against the hourly goal, and cycle time or production rate colored against the cycle-time goal.

Under the identifier, a running machine shows a **Running** pill. A stopped machine shows **Last Op** and how long ago it was, in the current status color, so the card answers "how long" without being opened.

A *shift status bar* runs the width of the machine, from the start of the window to its end, colored for the state the machine was in at each moment. It is the one element that shows you the shape of the shift rather than its totals: six short red stretches and one long one are the same downtime total and completely different problems.

![A machine card for DMG DMU 65, identifier DMU-65. A green ring surrounds the machine photo, a green Running pill sits beside it, 05:02h uptime and 00:21h downtime are below, a 93% Uptime gauge and a 7 made count gauge sit at the right, and a green shift status bar runs 8am to 5pm along the bottom.](/images/monitoring/mon-assets-03.webp)

*A running machine's card: green ring, Running pill, Uptime against goal, parts made, and the shift status bar.*

A sensor reports a machine as running or down. There is no third state. What the colors add is how long it has been down.

### Status colors
| Color | Means |
|---|---|
| Green | Running |
| Orange | Down past the first threshold, one minute by default |
| Red | Down past the second threshold, five minutes by default |
| Dark red | Down, and the stop has been classified |
| Gray | No data from the sensor for that stretch |

Gray is absence of data, not downtime. A bar striped with gray through a shift is a connectivity problem, not a machine that keeps stopping, and the card still reads stopped because it carries the last state the cloud recorded. See [Troubleshoot a device that is offline](/docs/hardware/troubleshoot-offline-device/).

Both thresholds are organization-wide, and you set them in **Adjust Status Colors**. See [Status colors](/docs/monitoring/status-colors/). A classified stop skips them: it is drawn dark red from the moment it is classified, rather than working through orange first.

Dark red is only the default. Each downtime category can carry a color of its own, picked from a palette under **Color** when you add or edit the category. Reports and Pareto charts draw that category in its color, see [Manage downtime categories](/docs/monitoring/downtime-categories/).

![A machine card for Doosan 2600, identifier TXV-2600. A red ring surrounds the machine photo and a red pill reads Last Op: 11 minutes ago. Uptime is 00:42h and downtime 04:52h, the Uptime gauge reads 13%, and the shift status bar along the bottom is almost entirely red.](/images/monitoring/mon-assets-04.webp)

*A machine stopped eleven minutes, well past the five-minute red threshold.*

Click any card to open that machine, see [Inspect a single machine](/docs/monitoring/asset-detail/).

## Choose a view mode
Five icons at the right of the toolbar switch how the fleet is drawn.

| Mode | Shows | Best for |
|---|---|---|
| Card | Photo, status, uptime gauge, hourly production, cycle time | The default, up to roughly 20 machines |
| Large card | The same, at a size readable across a room | A wallboard or a supervisor's second monitor |
| Large uptime card | Uptime and goal given the whole card, with first pass yield where it is enabled | Watching goal attainment rather than activity |
| Cycle count | Production counts and cycle time, other elements dropped | Count-driven work, where the number is the point |
| List | One dense row per machine | Large fleets, and scanning for anything stopped |

**Choose the list view above roughly 20 machines.** Card view stops being scannable at the point where you have to scroll to see the whole fleet.

Your choice is saved to your IoTFlows account, not to the browser, so it follows you to any machine you sign in on. A toast reading "View settings changed" confirms the save. On a phone, only Card and Cycle count are offered, with List added on a tablet.

![The five-icon view switcher from the Assets toolbar, each icon labeled by an arrow: Card, Large Card, Large Uptime Card, Cycle Count and List, left to right.](/images/monitoring/mon-assets-05.webp)

*The five view modes. Your choice is saved to your account, not the browser.*

![The Assets page in card view: twenty machine cards in a four-wide grid, split under the department headings Production, Sheetmetal and UliProd. Each card carries a status ring, an Uptime percentage, an hourly production chart and a status bar, and the rings are a mix of green for running and red for stopped.](/images/monitoring/mon-assets-06.webp)

*Card view at twenty machines, grouped by department. This is about as much fleet as fits before you start scrolling.*

## Filter the fleet
**Department** and **Tag** narrow the page to part of the fleet. A *tag* is a label you attach to machines yourself, for a set that crosses departments, such as `CNC`. **Machine type** filters by catalog model, and is offered only in the expanded view, which the arrows icon opens.

Every filter is held in the URL, so a filtered page is a link you can send. **Reset filters** clears them all.

![The Assets filter bar in expanded view, carrying six chips: Department with a count of 4, Machine type, Tag with a count of 1, Group by Department, Sort by Name A to Z, and Shift Day Shift. Each applied chip has a cross for clearing it.](/images/monitoring/mon-assets-07.webp)

*The filter bar in expanded view. Machine type appears only here, and a chip carries the number of values you picked.*

## Group and sort
**Group by** splits the page under headings: **Department**, **Status** or **Machine type**. **Sort by** orders the machines within each group: name A to Z, name Z to A, department, or machine type.

Group by **Department** for everyday use: it matches how most plants are organized. Group by **Status** when you are working a shift and want everything stopped collected at the top. Leaving **Group by** unset draws the fleet as one flat run.

![The Assets page in list view, with machine rows collected under the department headings Machining and Production. Each row carries a status ring, hourly production bars, the current operation, cycle time, a utilization donut, and a full-width status bar.](/images/monitoring/mon-assets-08.webp)

*Grouping by department puts each area under its own heading.*

## Choose the window
**Shift** decides what every number on the page counts. Leaving it alone tracks the current shift live. You can also pick a named shift, **All Day**, or **Custom Time** with your own start and end in 30-minute increments, and set the date to yesterday or any past day.

The page refreshes itself every minute and redraws a card as soon as its sensor publishes. **Selecting a shift or a date stops the refresh**, because the window is now historical and a refresh would have nothing to add. Clear the shift filter to go live again.

A shift that crosses midnight is shown whole here. Pick Friday's 10 PM to 6 AM shift and the page counts all eight hours, with no break at midnight. Reports divide the same shift at midnight unless **Shift islands** is on, which is why this page and a report can disagree about one night, see [Where the overnight hours land](/docs/admin/shifts-and-timezone/#overnight-hours).

Shifts themselves are defined once for the organization, see [Shifts and time zone](/docs/admin/shifts-and-timezone/).

## When a machine is missing
Work down this list before suspecting the data.

1. Clear the filters. A department or tag filter is the usual answer.
2. Check that the machine is not hidden in **Edit Assets**.
3. Check your machine access. A grant you do not have removes the machine from the page entirely, see [Machine access](/docs/admin/machine-access/).
4. If the machine is on the page but gray, the sensor is not reporting. See [Troubleshoot a device that is offline](/docs/hardware/troubleshoot-offline-device/).

You do not need to add anything here to fix a missing machine. **Add asset** provisions a new machine, and that is a different task, see [Add a machine](/docs/monitoring/add-an-asset/).

## See also
- [Inspect a single machine](/docs/monitoring/asset-detail/)
- [Analyze downtime with Pareto and trend charts](/docs/monitoring/downtimes/)
- [Status colors](/docs/monitoring/status-colors/)
- [Metrics](/docs/monitoring/metrics-reference/)
- [Display a wallboard on a TV](/docs/monitoring/wallboards/)