Have a site that one server with multiple sites. Most vendor would like setup alarms on jace, I think it is easier to manage if all alarms and trending setup on server. Any suggestion?
I would set up the alarms in the Jace, then push them to the server for client interaction.
To add to this (sorry, I didn’t see this before), putting Alarms in the JACE and pushing them to the supervisor is the way it’s intended. What you can do is create the same alarm classes in each JACE and the supervisor and in the alarm properties click “use existing” should the customer need something for locations and such or different types of classes like Fan Alarms, Flow Alarms, etc.
But you have to create alarm class in each jace. If Jace is not setup as email out, what is advantage setup alarms in Jace? I preferred setup alarms in server. So I can easier manage them.
It’s all a matter of preference. But here are my thoughts:
JACEs should have as much local programming as possible. Supervisors go down more regularly than JACEs do. So if a supervisor gets turned off for any reason, nothing is happening and nothing is being collected. If everything is as the JACE, then routed to the supervisor, at least there is a record somewhere of something happening.
I’m not saying you’re wrong in the very least and I understand what it would require going back to the JACEs. To me, as long as the customer is aware of the risks, then all should be good.