Component naming convention

Even i would also stick to Aveva convention...

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

lemme know if anyone has any comments?

Best Regards...

Hi

Guys can somebody send me AVEVA's naming conventions for Catalogue elements as well as Specon elements.
Thnx in advance

in which manual can I find AVEVA's naming conventions for Catalogue elements?
because i try to search manuals but I didn't get it

Talk to your Aveva rep.
They do not issue a copy af this system as a rule (maybe because it is so old)
They probably have copies of it somewhere that they could let you have.

did anyone have a copy of it?
I think that no problem to upload that data

AVEVA have a copy

I mean the forum members

It is copywrite protected. Only AVEVA can provide a legal copy.

Is there some reason you are unwilling to talk to AVEVA?

You may develope your own naming conventions...

Can someone alighten me the way to get the component code list or item code list? for instance; ELL (Elbow)...etc.? Thanks in advance!