# Modeling Events - Scenario Time Parameters

**URL:** <https://forum.encoord.com/t/modeling-events-scenario-time-parameters/516>\
**Category:** General\
**Created:** [March 2, 2026, 7:44am UTC](https://forum.encoord.com/t/modeling-events-scenario-time-parameters/516 "2026-03-02T07:44:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![emmacooper](https://forum.encoord.com/letter_avatar_proxy/v4/letter/e/fbc32d/32.png) [@emmacooper](https://forum.encoord.com/u/emmacooper)\
**Post date:** [March 3, 2026, 9:01pm UTC](https://forum.encoord.com/t/modeling-events-scenario-time-parameters/516/3 "2026-03-03T21:01:57Z")

</div>

Hi @will,

Thanks for these instructions. It seems like it would be easy to run into infeasibilities related to generator up and down times using this approach, as the scenario will have two separate sets of generator ON/OFF/ONOFF events, where the first set is imported from the original DA problem, and the second set is loaded in using this [approach](https://forum.encoord.com/t/modeling-generator-on-off-events-over-time/273/2). While both sets of events may feasible when implemented in isolation, they may violate MinUpTime and MinDownTime constraints when combined. This might be exacerbated by the fact that the binary generator commitments from the DA problem are imported as ON/OFF events, as opposed to ONOFF/OFF events – even though I specified the ToProperty as ONOFF in the Transfer Configuration tab. Do you have any guidance on automated methods of identifying and reconciling any infeasibilities that may arise from conflicting sets of events?

Thanks,

Emma

---

_[View the full topic](https://forum.encoord.com/t/modeling-events-scenario-time-parameters/516)._