OPC Data Logger

Once connected to an OPC Alarm and Events Server PALLAS starts logging all events.

These events are stored locally on the PALLAS PC allowing for access to historical event data.

Live Cause and Effects Viewer

PALLAS has a Live Cause and Effect Viewer utilising known ‘normal’ system states, the current system state (using the A&E data) and a Cause and Effect matrix defined from CERES (or manually).

When a system input transitions to a tripped state the input is flagged as tripped on the input section of the Cause & Effect matrix.

PALLAS also monitors the system outputs highlighting when the outputs transition to trip.

If input and output correspond based on the defined Cause & Effect information, the appropriate intersect will behighlighted as tripped.

If there is a discrepancy between input and output, either an un-successful trip or an un-expected trip, the intersect field will be highlighted a failed.

The colours displayed on the matrix are user configurable, allowing PALLAS to conform to end user requirements.

Feedback Confirmation and Timing

Each output defined within PALLAS can be associated with feedback inputs. These inputs can include valve limit switches and switchgear tell backs.

Numerous feedback signals can be declared for each output and the ‘healthy’ and ‘tripped’ feedback states must be declared.

Using this information, an output discrepancy is flagged and logged when the feedback signals disagree with the output state.

This feature acts as a record for end-to-end testing of system end elements. Using the feedback signals, output timing can be measured allowing for the open/close times of  valves etc to be recorded.

OPC Data Logger

Once connected to an OPC Alarm and Events Server PALLAS starts logging all events.

These events are stored locally on the PALLAS PC allowing for access to historical event data.

Live Cause and Effects Viewer

PALLAS has a Live Cause and Effect Viewer utilising known ‘normal’ system states, the current system state (using the A&E data) and a Cause and Effect matrix defined from CERES (or manually).

When a system input transitions to a tripped state the input is flagged as tripped on the input section of the Cause & Effect matrix.

PALLAS also monitors the system outputs highlighting when the outputs transition to trip.

If input and output correspond based on the defined Cause & Effect information, the appropriate intersect will behighlighted as tripped.

If there is a discrepancy between input and output, either an un-successful trip or an un-expected trip, the intersect field will be highlighted a failed.

The colours displayed on the matrix are user configurable, allowing PALLAS to conform to end user requirements.

Feedback Confirmation and Timing

Each output defined within PALLAS can be associated with feedback inputs. These inputs can include valve limit switches and switchgear tell backs.

Numerous feedback signals can be declared for each output and the ‘healthy’ and ‘tripped’ feedback states must be declared.

Using this information, an output discrepancy is flagged and logged when the feedback signals disagree with the output state.

This feature acts as a record for end-to-end testing of system end elements. Using the feedback signals, output timing can be measured allowing for the open/close times of  valves etc to be recorded.