Tool Requirements for Integrating Smart P&ID - Intergraph Smart P&ID - Installation & Upgrade - Intergraph

SmartPlant P&ID Installation and Upgrade Guide

PPMProduct
Intergraph Smart P&ID
PPMCategory_custom
Installation & Upgrade
SPFVersion_custom
Version_SPEL_custom
2015 R1 (7.1)
Version_SPI_custom
(none)
Version_SPPID_custom
7.1 (2014 R1)
Version_SPEM_custom
7.2 (2014 R2)
Version_WebSPID
(none)

This topic describes rules and settings that allow SmartPlant P&ID data to be shared correctly with Aspen Basic Engineering, Smart Instrumentation, Smart 3D, and the other tools that are part of an integrated environment.  Other tools that are not listed here have no known SmartPlant P&ID/integration issues.

General Integration Requirements

The following is a list of best practice scenarios for using SmartPlant P&ID so that data will migrate correctly to other tools:

  • In general, when modifying P&IDs that have been published, avoid unnecessarily deleting items in order to move them inside the active drawing or moving them to other drawings. Deleting and replacing items (with the same tag), causes additional work in applications retrieving the P&IDs that may negate the time-saving benefits of the P&ID changes.

  • When working with Projects and As-Built, all instruments to be published must be placed on a P&ID drawing or in the active drawing stockpile.  This is because the plant stockpile is not communicated back and forth between Projects and As-Built.

  • To enable publishing from a project, you must create a project in SmartPlant Foundation with the same name (case-sensitive) as the P&ID project.

  • When creating symbols, connection points (piping, signal, and auxiliary) must be added in the correct sequence. For details, see the Important note at the end of the Place Point Ribbon (P&ID) (see ) topic in Catalog Manager Help.

    Signal points and piping points are not supported for Equipment and Equipment Components when publishing to SmartPlant Foundation.

  • When creating formats for use with SmartPlant P&ID publishing, the formats must be added and mapped in SPPIDDataMap.xml using Schema Editor. The UID string of the custom SPMapUOMDef map file must be of the form SPMU_<NN>_FormatName>, where 'NN' represents the SPMapUOMListDef ID for the format type (for example Temperature = 5; Pressure = 27). Since spaces or restricted characters are not allowed in the UID string, custom format names must not include spaces or restricted characters.

  • If you intend to publish select lists (enum lists) to SmartPlant Foundation, make sure that you review the SmartPlant Adapter for SmartPlant P&ID Guide to understand the requirements (see under Data Transformation Logic > Publish/Retrieve).

  • If the SmartPlant P&ID item tag validation allows for duplicate tags, this may have an impact on downstream tools such as Smart Instrumentation, which does not allow duplicates. In such cases, allowing duplicates in SmartPlant P&ID can cause problems in the retrieving tool.

    By default, SmartPlant P&ID item tag validation does not allow duplicate item tags for loops or instruments.

Integration with Smart Instrumentation

Retrieving Documents

  • If a SmartPlant P&ID drawing that includes items with a flow direction is to be retrieved by Smart Instrumentation, a flow direction of End 1 Upstream or End 1 Downstream must be defined in SmartPlant P&ID Modeler. Bi-directional flow is not supported.

Connect to Process Lines

  • Connect to Process lines are required for connecting instruments to equipment nozzles and pipe runs in SmartPlant P&ID.

  • All non-piped offline equipment instruments must be connected to vessels through non-electric signal lines and nozzles in SmartPlant P&ID. This enables Smart Instrumentation to recognize that instruments are connected to vessels.

    If SmartPlant P&ID assigns an object to an intermediate level in the hierarchy and publishes, Smart Instrumentation will assign the object to the level in the hierarchy in Smart Instrumentation determined by their logic. Because instruments belong to units in Smart Instrumentation, an instrument assigned to the intermediate level in SmartPlant P&ID will be assigned to the unit in Smart Instrumentation. Panels will be assigned to the plant. SmartPlant P&ID may get an update on retrieve to move the object to another level in their hierarchy than where it was published based on the move done automatically by Smart Instrumentation. Panels will move to the top level; instruments will move to the bottom.

Deleting and Adding Items

When you are working in a Projects environment, and items are correlated using the SmartPlant integration tools, you should minimize deleting and re-adding any items. SmartPlant P&ID will reuse tag numbers in the numbering scheme when you delete and re-add items. Smart Instrumentation tracks tag numbers claimed in a project, and this tracking will not work if tag numbers are reused after correlation. If you must delete an item in this situation, you can delete the item to the SmartPlant P&ID Stockpile.

Instrument Expansion

  • A SmartPlant P&ID instrument or loop tag does not always have a 1:1 relationship with instruments in Smart Instrumentation. In some cases, a single item tag in a P&ID corresponding to an instrument or loop needs to be expanded to create several instruments when publishing the data for Smart Instrumentation. For this purpose, the Expansion Type property in SmartPlant P&ID Modeler specifies the expansion behavior when publishing an instrument or loop. Each value of the property corresponds to a Smart Instrumentation rule that determines which instrument types and numbers are to be created in Smart Instrumentation when the SmartPlant P&ID tag is expanded and retrieved.

    When retrieving data back to SmartPlant P&ID, the behavior of a particular instrument created by expansion is determined by Smart Instrumentation parameters. For an expanded instrument, the state of the IRetrievableExpansion interface determines whether that instrument will be retrieved by SmartPlant P&ID: if the IRetrievableExpansion interface is realized, the instrument is retrieved, whereas if the IRetrievableExpansion interface is not realized, the instrument is not retrieved. The 'parent' item tag is always retrieved, regardless of the realization state of the IRetrievableExpansion interface.

Ports

  • Smart Instrumentation uses physical ports, while SmartPlant P&ID uses logical ports. Smart Instrumentation publishes the physical ports with the Dimensional Data Sheets and not the Instrument Index. SmartPlant P&ID retrieves the Instrument Index and does not retrieve the Dimensional Data Sheets.

    When the workflow goes from SmartPlant P&ID to Smart Instrumentation, followed by Smart Instrumentation publishing the Dimensional Datasheet, a Same As relationship is created between the ports in the SmartPlant Foundation database. That Same As relationship is required by Smart 3D to correctly match the design basis ports to the 3D representation of the ports.

    When the workflow goes from Smart Instrumentation to SmartPlant P&ID, however, a Same As relationship is not created in the SmartPlant Foundation database. Without the Same As relationship created in the SmartPlant Foundation database, the result may be additional ports in Smart 3D. To obtain the Same As relationship on the ports requires that SmartPlant P&ID publish the P&ID with the instrument, this P&ID be retrieved by Smart Instrumentation and then having Smart Instrumentation publish the Dimensional Data Sheet.

Integration with Smart 3D

General

  • In Options Manager, ensure that under Settings, the Use Piping Specification setting value is Smart 3D even if the P&ID plant is not validating piping specifications. This is to ensure that the required Piping Component Select List entries are properly set to match the PIP short codes expected by Smart 3D. For details, see Configure Piping Specification Settings in SmartPlant P&ID Options Manager User's Guide.

Drawing Items

  • For Smart 3D to properly determine flow direction in a process run, that process run must be connected to at least 2 items.

  • Some items that can be represented as single objects in SmartPlant P&ID, such as Vent Detail, are modeled in Smart 3D as a set of separate objects. For full correlation to be established between the two tools, ensure that these objects are modeled in SmartPlant P&ID with the same configuration used to represent them in Smart 3D.

Properties

  • Smart 3D handles temperature and pressure properties in pairs and does not support having a temperature (for example, Normal Operating Temperature) without defining the matching pressure (in this case, Normal Operating Pressure). While this is a valid condition for SmartPlant P&ID, it should be a consideration when publishing for retrieval into Smart 3D. Without the Pressure / Temperature pair of values defined, the Smart 3D user will be required to enter a value that was not defined in SmartPlant P&ID.

Integration with Aspen Basic Engineering

Retrieving Documents

  • Basic Engineering data sheets can contain multiple objects and may be formatted in a traditional data sheet view or list view (for example, as an equipment list). Data sheets retrieved from Basic Engineering may include stream data, specialty piping data, or relief valve data as required by business practices.

Using the Catalog Index in SmartPlant P&ID and SmartPlant Integration

When you select the Retrieve command, the software accesses the CatalogIndex.mdb and the system performs the following actions:

  1. Using the retrieved document, the object type and classification of the retrieved item is determined.

  2. Using the SmartPlant P&ID Map file, the ItemTypeName (Equipment, PipeRun, PipingComp, Loops, and so forth), and codelist indices for Class, Sub-Class, and Type is determined.

Catalog Index Lookup

The Catalog Index file is used to find a symbol in the catalog with type properties that match the given values.  The lookup is performed using the most specific information first. If a match is found, that symbol is used. However, if there is no match, the more generic type information is used for additional searches. In this way, a generic symbol will be returned if no specific symbol is available in the catalog.

Search Based on Type Value — Searches the catalog index for all rows with matching ItemTypeName and Type values and IsDefaultForType = True.  If one or more rows are found, the software uses the CatalogItemName from the first one.  If no match is found, the software performs the search based on Subclass.

Search Based on Subclass Value — Searches the catalog index for all rows with matching ItemTypeName and SubClass values and IsDefaultForSubclass = true.  If one or more rows are found, the software uses the CatalogItemName from the first one.  If no match is found, the software performs the search based on Class.

Search Based on Class Value — Searches the catalog index for all rows with matching ItemTypeName and Class values and IsDefaultForClass = True.  If one or more rows are found, the software uses the CatalogItemName from the first one.  If no match is found, the software returns an empty string.