Why is the "formatted size" in a door schedule different from the actual door size?

[Michael_Gia]

Why is the "formatted size" different from my door size?

 

I really just need a column that can display the door size and hinge side.

 

I was hoping the "size column" could do that.

 

 

The image below shows a 30" x 84" door but the size column shows 2670 L 

What does the 2670 refer to and how to correct?

 

Why is this so confusing or am I that dense? (highly possible)

 

[DBCooper]

2670 means 2'6" x 7'0".

 

If you want the size in inches, you could just add the width and height columns.

 

[TeaTime]

Could also make a custom column reporting something like %width%" x %height%" - that's a bit more work though.

[Michael_Gia]

3 hours ago, DBCooper said:

2670 means 2'6" x 7'0".

 

If you want the size in inches, you could just add the width and height columns.

 

 

Thanks, for the clarification. 
 

Pretty humiliating, actually. 
 

Learning every day.

[GeneDavis]

I worked in the door business, and every one of our many distributors, coast to coast, had window lines.  Door callouts, by callouts I mean the number strings like 2670, differ from window callouts in this key way:  with doors, the sizing is the frame opening, and with windows, it is the unit size, which includes frame.

 

And the convention for both is feet-inches.  Width first, height after. 

[Michael_Gia]

2 minutes ago, GeneDavis said:

And the convention for both is feet-inches.

So my door supplier will be comfortable with 2670 L ?
 

Up until now I would just send them the plan but I’m trying to help them out a bit for a much larger project. 

[JKEdmo]

39 minutes ago, GeneDavis said:

I worked in the door business

Gene,

 

Just curious -- have you ever had issues or needed to clarify with your door / window mfgs Chief's default sizing convention (e.g. 2670) or is it pretty clear to them what's meant?

 

The reason I ask is in my "ideal world" the inches would be underscored (e.g. 2670) but Chief does not do this out of the box.

 

Thanks,

 

Jim

 

 

 

[GeneDavis]

I think window schedules should table out unit width and unit height.  For windows, the Chief callout might lead to a mistake in window sizing.  So while my window schedules do include "label," they also include width and height.

 

Doors same.  Label plus width and height.

 

Why leave things to chance?  Use the paper space to avoid costly errors in building.  That's what we're doing here with all this con doc documentation, right?   

[JKEdmo]

On 5/9/2024 at 7:08 AM, GeneDavis said:

I think window schedules should table out unit width and unit height.

Thanks for your insight.

 

On 5/9/2024 at 7:08 AM, GeneDavis said:

Why leave things to chance?

 

I agree.

 

Jim

 

[Joe_Carrick]

I'm using a custom macro that displays the inch value as a superscript.  I actually include several macros to include additional information such as:

• type 
• egress
• tempered
• etc.