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

Implemented interfaces.
Explicit scope.

The current development build supports controller reads and permitted writes through the following drivers.

Modbus TCP / UDPCoils and registers, configurable types and byte order. Zero-based addressing. UDP uses MBAP framing.
Siemens S7Classic S7 absolute addressing for DB, memory and I/O areas; configurable rack and slot. Read/write support with retained protocol tests. This is not a claim of universal Siemens CPU or S7plus compatibility.
Allen-Bradley EtherNet/IPLogix symbolic tags, controller/program tag browsing, scalar reads and permitted writes. Configure the controller route and tag symbol; hardware compatibility must be confirmed for the target controller.
OPC UA clientBrowse and import tags, configure certificate trust and authenticated access, read values and write enabled tags. Capture supported source metadata at startup.
OPC UA serverExpose shared values, quality, timestamps and an asset hierarchy. Stable tag NodeIds, encrypted connections and explicit certificate trust. Permitted writes route back to the source.
YFP NMEA 2000 UDPIn development. YFP binary multicast receiver and initial heading, position, course/speed, depth and apparent-wind decoding pass focused local tests. Discovery and live signal integration are not yet complete. Read-only; this is the YFP transport, not a generic NMEA gateway compatibility claim.
MQTT / SparkplugPlanned. Not available in the current build.

04 / Operation

Configure. Operate. Investigate.

Excel and browser configurationEdit devices, assets, tags, alarms and historian policies. Validate, save with a backup, then explicitly apply or restart when required.
Asset model and stable identityPermanent tag and asset IDs are independent of PLC addresses. Choose public names, display labels, units and equipment hierarchy. OPC UA blank fields inherit supported metadata; workbook values take precedence. Restart to refresh field-device metadata.
Dashboard and editorSeparate operator and engineering pages. Reusable SVG equipment libraries for water and marine applications, a visual component picker, configurable bindings, titles, geometry, colours and scales.
Operator commandsBoolean buttons and numeric writers use authenticated requests. Tags must explicitly permit writing. Types, configured bounds and command outcomes are checked; values are read back from the controller.
Alarm handlingHigh, low and Boolean conditions, hysteresis, delays, latching and acknowledgement. Individual alarm states can be bound as read-only signals. Equipment graphics show configured alarm states and lost connections.
Embedded historianSQLite storage, periodic or on-change recording, deadband, heartbeat, retention days and a maximum database size. Browser trends overlay multiple tags with independent left/right axes, time-range queries and CSV export.
DiagnosticsDevice and tag health, freshness, timestamps and quality; historian storage and buffering status. Detailed downstream-consumer and throughput instrumentation remains planned.

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 / Current build · 11 October 2026

Working software.
A clear route to V1.

The latest lift-station demonstration uses one OpenPLC program with simultaneous Modbus TCP, OPC UA and S7 interfaces, 44 signals per interface and three separately mapped screens. Cross-protocol numeric writes, Boolean commands and fault/reset behaviour have been verified.

Verified development evidence365 gateway regression checks passed, plus retained live cross-protocol checks. The new YFP multicast driver has separately passed 68 focused tests; it has not yet completed live network integration or the full updated regression run.
Still to completeMQTT delivery, the packaged installer, production capacity and soak testing, supported-hardware qualification, and release security and upgrade/recovery validation.
Commercial target$995 software-only per gateway installation, unlimited tags with no per-tag licensing. Customer-supplied PC or VM; an optional appliance is separate. This is the V1 target, not a claim that every planned feature is shipping today.
Explore the working demonstration