Licensing in Blueprint
Blueprint Products
The Blueprint platform is made up of two main technologies:
- Blueprint Conversion Technology
- Blueprint Extraction Technology
Use of these technologies is licensed through Blueprint Products, which make parts of these technologies available for a specific purpose. Refer to the product feature sheets (linked below) for a listing of specific features in each product.
Product | Technology |
Parts of Blueprint’s Conversion Technology to convert legacy RPA code to Microsoft Power Automate Desktop | |
Parts of Blueprint’s Conversion Technology and all of Blueprint’s Extraction Technology to support understanding, analysis, migration estimation, improvement, monitoring, and lifecycle management of RPA automations | |
Blueprint Suite | All of both technologies |
Blueprint Product Licensing
- A Blueprint license grants use of a Blueprint product for a specific number of RPA bots for a specific amount of time. Example: A user may purchase a license to use Blueprint Assess for 50 bots for 1 year. There is no limitation on the number of users in any Blueprint product.
- Blueprint licensing follows a ‘consumption’ model. When a license is used for a bot is it considered to be ‘consumed’. The license cannot be transferred to a new bot, and deleting the bot will not ‘release’ the license.
- When a license is consumed for a bot, all features of the licensed product can be used for that bot for the license term, including re-import of a bot (e.g. when it changes in the source RPA tool).
Definition of a Bot for Licensing Purposes
Regardless of the RPA tool from which Blueprint imports data, it considers a bot to be all the code from the execution starting point (the Main module) through all the modules it calls as part of execution (a Call Tree or Dependency Tree).
To translate what this means into the language of the RPA tools Blueprint supports:
When working with data from this RPA Tool | A Blueprint “Bot” means: |
UiPath | The Main xaml in a UiPath Process along with all other xamls being referenced. |
Blue Prism | The Main page in a Blue Prism Process along with all other process and object pages being referenced. |
Automation Anywhere | Root taskbot (i.e. a taskbot not called by any other taskbot), along with all other taskbots being referenced |
Power Automate Desktop | A desktop Flow |
Consumption of Licenses
See Activation and License Consumption for more information about how licenses are consumed in Blueprint.
Tracking License Availability and Use
As previously mentioned, Products are the way Blueprint licenses use of its technology. For example:
- When an organization purchases the Blueprint Migrate product, they are purchasing a time-limited license to use the Migrate part of the Conversion technology for a specified number of bots.
- When an organization purchases the Blueprint Assess product, they are purchasing a time-limited license to use:
- The Migrate Dashboard part of the Conversion technology and
- The Analyze part of the Extraction technology
See table below for a summary.
Technology | Blueprint Conversion Technology | Blueprint Extraction Technology | |
Licenses: | Migrate | Migrate Dashboard | Analyze |
Product: Blueprint Migrate | #Bots | - | - |
Product: Blueprint Assess | - | #Bots | #Bots |
This information is found in Blueprint’s License reporting within Settings:
- Click the hamburger menu in the top left and select Settings
- Select System Reports
- Review the tab called License & Activity Reporting. In this section, three license types will be displayed:
- Migrate License Status
- Analyze License Status
- MigrateDashboard License Status
Each section displays:
- Total licenses available
- Total licenses used
- Expiry date
Users may download a report of all licenses used by clicking the License Consumption Report button in each applicable section.
For more information on using this report, see License and Activity Reporting.