smartplant reference data plus smartplant isometrics...

SmartPlant Reference Data Plus SmartPlant Isometrics Interface

Version 2011 R1 (7.1.0)

November 2013

DMAR1-PE-200151B

Copyright Copyright © 2012-2013 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished - rights reserved under the copyright laws of the United States.

Intergraph Corporation 300 Intergraph Way Huntsville, AL 35813

Documentation Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides, Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a particular software product.

Other Documentation Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support, SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph as guidance for using a software product.

Terms of Use a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the

software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product and Documentation. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal, non-commercial use. The Documentation may not be printed for resale or redistribution.

b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid licenseagreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial. The Other Documentation may not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any reason by Intergraph Corporation by giving written notice to Licensee.

Disclaimer of Warranties Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

2 SmartPlant Reference Data Plus SmartPlant Isometrics Interface

Limitation of Damages IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.

IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.

Export Controls Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access) under the following circumstances:

a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries. b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce

Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S. Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S. Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.

c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive nuclear uses.

d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place. e. Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export

Compliance Department, Huntsville, Alabama 35894, USA.

Trademarks Intergraph, the Intergraph logo, Intergraph Smart, PDS, SmartPlant, SmartMarine, FrameWorks, I-Sketch, IntelliShip, ISOGEN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

SmartPlant Reference Data Plus SmartPlant Isometrics Interface 3

Contents Preface .......................................................................................................................................................... 7

Documentation Comments ..................................................................................................................... 7

Export Interface Configuration .................................................................................................................. 9

Create interface....................................................................................................................................... 9 Specify interface attributes .................................................................................................................... 10

SmartPlant Isometrics Master Data ......................................................................................................... 11

Define groups ........................................................................................................................................ 12 Define component types ....................................................................................................................... 13 Define configurations ............................................................................................................................ 14 Define symbol key sets ......................................................................................................................... 15 Define symbol keys ............................................................................................................................... 16 Assign graphics to symbol keys ............................................................................................................ 17 Define end preparations ........................................................................................................................ 17 Map symbol keys to commodity codes ................................................................................................. 19 Map symbol keys to attributes .............................................................................................................. 21 Map material attributes ......................................................................................................................... 22 Define bolt mapping .............................................................................................................................. 22

Export Jobs ................................................................................................................................................ 25

Set up default sets ................................................................................................................................ 25 Define a new export job ........................................................................................................................ 27 Run an export job .................................................................................................................................. 28

Customization ............................................................................................................................................ 29

Export tables ......................................................................................................................................... 29

Branch Selection Table ............................................................................................................................. 33

Define the branch operation .................................................................................................................. 34

Bend Selection Table ................................................................................................................................ 37

Define bend table .................................................................................................................................. 37

Index ........................................................................................................................................................... 41


Contents


The SmartPlant Isometrics interface exports catalog data from SmartPlant Reference Data Plus to SmartPlant Isometrics using Microsoft Access database files.

Documentation Comments Send documentation comments or suggestions to [email protected] (mailto:[email protected]?subject=documentation comments).

Preface


mailto:[email protected]?subject=documentation%20comments

Preface


S E C T I O N 1

This section explains how to configure SmartPlant Reference Data Plus for exporting data to SmartPlant Isometrics.

What do you want to do? Create interface (on page 9)

Specify interface attributes (on page 10)

Create interface 1. In SmartPlant Materials, on the A.70.01 Interfaces screen, add a new entry for the

SmartPlant Isometrics interface.

2. Type SPISO in the Interface box and descriptions in the Short Desc and Description

boxes.

SPISO must be entered in all uppercase; otherwise, the export fails.

Export Interface Configuration


Export Interface Configuration

Specify interface attributes 1. In SmartPlant Materials, on the A.50.I.02 Interface Attributes screen, specify the attribute

translations for bolt length, bolt diameter, and bolt quantity. The attributes must already be defined on the A.50.01 Attributes screen.

2. In the second block, select SPISO from the List of Values (LOV) in the Interface box, and

type the attribute translation in the Translation box. The attributes must match the translations used in SmartPlant Isometrics as listed below:

BDIA for bolt diameter

BLGT for bolt length

BQTY for bolt quantity


S E C T I O N 2

In SmartPlant Reference Data Plus, open the master data screens from the Integration > XI10 SPIso > XI1010 Master Data menu to view and edit the data stored in SmartPlant Reference Data Plus. This data must reflect the SmartPlant Isometrics master data needed to run the export interface.

The most common data is installed and delivered with SmartPlant Reference Data Plus.

Symbol Key Set screen The sort order in the Order Seq box determines in what order the export job searches for

mapped attributes.

The Standard indicator means that this set is the default set delivered with SmartPlant Reference Data Plus. This set cannot be deleted or modified.

The Lookup others indicator determines if it is allowed for this set to search other sets to find attribute mappings.

The Used by others indicator shows if this set can be searched.

The bore unit and dimension unit assigned to the set in the Bore Unit and Dim Unit boxes are copied from the set to the export job when this SKEY set is selected on the XI3020 Export Jobs screen.

The Comment box can be used to add a comment or description to the selected SKEY set.

Symbol Key screen If the Reversible indicator is selected, parts belonging to the SKEY can be used

independently of the flow direction.

If the Bolt Material check box is selected, parts belonging to the SKEY represent bolting material.

For bolts, ensure that the Bolt Material check box is selected when you are mapping to the BOLT SKEY with the group and parts. This requirement is necessary to identify and handle bolts.

SmartPlant Isometrics Master Data


SmartPlant Isometrics Master Data If the Default Choice check box is selected, the commodity codes belonging to the SKEY

are not stored in the Default Choice table in the SmartPlant Isometrics Access database. For more information about Default Choice, see the SmartPlant Isometrics documentation.

What do you want to do? Define groups (on page 12)

Define component types (on page 13)

Define configurations (on page 14)

Define symbol key sets (on page 15)

Define symbol keys (on page 16)

Assign graphics to symbol keys (on page 17)

Define end preparations (on page 17)

Map symbol keys to commodity codes (on page 19)

Map symbol keys to attributes (on page 21)

Map material attributes (on page 22)

Define bolt mapping (on page 22)

Define groups 1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101010 Define Groups.


SmartPlant Isometrics Master Data 2. View and edit the SmartPlant Isometrics groups and group numbers.

Define component types 1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101020 Define Component

Types.


SmartPlant Isometrics Master Data 2. View and edit the SmartPlant Isometrics component types and numbers.

Define configurations 1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101030 Define

Configurations to define the mandatory and optional settings for bores and dimensions.


SmartPlant Isometrics Master Data 2. Select a check box to define an attribute as mandatory, or leave it empty to define the

attribute as optional.

When you map attributes for SKEYs (symbol keys) on the XI1020 Symbol Key Mappings screen, the Mandatory check box indicates whether the attribute is mandatory or optional. For more information, see Map symbol keys to attributes (on page 21). You can change the mandatory option on the mapping screen.

When you export catalog files, number values such as configuration number, group number, and component number are always relevant to the export. Therefore, they must be set to SmartPlant Isometrics rules. The code values are only used in SmartPlant Reference Data Plus and are not exported. For more information regarding the code and number values of SmartPlant Isometrics related master data, refer to the SmartPlant Isometrics documentation.

Define symbol key sets You can group symbol keys (SKEYs) into SKEY sets. This feature allows you to assign different mappings and attributes to the same SKEY. When an export job is defined, an SKEY set can be selected to determine which attributes are considered.

1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101040 Define Skey Sets.

2. Select a set, and then click Call Copy Symbol Key Set .

The new SKEY set is placed at the bottom of the grid.

Depending on the settings of each SKEY set, the assignment of SKEYs to a specification item follows certain rules:

a. The SKEY set assigned to the export job is searched first. If an SKEY is found, other sets are not searched. If no SKEY is found, processing continues with step b.

b. The Lookup Others option of the selected SKEY set must be selected to continue the search. If this is the case, continue with step c.

c. The SKEY set that has the Used by others option selected and with the lowest value in the Order Seq box is searched next. This step is repeated until an SKEY is found or no more SKEY sets are available.



Define symbol keys You can edit symbol keys and assign them to symbol key sets.

SmartPlant Reference Data Plus is delivered with SKEYs already configured and assigned to the standard SKEY set.

1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101050 Define Skeys.

2. In the tree view on the left, double-click an SKEY set.

3. In the grid, assign and edit symbol keys.

If you assign additional SKEYs, be sure they are assigned to a group, configuration, and component type that can be selected by pick lists.



Assign graphics to symbol keys 1. On G.10.02 Part Symbols, load up to two graphics into the database.

Part symbols to be used as diagrams for an SKEY should be defined in the product

group so that they are visible in all projects, because SKEYs are project independent.

2. On the Define Skeys screen in SmartPlant Reference Data Plus, select the graphic from the LOV in the Symbol Code or Symbol Code 2 box.

On the Define Skeys screen, you can use the slider at the top of the graphic to zoom in and out.

Define end preparations 1. Click Integration > XI10 SPIso > XI1010 Master Data > XI101060 Define End

Preparations.


SmartPlant Isometrics Master Data 2. View all available end preparations.

The installation process loads the default end preparations data and assigns the end

preparations to SKEYs. You can see the assignments on the Define SKEYs screen. For more information, see Define symbol keys (on page 16).

The transfer process uses the data defined on the Define SKEYs screen to populate the interface data in M_SPISO_EXP_SPEC_IDENTS. For an SKEY without any end preparation definitions, the transfer process uses SmartPlant Isometrics default settings.

To modify the data transferred to SmartPlant Isometrics, the following options are available:

You can assign different end preparations to SKEYs on the Define SKEYs screen.

You can assign different end preparations to records in M_SPISO_EXP_SPEC_IDENTS using code in M_PCK_SPISO_CUSTOM.GENERAL_CIP. For more information, see Customization (on page 29).

Modifying end preparation data can cause errors during the transfer process and unexpected behavior in SmartPlant Isometrics. To restrict who can change end preparation


SmartPlant Isometrics Master Data data, an administrator should set the role assignments for the End Preparations screens to read-only on A.30.03.

Map symbol keys to commodity codes Each SKEY needs filter criteria to define the commodity codes belonging to the SKEY.

SKEYs can be mapped to commodity codes in different ways:

Group/Part only – Most useful for mapping an entire group or set of parts to a separate SKEY.

Group/Part with Table Details – Most useful for more complex environments where table details are required and have their own SKEY.

When you create filter criteria for table details, you must consider these rules:

Group - Rows with the same group number are enclosed in brackets when building the query.

Group Seq - Rows belonging to a group have a unique number within the group. This number is an order sequence used to sort the criteria when building the query.

Row Operator - Select AND or OR to determine how the table detail results are combined.

Within a group, the AND operator means that a commodity code must have both table details. The OR operator means that a commodity code must have at least one of the table details. All rows entered for a group must have the operator (AND/OR) except for the last row of this group.

Group Operator - Select AND or OR to determine how the results of each group are combined when calculating the total results.

The AND operator means that commodity codes must be in both groups. The OR operator means that commodity codes must be in one of the groups. The group operator (AND/OR) must be selected in the last row of all groups except for the last group.

Commodity Code – Most useful for mapping exceptions, which are all mapped to their own SKEY.

How the software determines the SKEY for a commodity code The following diagram explains the processing logic used to identify which SKEY belongs to a commodity code. Understanding this logic helps you to define SKEY mappings properly.



The "Yes, but 1:n" box means the mapping between the commodity code and SKEY is not uniquely defined. More than one SKEY is defined, and the process does not know which one to take.

1. Click Integration > XI10 SPIso > XI1020 Symbol Key Mappings.

2. On the Symbol Key Mapping tab (see bottom of window), map SKEYs to commodity codes.

When the SKEY mappings are done, it is possible that commodity codes are mapped to more than one SKEY, or the SKEY mapping is missing for commodity codes. Before you start an export, check the mapping. In addition, you can check the export log files.



Map symbol keys to attributes When exporting SmartPlant Isometrics catalog files, it is necessary to apply nominal sizes (Bores A – D) and physical lengths (Dimensions A – D) where applicable. For this purpose, appropriate attributes must be defined on A.50.01 Attributes and mapped to SKEYs. The SKEYs are mapped to attributes on the Attribute Mapping (Bore, Dim) tab.

1. Click Integration > XI10 SPIso > XI1020 Symbol Key Mappings.

2. On the Attribute Mapping tab (see bottom of window), map SKEYs to attributes.

Lists of values are available for each bore and dimension box. The list shows the attributes used by commodity codes belonging to one of the specified group or part records. You must select the group or part before the attributes can be mapped.

The Mandatory check boxes indicate if the attribute is required (check box selected) or optional (not selected). You must assign the mandatory attributes to store the attribute mapping.

Graphics assigned to the SKEY on the Define Skeys screen appear at the bottom of the tab. For more information, see Define symbol keys (on page 16).

Depending on the setup of your environment, it may be necessary to define new geometrics

and geometric relations to provide SmartPlant Reference Data Plus with all the information needed for the SmartPlant Isometrics catalogs.

For each SKEY, it is possible to define one set of attributes within the product group and one set within each project. When you run the export, the attribute set from the project is used where the user is logged in. If no attribute set is defined for the project, the set defined in the product group is used.



Map material attributes 1. Click Integration > XI10 SPIso > XI1020 Symbol Key Mappings.

2. On the Material Attributes tab (see bottom of window), define the material attributes.

SmartPlant Isometrics can handle up to 100 material attributes. You can define the

material attributes related to the SKEY after you have defined the mappings for group and part.

Define bolt mapping With this procedure, you prepare a specification for export to the SmartPlant Isometrics catalog by adding bolt information.


SmartPlant Isometrics Master Data 1. In SmartPlant Materials, open the S.50.06 Specification Management screen, and query

for the specification for which you want to define the mapping.

2. Double-click in the Spec Code box to open Window 2 where the specification items appear.


SmartPlant Isometrics Master Data 3. Select a specification item with a bolted part, and open the LOV in the Bolt Commodity

Code box on the Geometric tab.

4. Select a bolt commodity code from the list, and click OK.

The LOV for bolt commodity codes is restricted to show only commodity codes that are mapped to SKEYs marked as bolting material on the Define Skeys screen in SmartPlant Reference Data Plus.

5. Repeat steps 3-4 until all bolted parts of the specification have the appropriate bolt commodity codes assigned.


S E C T I O N 3

Export jobs are defined for a selected SKEY set.

Before you start an export job, check the SKEY mapping to see if commodity codes are mapped to more than one SKEY, or if SKEY mapping is missing for any commodity codes. For more information, see Map symbol keys to commodity codes (on page 19).

What do you want to do? Set up default sets (on page 25)

Define a new export job (on page 27)

Run an export job (on page 28)

Set up default sets 1. Click Integration > XI10 SPIso > XI1030 Export > XI103010 Export Job Default Sets.

2. In the upper grid, click Edit Grid .

3. Click Add Row .

4. In the Default Set box, type a name for this set.

5. Specify the other columns for this set, as needed.

6. Click Save Grid .

7. Click Read-Only Grid .

8. Select the row you just added in the upper grid.

9. In the lower grid, click Edit Grid , and add or modify details, as needed.

10. Click Save Grid .

11. Click Read-Only Grid .

All delivered details of the delivered standard set must be available in every new set. The

values are mandatory and must be filled.

When you create a new export job default set, the software automatically creates the standard default details. The new details are visible after you save the set, leave the Edit Grid mode, and select the new record.

The delivered export job defaults are listed in the following table.

Export Jobs


Export Jobs Name Description

BOLTCODELENGTH Length of the bolt commodity code.

BOLTDIAMETERUNITS Unit for the bolt diameter (mm or in).

BOREUNITS Unit for the bore (mm or in).

CONFIGURATIONMAP.XML Path to configurationmap.xml, which is delivered with SmartPlant Isometrics and is stored in the C:\Program Files\Common Files\Alias folder, by default.

DEFAULT SUPPORTS If set to TRUE, the software creates default supports automatically (TRUE or FALSE).

LENGTHUNITS Unit for the length (mm or in).

MAXBORES Number of maximum bores.

MDB EXPORT PATH Path where the SmartPlant Isometrics Access database is created (default is C:\).

MINTUBE Number of minimum tube lengths.

PULLEDBEND Pulled bend (TRUE or FALSE).

STANDARD Information only (like ANSI or DIN).

SYSTEMMATERIALMANAGER.XML

Path to systemmaterialmanager.xml, which is delivered with SmartPlant Isometrics and is stored in the C:\Program Files\Common Files\Alias\Data folder, by default.

USE OPTIONAL CODE If set to TRUE, use the commodity code instead of the ident code for bolt processing in SmartPlant Isometrics (TRUE or FALSE).

This setting is not inserted automatically when creating a new default set.

WEIGHTUNITS Unit for the weight.


Export Jobs

Define a new export job 1. Click Integration > XI10 SPIso > XI1030 Export > XI103020 Export Jobs.

2. In the upper grid, click Edit Grid .

3. Click Add Row .

4. Type a job name in the Job Code box.

5. (Optional) Change the number in the Run Number box if necessary. This value is set to 1 by default.

6. Select a pre-defined export definition set from the LOV in the Export Definition Set box.

7. (Optional) Delete or update the Bore Unit and Dim Unit values if necessary. These values are copied from the symbol key set entries.

8. (Optional) In the Comment box, type any text about the export job.

9. Click Save Grid in the upper grid.

10. Click Read-Only Grid in the upper grid.

11. In the lower grid, click Edit Grid .

12. Click Add Row .

13. In the Spec Code box, use the LOV to select a specification.

The LOV on the Export Jobs screen is restricted depending on the project default ZX_ALLSPEC (only issued specs are shown or all specs are shown). In addition, product group specs are only visible in the project if they have been released on A.20.10.

14. Click Save Grid in the lower grid.

The Status, Start User, Start Date, End Date, and Job Summary boxes are populated by

the job procedure and cannot be updated by the user.

The selected SKEY set in the tree on the left determines which set should apply to export processing. For more information, see Define symbol key sets (on page 15).

An export job can contain more than one specification. For each specification, a separate .mdb file is created.

To create a new export job from an existing job, select the existing export job, and click New Run at the top. A new export job is created from the selected job, with an incremented Run Number value.


Export Jobs

Run an export job 1. Click Integration > XI10 SPIso > XI1030 Export > XI103020 Export Jobs.

2. Select an export job, and click Start Export at the top of the Export Job grid.

The export job creates new Microsoft Access databases for each exported specification by

copying the template database.

The new database is stored in the directory that is assigned to MDB EXPORT PATH in the default set. The database gets the name of the exported specification.

The export job creates two log files; the files are stored in the utl file directory of the database. The first log file tracks the export procedure, and the second one the creation of the Access database.


S E C T I O N 4

After the data is searched and stored in the export tables, you can update the data in the export tables with the custom package M_PCK_SPISO_CUSTOM. The following procedures are called at the end of the export:

M_PCK_SPISO_CUSTOM.GENERAL_CIP

M_PCK_SPISO_CUSTOM.GENERAL_GET_BOLT

You can use these procedures to insert new data or update the exported data before the data is written to the Microsoft Access database.

In addition, the following procedures are available:

M_PCK_SPISO_CUSTOM.FORMAT_BOLT_CC - Customizes the standard logic for formatting the bolt commodity code.

M_PCK_SPISO_CUSTOM.GENERAL_BRANCH - Modifies the branch data stored in M_SPISO_EXP_SPEC_BRANCHES.*

M_PCK_SPSIO_CUSTOM.GENERAL_BEND - Modifies the bend data stored in M_SPISO_EXP_SPEC_BENDS.*

* These two CIPs run at the end of the database part of the export processing after the M_SPISO_EXP_BRANCHES and M_SPISO_EXP_SPEC_BENDS tables are populated

according to standard processing logic.

Export tables M_SPISO_EXP_SPEC_ASSOC_MTLS

Name Data Type

SESAM_ID NUMBER(12,0) NOT NULL

SPIES_ID NUMBER(12,0) NOT NULL

ITEM_CODE VARCHAR2(60) NOT NULL

ASSOC_ITEM_CODE VARCHAR2(60) NOT NULL

QUANTITY NUMBER(15,3) NOT NULL

PROJ_ID VARCHAR2(10) NOT NULL

USR_ID VARCHAR2(10) NOT NULL

LMOD DATE NOT NULL

Customization


Customization Name Data Type

INT_REV NUMBER(6,0) NOT NULL

M_SPISO_EXP_SPEC_CCS

Name Data Type

SPIESCCS_ID NUMBER(12,0) NOT NULL

SPIES_ID NUMBER(12,0) NOT NULL

ORDER_SEQ NUMBER(5,0) NOT NULL

SPIS_CODE VARCHAR2(4 CHAR) NOT NULL

SPIC_NUMBER VARCHAR2(6 CHAR) NOT NULL

SPIG_NUMBER VARCHAR2(6 CHAR) NOT NULL

SPICT_NUMBER VARCHAR2(6 CHAR) NOT NULL

COMMODITY_CODE VARCHAR2(60 CHAR) NOT NULL

FROM_SIZE1 VARCHAR2(12 CHAR) NOT NULL

TO_SIZE1 VARCHAR2(12 CHAR) NOT NULL

UNIT_CODE VARCHAR2(10 CHAR) NOT NULL

CC_DESCRIPTION VARCHAR2(1024 CHAR)

OPTION_CODE VARCHAR2(10 CHAR) NOT NULL

M_SPISO_EXP_SPEC_IDENTS

Name Data Type

SPIESI_ID NUMBER(12,0) NOT NULL

SPIESCCS_ID NUMBER(12,0) NOT NULL

INDEX_NUMBER NUMBER(6,0) NOT NULL

IDENT_CODE VARCHAR2(60 CHAR) NOT NULL

IDENT_DESCRIPTION VARCHAR2(1024 CHAR)


Customization Name Data Type

BORE_A VARCHAR2(10 CHAR) NOT NULL

BORE_B VARCHAR2(10 CHAR) NOT NULL

BORE_C VARCHAR2(10 CHAR) NOT NULL

BORE_D VARCHAR2(10 CHAR) NOT NULL

DIM_A VARCHAR2(10 CHAR) NOT NULL

DIM_B VARCHAR2(10 CHAR) NOT NULL

DIM_C VARCHAR2(10 CHAR) NOT NULL

DIM_D VARCHAR2(10 CHAR) NOT NULL

WEIGHT VARCHAR2(10 CHAR) NOT NULL

UNIT_BORE VARCHAR2(10 CHAR)

UNIT_LENGTH VARCHAR2(10 CHAR)

UNIT_WEIGHT VARCHAR2(10 CHAR)

BOLT_COMMODITY_CODE VARCHAR2(70 CHAR)

BOLT_QUANTITY VARCHAR2(3 CHAR)

UNIQUE_COMMODITY_CODE

VARCHAR2(70 CHAR)

ATTRIBUTE1 VARCHAR2(20 CHAR)

ATTRIBUTE2-99 VARCHAR2(20 CHAR)

ATTRIBUTE100 VARCHAR2(20 CHAR)

BOLT_DIA VARCHAR2(10 CHAR)

BOLT_LENGTH VARCHAR2(10 CHAR)

SCHEDULE_RATING VARCHAR2(80 CHAR)

MATERIAL VARCHAR2(80 CHAR)

STANDARD VARCHAR2(255 CHAR)


Customization


S E C T I O N 5

This section describes the logic that is used to populate the branch selection table in the Microsoft Access database.

All idents (with the same group and part defined in the branch table that is attached to the specification and in the defined range) of the specification are exported to the branch selection table for SmartPlant Isometrics.

The Operation field in the branch selection table is populated with None for all idents corresponding to physical parts like tees or weldolets. Set-on type branch connections require a dummy part that represents the operation.

The available operations in SmartPlant Isometrics are SetOn, Tap, ReinforcedSetOn, and PulledSetOn. If you want to use an operation other than None, you must:

1. Define the attribute BRANCH_OPERATION.

2. Attach this attribute to M_PARTS.

3. Define a dummy part that represents the branch operation.

4. Add this dummy part to the branch table.

Branch Selection Table



Define the branch operation 1. On the A.50.01 Attributes screen, create a new attribute with the exact name

BRANCH_OPERATION as displayed in the following picture.

2. Click the Next Block button to open Window 2.

3. Define allowed values for the attribute as displayed in the following picture.

These valid values are used to provide a LOV when you enter an attribute value. The valid values are also used to validate the entered attribute values.

4. Attach the new attribute to the physical table M_PARTS on the A.50.03 Tables/Attributes screen.

In this example, the BRANCH_OPERATION attribute is assigned to the ATTR_CHAR9 physical attribute (database column).


Branch Selection Table 5. On the S.10.03 Commodity Part screen, enter a value for the parts that have a branch

operation like SetOn, Tap, ReinforcedSetOn, or PulledSetOn.

For parts without a branch operation (None), you do not need to assign an attribute value to the part. None is the default value.

6. Define a dummy part that represents the branch operation.

Because it is non-physical material, do not create idents for this part. In the example above, the OPER-… parts are created for the non-physical material, with the attribute values SetOn, Tap, ReinforcedSetOn, and PulledSetOn assigned.

7. Use these dummy parts in the branch table. Open the S.40.05 Branches screen, select the branch table you want to edit, and click the Next Block button to open Window 2 where the branches are maintained.

8. Assign the dummy parts where applicable, using the LOV in the Part box.


S E C T I O N 6

This section describes the logic that is used to fill the bend selection table in the Microsoft Access database.

Define bend table 1. In SmartPlant Materials, define the GROUP and PART attributes on the A.50.01 Attributes

screen.

2. In the Derived From box, enter the following statement for the GROUP attribute:

SELECT CG.CG_GROUP_CODE, CGN.SHORT_DESC, CGN.DESCRIPTION FROM M_COMMODITY_GROUPS CG, M_COMMODITY_GROUP_NLS CGN WHERE CG.GROUP_ID = CGN.GROUP_ID(+) AND CGN.NLS_ID(+) = MPCK_LOGIN.CURRENT_NLS_ID ORDER BY CG.CG_GROUP_CODE

3. For the PART attribute, enter the following statement in the Derived From box:

SELECT P.PART_CODE, CG.CG_GROUP_CODE, PN.SHORT_DESC, PN.DESCRIPTION FROM M_PARTS P, M_COMMODITY_GROUPS CG, M_PART_NLS PN WHERE P.GROUP_ID = CG.GROUP_ID AND P.GROUP_ID = PN.GROUP_ID(+) AND P.PART_ID = PN.PART_ID(+) AND PN.NLS_ID(+) = MPCK_LOGIN.CURRENT_NLS_ID ORDER BY P.PART_CODE, CG.CG_GROUP_CODE

4. On the A.50.02 Tables screen, define a new table BEND with table type GEOM_S4013.

5. On the A.50.03 Tables/Attributes screen, assign three attributes to the BEND table:

Bend Selection Table



NPS (nominal pipe size), assigned to GD.IN1

GROUP, assigned to GD.IN2

PART, assigned to GD.IN3

6. Select the attribute from the LOV in the Attr Name box and the physical attribute (database

column) from the LOV in the Physical Attribute box.

7. Select the Required check box for all attributes.

8. Create the geometric table on the S.40.13 Filter Geometrics screen.

9. Enter the geometric name in the Geometric box.

The name must start with the string BEND, for example, BEND-10BD113.

10. Select the table name BEND from the LOV in the Tablename box.

11. Enter geometric descriptions in the Short Desc and Description boxes.

12. Select a standard from the LOV in the Standard box.

13. Save the new geometric.

14. Double-click in the Geometric box to open Window 2, where geometric details are specified.

15. Enter the nominal diameter in the Nps box, select the group from the LOV in the Group box,

and select the part from the LOV in the Part box.


Bend Selection Table 16. Attach this bend geometric to the specification on the S.50.06 Maintain Specification

screen.

17. On the Spec Header Geometric tab, select a short code from the LOV in the Short Code

box.

18. Select User defined from the LOV in the Table Type box.

19. Select the previously created bend geometric name from the LOV in the Table Name box.

20. Type the allowed range in the From1 and To1 boxes.

The Filter indicator must not be selected.

If you have defined the PULLEDBEND default with TRUE in the export job default set, the bends are inserted with operation = BendPipe. The component type for the bends is defined using the M_PCK_SPISO_CUSTOM.ComponentTypeForBendPipe CIP function.


A Assign graphics to symbol keys • 17

B Bend Selection Table • 37 Branch Selection Table • 33

C Create interface • 9 Customization • 29

D Define a new export job • 27 Define bend table • 37 Define bolt mapping • 22 Define component types • 13 Define configurations • 14 Define end preparations • 17 Define groups • 12 Define symbol key sets • 15 Define symbol keys • 16 Define the branch operation • 34

E Export Interface Configuration • 9 Export Jobs • 25 Export tables • 29

M Map material attributes • 22 Map symbol keys to attributes • 21 Map symbol keys to commodity codes • 19

P Preface • 7

R Run an export job • 28

S Set up default sets • 25 SmartPlant Isometrics Master Data • 11

Specify interface attributes • 10

Index


smartplant reference data plus smartplant isometrics...

Documents