Re: [foxboro] Running Hours Counter and OSI-PI

PI is an historian, we've been using it for 7 years or so (more than 6500
tags, not counting the totalizer tags)  and all the data is still available
and will remain so for a couple of years more. The pi server is not part of
the DCS system and is maintained and updated by IT, it's a modern win 2003
server with plenty of capacity. It is also part of the backup strategy. The
excel sheet our maint guys are using gives them the opportunity to reset
data after overhauls and adjust running hours. It's up to maint to keep
track of the servicing data. Also if you require the total liftetime hours,
not counting overhauls,  you could make 2 totalizer tags, one which is
never reset until replacement and one which is reset each overhaul. It
doesn't stress the DCS at any way, cause it uses data ftom the "normal" pi
tag which is already present in the PI taglist.

Infact PI has become our most important tool for analysis, loop tuning
etc... and has proven to be reliable. (as long as the pi interface is
online...) We have buffering enabled which allows us to take the pi server
off line during considerable time, before we loose any data.  It is however
not easy to use and sometimes requires some VB knowledge to generate
complicated reports. Also you have to be carefull on how you tune the tags
to avoid bottlenecks etc... our pi interface is foxapi residing on an AW51
E so this is not the most modern type of communication and we have never
had serious problems with it.

We're more or less considering to use OPC in the future, but for the moment
the good old foxapi is doing very well.

Rgds,


Dirk Pauwels - DCS/MOC coordinator
Engineering dept.
Hexion Specialty Chemicals
E mail: dirk.pauwels@xxxxxxxxxx
T.  +32.(0)3.570.95.97
F.  +32.(0)3.570.16.09
Mob. +32.(0)497.428.300

Wrote:

Hello, it looks so simple but I do not believe it is.
Some motors may run several years and in order to get the real running
hours you may need historian info for several years: question is, can
the system hold all that data.
Also, one motor may be replaced yesterday, the second may have been
overhauled 3 months ago and one may be running for  3 years: so you need
to know for each motor when it was overhauled/replaced and the running
hour counter should for each motor go back in the historian for the
period relevant for that motor. That period may be different for each
motor.
Good luck

Kind regards,
Hub Stapper











 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: