All new products are getting more powerful than before, but those are sensitive and difficult to control.
PDMS 12 is already difficult to understand its full functon by one person.
Earlyer versions of PDMS also difficult system to support by one persion, but now it's being more difficult.
Many software developpers try to "add" new function, and sometimes forgot to "improve" existing function to their product.
PDMS 12 has both improved and added function, but I guess AVEVA could spend more power to make it easy not only for existing users, but also new users.
If the software provider can show more examples to users how they can use the new function, but often AVEVA does not show it.
e.g. In the manual, purpose of User defined element type is explained for making different types of equipment, such as pumps, or, vessels.
I think this is not good example. What is difference between making different types of equipment and define its type by FUNCTION attribute?
[QUOTE=harryh;21447]e.g. In the manual, purpose of User defined element type is explained for making different types of equipment, such as pumps, or, vessels.
I think this is not good example. What is difference between making different types of equipment and define its type by FUNCTION attribute?
Well you forget that we cater to both the marine and plant markets. I believe the UDET functionality came from Tribon and we then incorporated it into Marine 12 and then in PDMS 12.
You're right that you can set the function attribute, but with UDETs you can see in the Design Explorer weather it is a pump, tank, exchanger, etc. without having to display it in the Graphical View or querying the attributes.
It also helps in reporting because not everybody remembers to fill in attributes like function or description. With UDETs you can easily see if the UDET isn't set because it would say EQUI.
Lastly UDETs don't just apply to EQUI, you can also have a UDET for Sites (eg. :AREA) and Zones (eg. :Compartment).
Harry,
Nice bikes, are you going to buy one of those sometime?
I agree with you 100% on PDMS being more and more complicated for anyone person to be able to grasp/implement. Guess that is one of the reasons experienced users like you are visiting this site to share thoughts and insights on how we are using the system.
The aim of software company and users are quite different, one wants to keep on selling new gadgets, and the other wants to keep it simple and be able to get work done with what they have on hand. Some of the gadgets developed over the years are very nice and are real time savers, others are just "*** on a hog".
I am really confused.
I have only tested two functions and both crashed in PDMS12.
Latest I noticed that type of attributes has been changed.
In 11.6 type of uwei of cmpref was REAL
In 12 type of uwei of cmpref is STRING.
I am little be affraid that there is lot of work to be done to uppgrade all in-house functions to PDMS12
Most difficult part of software upgrade for develpper is to keep compatibility...
Whatever the modifications were written in the User Bulletin, it is difficult to guess where the modification will make impact to the customer's applicaiton/setup.
I guess this is just a side effect of software upgrade, and difficult to accuse somebody.
What I wanted to say in this thread is, the software is going difficult to use "full function" whatever the software provider is advertising those new functions, because the new functions were just added and existing function are not (notably) improved.
We can see good progress with spec. definition in Paragon, but how may years we needed to wait for it?
Why it was released after many of PDMS users are finished to develop own spec. edit/definition system?
> codooaustin
Can you please put good example of usage of UDET, if it is not a confidential matter?
It is good to hide needless attributes when we query attributes, but I have no good idea of usage/purpose other than this...
By the way, talking about Design Exporer, why PDMS12 can not display folded(wraped) DB element name correctly? This is confusing...
