PlantSpace and V8i

Hi Mike,

Bentley have been pretty open in saying there will be no PlantSpace for V8i with their efforts going into the Open Plant product. I believe the P&ID component is already being beta tested as we speak. Noy sure 100% on other dates, but it will be interesting to see how things go once it's released.

So is it like a name change?

Is there a diagram somewhere, to make sense of it all?

 Does that mean there will be no Autoplant?

Jeff,

I believe, from the meetings we've had with Bentley, that it's the next generation on from PSDS with many changes. I'll see if I can dig up a few things for you as it seems this one hasn't been seen my B yet.

Have a look at :

http://www.bentley.com/en-US/Products/Plant%20Design%20and%20Engineering/OpenPlant.htm

Jeff,

I believe, from the meetings we've had with Bentley, that it's the next generation on from PSDS with many changes. I'll see if I can dig up a few things for you as it seems this one hasn't been seen my B yet.

Have a look at :

http://www.bentley.com/en-US/Products/Plant%20Design%20and%20Engineering/OpenPlant.htm

Bear,

For the time being it should have been possible to use the Plantspace with the V8i application graphics engine. I do not understand why it is so dificult to transfer Plantspace under V8i. All other triforma based applications like BA , STF mechanical systems etc are already under V8i. 
This new "Openplant" version may be released after 2 years.

I think the OpenPlant idea is great.

Combine the good things from PlantSpace, AutoPlant, and new ideas into one package that can design independent of the CAD engine, then create drawings to issue in what makes the most since for the particular project. What needs to be done is to keep in mind all the work that has gone into the use of these previous systems, and provide a clear upgrade path.

Current users need to be kept in the loop during development to ensure that Bentley produces a good usable (in the real world) product when finished and to make the migration from present technology to the future system as smooth and painless as possible. Bentley needs to keep in mind the expense and resistance to change encountered when upgrading a whole design environment.

Change is great, just plan it out prior to implementation so we can all keep going on the same path to the future.

Thanks for the rant space...

Mike

I'm trusting that the most immediate and beneficial thing to come from the ISO15926 platform is better integration and interoperability between the Bentley products, not necessarily the between Bentley products and other vendors. As a file based PlantSpace Design Series user, and a PlantSpace P&ID user, what I'd like to see in the OpenPlant products a single instance of a valve, pipe, or instrument for example. Furthermore, if someone moves it in the model, I need corresponding and intuitive functionality in the P&ID, and vise versa. If it exists in one and not the other, I need to know. With regards to that instrument, in addition to delivered integration with Datasheets and DataManager, I'd expect integration across platforms into BBES for example. And, all that without the need for some robust ProjectWise backbone.

All that is surely possible with my existing tools, but not without a lot of time, new work processes, and a lot of aptitude with the classes and J-Space.

The current Beta of PowerPID doesn't have any data back end. It seems to be a pure drafting tool at this point. I'm a little concerned that when the data back end shows up, and when I own the next iteration of modeling tool (whatever that's called and however it works), that aptitude in J-Space and familiarity with the classes is not going to be as valuable; that I'm going to need to learn .net or something.

So, to read something like "there will be no PlantSpace" is a little disconcerting.

Tell Logrie "hey" Mike.

Hi Jeff and all on the thread,  

Well I guess it's time  I waded into this thread.

At the BE 2008 Conference Bentley announced it's future plans for PlantSpace Design Series and the news was recieved by the conference participants as very good news indeed. PSDS for V8i has been under development for over 16 months now and will be rebranded and released in 2009 as part of the OpenPlant family of products based on ISO 15926.

For those of you not aware of what ISO 15926 means to OpenPlant and yourselves you can get more information at:

ftp://ftp2.bentley.com/dist/collateral/whitepaper/OpenPlant_WP_Final.pdf

All of the OpenPlant applications will be using the V8i EC Framework configured on the ISO 15926 data structure and stored in the OpenPant schema. This brings a consistent data format which will provide data consistenty among all the applications. So now you will be able to do consistency checks between P&ID and 3D.

 Your experience with JSpace will certainly come in very handy Jeff as OpenPlant carries the same concepts forward. JSpace class libraries now become schema files stored in xml format. The new class editor has similar concepts with JSpace of classes and properties and project class libraries become child and supplemental schemas. 

So the good news is that PSDS is alive and well and not disappearing but is currently under a very aggresive development update. Early in 2009 I will be creating a BE Community for the new OpenPlant plant modleing tools where more detailed information can be found. We are also planning on having our Beta program kick off early in Q1,09.

 Thanks,

Ian Robinson

3D Plant product Manager - Bentley Systems

Hi Ian and to all Plantspace users,

I would like to know if any good news exist about the anticipated transfer of Plantspace (or openplant 3D design product)  to V8i platform.  It was supposed to be Q1 2009.

Regards

Chris