[David Cutler]

This sounds like a good challenge for @lizlarsen and her Javascript tools…

[David Cutler]

I like the concept of rounding each piece @troy-degroot . I think I’d want to have a total both ways (straight measurement and rounded) so I would be able to better understand the waste that is being incorporated with the rounding. One could even incorporate a simple formula to calculate the waste in each run so you could avoid “over compensating”.

For example if you had 4 each 25 foot runs (100 lf neat length) you wouldn’t want to buy 2 each 20 ft sticks for each run (160 lf of pipe) as you would most likely have an extra 40 lf (or more) left over. At the same time I don’t know that I’d order exactly 100 lf either!

The other example would be 4 each 35 foot runs (140 lf neat length). I don’t think my superintendent would be happy if I ordered exactly 7 sticks and told him he had to use a bunch of 5 ft cutoffs to finish the last run. Here I probably would want 2 each 20 ft sticks per run so I’d order 160 lf.

Great discussion!

[David Cutler]

Always interesting to hear about the issues in other portions of the industry @Doug McLean

Do you make your allowances for waste? In your takeoff, in your data washing, or in your estimating system?

For example we measure storm drain piping from the center of the drainage inlet to the center of the next drainage structure. We then total all of the takeoff for a certain size – 18″ High Density Polyethene Pipe (HDPE) and enter that into our estimating software. Once it is entered – say 950 LF, we use that quantity for calculating our production. For purchasing we calculate and apply a waste factor so that we purchase 960 lf as the standard stick of pipe is 20 ft long. This can throw off your “typical” unit prices if say you are pricing a 22 ft long run as now you have 40 ft of pipe material cost in your item. Buying 2,000 lf for a 1,996 lf long run not so much.

Curb we run our takeoff and typically round up to the nearest 5 ft when we enter the item into the software.

Stone/Asphalt we typically round to the nearest 5 square yards.

Curious to learn how others handle this.

[David Cutler]

Coming up on a year since your post @Jeff.Collins . Have you made any progress promoting digital reviews?

[David Cutler]

While that sounds possible @Vince the “status” appears to be a running record of all statuses that have been applied with the most recent status being what would be displayed. So while your “current” status would be “blank” you’d still have the previous statuses listed in the column.

[David Cutler]

Seems as if that the ability to “clear” or “reset” a status should be a setting that you select with your document – similar to the way you can select to make “unflatten” available.

Not being able to change or delete a status seems to be very unforgiving and inflexible – not something Revu is known for. 😕

[David Cutler]

I still have to insert the USB receiver on mine @troy-degroot . It’s a step above a corded mouse, though not a very tall one… 🤣

[David Cutler]

That’s a good hotkey to know @ChrisRiley – I have my “Rectangle” tool preset to a borderless yellow highlight. Using the “R” hotkey to launch the tool will be a nice timesaver.

[David Cutler]

Is there a way to “undo” a status change @bluebeamsupportuchapter2-com ? I started toying around with status settings on a few of my takeoff items and now I don’t seem to be able to remove them…

[David Cutler]

That sounds incredibly frustrating @ChrisRiley , have you reported the issue to Bluebeam?

[David Cutler]

I just looked up the keyboards and mice that you folks are running with and I think I’m running with the equivalent of a dull pencil and recycled yellow pad! 🤣

[David Cutler]

Good to know @Doug McLean ! I never would have thought to look for them…

[David Cutler]

This could be a new competition for MCR. “I can complete that takeoff with X tools.”

[David Cutler]

It’s all part of the matrix….😎

[David Cutler]

I’m sure using the #Revunitroskit @Doug McLean could remove the door from the wall area @Vince and @troy-degroot

@lizlarsen could probably write some code to remove the door quantity too…

How about window area?

😎