# Equipment: overview and quick start

The agent answers questions about how equipment runs from live data: what a machine is doing now, what the temperature was overnight, how long a line stood idle, which alarms fired during a shift. The data is read by the gateway, a program on a server at the site. It connects to the equipment on the site network and sends the values to the cloud, where the agent reads them.

## How it works

| Link | Where it runs | What it does |
|---|---|---|
| Equipment | site network | PLCs, SCADA, OPC UA servers, MQTT brokers, CNC machines and IP cameras serve data over their own protocol |
| Gateway | a server at the site (Windows or Linux) | reads the connections assigned to it, buffers data on its disk and sends it over an outbound connection to 443 |
| Cloud | Samreshuuu | receives the data, keeps the history, watches task conditions |
| Agent | chat, tasks, messengers | answers questions and runs tasks on equipment events |

Everything is read only: there is no write to equipment, neither in the gateway nor for the agent. More for the security team: [gateway security](/help/equipment-security).

## What you can ask

<TryPrompt prompt="What are the machines on line 2 doing now: which are running, which are idle and why." />

- Current values: pressure, temperature, level, part count.
- History for a period: minimum, maximum and average per interval, and where there were gaps.
- Alarms: which are active now and which fired during the shift.
- Machine state: running, idle, stopped, setup, maintenance.
- A camera frame on request.

More examples and event tasks: [questions and tasks](/help/equipment-questions).

## What to prepare

- A server on the site network that can see the equipment: Windows 10 or Windows Server 2016 and later (x64), or Linux. Requirements: [installing the gateway](/help/equipment-gateway).
- Outbound access from that server to the data intake on 443, direct or through a proxy.
- Addresses and connection settings of the equipment: the OPC UA server address, the controller IP, the broker address, a login and password where they are needed.
- The right to manage integrations in the organization: only someone with it sees the Gateways tab.

## Quick start

**Enabled on request**
Equipment data is enabled for an organization on request. Until then there is no Gateways tab under Integrations. [Write to us](/help/contacts): we turn it on and hand over the gateway build.

### Add a site
Under **Integrations** open the **Gateways** tab and press **Add site**: a boiler house, a workshop, a building. The site's time zone sets days and shifts in the data. If the site is part of critical information infrastructure, mark it right away: what changes is described in the [critical infrastructure section](/help/equipment-security).

### Install and connect the gateway
Press **Connect a gateway**, choose the site, name the gateway and press **Get code**. Run the command shown on the site server where the gateway is installed. The code works once and for a limited time; the time left shows in the window. How to install the gateway on Windows and Linux: [installing the gateway](/help/equipment-gateway).

### Add an equipment connection
On the **Services** tab choose the protocol (OPC UA, Modbus, MQTT and others) and fill in the address and settings. Which protocols exist: [protocols](/help/equipment-protocols).

### Assign the connection a gateway
On the **Gateways** tab, in the **Equipment connections** group, choose a gateway for the connection. One gateway reads a connection. Once values arrive, the status changes to **Reading, tags: …**.

<TryPrompt prompt="Find the pressure tags at the boiler house and show their current values." />

If the status does not change or the connection says **Not reading**, see [statuses and what to do](/help/equipment-troubleshooting).