Bentley Map CONNECT Edition Technology Preview?

Is there a schedule now?

Thank you for asking. We are currently in the process of finalizing our plans for 2017. Please stay tuned...

Hi Gijbert,

it would be great to stop to say "we are working on it" and to become more specific. CONNECT Edition platform was announced with big appluad in 2015, MicroStation is there more than a year, other product lines were released already (Descartes) or will be available at least as Technology Previews or Betas shortly (GenerativeComponents, OpenRoads Designer...), but no information about geo.

In such situation I understand my customers who have lost their confidence in Bentley geo focus and started to think about future and what platform to use. And loyal customers who like Bentley Map are disillusioned, because for more than year there is no clear information about plans and development direction. Also in mixed environment (MicroStation + BM) it often blocks migration to MicroStation, because IT people don't want to maintain two different workspaces and product lines (regardles sometimes they are used in different teams or departments).

With regards,

  Jan

If Bentley Map CONNECT will have the same old and ugly "Bentley Geospatial Administrator" then I better wait.

At least some insights what we could expect from Bentley Map CONNECT. It will be just a port to Microstation CE with migrated old and introduced new bugs or major update?

If Bentley Map CONNECT will have the same old and ugly "Bentley Geospatial Administrator" then I better wait.

At least some insights what we could expect from Bentley Map CONNECT. It will be just a port to Microstation CE with migrated old and introduced new bugs or major update?

Unknown said:

At least some insights what we could expect from Bentley Map CONNECT. It will be just a port to Microstation CE with migrated old and introduced new bugs or major update?

It's exactly the information that were shared in disucssions for some other products and despite of because of time and software development constraints not always were reached fully or had to be changed, they have helped user to make preliminary decisions and plans. It's very usefull e.g. when budget and resources are planned annually.

Regards,

  Jan

Honestly in each project we have tried to push Bentley Map it ended with stumbling upon critical bugs/missing features which makes BM not usable for production. If Bentley is really geo focused the development for Map should be more rapid and release priority patches and not just "will be fixed in next version" when actually it just don't happen.

For example:
#195654 issue that hole elements are lost after split command. Registered at 2015.03 and still not fixed but shouldn't take that long.
#222435 89 Associative region that are restricted, while they should not 2015.10
#217844 Corrupt DGN level table after SHP import 2014.02

Hello Oto,

First, let me apologize for being a little too brief in replying to your previous question. I hope I improved on that with my reply to Jan's message earlier in this thread. As I stated in the message to Jan, we are close to announcing our post-V8i plans, but allow me to comment briefly:

"(...) It will be just a port to Microstation CE with migrated old and introduced new bugs or major update?"

By definition, any post-V8i development is a major update. It will mean shifting from 32-bit to 64-bit, adopting a new UI paradigm and embracing/integrating new features available in the new platform, etc. Inherently, an important part of this will be to migrate the existing code to the new platform, but be assured that the Map development team will not treat this as "just a port".

"(...) If Bentley Map CONNECT will have the same old and ugly "Bentley Geospatial Administrator" then I better wait.

It is too early to tell what will happen to individual tools, but the nature of Map is that is will always require an object editor of some kind to allow the user to define the object model(s) it wishes to work with. That said, I have confidence that the "pull" factor of any post-V8i development should convince you not to wait but to upgrade.

"(...) At least some insights what we could expect from Bentley Map CONNECT.

At this point in time, I can only repeat what I wrote to Jan in an earlier message: once our plans are in place - which I expect to be (very) soon - I will inform you and the community.

Best regards,


Gijsbert

Hello Oto,

With regards to your next message that discusses critical bugs/missing features.

I am very sorry to hear that you are not happy with the way things are developing for Bentley. Again, allow me to comment on some of your remarks:

"(...) If Bentley is really geo focused the development for Map should be more rapid and release priority patches and not just "will be fixed in next version" when actually it just don't happen."

#development for Map should be more rapid:

This year we have released two update releases for V8i SELECTseries 4 - in April and July - and we are finalizing a third update release that should be available before the end of the year. Possibly what you are referring to with "rapid" is the lack of speed in moving to post-V8i development, but I still wanting to point out that we did make an effort to regularly update and refine our existing V8i offering.

#and release priority patches

Besides the mentioned update releases we have released (and do release) priority builds to users with production preventing issues. We have an escalation procedure in place that in my experience works well and delivers priority builds when they are needed. Reading your remarks -- e.g. stating "makes BM not usable for production." -- I am wondering what happened in your case, and whether escalations where used to get you the right Map versions when needed.

#"will be fixed in next version" when actually it just don't happen

My experience is that we do not make these kind of statements unless a problem is actually going to be fixed. As part of an escalation procedure I can see those statements being made, or in communications about service tickets once it is confirmed that something is actually resolved. So again, I am wondering what happened in your case.

I will forward this tread to our support team and ask them to look into the examples you gave to give you a status update.

Best regards,


Gijsbert