nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bluebeam Community

Build connections with Bluebeamers around the world, discover what’s new, and make your voice heard.

Bluebeam Revu Tool Sets for CCTV, Access Control & Low Voltage Projects

SMC09

Hi everyone,

I work with low-voltage systems, including CCTV, access control, and structured cabling.

One challenge I've encountered is keeping Bluebeam markups, device schedules, and project closeout documentation organized across different installations.

To address this, I've developed a toolkit with:

32 CCTV tools
32 Access Control tools
32 AV / Data / Network tools
Excel templates for device registers, schedules, punch lists, and closeout documentation

The Bluebeam tools are in BTX format.

I'm interested in feedback from other Revu users:

How are you currently organizing your low-voltage Tool Chest libraries and project handover documentation?

Are there any specific tools or workflows you feel are missing?

For transparency, I've also developed a commercial toolkit around this workflow, but my main goal here is to learn from other professionals and improve it.

Thanks for any suggestions!

https://payhip.com/b/Q3gmo

Find more posts tagged with

Workflows

Tool Sets & Tool Chest

Tips & Tricks

Comments

Dhanush Kodi Raj

Hi SMC09

In my experience, one .btx per trade (CCTV, access control, AV/data) works best, kept in a shared Studio Project folder so my whole team pulls the same version. Bluebeam won't auto-sync an updated tool set otherwise.

For device schedules, I rely on Markups List custom columns (device type, location, IP/MAC, status), exported via Markups List Summary straight to CSV. That feeds my Excel register without re-typing anything.

The gap I keep running into: custom columns don't enforce naming, so "Camera" vs "CCTV Cam" drifts across installers on longer jobs. I also don't have a built-in way to reconcile a device change after I've issued the closeout PDF, the as-built record just goes stale from that point.

Thank You

SMC09

Thank you so much for sharing your experience and such detailed feedback! I really appreciate it.

You've highlighted two important challenges that many Bluebeam users face, especially on larger projects.

I actually have a NEXORA solution designed to address exactly these issues: standardized device naming and tracking equipment changes after project closeout.

It combines a structured device register, naming consistency checks, and an as-built change tracking system to help teams keep their documentation accurate and up to date.

I'd be really interested to hear your thoughts. Would a tool like this be useful in your current workflow?

Your feedback would be incredibly valuable. Thanks again for taking the time to share your experience!

Welcome!

It looks like you're new here. Sign in or register to get started.