| |
|
MatrikonOPC Alarms & Events Historian
Data storage for text-based alarm & event systems
The MatrikonOPC A&E Historian is a Sequence of Events (SOE) database that collects
and archives time-stamped, text-based information from any device that can send
information using serial, TCP/IP, printers, network printers, or OPC A&E.
The A&E Historian is perfect for merging DCS alarms and events, logging network events, replacing
sequence of event recorders, loggers, or any other type device that sends
text-based messages.
Speed & Reliability
Get distributed high-speed data collection with store-and-forward reliability!
Matrikon Event Collector communicates directly with a variety of data sources,
stores up to 2,000 events or messages per second, and reliably forwards that
information to the OPC A&E Historian.
Different device events can be consolidated into a single Event Archive
database or distributed to different databases.
Data in the Event Archive database can be viewed anywhere from the Web. You
can also connect directly to the database and use your own reports or applications
to view the data.
Guaranteed reliability!
Easy to configure
Installing the OPC A&E Historian is easy. You can have the Historian up and running
in 3 simple steps:
- Create a connection. (Pic1)
- Choose from pre-configured connections:
- ABB Advant
- Bailey
- MOD300
- Plant portal
- Honeywell TDC2000
- TDC 3000
- Westinghouse
- Ovation
- Fix
|
- Wonderware
- Ticonex
- HIMA
- Fisher RS/3
- Fisher Provox
- DeltaV
- Foxboro IA
- Siemens
- and many more...
|
- Or if we missed one, you can define parsing rules on your own. (Pic2)
Why an Alarm and Event historian instead of a process historian?
Process historians perform poorly when archiving text messages. Because alarms and events are text messages, they can impair historian performance. The OPC A&E Historian uses a relational database (either MS SQL or Oracle), which is ideal for storing text-based information. By using the OPC A&E Historian to store your data, you can avoid overloading your process historian or having to pay those tag licensing fees.
The OPC A&E Historian stores a chronological log of events. Process historians are designed to store large volumes of data on a tag-by-tag basis for several tags at a time, or the current value for many tags at once. The OPC A&E Historian, on the other hand, is especially designed to provide information on every tag and every event in chronological order for a given time period or across multiple time periods. This provides a detailed record of each event in the process and the order in which events occurred. Asking for chronological events from every tag in a historian would result in massive amounts of data being returned.
Minimum System Requirements
Event Collector
Pentium II or better
64 MB of RAM or more
Windows NT 4 with Service Pack 6 or better, or Windows 2000 with
Service Pack 2 or better
Internet Explorer 5 or better
Sufficient disk space to hold store and forward buffer files.
OPC A&E Simple Interface support
OPC A&E Historian
For 50 messages per second stored to database, 800MHz processor or better
For 100 messages per second stored to database,
1.6GHz processor or better
128 MB of RAM or better
Windows NT 4 with Service Pack 6 or better, or Windows 2000 with
Service Pack 2 or better
Internet Explorer 6 or better
Sufficient disk space to hold store and forward buffer files.
(10GB recommended)
|
|
 |