SS4 - stopping support question

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?

Parents
  • 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 Wing
    Senior 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.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Look back at your rock analogy. Bentley wants to make sure they are getting reimbursed for you taking both rocks.

    Rod Wing
    Senior Systems Analyst

  • Shouldn't it be we get a node lock for ss4 and earlier and the continue to pay the yearly update/ support fees for the connect version? I was told by the support it didn't matter if you had both versions of the software loaded. And that there would be no charges for using both versions

    I paid for this license years ago and the yearly updates.  Isn't this like taxation without representation?

    What if I am not going to use the connect version?

    Do I need to jump ship to another software company? Most of my client has started using Revit. I'd hate to jump over to Autodesk after 33 years of using Microstation

    Earlier versions are now obsolete it should belong to Bentleys client for its use on one PC per license and allowed to be moved to another PC as pcs are upgraded and windows is updated.

    Kirk

    I Wish Cadland was Reality

  • I was told by the support it didn't matter if you had both versions of the software loaded

    False. it is considered as two different products at least for now because one is v8 and other is v10 version. You double your productivity by using two versions at once so double charge. Relaxed

    What will most likely happen if this switch to node-locked will not be handled reasonably is that more companies for products which don't have SS10 versions will be locked in v8i platform without SELECT.

  • Hi,

    Can I ask why users might want to continue using older software?  I understand that some agencies have contracts that require certain versions and I also understand some users have concerns/inability to use an application that would require internet access.  But I would like to understand if there is a reason beyond that which we are missing.  We've read on the Forum for years the need for better license control/visibility and the CONNECT versions with Subscription Entitlement Service provides that and will continue to be refined to add additional options.  If anyone is already using the Hosted SELECTserver model, the transition is relatively easy.  If there are issues/concerns with the transition process, I'd like to hear those as well.

    Thanks for the feedback,


    Glenn

  • Older projects are the number one reason. While Connect has been out for years, it has only (relatively) recently become stable and well-developed enough for our major clients to be interested. My major client has just now set up their "alpha" workspace (not even up to beta testing)! That means that we have dozens (if not hundreds) of projects that have begun in the older software, with multi-year project schedules, that will not be brought forward.

    This "easy" transition is also not always in the hands of the CAD guy. Contracts are often managed by front-office people who don't deal with the technical side of things. I have tried to write up a "justification" to switch our CAD over to SS10 with the Enterprise licensing, and all I really know to tell them is the Select Licensing is ending, please go to Bentley.com and find the FAQ. All of that switchover is in their hands, and there's nothing I can do except to encourage them.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Reply
  • Older projects are the number one reason. While Connect has been out for years, it has only (relatively) recently become stable and well-developed enough for our major clients to be interested. My major client has just now set up their "alpha" workspace (not even up to beta testing)! That means that we have dozens (if not hundreds) of projects that have begun in the older software, with multi-year project schedules, that will not be brought forward.

    This "easy" transition is also not always in the hands of the CAD guy. Contracts are often managed by front-office people who don't deal with the technical side of things. I have tried to write up a "justification" to switch our CAD over to SS10 with the Enterprise licensing, and all I really know to tell them is the Select Licensing is ending, please go to Bentley.com and find the FAQ. All of that switchover is in their hands, and there's nothing I can do except to encourage them.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Children
  • To add on to what Mary said, there are some DOT's (and by extension, their consultants) still using InRoads SS2 as their primary civil design software. They never made the switch to SS3/SS4 and thus it does not make sense for them to migrate to SS10 as there is quite a steep conversion.Then there another steep conversion to migrate the InRoads SS2 (or SS4/SS10 for that matter) standards to OpenRoads Designer.

    Beyond the redefinition of all of their civil standards, there is the issue of functionality. As Mary said, files developed in the older software cannot be brought forward into the newer software. Projects started in the older software will need to be completed in the older software. The other part of the functionality issue is the tool set. There are COGO functions in InRoads SS2 that have not been moved to OpenRoads Designer.

    Rod Wing
    Senior Systems Analyst