Академический Документы
Профессиональный Документы
Культура Документы
pdms1151/man16/doc1
issue 140403
PLEASE NOTE:
AVEVA Solutions has a policy of continuing product development: therefore, the
information contained in this document may be subject to change without notice.
AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO
THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
While every effort has been made to verify the accuracy of this document, AVEVA
Solutions shall not be liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing, performance or
use of this material.
This manual provides documentation relating to products to which you may not have
access or which may not be licensed to you. For further information on which Products
are licensed to you please refer to your licence conditions.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
This guide is intended for specialists who are responsible for building up and
maintaining the standard Catalogue databases within a PDMS project team.
Although in principle you have a lot of flexibility in the ways in which you can construct
the database hierarchy for PDMS Catalogues and Specifications, in practice it is very
important that you follow strict conventions within any given project to ensure complete
compatibility of all data within that project. Further, unless there are exceptional
reasons for not doing so, it is sensible to adopt common conventions for structuring all
PDMS databases within your company, thus simplifying the exchange of data between
projects.
If you intend to use the standard Cadcentre applications for building Catalogue
databases (using PARAGON) and for accessing those databases during the plant design
process (using DESIGN), it is important that your data structures are compatible with
those expected by the application macros. If this is not so, the transfer of information to
and from the databases might not work successfully and the applications could fail.
This guide explains, with some examples, the essential features of the conventions used
in building up the Catalogues and Specifications which are supplied by Cadcentre. You
must follow these conventions in your own Catalogues and Specifications if you want the
standard Cadcentre applications to work reliably with your data. In particular, some
parts of the Catalogue database have been used to store information which is essential
for the successful use of some design applications but which is not obvious catalogue
data by the conventional definitions; for example, the Hangers and Supports application
uses data stored in user-defined attributes in the Catalogues and Specifications to
access associated information needed by the application.
This version of the guide includes the detailed data needed by two major types of
application supplied for use with PDMS DESIGN:
• Chapter 2 details the conventions used for setting up the structural
Catalogues and Specifications used by the Cadcentre Beams & Columns and
Panels & Plates applications.
• Chapter 3 lists the full Specification Tables used to hold data specific to the
Cadcentre Hangers & Supports application.
This guide does not attempt to tell you how to build Catalogue databases; it only
summarises the final format for the data which you should seek to achieve. For details
of the commands and specific applications which you need to use to carry out your work,
refer to the following sources:
2.1 Catalogues
You must use the following conventions for structural catalogues so that the DESIGN
applications can recognise them and so that the PARAGON applications can use them:
• The PURPose of the CATAlogue must be set to one of the following: STL, FITT,
JOIN or PFIT. This ensures that any specifications and applications which are built can
recognise the correct catalogue element. Thus the steel Profile specification looks for the
purpose STL, the Joint specification looks for the purpose JOIN, the Fitting specification
looks for the purpose FITT and the Panel Fitting specification looks for the purpose
PFIT. A meaningful DESCription is also beneficial.
• The PURPose of the STSEction must be set to REF for Reference Data, PRFL for
Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.
• The PURPose of the STCAtegory must be set to REF for Reference Data, PRFL
for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.
• The GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This
ensures that specific restrictions can be applied to Joints and Fittings when building the
specifications. For example: any Section with a GTYPE set to BEAM can be used with a
Joint which has its GTYPE set to BEAM; any Fitting with a GTYPE set to FITT can be
used with any Fitting specification.
• The purpose of a CSTANdard is to let you define in a text string the type of
standard that is being used. It is used purely for information and administration of the
Catalogue. For example, the CSTANdard for British Sections is BS 5950.
The following diagrams illustrate the structure of the catalogues.
The basic layout of the catalogues is the same as for piping, i.e. where the reference data is stored, but the way
in which the data is separated differs.
CATA
Ref. Data
STSE
Pline
Set
PTSS
2.2 Datasets
The general purpose of Datasets is twofold :
• To let you query catalogue parameters
• To let you input design parameters via simple forms and menus
(See Paragon Reference Manual, Section 9.7.)
CATA
HPRF HPRF
CATA
HFIT HFIT
CATA
4M20 6M20
HJOI HJOI
C ATAlogue British
British
Description <string> Profiles
Profiles
Purpose STL
Cstandard <string>
BE AM BE AM ANG
STSEction Profile
Profile
Colum
Columns
ns Beam
Beamss Angle
Angle
Description <string> Ref.
Ref.Data
Data
Purpose PRFL
G type <word>
C ATAlogue DIN
DIN
Description <string> Profiles
Profiles
Purpose STL
Cstandard <string>
H I L
STSEction Profile
Profile
HHProfiles
Profiles I IProfiles
Profiles LLProfiles
Profiles
Description <string> Ref.
Ref.Data
Data
Purpose PRFL
Gtype <word>
C ATAlogue Fittings
Fittings
Description <string>
Purpose FITT
Cstandard <string>
STSEction Fitting
Fitting
Lugs
Lugs Stiffeners
Stiffeners Penetrations
Penetrations
Description <string> Ref.
Ref.Data
Data
Purpose FITT
Gtype <word>
CATAlogue Joints
Joints
Description <string>
Purpose JOIN
Cstandard <string>
STSEction End
End End
End Joint
Joint
Cleats
Cleats
Description <string> Plates
Plates Preps
Preps Ref.
Ref.Data
Data
Purpose JOIN
Gtype <word>
STCAtegory Joint
Joint Seating
Seating Bolted
Bolted Notched
Notched
Description <string> Ref.
Ref.Data
Data I I- -I I I I- -I I I I- -I I
Purpose JOIN
Function <string>
Gtype <word>
Ptref <ref>
Gmref <ref>
Ngmref <ref>
Joint 4M20 6M20
Dtref <ref> 4M20 6M20
Pstref <ref> Gtype <word>
Gstref na Parameters <array>
CDetail Pstref <ref>
Ownconn <word> Gstrer <ref>
Attconn <word> Dtref <ref>
Cplot
Icon
Cstandard
C ATAlogue Panel
Description <string>
Panel
Purpose PF IT
Cstandard <string>
STSEction Fitting
Fitting
W
Windows
indows Doors
Doors Holes
Holes
Description <string> Ref.
Ref.Data
Data
Purpose PF IT
Gtype <word>
STSEction
STSEction
STCAtegory
Description <string>
Purpose REF Structural
Structural
Function <string> Category
Category
Gtype <word>
Ptref <ref>
Gmref <ref>
Ngmref <ref>
Dtref <ref>
Pstref na
Gstref na
CDetail Geometry Pline Negative Data
Ow nconn <word>
Geometry Pline Negative Data
Set
Set Set
Set Geom
GeomSet
Set Set
Set
Attconn na
Cplot
Icon
Cstandard
Point
Point
Set
Set
GMSE/PTSS/GMSS/DTSE
Description <string>
Gtype <word>
Purpose <word>
PTSE
Description <string>
Gtype <word>
Skey <word>
Purpose <word>
2.3 Specifications
The following conventions for structural specifications must be followed to ensure that a
correct specification is built. The applications follows strict rules when building these
specifications and reads the specification in a tabulated format. Description should be
given at the correct level and any question of Tanswers must be input for the forms and
menus to be correctly built. The steelwork specifications work in a different way to
piping specifications, where there can be more than one answer. For example, a typical
connection for two beams can either be a bolted or welded connection; hence there can be
two answers to one question.
BS-Standard
SPEC
SPEC
UB UC RHS CHS
SELE
SELE SELE
SELE SELE
SELE SELE
SELE
SPCO
SPCO SPCO
SPCO SPCO
SPCO SPCO
SPCO
Fitting
SPEC
Single Double
SPCO SPCO
Panel Fitting
SPEC
SPCO SPCO
SPEC
Column
Connections Beam Universal
Connections Joints
SELE SELE SELE
60x60x10 60x60x10
4 Bolts 6 Bolts
SPCO SPCO
S pecification B ritish
Standard
D escription <string>
Purpose STL
Q uestion G TYP
M atref <ref>
C standard <string>
B EA M B EA M CHAN
S elector U niversal U niversal
C hannels
C olum ns B eam s
D escription <string>
Tansw er <w ord>
W IN D DOOR L IG H
S e le c to r (le v e l 1 ) W in d o w s D o o rs L ig h ts
D e s c rip tio n < s trin g >
Tansw er < w o rd >
Q u e s tio n STYP
IN S P B U LK F IR E BLAS
S e le c to r (le v e l 2 ) In s p e c tio n W a te r T ig h t F ire B la s t
C o v e rs B u lk h e a d s D o o rs D o o rs
D e s c rip tio n < s trin g >
Tansw er < w o rd >
SpecC om ponent S td S in g le S td S in g le
In te rn a l E x te rn a l
C a tR e f < re f>
D e ta il < re f>
Specification BS Profile
Fittings
Description <string>
Purpose FITT
Question TYPE
Matref <ref>
Cstandard <string>
P ro file Jo in t S p ecificatio n s
S p ecC om po n en t 60 x6 0x 10 60 x6 0x 10
4 B o lts 6 B o lts
C atR ef < ref>
D etail < ref>
For the materials of a structural element (MATR) to be set in DESIGN, you must be
able to see a Properties DB containing the available materials.
To create a Material World, carry out the following steps:
To load the new/modified materials into the system, follow step 4 above. If you moved
the file to some other directory, run the macro by passing the full pathname of the file,
thus:
$m/%PDMSUI%/DES/DATA/MLOADPROP <pathname>
3.1 Introduction
The following Datakeys are reserved for use by the application and have the special
meaning shown:
POD Pipe outside diameter (e.g. for lugs)
SWID X -width of attached steel section (SCTN)
FLTH Flange thickness of attached steelwork
CRAD Component bend radius (e.g. for lugs/trunnions attached to bends)
RINA Rod insertion distance at P1 *
RINB Rod insertion distance at P2 *
VSLO Variable spring load (Note: PUNIT attribute should be set)
VSEX Variable spring extension/compression distance
DATA A special case where the design parameter is not set automatically, but
rather prompts the user to enter the data.
(* These values are calculated from the ‘Rod take-out values’ of the Prev/Next
components and represent the distance between the P1/P2 points and the actual ends of
the component.)
Datakeys which give information either to DESIGN appware for sizing purposes or to
ADP (automatic drawing production) appware for drawing data etc. are usually set to
component parameters or hard data. The PURP attribute is set to PARA to indicate
that, while the information is used by the DESIGN appware, it is not required for ADP
or MTO:
RTVA Rod take-out value at P1 #
RTVB Rod take-out value at P2 #
THLA Thread length at P1
THLB Thread length at P2
VSPR Variable spring rate (units as set for VSLO)
MNLO Minimum load in working range
DHEI Loaded default height (for components which are adjusted, regardless of
load, to a fixed height)
(# These values represent the distances from P1/P2 that attached rods should extend in
the ‘fitted’ position.)
Other Datakeys may be defined as a means of forcing an ADP application to output
database information on drawings and MTO lists. The PURP attribute of these
Datakeys should be set to DATA. The following settings of this type are used in the
supplied catalogue:
OLEN Component overall length
HEIG Height
DIMA Dimension A (as defined in the paper catalogue)
Naming Conventions
A naming convention for catalogue components has been developed following the
conventions of the ISOCAT style in use by Cadcentre and a number of customers for
many years. This convention is detailed later in this section.
3.7.1 Configurations
The Hangers & Supports application makes use of catalogue information which describes both
support template and hanger configurations. This data is stored in catalogue elements and is accessed
by means of a specification. Configurations are thus similar to a Specification Reference (SPREF)
and both the Subframe (SBFR) and Hanger (HANG) elements have :CONFIG UDAs. The referenced
SPCO points, via an ACOM and a GMSE, to a CATE which actually holds all the configuration data.
Members
The configuration CATE may own any number of TEXT elements which are used to describe the
components used in the hanger. Each component has a TEXT element placed in the correct order in
the members list; the description is stored in the STEX attribute.
XHBPCLA:
Arguments
1 PCLA STYP(s)
For tube ATTAs, single value (quoted if using TANS)
For component ATTAs, space or / separated list for TEE, ELBO, BEND components
(NONE if not applicable)
Globals used
None
Globals set
!!CDSNHB.RTOVAL1 Derived RTO value at P1 end
!!CDSNHB.RTOVAL2 Derived RTO value at P2 end
XHBFITT:
Arguments
None
Globals used
None
Globals set
None
XHBHELE:
Arguments
1 HELE STYP
2 Any other selectors (quoted if using TANS)
3 HELE GTYP. Unique WORD attribute used to identify HELE for later operations
4 GTYP of element which will be at the arrive end of the new HELE
5 GTYP of element which will be at the leave end of the new HELE
N.B. If argument 4 identifies an element which occurs later in the hanger's members
list than argument 5, this will cause the new element to be created in ‘backwards’
mode. This can be very useful in some circumstances.
6 Arrive p-point/Leave p-point (e.g. 2/1)
7 Connection/Fitting instructions:
FIT Fit the HELE into the available space (by setting HEIGHT attribute)
CONN Connect the HELE to the previous element (or HH/HT)
DIST Set the HELE at a specified distance from the previous element
PROP Set the HELE at a specified proportional distance between the previous
and the next elements
DIST and PROP both have the format <keyword> <value> <p-point>
(the p-point designation is optional and defaults to P0)
8 Angle flag. True if the component has a DDANG which needs to be deduced.
9 Specification from which to select component:
INSPEC Select from current HSPEC
PSPEC Select from attached pipe PSPEC
<gid> Select from explicit specification
Globals used
!!CDSNHB.RINS1 Rod insertion length at P1
!!CDSNHB.RINS2 Rod insertion length at P2
Globals set
!!CDSNHB.RTOVAL1 Derived RTO value at P1 end
!!CDSNHB.RTOVAL2 Derived RTO value at P2 end
XHBHORI:
Arguments:
1 HELE GTYP
2 Mode FORW or BACK
3 Connection/Fitting instructions
FIT Fit the HELE into the available space (by setting HEIGHT
attribute)
CONN Connect the HELE to the previous element (or HH/HT)
DIST Set the HELE at a specified distance from the previous
element
PROP Set the HELE at a specified proportional distance between
the previous and the next elements
DIST and PROP both have the format <value> {<p-point>}
The default p-point is P0.
4 Angle Flag to direct component arrive/leave
Globals used:
Globals set:
XHBSCLA:
Arguments
1 SCLA STYP
2 Any other selectors (quoted if using TANS)
3 Fit flag. True if SCLA is to be fitted into the available space.
4 P-point to orientate towards previous component. The subroutine will attempt to
align the PA/PL, but if this in insufficient, then it will use this p-point. Default
orientation is determined by argument 5.
5 Default orientation:
Globals used
None
Globals set
!!CDSNHB.RTOVAL1 Derived RTO value at P1 end
!!CDSNHB.RTOVAL2 Derived RTO value at P2 end
XHBHCLN:
Arguments
1 GTYP of element to be checked
2 Minimum/Maximum distance:
Explicit value
Parameter number (e.g. PARAM 1)
3 P-points which min/max distance applies to (in arrive–leave order)
4 Type flag: MIN or MAX
Globals used
None
Globals set
None
XHBSPAC
Arguments:
Globals used
None
Globals set
None
Support Configurations
Support configurations store the following data:
Members
The configuration CATE may own any number of TEXT elements which are used to describe the
support template. The TEXT element's role is determined by the setting of the :DESCR UDA and the
data is stored in the STEX attribute.
The following TEXT elements are mandatory and are used to determine the numbers of support
members expected before and after configuration:
:DESCR = #ST
STEX = <value>
where <value> represents the number of stanchions expected in the final configuration and must
be a non-negative integer or the letter ‘N’ to indicate any number, but it can have the following
modifiers:
> There must be greater than zero before configuration
= The number before configuration must be the same as the number specified
:DESCR = #XM
STEX = <value>
where <value> represents the number of cross-members expected in the final configuration and
must be a non-negative integer or the letter ‘N’ to indicate any number, but it can have the
following modifiers:
> There must be greater than zero before configuration
= The number before configuration must be the same as the number specified
Each type of member ennumerated above must be described by another TEXT element:
:DESCR = <member type>_<member number>
where <member type> is XM or ST and <member number> is the number of the
stanchion/cross-member being described
STEX = <start connection info> <end connection info>
where <start connection info> takes the form
S:<member at start>/<joint position>/<Attached or Owner>:<clearance code>
and <end connection info> takes the form
E:<member at end>/<joint position>/<joint ownership>:<clearance code>
<member at start> is a support member identifier of the start connection
<member at end> is a support member identifier of the end connection
Member identifiers can have the following forms:
<value> For a specific member number
N Representing the Nth member
< The most extreme ST/XM member in the XM/ST direction
> The least extreme ST/XM member in the XM/ST direction
:DESCR = PARAM
STEX = <parameter>/<descriptor> <parameter>/<descriptor> ...
where <parameter> is a single-character text string in the range A–I
and <descriptor> can refer to any of the following:
The length of a member; e.g. ST_1 or XM_N (length of 1st stanchion or Nth cross-
member)
A dimension between a member and the start/end of another section; e.g. XM_1<ST_1
(distance of 1st cross-member from start of 1st stanchion)
A dimension between two members; e.g. XM_1-XM_2 (distance between 1st cross-
member and 2nd cross-member)
• Hanger Lengths
• Hanger/Steel Clearances
• Maximum Unsupported Spans
Data tables for Hangers & Supports should exist in a SPWL with PURP set to HSUP.
The Hanger Length Table is used by the application to determine the minimum and maximum Head to
Tail lengths for a given configuration. This is checked every time a hanger is created, but it is most
important for template-type configurations which use the minimum length to position the supporting
members. The values derived from this table override the values set in the configuration CATE
:MAXLEN and :MINLEN attributes.
The Hanger Length Table should be in a SPEC with PURP set to HMML. An example named
/CADC/HS/SAMPLE/SPEC/HANGLEN is supplied with the product.
The following hierarchy is mandatory for the Hanger Length Table:
SPEC
QUES PBOR
:VISI false
PURP HMML
DESC <optional text description>
1st Level of SELE
ANS <pipe nominal bore>
QUES SMAT
2nd Level of SELE
TANS <steel material code> *
QUES PMAT
3rd Level of SELE
TANS <pipe material code> *
QUES HTYP
SPCO level
ANS <length type code> **
TANS <hanger configuration type code> ***
COMM <min length>/<max length> (including units, e.g. 0mm/60mm)
* Material codes are defined in the application defaults from the Settings>Admin>Materials
menu option.
** This can be set to 0 or 1:
1 – Lengths are calculated from outside of pipe. This is the default mode if a configuration is
not defined in the Hanger Length Table.
0 – Lengths are calculated from the C/L of the pipe. In this mode, the application selects the
PCLA to calculate the minimum length when creating support templates.
*** Code corresponds to the Hanger Build Macro suffix and the GTYP of the configuration CATE.
This table is used at two stages during the creation of a support (with steelwork). First when initially
applying a configuration to deduce the lengths of the supporting members, and again when the
profiles have been selected to maintain the minimum clearance between hanger attachment points and
supporting member ends. There are three types of clearance code, depending on the type of joint at
the member end:
A1 Free end (no joint) before profiles set
A2 Free end after profiles set
B Perpendicular joint
C1 Angled end (braced free end - only really used in the ‘Braced Cantilever’ type configuration)
before profiles set
C2 Angled end after profiles set
The following hierarchy is mandatory for the Hanger Clearance Table:
SPEC
QUES PBOR
:VISI false
PURP HCLR
DESC <optional text description>
1st Level of SELE
ANS <pipe nominal bore>
QUES CTYP
2nd Level of SELE
TANS <clearance code>
QUES HTYP
SPCO Level
TANS <hanger configuration type code> *
COMM <clearance> (measured from pipe C/L including units, e.g. 75mm)
* Code corresponds to the Hanger Build Macro suffix and the GTYP of the configuration CATE
Some users base maximum unsupported spans for pipes on ‘Span Tables’. The Hangers & Supports
application provides a method whereby these tables can be entered into a data table and the maximum
spans can be graphically indicated in the 3D model by partially highlighting the supported branches.
The PURP attribute of the Span Table SPEC should be set to HSPT, the :VISI set to false, and the
DESC attribute may have an optional description text.
The hierarchy for this data table is variable, depending on the number of parameters which you wish
to cross-reference, but the format is as follows:
At SELE/SPCO Owner
TDEF <expression>
This expression can be anything which yields a single numeric or text value based on the current
HANGER. It is recommended that the supplied user function SELEATT be used, as this will
return the value of any attribute or any pseudo-attribute of any part of the hanger or related
support or pipe. For example:
USRFUNC (SELEATT ATTA LBOR) returns the leave bore of the ATTA.
USRFUNC (SELEATT ATTA $<part (RTEX of DETREF of LSTU , 2)$>) returns the
schedule of the attached pipe (for the standard CADC pipe specs).
USRFUNC (SELEATT BRAN TEMP) returns the temperature rating of the attached branch.
(See the internal macro documentation of SELEATT for further details of this function.)
At SELE/SPCO
TANS <test>
This test is used for the data returned by the owner's TDEF expression to yield a logical true or
false.
Suitable tests might be (for the above examples):
eq 20
eq 'SCH80' (notice the use of quotes '...' and not vertical bars |...| )
lt 177
Tests are performed in list order, so if multiple matches are possible, the first is assumed. In this
way, ranges can be defined (as with the temperature example above) by using lt or gt and putting
the test values in increasing or decreasing order as applicable.
The actual span is stored in the COMM attribute of the SPCO. The application will
return an error value if matches cannot be made from the Span Table.