← SSLOCSD

Clients/SSLOCSD/slack/2026/03/2026-03-03_south-county.md

slack
Source
1
Chunks
5
Entities
Doc
Type

Content

# #south-county — 2026-03-03 **19:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595024652369):** all findings indicating a momentary loss of communication between the PLC and SCADA.. and not the entire MCC PLC but just for 3 tags.. this further points to network issues. **19:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595049405129):** just a few CIP messages got dropped? or i dont know. **19:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595073298229):** writing up findings now. i think spice and a deep dive on the network testing is a good idea. **19:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595430174159):** [[F0AJ7EVS40K_Alarm_Investigation_Report.docx]] **19:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595472277619):** let me know if you want me to send this to them or if you just want to tell them it is likely part of the ongoing network issues we're troubleshooting. **19:54 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596474849069):** If you are happy with the report you can send it to them. **19:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596534085519):** did you look it over? there is no clear answer, but it almost has to be a network hiccup **19:56 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596611253839):** Ya I read the first page **20:00 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596845494259):** Is there anyway to know for sure it was network? It seems odd that it was only three tags. **20:01 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596919061789):** its not a physical network issue. its a protocol issue or factory talk thing.. or i dont know.. its the same issue that has been causing this bad quality communication failure messages and likely the faceplate slowness, etc **20:02 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596932399579):** Ah **20:02 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596932565899):** more ammunition to do a deep dive **20:02 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596936385889):** we need to figure it out **19:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595024652369):** all findings indicating a momentary loss of communication between the PLC and SCADA.. and not the entire MCC PLC but just for 3 tags.. this further points to network issues. **19:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595049405129):** just a few CIP messages got dropped? or i dont know. **19:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595073298229):** writing up findings now. i think spice and a deep dive on the network testing is a good idea. **19:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595430174159):** [[F0AJ7EVS40K_Alarm_Investigation_Report.docx]] **19:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772595472277619):** let me know if you want me to send this to them or if you just want to tell them it is likely part of the ongoing network issues we're troubleshooting. **19:54 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596474849069):** If you are happy with the report you can send it to them. **19:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596534085519):** did you look it over? there is no clear answer, but it almost has to be a network hiccup **19:56 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596611253839):** Ya I read the first page **20:00 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596845494259):** Is there anyway to know for sure it was network? It seems odd that it was only three tags. **20:01 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596919061789):** its not a physical network issue. its a protocol issue or factory talk thing.. or i dont know.. its the same issue that has been causing this bad quality communication failure messages and likely the faceplate slowness, etc **20:02 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1772596932399579):** Ah **20:02 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596932565899):** more ammunition to do a deep dive **20:02 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1772596936385889):** we need to figure it out

Extracted Entities

TypeKeyValueConfidenceEvidence
contact Mason Radke Mason Radke 90% 19:30 [Mason Radke]: all findings indicating a momentary loss of communication
contact Kevin Kevin 90% 19:54 [Kevin]: If you are happy with the report you can send it to them.
system SCADA SCADA 90% momentary loss of communication between the PLC and SCADA
system PLC PLC 90% momentary loss of communication between the PLC and SCADA
system FactoryTalk FactoryTalk 80% its not a physical network issue. its a protocol issue or factory talk thing
File: Clients/SSLOCSD/slack/2026/03/2026-03-03_south-county.md
Updated: 2026-03-04 14:50:30.417903