Hexagon default plant breakdown structure versus cross-plant interaction plant breakdown structure - HxGN SDx - Update 56 - Reference

HxGN SDx Schema Overview

Language
English
Product
HxGN SDx
Search by Category
Reference
SmartPlant Foundation / SDx Version
10

The Facilities breakdown can be set up in two different ways, each having their own reasons and characteristics:

  • Hexagon default: Site-SPFPlant-Area-Unit

  • Cross-plant interaction: Site-SPFPlant-Plant-Unit

Although there are two different breakdown structures, the underlying data model is the same (SDASite-SPFPlant-SDAArea-SDAUnit). This also addresses the different needs for uniqueness of the objects, where objects like Units and Tags are unique within their plant.

The main difference between these structures is the way plants are stored in the system:

  • In the Hexagon default, each configuration is one plant.

  • In the cross-plant interaction, each configuration can store multiple plants.

The image below illustrates the Hexagon default mode for the plant breakdown structure in SDx, where SPFPlant is a configuration.

Plant hierarchy DEFAULT

The following image illustrate the cross-plant interaction mode in SDx where a configuration can contain one or more plants.

Cross-Plant hierarchy_11-2020

The "Config" is the strict boundary for your data in the system, also known as the "SPFPlant" or "ConfigLevel1". This provides a strict container for the data you store in it, allows you to assign people with access to it, or restricts users from accessing it. This is primary reason for having the two different structures: as many users of SDx (typically Owner Operators) don’t want these strict boundaries between their plants, whereas other customers (typically EPC’s) need these strict boundaries.

The main difference between the two plant breakdown structures is that you can store each of your plants' data in separate configurations, or you can have all your plants in one configuration. The first approach will not allow you to interact between the plants, as they are strictly separated by the configuration. Alternately, having all your plants in one configuration allows for cross-plant interaction, such as relating tags and documents from different plants to each other, having cross-plant projects, and so forth.

Hexagon default PBS

Cross-plant interaction PBS

Configuration = Plant

Configuration can contain one or many plants

Main functional breakdown goes 4 levels deep

Main functional breakdown goes 3 levels deep (SPFPlant is just a configuration)

No cross-plant relations are possible

Cross-plant relations are possible

Allows access and security segregation between plants

Denies access and security segregation between plants

Cross-plant projects are not supported

Cross-plant projects are possible

Tag names are unique within your configuration, as the configuration is the plant

Tag names are unique within each plant, but are not unique within the configuration itself

Both manual creation of PBS items using the Web Client and loading through Load Manager are possible

PBS items are created only through the Load Manager