20
Data consistency check Design errors can be detected by doing consistency check. This is the list of errors for data consistency check. ERROR CODE ERROR DESCRIPTION ERROR CAUSE ACTION BY A10 HEAD REFERENCE NOT SET The Head reference should only be unset (i.e. null) if the Head Connection Type HCONN is set to OPEN, VENT, CLOS or DRAN. DESIGN A20 HEAD REFERENCE POINTS TO NONEXISTENT ELEMENT This error would result from the deletion of a component, such as a Nozzle, to which the Head of the Branch was originally connected DESIGN A30 BAD HEAD RETURN REFERENCE The Head is connected to an element that does not refer back to the Branch. This can occur when the Head of a Branch is connected to another Branch, implying that a Tee should be placed somewhere along the DESIGN

Data Consistency Check

  • Upload
    karuna

  • View
    546

  • Download
    33

Embed Size (px)

Citation preview

Page 1: Data Consistency Check

Data consistency checkDesign errors can be detected by doing consistency check. This is the list of errors for data consistency check.

ERROR CODE

ERROR DESCRIPTION ERROR CAUSE

ACTION BY

A10HEAD REFERENCE NOT SET

The Head reference should only be unset (i.e. null) if the Head Connection Type HCONN is set to OPEN, VENT, CLOS or DRAN. DESIGN

A20

HEAD REFERENCE POINTS TO NONEXISTENT ELEMENT

This error would result from the deletion of a component, such as a Nozzle, to which the Head of the Branch was originally connected DESIGN

A30BAD HEAD RETURN REFERENCE

The Head is connected to an element that does not refer back to the Branch. This can occur when the Head of a Branch is connected to another Branch, implying that a Tee should be placed somewhere along the second Branch. The error can also occur when two or more branches are inadvertently connected to the same terminal. DESIGN

A100

HEAD TERMINAL PROBLEM WITH SPREF

Either the Head terminal has an unset SPREF or the SPREF points to a non-existent SPCOM. ADMIN

A110

HEAD TERMINAL PROBLEM WITH CATREF

Either the Head terminal has an unset CATREF or the CATREF points to a non-existent Catalogue component. ADMIN

A120 HEAD TERMINAL There is a Catalogue ADMIN

Page 2: Data Consistency Check

PROBLEM IN ACCESSING P-POINTS

problem in accessing the p-points of the Head terminal.

A130

HEAD TERMINAL PROBLEM, P-POINT NO.n DOES NOT EXIST

A required p-point of the Head terminal does not exist in the set of p-points. ADMIN

A140

HEAD TERMINAL PROBLEM INVALID FLOW ATTRIBUTE ON CONNECTED BRANCH

This is testing for flow with Branch to Branch connections. Branches have a FLOW attribute which can be set to FORW or BACK or NUL. If FLOW is not set correctly this results in an error DESIGN

A150

HEAD TERMINAL PROBLEM, TERMINAL INCONSISTENT FLOW ACROSS BRANCH CONNECTION

The FORW flow means that the fluid in the Branch goes from Head to Tail with the reverse for BACK. The code then checks that the fluid flows correctly from one Branch to the next. To fix the problem check the network to see that all the flows are in the correct direction DESIGN

A200

DIRECTION HDIR NOT SAME AS TERMINAL DIRECTION

If the Head is connected to a terminal, such as a Nozzle or Tee, then the direction HDIR should always be identical to that of the appropriate p-point of the terminal. DESIGN

A210

POSITION HPOS NOT SAME AS TERMINAL POSITION

If the Head is connected to a terminal, such as a Nozzle or Tee, then the position HPOS should always be identical to that of the appropriate p-point of the terminal. DESIGN

A220HBORE NOT SAME AS TERMINAL BORE

If the Head is connected to a terminal, such as a Nozzle DESIGN

Page 3: Data Consistency Check

or Tee, then the bore HBORE should always be identical to that of the appropriate p-point of the terminal.

A230

CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE

If the Head is connected to a terminal, such as a Nozzle or Tee, then the connection type HCONN should always be identical to that of the appropriate p-point of the terminal. DESIGN

A300REFERENCE HSTUBE UNSET

There is more than 1mm of tube between the Head and the p-arrive of the first Component (or the Tail), but HSTUBE is unset. ADMIN

A310

REFERENCE HSTUBE REFERS TO A NONEXISTENT SPCOM

This may occur if part of the Specification has been deleted. ADMIN

A320

HSTUBE PROBLEM, CATREF IN SPCOM IS UNSET

This indicates an error in the Specification. ADMIN

A330

HSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NONEXISTENT Catalogue COMPONENT

This may occur if part of the Catalogue has been deleted or if the CATREF is unset. ADMIN

A340

HSTUBE PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SET TO TUBE

The component pointed to by HSTUBE is not of type TUBE in the Catalogue. ADMIN

A350

HSTUBE PROBLEM IN ACCESSING P-POINT

There is a Catalogue problem in accessing a p-point of the tube pointed to by HSTUBE. ADMIN

A400 HBORE NOT SAME The bore of any tube ADMIN

Page 4: Data Consistency Check

AS BORE OF HSTUBE

leading from the Head, determined from the Catalogue, should always be identical to HBORE

A410

HCONN NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE

The connection type of any tube leading from the Head, determined from the Catalogue, should be compatible with HCONN. ADMIN

A420

ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT

This error would occur if, for example, the Insulation Specification pointed to by ISPEC had been deleted. ADMIN

A430

INSULATION CANNOT BE SELECTED USING HBORE

There is no suitable insulation in the Catalogue for the combination of temperature TEMP and bore HBORE ADMIN

B10TAIL REFERENCE NOT SET

The Tail reference should only be unset (i.e. zero) if the Tail connection type TCONN is set to OPEN, VENT, CLOS or DRAN. DESIGN

B20

TAIL REFERENCE POINTS TO NONEXISTENT ELEMENT

This error would result from the deletion of a component, such as a Nozzle, to which the Tail of the Branch was originally connected. DESIGN

B30BAD TAIL RETURN REFERENCE

The Tail is connected to an element that does not refer back to the Branch. This can occur when the Tail of a Branch is connected to another Branch, implying that a Tee should be placed somewhere along the second Branch. The error can also occur when two or more branches are inadvertently connected to the same terminal. DESIGN

Page 5: Data Consistency Check

B100

TAIL TERMINAL PROBLEM WITH SPREF

Either the Tail terminal has an unset SPREF or the SPREF points to a non-existent SPCOM. ADMIN

B110

TAIL TERMINAL PROBLEM WITH CATREF

Either the Tail terminal has an unset CATREF or the CATREF points to a non-existent Catalogue component. ADMIN

B120

TAIL TERMINAL PROBLEM IN ACCESSING P-POINTS

There is a Catalogue problem in accessing the p-points of the Tail terminal. ADMIN

B130

TAIL TERMINAL PROBLEM, P-POINT NO.n DOES NOT EXIST

A required p-point of the Tail terminal does not exist in the set of p-points. ADMIN

B140

TAIL TERMINAL PROBLEM INVALID FLOW ATTRIBUTE ON CONNECTED BRANCH

This is testing for flow with Branch to Branch connections. Branches have a FLOW attribute which can be set to FORW or BACK or NUL. If FLOW is not set correctly this results in an error DESIGN

B150

TAIL TERMINAL PROBLEM, TERMINAL INCONSISTENT FLOW ACROSS BRANCH CONNECTION

The FORW flow means that the fluid in the Branch goes from Tail to Tail with the reverse for BACK. The code then checks that the fluid flows correctly from one Branch to the next. To fix the problem check the network to see that all the flows are in the correct direction DESIGN

B200 DIRECTION TDIR NOT SAME AS TERMINAL DIRECTION

If the Tail is connected to a terminal, such as a Nozzle or Tee, then the direction TDIR should always be identical to that of the appropriate p-point of the

DESIGN

Page 6: Data Consistency Check

terminal.

B210

POSITION TPOS NOT SAME AS TERMINAL POSITION

If the Tail is connected to a terminal, such as a Nozzle or Tee, then the position TPOS should always be identical to that of the appropriate p-point of the terminal. DESIGN

B220TBORE NOT SAME AS TERMINAL BORE

If the Tail is connected to a terminal, such as a Nozzle or Tee, then the bore TBORE should always be identical to that of the appropriate p-point of the terminal. DESIGN

B230

CONNECTION TYPE TCONN NOT SAME AS TERMINAL CONNECTION TYPE

If the Tail is connected to a terminal, such as a Nozzle or Tee, then the connection type TCONN should always be identical to that of the appropriate p-point of the terminal. DESIGN

C500

TUBE BETWEEN HEAD AND TAIL LESS THAN TUBE MINIMUM

The distance between the Head position, HPOS, and the Tail position, TPOS, is greater than zero and less than the specified minimum tube length (default: 100mm). DESIGN

C510BAD HEAD TO TAIL GEOMETRY

Either the Head position, HPOS, does not lie at a positive distance along the line through TPOS in the direction TDIR or the Tail position, TPOS, does not lie at a positive distance along the line through HPOS in the direction HDIR. DESIGN

C520 HBORE NOT SAME AS TBORE

When there are no components on the branch, the Head bore, HBORE, should be identical to the

DESIGN

Page 7: Data Consistency Check

Tail bore, TBORE

C530

HCONN IS NOT COMPATIBLE WITH TCONN

This implies that the Head is connected directly to the Tail with no Tube or piping components in between; hence the Head connection type, HCONN, must be compatible with the Tail connection type, TCONN. DESIGN

C540THIS BRANCH HAS NO COMPONENTS

This does not necessarily indicate an error. It is merely output as a warning to the designer. DESIGN

D100REFERENCE SPREF UNSET

This probably means that the designer has forgotten to select the piping component. DESIGN

D110

REFERENCE SPREF REFERS TO A NON-EXISTENT SPCOM

This may occur if part of the specification has been deleted ADMIN

D120

SPREF PROBLEM, CATREF IN SPCOM IS UNSET

This indicates an error in the Specification. ADMIN

D130

SPREF PROBLEM, CATREF IN THE SPCOM REFERS TO NON-EXISTENT CATALOGUE COMPONENT

This may occur if part of the Catalogue has been deleted or if the CATREF in the SPCOM is unset. ADMIN

D140

SPREF PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SAME AS TYPE OF DESIGN DATA COMP0NENT

The GTYPE of the Catalogue component must be the same as the type of the piping Component in the design data. ADMIN

D150 SPREF PROBLEM, GTYPE OF CATALOGUE COMPONENT IS

An error has been found in accessing the p-points of the Catalogue component pointed to by CATREF

ADMIN

Page 8: Data Consistency Check

NOT SAME AS TYPE OF DESIGN DATA COMP0NENT

D160REFERENCE CATREF UNSET

This applies only to Nozzles, for which the CATREF must be set. ADMIN

D170

REFERENCE CATREF REFERS TO A NON-EXISTENT CATALOGUE COMPONENT

This may occur if part of the Catalogue has been deleted. It applies only to Nozzles. ADMIN

D200

ARRIVE P-POINT NOT IN PTSET OF CATALOGUE COMPONENT

The arrive p-point number does not exist in the PTSET of the Catalogue Component. ADMIN

D210

LEAVE P-POINT NOT IN PTSET OF CATALOGUE COMPONENT

The leave p-point number does not exist in the PTSET of the Catalogue Component. ADMIN

D300REFERENCE CREF NOT SET

Multi-way Components may be left unconnected only if the connection type of the relevant p-point is OPEN, CLOS, VENT, DRAN or NULL. DESIGN

D310

REFERENCE CREF POINTS TO NON-EXISTENT BRANCH

This may occur if the Branch that is pointed to by the CREF has been deleted. DESIGN

D320BAD CREF RETURN REFERENCE

This may occur if the Branch that is pointed to by the CREF has been reconnected to another terminal. DESIGN

D330 REFERENCE CRFA n NOT SET

An entry in the connection reference array may only remain unset if the corresponding p- point in the Catalogue does not exist or if the connection type of the corresponding point is

ADMIN

Page 9: Data Consistency Check

VENT, OPEN, CLOS or NULL.

D340

REFERENCE CRFA n POINTS TO NON-EXISTENT BRANCH

This may occur if the Branch pointed to by the nth reference in the connection reference array has been deleted. DESIGN

D350

BAD CRFA n RETURN REFERENCE

This may occur if the element pointed to by the nth reference in the connection reference array has been reconnected to a third Branch. DESIGN

D400

ARRIVE TUBE [ROD] LESS THAN TUBE [ROD] MINIMUM. ACTUAL TUBE [ROD] LENGTH IS …

The distance between the arrive p-point of this component and the leave p-point of the previous component (or Head) is greater than zero and less than the specified minimum tube [rod] length (default: 100mm). DESIGN

D410

BAD ARRIVE GEOMETRY + details of geometric errors

The position and direction of the arrive p-point of this component are not correct with respect to the leave p-point of the previous component (or Head). The error could be caused by incorrect positioning of this component, the previous component (or Head) or both. DESIGN

D420BAD ARRIVE BORE [ROD DIAMETER]

The bore of the arrive p-point of this component is not equal to the bore of the preceding tube or, if this component is not preceded by tube, to the bore of the leave p-point of the previous component (or HBORE). DESIGN

Page 10: Data Consistency Check

D430BAD ARRIVE CONNECTION TYPE

The connection type of the arrive p-point of this component is not compatible with the preceding tube or, if this component is not preceded by tube, to the connection type of the leave p-point of the previous component (or HCONN). DESIGN

D500

REFERENCE LSTUBE [LSROD] UNSET

The user has probably forgotten to select the piping/hanger Component. DESIGN

D510

REFERENCE LSTUBE [LSROD] REFERS TO A NON-EXISTENT SPCOM

This may occur if part of the Specification has been deleted. ADMIN

D520

LSTUBE [LSROD] PROBLEM, CATREF IN SPCOM IS UNSET

This indicates an error in the Specification. ADMIN

D530

LSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NON-EXISTENT CATALOGUE COMPONENT

This may occur if part of the Catalogue has been deleted or if the CATREF in the SPCOM is unset ADMIN

D540

LSTUBE PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SET TO TUBE

The component pointed to by LSTUBE is not of type TUBE in the Catalogue. ADMIN

D550

LSTUBE [LSROD] PROBLEM IN ACCESSING PPOINTS

There is a Catalogue problem in accessing a p-point of the tube/rod pointed to by LSTUBE [LSROD]. ADMIN

D600

LEAVE BORE [DIAMETER] NOT SAME AS BORE [DIAMETER] OF LSTUBE [LSROD]

The bore of the leave p-point of this Component is not the same as the bore of the tube/rod following the Component. DESIGN

Page 11: Data Consistency Check

D610

LEAVE CONNECTION TYPE NOT COMPATIBLE WITH CONNECTION TYPE OF LSTUBE [LSROD]

The connection type of the leave p-point of this Component is not compatible with the tube/ rod following the component. DESIGN

D620

INSULATION CANNOT BE SELECTED USING LEAVE BORE

There is no suitable insulation in the Catalogue for the combination of temperature TEMP and the bore of the leave p-point. ADMIN

D630

ATTACHMENT TYPE INVALID – MUST BE ONE OF FLOW, XXXX, SSSS, CCCC, CCNN, INPP, WELD, HANG, PENI, NUL OR NULL

You have set an incorrect TYPE attribute for an ATTA. DESIGN

D740

ANGLE OF COMPONENT IS GREATER THAN MAXIMUM ANGLE SPECIFIED IN SPREF

The designed angle of a Pulled Bend, Elbow or Weld is greater than is allowed by the SPECs DESIGN

D740

ANGLE OF COMPONENT IS LESS THAN MINIMUM ANGLE SPECIFIED IN SPREF

The designed angle of a Pulled Bend, Elbow or Weld is less than is allowed by the SPECs. DESIGN

D740

ANGLE GREATER THAN m DEGREES. ACTUAL ANGLE IS n.

The designed angle of a Pulled Bend or Elbow is greater than the maximum angle specified by the user (see TOLERANCE MAXANGLE). DESIGN

D800Reference DETAIL unset.

This refers to the DETA attribute of the SPREF of the branch component. Without it no SKEY will be available for that element within ISODRAFT. ADMIN

D820 SKEY not set ADMIN

Page 12: Data Consistency Check

D840

SKEY #N not known. Assumed to be user defined ADMIN

E700

LEAVE TUBE LESS THAN TUBE MINIMUM. ACTUAL TUBE LENGTH IS …

The distance between the leave p-point of the current component and the tail position, TPOS, is greater than zero and less than the specified minimum tube length (default: 100mm). DESIGN

E710BAD LEAVE GEOMETRY

The position and direction of the leave p-point of this component are not correct with respect to the position, TPOS, and direction, TDIR, of the tail. The error could be caused by incorrect positioning of this component, the Tail, or both. DESIGN

E720LEAVE BORE NOT SAME AS TBORE

The bore of the leave p-point of this component is not the same as the tail bore, TBORE. DESIGN

E730

LEAVE CONNECTION TYPE NOT COMPATIBLE WITH TCONN

The connection type of the leave p-point of this component is not compatible with the tail connection type TCONN. DESIGN

Types of ATTAISODRAFT uses attachment point elements in the DESIGN database, known as ATTAs. These are used to allow forces, moments, etc. to be applied to a Branch during pipe stressing, to show the location of support points, and to attach comments, flow arrows, etc. to the pipes on isometric plots.

Page 13: Data Consistency Check

The different types of ATTA are defined by the setting of the ATTY attribute. The ATTY settings and other information for different types of ATTA are given below. Support ATTAs are used to mark the position of a support on the pipe. There are three types of

support ATTA:Comment ATTAs are used to add a drawing note with leader line to a position on a pipe, typically to add a floor penetration note. They have ATTY set to CCCC. If this point is not already dimensioned, for example, if it lies in the tube, additional dimensions to the ATTA position will be output.o ATTY type Unset, is the default type of support ATTA. They are used to mark the position of a

support on the pipe. They should be positioned on the centreline of the pipe. If they are not: Data consistency checking will generate an error message, unless ATTACHECK OFF is set, in

which case no check is made for correct orientation and position of the ATTA. If the ATTA is within tube, it will be shown at the p-leave of the previous component or at the head of the branch. This can cause the dimensioning of another Support ATTA further down the pipe to be omitted.

To position the ATTA within the previous component, connect it in list order after the component, then explicitly set its position, or move it BY the required distance along the direction of P-arrive. Note that, in this case, data consistency checking will generate an error message unless ATTACHECK OFF is set.For elbows and bends, ATTAs can be positioned on projected centrelines, i.e. at the intersection of centrelines.Note:   Supports on tube are shown with a symbol, but supports on components are not.

ATTY type Hang ATTAs are used in the Hangers & Supports application to indicate where a hanger type support will be attached to a pipe or component. They operate in exactly the same way as ATTY type Unset ATTAs.

ATTY type Weld ATTAs are also used in the Hangers & Supports application. This type of ATTA is used to position the plotted ATTA symbol a fixed distance inside the previous component (e.g. at the P0 of an ELBO component), rather than moving the ATTA to that point as you have to do with ATTY types Unset and Hang.It is accomplished by the ATTA having a P3 point, which is a set distance in the arrive direction from P1/P2. The distance between P1/P2 and P3 must be set in the catalogue for each ATTA of this type, which is then used with the same component (e.g. ELBO). The symbol for this ATTA is automatically plotted at its P3 point.Inserting the ATTA directly after the previous component ensures the ATTA symbol is plotted at the correct point inside that component.

Comment ATTAs should lie on the centreline of the pipe.To position the ATTA within the previous component, connect it in list order after the component, then explicitly set its position, or move it BY the required distance along the direction of p-arrive. Note that, in this case, data consistency checking will generate an error message unless ATTACHECK OFF is set.

Non-dimensional Comment ATTAs are used to add a drawing note with leader line to a position on a pipe; for example, to add a paint colour note. They have ATTY set to CCNN. This type of ATTA will not be dimensioned.

Flow ATTAs are used to position inline flow arrows in tube. They have ATTY set to FLOW. The arrow is not dimensioned, but it is positioned on the tube in proportion to its 3D position.The flow is from head to tail if the FLOW of the branch is the default forwards direction, or tail to head if the FLOW of the branch is backwards.Note:   The FLOWARROWS INLINE command must be used for flow arrows to be plotted for tube.

Page 14: Data Consistency Check

Split ATTAs for a normal isometric are used to set the point at which an isometric should be split onto the next sheet. They have ATTY set to XXXX.ISODRAFT sometimes repositions split points if a more logical point is close. For example, consider a Tee with a Flange welded to P3, and a Gasket and a Valve connected to the Flange. If a Split ATTA is positioned between the Tee and the Flange, ISODRAFT will split the pipe at the natural break formed by the Flange.Normal Split ATTAs are ignored for system isometrics and equipment trim isometrics.

Split ATTAs for system isometrics have ATTY set to SSSS. This type of ATTA is used to set the point at which a system isometric or equipment trim isometric should be split onto the next sheet. The same considerations as for normal isometric split ATTAs apply.

Insulation symbol ATTAs have ATTY set to INPP (insulation personnel protection). This ATTA type is used to set the start and stop points of insulation on the isometric. The insulation specification note will be shown at the start point of the insulation, but not at the end (to avoid duplicating information).