we have an application when an Alarm comes, we can only acknowledge the Alarms to continue the next execution.
OPC UA supports Alarm workflows like 'Suppressed, shelve, out of service, Inactive etc', but this Alarm workflow is not supported by our application.
So I just wanted to know for CTT, is this mandatory to implement this complete Alarm Workflow or it is up to the our application implementation.
Thanks and Regards,
In the OPC UA Alarm model there are multiple Facets that describe different levels of support.
I am not sure if the question is related to what an Alarm Server supports or what an Alarm Client supports?
You must implement what is required for the Facet that you are supporting. If you only support "A & C Acknowledgeable Alarm Server Facet" on the server side then you do not need any of the functionality that comes with "A & C Alarm Server Facet" (suppress, shelve,...). This also means that your Alarm Object can not expose the additional items in this type. In addition "A & C Alarm Server Facet" does have a number of optional ConformanceUnits which a Server might support (or might Not) on an instance by instance basis. Again if you are the Server you can choose to support these optional items. The CTT will test A&C and indicate what optional and mandatory items are supported.
Paul Hunkar - DSInteroperability
Thank you Paul,
we have implemented the code that supports Alarm states from Alarm Server , but Alarm client is not supporting those Alarm work flows.
As of now only Acknowledge and Confirm states are supported.
Tried with the clients - OPC UA Expert, Metrikon, Data Feed (Softing client), OPC UA Client
Kindly suggest if you know any Client that supports the Alarms states 'suppressed, shelving, out of service, inactive'.
Thank you for your time.