Regulatory Compliance Monitoring

Using the OPC Time Monitor’s ability to specify a “condition” based on a range of values and its ability to specify condition that would imply loss of communications to the field device (OPC Quality conditions), the OPC Time Monitor can then monitor your field instruments through your OPC Data Access servers and generate notification events to your HMI application or other regulatory monitoring applications.  Information possible includes:

• Current compliance condition (in or out) with event generation if condition changes
• Notification/count of loss of communications to field devices (OPC Quality =Bad or Uncertain)
• Number of Times out of Compliance (using the CycleCount aggregate)
• Total Time out of Compliance (using the TotalClientTime or TotalServerTime aggregates)
• Maximum Time out of Compliance on any single excursion beyond limits (using the MaxClientTime or MaxServerTime aggregates)
• Average Time out of Compliance (using the AverageClientTime or AverageServerTime aggregates) since the OPC Time Monitor was last started or Aggregates reset using the Basic Reset Tag.

By using the OPC Time monitor to handle detecting out-of-compliance conditions, you free yourself from writing custom scripting or other decision making logic in your monitoring application or in field devices.  Because the OPC Time Monitor can simultaneously report information and events to multiple client applications, your choices for monitoring and notification are extensive.