Roger, The real problem is there are several system monitors on different AWs. It would be possible to write something to periodically get the data from the smon_logs and consolodate across the mesh, but is going to take some doing. All of the system monitors are pointed at the same single AIM* historian, so the historian should already have the messages in it. This same method (extraction from the historian) was successfully used on a duplicate system running the legacy historian. Unfortunately this new all XP, all AIM* system doesn't have the tools out of the box to do this. We are looking at some programs that Kevin Fitzgerrel and Otto Kubbenga (my vote for a name cooler than Duc Do) have sent. If we can't get something working pretty quick we will roll a smon_log consolidator, but it seems like the wrong thing to do in this instance. Besides the historian has the data, we just need a way to extract it... on a scheduled basis....in the background....to a csv file....that we can use for operations. But if you do something good extracting date from the sysmon_log, please let us post a copy on the Cassandra site. Thanks, David PS: Tell Ted that Mike Baker's sister says hi. He'll understand. _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave