---
title: Configuring an OPC-DA collector
slug: how-tos/a9Y--configuring
docTags: cUV_Sa6jBAIeXJcsVeSZ9,GOo15ntkoXThxPf_Z8vVm
createdAt: 2025-09-09T08:21:41.649Z
---

The **OPC-DA collector** in Factry Historian allows you to connect to an OPC-DA server and collect process values. Once configured, the data is historized and made available for further processing in Factry Historian, and for trending, reporting, and analysis.

## Prerequisites

- Permissions in Factry Historian to *manage* collectors. See [Privileges](docId\:K2NnYEcUxqQsiuCLmpfKH).
- An installed OPC-DA collector. If you have not done so already, first [install the collector](docId\:Iv4_SD56TdxcqKRKCj4kv).
- A working OPC-DA connection. If you are running into issues or setting this up for the first time, follow our guide to [test an OPC-DA connection](docId\:v3uERmlrQ4s9UxJ3XD-91).
- A configured [time-series database](docId\:F8UdoT0apxmjws-t-GcPV) to write the collected data to.

## Configure the collector

After installing the collector, you should be able to see that the collector is in an <font color="#46abdd">**initial state**</font> and is actively running. This means that the collector has established a connection to Factry Historian and is awaiting further configuration.

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/051RfS7T-VeZUyoZWd-kL-20250918-143148.png)

To configure the collector, select it from the Collectors overview in Factry Historian and click the **Edit** button. Configure the following fields:

### ProgID

This is the **programmatic identifier of the OPC-DA server** to connect to.

The ProgID must exactly match the one exposed by your OPC-DA server. If you are unsure which one to use, check the server’s ID in your OPC-DA server configuration or discovery tool. For example:

- `Graybox.Simulator.1`
- `Matrikon.OPC.Simulation.1`

:::hint{type="warning"}
If you’re having trouble connecting to the OPC-DA endpoint, see this page:[Testing an OPC-DA connection](docId\:v3uERmlrQ4s9UxJ3XD-91)
:::

### Nodes

This is a comma-separated list of the **nodes** of the OPC-DA server. For single-node servers, the default value of localhost should suffice. For setups involving multiple servers with the same ProgID, this setting is used to specify which node or nodes to connect to.

### CollectionSource

The collection source controls where data is read from

- Cache: fast read, returns data already stored on the OPC-DA Server
- Device: slower read, fetches the most up-to-date values from the underlying automation devices

### Example

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/AuQeeLYYggpAd7eBkyHR8-20250918-143148.png)

Then, click **Save**.

### Expected outcome

After you have configured the collector, a green Start button will appear in the top right corner of the collector page.

1. Click **Start** to launch the collector.

If the connection is successful, you should observe the collector status change to <font color="#15803D">**Collecting**</font>.

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/2-o5o60J4UkQMR505FWWp-20250918-143148.png)

## Adding measurements

Follow the guide on [Adding measurements to an OPC-DA collector](docId\:gP6_uW0fIjgfgM6tbuxve).

## Best practices

### Timestamps

Make sure all clocks (collector, server, devices) are synchronized, for example using NTP.