Good morning everyone,
I’m looking for some guidance on how to organize real-time and historical alarms into separate areas.
In my current projects, I’ve always used Ignition by splitting the databases, but typically with a single tag provider and a single alarm journal per database.
Now I’m facing a new requirement: an industrial plant may be divided into multiple areas, and I need to separate alarms (both real-time and historical), trends, and other elements accordingly.
Depending on the user login, certain users should be able to view all areas, while others should only see specific ones.
How can I configure this on the gateway and also control what is shown in the real-time and historical alarm views?
Any advice or best practices would be appreciated!
Display Path or Tag Source is the easiest. On vision, i personally use Display Path.
yes, i agree with you. I use Perspective and I think this is the only way
if I create different Journal Profile with different filter source; how i che show every profile on the journal table?
it seems that "filter - condicions - source" and "filter - condition - provider" refer to Tag provider; so how i could show different journal profile?
I'm not certain if I'm following your question, but if you're asking how to change a journal filter dynamically, I do it by creating client tags that store the filter value, then bind the journal filter to that tag. Change the value of the tag, the filter then changes.
Sorry I wasn't clear.
Theoretically, on Gateway, it's possible to create different Journal Profiles already associated with different tag filters in the same database. I don't understand how to display these different Journal Profiles dynamically on the Perspective table component. I tried, but it doesn't work. All the historicized alarms are displayed; it works only the filter in the "filter - conditions" section.
Ah, I understand now. Unfortunately my experience with Journal manipulation is with Vision, so not exactly certain on the mechanics in perspective. Hopefully one of the perspective gurus will chime in. But it still seems you simply need to bind a tag to the alarm journal table that defines which alarm journal on the gateway you are using.
You are expected to send different journals to distinct tables in your database, and point your alarm history table UI at the desired journal.
Thanks a lot for your input!
Yes, I’ve decided to keep things simpler by using a single database and a single Alarm Journal Profile.
Instead of separating the alarms physically across multiple journal profiles or databases, I’ll filter the real-time and historical alarm views dynamically in Perspective using the source or displayPath, based on the user's area or roles.
This approach keeps data centralized and still gives me the flexibility I need in the UI.
Appreciate your help and everyone else’s suggestions — it really helped me clarify the direction to take!