I may be missing something, but I don't see a field for the "current" or "present" position for a valve -- as opposed to its normal position. Which would be used to identify those valves that, for whatever purpose, were in a abnormal position.
If a field serving this purpose is present and I've missed it I would offer multiple kudos to whoever points it out.
If a premise of the UPDM model is to represent only the normal, as-designed state of the network, then I guess I would understand that as well.
Any insights would be much appreciated.
Thx,
Ed
Solved! Go to Solution.
The 'Device Status' field is intended to reflect the present position of the valve, whether open or closed. This is intended to be used along with the 'Normal Position' field to indicate both the present and the normal operational states of a valve.
The 'Device Status' field is intended to reflect the present position of the valve, whether open or closed. This is intended to be used along with the 'Normal Position' field to indicate both the present and the normal operational states of a valve.
Makes sense! Thank you very much!
Ed
Device status controls tracing, normal position does not.
Sure. But as I look at the values in the device status domain they are "active" and "inactive" - which to me implies whether the asset is or is not in service - not whether it is "open" or "closed". A "closed" valve is very much "active". Is this just something I'm going to have to get over?
@EdwardBlair what version of the model are you looking at? In the latest versions of the model both the devicestatus and normalposition fields have domains that only include the open/closed values.
In earlier models, there was a domain assigned at the class level that also included active/inactive, but the domain assigned to operable devices should only include the values open/closed. As you know, when a class has subtypes, you must look at the domain assigned at the subtype level.
Doh! I'm such an idiot. Of course its at the asset group/subtype level. Thanks @RobertKrisher !
Don't worry about it, we keep a swear jar of sorts around the office for every time someone forgets to check the subtype 🙂