To avoid having to transfer component design or specification errors from the Catalogue database to the Design database before data inconsistencies can be detected, a facility is provided for checking the main settings of a piping catalogue as you build it in PARAGON.
(This facility is not yet available for checking a structural catalogue.)
9.1 Initiating a Standard Data Consistency Check
The basic command to initiate a database consistency check, using default settings, is CHECK <gid>
where <gid>, the element below which checks are to be carried out, may be any SPEC, SELE, SPCO or COMP.
If you start the check from within a specification (SPEC, SELE or SPCO) all components referenced via the starting element will be checked. If you start the check at component level (COMP), only that component and elements below it will be checked.
(See Controlling the Detailed Checking Procedure for details of the ways in which you can modify the default checking procedures.)
9.2 What the Checking Facility Does
The following tests may be carried out:
At SPEC level:
• Check that no question in the specification is repeated.
• Check that one question in the specification is TYPE.
• From the TYPE reference, check that the GTYPE of the COMP has the same setting.
• From the TYPE reference, check that the SKEY setting of SDTE is correct.
• From the TYPE reference, check that the point set has the correct geometry, as required by ISODRAFT.
At SPCO level:
• Check that all of the following reference attributes are set: CATREF, DETAIL, MATX, CMPR, BLTREF. (The BLTREF need be set only if the connection type begins with F or L.)
12.0 9:2
At COMP or equivalent level:
• Check that there is a valid PTREF and GMREF.
• At a PTSE, check that P-points are set and that there are no duplicate numbers.
• At a GMSE, check that there are primitives set and that they are not degenerate. Check also that no invalid P-point numbers or parameters are used. Note that this test uses catalogue parameters, so that if a primitive is constructed only from design and insulation parameters, spurious warnings will be generated.
• Check that each P-point connection type exists in the COCO tables. P-points used for construction purposes can have connections of 0.0, NUL or NULL. The connection type will not be checked for validity for a specific type of component.
• Check that a P-point bore is valid for a recognised set of nominal bores. P-points used for construction purposes, and a P-point with connection type CLOS, can have a zero bore.
9.3 Controlling the Detailed Checking Procedure
You can modify the effect of the CHECK command by using additional syntax so that you can check different types of catalogue without generating unnecessary errors.
The command options are as follows:
TOLerance CATAlogue CMPRef ON/OFF
switches Component Reference checking on or off for all component types in a SPCO.
TOLerance CATAlogue CMPRef word ON/OFF
switches Component Reference checking on or off for the specified component type in a SPCO.
TOLerance CATAlogue GMREf ON/OFF
switches Geomset Reference checking on or off for all component types.
TOLerance CATAlogue GMREf word ON/OFF
switches Geomset Reference checking on or off for the specified component type.
TOLerance CATAlogue BORE ON/OFF switches bore checking on or off for Pointsets.
TOLerance CATAlogue BORE value value sets range of permissible bores to be checked for Pointsets.
TOLerance CATAlogue ISOMetric ON/OFF checks for SKEY and similar ISODRAFT-related settings.
TOLerance CATAlogue DEFault resets all checking options to their default settings.
These defaults are:
• Do not check any CMPREFs.
• Ignore GMREF settings for ATTA, FLAN, TUBE and BOLT.
• Check nominal bores in the range 6 mm to 2150 mm.
• Check all ISODRAFT-related settings.
To query any of the current data consistency checking settings, use the corresponding command format
Q TOLerance CATAlogue ...
9.4 Error Messages
Error messages which can result from diagnosed data inconsistencies are as follows:
C10 Spec error: Question word asked more than once C20 Spec error: Question TYPE never asked
C30 Spco error: DETA not set
C40 Spco error: Unknown ref for DETA C50 Spco error: MATX not set
C60 Spco error: Unknown ref for MATX C70 Spco error: CMPR not set
C80 Spco error: Unknown ref for CMPR C90 Spco error: BLTR not set
C100 Spco error: Unknown ref for BLTR C110 Spco error: CATR not set
C120 Spco error: Unknown ref for CATR C130 Comp error: PTRE not set
C140 Comp error: Unknown ref for PTRE C150 Comp error: GMRE not set
C160 Comp error: Unknown ref for GMRE
C170 Ptset error: Duplicate ppoint number integer C180 Ptset error: No ppoints set
C190 Ptset error: Unknown connection type word for ppoint C200 Comp error: GTYPE word different from spec TYPE word C210 Ptset error: Non standard bore value for ppoint
C220 Gmset error: Unknown parameter integer for primitive
C230 Gmset error: Axis defined with unknown Ppointinteger for primitive C240 Isometric error: Ppointinteger not defined
C250 Isometric error: Cannot calculate angle between Ppointinteger and Ppointinteger C260 Isometric error: Incorrect angle between Ppointinteger and Ppointinteger. Angle
is value and should be value.
12.0 9:4
C270 Isometric error: Incorrect angle between Ppointinteger and Ppointinteger. They should not be parallel.
C280 Gmset error: primitive may be a degenerate primitive
C290 Isometric error: Ppoint1, Ppoint2 and Ppoint0 should be colinear C300 Gmset error: primitive cannot be constructed
C310 Gmset error: Expression error for primitive C820 SKEY not set
C830 SKEY word is used with generic type word, not word C840 SKEY word not known. Assumed to be user defined.