--- title: "The STREAM Method™ — Advanced Industrial Network Troubleshooting" description: "A six-step cyclic troubleshooting methodology for complex and intermittent industrial network problems: Scope, Test direction, Replicate, Execute, Assess, Mitigate. By River Caudle." canonical: "https://rivercaudle.com/stream/" author: "River Caudle" keywords: - STREAM Method - advanced troubleshooting - OT troubleshooting - intermittent network issues - remote troubleshooting - complex network problems - ICS diagnostics - Scope Test Replicate Execute Assess Mitigate - River Caudle - Riverman robots: index, follow license: Riverman Fair License v2.0 --- # The STREAM Method™ **Advanced industrial network troubleshooting.** > *"Follow the STREAM in cycles until you reach the solution."* Originated by [River Caudle](https://rivercaudle.com/). Used under the [Riverman Fair License v2.0](https://rivercaudle.com/license/). --- ## Why this exists [RIVER](https://rivercaudle.com/river/) is for the device in the cabinet. **STREAM is for the thing that intermittently disconnects three HMIs twice a day and only when the foundry is running.** Six steps, designed to **cycle** — Execute → Assess → Execute → Assess — until you reach the solution. Expert-friendly. Remote-capable. Built for the issues that RIVER's linearity can't catch. --- ## Overview | Step | Action | What it addresses | |:----:|------------------------------|--------------------------------------------------------| | **S** | Scope the Symptom | Need for formal information gathering | | **T** | Test Direction | Rigid linearity of bottom-up troubleshooting | | **R** | Replicate or Review | Intermittent issues that can't be observed live | | **E** | Execute Targeted Action | Overly broad "examine everything" approaches | | **A** | Assess the Result | Missing feedback loop in complex problems | | **M** | Mitigate & Maintain | Combining immediate fixes with long-term prevention | --- ## S — Scope the Symptom ### What to do - Define the exact problem and its impact - Identify affected systems, users, and processes - Determine the blast radius and urgency level - Gather initial information from users and monitoring systems > *"What is the exact problem and its blast radius?"* **Addresses:** The need for *formal* information gathering before jumping into troubleshooting. --- ## T — Test Direction ### What to do - Assess whether this is likely physical (bottom-up) or logical (top-down) - Use experience and symptoms to choose starting point - Consider environmental factors and recent changes - Make an educated decision on investigation approach > *"Is this likely a physical or logical issue?"* **Addresses:** Rigid linearity. STREAM lets experienced technicians jump to logical starting points rather than mechanically walking Layer 1 up. --- ## R — Replicate or Review ### What to do - **Active issues** — attempt to reproduce on demand - **Intermittent issues** — review logs, monitoring, historical patterns - Gather evidence from multiple sources - Build a timeline of events and symptoms > *"Can I make it happen on demand, or do I need to review logs/data for clues?"* **Addresses:** Intermittent issues that can't be observed in real-time. --- ## E — Execute Targeted Action ### What to do - Based on gathered data, perform **one** specific change or test - Make changes incrementally and deliberately - Document what you're about to do *before* doing it - Focus on single variables to isolate cause and effect > *"Based on the data, what is the one specific change or test I will perform?"* **Addresses:** Overly broad "examine everything" approaches with focused action. --- ## A — Assess the Result ### What to do - Evaluate: did the action fix, change, or do nothing? - Document what you learned from this iteration - Determine next steps based on results - Decide whether to continue cycling or try a different approach > *"Did my action fix it, change it, or do nothing? What did I learn?"* **Addresses:** Missing feedback loop for complex problems requiring multiple iterations. --- ## M — Mitigate & Maintain ### What to do - Implement the permanent fix - Document the solution for future reference - Update procedures, monitoring, or preventive measures - Ensure the solution is properly tested and communicated > *"Is the fix in place? Is it documented for the future?"* **Addresses:** Combining immediate fixes with long-term documentation and prevention. --- ## The STREAM Cycle™ Linear methodologies don't survive complex problems. STREAM is designed as a loop. **Execute → Assess → Execute → Assess.** Each iteration produces new data that informs the next action. ### Decision points after Assess - Return to **Execute** with new targeted action - Return to **Replicate** if you need more data - Move to **Mitigate** if the problem is solved ### Escape conditions - Problem resolved → Mitigate - Problem requires escalation → document and hand off - Problem requires a maintenance window → plan and schedule --- ## STREAM vs. RIVER — when to use which | Scenario | Method | Why | |-----------------------------------|---------|----------------------------------------------| | Device dead in cabinet | RIVER | Simple, physical-first | | Intermittent network performance | STREAM | Requires data analysis and cycling | | Remote troubleshooting | STREAM | All steps can be performed remotely | | Complex multi-system issue | STREAM | Handles scope and iteration well | | New technician training | RIVER | Simpler, linear learning | | Experienced team investigation | STREAM | Leverages expertise and flexibility | --- ## STREAM Advantages ### Expert-friendly The **Test Direction** step lets experienced technicians leverage knowledge — skip physical checks for known software issues, start with logs for familiar failure patterns, use intuition built from years of experience. ### Handles complexity The **Execute → Assess** cycle manages multi-variable problems — each iteration builds knowledge, failed attempts provide valuable data, complex problems break into manageable steps. ### Remote-capable Every STREAM step works remotely — Scope (phone, tickets, monitoring), Test (mental), Replicate (log analysis), Execute (configuration changes), Assess (remote testing), Mitigate (documentation). ### Intermittent-issue ready The **Replicate or Review** step specifically addresses problems you can't see — historical log analysis, pattern recognition, timeline correlation, proactive investigation techniques. --- ## STREAM in Practice ### Scenario 1 — intermittent HMI disconnections - **Scope** — three HMIs losing connection randomly, 2–3 times per day - **Test** — likely network/logical (multiple devices, time pattern) - **Replicate** — can't reproduce on demand → review switch logs and monitoring - **Execute** — enable detailed logging on affected switch ports - **Assess** — logs show CRC errors during disconnections - **Execute** — test cable integrity on affected runs - **Assess** — cable tests reveal intermittent opens - **Mitigate** — replace cables, update preventive maintenance schedule ### Scenario 2 — sudden production line halt - **Scope** — entire line stopped, PLC comms lost, production impact high - **Test** — could be physical (power/connection) or logical (network storm) - **Replicate** — issue is active → immediate investigation possible - **Execute** — check PLC status lights and power - **Assess** — power good, status lights indicate network fault - **Execute** — check switch port status and connectivity - **Assess** — switch port down, cable issue suspected - **Execute** — replace patch cable - **Assess** — line restored, production resumed - **Mitigate** — document cable failure, check other cables of same vintage --- ## Quick Reference Card | Step | Focus | Remote? | Key output | |:----:|----------------------|:-------:|---------------------------------------| | **S** | Problem definition | ✓ | Clear scope and impact | | **T** | Investigation strategy | ✓ | Bottom-up or top-down approach | | **R** | Evidence gathering | ✓ | Reproduction or historical data | | **E** | Focused action | ✓ | Single, targeted change | | **A** | Results analysis | ✓ | Learning and next-step decision | | **M** | Solution | ✓ | Permanent fix and documentation | --- ## Closing > *"The best troubleshooting methodology adapts to both the problem and the troubleshooter."* --- ## See also - **RIVER Method™** — Layer-1-up cabinet troubleshooting: - **SHIP Framework™** — well-designed networks are easier to troubleshoot: - **Frameworks index**: - **Riverman Fair License v2.0**: --- *Document — The STREAM Method™ · Originator — R. Caudle · Rev. 01 · Issued Houston, Texas, 2026.05.11*