# Monitor

> Watch the plant live. See what needs attention, follow tag values over time, find where data stops and handle alarms.

Source: https://proxus.io/docs/monitor

**Monitor** is where you look when you want to know whether the plant is running and, if it is not, where and why.
These screens only read: nothing you do here changes how a machine is read, except acknowledging or closing an
alarm and saving your own trend views. In the hub, they are in the **Monitor** menu.

## The screens

| Screen | What it answers |
| --- | --- |
| **Operations Center** | Is anything wrong right now, where, and what should I do? One page for alarms, silent gateways, devices without data and the flow of data through the hub. |
| **Trend Workspace** | How did these values change? Tags of one or more devices on one time axis, with alarms, changes and machine state next to the line. |
| **Topology** | Where does the data come from and where does it stop? A map of sites, lines, devices, gateways and outbound targets, coloured by health. |
| **Alerts** | Which alarms are open, who took them and how were they closed? The list of every alarm that rules and pipelines raised. |
| **Copilot** | Can you explain what is going on? Ask in plain language; Copilot reads devices, gateways, alarms and health checks with your permissions. |

## How they work together

A typical shift starts in the **Operations Center**. A problem there leads to one of the other screens: an alarm
opens in **Alerts**, a device without data is found on the **Topology** map, and a value that looks wrong is
compared with yesterday in the **Trend Workspace**.

## Screens

## Common tasks