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
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
