Knowledge baseStart
Getting started
From a fresh install to the first trend, alarm and report: the order to set SyncTide up in, and where each step lives in the platform.
SyncTide reads values from PLCs and RTUs (Modbus TCP, OPC UA, IEC 60870-5-104), from MQTT and from datalogger files, and keeps one history per tag. It watches that history with alarm rules, tells people through Messaging, draws reports and — with the Interventions module — records the work done on site. Everyone uses it from a browser: nothing is installed on the users’ computers or phones.
This guide follows the order that works best on a new installation. Each step links to the guide that covers it in full.
Before you start
- A server. A Windows machine or virtual machine on your network, or an instance in our cloud. See Installing SyncTide and the sizing simulator.
- Your licence file (
.lic). It sets the tag limit and the optional modules (Messaging, Reports, Editor, Forecasting, Interventions). Reading PLCs, MQTT and files is part of every licence. - The details of your devices: IP addresses and ports of the PLCs, the MQTT broker, or how your dataloggers deliver their files.
1. Install and sign in
- Run the installer on the server. The wizard asks for the database settings (the bundled PostgreSQL is set up for you), the folders for datalogger files and reports, the first administrator account and the licence file — the licence can also be uploaded later in Configuration → License.
- When it finishes, a welcome page opens on the server’s desktop with the address of the platform.
- From any computer or phone on the network, open
http://<server address>/and sign in with the administrator account.
An account that still has a default password is asked to change it before it can go on. Turn on two-factor authentication for your own account in My account; an administrator can make it compulsory per role in Configuration → Runtime → Security.
2. Add your first equipment
- Open Equipment and use Add device: a code, a name, an alarm category and how it is read — files, Modbus TCP, OPC UA, IEC 60870-5-104 or MQTT.
- On the Communication tab, fill in the connection (address, port, poll interval…) and press Test connection. It reads the device without saving anything.
- For a datalogger that sends files, the equipment gets its own folder; files dropped there are read automatically. You can also upload files from the browser.
Connecting data sources has the settings of each protocol and of the files.
3. Map the tags
On the Tag Mapping tab, link each tag the device sends to a system tag (a standard name and unit), with a scale factor if needed. Only active, mapped tags are stored and count towards the licence limit; a column that is not mapped still shows its current value but keeps no history. Map every tag whose history matters before you rely on it. See Tags, virtual tags and deadband.
4. Look at the data
- Dashboard — the live overview: values, active alarms and the equipment list.
- Explorer — any tags from any equipment on one time axis. Pick the tags in the series tree, choose the period and the bucket (or Raw to see every stored sample), and compare them on a shared axis or one axis per unit.
A line breaks only where data is really missing: set the equipment’s expected data period (Monitoring & Alarms) so the charts show gaps instead of drawing across them.
5. Raise an alarm and tell someone
- In Equipment → Monitoring & Alarms, add a rule on a tag: a threshold, a severity and, if the signal is noisy, a hysteresis.
- In the Messaging Center, add a gateway (email, Telegram, WhatsApp or an SMS gateway), the contacts, an escalation list, and an alarm rule that links them.
- Use Test send to check the gateway before you need it.
Alarms & Messaging explains each setting.
6. Schedule a report
In Reports, set up the PDF header once (Reports → Header: logo, titles, information boxes, colours) New in 1.14.8 — coming soon, then generate a template report or schedule one — daily, monthly or yearly — with a list of email recipients. See Reports and the PDF header.
7. Check that backups run
The installer schedules a backup every night at 02:00. In Configuration → Runtime → Retention, the Backups card lists the archives and takes one on demand. Copy an archive off the server now and then — a backup that only lives on the machine it protects is not enough. See Backups, recovery and updates.
Who can do what
Every account has one of three roles. An administrator can also limit any account to some equipment (by alarm category or by device); the limit applies to every screen, report and export.
| Area | Viewer | Operator | Administrator |
|---|---|---|---|
| Dashboard, Explorer | View | View | View and export |
| Alarms | View and acknowledge | View and acknowledge | Everything |
| Reports | View and download | View and download | Everything |
| Messaging contacts and rules | — | Create, edit, delete | Everything |
| Messaging gateways | — | View | Everything |
| Equipment settings | — | Create and edit | Everything |
| Users and Configuration | — | — | Everything |
Correcting stored values (the Editor module) is for administrators; every role sees which points were corrected. In the Interventions module, administrators manage the site structure and the forms, operators fill visits, and viewers do not see the module. New in 1.14.8 — coming soon