How to have different elevations in design options-Revit

[panizBMS2M]

Hi all,

I need to have 2 different options, with different elevation heights. but I cannot assign design options to elevations. Would you please help me.

[ToanDN]

Do you mean different Level heights?

[panizBMS2M]

Yes exactly. 

[ToanDN]

Then you need to either create different Levels and use one for each design option.  Or model the design options without any level constraints.

[panizBMS2M]

But when I'm trying to create new level an add it to for example design option 2, it shows me an error as attached screenshot depicts.

[ToanDN · Accepted solution]

---

@panizBMS2M wrote:

But when I'm trying to create new level an add it to for example design option 2, it shows me an error as attached screenshot depicts.

---

No you don't add Levels to a design options, but elements constrained to the Levels.  You can hide the unwanted level in each design option view for less confusion.  But it maybe easier to constrain to ref planes instead of Levels.

[ToanDN]

The easiest way may be to make a copy of the model and change the level elevation instead of using design options.

[panizBMS2M]

My intend is to avoid creating different models, and using design options. And I'm trying to see how can I implement what you explained earlier. Thank you so much for the solution. 

[barthbradley]

---

@panizBMS2M wrote:

Hi all,

I need to have 2 different options, with different elevation heights. but I cannot assign design options to elevations. Would you please help me.

---

Is this for Architectural Planning? Are you creating DOs that add Levels of construction or DOs where Levels differ in relationship to one another (for example, Level 2 is 10'-0" in DO 1 and 15'-0 in DO 2)?  Or, are you simply wanting all the Levels to read a different Elevation?        

[panizBMS2M]

It's a DOs where Levels differ in relationship to one another! Same thing as your example. and I don't want to show elevations on DO1, in DO2 sheets! (I prefer not to hide them because it's time consuming)! Any better suggestion?

[barthbradley]

---

@panizBMS2M wrote:

It's a DOs where Levels differ in relationship to one another! 

---

Well, that's a pretty significant thing. Could even become nightmarish. I wouldn't do Design Options in this case. I'd create another model.   

[panizBMS2M]

 I would keep it in one model, but I guess the only choice is having all levels and hiding other DO's levels!

Thanks @barthbradley!  

[hwo_osa]

our office have just encountered this - we have a pretty messy early-stage schematic design model of a campus with different buildings and multiple design option sets, each with several design options for differing level heights for the different buildings. We now have to reduce the ground floor level height of one of the buildings across all design options, so all of the levels above need to move down as well. Trying this results in an error that essentially forces us to delete all model elements of one of the design options as well as the corresponding ground floors.

Conclusion: Design options with differing story heights are a bad idea. You have to either create completely separate level sets for each design option and hide them via filters, or you start a completely new model for every option.

This is making early stage design work very tedious. Maybe it would be a good idea to be able to move levels to a specific design option.....