Content
# #google — 2026-02-18
**08:47 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771433234576239):** @Reno Hiltermann are you free around 10 or 1030 to work on this?
**08:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771433498453979):** yes
**08:52 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771433543418679):** let me know. I will be at my desk 930 to 1230
**08:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771433582920559):** K
**09:22 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771435338542129):** do you have a gmail?
**09:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771435568885299):** Mason.radke
**09:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771435573679199):** @gmail
**10:24 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771439070521239):** ok, i am ready to dive into this
**10:27 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771439226740679):** ok
**10:27 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771439233515869):** can you still get on the server
**10:27 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771439245049939):** you're going to have to remind me.. i'll take better notes this time.
**11:08 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771441692182349):** @Kevin I would like autosys to handle Signl4 subscription and bill monthly at first. Plan for annual after 3 month trial. Reasonable markup for your time. We will have 7 users (including Mason). Basic plan should be fine unless Mason indicates otherwise.
**11:18 [Kevin](https://slack.com/archives/C0A56N14A5S/p1771442286894419):** Okay sounds good. I will try to get that set up this afternoon
**11:23 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771442615638269):** Just before 2/26
**11:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771442775648609):** my original plan isnt panning out.. for P0, would it be ok to get push notification and call at the same?
**11:34 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443279888699):** Yes. P0 can be all alerts.
**11:34 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443295734949):** ok, there doesnt seem to be a clean way to do this. im investigating options
**11:35 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443355389749):** Simple idea. P0 and P1 to a new gmail, those are sent to Signl4.
**11:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443373172069):** Organization in Ignition.
**11:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443406214939):** Can P0 and P1 be groups that users in Signl4 select?
**11:37 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443442108499):** I think we can create multiple "teams" let me see if that will help us
**11:37 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443455572919):** Yeah that sounds promising
**11:38 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443492443119):** yes, this is sounding promising,
**11:41 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443708048689):** Users can enable/disable calls
**11:41 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443712784989):** individually
**11:42 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443756296829):** in the app? when im adding users to both teams, they are currently sharing the same notification settings... im working on this now
**11:42 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443766315599):** Yes in app
**11:43 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771443790513789):** They can also individually add delays up to 20 minutes
**11:43 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443797375079):** oh yes, i see that
**11:43 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443833870149):** ok.. "team pattern" is the keyword on that page
**11:44 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443871662859):** bingo
**11:44 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443875105659):** standby
**11:46 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443973975369):** if a P1 alert is not acknowledged in 60 minutes or X minutes do you want to escalate it to a call?
**11:46 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771443993849629):** or just persistent app/text notifications
**13:15 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771449346542319):** ok, big progress over here.
**13:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771449472437379):** I will consider escalation actions. Can the? be per user?
**13:23 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771449783888139):**
![[F0AFBKTMGK1_image.png]]
**13:23 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771449810057069):** its a bit limited.. if a signl is not responded to in a certain amount of time it can send the signl to another team or "manager"
**13:23 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771449828799629):** im looking into what manager means.. its likely a user role or something to do with scheduling maybe
**13:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771450563955079):** @Reno Hiltermann quesiton - There will be 5 pipelines, P0-P4. P0 will call with Signl4, P1 will text with Signl4, P2 will email using Ignition, and P3-P4 are Ignition local alarms only.
are we correlating these priorities to ignitions alarm priorities? P0=critical, P1=High, P2=Medium, P3=Low, P4=Diagnostic?
**13:37 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771450669098059):** and how do you feel about doing this in a single pipeline with a priority switch? so all alarms will be run the same pipeline.. but depending on the severity setting of the alarm it will execute P0, P1, etc
**13:42 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771450957454609):**
![[F0AFLR2GM4K_image.png]]
**16:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771461964989829):** Sorry been in meetings and had a doctor appointment.
**16:46 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771461997924629):** no problem. can we pick up tomorrow? i think we're close to a solution
**16:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462006945669):** I wrote the actions in a sheet.
**16:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462014565329):** Yes
**16:47 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462050697099):** That's actually great that the number corresponddirectly with Ignition.
**16:47 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462050830159):** i tested on my signl4.. triggered a high alarm. only got text/push.. triggered a critical alarm and immeditately got a cal
**16:47 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462059320829):** Perfect.
**16:47 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462060040029):** it was perfect
**16:48 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462086681799):** P0-P4 is a Google standard for alarms and everything else with priority.
**16:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462101026829):** interesting. yeah that worked out great then
**16:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462129503489):** once this is done, just setting the priority on an alarm will determine how it notifies
**16:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462146641059):** did you need a way for operators to make severity changes?
**16:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462150837669):** i wasnt clear on the sheet
**16:49 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462182523979):** The users sheet is just who gets what alarms.
**16:50 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462221014619):**
![[F0AGNDZFHR6_image.png]]
**16:50 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462222001809):** this part i mean
**16:53 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462402635899):** ahh. There is an Ignition Object that is a popup that has configurations for analog points. Similar to PlantPAX popups but simpler. I want to add a configuration for alarm priorities for each analog alarm. We don't need a tag, because the alarms already have 5 priorities built in. Just a configuration for HIHI, HI, LO, LOLO. It will be a simple drop down for each that assigns an alarm priority parameter to each level of alarm.
**16:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462420261009):** gotcha
**16:54 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462488076339):** At this point it should be simple. We can discuss tomorrow. There are also other features that could probably be added with minimal effort. Again, let's connect tomorrow. I have a doctor appointment from 945 to 1045ish. Want to meet before or after?
**16:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462709003299):** I should be logged in and ready to go by 7:30 or so
**16:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771462724214619):** Let's do what we can otherwise we can meet again when you're done
**16:59 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771462745339329):** Sounds good