Component naming convention

Hi wolf,

I adopted a simpler approach on naming conventions which is specifically based on the client piping specs standards. We coded the piping specs to a one (1) letter code and combined it with component type...see below:

Code A = 1143B Carbon Steel ANSI Class 150
Component Type = PIPE, EL45, EL90...etc
Size = 25, 40, 50....etc

therefore:

Catref Name = A-PIPE-25  (code+component type+size)
Detail = A-PIPE-SDTE
Matx= A-PIPE-SMTE

The above format provides clearly shows component identification, easy to understand and requires few keyins to point the files. Everything is similar/standard except for the pipe coding.

Regards,
Ferdinand

Hi wolf,

I adopted a simpler approach on naming conventions which is specifically based on the client piping specs standards. We coded the piping specs to a one (1) letter code and combined it with component type...see below:

Code A = 1143B Carbon Steel ANSI Class 150
Component Type = PIPE, EL45, EL90...etc
Size = 25, 40, 50....etc

therefore:

Catref Name = A-PIPE-25  (code+component type+size)
Detail = A-PIPE-SDTE
Matx= A-PIPE-SMTE

The above format provides clearly shows component identification, easy to understand and requires few keyins to point the files. Everything is similar/standard except for the pipe coding.

Regards,
Ferdinand