Mike Hyde's Special Projects |
---|
My Vision | Ping | Read | DRU Auditor
Since we installed the DRU devices on Air Conditioning compressors many years ago, I have struggled with maintaining connectivity.
I am not sure how many other TWACS customers are having luck with these devices,bbut I can honestly say thay have been a pain in my butt.
Once a month, I ping all of our DRU's and attempt to investigate the ones that do not respond.
I am not really sure how many other utilities are doing this,
but I do not know any other way to verify that these devices are
doing what we think they should be, and that is to help reduce load
during peak events.
I have always felt that devices should be configured to a location identifier, and not the meter at that location.
The meter will change, any auxilary devices (LCT's, DSI's, DRU's and IHD's) will probably change also.
Anyone who has used the TWACS system has probably experienced how difficult
it may be to get all the associated devices reassociated with the new meter, when there is a meter change.
This is further complicated when different applications must be used for each auxuiliary device type.
I believe TWACS OC must be used to associate DSI's with meters, and the DRU Manager must bwe used to associate DRU's with the meter.
At NNEC, this is complicated by our periodic meter changes (200/month) and path changes.
I had to find a better way to get these devices associated easier.
For this, I have created the DRU Auditor. The DRU auditor lists the DRU's that are not associated with a meter, and orphaned DRU's.
An example is shown below.
This reports point out several differnet types of issues.
The next phase will be to have this option available when a
protective device is selected on the map.
How about, when an outage ticket is created, the pings get
submitted automatically? That way, when the dispatcher looks
at the map, he can get get an idea as to the extent of the
outage, and possibly the device that caused it.
Once I get the GPS coordinates from the mapping system into the
CIS, then as meters are changed, the GPS data will be
automatically populated in the TWACS system. Then who knows what will be next.
Once the tables are populated, you can look at the hierarchy
using some interesting scripting (Base script complimehts of George from PPL).
Disclaimer - Not responsible for anything these may do to your system.
I use them, but they may not function the same on your system.
SQL>delete from amrcommfail where serialnumber not in (select serialnumber from serialnumber);
If you have any comments or questions, please feel free to email me, I am really interested in hearing what you have to say, both good and bad
Thanks,
Mike