> 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/batteries-overview.md).

# Batteries overview

The **Overview** tab of the Batteries screen is the health check for every battery in the groups you can see: how many there are, how many are worn out, how many have stopped reporting, and which apps drain them. To reach it, select **Batteries** in the sidebar, then the **Overview** tab; the **Overview** and **Inventory** tabs sit under the heading **Battery Lifecycle Intelligence**.

## Why this screen matters

When phones die mid-shift, the battery is the first place to look, and a worn battery does not fix itself: it goes back into the charger and circulates until someone takes it out.

The **Overview** tab answers two questions: how many of my batteries are worn out, and how many have stopped reporting? Three figures answer them: [Replace Now](#replace-now), the **300+** bar in [Cycle Count](#cycle-count), and [Offline >7d](#offline-7d). [Battery Consumption by App](#battery-consumption-by-app) shows which apps consume the most battery across every battery the tab counts.

When **Replace Now** is above zero, open the [Inventory](/amie-advanced/using-the-platform/batteries-inventory.md) tab, sort by the **Health** column, and take the batteries in the [Replace (<65%)](#health-distribution) band out of circulation.

When **Offline >7d** climbs, use the **Inventory** tab's **Last Device** column (the handset the battery was last in) and **Location (Last AP)** column (the wireless access point that handset last connected to) to find where each battery that has stopped reporting was last seen.

## Before you start

The **Overview** tab counts every battery AMIE knows about in the groups you can see. A battery reports when the handset it is fitted in sends AMIE a reading for it; AMIE keeps the time of the most recent report.

The tab does not follow the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header. Whatever group is selected, the tab counts every group you can see, so two people with the same access but different groups selected see the same figures.

## Screen layout

![The Overview tab: battery totals, cycle counts, health bands, and consumption by app.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-803e877f2353eff5797100f08821853740a8629a%2Fbatteries.png?alt=media)

### Total Managed

**Total Managed** is the number of batteries AMIE knows about in the groups you can see. The text beneath the number reads **Batteries in fleet**. A battery stays in the count after it stops reporting: a battery swapped out and left in a drawer is still counted, and so is one whose handset has since been taken out of service.

**0** means AMIE knows of no battery in any group you can see.

### Offline >7d

**Offline >7d** is the number of batteries counted in [Total Managed](#total-managed) whose most recent report was 168 hours (7 days) or more before the screen loaded. The text beneath the number reads **Inactive batteries**. The time since the last report is counted back from the moment the screen loaded and does not depend on your time zone — a [rolling age](/amie-advanced/metrics-reference/time-and-time-zones.md).

A battery that reports again leaves the count. A battery that AMIE knows about but has no report time for is never in it.

**0** means every battery with a report time has reported within the last 7 days.

### Replace Now

**Replace Now** is the number of batteries in the **Replace (<65%)** band of [Health Distribution](#health-distribution) — batteries whose remaining capacity is under 65% of what they held when new. The text beneath the number reads **Health <65%**.

**0** means no battery with a capacity reading is under 65%. Batteries that have not yet reported a capacity reading are not counted, so **0** does not prove that every battery is healthy.

### Cycle Count

**Cycle Count** is a bar chart of how many complete charge-and-discharge cycles each battery has been through. Above each bar is the number of batteries in it; beneath each bar is its range and, under that, its share of [Total Managed](#total-managed) as a whole-number percentage.

| Bar         | Color      | Cycle count |
| ----------- | ---------- | ----------- |
| **<100**    | Light gray | 0 to 99     |
| **100-199** | Dark gray  | 100 to 199  |
| **200-299** | Orange     | 200 to 299  |
| **300+**    | Red        | 300 or more |

The tallest bar fills the chart's height and the others are drawn in proportion to it; a bar with no batteries is drawn as a thin line so its label stays visible. A battery with no recorded cycle count is left out of every bar, so the four counts can total less than **Total Managed**; when no battery has a cycle count, all four bars read **0** and **0%**.

### Health Distribution

**Health Distribution** groups batteries by remaining capacity: how much charge a battery can now hold when full, as a percentage of what it held when new. Remaining capacity is not the battery's current charge — a fully charged battery can still be in the **Replace (<65%)** band. The percentage can move slightly up or down between reports. See [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md).

The chart is a donut with a legend listing three bands and the number of batteries in each. The donut fills clockwise from the top in legend order, each band's arc in proportion to its count.

| 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%                  |

A battery with no capacity reading is left out of all three bands, so the three counts can total less than **Total Managed**. When no battery has a capacity reading, the donut is a single gray ring and every band reads **0**.

### Battery Consumption by App

**Battery Consumption by App** is a bar chart of the apps that consumed the most battery, across every battery counted in [Total Managed](#total-managed), during the selected time range. There is one bar per app, tallest first, up to 15 apps. Above each bar is its value to one decimal place; beneath it is the app's package name — the technical identifier such as `com.example.app`, not the name shown on the handset — printed at an angle.

The value is the app's total reported consumption over the range.

{% hint style="warning" %}
TODO: the unit of the consumption figure — whether it is a percentage of a full charge, milliamp hours, or another measure — is not stated on the screen. Confirm the unit and how a reader should compare two bars.
{% endhint %}

The **Time Range** list to the right of the **Battery Consumption by App** heading sets the range. **Last 7 Days** is selected when the screen loads. Every range is cut at midnight in your browser's time zone — [calendar days](/amie-advanced/metrics-reference/time-and-time-zones.md) — so a colleague in another time zone can see different totals for the same range.

| Time Range                                           | Covers                                    |
| ---------------------------------------------------- | ----------------------------------------- |
| **Today**                                            | From midnight this morning to now         |
| **Yesterday**                                        | The previous complete day                 |
| **Last 7 Days**                                      | Today and the 6 days before it            |
| **Last 30 Days**, **Last 60 Days**, **Last 90 Days** | Today and the 29, 59 or 89 days before it |

When no app consumption was reported in the range, the chart area reads **No batteries to display.** — the same text it shows when AMIE knows of no battery at all.

## Controls

| Control                           | What it does                                                                                                                                                                                                                                                                  |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Overview** / **Inventory** tabs | Switch between this summary and the list of individual batteries, described on [Batteries inventory](/amie-advanced/using-the-platform/batteries-inventory.md)                                                                                                                |
| **Time Range**                    | Changes the period covered by [Battery Consumption by App](#battery-consumption-by-app) only. **Total Managed**, **Offline >7d**, **Replace Now**, **Cycle Count** and **Health Distribution** have no date range: they show the figures as they stood when the screen loaded |

Nothing on the **Overview** tab refreshes by itself. Reload the page to recalculate.

## Icons and indicators

| Icon or indicator                                 | Meaning                                                           | When it appears  |
| ------------------------------------------------- | ----------------------------------------------------------------- | ---------------- |
| Battery icon beside **Total Managed**             | Decoration. Hovering or clicking does nothing                     | Always           |
| Clock icon beside **Offline >7d**                 | Decoration. Hovering or clicking does nothing                     | Always           |
| Crossed-circle icon beside **Replace Now**        | Decoration. Hovering or clicking does nothing                     | Always           |
| **?** beside each of the six headings             | Hover over it to show a short explanation of that figure or chart | Always           |
| Colored dot in the **Health Distribution** legend | The band's color on the donut                                     | Every legend row |
| Dash (**—**) in place of a number                 | The figure has not loaded yet                                     | While loading    |

## What to look for

* **Replace Now** above zero. Every battery it counts holds under 65% of what it held when new and may not last a full shift. Open the **Inventory** tab, click the **Health** column heading until the lowest percentages are at the top, and use **Last Device** and **Location (Last AP)** to find each one.
* A **300+** count higher than the last time you looked. The batteries in that bar are the most worn by use and the likeliest to lose capacity next. Sort the **Inventory** tab by **Cycles** to see which they are and what their **Health** reads.
* **Offline >7d** climbing from week to week while **Total Managed** does not. The usual causes are spares left in a drawer and batteries that left with a lost handset. Sort the **Inventory** tab by **Last Seen**, oldest first, and note the **Last Device** of each battery that has not reported for a week. Then open the **>31 days** band on [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) and look for those handsets: the missing battery is usually still in a handset that has not checked in for a month.
* The same app at the top of **Battery Consumption by App** whichever **Time Range** you choose. That app is a steady drain, not a one-off. Open [Top App Consumption](/amie-advanced/using-the-platform/device-details/device-top-app-consumption.md) on two or three handsets: if the app is near the top on each, the drain is fleet-wide; if only on one, the problem is that handset.
* **Cycle Count** or **Health Distribution** totals below **Total Managed**. The difference is batteries with no cycle count or capacity reading yet — see **Cycle Count** and **Health Distribution** above.
* Figures that disagree with the [Dashboard](/amie-advanced/using-the-platform/dashboard.md). The **Dashboard** follows the group selector; the **Overview** tab always counts every group you can see. Select the top-level group in the group selector on the **Dashboard** to compare like with like.
* **Today** totals that differ from a colleague's. **Time Range** is cut at midnight in each person's browser time zone; **Offline >7d** is not affected by time zone.
* **Cycle Count** percentages that do not total 100%. They are whole numbers; the counts above the bars are exact.

## Metrics on this screen

* [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md) — the health bands
* [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — which clock each figure on this screen uses

## Related

* [Batteries inventory](/amie-advanced/using-the-platform/batteries-inventory.md) — the batteries behind these figures, one per row
* [Battery details](/amie-advanced/using-the-platform/battery-details.md) — one battery's health, charge and history
* [Alerts](/amie-advanced/using-the-platform/alerts.md) — the battery alerts AMIE raises


---

# 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/batteries-overview.md?ask=<question>&goal=<user_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.
