Int PDMS
Int PDMS
Int PDMS
November 2014
DMAR1-PE-200010I
Copyright
Copyright © 2000-2014 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.
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 license
agreement 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.
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, SupportModeler, Sapphire, and FreeView 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.
Introduction .................................................................................................................................................. 9
Configuration ............................................................................................................................................. 11
DBA Settings ......................................................................................................................................... 11
Project Defaults ..................................................................................................................................... 11
SQL_PATH ........................................................................................................................................... 11
Definition of the PDMS Interface........................................................................................................... 12
Index ........................................................................................................................................................... 91
Documentation Comments
Send documentation comments or suggestions to PPMdoc@intergraph.com
(mailto:ppmdoc@intergraph.com?subject=documentation comments).
Introduction
This guide describes how to configure the PDMS interface in SmartPlant Materials. There are
several steps required to work with the PDMS interface.
The PDMS interface contains two different types of transfers: ident transfer and specification
transfer. Some steps are the same for both kind of transfers, and some are only for one type of
transfer.
The transfer generates a set of ASCII files that can be separated into one file for the
specifications (SPECON) and a set of files for the ident transfer. For more information about the
purpose of each individual file, see Ident Transfer (on page 13).
These files are loaded into PDMS.
Configuration
Check the following configuration settings:
DBA Settings
PLUS_EXECUTABLE: Enter the SQL plus version with which the scripts will be worked.
PDMS_DOWNLOAD_DEST: To enable the file download, you must specify the file destination
on the application server. Here is an example of the value:
C:\SPMAT\download\
PDMS_DOWNLOAD_URL: To enable the file download, you must specify the URL of the file
destination on the application server. Here is an example of the value:
your_as_server/download
The name of the application server is followed by a virtual directory name.
For more information about these DBA settings, see SmartPlant Materials DBA Settings,
available from the Printable Guides page in the software.
Project Defaults
ZI_PDMS_ZI: Must be set to Y if you want to download all created spoolfiles bundled in a ZIP
file.
For more information about project defaults, see SmartPlant Materials Project Defaults,
available from the Printable Guides page in the software.
To know which steps are necessary to enable the ZIP feature in SmartPlant Materials, refer to
the SmartPlant Materials Installation and Migration Guide, also available from the Printable
Guides page in the software.
SQL_PATH
The application server registry entry for SQL_PATH points to the folder where the files
necessary for the PDMS interface are located.
These scripts are delivered with the SmartPlant Materials installation and are automatically
placed in the right location.
Ident Transfer
Depending on the file type (PDMS 20.01 Create PDMS Files), various files are created. The
ones you need depend on the way you work with PDMS and the way you want to use your
existing data in PDMS. A PDMS expert should help you make this decision.
You can also influence the building of text built here; it comes from the CIP
m_pck_pdms_custom.text.
If a commodity code has no SKEY (SKEY = ‘NONE’), a blank line for SKEY will be written.
pdms_d.del Contains information about detail text that is no longer contained opposite
the last run in the PDMS_D.dat (Ident). (When an ident in SmartPlant
Materials is deleted, it is written in this file. It should be deleted in PDMS,
too.)
pdms_d.err Contains information about errors that occurred during the detail text
transfer.
pdms_c.del Contains information about weights that are no longer contained opposite
the last run in the PDMS_C.dat (Ident). (When an ident in SmartPlant
Materials is deleted, it is written in this file. It should be deleted in PDMS,
too.)
pdms_c.err Contains information about errors that appeared during the component data
transfer.
Geometrics (PDMS_G.DAT)
Contains the geometric information and all needed references to geom. set, point set, data set,
and bolt reference.
<START> CATA SECT CATE SCOM
GTYPE
GMREF
PTREF
DTREF
PARAM N1 .. N13
BLRFA
pdms_g.err Contains information about errors that occurred during the geometric
transfer.
Flange-Bolt-Points (PDMS_F.DAT)
Contains all the information of the bolt ident that is referenced in the PDMS_G.dat file.
<START> CATA SECT CATE BTSE
NUMBER
DIAMETER
BTYPE
BTHK
On PDMS 30.01, you can define an additional attribute for the value that is added to the flange
thickness.
Also on PDMS 30.01, you can define more than one bolt.
pdms_f.del Contains information about SCOM that is no longer contained opposite the
last run in the PDMS_F.dat.
pdms_f.err Contains information about errors that occurred during the flange bolt
transfer.
The Insert into the table m_pdms_bolt_refs is moved completely into a CIP,
M_pck_pdms_custo.file_bolt_ref (p_pcc_id => internal ID from the job that is started in PDMS
20.01, p_commodity_Id => Primary of the commodity-code, p_input_1 => Diameter of the Bolt
ident)
pdms_bs.err Contains information about errors that occurred during the bolt set
transfer.
In the m_pdms_bolt_ref_errs table, you can report any data errors or problems encountered
during the CIP. This file contains these messages.
BoltLength: INPUT_2,
All commodity codes that are listed in the rule defined on PDMS 30.01
Configure PDMS field Rule for Bolts
IDENT: IDENT
pdms_b.del Contains information about SCOM that is no longer contained opposite the
last run in the PDMS_B.dat. (When an ident in SmartPlant Materials is
deleted, it is written in this file. It should be deleted in PDMS, too.)
pdms_b.err Contains information about errors that occurred during the bolt transfer.
Material (PDMS_M.DAT)
Contains the material text information.
<START> CATA SECT SMTE
XTEXT
YTEXT
ZTEXT
SMTE: default is TD_CODE || ‘_’ || TAB_ID (or table detail link) || ‘-M’
CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID,
'MATXT', INTERFACE_ID, NLS_ID, 'CODE')
For NLS_ID will be used the defined nls_id of PDMS 30.01 Configure
PDMS field Nls for RTEXT/XTEXT
If no Nls is defined for STEXT/YTEXT and/or TTEXT/ZTEXT, then a blank line will be written for
YTEXT and/or ZTEXT.
pdms_m.err Contains information about errors that occurred during the material text
transfer.
For the GTYPE attribute, insert the following Derived From clause:
Here you must define the tables for the PDMS interface. They must belong to the INTERFACE
table type.
You need one table for GTYPEs and one for SKEYs. The names of the tables are free format.
Table Attributes
This screen shows the GTYPE attribute with the SKEY table. Enter TD.CHAR1 in the Physical
Attribute field.
GTYPE Data
In the Import Type field, use the LOV to insert PDMS_GTYPE. In the Table Type Description
field, enter an existing table type description, and in the Table Type field, select INTERFACE.
In the Table Name field, enter the table name, which was defined in the previous step, for the
table GTYPE.
Do not change the mapname GTYPE. This is the interface table translation for PDMS.
Click the Display Import Rows button to see the default data.
Click the Start Import button.
SKEY Data
In the Import Type field, use the LOV to insert PDMS_SKEY. In the Table Type Description
field, enter an existing table type description, and in the Table Type field, select INTERFACE.
In the Table Name field, enter the table name, which was defined in the previous step, for the
table SKEY.
Do not change the mapname SKEY. This is the interface table translation for PDMS.
Click the Display Import Rows button to see the default data.
Click the Start Import button.
In this case, the catalog reference for PDMS is D31CG5WHM1TB000 and specifically for the
commodity code "D31CG5WHM1TB000" given above. Use the LOV in the Interface field in the
Interface Codes block to select ‘PDMS’ from the list. Then enter the PDMS specific code in the
Interf. Comm. Code field.
By default, the CATREF is reduced to 20 characters during the transfer.
PDMS Groups
Define a rule for the PDMS ident transfer. Enter at least one group code. This rule transfers all
idents that are under this group code.
You can also break down to a part code and commodity code, if you want to transfer a subset of
idents for this group code.
In the third block, you can reduce the commodity codes. Only commodity codes with the
inserted table details will be used.
Define a rule on PDMS 20.04 for all bolt material.
This information will be used for PDMS_B.dat and PDMS_BS.dat. The INPUT_1 of the bolt
idents must be the diameter; the INPUT_2 must be the bolt length.
You can also break down to a part code and commodity code, if you want to transfer a subset of
bolt idents for this group code.
In the third block, you can reduce the commodity codes. Only commodity codes with the
inserted table details will be used.
PDMS Configurations
Use the PDMS 30.01 Configure PDMS screen to configure the origin and/or the defaults of the
data for the PDMS transfer on PDMS 20.01.
These settings are project- or product group-specific. Product group settings affect only the
attached projects that do not have their own configuration. You can use the functionality to copy
the product group configuration to the logged on project.
The translated values are defined in the Dn Translation field on S.40.01 Window 2.
ATTR_NUM 1 - 3
You can query all G-types, which are table details of the table with the interface translation
‘GTYPE’ for PDMS (A.50.I.01 Interface Tables).
The needed parameter list can vary from G-type to G-type. The parameter positions (Parameter
Seq) can have another meaning within different G-types.
GType FILT
GType CROS
Type Geometric
For all geometry attributes that will be used, you must have a translation for the PDMS interface
on A.50.I.02 Interface Attributes.
For the attributes such as diameter, length, thickness, and so on, PDMS needs a suffix (in), if
you want to use the imperial unit system. The default suffix will be the unit code of the attribute
(Unit field ). If you have entered an interface dependent unit (A.10.14), then the interface unit is
used as the suffix. With the Use Unit indicator, you can determine which attribute needs a suffix.
This is only required for the unit inch. If no suffix is attached to the parameter, PDMS knows that
you are working with the metric unit mm (millimeter).
With the selection in the Value defined in field on PDMS 30.02, you define the origin of the
value. The available fields are: TD_CODE, ATTR_CHAR1, ATTR_CHAR2, ATTR_CHAR3,
ATTR_NUM1, ATTR_NUM2, and ATTR_NUM3.
Type CIP
If you want to get the values from a CIP (customer-defined procedure), you can select all
functions from the valid package M_PCK_PDMS_CUSTOM (owner M_SYS) with the input
parameter P_IDENT.
M_PCK_PDMS_CUSTOM specification:
/*
|| function example_cip_pdms3002
||
|| this is only an example for a CIP function, which will be used in PDMS
30.02
|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.
|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)
||
*/
FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)
RETURN VARCHAR2;
M_PCK_PDMS_CUSTOM body:
/*
|| function example_cip_pdms3002
||
|| this is only an example for a CIP function, which will be used in PDMS
30.02
|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.
|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)
||
*/
FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)
RETURN VARCHAR2
IS
v_return VARCHAR2(19);
BEGIN
v_return := 'CIP example';
--
RETURN v_return;
END example_cip_pdms3002;
Enter the export path for the PDMS files in the Export Path field, and enter the export file name
in the Export File field.
The Project Filter field specifies how the idents are filtered according to the project or product
group: only idents from the logged in project or also from the attached product group.
The Spec Filter field specifies how to filter the idents against specifications. The purpose of this
setting is to reduce the amount of output data.
Use the Restrictions button or the next block arrow to insert the predefined rules for this PDMS
job.
Enter your predefined rules (PDMS 20.04 PDMS Groups). You do not need to enter the rules
for the bolts, which are only defined for the PDMS 30.01 Configure PDMS screen.
Click the Create File button to start the PDMS ident transfer. A message appears to inform you
about the SQL Plus version. This information about the DBA setting is useful if there is a
problem in the creation of the spool-files.
After the transfer has finished, you can see all relevant job information in the History
Information section.
Click the button to display error information about the PDMS ident transfer.
Specification Transfer
Create a standard Specon file or an Insulation Spec (PDMS 10.02 Create PDMS Spec-File
screen).
In addition to the Specon file, you can create various files on the PDMS 20.01 Create PDMS
Files screen. The files are: PDMS_D.DAT, PDMS_C.DAT, PDMS_B.DAT, PDMS_BS.DAT, and
PDMS_M.DAT. For more information, see Ident Transfer (on page 13).
The ways you want to work in PDMS and use your existing PDMS data determine the files you
need. A PDMS expert should help you make this decision.
Select the Delta check box on PDMS 10.02 to compare the spec against a delta result. Four
files are created:
The new file containing all lines from the actual spec.
The insert file containing all lines that are added (new NAMEs) compared to the delta result.
The modify file containing all lines that have the same NAME but other attributes changed.
The delete file containing all lines that were removed in comparison to the delta result
(NAME).
Double-click in the Spec Code field to open PDMS 10.03 Show Log Entries to view the job
marked as the delta job. After the spec transfer finishes, the actual job will become a delta job.
Generally, delta creation depends on the setting of the 'Spec Rev Delta Handling' item. If it is set
to 'Autonomous' and the spec transfer has finished, the delta indicator of all jobs of the same
spec revision (except the actual one) is cleared, but the delta indicator of other revisions is left. If
a new job is started afterwards (in another revision) and it will pick up a delta, it first looks if
there is a delta job in its own revision and only if not, looks in a lower revision. Revisions are
autonomous related to another (multiple delta indicators are allowed per spec, one per each
revision).
If 'Spec Rev Delta Handling' is set to 'Merge', and the spec transfer has finished, the delta
indicator of all jobs of the same spec (code, type, project) is cleared (except the actual one). If a
new job is started afterwards (in another revision) and it will pick up a delta, it looks from the
latest to the oldest revision of the same spec and compares the job to the first delta job found.
The revisions are merged related to another with respect to the delta creation.
If you plan to transfer the same spec in different revisions in the same run, the delta job indicator
will be updated as soon as a spec is transferred. The delta job can also be in another spec
revision than the actual one, so you might get unexpected results running the same spec in
different revisions in the same run.
You can check Reset to let the update-file contain all current lines, not only those that changed.
The Copy option tells the transfer to read the SmartPlant Materials spec or copy the result set of
a job that is marked as 'Master' on PDMS 10.03. If you choose Copy, the contents of the actual
SmartPlant Materials spec do not play any role.
You must not enter the attributes TYPE and NAME, because these are always part
of the header and also always come at the beginning. Here only those attributes are defined that
you need in addition.
The following table explains where SmartPlant Materials gets the information if the attribute in
the PDMS header is referenced.
BLTREF '/' and bolt_commodity_id and '-' and the value of the geometry attribute for
the related ident, which is mapped on A.50.I.02 for ‘PDMS’ interface with the
translation ‘BDIA’
BDIA input 1
BAUL the value of the geometry attribute for the related ident, which is mapped on
A.50.I.02 for ‘PDMS’ interface translated as ‘LGTO’
You need at least one table for the PDMS header, SHOP, STYP, BTYP, ANGLE, GTYPE, and
RADIUS.
It is important that the name of the table be PDMS_HEADER_XY , where XY is a combination of
numbers.
In the Table Name field, enter the table name, which was defined in the previous step, for the
table GTYPE.
Do not change the mapname GTYPE. This is the interface table translation for PDMS.
Click the Display Import Rows button to see the default data.
Click the Start Import button.
It is important that the translation of the material table be MATXTxy , where xy is a combination
of free format characters.
Table Attributes
Here you can define the attributes from which the description of a PDMS file is composed.
Enter the accompanying commodity code of the bolts in the Bolt Commodity Code field. You
can use this commodity code in your CIP to build the bolt references in the spec file. The
internal column name in the table m_spec_items is bolt_commodity_id.
In this case, the catalog reference for PDMS is D31CG5WHM1TB000 and specifically for the
commodity code "D31CG5WHM1TB000" given above. Use the LOV in the Interface field in
the Interface Codes block to select ‘PDMS’ from the list. Then enter the PDMS specific code in
the Interf. Comm. Code field.
By default, the CATREF is reduced to 20 characters during the transfer.
In the second block, you create the assignment of the SmartPlant Materials short codes to the
PDMS terms.
In the GType field, enter a Gtype. The entry is checked against the S.20.I.03 tablename for
Gtypes (Translation = GYTPE). If a Gtype is missing, it must be entered on S.20.I.03. An LOV is
available and contains all valid Gtypes from S.20.I.03.
During the transfer, the Gtype is reduced to 4 characters.
In the GType Config field, select a pre-defined GType configuration from the LOV.
With the PBORx check boxes, you can define at which places the nominal sizes should be
stored in the spec file.
You can order the PBOR values in the Specon file such that the larger bore value comes first
and then the smaller bore. For this purpose, the Order PBORs check box must be selected. If
this check box is selected, the PBORs are ordered from larger bore to smaller bore for the
selected GType.
Post Processing
The PDMS 10.04 Create Procedures and PDMS 10.05 Spec Type Procedure Relations
screens allow for the definition of post processing procedures for the PDMS interface.
On the PDMS 10.04 Create Procedures screen, you can define and maintain procedures.
Enter the name of the procedure in the Procedure field. Then define the procedure in
the Procedure Body field. Click the Check button to validate the syntax of the procedure.
Validation is also done automatically for each record when scrolling through this block. The
validation result is always displayed in the Check Result field. Click the Execute button to
execute the selected procedure immediately. The Standard check box indicates a standard
procedure delivered with the software.
On the PDMS 10.05 Spec-Type-Procedure Relations screen, you can link the procedures to
the spec type and run them automatically after the Specon file is generated.
Select the spec type in the first (S.50.02 Specification Types) block. Then assign the
procedures to the selected spec type in the second (Spec-Type-Procedures) block. Enter a
sequence number in the Seq field; this number controls the order of the procedure execution.
Select the procedure from the LOV in the Procedure field. The Project/PG field is filled
automatically with the login project/product group.
GType Configurations
The architecture of the PDMS attributes is flexible enough that a new attribute can be added
without any restriction of having the attribute as a physical column in the table
M_PDMS_SPEC_IDENTS. A provision for the addition of 40 attributes has been provided.
A.50.03 attribute mappings are no longer considered during the export of the Specon file.
The PDMS 10.06 GType Configurations screen is used to store GType configurations and
GType configuration details.
This screen allows flexible attribute handling. On this screen, you can map the attribute to the
physical attribute of table M_PDMS_SPEC_IDENTS. There is a provision for 40 attribute
mappings. You can specify the default value for an attribute.
You can control which attribute is to be written to the file by selecting the Header Column?
check box.
You can also control whether to prefix the attribute value with Specon the word TEXT by
selecting the appropriate option from the drop-down list in the Prefix Text? field. The following
options are available:
Always - TEXT is always prefixed to the attribute value.
Alpha Numeric - TEXT is prefixed only when the attribute value is alphanumeric.
Never - TEXT is not prefixed.
You can specify a default value for the attribute in the Default Value field in the Gtype Config
Details block of PDMS 10.06. The DEFAULTS section of the Specon file will consider the
values specified in this field.
This configuration can then be linked to the GType on the PDMS 10.01 Short Code-GType
Mappings screen. The GType will be exported as per the GType Config linked.
Clicking the Use product group details button displays a message that the current project
configuration details will be deleted and replaced by the product group details.
Click Yes to continue. The button label changes back to Copy product group details.
The Missing CATEREFs and Missing GTypes buttons allow you to search for missing
information. You can click them before or after the transfer has finished. For more information,
see Missing CATREFs (on page 59) and Missing GTypes (on page 60).
You can specify the order-by criteria within the GTypes using the Sort Order in GTypes button.
Click this button to open a new window where you can specify the order preferences of the
attribute codes used in GType configurations. The contents of the generated Specon file will be
ordered according to these preferences. The order preferences are project dependent.
After querying on this screen, all pipe classes of the project appear. You can use the Spec Type
field to filter the specifications based on the selected specification types.
Using the Display Options group, you can filter the displayed specs based on their revision and
whether they are issued or not. Select All to display all specs regardless of their revision and
issue status; select Highest Rev. Issued or not to display only the highest revision of a spec
regardless of whether they are issued or not; select Not Issued and Highest Rev to display
only the specs that are not issued and that have the highest revision number.
If the default ZI_PDMS_IS is set to Y, the not issued specifications do not appear on
PDMS 10.02.
You can click the left Select All button to mark the Sel check box of all displayed specifications.
Click the left Deselect All button to cancel the current selection.
You can click the right Select All button to mark the Delta check box of all displayed
specifications. Click the right Deselect All button to cancel the current selection.
The two check boxes on the left side indicate whether or not all necessary mapping work has
been done for the pipe class in each case.
CR - A Catalog Reference in S.30.I.01 was assigned (definition PDMS-CATREF per
SmartPlant Materials commodity code) to all commodity codes of the pipe class
GT - A GType in PDMS 10.01 was assigned (mapping of GTypes, header, details with
SmartPlant Materials short codes and option codes) to all short codes of the pipe class.
With the PBOR translation feature, the PBORs can be translated from either IN to MM or MM to
IN when creating PDMS spec files. If the value of the dropdown list in the PBOR Translation
field is set to ‘IN to MM,' the PBORs will be translated from IN to MM for a specification being
transferred to PDMS. If PBOR Translation is set to ‘MM to IN,' the PBORs will be translated
from MM to IN.
The PBOR translation is considered only if UOM is not turned on.
Before you can start the transfer, you must select at least one specification by selecting the Sel
indicator and entering a path in the Export Path field (manual input, via LOV, or Save button).
If the Run CIP indicator next to the Transfer selected Specs button is selected, the custom
procedure M_PCK_PDMSEXP_CUSTOM.PUBLISH will be executed after the transfer job
finishes successfully.
When you click the Transfer selected Specs button, a message appears. Click Yes to start the
transfer.
When the creation of the spec file is completed, the following message appears.
Click Yes to generate the component files. The PDMS 20.01 Create PDMS Files screen opens.
Specify the job information (except project filter and spec filter) on PDMS 20.01, and then click
the Create File button to create the component files. The content of the component files is
driven by the idents of the specifications selected on the PDMS 10.02 Create PDMS Spec-File
screen.
Both the spec files and the component files are downloaded into a single zip file.
When the component file generation is done, the following message appears.
Click OK to continue. Next you can decide to download the created files.
Click Yes to download the files or No to end the job. Then close PDMS 20.01 to go back to
PDMS 10.02.
When the transfer is completed, you can double-click in the Spec Code field to open the PDMS
10.03 Show Log Entries screen.
In the first (Specification Headers) block, the selected specification is displayed with revision
and descriptions.
In the second block, the revisions of the transfer jobs for the selected specification are displayed
depending on the setting of the Display Revisions group. The jobs are shown with the job
number, revision, and date and time when it was executed. If the Master check box is checked,
you can use this job as a master for the next transfer run. Select the Delta check box to use the
job's result to compare with the next transfer result. The Action field shows the action of the
transfer job. The available options are listed below.
First creating - The first time when creating a transfer file for this specification.
New - A new spec file regardless of any delta logic.
Update from previous inserted - A job including delta management.
The number of records written to the NEW file is shown in the New field. The number of records
written to the INSERT file is shown in the Insert field. The number of modified lines is shown in
the Modified field. The number of records written to the DELETE file is shown in the Deleted
field. When this job has created an insulation spec file, the Insu indicator is checked. The Reset
check box is used for delta management. If the Master Job field is filled with a job number, the
actual job result was copied from the result of this job. If the Delta Job field is filled with a job
number, the actual job result was compared to the result of this job number.
Click the Next Block button to open Window 2 with the data of the selected job.
The GType Config data corresponding to the job are shown in the second (GType Configs)
block. For each GType the specification item idents data is shown in the third (PDMS Spec Item
Idents) block.
While generating a Specon file from the PDMS 10.02 Create PDMS Spec-File screen,
when two PBORs (for example, PBOR0 and PBOR1) are checked and there is no value
specified for the INPUT_2 of the corresponding specification, the INPUT_1 value is considered
as the value for INPUT_2 also.
If the project default ZI_PDMS_SN is set to Y, the Add, Delete, Modify, and New specification
files are merged into a single specification file. The merged specification file name is prefixed
with ‘mer’. The contents of the merge file are structured as follows:
$* Piping specification File for all items
<< new specs >>
$*
$* Piping specification File for additionally inserted items
$* ----------------------------------------------------------
<< inserted specs >>
$*
$* Piping specification File for modified items
$* ----------------------------------------------------------
<< modified specs >>
$*
$* Piping specification File for deleted items
$* ----------------------------------------------------------
<< deleted specs >>
You can link a specification to others. Right-click in the Spec Code field to open the pop-up
menu.
Select the Spec Links option to open a new window where you can link other specifications to
the selected specification.
Missing CATREFs
Click the Missing CATREFS button. A new window opens, displaying a list of all the commodity
codes for the pipe class to which no catalog references have been assigned yet.
You can enter the missing catalog references when you click the Maintain CATREFs in
S.30.I.01 button. Click the Back button to close this window.
Missing GTypes
Click the Missing Gtypes button. A new window opens, displaying a list of all the short codes of
the pipe classes to which no GType has been assigned.
You can enter the missing GTypes when you click the Maintain missing GTypes button. Click
the Back button to close this window.
$M %PMLLIB%\cpsimportmarian\MARIAN-COCO.mac
5. Select the type of file and its directory location, and then click OK.
6. On the Import dialog box, click Import.
The files are imported in the following order:
*_M.DAT - Material text
*_D.DAT - Detail text
*_B.DAT - Bolt diameter table
*_BS.DAT - Standard bolts elements
Follow the same steps as described in Creating a Catalog in PARAGON Module (on page
63).
Creating Specifications
Specifications are created in the standard way in SPECON.
Example
Specon File
$* Piping specification File for all items
$* Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 - 2010,
Intergraph Corporation
$* SPMat - PDMS SPECS INTERFACE - SPEC CREATING DATE : 13-JAN-10
$* on 13-01-2010 at 15:23 $*
Number of Records: 57
$*-- **** Project - No. **************
$* PROJECT 'LIB_INGR'
$*-- **** Project - No. **************
NEW SPECIFICATION /FLOW_DIR
MATREF =0
FLUREF =0
RATING 0.100
LINETYPE NULL
Text 'PIPING'
BLTM 'NEW'
HEADING
TYPE NAME PBOR0 SUFF SHOP CATREF DETAIL MATXT CMPREF BLTREF
DEFAULTS
- - - = =
TUBE */I4199422 100 PREF TRUE /PDPR---B01--1-KP00_100-SCOM /4199422-D
/B01-2_32248-M /4199422-C =0
TUBE */I4199423 125 PREF TRUE /PDPR---B01--1-KP00_125-SCOM /4199423-D
/B01-2_32248-M /4199423-C =0
TUBE */I4199424 15 PREF TRUE /PDPR---B01--1-KP00_15-SCOM /4199424-D
/B01-2_32248-M /4199424-C =0
TUBE */I4199425 150 PREF TRUE /PDPR---B01--1-KP00_150-SCOM /4199425-D
/B01-2_32248-M /4199425-C =0
TUBE */I4199426 20 PREF TRUE /PDPR---B01--1-KP00_20-SCOM /4199426-D
/B01-2_32248-M /4199426-C =0
HEADING
TYPE NAME PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - - = =
FLAN */AAFSBF0DD 15.00 15.00 TEXT 'FLSW1' TRUE /AAFSBF0DD /6497796-D
/S54U_502950-M /6497796-C =0
EXTRA :TP-IDENT 'C5FN5D'
EXTRA :TP-COMMCODE 'FSW1S54U22D01'
FLAN */AAFSBF0EE 20.00 20.00 TEXT 'FLSW1' TRUE /AAFSBF0EE /6397957-D
/C54X_502950-M /6397957-C =0
EXTRA :TP-IDENT 'C5CWFZ'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
HEADING
TYPE NAME PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - - = =
FLAN */AAFSBF0FF 25.00 25.00 TEXT 'FLSW1' TRUE /AAFSBF0FF /6397958-D
/C54X_502950-M /6397958-C =0
EXTRA :TP-IDENT 'C5CWG0'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
FLAN */AAFSBF0HH 40.00 40.00 TEXT 'FLSW1' TRUE /AAFSBF0HH /6397959-D
/C54X_502950-M /6397959-C =0
EXTRA :TP-IDENT 'C5CWG1'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
HEADING
NAME TYPE PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - - = =
*/AAFSBF0DD FLAN 15.00 15.00 TEXT 'FLSW1' TRUE /AAFSBF0DD
/15858200-D /S54U_502950-M /6497796-C =0
EXTRA :TP-IDENT 'C5FN5D'
EXTRA :TP-COMMCODE 'FSW1S54U22D01'
*/AAFSBF0EE FLAN 20.00 20.00 TEXT 'FLSW1' TRUE /AAFSBF0EE /632500007-D
/C54X_502950-M /6397957-C =0
EXTRA :TP-IDENT 'C5CWFZ'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
*/AAFSBF0FF FLAN 25.00 25.00 TEXT 'FLSW1' TRUE /AAFSBF0FF /63002456-D
/C54X_502950-M /6397958-C =0
EXTRA :TP-IDENT 'C5CWG0'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
*/AAFSBF0HH FLAN 40.00 40.00 TEXT 'FLSW1' TRUE /AAFSBF0HH /6397959-D
/C54X_502950-M /22200-C =0
EXTRA :TP-IDENT 'C5CWG1'
EXTRA :TP-COMMCODE 'FSW1C54X22D01'
D. Removing a Component
Reference is made to cases A, B, and C, which are supposed to be loaded before D.
REMOVE */AAFSBF0DD
REMOVE */AAFSBF0EE
REMOVE */AAFSBF0FF
This format is necessary to remove components that are no longer needed from the spec. Old
information will be switched from an active spec to a hold spec named LIMBO by PDMS.
No header is needed to proceed.
The spec header contains:
DESC ‘Revision date …..’
This is controlled by a CIP.
Text 'INSUL'
HEADING
TYPE NAME TEMP PBOR0 CATREF DETAIL
INSU */IN4497032 101,200 10mm,50mm /IS40 /DE.INS
INSU */IN4497033 101,200 80mm,200mm /IS50 /DE.INS
INSU */IN4497034 201,400 10mm,50mm /IS60 /DE.INS
INSU */IN4497035 201,400 80mm,200mm /IS80 /DE.INS
INSU */IN4497036 0,100 10mm,200mm /IS40 /DE.INS
PDMS_B.DAT
$*#PDMS Interface - BOLT_DIAMETERS#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
PDMS_BS.DAT
$*#PDMS Interface - SingleBolt#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_bs.dat
$*-- Delete File : C:\temp\pdms\pdms_bs.del
$*-- Errors and Warnings in : C:\temp\pdms\pdms_bs.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts 1----------------
$*-- -------------------------------------------------------
$*--
27 27 4 4
PDMS_C.DAT
$*#PDMS Interface - SingleBolt#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_bs.dat
$*-- Delete File : C:\temp\pdms\pdms_bs.del
$*-- Errors and Warnings in : C:\temp\pdms\pdms_bs.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts 1----------------
$*-- -------------------------------------------------------
$*--
27 27 4 4PDMS_C.DAT
PDMS_D.DAT
$*#PDMS Interface - Detail#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_d.dat
$*-- Deletefile : C:\temp\pdms\pdms_d.del
$*-- Errors and Warnings in : C:\temp\pdms\pdms_d.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts ----------------
$*-- -------------------------------------------------------
$*--
ELBW
Elbow 90° St37.0 DIN 2605 - no entry
PDMS_F.DAT
$*#PDMS Interface - FLANGE-BOLT-POINTS#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_f.dat
$*-- Delete File : C:\temp\pdms\pdms_f.del
$*-- Errors and Warnings in : C:\temp\pdms\pdms_f.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts ----------------
$*-- -------------------------------------------------------
$*--
STUD
PARAM 12
PDMS_G.DAT
$*#PDMS Interface - Catref#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation $*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_g.dat
$*-- Delete File : C:\temp\pdms\pdms_g.del
$*-- Errors and Warnings in : C:\temp\pdms\pdms_g.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts ----------------
$*-- -------------------------------------------------------
$*--
nulref
PDMS_M.DAT
1. $*#PDMS Interface - Detail#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- Call parameters:
$*--
$*-- PDMS Copy Job ID : 5261
$*-- Job Code : PDMS
$*-- Project (PG) : LIB_INGR
$*-- Started on : 20-NOV-2002
$*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log
$*-- Spoolfile : C:\temp\pdms\pdms_m.dat
$*-- Errors and Warnings in : C:\temp\pdms\pdms_m.err
$*--
$*-- -------------------------------------------------------
$*-- ---------------- Data Section starts ----------------
$*-- -------------------------------------------------------
$*--
Appendix: CIPs
PROCEDURE SET_S2008(p_log_id IN NUMBER);
Is called by the creation of the spec-file. This procedure summarizes all
calls to attributes in the spec-file which are mapped in the SmartPlant
Materials-screen S.20.08.
Returns the cate. Standard is the commodity code interfaced translation for
PDMS.
This function is used for the g.dat file. It is additional information about
the cate.
This function is used for the g.dat file. It is additional information about
the cate.
P_IDENT IN M_IDENTS.IDENT%TYPE,
P_LOG_ID IN NUMBER )
RETURN VARCHAR2;
This function is used for the g.dat-file and the spec-file. Standard is that
the function returns the cate and information about the Nominal Sizes.
FUNCTION GET_UNIT(p_commodity_id IN
m_commodity_codes.commodity_id%TYPE,
p_digit IN m_obj_parm_det.detail_id%TYPE)
RETURN VARCHAR2;
Looks for the unit of several Attributes.
FUNCTION get_insu_type
RETURN VARCHAR2;
This function returns the needed g-type reference for the spec file
FUNCTION get_insu_heading
RETURN VARCHAR2;
=>this function returns the needed heading fields for the spec file
p_pdms_si_id IN
m_pdms_spec_idents.pdms_si_id%TYPE);
CIP to fill the Bolt-related data into the specfile.
PROCEDURE file_bolt_ref(p_pcc_id IN
m_pdms_copy_ccs.pcc_id%TYPE,
p_commodity_id IN
m_commodity_codes.commodity_id%TYPE,
p_input_1 IN m_idents.input_1%TYPE);
FUNCTION COCO
(p_commodity_id IN m_commodity_codes.commodity_id%TYPE)
RETURN VARCHAR2;
Get the connection-type for g.dat-file.
FUNCTION IDENT_ATTRS
(P_IDENT IN m_idents.ident%TYPE,
P_INTERFACE_ID IN m_interfaces.interface_id%TYPE)
RETURN VARCHAR2;
Fill the parad-line in the g.dat-file.
FUNCTION DTSE
(P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE,
P_INTERFACE_ID IN m_interfaces.interface_id%TYPE)
RETURN VARCHAR2;
Only for the dataset used. The dataset describes the attribute-set which
you transfer with the g.dat-file. This file-type is only available when in
PDMS 30.01 the checkbox ‘With dataset?’ is marked.
FUNCTION SKEY
(P_INTERFACE_ID IN m_interfaces.interface_id%TYPE,
P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE)
RETURN VARCHAR2;
Returns the skey for the d.dat-file.
Fill the heading lines like ‘MATREF’, ‘RATING’. You can change the default
here.
A G
A. Creating a New Specification • 72 Geometrics (PDMS_G.DAT) • 15
Appendix G-Type Attribute Mapping • 31
CIPs • 85 GType Configurations • 52
File Examples • 69
Assigning Bolts to Specification Parts • 47 I
Assignment of Interface Details to Parts •
26, 50 Ident Transfer • 13
Attribute Translation for PDMS • 21, 43 Ident Transfer Files • 13
Attributes for Ident Transfer • 20 Importing GTYPE and SKEY Data • 24
Attributes for Spec Transfer • 41 Importing GTYPE Data • 44
Installing the PDMS Interface Software • 61
Introduction • 9
B
B. Creating a New Component in an L
Existing Specification • 72
Bolt Length (PDMS_B.DAT) • 18 Loading SmartPlant Materials Files into
PDMS (User Guide) • 61
C
M
C. Modifying a Component in a
Specification • 73 Material (PDMS_M.DAT) • 19
Component Data (PDMS_C.DAT) • 14 Missing CATREFs • 59
Configuration • 11 Missing GTypes • 60
Copy Product Group Details • 53
Creating a Catalog in PARAGON Module • P
63 PDMS CATREFs Defined per Commodity
Creating Component Data • 66 Code • 27, 49
Creating Specifications • 67 PDMS Configurations • 29
Creating Standards for COCO table, PDMS File for Spec Transfer • 54
GMSE, PTSE, DTSE • 61 PDMS Files for Ident Transfer • 37
Creating UDA Attributes • 63 PDMS Groups • 28
PDMS Insulation File • 40
D PDMS Specon File • 40
D. Removing a Component • 73 PDMS_B.DAT • 74
DBA Settings • 11 PDMS_BS.DAT • 75
Definition of the PDMS Interface • 12 PDMS_C.DAT • 77
Detail Text (PDMS_D.DAT) • 13 PDMS_D.DAT • 79
PDMS_F.DAT • 80
PDMS_G.DAT • 82
E PDMS_M.DAT • 83
Example • 68 Post Processing • 51
Preface • 7
F Project Defaults • 11
Flange-Bolt-Points (PDMS_F.DAT) • 16
S
Short Code – Gtype Mapping • 50
T
Table Attributes • 24, 47
Table Translation for PDMS • 22, 45
Tables for PDMS • 22, 44