Overall Integrity and Pair Integrity

Please share your knowledge to clear my concept about overall Integrity and Pair Integrity for Redundant I/O cards and why they show pair Integrity and overall Integrity status BAD.

6 Replies

  • The integrity flag reporting is a hierarchy with Overall Integrity at the top. This bit is set if any integrity issue is present on the node. So an issue with Redundant IO cards will set the Overall Integrity. The Overall Integrity is shown in DeltaV Explorer, indicating the node should be diagnosed. Clearing the subordinate integrity condition will clear the overall flag, if it is the only subordinate condition.

    In DeltaV Diagnostic Explorer, every subsystem and component shows its integrity. There is a Show next Integrity button in the ribbon that allows you to quickly move to the next component.

    The Condition Summary lists all the integrity flags that set the Hardware alerts and gives you the ability to manage these conditions by suppressing conditions that cannot be corrected and the hardware alert can be cleared so that new conditions can trigger a new abnormal condition. As with alarms, having standing conditions can reduce the Alert usefulness.

    Andre Dicaire

  • In reply to Andre Dicaire:

    Thank you for sharing this
  • In reply to Andre Dicaire:

    Andre - not sure why I can't find the condition summary. Books Online references the "Condition Summary Viewer" but still searching for where one would open this application . . .
  • In reply to John Rezabek:

    John,
    In diagnostic explorer, right click on a node. Condition Summary should be in the list and click there. Also, the Node faceplates have an Icon that will launch the condition summary as well. The Network switch command center allows you to launch the condition summary for a switch. It is launched always in context so I don't think you would launch it as a program but launch it from a menu or a faceplate where the context is defined and the summary is available.

    Andre Dicaire

  • In reply to Andre Dicaire:

    Okay, I see where to launch it. It opens for any "node" on the DeltaV network but not for any subordinate contents e.g. I/O or assigned modules.
    Is there a reason both "suppressed" and "unsuppressed" fields are blank? I'm logged in as an admin and viewing controller nodes with yellow "?" - caused by I/O issues or module faults. Running 14.3.LTS.
  • In reply to John Rezabek:

    Sorry John, I don't have a list for what is and is not included for the condition summary. My understanding is that all items that map to the hardware alerts would appear in the condition summary. The Hardware Alert faceplate also launches Condition Summary and from there you can suppress nuisance alerts that you can't address at the source for some reason. I would expect that for the node in question, it does not have an alert, though it is showing Overall integrity flag.

    The other side of things is that module level faults that report via the modules shouldn't flag a Hardware alert too. Same for IO related faults that would trigger a Device Alert. These would duplicate errors and contribute to alarm floods. The integrity flags are a diagnostic bread crumb mechanism while the Hardware and device alerts are a separate mechanism highlighting a node or device issue. Module issues report on a module alarm. But as to what specific conditions flag a hardware alert vs just an integrity flag, I don't have that.

    Andre Dicaire