> For the complete documentation index, see [llms.txt](https://captic-2.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captic-2.gitbook.io/docs/overview/hands-on/required-preparation.md).

# Required preparation

What must be in place on your site before we can start the installation.

Before we can start the installation, three things must be ready on your site: **networking**, **LAN** and **power**. This page covers the basics that apply to every Captic system.

The exact requirements depend on your setup: how many cameras and IPCs you have, and which types of devices. We'll confirm the specific list for your project, including the number of IP addresses and the power requirements of each device.

{% hint style="warning" %}
All of the items below must be ready **before** we arrive. Missing networking or power is the most common reason an installation is delayed.
{% endhint %}

## Networking

For **each device that connects to your network**, provide us with:

* [ ] a **static IP address**
* [ ] the **netmask**
* [ ] the **gateway**
* [ ] the **DNS server** IP
* [ ] an **NTP server** for time synchronisation: your own time server, or access to `ntp.ubuntu.com` (UDP 123)

Cameras connected directly to the IPC usually don't need an address on your network. If you're unsure which devices need one, ask us.

Then:

* [ ] **Choose a connectivity tier** with your IT/OT team and set it up, for example the firewall rules or a proxy. See [Network Security](/docs/overview/good-to-know/security/security.md). For the strictest tiers, start early: they involve your network and cloud architects.

### Check the connection

Every device can check its own connectivity. Once a device is on your network, open the Product UI at `http://[serial-number].local:3000` and go to **Details > Networking**. The page automatically tests the connections the device needs and shows which ones pass and which fail.

![Network check in Details > Networking](https://482575286-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F22HCD2cZG8ud6cPRBzVQ%2Fuploads%2FWs2BFyQ9B5enOceNKSyl%2FScreenshot%202025-06-24%20at%2011.25.44.png?alt=media\&token=e2ac4a56-477f-4a44-b04a-0545e2ca9765)

A failed check almost always means a firewall rule is missing. Compare your setup with your tier in [Network Security](/docs/overview/good-to-know/security/security.md).

## Remote access

We use **Teleport** for secure remote access to your devices. It lets us support you, diagnose problems and apply updates without a site visit.

* [ ] **Allow Teleport** through your firewall. It's included in the firewall rules of tiers 1 to 3.
* [ ] **Using a different remote access tool?** If your company requires another solution, for example BeyondTrust or FortiClient, **tell us before delivery** so we can prepare the devices for it. See [tier 4: Without Teleport](/docs/overview/good-to-know/security/security.md#tier-4-without-teleport).

## LAN

* [ ] A working **Ethernet connection to your OT network** at the install location, for each device that connects to your network.

## Power

Power requirements depend on the hardware in your system. Check the datasheets on the [Hardware](/docs/overview/whats-in-the-box/hardware.md) page, or ask us for the requirements of your devices.

* [ ] A suitable **power supply** at the install location for each device that needs one.

{% hint style="info" %}
Cameras connected to the IPC are usually powered through it over PoE, so they don't need a separate supply.
{% endhint %}

{% hint style="info" %}
Questions about any of these? Email <support@captic.com> and we'll help your IT/OT team get ready.
{% endhint %}