# OEE Downtime Table - Merging 2 Downtime Events

**URL:** <https://forum.inductiveautomation.com/t/oee-downtime-table-merging-2-downtime-events/113395>\
**Category:** Ignition\
**Tags:** sepasoft, vision\
**Created:** [January 19, 2026, 7:49pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-table-merging-2-downtime-events/113395 "2026-01-19T19:49:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Taylor\_Jones](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Taylor\_Jones](https://forum.inductiveautomation.com/u/Taylor_Jones)\
**Post date:** [January 19, 2026, 7:49pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-table-merging-2-downtime-events/113395/1 "2026-01-19T19:49:19Z")

</div>

Is anyone aware of if it’s at all possible to “merge” 2 downtime events into one using Sepasoft’s OEE Downtime Table?

I know technically you could do this through the value editor by deleting the “running“ tag value state in between the 2 downtime states and then by deleting the second downtime state it would show as though the first downtime state has been in effect that entire duration.

The reason I ask is because it was brought up that we have a user requirement for some of our downtime events that an additional note is required to be entered manually and these downtime events are reoccurring consistently with only a dozen or so seconds between them where the equipment is technically in a “running” state. So realistically the equipment is down that entire time but there are several short downtime events instead of one that encompasses that entirety. Thus leading to a bunch of duplicate work for our end users to carryout instead of just entering one note for the entire block of downtime.