> 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/dashboard.md). # Dashboard The **Dashboard** is the one-screen summary of the fleet in your selected group: how many devices and batteries AMIE knows about, how recently they have reported, how healthy the batteries are, and how voice calls have been performing. It is the screen you land on when you sign in (rather than following a link to a particular screen), and you return to it by selecting **Dashboard** in the sidebar. ## Why this screen matters The **Dashboard** answers the questions an administrator asks first: is anything not checking in, are batteries wearing out, and did calls go badly yesterday? Nothing on it can be changed, and each of its eight figures has a screen that holds the detail behind it: the [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) behind [Managed Devices](#managed-devices) and [Device Status](#device-status), the [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md) behind the two battery figures, the **Licenses** tab under **Settings** behind [Available Licenses](#available-licenses), and [Performance](/amie-advanced/using-the-platform/performance.md) behind [the three call figures](#the-three-call-figures). Read it left to right, top to bottom, then open the screen behind the first figure that looks wrong. ## Before you start The **Dashboard** counts every device that has [completed enrollment](/amie-advanced/introduction/how-it-works.md) with AMIE in the selected group and the groups beneath it — whether or not it has reported yet — and every battery AMIE knows about in those groups. A device reports when it checks in with AMIE; a battery reports when the handset it is fitted in sends AMIE a reading for it. On a [Space](/amie-advanced/introduction/how-your-space-is-organized.md) with nothing enrolled yet, every figure reads **0**. The **Dashboard** 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 the groups beneath it. ## Screen layout ![Fleet totals, check-in and battery health distribution, and call trends, on one screen.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-8c6784006bac8d5d2f516b7d11b5a0d453778df6%2Fdashboard.png?alt=media) The heading **Dashboard** carries the subtitle **Fleet overview and system health**. Below it, three rows: three fleet totals, two distribution charts, and three call figures. ### Managed Devices **Managed Devices** is 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 has a license, and whether or not it has ever checked in. A device switched off in a drawer for a month is still a managed device, and so is one that enrolled and has yet to report. Devices that started but never completed enrollment are not counted. **Managed Devices** is the same count as **Devices managed** on the [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) for the same group. {% 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-dashboard-1] {% endhint %} The line beneath the number reads, for example, **33% checked in last 24h**: the share of those same devices that have reported within the [rolling 24 hours](/amie-advanced/metrics-reference/time-and-time-zones.md) ending when the screen loaded, rounded to a whole number. In a fleet of 30 with 10 heard from in the last 24 hours, it reads **33%**. {% hint style="warning" %} Review: the console shows this as a percentage. The product specification is a count of devices checked in. \[REVIEW-dashboard-2] {% endhint %} **0** means no device in the selected group and the groups beneath it has completed enrollment; the line beneath then reads **0% checked in last 24h**. ### Managed Batteries **Managed Batteries** is the number of batteries AMIE knows about in the selected group and the groups beneath it, whether or not each has been seen recently. A battery stays in the count after it stops reporting. The line beneath the number reads, for example, **41% checked in last 24h**: the share of those batteries that a handset has reported within the [rolling 24 hours](/amie-advanced/metrics-reference/time-and-time-zones.md) ending when the screen loaded, rounded to a whole number. AMIE matches batteries to a group differently from devices, so **Managed Batteries** can read **0** for a group whose **Managed Devices** looks normal — see [Which screens follow the selector](/amie-advanced/using-the-platform/the-console.md#which-screens-follow-the-selector). **0** means AMIE knows of no battery in the selected group and the groups beneath it; the line beneath then reads **0% checked in last 24h**. ### Available Licenses **Available Licenses** is how many more devices you can assign before your current licenses are used up: the total number of devices your licenses allow, minus the number of devices already assigned to them. A license counts only if it is current by AMIE's own calendar date, not your browser's — a [service date](/amie-advanced/metrics-reference/time-and-time-zones.md). Current means on or after its start date and on or before its expiry. At least one device from the selected group and the groups beneath it must already be assigned to it. Two consequences follow. A newly purchased license with nothing assigned to it yet does not appear here. And the devices subtracted are all devices assigned to those licenses, including devices in groups you cannot see, so the figure can be negative when more devices are assigned to a license than it allows. **0** means every license in use is full — or that no current license has a device from your selection assigned to it yet. ### Device Status **Device Status** is a donut chart, with a legend headed **Last Check-in**, that takes every device counted in [Managed Devices](#managed-devices) and places it in exactly one band by how long ago it last checked in. Because every device lands in one band, the five counts add up to **Managed Devices**. The donut fills clockwise from the top in the order the legend lists the bands, 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** | Orange | 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. **8-14 days** and **15-31 days** are two shades of orange, and which is the deeper depends on 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**. ### Battery Health Distribution **Battery Health Distribution** is a donut chart that places every battery counted in [Managed Batteries](#managed-batteries) that has reported its capacity into one of three bands by how much of its original capacity it still holds. | Band | Color | Remaining capacity | | -------------------- | ------ | -------------------------- | | **Good (≥80%)** | Green | 80% or more | | **Warning (65-79%)** | Orange | 65% or more, but under 80% | | **Replace (<65%)** | Red | under 65% | Remaining capacity is how much charge a battery can hold when full, as a percentage of what it held when new; it is not the battery's current charge. See [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md). A battery that has not yet reported a capacity reading is left out of all three bands, and the chart does not say how many were left out, so the three counts can total less than **Managed Batteries**. With nothing to plot the donut is a single gray ring and every band reads **0**. ### The three call figures **Call Performance**, **Call Volume** and **Call Minutes** sit across the bottom, each showing the same four things about a different measure. The four things do not cover the same period — see [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md). | What you see | What it is | Period | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | The large figure | The measure's value | The [rolling 24 hours](/amie-advanced/metrics-reference/time-and-time-zones.md) ending when the screen loaded, so today and part of yesterday | | The small figure labeled **Yest.** | The measure's value for yesterday | Yesterday: the most recent complete calendar day in your browser's time zone | | The percentage under **Yest.** | How much higher or lower yesterday's figure was than the day before's, as a percentage with up to one decimal place — **+12.5%**, **-3%**, **+0%**. Green when higher or unchanged, red when lower | Yesterday and the day before, in your browser's time zone | | The small line across the bottom | The measure's value on each day, with a shaded area beneath it | The last seven complete calendar days, ending yesterday. Today is not on the line | Beneath the line is each day's abbreviated weekday name; above it and below it to the left are the top and bottom of its scale, rounded outward to whole numbers. The line's last point is the **Yest.** figure, not the large one, and today's calls are in the large figure but not on the line. See [Trend sparklines](/amie-advanced/charts-reference/trend-sparklines.md) for how to read the line. The percentage under **Yest.** reads **+0%** when the day before yesterday had no calls, however large the jump, and when a decrease is too small to show at one decimal place. ### Call Performance **Call Performance** is the average voice quality across the calls in the period each figure covers — see [The three call figures](#the-three-call-figures) — as a score out of 100 shown with a percent sign — the large figure, the **Yest.** figure and the scale of the line all carry the sign. AMIE calculates each call's quality from measurements the handset reports during the call. See [Call Performance](/amie-advanced/metrics-reference/call-performance.md). **0%** means there were no calls in the period, not that quality was terrible — check **Call Volume** beside it. ### Call Volume **Call Volume** is the number of calls that ended in the period each figure covers — see [The three call figures](#the-three-call-figures). A call is counted when it ends, so a call spanning midnight belongs to the day it finished. **0** means no call ended in the period. ### Call Minutes **Call Minutes** is the total duration of the calls that ended in the period each figure covers — see [The three call figures](#the-three-call-figures) — in minutes to two decimal places. **0** means no call ended in the period. ## Controls The **Dashboard** has no controls of its own — no buttons, filters or date pickers. The one control that changes what it shows is the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header. Nothing on the **Dashboard** refreshes by itself; reload the page to recalculate. ## Icons and indicators | Icon or indicator | Meaning | When it appears | | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | Handset, battery and key icons at the top right of **Managed Devices**, **Managed Batteries** and **Available Licenses** | Decoration identifying the figure. Hovering or clicking does nothing | Always | | **?** beside each of the eight headings | Hover over it to show a short explanation of what that figure measures | Always | | Colored dot in a legend row | The band's color on the donut | Every legend row | | Green or red percentage under **Yest.** | Green: yesterday's figure was equal to or higher than the day before's. Red: lower | Whenever the figure has loaded | | The two small figures around a call figure's line | Above the line, the top of its scale; below and to the left, the bottom | Always; while loading they read **0** and **1** and the weekday names are blank | | Dash (**—**) in place of a figure | The figure has not loaded yet | While loading | ## What to look for * The **checked in last 24h** percentage under **Managed Devices** below 100%. The rest of the fleet has not reported in the last 24 hours. Read [Device Status](#device-status) to see how long they have been quiet, then set the **Last Seen** filter on the [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md) to the same band to list them. * Anything in the **>31 days** band. A device that has not checked in for a month is switched off, out of range, or lost; a brand-new device that has never reported sits here too. On the [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md), set the **Last Seen** filter to **>31 days** to list them with the access point each was last seen on. * Anything in **Replace (<65%)**. Each is a battery that may not last a shift. Open the **Inventory** tab on the **Batteries** screen — [Batteries inventory](/amie-advanced/using-the-platform/batteries-inventory.md) — and sort by **Health** to find them. * **Available Licenses** at **0** or below. At **0**, either every license in use is full or a new license has nothing assigned to it yet — see [Available Licenses](#available-licenses). Below **0**, more devices are assigned than your licenses allow. Licenses are managed under **Settings**, on the **Licenses** tab. * A red percentage under **Yest.** on **Call Performance**. Yesterday's call quality was worse than the day before; [Performance](/amie-advanced/using-the-platform/performance.md) shows which access points and handsets were responsible. * **Managed Batteries** or the three call figures at **0** while **Managed Devices** shows the group's handsets. If the group should have batteries, contact Spectralink support — see [Getting help](/amie-advanced/introduction/getting-help.md). * Figures that do not add up. [Battery Health Distribution](#battery-health-distribution) can total less than **Managed Batteries** — the difference is batteries with no capacity reading — and **+0%** under **Yest.** also appears when the day before yesterday had no calls. * Different totals from a colleague. Check the group selector first; then remember that **Yest.**, the percentage under it and the line are cut at midnight in each person's browser time zone, while the large figures and the check-in bands are not affected by time zone. ## Metrics on this screen * [Managed Devices](/amie-advanced/metrics-reference/managed-devices.md) * [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md) * [Call Performance](/amie-advanced/metrics-reference/call-performance.md) * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — the four kinds of time on this screen * [Trend sparklines](/amie-advanced/charts-reference/trend-sparklines.md) — how to read the small lines under the call figures ## Related * [The console](/amie-advanced/using-the-platform/the-console.md) — the group selector, the user menu and the sidebar * [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) — the same five check-in bands as a donut; the [Devices inventory](/amie-advanced/using-the-platform/devices-inventory.md) lists the devices in each band * [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md) — battery health, cycle counts and consumption by app * [Alerts](/amie-advanced/using-the-platform/alerts.md) — conditions AMIE has detected for you, including battery health alerts --- # 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/dashboard.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.