TTagHarbour

TagHarbour / Product specification

A clear path from
controller to consumer.

One managed acquisition layer. Consistent industrial data. A simpler connection between your production equipment and every application that needs it.

01 / Purpose

Stop rebuilding access to the same data.

TagHarbour sits between your industrial controllers and the applications that need their data. It brings acquisition into one shared layer, so dashboards, historians and business systems can use the same source without each managing a direct PLC connection.

Controller workloadShare acquired values across consumers to reduce duplicate polling. Match acquisition rates to the needs of your equipment and applications.
Integration effortManage acquisition and data mapping centrally, reducing repeated connection configuration across applications.
Future expansionConnect downstream consumers through a common interface. Expand the use of your plant data without repeating the same controller integration.

02 / Architecture

Acquire. Organize. Distribute.

ControllersTAGHARBOURAcquisition · Common data modelValues · Timestamps · QualityApplications
Managed acquisitionCentralized connection settings and configurable collection rates bring controller data acquisition into one managed place.
Consistent dataA common representation of values, timestamps and quality gives consuming applications the context they need to interpret plant data.
Shared deliveryApplications consume data through TagHarbour's outward interfaces rather than establishing their own direct polling loops.
Your PLC controls the machine. TagHarbour handles the data consumers.

03 / Connectivity

Built around a mixed industrial world.

Bring controller data into a common layer and deliver it through familiar industrial interfaces. Simplify the connection between equipment on the plant floor and applications across the business.

One layer. Many uses.

SCADAHistoriansMESOEEDashboardsAnalytics & AI
OPC UAStructured access to industrial values and their context for connected applications.
MQTTPublish/subscribe messaging for distributing plant data to downstream systems.
Application integrationA shared source for monitoring, production intelligence, reporting and analysis.

Build your integration around the controller models, protocols and application interfaces used in your plant.

04 / Operation

Know what your data is doing.

Make data freshness, connection health and collection requirements part of one coherent data strategy. Give your applications useful context alongside every value.

Data freshnessExpose acquisition timestamps and quality so applications can assess whether values are current.
Connection visibilityProvide communication status and diagnostics to help identify source connection problems.
Access and networkingPosition the shared data layer within your plant network and align application access with your security policies.
Capacity and latencySize acquisition around your tag counts, update rates and consuming applications. Collect data at the pace your use case requires.
Deployment formatPlan the shared acquisition layer alongside your plant infrastructure, with a clear route from controllers to consuming systems.

05 / Application fit

A good fit starts with your plant.

Consider TagHarbour when

Several systems need the same PLC data.

New applications keep creating new controller integrations.

You want a common data access layer across mixed equipment.

Shape your integration

Controller models, firmware and available protocols.

Required tags, update rates and data consumers.

Network, security and uptime requirements.

Keep the tools your teams rely on. Give them a simpler, shared route to the data they need.

06 / Move forward

Your next application.
Already connected to the bigger picture.

A new historian. Better production reporting. The first analytics project. Whatever comes next, start with a shared data foundation instead of another set of direct PLC connections.

Connect once. Share consistently. Put your industrial data to work across the business.

Explore the TagHarbour advantage