[Alex Smith]

We have a company profile that is stored on a network drive, but gets deployed to the users rather than remapping the profile path to the network folder. It contains redlining tool chests that are network mapped, so updates to the tool chests get pushed automagically. We also have custom line styles that mimic our Revit lines that get network pathed, and we actually overwrite (via separate deployment) the default hatch pattern file to add a few custom ones (1% dots, 5% dots, steel, grout). The network folder has its permissions set so only I can write to it; it’s also set to read only so it triggers the pop up in Revu.

We have a custom status model that is built into the company profile too. Just a simple redlining one that has “Redline”, “Picked Up”, “Backchecked” as options. We don’t utilize the coloring options, our redline tool chests includes grouped text/shapes and snapshots from Revit and neither behave particularly well (see below). We also have a Studio tool chest that follows our internal color coding for redlining (red is a redline, blue is an engineering comment to an engineer/PM, green is a general comment).

I was the brave soul that asked about custom statuses in Studio Sessions on MCR. I’m thankful for all the discussion that occurred, though more than anything it just confirmed that Bluebeam has some work to do to make it easily implementable company wide. I have a hard enough time getting users to set the page labels or using the date as the file name prefix before uploading to a Session, you think I’m going to be able to have them do anything more??

I’m going to do some testing internally regarding custom statuses in Sessions as I’ve received feedback internally that more project teams want to use it. But ideally Bluebeam would implement the ability to have custom statuses (and probably other things, i.e. tool chests, custom columns), assignable on the back end of a Session PDF. That way, no matter how the PDF was processed before being uploaded, and no matter what Profile the (external or internal) user has set, all users have a single source of statuses available to them to use in that Session. I know a few years ago during either the Revu 19 or 20 beta program, there was a TON of discussion around requests for improvements regarding Studio Session. I even pitched a new tool concept that would be a “status setting tool”. Even though there was a lot of hype among the users, everything seemed to fall on deaf ears.

[Alex Smith]

I don’t mind the “full control” workflow. I’ve ran into issues in a Studio Session environment when I have just the custom status model checked on, but the architect is utilizing the built in “Review” statuses. It leaves me no way to change the statuses, so I have to go to a non-studio PDF and check the built in status model on. It’s just a little clunky at times.