Door & Window Schedule Labels ?

[ACADuser]

So when we are late in the project & the client wants to add windows I do not want to reorder the schedule.

It would be great is we could have W14 and new W14a or W14.1 so the windows call outs don't  change down stream of W14.

 

This causes confusion for any take offs done by the GC or window supplier.

 

Any way to deal with this?

 

[Alaskan_Son]

Just put any new windows onto a separate schedule.

[ACADuser]

Duh, wish I had thought of that! A little awkward on the plans.

But I'm off to try it.

 

[joey_martin]

Perhaps label it "Addendum Schedule"

 

[ACADuser]

Good Idea.

This is what I have so far.

[Alaskan_Son]

1 minute ago, ACADuser said:

Good Idea.

This is what I have so far.

 

Don't forget that we can also control the Schedule Number Start these days.

[ACADuser]

When a window is adjacent to a balcony that name is appended.

Any way to trim that off, see W8 & W9

 

[Alaskan_Son]

1 minute ago, ACADuser said:

When a window is adjacent to a balcony that name is appended.

Any way to trim that off, see W8 & W9

 

Are you talking about the same thing that's happening with Patio, Roof at Stairs, and Rear Entry?

[ACADuser]

Yes, looks like Chief know which is the interior side then adds / plus the exterior side room.

[Alaskan_Son]

Simple text macro placed into an Object Information Field.  Using the #String.split method along with the #Array[] method for example you could just use %room_name.split("/")[0]%:

 

room_name = "Dining/Balcony 201"
room_name.split("/")[0]
#=>  "Dining"

...assumes you don't use the forward slash in your room names though.  If you do, the macro would need to be a little more complex.

 

 

[ACADuser]

Thanks You Sir.

 

[ACADuser]

So for the macro to be used as Room Name it will need a custom Field or repurpose an existing field.

Just wanted to be clear here.

 

[Alaskan_Son]

29 minutes ago, ACADuser said:

So for the macro to be used as Room Name it will need a custom Field or repurpose an existing field.

Just wanted to be clear here.

 

 

It doesn't matter.  Functionally speaking they're pretty much the exact same thing.  Main difference is really just that you can give your own Custom Fields a more appropriate name.