Business solutions - Telemetry

Telemetry & management of time-stamped data at the source

Compatible with a wide range of remote management equipment or connected objects (IoT) on all types of communication media, Topkapi SCADA software meets all your telemetry needs. 

Topkapi: a solution designed for telemetry and management of time-stamped data at the source

Widely used for the management of drinking water or wastewater networks, energy management, public lighting, etc., remote management requires a real know-how in industrial supervision. The various type of equipments encountered and the associated communication protocols, the numerous communication media used and the ability to process data natively (often time-stamped at the source), as in real time, are some of the challenges that must be met.


To meet the practical and technical expectations of users, Topkapi software platform, published by AREAL, has been designed to natively manage time-stamped data at the source and permanent or non-permanent links (GSM data, 3G/4G, etc.) with connected equipment. 
 

On the one hand, Topkapi interfaces natively with all remote management equipment on the market (PLCs and data loggers from brands such as HWM, Technolog, Ovarro, Sofrel, Perax, Wit, etc.) or connected objects, and on the other hand, it is compatible with all communication media. 
 

Its configuration is as simple as for a real-time link and completely transparent to the user. To facilitate the deployment of applications, AREAL has also developed a configuration assistant called SOFTLINK which allows the auto-setting of an application by importing an external data source (files from the manufacturer's software used to configure PLCs or remote management stations or customised files).
 

As an optional module of the Topkapi SCADA solution, it integrates the management of time-stamped data at the source in a native way without any particular development in:

  • Taking into account the date and time sent by the remote system to update the Topkapi archive files.
  • By treating the data as if it had been acquired in real time: for the generation of alarms specific to supervision, for example.

More details on timestamping at source

What is timestamping at the source?

Timestamping is a mechanism for associating a date and a time with an event or a data. Its purpose is to record the value of a variable at a given time.


In the case of conventional use of so-called "real-time" protocols such as Modbus IP, Modbus or Profinet, the time and date stamping of events/data is carried out by the supervision according to criteria defined by configuration (dead band, periodic, event, etc.) in order to create historical data.
In the case of timestamping at the source, it is the equipment (remote management PLC, data logger, regulator, possibly an industrial PLC, connected object, etc.) that is responsible for dating the information according to its own criteria; it is then up to the SCADA software to "retrieve" and process this time-stamped information, ideally as if it had been acquired in real time.


The acquisition of time-stamped data at the source by the SCADA requires the use of communication protocols supporting this data profile. These protocols are known as:

  • Proprietary: Lacbus&Sofbus (Sofrel), TRSII (WIT), etc.
    or
  • Standardised and normalised : BacNet, DNP3, IEC 60870-5-101 or -104, OPC DA, etc.


But also other exchange mechanisms such as SMS, file transfers on FTP server, serial or IP Modbus time-stamped, Webservices, etc.
 

When to use timestamping at the source?

The use of time-stamped data at the source may become necessary when:

  • The connection between the SCADA and the equipment is not permanent (case of PSTN links, GSM Data (2G), energy autonomous communicating equipment, non-permanent IP links, etc.). In this case, information from the equipment is never lost.
  • There are doubts about the reliability of the communication medium and/or you want to make the data history more reliable (avoid "gaps" in the data) in the case of 4G networks links for example: in the event of loss of service on the communication medium, you never lose data from the equipment.
  • The aim is to integrate data from an IoT portal.
  • This is used, for example, in the case of fine chronology to discriminate the first fault in the case of an avalanche of faults following a first event.

Remote management & time-stamped data at the source

From a supervisory point of view, remote management can be summed up as the ability to remotely manage and control equipment. In this context, remote management uses a wide variety of communication media - PSTN, LP/LS, 2G (GSM data), GPRS, 3G, 4G, ADSL, Radio, etc. - therefore links that are not necessarily permanent, hence the need to manage time-stamped data at the source (see above).
 

Business sectors

Topkapi: multi-sector software platform

Find out how our SCADA solution meets the needs of your business sector: challenges, functional advantages, business applications, concrete cases of use.
A project? Any questions? We are here to listen to you.
Contact us