Creating an alternate plant breakdown structure (PBS) - 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)

In an integrated environment, engineering data is organized using a plant breakdown structure (PBS). For example, a PBS for organizing plant data might be plant/area/system/subsystem or plant/area/unit.

The PBS hierarchy is defined in the SmartPlant schema and is used to create the PBS hierarchy in SmartPlant Foundation. This hierarchy is communicated to integrated authoring tools when SmartPlant Foundation publishes the plant breakdown structure and the tools retrieve it.

Integration Hierarchy Limitations

The integrated environment imposes the following limitations on custom hierarchies, based on requirements from the authoring tools. This list includes the tool imposing each restriction, so that customers can factor these limitations into their hierarchy setup based on their current and future tool usage.

  • The hierarchy must have a minimum of 3 levels. This limitation is imposed by Smart Instrumentation.

  • The names of hierarchy items cannot be changed once created. This limitation is imposed by SmartPlant Foundation.

  • The hierarchy scheme cannot be modified after the plant is created. This limitation is imposed by Smart P&ID and SmartPlant Foundation.

  • If using a unit in the hierarchy, the unit number must be unique. Unit names can be duplicated across the hierarchy. This limitation is imposed by Smart Instrumentation.

Plant Naming Guidelines

Use the following guidelines when naming your plant, or top-level hierarchy items, which will be used in an integrated environment. These limitations are imposed by the authoring tools and the database software. For these guidelines, "plant" is used as an example of a top-level hierarchy item.

  • Do not use special characters at all in any part of a plant name or plant breakdown structure such as area or unit. These include .<,>^=+:?|/';{}[]~`!%*()&$@#".

  • A warning message that the characters are invalid is displayed if you use any special characters.

    • The plant name is case-sensitive and cannot exceed 52 characters if Smart Instrumentation will be participating in integration.

    • The plant name must be unique within the current domain. This limitation is imposed by Smart Instrumentation.

    • We recommend that the Smart Instrumentation domain schema name and domain name match the plant name.

    • We recommend that the plant name be the same name across all authoring tools.

    • You can use digits and spaces within the body of the plant name, for example Plant 1. However, spaces are treated the same as underscores; so, if you name a new plant with a name that already exists, but use a space or an underscore to differentiate, an error message will state it is already in existence. For example, Plant 1 and Plant_1 are considered the same.

Remove the existing PBS structure Check out and launch the CMF file Define a custom PBS hierarchy from a template Define a custom PBS hierarchy Check in the CMF and load schema changes Generate component schema files Generate authoring schema and load files Load alternate PBS objects Create a new plant and structure Associate a vault with the new plant Register and publish the PBS

SHARED Tip Click a box in the diagram to go to the associated procedure.

What do you want to do?