> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/using-the-platform/devices-overview.md). # Devices overview The **Overview** tab of the Devices screen summarizes the devices in your selected group and the groups beneath it: how many there are, how recently each has checked in, what share of them is in use each day, and which models and software versions they run. To reach it, select **Devices** in the sidebar; the **Overview** tab is shown when the screen opens, and the **Inventory** tab beside it lists the devices one by one. ## Why this screen matters A device that has stopped checking in is switched off, lost, or unable to reach the network. The **Overview** tab answers three questions for the selected group: how many devices have gone quiet, and for how long ([Device Status](#device-status)); how much of the fleet is actually used on a working day ([In-Use](#in-use)); and whether every device is on the same software ([Software Versions](#software-versions)). The tab has no filters or date selectors, and none of its charts respond to clicks. To list the devices behind any check-in band, model bar or software row, open the [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab and use its **Last Seen**, **Model** or **Software** filter. ## Before you start The **Overview** tab counts every device in the selected group, and every group beneath it, that has [completed enrollment](/amie-advanced/metrics-reference/managed-devices.md) with AMIE — whether or not it has a license, and whether or not it has ever checked in. A device checks in each time it sends AMIE a report; AMIE keeps the time of the most recent one, and every check-in figure on the tab is counted from it. On a [Space](/amie-advanced/introduction/how-your-space-is-organized.md) with nothing enrolled yet, every figure reads **0**. The tab follows the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header: change the group and every figure reloads for that group and its sub-groups. ## Screen layout ![The Overview tab: check-in activity, daily in-use share, models and software versions.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-c3076a3e8aada79812afd267d74c2652f88acc50%2Fdevices-overview.png?alt=media) The heading **Devices** sits above two tabs, **Overview** and **Inventory**. Below them, a count of devices managed, then three charts and a table in two rows. ### Devices managed The count reads, for example, **30 Devices managed**: the number of devices in the selected group, and every group beneath it, that have completed enrollment with AMIE. A device counts from the moment enrollment completes and keeps counting whether or not it holds a license, and whether or not it has ever checked in. It is the same count as [Managed Devices](/amie-advanced/metrics-reference/managed-devices.md) on the [Dashboard](/amie-advanced/using-the-platform/dashboard.md) for the same group. To the right, **View all** opens the **Inventory** tab with no search or filter applied. {% hint style="warning" %} Review: the console counts every enrolled device, licensed or not. The product specification is that a managed device is one that has enrolled and holds a license. \[REVIEW-devices-overview-1] {% endhint %} **0 Devices managed** means no device in the selected group or any group beneath it has completed enrollment. ### Device Status **Device Status** is a donut chart, with a legend headed **Last Check-In**, that places every device counted in [Devices managed](#devices-managed) in one band by how long ago it last checked in. Every device is in exactly one band, so the five counts add up to **Devices managed**. The donut fills clockwise from the top in legend order, each band's arc in proportion to its count. | Band | Color | Last check-in | | -------------- | ------ | --------------------------------------- | | **Today** | Green | within the last 24 hours | | **1-7 days** | Blue | more than 24 hours and up to 7 days ago | | **8-14 days** | Amber | more than 7 days and up to 14 days ago | | **15-31 days** | Orange | more than 14 days and up to 31 days ago | | **>31 days** | Red | more than 31 days ago — or never | The band names are approximate: the boundaries fall at exactly 24 hours, 7, 14 and 31 days counted back from the moment the screen loaded — a [rolling age](/amie-advanced/metrics-reference/time-and-time-zones.md) — so a device last seen 7 days and 6 hours ago sits in **8-14 days**. A device that enrolled but has never reported sits in **>31 days**, however new it is. The exact shades vary with the light or dark appearance chosen on your profile, so read the legend rather than the shade. With no devices managed the donut is a single gray ring and every band reads **0**. ### In-Use **In-Use** is a bar chart with one bar per day for the last seven [calendar days](/amie-advanced/metrics-reference/time-and-time-zones.md) including today. Each bar is filled from the bottom with **Used** (blue) and topped up to 100% with **Unused** (gray). The vertical axis is labeled **In-Use %** and runs from 0% to 100%; the horizontal axis is labeled **Date**, with each bar labeled by its month and day. **Used** is the share of the devices counted in [Devices managed](#devices-managed) that were in use at some point during that day. A device counts as used on a day if, in at least one of that day's 24 hours, its reports to AMIE flagged it as being in use — even briefly; a device used for five minutes and one used all day count the same. Devices that have never reported cannot appear in **Used** but are in the total, so they pull the share down. **Unused** is 100% minus **Used**. {% hint style="warning" %} TODO: what the handset counts as being in use when it reports — handled, unlocked, on a call, or off its charger. {% endhint %} Days are cut at midnight in your browser's time zone, and today's bar covers only the part of today that has passed, so it can read lower than the completed days. In a week that includes a daylight-saving change, the days before the change begin and end an hour off midnight. Hover over a bar to read its percentage rounded to a whole number — for example **Sep 21 — Used: 43%**. The seven-day range is fixed; **In-Use** has no date selector. With no devices managed all seven bars are gray, and hovering over one reads, for example, **Sep 21 — Unused: 100%**. ### Device Models **Device Models** is a bar chart with one bar per model, tallest first. The heading carries the total in parentheses — for example **Device Models (30 devices)**. Above each bar is the number of devices of that model; beneath each bar is the model name and, under that, the model's share of [Devices managed](#devices-managed) as a whole-number percentage. The vertical axis is labeled **Devices** and the horizontal axis **Model**. Model names are shown without the "Versity" prefix — **9740**, **9540** and so on. A device for which no model is recorded yet appears in a bar labeled **Pending**. Hover over a bar to read the model and its count. The bars do not respond to clicks; to list the devices of one model, use the **Model** filter on the [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab. With no devices managed the heading reads **Device Models (0 devices)** and the chart reads **No devices to display.** ### Software Versions **Software Versions** is a table with two columns, **Version** and **Devices**: each Spectralink software version — the second line of the **Software** column on the Inventory tab, not the **Android** version — running on at least one device counted in [Devices managed](#devices-managed), and how many devices run it, from most devices to fewest. A device that has not reported its software version is counted in a row labeled **Unknown**. The rows do not respond to clicks; to list the devices on one version, use the **Software** filter on the [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab. With no devices managed the table reads **No devices to display.** ## Controls | Control | What it does | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Overview** / **Inventory** tabs | Switch between this summary and the device list, described on [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md). Each is its own page, so the browser's Back button steps back through the tabs you have visited | | **View all** | Opens the **Inventory** tab with no search or filter applied | The **Overview** tab has no filters or date selectors of its own. Nothing on it refreshes by itself; reload the page to recalculate. ## Icons and indicators | Icon or indicator | Meaning | When it appears | | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------- | | Handset icon beside the **Devices managed** count | Decoration. Hovering or clicking does nothing | Always | | Arrow after **View all** | Part of the link to the **Inventory** tab | Always | | **?** beside **Device Status**, **In-Use**, **Device Models** and **Software Versions** | Hover over it, or reach it with the Tab key, to show a short explanation of that chart or table | Always | | Colored dot in the **Last Check-In** legend | The band's color on the donut | Every legend row | | Blue and gray squares beneath the **In-Use** chart | Key to the bars: blue is **Used**, gray is **Unused** | Whenever the chart has loaded | | Dash (**—**) in place of the **Devices managed** count or the **Device Models** total | The figure has not loaded yet | While loading | | Spinning icon in a chart | That chart has not loaded yet. **In-Use** loads separately from **Device Status**, **Device Models** and **Software Versions** and may appear before or after them | While loading | ## What to look for * Anything in **15-31 days** or **>31 days**. A device quiet for two weeks or more is switched off, lost, or unable to reach the network; a brand-new device that has never reported sits in **>31 days** too. On the [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab, set the **Last Seen** filter to the same band to list them; its **Location** column shows the access point each was last connected through. The chart's bands and the filter's bands are both counted back from the moment each screen loaded, so filter soon after reading the chart. * **Used** well below 100% on every completed day. More devices are deployed than the selected group needs, or some are sitting in chargers. Compare groups with the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) and consider moving devices to busier areas. * **Used** low on one day only. Check whether it was a weekend or holiday before reading anything into it; today's bar is always a part-day. * More than one row under **Software Versions**. Not every device is on the same software version. Use the **Software** filter on the **Inventory** tab to list the devices on each older version. * A **Pending** bar under **Device Models** or an **Unknown** row under **Software Versions**. These devices have enrolled but have not yet reported a model or software version. Set the **Model** filter on the **Inventory** tab to **Pending**, or the **Software** filter to **Unknown**, to see which they are. * Figures that disagree with the [Dashboard](/amie-advanced/using-the-platform/dashboard.md). Check that the same group is selected; **Devices managed** and **Managed Devices** are the same count for the same group. * Model percentages that do not total 100%. They are whole numbers, and a model with a single device in a large fleet can read **0%**; the counts above the bars are exact. * **Used** figures that differ from a colleague's. **In-Use** is cut at midnight in each person's browser time zone; the **Last Check-In** bands are not affected by time zone. ## Metrics on this screen * [Managed Devices](/amie-advanced/metrics-reference/managed-devices.md) — the condition that makes a device count, shared with the Dashboard * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — rolling ages and calendar days ## Related * [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md) — the same devices as a searchable, filterable list * [Device details](/amie-advanced/using-the-platform/device-details.md) — everything recorded about one device * [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — the same check-in bands alongside batteries and calls * [The console](/amie-advanced/using-the-platform/the-console.md) — the group selector and the sidebar --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-advanced/using-the-platform/devices-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.