Re: [foxboro] Data, alarms, and reports
- From: "Dumitru, Alex" <alex.dumitru@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 08:42:17 -0400
Hi Joseph,
Some other options with the currently known tools at site:
A)
1. Create a separate off-platform AIM*Historian instance exclusively for
the long term collection of the environmental data and messages so that
data can be accumulated for a long period of time outside the IA
stations (where disk space resources are limited).
2. Use the Excel based Alarm Extractor from Invensys Canada (very
similar to the IA Series Report Package) to create Excel based alarm
reports.
3. Use the AIM* Client tools that the customer probably already has
(such as AIM*Datalink) for ad-hoc queries from the historian(s).
Usually the set of environmental data is quite small and most
regulations request a data history in the range of 5 years. This means
you can get away with the smallest AIM*Historian license (200 points for
around $3K list) and a small W2K3 server (based on on-line prices around
3K from DELL with RAID, enough storage, OS included + 3 years HW
support). The off-platform historian can have two separate remote
collectors one on the UNIX and the other on the Windows site of the DCS.
The Alarm Extractor will offset you somewhere in the range of $4K list
but will require no training since it's a close cousin of the IA Series
Report Package.
B) =
1. If having a third AIM*Historian on site is not appealing, then create
separate instance(s) using the existing historian(s) and dedicate these
new instance(s) to the environmental data collection. Due to the limited
disk space resources on the IA stations you will have to archive the
files externally to your network server either manually or using the
AIM*Autoarchiver and possibly some other packages.
2. & 3. same as above.
I would recommend A over B, unless your budget is really low and you are
not afraid to deal with the archiving of AIM data files.
On the other hand, if you are willing to explore some new tools (option
C) there are means to do things also with the InFusion historian and
your current DCS setup.
Hope this helps,
Alex Dumitru, Eng.
SI & IT
Invensys Systems Canada Inc.
Phone: (514) 421 8073
Fax: (514) 421 8054
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Joseph M. Riccardi
Sent: Friday, March 16, 2007 9:08 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Data, alarms, and reports
Folks,
Here is our scenario:
* Mandate
* We have a mandate to collect environmental data for
long-term
storage. On the existing (being replaced) system (a non-Foxboro, old
proprietary software type system), this data was collected and shift
reports (yes, actual paper) were generated daily, reviewed 1st for any
areas of concern, then stored away in case they were needed in the
future (employee health concerns, civil action. etc.).
* Goal =
* The existing system is being replaced and my goal is to
bring
the required data (AINs and any alarms generated from these blocks) into
the IA System to be historized for data collection, trends, reports, and
long-term storage on a Network server.
* Platform
* Our platform is AW/WP51D/F/Gs, (2) AW70s (NFD and Batch),
V6.5.X/V7.X, etc.
* Tools
* AIM*Historian (1 on an AW51D and 1 on an AW70).
* IA Series Report Package (AW70).
* Connection to a Network server.
I have the easy configuration part done; data is to the AIN blocks and
in the AIM*Historian for displays and trends. =
Now the hard part. Operations is asking us to replace the shift reports
generated daily by the previous system. My initial response was to
offer 2 alternate choices:
* Configure Reduction Groups in the AIM*Historian and generate Excel
reports using the IA Series Report Package. An easy to do choice and
they get paper (I am still trying to wean them off paper copies) and
files for long-term storage on a Network server. Their preference...
* I naturally think data belongs in a database and would like to
offer
this data up in an Access database and I'll build a form to query the
data they need (which specific points) and from when (time/date range).
They can do this daily (review for any areas of concern) or any time in
the future (the next law suit). Unfortunately, I don't know if or how
to do this one.
I your need help and advice on how, if this is even feasible on the
platform we have and with the existing tools. =
The next dilemma I face is getting the process alarms generated by these
blocks into the Historian and into the reports (either Excel and/or
Access).
I would appreciate your help and advice...
Thanks.
Joseph M. Riccardi, Inc.
DCS Services - Industrial Process Control North-Central Office (OH, PA,
MI, IN, WV Area) South-East Office (FL, GA, AL, SC, NC Area)
mailto:Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A.
Adams
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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
- References:
- [foxboro] Data, alarms, and reports
- Re: [foxboro] Data, alarms, and reports
- From: Johnson, Alex P \(IPS\)
- Re: [foxboro] Data, alarms, and reports
- Re: [foxboro] Data, alarms, and reports
- From: Johnson, Alex P \(IPS\)
- Re: [foxboro] Data, alarms, and reports
Other related posts:
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports
- » Re: [foxboro] Data, alarms, and reports