Platform

What happens to the data

Every value that reaches SyncTide — from a PLC, an MQTT broker, a datalogger file or a formula — lands in the same history. From there it is watched, analysed, reported and, when needed, corrected.

01 · Store

Every tag keeps its own history

Values from every source are written to one time-series history per tag. What gets written is decided per tag, so the history holds the changes rather than endless repeats.

What is written

  • Deadband per tag on Modbus, OPC UA and IEC 104: a value is stored once it moves more than the deadband from the last stored value, so a slow drift is still recorded. New in 1.14.7 — coming soon
  • Report-by-exception per equipment: a value that has not changed is not written again.
  • A heartbeat stores a value at least every so many seconds, so a flat signal never looks like missing data. New in 1.14.7 — coming soon
  • On OPC UA subscriptions the deadband is also sent to the server, so unchanged values never cross the link.

How it is kept

  • PostgreSQL 17 with TimescaleDB: the history is split into time chunks and closed chunks are compressed.
  • Every hour, the chunk size (from 1 hour to 7 days) and how soon a chunk is compressed are chosen from how much data really arrives. Small installations keep 7-day chunks; large ones compress within hours. New in 1.14.7 — coming soon
  • A file sent twice, or two polls that overlap, never store the same value twice.

Virtual tags

  • Tags computed from a formula over other tags, such as ${FT-101} + ${FT-102}, also across equipment.
  • Numbers and a short list of functions only — abs, min, max, round, sqrt, pow, log, exp, and bit / bits to read flags from a status word — evaluated in a sandbox.
SyncTide / Tag FT-101 · storageDEADBAND ±0.5

Tag settings

Source
Modbus TCP · hr:100 · float
Deadband
0.5 m³/h
Heartbeat
900 s
Report-by-exception
on
Read today
86 400
Stored
1 214
Chunk
1 d
Compress after
1 d

Virtual tag · Total flow

${FT-101} + ${FT-102}

02 · Watch

Alarms that reach someone

An alarm service checks the rules every few seconds, whether or not anyone has the platform open. When a rule fires, Messaging sends it down an escalation list until someone acknowledges.

Alarm rules

  • Several rules per tag — numeric, digital or on a totaliser's volume over a period — with severity info, warning or critical, and categories.
  • Hysteresis: an alarm above a limit clears only once the value is back below the limit minus the hysteresis.
  • An on-delay for live sources: the breach must hold for a set time before the alarm is raised.
  • Datalogger files too: every crossing inside a delivered file raises its alarm, stamped with the time of the reading.

Communication loss

  • Each equipment has a timeout. When nothing arrives for that long, a Communication Lost alarm opens; it closes when data comes back.

Messaging

  • Email, Telegram, WhatsApp, an SMS gateway through a Teltonika cellular router, or your own HTTP gateway.
  • Escalation lists: each person has an order and a delay, and the next one is contacted until the alarm is acknowledged.
  • Acknowledge by replying on Telegram or to the SMS gateway, or in the platform — the escalation stops at once.
  • Messages that fail to send are retried.

Forecast alarms

  • With the prediction module, a rule on the forecast is raised when the forecast crosses a limit within a chosen window — before the measured value gets there.
SyncTide / Alarms · Pumping station 1ESCALATING
Open
1
Acknowledged today
6
Comm. lost
0

Alarm PT-20103:12 – 03:19

  1. ACKAcknowledged by reply, escalation stoppedSMS gateway · supervisor · 03:19:05
  2. LEVEL 2Sent to the supervisorMessaging · SMS gateway · 03:17:42
  3. NO REPLYNo acknowledgement after 5 minescalation list · night shift
  4. LEVEL 1Sent to the on-call technicianMessaging · Telegram · 03:12:41
  5. CRITICALPressure above 6.5 barPT-201 · 03:12:40

03 · Analyse

Trends, dashboards and what comes next

Put tags from any source on one chart, build the screens your team looks at every day, and compare equipment and sites.

Explorer

  • Tags from different equipment and protocols on one time axis.
  • The time axis is proportional to time, and an expected sample interval per equipment shows where data is missing instead of drawing a line across the gap.

Dashboards, heatmaps and rankings

  • Dashboards with live values that refresh by fetching only what changed. New in 1.14.7 — coming soon
  • A calendar heatmap of a tag's daily average, maximum, minimum, total or change, over up to a year.
  • A ranking of equipment by a tag's change, average, maximum, minimum or last value.

Prediction

  • One model per tag and horizon, retrained every night, with horizons of up to seven days.
  • A forecast with a band between the 10th and 90th percentiles, widened when the real misses show it is too narrow.
  • Before training, a ceiling check scores simple references — the average, the hour-of-day table, the last value — so you see what a model has to beat.
  • Prediction is an optional module of the licence.
SyncTide / Explorer · Pumping station 1FORECAST

Flow, level and forecast7 days + 2

  • FT-101 · Modbus
  • LT-07 · file
  • forecast

Daily average · FT-101last 8 weeks

04 · Report

PDFs with your letterhead, Excel in your layout

New in 1.14.8 — coming soon

Reports module

SyncTide draws the PDF itself, with the header you set up and preview in the platform. Excel reports keep the layout of the workbook you upload.

The PDF header

  • Your logo, the SyncTide logo or none, on the left or the right.
  • A title that is automatic or fixed, a subtitle and the company name.
  • Information boxes in the order you choose: report date, period start and end, first and last data, equipment, site, generated by, time zone, report type.
  • Colours, footer text, page numbers, portrait or landscape — with a live preview while you edit.
  • Several headers can exist; each report template can use its own.

Excel

  • An Excel report fills the workbook layout uploaded for its template.

Schedules

  • Daily, monthly or yearly reports at a set time, sent as an email attachment to a list of recipients.
  • Scheduled exports of raw data as CSV, with your column order and separator.
  • Long reports are generated in the background; the platform tells you when the file is ready. New in 1.14.7 — coming soon
SyncTide / Reports · HeaderPREVIEW

Header · Default

Logo
your logo · left
Title
automatic
Boxes
PeriodFirst dataLast dataSite
Colours
Page
portrait · page X of Y

Schedules

  1. RUNNINGAnnual summary, in the backgroundyearly · started 06:05
  2. SENTDaily flow report · PDFdaily · 06:00 · 3 recipients
  3. READYMonthly report · Excelmonthly · 1st at 07:00

05 · Correct

Fix the history, keep the trail

Editor module

Meters drift, a sensor is replaced, a link drops for a night. The editor changes the stored history without hiding what was there before.

Edits

  • Drag points on the chart, add missing points, shift a period by a percentage or an amount, or set digital values.
  • Every change needs a written reason.
  • Each change is a batch that records who, when, the reason and the values before — and it can be reverted.

Fill gaps from forecasts

  • Where a communication gap left a hole, accept the stored forecast's points for it — exactly the forecast line, nothing interpolated.
  • Filled points stay marked, and real data that arrives later replaces them.
  • Filling from forecasts needs the prediction module.
SyncTide / Editor · FT-1012 EDITS

Stored and corrected valueslast 3 days

  • original
  • corrected
  • filled from forecast

Edit history

  1. FILLGap filled from the forecast · 6 hreason: link down overnight · operator
  2. OFFSET−2 % over 3 daysreason: meter recalibrated · revertible
  3. REVERTEDPoint edit undonereason: wrong point · admin

Where the data comes from

Modbus TCP, OPC UA, IEC 60870-5-104, MQTT, datalogger files, formulas and forecasts — and field visits from 1.14.8 — what each one supports, for the engineer who connects it.