Conceptual or Test models in AutoPLANT Project

Looking for methods, ideas or best practices.

In an AutoPLANT V8i project, how do you handle multiple versions or conceptual versions of a design?

Scenario:
Routing pipe; need to have 2 or more different routings to present for review to decide on which to use.

  • What method do you or your company use to accomplish this?
  • How does this affect the data?
  • Do you have duplication of tags?
  • What do you do with the rejected models after a decision is made?
  • How many fingers am I holding up?

Thanks in advance for your time!

Parents
  • Hi Steve,

    I guess this all depends upon your viewpoint.  If you have a master "project" then you could briefcase out the models you need and work on them independently.  The "promoted" model can then brought back into the project and merged.

    Using i-model composer each of the "options" can be viewed alongside the master project in-situ etc

    This would not affect the data at all, but of course if you have new tags which you need to add you would not have access to the project tag register, so consideration is required for that (and there are methods of embedding them into the briefcase model)

    Note that this method has the major benefit of a cancelled project having NO impact on the master project, which is generally a consideration for stakeholders.

    There are some enhancements within AutoPLANT which enable the same tag to be used on multiple Piping models (much as they are within P&ID), but this is not the default.  This was created for a specific workflow and is therefore disabled by default.  This would cater for your multiple models of the same design.  However, the cancellation / selection workflow would require additional effort.

    As to how many fingers ... "that is impossible ... realise the truth, there is no spoon"

    Glen Worrall

    Bentley Systems



Reply
  • Hi Steve,

    I guess this all depends upon your viewpoint.  If you have a master "project" then you could briefcase out the models you need and work on them independently.  The "promoted" model can then brought back into the project and merged.

    Using i-model composer each of the "options" can be viewed alongside the master project in-situ etc

    This would not affect the data at all, but of course if you have new tags which you need to add you would not have access to the project tag register, so consideration is required for that (and there are methods of embedding them into the briefcase model)

    Note that this method has the major benefit of a cancelled project having NO impact on the master project, which is generally a consideration for stakeholders.

    There are some enhancements within AutoPLANT which enable the same tag to be used on multiple Piping models (much as they are within P&ID), but this is not the default.  This was created for a specific workflow and is therefore disabled by default.  This would cater for your multiple models of the same design.  However, the cancellation / selection workflow would require additional effort.

    As to how many fingers ... "that is impossible ... realise the truth, there is no spoon"

    Glen Worrall

    Bentley Systems



Children
No Data