I have a query..... the project iam working is done at two locations and we r not using PDMS Global... The part of scope in catalogue is similar to some extent... and theres more specs frm my end... the review is done by client by adding the scope of other company into our databases..... (the other company will do their part separately but as the large part of scope is in our end the client want 2 see the full project by adding both the scope into ours) so here we have two catalogue database.... n some spec names are similar..... and der part of scope is simply for review... so at this point wat i have done is i have made a separate MDB for reviewing the full project
(two scopes) and the other end catalogue will be on the top of mine.... these catalogues are foregin database..... i get the updated model at frequent intervals with all the design n catalogues database.... n there will b updation done to the catalogue as per the requirement of their design database... so the ques is whn i replace the updated master catalogue with the old master catalogue (replacing the 000 foler i.e Environmental folder n this replacement is done in their project not mine) does it gona work well... as they are foreign database... or else do i hve to exclude them and again add the database... some times i may not update all the design database as there will not be any change in design.....so it recalls the old reference number....will it result to a mess... which is the better way to go ahead......in my present situation....actuall i hve done by replacing the 000 folder n al these days it works fine, no problem is der.....but like 2 knw what i am doing is rgt r wrong....
The techniques you are using...copying the 000 folder over and manipulating the files are sometimes referred to as poor mans Global. Because PDMS is a tough little cookie and its databases self contained most of the time you will get away with this especially if you are careful about locking the project and taking precautions. However it is not unheard of for poor mans global to bite back and go wrong..... Global is expensive... no shame in taking the poor man's way :) But be careful.. !
To address your question.... The important thing is the number of the databases within the two MAS projects. As you probably know design elements using the catalogue look to the catalogue spec with their specification reference. On the command line this look like the name ... you type q spref....it says spref SPCO1 of SELE3 of blah blah.... actually what it really uses (as is often the case) is the reference number of this item. And the reference numbers in your catalogue need to be unique and match the expectations of the design database for it work properly. Reference numbers are a factor of the db number.
So if your MAS and the other MAS have the same dbnumbers and you try to mix and match you are probably going to struggle... as the same ref numbers may collide :(
@yar_nl : the scope of the other company and its locations will be decided by us.... and their sites and zone will be at 0,0,0 where i hve to move them to required location as per the layout. they r not made at the plant co-ordinates... this decision is taken by management whn there is no administrator in da company.......
@Big: v hve taken care with db numbers tht they shld not b same..... the db numbers are unique.... n whn iam importing to my model i am maintaining the unique db number...... theres no chance of reference number mix..... as the model of ours have the separate db whn designers do modelling the components are called frm our db and there only one catalogue db in tht mdb. whn its turn of review there will b two catalogue dbs in other mdb where the other company catalogue db will b on top...... as the model is already build up there will not b any issue.... if we try 2 model in tht db thn it def... gona to b a big mess....... every time v hve to check frm which catalogue db is tht component called.......anyhow taking a big risk.....
You have two nearly identical catalogue databases.... based on the AVEVA supplied MAS project one from you one from client with different numbers and hence different unique refs.
You want to bring these two CATA DBs and your DESI's into one DB. If that is correct then there is no problem you can create an MDB with these two sets of unique CATA DBs and DESI together no problem.
I am gathering that you are maybe worried that going forward your users are going to possibly select catalogue references from the client MAS, rather than yours. Resulting in a mess of cross references.
Is this your problem?
If it is you have some options. :)
If you have your own copy of the clients MAS that you will use going forward you need to disable the specs in it so your users can't pick the components from there.... effectively moving the whole client catalogue to limbo spec, and stopping your users selecting it's content.
nope.., thts not the case.... the project is between 2 companies and the scope is divded into two. v hve our master catalogue db and the other company hve their master catalogue db...whn i import their design db's into our project it needs their master catalogue..... so i hve created an MDB where their catalogue db is top of ours.... ofcourse v got their master catalogue db... which is similar upto some extent..... Here there is no matter of MAS catalogue.....
Hi,
I don't see the problem. I would suggest to include the MAS-DB not as a foreign DB but to copy MAS into the project but in all MDBs only as READ. Then both of you will refer to the same DB.
In a next step I would create a CATA-DB for every location that will have to be exchanged together with the DESI-DB. Then you have to exchange once the MAS-DBs and afterwards only you DESI and your CATA and the client will be able to review the model with your catalogue.
Global might need some admin work but it mainly costs a lot of money. I prefer a data exchange via DB-Exchange as possible faults in one site can be undone without disturbing the other planners.
