[Doug McLean]

Chances are, someone else has opened it previously and their custom columns are already with the PDF.

To save yourself some effort, you can set up a quick macro to import your custom columns. (If you have Extreme/ Complete)

[Doug McLean]

You will need a second area markup, but you won’t need another Column.

You could do a second custom column, ‘material 1’ ‘material 2’ but I’m not too sure how any value associated with the material would play out in that scenario.

Run an experiment

[Doug McLean]

I did eventually find something and you can’t. If you open it via a hyperlink, it will always open in the browser

[Doug McLean]

Hey Nic, all great questions.

#1 yes. Click on the end node to select the tool, Rt. Click (right click is your very best friend btw) and then click Resume.

#2 Try applying your custom columns first. If that doesn’t work, check your tools to see if they have built in layers

#3 You can change the column layout (pretty much works like Excel in dragging columns) and you can change the sort order, but that’s about it. You can also set custom filters if that works for you

#4 Open the Legend Properties. You can do all of that there.

#5 in a word no…but… you can apply the same scale to multiple pages at the same time.
I have a trick for this to select them quickly. It should be under the Tips and Tricks forum.

Hopefully I helped a little

[Doug McLean]

the real key to using Power Query is a consistent output of data.

Take the time to learn how to set up a proper BatchConfig output file with exactly what you want.
I talked about planning properly in my presentation, because that is the very first thing you need to do. Figure out what you want to do, figure out where you are, then figure out how to get there.

I have one slide in my presentation that says how data without context is just noise. We can generate so much data now in construction that we have to learn how to filter out all of the noise and get to what we really want.

[Doug McLean]

I put it up on our TV in the Estimating office and had my team watch it.

More than one note was taken. Even by me.

Liz mentions this herself, if she can teach even an advanced user something, she’s done well.

[Doug McLean]

I’ve mentioned before that there are some issues with working with Sets on the cloud (in both SharePoint and Studio) but the solution is almost too simple. I’m actually a little ticked at myself for not thinking of doing this sooner because I actually USE this workflow at times.

Sets allows you to create a drawing log really easily. Once the Set is created, simply make that and then pin the log to your file access panel. That’s it. Incredibly simple right? You can just use the drawing index page, if there is one, but a full log does have the potential to be more useful if you want to see revisions easier.

When you go to load a Set from the DMS toolbar, it takes quite a while, and I’ve noticed that the files don’t automatically try to ‘check out’ when opened from a hyperlink. If I do this from the drawing log… they ‘check out’ themselves. Plus you’re not opening the whole set, you’re really only opening the drawing log.

SharePoint doesn’t recognize the .bet file that Revu creates for a Set, so you can’t open it directly from SharePoint, like you can with a regular PDF. The drawing log is a regular pdf file, so it opens.

I’m kicking myself for not thinking of this earlier.

[Doug McLean]

My whole process is this

1) Remove all Viewports

2) Move any markups I wish to keep to their own layer

3) Flatten any/ all AutoCAD markups

4) Create new page labels

5) Apply Custom Columns and Statuses

We find we may have to do this if the person who sent us the drawings has done this as we want our own stuff. We may have to adjust our custom columns per the job as well. Its also a whole lot easier to do this as one drawing package

6) Use Headers and Footers to apply a Drawing Package tag

7) Hyperlink

8) Break into individual pages

9) Create a Set

10) Create a Drawing Log (if its a larger drawing package with multiple disciplines)

This actually works better in the long run when you work on something like SharePoint

[Doug McLean]

If designers really wanted to help us out, they should go through the process of getting a proper budget.
I see far too often, where the designer has this amazing vision, but they have ABSOLUTELY NO IDEA of the cost ramifications therein.

What this now does is force a race to the bottom with VE options, with material changes, with a whole lot of extra work for no reason whatsoever.

So before they fall in love with a design, and then sell it to the owner, get some cost ideas together. Work with who ever is going to build it and try to figure out the best and cheapest way to do it.

[Doug McLean]

Maybe think about adding the Status column.

I know you’re new, but you should learn about this wonderful column and what it can do.

If your Estimating team is making the markups, then build your Custom Status to default to “Estimator Review”. Then the PM can update the status later to “PM Review”.

You’ll also be able to sort by Status in the markups list

[Doug McLean]

I was also thinking maybe multiple legends might be a solution.

[Doug McLean]

NIc

Power Query will allow you to take your data, and then reconfigure it just about any way you want it. It’s really nothing more than a series of pre defined steps to wash the data.

If you want the guru’s, check out guys like Mike Girvin @Excelisfun or Leila Gharani @XelPlus on YouTube. These guys will get you started. There are many others out there as well.

As Troy mentioned, I’m doing my XCON presentation in June, so make sure you register for it. I’ll be doing some of it live, so you’ll get to see it in action.

[Doug McLean]

its (Painfully) SLOWLY becoming a reality

[Doug McLean]

just click the Help files Help> Help and Studio will be right on the first screen.

Its included in your Revu license, so you don’t even have to buy anything new.
There are probably even a few videos right on this site you can explore as well.

[Doug McLean]

This is one of the very first things I learned in Bluebeam.

It was told to me by a guy named John Davenport who works for our US partner.