Equipping a design or engineering department with top-tier Computer-Aided Design (CAD) software is a significant investment. As your organisation grows, ensuring every draughtsperson, architect, and engineer has access to the tools they need, without overspending on unused software seats, becomes a strategic balancing act.
If you are looking to streamline your software overheads while maintaining maximum productivity, getting to grips with how your team accesses their software is paramount. This comprehensive guide covers everything you need to know, with BricsCAD Network Licensing Explained for Teams in full detail. We will explore how to transition from individual setups to a centralised system, the financial benefits of concurrent usage, and the technical steps required to get your server up and running. We will also clarify how a BricsCAD floating licence and a BricsCAD roaming licence work within a BricsCAD network licence, coordinated by a BricsCAD licence server to support efficient BricsCAD team licensing.
For growing businesses, managing individual software installations quickly becomes a logistical nightmare. When evaluating your software infrastructure, the first question most IT managers ask is: what is the difference between single and network license models?
A single (or volume) standalone licence is tied directly to an individual workstation. If you purchase ten standalone licences, they are activated on ten specific computers. If an eleventh person needs to use the software, they simply cannot, even if five of your licensed users are on annual leave.
Conversely, a BricsCAD network licence operates on a concurrent usage model. The licences are held centrally on a server and distributed on demand. When weighing up a BricsCAD network vs standalone license, the network option provides unparalleled flexibility. If you own ten network licences, you can install the software on fifty different machines. As long as no more than ten users attempt to open the application at the exact same time, everyone has the access they need.
This flexibility forms the foundation of modern BricsCAD team licensing, allowing organisations to cater to shift workers, part-time staff, and multi-disciplinary teams without purchasing a dedicated seat for every single employee.
At the heart of this system is the BricsCAD floating licence. When a user launches the application on their local machine, the software pings your central server to request a seat. If one is available, the software opens, and the pool of available licences decreases by one. The moment the user closes the software, the licence “floats” back to the server, instantly becoming available for a colleague. This dynamic allocation is the cornerstone of reducing CAD software costs with concurrent licensing, as it ensures your software is working hard for your business every hour of the day.
But what happens when a team member needs to visit a construction site or travel for a client meeting where internet access is unavailable? This is where the BricsCAD roaming licence comes into play.
A roaming licence allows a user to “check out” a floating licence from the server for a specified number of days. While roamed, the licence is deducted from the server’s available pool, allowing the user to run the CAD software entirely offline. Once the specified period expires, or the user manually returns it upon reconnecting to the network, the licence goes back into the central pool. This ensures uninterrupted productivity for staff in the field while maintaining centralised control.
Transitioning to a network-based infrastructure is not just an IT decision; it is a financial strategy. By pooling resources, companies can significantly reduce their software procurement budgets.
When evaluating how to proceed, you will likely encounter the debate between perpetual vs subscription network licensing models. BricsCAD is available with both perpetual and subscription licence types.
Whichever commercial model you choose, the benefits of floating CAD licenses for remote teams and in-house staff remain the same: you buy only what you actually use.
Transitioning to a concurrent model requires configuring a central server to manage the distribution of seats. Octave utilises the Reprise License Manager (RLM), a robust and industry-standard tool for managing software access.
Before beginning, you must ensure your chosen server meets the necessary specifications. Fortunately, the RLM software is incredibly lightweight. The BricsCAD license server system requirements dictate that the machine does not need to be a high-end graphics workstation. It simply needs:
Actionable Tip: Many firms successfully run their Reprise License Manager on a virtual machine (VM). Just ensure the VM’s MAC address is static, as your licence file will be tied to this unique hardware identifier.
The next step is the Octave network license manager download and installation. You can acquire the latest version of the RLM directly from the Octave website under the administration tools section.
Ensure you download the version appropriate for your server’s operating system. The installation process is a standard wizard-driven affair. Follow the prompts to install the manager into your preferred directory. By default, on Windows, this is usually located within the Program Files directory.
Understanding how to set up Octave network license manager correctly is vital for seamless operations. Once installed, the RLM runs as a background service.
To configure it:
This web interface will become your primary dashboard for managing floating CAD licenses for teams, allowing you to view active users, server health, and historical usage logs.
With the manager installed, you need to authenticate it with Octave. Learning how to activate BricsCAD network license server is a straightforward process, but it requires your unique licence key (found in your Octave account portal).
To ensure your client machines can securely request access, a proper Reprise License Manager configuration for BricsCAD is required. The RLM uses specific network ports to communicate. By default, it uses port 5053 for the primary licence server and another dynamically assigned port for the vendor daemon (the specific Octave service).
Actionable Tip: To prevent the ISV port from changing at startup, edit the licence file and add a fixed port to the ISV line in this format: ISV bricsys port=[port_number]. Do not use port 5054 for this purpose, because Octave documents 5054 as the RLM web UI port. Open port 5053 and the fixed ISV port in the server firewall, then restart the computer or RLM service.
Modern design teams rarely operate entirely from a single office. Sharing BricsCAD licenses across local network environments is simple, but extending that reach to remote workers requires a touch of basic IT infrastructure.
For employees working from home, they will need a secure way to communicate with your office’s central server. This is typically achieved via a Virtual Private Network (VPN). When the remote worker connects to the company VPN, their local machine behaves as though it is sitting in the office. The CAD software will query the server over the VPN, acquire a floating licence, and open normally.
This highlights one of the major benefits of floating CAD licenses for remote teams: you do not need to purchase separate software keys for your employees’ home computers and their office computers. They simply tap into the central pool wherever they are working, creating a highly agile and cost-effective working environment.
Once your server is live, the focus shifts to administration. Effectively managing floating CAD licenses for teams ensures that productivity bottlenecks do not occur during peak business hours.
The RLM web interface provides real-time data on who is currently using the software. However, for long-term strategic planning, monitoring CAD license usage for teams via log files is highly recommended. The RLM generates a report log that can be analysed to identify peak usage times, average session lengths, and instances of licence denial (when a user tries to open the software, but all seats are taken).
If you frequently experience licence denials, you may need to purchase additional seats. However, before spending more money, you should focus on optimizing license utilization with RLM.
You can set up an options file (bricsys.opt) within the server directory to enforce specific rules:
Implementing these rules ensures your existing BricsCAD licence server is operating at maximum efficiency before you commit to purchasing additional capacity.
Even with a flawless setup, occasional technical hiccups can happen. Knowing how to resolve them quickly will keep your team drawing and designing without frustrating downtime. Here are the most critical steps for troubleshooting BricsCAD network license connection issues:
To migrate a network licence to a new server, revoke the licence, activate it on the new server, shut down the licence manager on the old server and delete the old licence file. Octave notes that revocation is limited to two per key, and you should contact support if you cannot revoke the licence.
Transitioning your design department to a centralised infrastructure is a smart, scalable business move. As we have covered in this guide on BricsCAD Network Licensing Explained for Teams, the advantages extend far beyond simple convenience.
By understanding the key differences between standalone and network models, you can implement a setup that maximises your software ROI. Leveraging tools like floating and roaming licences ensures your team remains productive whether they are at their office desk, working remotely via a VPN, or offline on a construction site.
Through careful setup of the Octave Network License Manager, diligent firewall configuration, and proactive monitoring using the Reprise License Manager, IT administrators can create a frictionless experience for end-users. By embracing concurrent usage and actively optimising how your seats are distributed, your organisation can reduce unnecessary software expenditures while empowering your creative and engineering teams with the reliable access they require to excel.
Question: What’s the key difference between standalone and network (concurrent) BricsCAD licenses?
Short answer: Standalone licenses are tied to specific machines, 10 standalone seats can run only on 10 designated computers, regardless of who is available. A BricsCAD network license is concurrent: licenses sit on a central server and are handed out on demand. You can install BricsCAD on many machines (e.g., 50), and as long as no more than your licensed number (e.g., 10) run it at the same time, everyone gets access when they need it. This concurrency delivers flexibility and minimizes idle seats.
Question: How do floating and roaming licenses work, and when should each be used?
Short answer: A floating license is checked out from the server when a user launches BricsCAD and automatically returns to the pool when they close it, ideal for day-to-day work on the network. A roaming license is a temporary “check-out” for a set number of days so a user can work offline (e.g., on-site or in transit). While roamed, that seat is deducted from the pool; it returns automatically at expiry or when the user reconnects and returns it.
Question: What are the essential steps and settings to set up the Octave Network License Manager (RLM)?
Short answer:
Question: How can remote or home-based users access network licenses, and what about working completely offline?
Short answer: Remote users connect to the office network via a VPN; BricsCAD then contacts the license server as if they were on-site and checks out a floating seat, no extra keys per device are needed. For truly offline work (no VPN or internet), users should check out a roaming license for a defined period; the seat is held for them while away and returns to the pool at expiry or on manual return.
Question: How do we optimize usage before buying more seats, and what common issues should we be ready to troubleshoot?
Short answer: Use RLM’s reporting to track peak times, average sessions, and denials, then tune an options file (bricsys.opt): set timeouts to reclaim idle seats, reserve licenses for critical roles, and restrict roaming where it’s not needed. For troubleshooting: verify client connectivity/VPN and correct server name/IP; ensure firewall rules allow port 5053 and the vendor daemon port; if RLM won’t start, check logs for a host ID (MAC) mismatch and re-activate if hardware changed; if roaming fails, confirm it’s allowed in the options file and that the client has network connectivity and local rights to store the roaming token.
