Much has been researched concerning the best ways to discover and alert stakeholders concerning the cessation of data streaming from an appliance. Here are some of the causes and they span everything from involuntary to intentional acts:

  • The appliance has failed in some way. This could be software or hardware related.
  • The appliance has lost power. This could be a power supply failure, overheating, or simply the appliance was shut off.
  • The bus battery has been reset (a common practice when a bus has troubles).
  • The bus is being serviced (cutting all power is common before working on vehicles)
  • The bus is in a state of disconnectedness (common in mobile climates).
Lacking any other evidence or data, Stream It's support process must assume that every interruption of data flow is an appliance-related failure. Evidence to the contrary is required for us to truly know who's responsibility the issue falls upon.

Outage Alerting Architecture

Stream It: Edge is capable of detecting loss of power through deliberate and unintentional acts. At the instant an appliance loses power, it sends a last-gasp event into the SlipStream network indicating the system is powering down because it has lost power. The potential causes of power loss are many, but knowing the appliance is without power, we can make a number of educated guesses about the cause. For example...

  • A loss of power at the location of the maintenance building at 400 S Taylor would be a usual and customary activity.
  • A loss of power while the bus is moving is a sure indicator of bus or appliance failure.
  • A loss of power while stationary, but outside the 400 S Taylor complex suggests the power to the appliance, or the entire bus, was intentionally disabled.
  • If no loss of power is detected and the data stream has been interrupted, this suggests the edge appliance and/or Stream It software issue as the likely cause.


From Stream It's perspective, any furtherĀ