Bridging the fiber network operations gap: Sending out crews - part 2. 

Welcome to Bite Size Fiber, the podcast where we break down the biggest challenges and best practices shaping the future of fiber and telecom networks, one bite at a time. I'm your host, Ellie Pulse, and this is episode four in our network operations series. In this episode, Sending Out Crews, part two, we're continuing our look at what happens after the truck rolls. We'll explore why access to the right data, tools, and knowledge is crucial in the field and how breaking down specialization silos can make teams faster, more flexible, and more effective. Once again, I'm joined by James Roach and Stefan Schneider, bringing their real-world insights on what it takes to build smart, connected field teams that keep networks running smoothly. Let's dive in. One more question I wanted to go back to when you were talking about the technicians and, you know, making sure that they have all the information that they need before going out on site. What do you think are some of the gaps that are kind of preventing them from having all the information they need? I think Stefan kind of stepped on this, and this is something that we've got to work with a lot of companies around, and that's they have siloed data. So they've created a process for a team to look at modems. They've created a process for someone to look at phones or small cells. They've compartmentalized their ability to build data sets, and it's hard then to pull that all into one spot. And what data do you pull into? So I think it's really about educating businesses that your data needs to be more efficiently built so that it can flow easily into a mapping software and give real-time data to a technician in the field or a construction worker in the field or someone doing work in your field so that it's available in real-time and not this report for this one specific thing and this report for this and this report for that. Can AI do that? Hopefully. But at the end of the day, we've got to teach MSOs and cable operators and telecom operators that how they collect data is just as important as where that data goes. Yeah. And who has access to that data. There used to be a joke many years ago that specialization is for ants, and people kind of forgot about that as time went on. People, like departments became like hyper-specialized, right? I am the modem tech, and I only know modems, and I can diagnose, you know, everything down to the modem, you know, down to a T. Oh, I am the access network tech. I am the distribution network tech. I'm the core network tech. And, you know, as you start stratifying the network, that becomes much more, you know, visible by even having techs that deal with core network routing issues versus customer-level routing issues. And, yes, you do need to have different knowledge and engineering departments to be able to support your operations. But for the tech in the field, that knowledge doesn't need to be that particularly specialized if they're just going in to do things, right? So we need to start rethinking more horizontal access to knowledge, and with knowledge comes data. So these things can be recontextualized for someone that's in the field that's not a specialized worker, right, because those are rare and hard to find, and be able to basically execute on-premise the knowledge that this specialized worker had before. We can't afford to keep having multiple operations teams with, like, different SLAs and different knowledge levels. We need to start thinking about how do we get to a point where customer folds get results so quickly that, again, they become invisible. It's also extremely inefficient to build teams like that. You know, our new networks are changing so drastically. You're always going to be creating that new team, and they're going to have access to that knowledge, and no one else will. You need a broad knowledge base in your network operations side so that anybody who's there, for the most part, can fix any issue. Absolutely. And if you think about how we're evolving into software-defined networking, the idea of the specialized support team that's, like, extremely focused on a specific area of the network, that's still necessary in the network operations center, and that's still necessary in product support teams. But that doesn't need to be the person that goes out to resolve a fault, because a lot of things can now be, you know, solved remotely, provided that it's not an infrastructure-level fault. And that then means that the people who need to deal with the infrastructure-level faults need to be much wider in knowledge. Yeah, and I think as we have more mobile-compatible softwares where you can do those as-built updates, things will probably get a little bit better to have all the information. The last key factor in that is we need to also understand what tools that technicians are using for data. Is it a laptop? Is it a phone? Is it a tablet? Because I think those drastically change how they perceive some of the things we're trying to provide. So we need to balance what do they need to accomplish and build that into our system so that their tools or their viewing portal into the network is simplified. It would be easy to go out with a tablet that's protected from weather and everything that you could easily move from your truck to up in the bucket or on a ladder or behind some building and have access to everything that we're looking at.