Business cases – Soft migration to Scada-LTS
This is a real-life example of a production site, modified to protect the client’s confidential information.
Using a Scada-LTS SQL datasource,

Example of a SQL datasource in Scada-LTS
it is possible to fetch, on regular basis, the datapoint values from an another Scada system, assuming the data structure and format is opened. (At least, it is the case with the Scada-LTS, so it is fully possible to fetch data from a Scada-LTS to an another Scada-LTS instance).

This allows to develop/customise the Graphical Views, the Event Triggers, the Alarms, … on the new Scada-LTS system, based on the actual values fetched by the Scada system that has to be replaced, without requiring to change the connections between the Scada and the field devices (PLCs).
This “temporary” solution may last as long as the new Scada-LTS system is not fully functional and receipt by the customer. At that moment, the field protocols may be moved from the old Scada system to the new one, and the old system can be decommissioned without business interruption.
The new Scada-LTS server may even send alarms using modern channels, such as SMS, e-mails, … based on the data received from the old Scada system, during the migration phase.
