SCADA This topic has 2 replies, 1 voice, and was last updated 22 years, 5 months ago by Martin. Viewing 3 posts - 1 through 3 (of 3 total) Author Posts 12th January 2001 at 17:05 #33174 limsiGuest Is there sombody tha could help me on how to characterize a traffic model for a SCADA (Supervisory Control and Data Acquisition) System? 19th January 2001 at 06:20 #33175 BrettGuest Limsi, I have no experience with SCADA, but after reading a number of papers of data diemsnioning, suggest that you may consider SCADA dimensioning in a similar fashion. Have a look at citeseer.nj.nec.com/leland93selfsimilar.html, and other similar papers at this site. It is a good source of info, Good luck, Brett 21st June 2001 at 22:23 #33176 MartinGuest Limsi, You posted your question back in January, so this response may no longer be of interest. The traffic model for a SCADA system depends critically on the nature of the scan process. There are three alternatives commonly used. Each requires a different model. a. Periodic scans with all data returned with each scan response. (For example, scan all status points every 5 seconds and all analog points every 30 seconds.) b. Periodic scans with only changed data returned (“report by exception”) c. No scanning, with remote terminals reporting changed data on detection (“unsolicited data reporting.”) The traffic with the third alternative is the closest to a Poisson distribution, where the Erlang calculations can be applied. If otherwise, you can drop me e-mail, and I’ll see if I can help. Martin Delson firstname.lastname@example.org Author Posts Viewing 3 posts - 1 through 3 (of 3 total) The forum ‘Telecom Design’ is closed to new topics and replies.