Production Standards - Sq. Ft. per Minute

We’re a manufacturer that has recently documented time studies for our production areas. The Production Standard we’ve recorded that is most universal across our production processes is a standard of Minutes per Square Foot or Minutes per Lineal Inch. For example, we might have a process of dimensioning that is 0.0287 minutes per square inch. Then we multiple the 0.0287 against our factor for each part; in this case our length and height of the part to get the total square inches cut. So if we had a part that 24"x12"x2", we’d take 24x2 to get 48 square inches and then multiple 48 by 0.0287 to get our total time for that part of 1.377 minutes. Note, sometimes this factor can change depending on the orientation of the part (so it can be length x width for some of our parts).

Is there a way in the Bill of Operations (BOO) DMT to record Minutes per Sq Inch or Minutes per Lineal inch to get the ProdStandard to populate correctly. I’ve thought maybe there’s a way using the StdFormat of Operations per Minute “OM” or Minutes per Piece “MP” and then maybe a combination of using other fields such as QtyParent or OpsPerPart, or QtyPerCycle.

Any ideas or solutions?

Thanks,
Tom

1 Like

It sounds like you want to use the Production Standard and Production Standard Format values on the BOO for the part.

image

The format you would most likely want to use here is Pieces/Minute. It is important to note in this case the term Pieces is not referring to any specific UOM, rather the UOM for the part/production quantity on the job.

4 Likes

Completely agree with @hackaphreaka. But want to add that this can get tricky. We do almost the exact same thing as you, and would love our own “UOM” for Prod Std. Each of our operations is either making a piece to go into the assemble, or assembling, or cleaning/packaging. In our first two operations, our Prod Std is pieces per minute for that thing we are making - not the finished good. The remaining operations are based on the assembled finished goods UOM.

We sue the configurator, so its rules take some calculated inputs, looks up factors in a UD table and writes the adjusted Operation’s Prod Std to each operation.

3 Likes