Plant breakdown structure - SmartPlant Foundation - IM Update 46 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)

The composition of the plant is based on the grouping of physical objects by their function in the plant. The plant usually occupies the top level of the hierarchy and is typically followed by subsections, such as areas, units, sites, or systems. This is commonly referred to as the Plant Breakdown Structure or PBS.

Once the PBS exists in SmartPlant Foundation, it must be published in order to be retrieved by the authoring tools. This is necessary in order to synchronize the different authoring tools and SmartPlant Foundation as part using the SmartPlant environment.

The publish and retrieve using a PBS from SmartPlant Foundation to other tools uses the same concepts and procedures. These tools can include Aspen Basic Engineering, Smart 3D, and Smart Electrical.

In previous versions of the software, you were required to use the default Plant/Area/Unit hierarchy. This restriction is no longer in place; however, the following restrictions do still apply:

  • You must apply the structure you create in SmartPlant Foundation across all authoring tools. For example, if you choose to use the Plant/Area/System hierarchy, you must use that structure in every tool that will be using SmartPlant. You cannot select different hierarchies for different authoring tools.

  • Your structure must consist of at least three levels.

You can configure your own hierarchy in the schema by using the Schema Editor. See SmartPlant Schema Editor Overview for more information about using the Schema Editor.

The following describes the process for defining a custom PBS hierarchy for integration:

  • If your current database contains an existing PBS hierarchy, remove the existing PBS structure from the database, update the existing plants in the database, and remove the existing PBSHierarchy graph definitions for SmartPlant Foundation authoring before creating your custom PBS hierarchy. These changes are made by running load files delivered with SmartPlant Foundation.

  • Check out the SmartPlant schema CMF file from the SmartPlant Foundation Desktop Client.

  • Browse to the location where you checked out the CMF_ver document, find the EFSchema.cfg file, and launch that file in the SmartPlant Schema Editor.

  • Select the schema version or versions that you want to view in the Specify configurations to display window of the Active Configurations dialog box.

  • Click the Advanced button on the Active Configurations dialog box to view the Set Configurations for new objects window, where you can specify what version or versions of the schema changes should be written to. For example, to modify the 2019 schema, select the 2019 configuration for new objects.

    By default, all configurations are checked to allow forward and backward compatibility between schema versions when creating new objects or modifying existing objects.

  • Define the hierarchy in the schema using a template in the Schema Editor.

    If you want to define the hierarchy without using a template, see Define a custom PBS hierarchy.

  • Check the CMF file back into SmartPlant Foundation.

  • Prepare the updated SmartPlant schema CMF file to be loaded into SmartPlant Foundation data warehouse database.

  • Load the updated schema file into the SmartPlant Foundation data warehouse database.

  • Generate SmartPlant Foundation authoring PBS configuration.

    • Generate a new SmartPlant Foundation PBS authoring component schema.

    • Generate a new SmartPlant Foundation PBS authoring tool map schema.

    • Generate PBS methods, menus and forms.

  • Load the generated files into SmartPlant Foundation to load administration and schema data and generate forms and menus.

  • Check out the existing PBS authoring adapter tool map schema and check in the PBS authoring tool map schema that was generated.

  • Create a new plant.

    Be sure not to create the plant until you complete all the previous steps in the work process.

  • Create a host and vault and add the necessary publish interfaces needed for the vault.

  • Relate the new plant to a vault configured for integration.