Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Grant a PW SES License?
    • Sign In

    • State Not Answered
    • Replies 9 replies
    • Subscribers 61 subscribers
    • Views 892 views
    • Users 0 members are here
    • pw explorer
    • SES
    • Grant license
    • licensing

    Grant a PW SES License?

    jcallicott
    Offline jcallicott 11 months ago

    Greetings,


    I have a hypothetical that may or may nor remain so. I'm looking for information as to how best to grant use of PW to a user, as we have an external user we may need to grant a PW license to. 

    Back before the advent of SES licensing, we could specify in the “Administrative” settings for a user where they received their license from. Either the connected integration server, or the client’s integration server. This granted a PW Passport license that could be used with PW Explorer (Visas did not exist at the time, so it was much less expensive to do). The licenses for MicroStation or toher design software were unaffected. 

    These days, for an IMS account using an SES license, the license would be granted by creating a user account on our Bentley portal that the user could log into. In this case, we would set the user up to use a PW VIsa license as they need to be using CADD data. But assuming we did that, how would the user be able to bring their own MicroStation or ORD license to be used? They can only be logged into CC under one set of credentials, and if they login to CONNECTION Client using the account we give them, we would extend PW Explorer usage only - we would not want to grant them licenses for the design software. is this possible?

    Can anyone shine a bit of light on this? 

    • Sign in to reply
    • Cancel
    Parents
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Sep 30 2022 8:00 PM

      This is a bit of an ugly situation that is supposed to be resolved in an upcoming release (hopefully the next one, and hopefully soon).

      Currently what you can do:

      • Create an Entitlement Group in your User Management
      • Assign ONLY ProjectWise Explorer Client entitlement to this group
      • Put the accounts you create for these users in this group

      This is where it gets ugly for the users, in order to ensure they have a MicroStation/ORD license from their own company they should:

      • Login to Connection Client with their company's credentials
      • Open MicroStation/ORD and any other products they may need.
      • Go to the File menu > Tools > License Management
      • Verify the application is Activated
      • Go to Tools > Send Logs Now
      • Close all the apps.

      Login to Connection Client with credentials from your ProjectWise. Open ProjectWise and begin working.

      What happens here is MicroStation/ORD will use the activation from being logged into their corporate accounts for about 7 days while they connect to your projectwise. They can change their login back to their company account open Microstation/ORD again and the activation will renew.

      When our users have to do this with other companies we recommend they just make it a habit on Monday's to always renew their activations.

      They can also (if allowed by their company) check out a license from their company's license server before logging into ProjectWise. However this puts the license into use 24/7 and kills the advantage of license pooling. How expensive that would be for your company I'm not sure.  We typically only allow checkouts for about 7 days to cover people in the field so there isn't really an advantage to our users to do check-outs.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • jcallicott
      0 Offline jcallicott Tue, Oct 11 2022 12:17 PM in reply to Kevin van Haaren

      Kevin, thanks for your reply. I'm assuming it's key that the entitlement management we would set up for such users would use the exact same email address they're putting into CC, correct? That way, it would be possible through CC that their email is used to grant a PW license from one org (say, a company they don't work for) and license for MicroStation, et al from their own license pool. Am I understanding correctly?

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Tue, Oct 11 2022 12:47 PM in reply to jcallicott

      Actually the opposite, the emails must be different.

      When they login with the projectwise account, microstation will still try and get a license from your system. It will be denied because that email is only allowed an entitlement for ProjectWise.

      However the way Bentley's licensing works being denied a license doesn't block you from the product. Instead the product records it's usage locally and you can proceed normally -- for up to 7 days. When they login with their microstation email, before or after the 7 days of activation expire, and then open Microstation -- all that usage is reported to Bentley and the activation is renewed for another 7 days. That way their licensing takes into account actual product usage.

      Bentley's system is setup with 1 email address = 1 account. If you were to try to add an account using an email that already has an account with a different company it would not be allowed.

      Phil's suggestion of them using Virtuosity, i'm not sure all the ins and outs, but I assume it would add a license to that user's account on their company's system. In this scenario you would use their own company's email address as the IMS identity for their user account inside of ProjectWise. That would then be used for authentication, but not licensing.

      Other than cost to the other party ($260/year) the only reason you might not want to do this is if you want more control over some of the account policies like password changes or mandatory 2 factor authentication.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Tue, Oct 11 2022 12:50 PM in reply to Kevin van Haaren

      Ah crap, i misread the Virtuosity site, cost is $860/year for ProjectWise Explorer level access, the $260/year is ProjectWise 365 access.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • jcallicott
      0 Offline jcallicott Thu, Oct 20 2022 4:45 PM in reply to Kevin van Haaren

      Okay, dumb question: I see no option anywhere to assign use of PW Explorer to any group, nor assign entitlements per group. Bentley's currently posted instructions say once you get to Entitlement Management "In left navigation menu under Users and Groups icon select Allowed Access Group." This is not an option, so none of the steps past this one are possible. I cannot see an option to assign or limit ProjectWise Explorer use - it does not show in the list of Applications. Under Entitlements, I am unable to click my CSS. Do I have a rare eye disease? What am I missing? 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Oct 21 2022 12:33 PM in reply to jcallicott

      This is what I do:

      • User Management
        • Groups > New Group
          • Group Name
          • Turn Entitlement checkbox on
          • Set Entitlement Country/Region
          • Set Description (this is required, don't know why)
      • Entitlement Management
        • Set Region at top (defaults to Global)
        • Users & Groups > Entitlement Groups
        • Group created in step above takes awhile to show up, once it does:
          • Allowed Applications tab
          • Turn off include allowed applications from Region and Global
          • Search for application in search field*
          • Check applications to add and click + next to search field

      When I'm in Entitlement Management this is the menu I see on the left:

      Groups have to be created in User Management first, and it takes 10-15 minutes to show up in Entitlement Management

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Oct 21 2022 12:33 PM in reply to jcallicott

      This is what I do:

      • User Management
        • Groups > New Group
          • Group Name
          • Turn Entitlement checkbox on
          • Set Entitlement Country/Region
          • Set Description (this is required, don't know why)
      • Entitlement Management
        • Set Region at top (defaults to Global)
        • Users & Groups > Entitlement Groups
        • Group created in step above takes awhile to show up, once it does:
          • Allowed Applications tab
          • Turn off include allowed applications from Region and Global
          • Search for application in search field*
          • Check applications to add and click + next to search field

      When I'm in Entitlement Management this is the menu I see on the left:

      Groups have to be created in User Management first, and it takes 10-15 minutes to show up in Entitlement Management

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Children
    No Data

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies