# Table calcuations

**URL:** <https://forum.inductiveautomation.com/t/table-calcuations/19053>\
**Category:** Ignition\
**Created:** [August 1, 2018, 7:18pm UTC](https://forum.inductiveautomation.com/t/table-calcuations/19053 "2018-08-01T19:18:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashley.schreder](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@Ashley.schreder](https://forum.inductiveautomation.com/u/Ashley.schreder)\
**Post date:** [August 1, 2018, 7:18pm UTC](https://forum.inductiveautomation.com/t/table-calcuations/19053/1 "2018-08-01T19:18:32Z")

</div>

I am trying to design table that will show value added time ( time the counter is changing) and non-value added time (when the counter is not counting). I would also like to add the mean, median to this data set. I am not sure on the coding of this and I am not sure if its even possible in ignition.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [August 1, 2018, 7:35pm UTC](https://forum.inductiveautomation.com/t/table-calcuations/19053/2 "2018-08-01T19:35:40Z")

</div>

There is really too little information here.

Are we talking about uptime/downtime and production counters, or this for takt time? Is it delineated over time, per part, or some other unit not mentioned?

---

<div class="post-metadata">

**Author:** ![Mr.K001](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mr.K001](https://forum.inductiveautomation.com/u/Mr.K001)\
**Post date:** [August 3, 2018, 3:55pm UTC](https://forum.inductiveautomation.com/t/table-calcuations/19053/3 "2018-08-03T15:55:03Z")

</div>

@JordanCClark is right, not much information here but i think you might be better off having a folder with the counter tag and two timers(from PLC), one timer that counts when the counter isn’t moving and one timer that counts when the counter is moving and put all in a transaction group and grab the data once every min or so.  
I love using Ignition with as much as I can but there are some stuff that PLC does best…  
if you can give more information we might be able to help you better.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 3, 2018, 5:32pm UTC](https://forum.inductiveautomation.com/t/table-calcuations/19053/4 "2018-08-03T17:32:15Z")

</div>

First, you have to decide your definition of “moving”. It’s not knowable just from a cycle counter until at least the minimum takt time has passed.
