Orion database setup
By default, the framework supports a standard file database for storing alarms. Storing open alarms in this local file alarm database and cleared alarms in a remote Orion alarm database provides an effective way to manage alarms.
Open alarms include alarms that have not been acknowledged and not yet transitioned back to normal. Cleared alarms are alarms that have been acknowledged and transitioned back to normal.
This table summarizes the possible alarm database configurations.
| Description | Local alarm database | Remote alarm database | Comments |
|---|---|---|---|
| Station with the default local file alarm database and no remote database |  | None | This configuration is for small installations that generate few alarms. |
| Station is configured with an OrionAlarmDatabase component. All alarms are stored in the remote database | N/A | | Disadvantage: connection ups and downs can disrupt open alarm storage and retrieval. |
| Station with a local file alarm database for open alarms, and a remote Orion alarm database for cleared alarms |  |  | This is the best configuration. The local Orion alarm database
in the station stores open alarms. The remote, larger Orion alarm
database stores cleared alarms. Alarm transitions, acknowledgements, adding notes, etc. update the local alarm database for viewing on an alarm console. Over time these should only be a small percentage of the total alarms and the local file alarm database should be large enough to handle them. Connection ups and downs should not impact these alarms. The station archives cleared alarms to the remote Orion alarm database on a regular schedule. |
The first two rows may describe your current alarm database configuration. The tasks in this section explain how to migrate from the first two configurations to the third. Gold platters represent open alarms. Blue platters represent cleared alarms. Larger remote databases can store many more cleared alarms than can be stored locally.
The alarmOrion palette provides the components to configure these databases. For more information about relational databases, refer to the Niagara Rdbms Driver Guide.