Well That was Interesting: Real Stories from Real Customers

Before we jump into optical vision networks, I think the best story I'll tell you, and I don't have files I can share here on the screen, but we have a large campus.

customer and, um, this large campus was experiencing, um, a lot of different issues, but in particular, uh, their schedule overwrites were not always taken.

And it was one of those lost in the noise, you know, going on vacation, uh, or holiday, um, the operator will issue an override to change the temperature settings, um, for the entire campus.

And it would come back with a lot of alarms.

And of course, over the years, they tried to, to diagnose and troubleshoot them.

And, and you just got into the point where they just knew this was happening.

There would always be some zones in the campus that would not get the override.

No, just leave it.

Um, They were using our product and they were able to pinpoint there was one controller that happened to be a bridge between two sides of the campus.

And that controller was meant to be there.

It was meant to bridge the two sides of campus, but it was meant to be used fairly rarely, right? It wasn't meant to transfer a lot of data.

And unfortunately, when they were moving points, they were forgetting that depending on which server you put it on, it might be reaching across this controller.

and just got worse and worse and worse over time.

And our product was able to pinpoint to them where the source was, where it was going to, and being able to see the bottleneck in between, allowing them to reallocate that point to the server on the right side of the campus.

And after fixing that, it did take them a few weeks to fix it.

But really, the most important thing was that in the end, the schedule overrides were working.

The energy savings were significant.

And remember, they sometimes had to remove the overrides.

And then there was less hot cold calls.

So significant amount of energy saved because it was actually reaching the temperature that was intended.

And what it was, was simply a bottleneck created by one router that was not meant to work that way.

That was probably one of the coolest story, but let's...

Before

we move on, I have a little bit of context on that story from before Wasn't there something about the number of hours and dollars spent troubleshooting that over time? Like, didn't they quantify that to some extent? And it was a pretty high number of wasted time before ultimately our product helped them find it.

You remember that? Yeah, I do.