Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

Bandwidth estimation for store-and-forward data

  • Last UpdatedJan 15, 2025
  • 2 minute read

If there is a network disconnection, HCAL sends data to local storage and later forwards the data to the Historian. After the forwarding process starts, HCAL will try to send as much as data as possible with a large packet. The forwarding bandwidth is the bandwidth required to stream the store-and-forward data.

The store-and-forward storage size is the same as for local Historian storage. The following table lists the average sizes used for bandwidth estimation used in this example.

Tag Type

Storage Item Size (Bytes)

Discrete Tags

5

Analog Tags (4 byte data)

8

String Tags (32 byte string)

37

Analog Summary (4 byte analog)

37

State Summary for Analog (for 10 states)

28 * 10 = 280

State Summary for Discrete (for 2 states)

20 * 2 = 40

State Summary for String (10 states and 32 byte string)

(1 + 32) * 10 = 330

The forwarding bandwidths are calculated using the following formulas:

BandwidthForwarding = 1.04 * 8 * SEach Tag Type (Data Rate * Storage Item Size)

BandwidthRecommendedForwarding = 1.3 * BandwidthForwarding

For this example, if all are stored in the local storage engine and forwarded later, the number of bytes required for every second is as follows:

  1. 798 * 8 = 6384 Bytes

  2. 815 * 5 = 4075 Bytes

  3. 187 * 25 = 4675 Bytes

  4. 800 * 37 / 60 = 493 Bytes

  5. 800 * 37 / 3600 = 8 Bytes

  6. 800 * 280 / 60 = 3733 Bytes

  7. 800 * 280 / 3600 = 62 Bytes

BandwidthForwarding = 1.04 * 8 * (6384 + 4075 + 4675 + 493 + 8 + 3733 + 62) = 162 Kbps

BandwidthRecommendedForwarding = 1.3 * 162 Kbps = 211 Kbps

TitleResults for “How to create a CRG?”Also Available in