AT&T / BellSouth
Telecommunications | Enterprise Scale | Charlotte, NC | 2000–2001
BellSouth operated one of the most extensive telecommunications infrastructures in the Southeast. In 2000, their judicial video conferencing network across North and South Carolina was held together by manual processes: Excel spreadsheets, phone calls from judicial offices, and technicians who hand-configured T1-based video switches and calculated routing by hand. When a judge needed to speak with a defendant in a remote facility, someone had to manually schedule the connection, verify the lines were available, and configure the switching infrastructure to make it happen. It worked until it didn't, and when it didn't, the consequences landed inside a courtroom.
The business problem had three sides. Judicial offices needed to schedule their own video resources without depending on BellSouth staff to do it for them. BellSouth needed to stop staffing a manual operation that technology could run. And the network had real capacity constraints: video bridging and T1 bandwidth were finite, and scheduling a call that the infrastructure couldn't support wasn't scheduling at all. Shad was tasked with building the system that solved all three. Leading a fourteen-member development team, he designed and built the platform from the ground up. Judicial staff could schedule video connections themselves, twenty-four hours a day, seven days a week, three hundred sixty-five days a year. A judge's office could see and schedule connections to the jails, prisons, and courts within their jurisdiction and nothing outside it. When a session was scheduled, the system verified line availability and confirmed that adequate video bridging and T1 capacity existed to support it, configured the video switching infrastructure at the appointed time, connected the parties, then released the resources when the session ended. BellSouth didn't need a team managing the network manually anymore. They needed people to watch over a system that largely ran itself.
The platform went from concept to production in under a year and ran twenty-four hours a day with no acceptable downtime window. The judicial system doesn't pause for maintenance. The architecture reflected that. What the engagement established early in the career arc was a standard that never changed: systems built for institutional environments have to work every time, because the people depending on them have no alternative.
The lesson Converge360™ carries forward: when the people depending on a system have no fallback, the architecture has to be the fallback.