Difference between an Entitlement and Product Billed


 

    Introductory Knowledge Landing Page

Subscription Analytics Landing Page

 

 

When reviewing usage reporting and invoicing, what you're seeing is known as the "Billed as" product; This could be the actual product used or simply a "Billed as" product representing legacy product usage, or a commercial offering bundle 

 

 

Where can I see the "Original Product" used?

 

The following Subscription Analytics Data Export (https://reporting.bentley.com/dataexport) reports will show both "Application" and "Original Product" -

 

 

For ProjectWise usage, the "ProjectWise Usage" report also shows "Original Product" (just listed as "Product") under Client Details.

 

 

Where can I see what products rolls up to a "Billed as" product?

 

The product rollup report can be accessed here - https://reporting.bentley.com/reports/productrollup

 

 

 

The "Billed as" product Relationship created by Product Consolidation

 

The most common scenario for a "roll-up" product to have multiple original products is when there's been a product consolidation. Older product functionality is rolled into a new product offering, but to ensure ease of transition Bentley creates the definition of the new product to include the legacy applications it replaces as child products. Below is a breakdown for OpenRoads Designer -

 

 

 

The "Billed as" product is a bundled commercial offering

 

 Sometimes Bentley offering are a commercial offering bundle. A common example is below, what products "roll-up" (for billing purposes) to Bentley Infrastructure Cloud ProjectWise - >

 

 

 

 

Access Control

 

For all intents and purposes, treat Entitlements at "face value"; Although the "Billed as" product may appear as an entitlement under the Entitlement Management Portal, when looking to control or restrict access to entitlements, you must use the "Original Product" entitlement not the "Billed as" entitlement.

 

Example -

 

If you wish to control access to "ProjectwWise Explorer Client" (via Default Access, User Exceptions, or Entitlement Group), you have to specify "ProjectwWise Explorer Client".

 

Even though "ProjectwWise Explorer Client" usage rolls up to "Bentley Infrastructure Cloud ProjectWise" for billing purposes, if you were to restrict access to "Bentley Infrastructure Cloud ProjectWise" you would only restrict "Bentley Infrastructure Cloud ProjectWise" (used for "Bentley Infrastructure Cloud" access), not any of the products that roll up to "Bentley Infrastructure Cloud ProjectWise".

 

 

What if I don't want to be billed for "Bentley Infrastructure Cloud ProjectWise" ?

 

If you wish to eliminate the possibility of being billed for "Bentley Infrastructure Cloud ProjectWise" (typically this is done to force users to use the lower tier offering, "Bentley Infrastructure Cloud Connect"), you have to block access to anything that could be billed as "Bentley Infrastructure Cloud ProjectWise", as we can see in the above product roll-up, this means blocking -
 

 

Bentley infrastructure Cloud uses a hierarchy; Entitlements are granted in the following order (if they are available)

 

Projects

  1. Bentley Infrastructure Cloud ProjectWise
  2. ProjectWise Validate (soon to be removed)
  3. SYNCHRO Control
  4. ProjectWise Engineer (soon to be removed)
  5. Bentley Infrastructure Cloud Connect
  6. ProjectWise Manage (soon to be removed)
  7. Bentley Infrastructure Cloud Essential

Build

  1. Bentley Infrastructure Cloud ProjectWise
  2. SYNCHRO Control
  3. Bentley Infrastructure Cloud Connect

 

A more reasonable request is "How do I force user's accessing Bentley Infrastructure Cloud to use Bentley Infrastructure Cloud Connect. For this you'd block -