My understanding is that Bentley are stopping support for MicroStation SS4 at the end of the year. Is that still correct?
Also I have seen somewhere that if we use CE and SS4 at the same time (after support fro SS$ has stopped) this will count as two licence usages. Again, is this correct?
As others have said, starting January 1 any SS4 (and earlier) license will have to be node-locked.
From what I have been told at your next Bentley contract renewal after January 1, you will be charged extra for any node-locked licenses you are still using.
Rod WingSenior Systems Analyst
WHAT...?
Haven't we already paid for the software (and the license to run it)? Why are we getting charged again for software already purchased?
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
I should have added 3rd party apps to the initial list, as that certainly is an issue for some.
QTL and now SLS licensing has scared away many customers for even thinking of signing SELECT ever again so they are stuck with v8i and those who have SELECT just avoid using pool licensing.So moving from SS4 to SS10 for them doesn't make much sense as it has additional administration to register users and even that doesn't help to not get QTL. If there would be an option to block additional usages in SLS we could get many back on track.
The main reason to upgrade to CONNECT is to use newer RealDWG version but other exciting new features doesn't increase productivity or some features even decrease productivity so the transition is not yet justified. This is regarding users of PD/MS working in 2D environment with minimal 3D reality data or point cloud data usage. 64-bit or 32-bit platform mostly for users is irrelevant but missing/broken v8i tasks and positional mapping is what decreases productivity. Some even are still on Windows 7. So starting from U14/U15 it seems is turning point to migrate to CONNECT but still for us locally some critical issues still remain. Bentley should have followed Intel strategy of tick-tock model and not do all at once(64-bit platform + SLS licensing + Ribbon interface + dropping features) so it is not surprise that it takes much longer than migration from XM to v8i.
Regarding Inroads to Openroads migration it is disaster as there is no direct replacement for PowerSurvey and they are left with v8i PowerSurvey and CE Powerdraft at same site which also is not reasonable as need to keep to workspaces. For Inroads users also it only recently it started to make sense to use OpenRoads.
I appreciate the insight Oto. One point you made was the mention of the additional overhead of registering users. This is a pretty simple operation that only needs to be done once. It can be done individually or in bulk up to 1000 users at a time. You only need 4 basic pieces of info: First Name, Last Name, Email address, and Country. If that is truly a barrier than I would like to understand why this is painful to be completed. Registration is fairly common anymore when you sign up for anything so I don't believe Bentley is breaking new ground here. I would also like to understand how Alerting a user when there are no more available licenses does not help with reducing or eliminating QTL's. Are the alerts not showing up, are users ignoring them??
Thank you,
Glenn
Yes. ORD isn't even on the U14 platform yet. 2020 R2 is still based on the U13 platform.
When ORD was initially introduced, it was lacking so much functionality it wasn't even funny. I forget how many versions in it took to get something as essential for submittals as End Area Calculations. Plans production has gotten better, but much of that was missing in earlier versions. As Rod said, there are COGO functions that still don't exist at this point. The work has to get done, and if the newer software can't provide neccssary functionality, managers are REALLY hesitant to change.
Hi Glenn,
Glenn Fernandes said:Can I ask why users might want to continue using older software?
as others mentioned already, there are number of reasons, for every individual customer is valid a different set of them.
I agree with Oto that the fact many changes were done together (GUI, features, licensing...), and in fact every single change was done in unprofessional way, when from the beginning nothing worked well, there was zero information available (and not even talking about translated information for local users) and the transition was not well described (I think there is no Bentley material using own weird terminology or newspeak that cannot be simply translated using normal vocabulary).
So all together, Bentley has built for last several years a feeling of unstable unfriendly environment, and even when many issues were solved (even when not all and not perfectly), users who have not decided to escape to competitive platforms (many my customers did), are simply scary and afraid to do the conversion.
My personal feeling is that when a company is bigger and there is somebody responsible for CAD software (often some advanced user, because only the biggest companies have dedicated CAD admins), an openness for the migration is bigger.
Glenn Fernandes said:This is a pretty simple operation that only needs to be done once.
Well, the process itself is quite straightforward, but unfortunately you guys live in ivory towers, far from everyday reality of (especially) smaller users. They do not understand the system, they are not able to find clear explanation (the problem is multiplied because everything is English only) and web interface is complex.
Also, many information is available now, but not in consistent form in one document, but at several places, often a bit de-sycnhronzied with quickly developing cloud systems and offer.
In the discussion important topic was asked and I do not recall I see explanation/confirmation anywhere: When licenses has become node locked, how licenses will be calculated when used in parallel with CE licenses. Even two the most simple scenarios are not explained:
Glenn Fernandes said:Registration is fairly common anymore when you sign up for anything so I don't believe Bentley is breaking new ground here.
Registration as idea yes, it's common, but Bentley has long history (and as former employee, I know what I am talking about ;-) to do things and to present everything more complicated than it is.
Plus, seen locally and compared with competitors, Bentley explain in complicated langauge features and aspects of technology and the solution, whereas competitors often provide (in local language) scenarios how to do migration to new version, new features... step by step. So it's not about "learn and understand our system", but "find scenario that is closest to your situation and use it" (and no deep knowledge of all details is required), so the same complexity looks often simpler.
Another long-term problem is quality of localization. Bentley products are pretty poorly localized to Czech language (often not respecting standard terminology and often also translated without understanding real functionality), but there can be used more or less. But web GUI and also CONNECTION client + Advisor is on big disaster (I normally use strong vulgarism here), done probably using automated translator ending with nonsense. CONNECT Centrum is sometimes localized, sometimes not, which is confusing, so the only solution is to switch everything to English ... but it's blocking for many users.
Glenn Fernandes said:I would also like to understand how Alerting a user when there are no more available licenses does not help with reducing or eliminating QTL's.
Many users are not aware of the alerting, I often received question (literally from all my customers) to explain how licensing works, because there is not single simple document describing in normal langauge how SES works from users' perspective. Also, it's not clear how to setup the alert and whether it is active or not.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi - I am reaching out and trying to understand details of the struggle so that I can try to push things through that will make it easier. I agree that the materials can be improved and I have been trying to do so. For instance, while not listed in the table of contents yet, I am creating a 'QuickStart Guide'. Please take a look and provide any feedback. We also have a longer version that takes into account user scenarios to view this from the user side. The objective is to move away from just describing how a feature works towards a journey through the application.
QuickStart Guide:
https://communities.bentley.com/products/licensing/w/licensing__wiki/50431/subscription-entitlement-service-ses-quickstart-guide
In-depth Guide:
https://communities.bentley.com/products/licensing/w/licensing__wiki/48337/understanding-the-subscription-entitlement-service-ses-workflow-options
In regards to the two questions you have reposted, they will be answered shortly as part of material created for the move away from SELECTserver.
Thanks,
Would it be possible for Bentley to warn us when we try to run MicroStation when another machine is already using it?
Kirk
I Wish Cadland was Reality
Glenn,
Putting instructions in the help document is nice, but not enough in this case. Bentley needs to be more aggressive in contacting their customers about the change in licensing. We spoke with a company last week that had no clue the license changes coming at the end of this year. I'm sure there are many others as well.
The only notice we ever got from Bentley about the change was in a long email in December. The shutdown of SELECTserver licensing kind of got lost in the details of extending the support dates for SS4 and SS10. Depending who in the company got the email, it may have never been passed on to the people who really could understand what all of this means.
There are a lot of companies in for one heck of a surprise when their Bentley products no longer work after January 1.
Hi - that is what the alerts are intended to do. The second link I posted above has examples and instructions on how to use them.
Thanks
Your point about the message possibly not getting to the Admin is valid. But I can tell you that we do look at who is on the contract (as those people are the Admins) and reach out to them. There are additional communications planned for Q3 so I will make sure this point is mentioned again to those that are involved.