# Statistic Data Availability for STTP

**URL:** <http://discussions.gridprotectionalliance.org/t/statistic-data-availability-for-sttp/1421>\
**Category:** openPDC\
**Created:** [June 16, 2025, 8:01pm UTC](http://discussions.gridprotectionalliance.org/t/statistic-data-availability-for-sttp/1421 "2025-06-16T20:01:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Renan\_Pires](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/renan_pires/32/1088_2.png) [@Renan\_Pires](http://discussions.gridprotectionalliance.org/u/Renan_Pires)\
**Post date:** [June 16, 2025, 8:01pm UTC](http://discussions.gridprotectionalliance.org/t/statistic-data-availability-for-sttp/1421/1 "2025-06-16T20:01:15Z")

</div>

Hello, I hope this message finds you well.

We are currently analyzing a configuration where the same PMUs are being forwarded from `openPDC_1` to other PDCs through two different streams:

 ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/0/047412d8354e548d2671f33743f839aa882fb85c.png)

 ![TCP - C37.118-2011](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/e/e718ffb2a72461bd09d2bdbd9bc35e63f9e87ff4.jpeg)

- **Stream\_2** : using the Output Stream of openPDC\_1 in C37.118 protocol\*

 ![STTP](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/2/2f232f93093a29fa15a6d0f1f73987fa866ac7ac.png)

- **Stream\_3** : using the STTP protocol\*

Both streams carry identical sets of PMUs.

When using **Stream\_2** , we are able to view detailed statistics information in openPDC\_3 — including stream latency, data frames received, expected, and lost — as expected from the standard openPDC\_1 outputs.

However, when using **Stream\_3** (STTP), these same statistical metrics do not appear in openPDC\_3.

Is it possible for openPDC\_3 to also calculate and display these statistical metrics (e.g., latency, frames received/lost, etc.) when data is transmitted via STTP, just like openPDC\_2 does?

Any clarification would be greatly appreciated.

Best regards,  
Renan Pires

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [June 16, 2025, 8:40pm UTC](http://discussions.gridprotectionalliance.org/t/statistic-data-availability-for-sttp/1421/2 "2025-06-16T20:40:52Z")

</div>

Hello Renan Pires,

It is not actually possible to compute the exact same set of statistics. In particular, STTP is not a frame-based protocol so any statistics related to frame counts or frame rates simply wouldn’t apply.

For latency, I do see that the “lifetime latency” statistics are provided by the STTP subscriber. Honestly, I’m not sure why `Lifetime Maximum Latency` is missing from your screenshot–it is supposed to be `UDP1_1!SUB-ST13`. Maybe check if a measurement with that signal reference exists and whether it is associated with the STTP subscriber device record. If you can figure out why that statistic is missing and how to get it back, I expect you should be able to see that statistic as well.

As for any of the other input stream statistics that are currently unavailable from the STTP subscriber, assuming it is theoretically possible to compute them, then it should also be possible to update the source code to provide them. Unfortunately, it is not something you can make happen through configuration alone.

Thanks,  
Stephen

---

<div class="post-metadata">

**Author:** ![Gabriel\_Effting](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/gabriel_effting/32/1532_2.png) [@Gabriel\_Effting](http://discussions.gridprotectionalliance.org/u/Gabriel_Effting)\
**Post date:** [November 24, 2025, 5:57pm UTC](http://discussions.gridprotectionalliance.org/t/statistic-data-availability-for-sttp/1421/3 "2025-11-24T17:57:21Z")

</div>

Hello everyone, I’m facing a similar issue where some STAT-type measurements of interest are being lost.  
The problem is happening because the IED, using a GE N60, sends more than one PMU within the same data stream. When the PDC receives the measurements, the latency values stop belonging to each individual PMU and instead become associated with the aggregated stream. When this aggregated stream is sent via STTP to another PDC, this information is lost.

I would like to know if there is any way—perhaps through an adapter—to calculate the average latency locally. Specifically, the same average latency that openPDC normally computes.
