Skip to main content

Bluebeam Revu 21

warning

The instructions on this page are for Open iT Core Client version 10.2.580 and later. If you're using earlier versions, please refer to this configuration guide for the appropriate instructions.

Introduction​

Open iT supports Bluebeam Revu 21 usage by polling the license servers at regular intervals to get the current status of its license use and availability.

For this collection, the data source is through an API. The data collector/preprocessor initiates the license status utility every hour using a 5-minute sample interval, triggering the data collection process. The license status utility requests the current license usage data from the license manager portal. After the license manager portal provides the requested data, the license status utility passes this information to the data collector/preprocessor. The data collector/preprocessor processes the data, preparing it for transmission. Finally, the preprocessed data is sent to the Core Server every night, according to the client's timezone, for further storage, completing the license usage data collection and processing.

License Manager Utility Polling Workflow through API

License Manager Utility Polling Workflow through API

This will produce the following aggregated data types used for historical reporting:

note

Open iT also supports this in the License Monitor and License Monitor Portal; however, since the data gathered from the portal lists Enterprise plans under Complete and does not explicitly list Enterprise Overage, usage under the Enterprise Overage plan is counted under the Complete plan and will show as zero (0) in the real-time report.

The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.

warning

Apply the configurations shown in the Open iT Core Client.

Requirements​

Setting up Bluebeam Revu 21 Data Collection​

These are the required steps to set up data collection from the Bluebeam Revu 21 portal.

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  3. Set the username, password, and region, run the command:

    Command Syntax
    genlicutil2 Bluebeam21 --config
    note

    If you need to collect data from more than one Bluebeam Revu 21 account, use the --account parameter when running this command. This allows you to create separate credentials for each account.

    Command Syntax
    genlicutil2 Bluebeam21 --config --account <account_name>

    where <account_name> is the name of the account you want to use for data collection.

    Example
    genlicutil2 Bluebeam21 --config --account acct1

  4. Type in the username when prompted.

    Example: Entering Username
    Enter username to use: sample-config@company.com

    then press Enter.

  5. Type in the password when prompted.

    Enter password: **********

    then press Enter.

  6. Type in the server region when prompted.

    Enter region: United States

    Possible values are:

    • Germany/Deutschland
    • United States
    • Australia
    • United Kingdom
    • Sweden/Sverige

    then press Enter.

note

Open iT saves the hashed Bluebeam Revu 21 credential file, Bluebeam21, in the OpeniT directory, which is by default in C:\ProgramData\OpeniT. When you use the --account parameter, Open iT appends the account name to the credential file (for example, Bluebeam21_acct1). This allows each Bluebeam Revu 21 account to maintain its own credentials within the same directory.

Configuring Data Collection​

These are the required steps to activate collection of usage data.

  1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and back up the licpoll.xml configuration file.

  2. Open a command prompt with Administrator level privileges.

  3. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  4. Once in the directory, copy the object node genericlicense-sample and rename it to your desired name. In this example, we will use genericlicense-bluebeam21. Run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-sample=>licpoll.license-types.genericlicense-bluebeam21"
    warning

    Element names cannot contain parentheses ( or ) because they are not valid for XML element names.

  5. Activate the collection of Bluebeam Revu 21 data, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-bluebeam21.active=true"

  6. Set the status command, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-bluebeam21.status-command=<bin_dir>\genlicutil2.exe"

    where <bin_dir> is the path to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin.

    Example
    openit_confinit -c "licpoll.license-types.genericlicense-bluebeam21.status-command=C:\Program Files\OpeniT\Core\bin\genlicutil2.exe"

  7. Set the arguments to the status command, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-bluebeam21.status-command.arguments=Bluebeam21"
note

If you have multiple Bluebeam Revu 21 accounts, repeat the configuration steps to create additional object nodes for each account. Use a unique name for every node (for example, genericlicense-bluebeam21_1, bluebeam21_2, and so on) and specify the corresponding account in the status-command arguments.

Example for acct1
openit_confinit -c "licpoll.license-types.genericlicense-bluebeam21_1.status-command.arguments=Bluebeam21 --account acct1"

This ensures that Open iT collects data separately for each configured Bluebeam Revu 21 account.

  1. Run the following command to update the configuration files:

    Example
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

Refer to the Bluebeam Revu 21 Data Collection Configuration table to learn more about Bluebeam Revu 21 configuration in licpoll.xml.

Object NameAccepted ValueDescription
activeBoolean (true or false)Setting this to true activates Bluebeam Revu 21 usage data collection.
typeString (i.e., GenericLicense)The license manager type.
intervalTimespan (e.g., P30S, P5M, P1H)The span of time between each polling round (it is recommended to set a value no less than P1M).
offsetTimespan (e.g., P30S, P5M, P1H)The span of time the aligned poll time decided by interval is shifted.
product-nameString (e.g., %host%;bluebeam)This object is defined if a vendor license name other than the default %host%;bluebeam will be used.
license-serverString (e.g., WIN-HOST01)The license server name.
status-commandFileName (i.e., ${OpeniT. directories.bin}/genlicutil2.exe)The binary used to obtain status from the license manager.
status-command.argumentsString (e.g., Bluebeam21)The arguments used for the status command.
Bluebeam Revu 21 Data Collection Configuration

Verifying Data Collection​

After configuration, you can verify that the data is collected by following these steps:

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  3. Run the command:

    Command Syntax
    openit_licpoll -# 1

  4. Verify that the temp directory, which is by default in C:\ProgramData\OpeniT\Data\temp, contains a LicPoll directory containing .data and status-*.log files.

  5. Verify that the Bluebeam21.token file exists in the OpeniT directory, which is by default in C:\ProgramData\OpeniT.

Sample Reports​

Historical Reports​

Max Available vs Max in Use​

This sample report compares max in-use licenses against max available licenses.
It offers several key benefits:

  • Optimized License Allocation - helps ensure you are not over-purchasing licenses you don't need or under-provisioning.
  • Cost Savings - identifies opportunities to downgrade or redistribute licenses, reducing unnecessary expenses.
  • Usage Trends & Capacity Planning - shows peak usage patterns, allowing better forecasting for future needs.
  • Avoiding Service Disruptions - helps prevent situations where users cannot access software due to reaching the license limit.
  • Compliance & Audit Readiness - provides a usage record to ensure compliance with vendor agreements and avoid penalties.
  • Performance & Productivity Insights - helps assess whether certain teams or departments are under-utilizing or over-utilizing software.

Max Available vs Max in Use Licenses per Feature

Max Available vs Max in Use Licenses per Feature

Feature Elapsed Time per User​

This sample report gives you helpful insights into software use, performance trends, and user behavior.
It offers several key benefits:

  • User Efficiency Analysis - tracks how much time users spend on specific features to help assess productivity.
  • Identifying Workflow Issues - highlights any delays or inefficiencies in processes that could be improved.
  • Usability & UX Insights - points out features that take longer to use, which could indicate design or functionality improvements.
  • Training & Support Guidance - helps identify users who might need extra training to use a feature more effectively.
  • Compliance Tracking - makes sure users are spending the right amount of time on regulated tasks.
  • Resource & License Optimization - finds underused features or areas where too much time is spent, helping with better resource allocation.

Feature Elapsed Time per User

Feature Elapsed Time per User

Real-time Report​

This sample report shows a drilled-down feature view of the assigned licenses in use and the licenses available.

Drilled Down Feature View

Drilled Down Feature View

Next Steps?​

Renaming Vendor License
Renaming Features
Create and Add Report
License Monitor