We are implementing a new procurement program at my company that tracks all components by a reference numbers. The program does not have a set standard so we are adapting PDMS naming convention. We’ve found that AVEVA’s naming convention falls short in two areas. First area it doesn’t account for fittings that are purchased schedule by schedule. Second and the biggest it doesn’t account for material grades. We want to keep a direct relation between our PDMS catalogs and our procurement software. Has anyone come up with a naming convention better than AVEVA’s that accounts for these things?
The only thing I've seen at other companies was a modified catalog naming convention based on the one from Aveva. You could always make the item code longer to add the items you mentioned.....
I have a few ideas that about this subject, but it would take some time to explain.
I'll try to find an easy example to help explain and post later.
We do not follow Aveva's naming convention. We have adopted more of a noun-adjective approach to naming. An example SCOM would be [COLOR="Blue"]/90.DEG.EL/LR/CS/150,3[/COLOR] while a corresponding SPCO example would be [COLOR="blue"]/SpecA/90.DEG.EL/LR,3,SSTD,CS[/COLOR]. The only difficulty that we run into is the character count in the names. We need to watch this when spec names get too large.
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
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.
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
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.
Thanks guys, but I don't think your suggestion is what I'm looking for. What would be the naming convention for:
6x4, Reducer Conc. buttweld sch. 40 x sch 80 A234 grade WPB
[QUOTE=The Wolf]Thanks guys, but I don't think your suggestion is what I'm looking for. What would be the naming convention for:
6x4, Reducer Conc. buttweld sch. 40 x sch 80 A234 grade WPB
For spco, I use A/6.0WNRF for 6in wn raise face flange, A/6.0ER4.0 for 6x4 ecc reducer.
For Scom, some places I worked use 7 digit code, some use 9 digit code, the difference is once place use two digits for vendor, the other use one digit for vendor.
If you creat things from scratch, then this will be a huge task. I will use what Aveva provides and build upon it.
For example - if you want a 7 digit SCOM name - you use ABCDEFF, A - vendor, B- gtyp of component, C- ... D - ... E -... FF = for bore size say 1 in or 25 mm.
Also have a look at the Catview it should have some pretty good examples.
The only consideration - do you have enough character for your info listing. eg, if you use one char for vendor, you may ran out of letters (ASCII table only allow some many), so should you be using two characters? Type - valve, redu, tee, cross etc, one character is probably enough, think it through, document it in a spreadsheet.
A.. COZ ITS GOOD
B...if anything goes wrong, it may take a while for Aveva support to figure out
C. If you wanna share catalogs/specs...its easy if you use std Aveva Convention...this way duplicates are easily checked..
We also follow Aveva convention and build upon watever comes as per project requirements
But make sure you dont change anything wat Aveva provides....i mean if u wanna add new components, but them under ur company.project catalog database and use Aveva std names etc......if you add things to the Aveva catalogs then u may end up in problems if they upgrade their catalogs....like they did with the introdution of New bolting and all
