# Add Revit to eQuest Export Settings for HVAC Mapping

**URL:** <https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138>\
**Category:** Revit Plugin\
**Tags:** feature-request\
**Created:** [September 13, 2023, 6:02pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138 "2023-09-13T18:02:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmaarouf](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/bmaarouf/32/6271_2.png) [@bmaarouf](https://discourse.pollination.solutions/u/bmaarouf)\
**Post date:** [September 13, 2023, 6:02pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/1 "2023-09-13T18:02:56Z")

</div>

Hi Mostapha,

**Background**  
eQuest is inherently very unfriendly when mapping HVAC systems to zones or zones to HVAC systems. A user would need a lot of time to apply changes, add, or remove HVAC systems or zones assigned to those systems

**Feature Request**  
I would kindly request that as part of the Revit export settings, the user can select whether the systems be assigned as:

1. One HVAC system for the entire building
2. One HVAC system per floor
3. One HVAC system per each zone  
This adds incredible amount of control and reduces friction when exporting models to eQuest.

**Additional Notes**  
From the Syden Opera example .inp I realized that you have option 2 above: system per floor; and that’s generally good but I see people preferring option 3 for residential and office towers. Also, your zones are currently all assigned as unconditioned and your systems assigned as “SUM” - and I just want to inform you that this is fine and workable until we get more advanced export features in the future.

Cheers.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [September 13, 2023, 10:20pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/2 "2023-09-13T22:20:53Z")

</div>

Hi @bmaarouf,

Thank you so much! Appreciate you taking the time to document this. I like the idea and I think we can even be more flexible and let users group the rooms as needed but we can start with the 3 options that you mentioned.

> [@bmaarouf](#):
>
> From the Syden Opera example .inp I realized that you have option 2 above: system per floor

Can you help me to understand how did you figure this out from the INP file or the eQuest UI?

Let me know if you want me to create a smaller model for you for testing. I have also updated the INP files for the Revit sample models to GitHub if those are easier to inspect. I imagine the Revit basic model should be a good case to use as a reference.

> **[GitHub - pollination/pollination-sample-models: A repository for sample...](https://github.com/pollination/pollination-sample-models)**
>
> A repository for sample models that are created by Pollination Rhino and Revit plugins - GitHub - pollination/pollination-sample-models: A repository for sample models that are created by Pollinati...

---

<div class="post-metadata">

**Author:** ![bmaarouf](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/bmaarouf/32/6271_2.png) [@bmaarouf](https://discourse.pollination.solutions/u/bmaarouf)\
**Post date:** [September 14, 2023, 4:53pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/3 "2023-09-14T16:53:34Z")

</div>

1. How did I know it’s system per floor?

- From the Sydney\_Opera\_House.inp I can scroll down to line 69767 and start reading the first system created **“Level\_0flr\_Sys (SUM)” = SYSTEM** any zones written under this system will be mapped to this system. As such, I see 5 HVAC systems:  
**“Level\_0flr\_Sys (SUM)” = SYSTEM** _line #69767_  
**“Level\_1flr\_Sys (SUM)” = SYSTEM** _line #69821_  
**“Level\_2flr\_Sys (SUM)” = SYSTEM** _line 69843_  
**“Level\_3flr\_Sys (SUM)” = SYSTEM** _line #69865_  
**“Level\_4flr\_Sys (SUM)” = SYSTEM** _line 69879_  
And I see zones defined under each of the 5 systems above. It seems to me that the zones in each floor are assigned to one system. Meaning, one system per floor.

- Assuming a person import this .inp to eQuest, when you navigate to the air-side tab in the UI you will see the same arrangement I described above.  

1. Can I help in testing?

- Absolutely, let me know when you have that ready.

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [September 14, 2023, 5:14pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/4 "2023-09-14T17:14:27Z")

</div>

Got it! Thank you so much. This is basically an additional mapping. Should be straightforward to implement.

cc: @tfedyna

---

<div class="post-metadata">

**Author:** ![tfedyna](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/tfedyna/32/170_2.png) [@tfedyna](https://discourse.pollination.solutions/u/tfedyna)\
**Post date:** [September 15, 2023, 4:16pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/5 "2023-09-15T16:16:24Z")

</div>

Hi! @bmaarouf  
I’ve attached two versions of the sydney opera house model, one containing **option 1** one building = one system.  
as well as **option 3** , one system per zone.  
You may notice there are also schedules and loads ( lighting, people, electric equipment and infiltration )  
That is a new feature as well  
[model\_method\_test\_model.inp](https://discourse.pollination.solutions/uploads/short-url/t6Mmbwoyy7pL10hUj8amwVGYe5R.inp) (2.1 MB)  
[room\_method\_test\_model.inp](https://discourse.pollination.solutions/uploads/short-url/yll7Fs5F2gHI2vle1h1fyo70Avp.inp) (2.1 MB)

---

<div class="post-metadata">

**Author:** ![bmaarouf](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/bmaarouf/32/6271_2.png) [@bmaarouf](https://discourse.pollination.solutions/u/bmaarouf)\
**Post date:** [September 18, 2023, 6:23pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/6 "2023-09-18T18:23:05Z")

</div>

Thanks Trevor, happy to engage with you again on this front. It’s great to see schedules assigned now. Let me know if I can help or test anything furhter.

---

<div class="post-metadata">

**Author:** ![tfedyna](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/tfedyna/32/170_2.png) [@tfedyna](https://discourse.pollination.solutions/u/tfedyna)\
**Post date:** [September 19, 2023, 2:46pm UTC](https://discourse.pollination.solutions/t/add-revit-to-equest-export-settings-for-hvac-mapping/3138/7 "2023-09-19T14:46:16Z")

</div>

Likewise! And thank you, I’ll be sure to take you up on that!