Configuring valid line end objects - 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 ValidLineEndObjects section of the line list header adapter document defines which object types are to be used in determining the consolidated "from" and "to" information for the line list records. If an object at the end of a line segment is defined in the adapter document to be a valid end object for a line list record, the consolidation process includes that object in the from/to information. Likewise, if an object is not defined to be a valid end object, then consolidation ignores that end object in determining the from/to information for the line list record.

The line list header adapter document specifies the class definitions and any property criteria for those class definitions to use as end objects. If the line list adapter finds an object that has a class definition that is specified in the adapter document, it will add a new interface to the object so that the consolidate code can recognize the object as the end of a line.

If the class definition has property criteria specified in the adapter document, when the adapter finds an object of that class definition, it also looks for a match on all the specified property values before adding the interface. This allows you to use typing information that is published on the P&ID but not instantiated by SmartPlant Foundation to determine which objects are valid line end objects.

For this to work, the relevant SmartPlant Foundation class definition must have an optional realizes relationship to the ISPFLLALineEnd interface definition.

The following interface definitions have this realizes relationship by default:

  • SPFLLAEquipment

  • SPFLLAInlineInstrument

  • SPFLLANozzle

  • SPFLLAOfflineInstrument

  • SPFLLAOffPageConnector

  • In the line list header adapter document, only equipment is configured to be end objects.

  • Note the following limitations of the end object determination:

    • Objects that are sometimes the end of a line and sometimes not are not supported. For example, if you decide that you want an off-page connector to be the end of a line until something links to the other side, this is not possible with this mechanism.

    • Another limitation is when a line segment is the end of another line segment, such as when two line segments are connected, but belong to different pipelines. Currently, this situation is not supported. Support for this situation is planned for a future release.