Window Schedule Problem

[JKEdmo]

Hi,

 

I have 6 fixed broken-arched clerestory windows (1-6 shown below):

 

 

These should schedule out as 2 types (left vs right arch) with quantity 3 each.  Yet, my window schedule shows them all as 1 type, quantity 6.  Chief seems them all as one type and does not recognize the mirrored window type.

 

 

How do I fix this scheduling error?

 

 

Thanks again,

 

Jim

 

 

[tundra_dweller]

I have noticed this same behavior with trapezoid windows. I figured I didn't have something quite right schedule/label wise but couldn't pin it down.

[JKEdmo]

54 minutes ago, tundra_dweller said:

I have noticed this same behavior with trapezoid windows. I figured I didn't have something quite right schedule/label wise but couldn't pin it down.

 

Brett,

 

Thanks for the reply.  I think I'll submit as a suggestion to Chief for them to look in to.

 

Jim

 

[MPDesign]

Hi Jim,

I was looking at this and found if you specify the label and add the text "LeftArch" and "RightArch" it seperates it correctly in the window schedule

 

[Chrisb222]

15 hours ago, JKEdmo said:

How do I fix this scheduling error?

 

Something needs to actually be included in the schedule that is different between the two styles of windows. Doesn't matter what it is, but if the schedule doesn't see any difference, it will group them together.

[JKEdmo]

12 minutes ago, MPDesign said:

Hi Jim,

I was looking at this and found if you specify the label and add the text "LeftArch" and "RightArch" it seperates it correctly in the window schedule

 

 

 

Thanks Michael.  That's a good workaround tip.

 

I sent this in to tech support and we'll see what they say.  I feel this is a bug or at least a program deficiency.  Schedules should automatically report these as different windows.

 

Jim

 

 

[DBCooper]

I don't think it's actually a bug because this is the way schedules have always worked in Chief.  Chief will group objects together just based on the text displayed in the schedule.  It ignores what the objects might actually look like.  So if you want your windows to be separate rows in the schedule, you have to add something to the schedule to make them different.

 

Michael's solution is easy and will work but you could make it more automatic by changing your labels to use the built in macros "%automatic_label%-%arch_side%" or by adding some info to the OIP comments such as "%arch_type_name%-%arch_side%".

 

 

 

 

 

[JKEdmo]

19 minutes ago, DBCooper said:

I don't think it's actually a bug because this is the way schedules have always worked in Chief.  Chief will group objects together just based on the text displayed in the schedule.  It ignores what the objects might actually look like.  So if you want your windows to be separate rows in the schedule, you have to add something to the schedule to make them different.

 

Michael's solution is easy and will work but you could make it more automatic by changing your labels to use the built in macros "%automatic_label%-%arch_side%" or by adding some info to the OIP comments such as "%arch_type_name%-%arch_side%".

 

 

 

 

 

 

Thanks for the insight.  Your explanation of how Chief schedules things based on text only really explains this scheduling behavior.

 

Jim