This issue, @eeshakhanna , is that the HVAC templates of the OpenStudio standards gem are just set up to not react to individual zone ventilation schedules. I guess that the OpenStudio team made that decision because an HVAC with central air loop has one central outdoor air mixer for several zones on the loop. So, if you diminish the total outdoor air being mixed at this central exhaust/intake based on an averaged schedule across multiple rooms, you might end up distributing the “ventilation reduction” unevenly (and consequently end up not meeting ASHRAE 62.1 in some rooms).
But I know that ventilation schedules on central air loops like this are used to model important ECMs so we’ll have to expose it somehow. I think the way that we will end up doing it is to add an option for ventilation_schedule_ on the components used to assign detailed HVAC templates to Rooms. Feel free to let me know whether you agree with this strategy on this Github issue:
In the meantime, you can account for your schedule in the OpenStudio application by going to the DOAS loop’s outdoor air mixer and applying a “Minimum Outdoor Air Schedule Name” on this object. For DOAS systems, you will probably need to change the “Minimum Fraction of Outdoor Air Schedule Name” to be blank:
Then, you can save the OSM and simulate it with the “HB Run OSM” component.
If you need a fully Grasshopper-based solution, you can also just model the whole system in IronBug, where you have full control over all HVAC properties. You can apply your IronBug HVAC to the OSM exported from LBT Honeybee using the workflow here: