If you have ever managed a busy design office, you know firsthand that without a rigid set of rules, drawing files can quickly descend into chaos. Missing fonts, erratic line weights, rogue dimension styles, and scattered support files are the bane of any draughtsperson’s existence. Understanding exactly how to standardise BricsCAD across a CAD team is the ultimate key to achieving consistent output, reducing errors, and onboarding new staff members with ease.
Whether you are upgrading from legacy software or simply tidying up your current workflow, standardisation ensures everyone pulls in the same direction. In this comprehensive BricsCAD deployment guide, we will explore everything from network licensing to user profiles, ensuring your transition to a unified drafting environment is as seamless as possible.
Before diving into the technical mechanics, it is worth asking: why implement CAD standards in BricsCAD in the first place? When multiple users access different blocks, layer structures, and plotting configurations, the integrity of your drawing output suffers. By enforcing a single source of truth, you eliminate time wasted on formatting.
Establishing robust BricsCAD CAD standards helps make drawings more consistent by controlling templates, support files, plot styles, user profiles and standards checking. BricsCAD CAD Standards can associate DWS standards files with DWG files and check layers, linetypes, text styles and dimension styles. It streamlines drawing reviews, minimises plotting errors, and drastically reduces the time spent searching for the correct blocks.
A successful BricsCAD enterprise deployment starts long before any software is installed on a user’s machine. The preparation phase is all about gathering your existing resources and laying the groundwork for your network.
Migrating Legacy CAD Standards to BricsCAD Chances are, you already have a wealth of resources from your previous software. Migrating legacy CAD standards to BricsCAD can be done by copying supported custom files into the appropriate BricsCAD folders or support paths. Gather your existing .dwt templates, .ctb and .stb plot styles, .lin linetype files, .pat hatch pattern files and AutoLISP .lsp routines. AutoCAD encrypted VLX and FAS LISP files cannot be loaded directly by BricsCAD and must be handled separately. Place these into a neatly organised, central staging folder on your network drive before proceeding.
Network Licensing Infrastructure If your organisation uses shared network licences, properly configuring the Octave Network License Server is essential for making those network licence seats available to client machines. Setting up the Reprise License Manager (RLM) on a central server allows your company to pool network licences.
When BricsCAD launches on a client computer, it requests a licence seat from the Network License Server and returns that seat when BricsCAD closes. This avoids activating separate standalone licences on each workstation where network licensing is used.
When it comes to a large-scale BricsCAD team rollout, manually installing the software on every individual machine is an outdated and inefficient approach. Modern IT environments require automation.
Automating BricsCAD Deployment for IT Administrators To save hours of manual labour, system administrators should look into automating BricsCAD deployment for IT administrators. Using endpoint management software (such as Microsoft Endpoint Configuration Manager or PDQ Deploy), you can push the software directly to user machines across the network.
To achieve this without disrupting your team’s workflow, you will need a BricsCAD silent installation guide for teams. By utilising standard MSI command-line parameters, you can install the software invisibly in the background.
A command such as msiexec /i “BricsCAD-V26.1.05-1-en_US(x64).msi” /qn /norestart performs a silent Windows installation without user interaction or an automatic restart. For network licensing, add the documented licence server parameters, such as BRXLICENSESERVER=”port@host”, where required.
With the software installed, it is time to establish the drafting environment. The goal is to make new drawings follow company policy when they are created from the approved template and use the approved support, plotting and standards files.
Creating a BricsCAD Master Template The cornerstone of any drafting team is the .dwt template file. Dedicate time to creating a BricsCAD master template that contains all your essential pre-loaded data. Your standard BricsCAD templates should include company title blocks, standard text styles, dimension styles, and multi-leader setups. Having an agreed-upon starting point instantly prevents users from going off-script and creating bespoke styles.
Plot Styles and Layer Conventions Equally important is standardising BricsCAD plot styles and layer configurations. Ensure your template contains your standard layers, assigned colours, linetypes and lineweights. For UK BIM information management, reference BS EN ISO 19650 where contractually required. BS 1192:2007+A2:2016 is withdrawn and superseded by BS EN ISO 19650 1 and BS EN ISO 19650 2, although it may still be relevant where an existing contract specifically requires it.
Accompany this by placing your company’s custom .ctb or .stb files in a shared network folder. This helps produce consistent plot output, provided the drawing uses the same CTB or STB plot style table, the same page setup, the same printer or PDF configuration, and the Plot with plot styles option is enabled.
Unified System Variables Do not overlook the benefits of unified CAD system variables. Variables like MEASUREMENT (ensuring the drawing is metric rather than imperial), INSUNITS (for block scaling), and LTSCALE heavily dictate how a drawing behaves. Set these variables in the approved template and, where required, reset them through a controlled LISP routine. MEASUREMENT, INSUNITS and LTSCALE are saved in the drawing, so template based control applies to new drawings created from that template and does not by itself lock existing drawings.
The most common mistake CAD managers make is allowing users to keep standard blocks, palettes, and routines saved on their local C:\ drives. When updates occur, local files quickly become outdated, leading to disjointed outputs.
Centralising Search Paths The remedy is centralising BricsCAD support file search paths. Create a read-only directory on your company server (for instance, Z:\CAD_Standards\BricsCAD\). Inside this directory, create subfolders for Blocks, Templates, Plot Styles, LISP routines, and Tool Palettes.
Within BricsCAD’s Settings dialogue, configure the relevant file paths for each file type. Use SRCHPATH for support files such as fonts, customisation files, plug ins, drawings to insert, linetypes and hatch patterns. Use TEMPLATEPATH for template drawings. Store plotter configuration files in PlotConfig and plot style files in PlotStyles, or configure those locations through the relevant BricsCAD file path settings.
Synchronisation Between Machines If you have a hybrid workforce that works from home without constant VPN access, you might be wondering how to sync BricsCAD settings between computers. For remote users without constant VPN access, a managed file synchronisation approach can be used, but it should be tested for path consistency, file locking, version control and offline access before it is adopted as a CAD standard.
Map the support file search paths to the local synced cloud directory. When the CAD manager updates a block or plot style in a synchronised standards folder, propagation to users depends on the chosen synchronisation system, user connectivity, permissions and conflict handling. This should be verified before relying on it for production CAD standards.
LISP Routines and Tool Palettes Custom commands and automated tools dramatically increase productivity. Managing enterprise BricsCAD LISP routines involves keeping your .lsp files in your central network folder and using an on_doc_load.lsp file. An on_doc_load.lsp file can be used to load company LISP routines when drawings are loaded. Octave documents that on_start.lsp and on_doc_load.lsp are loaded per session by default, and can be loaded for each drawing when ACADLSPASDOC is set to 1.
Similarly, distributing BricsCAD custom tool palettes ensures everyone has quick, visual access to company-approved blocks and hatch patterns. By authoring a master Tool Palette, exporting the palette, and saving the associated block source files in a controlled location, you can distribute a consistent palette setup. BricsCAD can import palette files in ATC, BTC and XTP formats.
You have migrated your files, installed the software, built the templates, and centralised your paths. The final step is capturing the BricsCAD environment settings that belong in a user profile and distributing that profile alongside the controlled support files, templates, plot files and standards files. User profiles are one part of the deployment package, not the whole package.
Profile Management For users familiar with AutoCAD style profile workflows, BricsCAD provides its own User Profile Manager, which can create, copy, delete, import and export user profiles. BricsCAD user profiles can be exported to .arg files and imported on another computer. A BricsCAD profile stores many drawing environment settings, including the main CUI file, current workspace, registry saved system variables and user preferences, default plot settings, recent paths, status bar settings, Properties panel settings, toolbar and menu configuration, and worksets.
Exporting and Distributing Following BricsCAD user profile manager best practices involves configuring a single “Master Machine” exactly how you want it. Once the support paths are pointing to the server, the crosshairs are configured, and the interface is stripped of unnecessary clutter, navigate to the Profile Manager.
By exporting BricsCAD user profile .arg files from this master machine, you generate a profile file that contains the BricsCAD profile settings documented by Octave. It should be distributed together with the controlled templates, support files, plot files, CUI files and standards files used by that profile. You can then place this .arg file on your network drive.
When new users open BricsCAD for the first time, they simply navigate to the Profile Manager and import your company’s master .arg file. Alternatively, your IT department can use a desktop shortcut with the /P command line switch. BricsCAD can start with a named user profile, and if the /P argument is an .arg file, that .arg file is used to initialise the profile settings on first run.
Learning how to standardise BricsCAD across a CAD team does not have to be an overwhelming prospect. By taking a methodical approach that includes legacy file migration, silent installation, controlled support paths, approved templates, plot configuration, CAD Standards files and managed user profiles, you create a more consistent and maintainable BricsCAD environment.
Investing the time upfront to build strict company standards ensures that your draughtspersons spend less time formatting and troubleshooting, and more time doing what they do best: designing and delivering high-quality, accurate drawings.
Question: What’s the quickest way to migrate our existing CAD standards into BricsCAD? Short answer: Collect your existing standards (templates, plot styles, line types, hatch patterns, and LISP) and place them in a clean, central network folder. BricsCAD natively supports common industry file types, so you can bring in .dwt, .ctb/.stb, .lin, .pat, and custom .lsp files directly. Start by staging these in a well-organized server directory so they’re ready to reference during deployment.
Question: How can IT deploy BricsCAD to many machines without interrupting users? Short answer: Use your endpoint management tool (e.g., Microsoft Endpoint Configuration Manager or PDQ Deploy) and perform a silent MSI install. A typical command is: msiexec /i “BricsCAD-Vxx-en_US.msi” /qn /norestart. This installs BricsCAD in the background with no user prompts, saving time and avoiding workflow disruption.
Question: What should go into our BricsCAD master template, and which system variables matter most? Short answer: Build a .dwt that includes your title blocks, text styles, dimension and multileader styles, standard layers (e.g., BS 1192/ISO 19650 naming) with predefined colors, linetypes, and lineweights. Store your .ctb/.stb plot styles on a shared network folder and reference them from the template. Set key drawing saved variables such as MEASUREMENT, INSUNITS and LTSCALE in the approved template, and use controlled LISP only where you need to reset or validate them. These settings apply to drawings that use those values and do not guarantee identical behaviour or appearance across all files.
Question: How do we centralize and keep support files in sync for both office and remote staff? Short answer: Create a read-only server directory (e.g., Z:\CAD_Standards\BricsCAD) with subfolders for Blocks, Templates, Plot Styles, LISP, and Tool Palettes, then point BricsCAD’s support file search paths to these locations. For hybrid or remote users without constant VPN access, a managed local synchronised standards folder can be considered. Test path consistency, permissions, sync timing, conflict handling and offline availability before using it for production support files, templates or plot files.
Question: What’s the best way to deploy LISP routines, tool palettes, and user profiles company-wide? Short answer: Keep .lsp files in a controlled support folder and use on_doc_load.lsp where appropriate. Octave documents that on_start.lsp and on_doc_load.lsp are loaded per session by default, and can be loaded for each drawing when ACADLSPASDOC is set to 1. For tool palettes, author a master palette, export the .xtp, and store it with the source blocks on the network so everyone sees the same drag-and-drop content. To standardise the user environment, configure a master workstation, then export a BricsCAD .arg profile for the profile controlled settings. Distribute that profile together with the controlled support files, templates, plot files and standards files it references. DDistribute it for users to import via Profile Manager, or have IT launch BricsCAD with the /P switch. BricsCAD can start with a named profile, and an .arg file supplied to /P is used to initialise profile settings on first run.
