Alarms
Use alarms to indicate the status of a process or machine at runtime. Alarms indicate that something requires attention or intervention, such as a variable reaching a critical value.
TIP:
For example, a temperature variable may change from the normal set value and activate the alarm.
Alarm types
FactoryTalk Optix Studio
includes several predefined alarm types. Different alarm types trigger different alarm event types. You can also create custom alarm types by configuring additional properties for the alarm.For more information, see Alarm types.
Alarms configuration
Create alarms with alarm object types and alarm object instances. Configure the variables polling time for alarms. For more information, see:
Use objects and preconfigured widgets to visualize alarms status at runtime. For more information, see:
TIP:
When a controller has a non-OPC UA server, to monitor the system, you must import the controller variables and reference the controller variables in the alarm objects. If the application exposes an OPC UA server,
FactoryTalk Optix Studio
may automatically communicate with OPC UA servers through the Applications
object. The application automatically reads alarm events exposed by the OPC UA server to display event status and alarm information.Alarms management
Use the alarm grid to confirm and acknowledge alarms at runtime. You can also configure the alarm grid to automatically confirm and acknowledge alarms. For more information, see Confirm and acknowledge alarms.
Alarm statuses
In
FactoryTalk Optix Studio
, alarms may have the following statuses.Status | Description |
|---|---|
In Alarm, Unacked, Unconfirmed | Active alarm that requires attention or intervention |
In Alarm, Acked, Unconfirmed | Addressed alarm |
In Alarm, Acked, Confirmed | Resolved alarm |
Normal | Inactive alarm |
disabled
Provide Feedback