> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/suites/energy-and-sustainability-intelligence/energy-anomaly-detection/anomaly-center.md). # Anomaly Center ### Overview In *Anomaly Center*, detected anomalies are displayed in a hierarchical list under [*Alert Center*](/collection/platform/alert-center.md).\ Here, you can: * review anomaly values * set the anomaly status * add comments * filter the displayed anomalies * sort and customize the table * open the anomaly statistics dashboard * open the detail page of an anomaly Navigate to: [*Alert Center*](/collection/platform/alert-center.md) **\[1]** -> *Anomaly Center* **\[2]**.\ ▷ The *Anomaly Center* opens.

### Elements of *Anomaly Center*

Marker	Element	Description
[A]	Select anomalies	Select one or more anomalies. Selected anomalies can then be updated.
[B]	Set status	Opens the dialog for setting the validity of the selected anomaly or anomalies.
[C]	Add comment	Opens the dialog for adding a comment to the selected anomaly or anomalies.
[D]	Anomaly hierarchy	Displays anomalies in a hierarchical structure. This hierarchy can follow the asset hierarchy and the timeframe hierarchy.
[E]	Confirmed	Shows or hides anomalies with the status Confirmed.
[F]	False positive	Shows or hides anomalies marked as false.
[G]	Not set	Shows or hides anomalies whose status has not yet been set.
[H]	Sortable columns	Many columns can be used to sort the anomaly list. Click the column header to sort by that column.
[I]	Columns	Opens a sidebar where you can define which columns are displayed and in which order.
[J]	Search	Opens a search sidebar for filtering the anomaly list.
[K]	Anomalies Statistics Dashboard	Opens the anomaly statistics dashboard.
[L]	Open detail page	Opens the detail page of the selected anomaly.

### Columns in the anomaly list

Column	Description
Source	The asset from which the anomaly originates.
Type	The main asset type creating the anomaly. For example, if the type is related to lighting, the anomaly was likely caused by the lighting system.
Severity	The severity of the anomaly impact. High means the impact is at least 100 times the configured activation threshold. Medium means the impact is at least 10 times the configured activation threshold. Low means the impact is below 10 times the configured activation threshold.
Financial impact	A conservative estimated financial impact based on the forecast model and its one-sigma bounds.
Validity	The user-defined status of the anomaly.
Tags	The tags assigned to the asset.
Timeframe	The timeframe in which the anomaly was detected.
Predicted	The value predicted by the model.
Actual	The measured value.
Deviation	The difference between the predicted and actual value.
Started	The time at which the anomaly started.
Ended	The time at which the anomaly ended.
Status set by	The user who last changed the anomaly status.
Status set at	The time at which the anomaly status was last updated.
ID	The anomaly ID.
Site	The site assigned to the anomaly.

### Understand the anomaly hierarchy The anomaly list is hierarchical in two ways: * **Asset hierarchy**\ A higher-level anomaly, for example at building level, can contain lower-level anomalies such as floor-level anomalies or device-level anomalies. * **Timeframe hierarchy**\ A higher-level anomaly for a longer timeframe, for example **1 d**, can contain related anomalies for shorter timeframes such as **4 h**, **1 h**, or **15 min**. ### Set the anomaly status 1. Select one or more anomalies using **\[A]**. 2. Click on **Set status** **\[B]**.\ ▷ The dialog **Set status** opens. 3. Select the desired status: * **Confirmed** * **False** 4. If required, enter a comment. 5. Click on **Update status**. ◈ This feedback helps the model learn over time.\ ◈ Anomalies marked as false have a lower probability of being alerted again if a similar event occurs. ### Add a comment 1. Select one or more anomalies using **\[A]**. 2. Click on **Add comment** **\[C]**. 3. Enter the comment. 4. Save the comment. ### Configure displayed columns 1. Click on **Columns** **\[I]**.\ ▷ The sidebar **Displayed Columns** opens. 2. Enable or disable the columns you want to show. 3. If required, change the order of the columns. 4. Click on **Save** to apply the changes. **⇄ OR** 5. Click on **Reset** to discard the changes. ### Search anomalies 1. Click on **Search** **\[J]**.\ ▷ The sidebar **Search** opens. 2. Define the required search criteria. 3. Click on **Apply**.\ ▷ The list is filtered according to your search criteria. Possible search criteria include: * keyword * Global Asset Identifier (GAI) * asset type * type * site * time range * priority * tags ### Open further views 1. Click on **Anomalies Statistics Dashboard** **\[K]** to open the anomaly statistics dashboard. 2. Click on **\[L]** in a row to open the detail page of an anomaly. ### Notes * The anomaly list can be filtered by status using **\[E]**, **\[F]**, and **\[G]**. * Many columns can be sorted directly from the table header. * The displayed columns can be customized individually. * Status feedback provided through **Confirmed** and **False** helps improve future anomaly evaluation. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.buildings.ability.abb/collection/suites/energy-and-sustainability-intelligence/energy-anomaly-detection/anomaly-center.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.