Improved KPIs with Enhanced Day-2 NetOps

Now as you continue to move to your new infrastructure, um, you've got, um, you, you have production nodes and, uh, all embedded on the new, the, the new operating system, the new management platform. What are you doing differently now, carrying forward? You know, of course we've talked about digital twin, uh, to a certain extent, but, uh, you know, you've talked about integration with CICD processes and so forth.

Yes. What do, what do day two operations look like for the whole team now on the new platform and infrastructure? Well, uh, currently, you know, um, on, on the new infrastructure we have, uh, the team, now it's becoming more, um, uh, you know, date, the date, day two plus is becoming more, more routine kind of changes, uh, as we are of course moving the, migrating the data centers and, and building our existing data centers on.

But, but also from an architecture perspective, we are now trying to do more in terms of, you know, implementing more AI functionality. Mm-hmm. To, to now to tell us more about the operational, you know, if something goes wrong, if an incident happens, uh, don't give me raw, raw information, even if it's correlated.

Even if correlate, give, gimme an RCA, gimme an RCA and point me to what, what could be the problem and what could be the impacts. So may maybe something has happened, but actually there is no real impact to the network. So a link might fail.

Mm-hmm. But there's enough in redundancy that we shouldn't worry about it. Sure.

Tell, tell me. I don't have to worry. So we're trying to build this more of an intelligent intelligence that there is some entity that is entity, uh, that is aware of our topology.

Sure. Our topology Yeah. And our network that can actually give us useful information about incidents and the results.

But the main, the main thing that's interesting also in the operational aspect is I, I, I talked to the operational team and, you know, they, they, they have a huge reduction in, in incidents, you know, like, like 80% to what we had before. Yeah. Not, not only, not only the tool is part of the aspect, but the, I think the, i, the, the NetOps and tracking and, uh, this idea of doing things before you implement them helps a lot in avoiding, uh, avoiding problems.

So, so the, the operations team are saying that most the, the are saying to me that most of the time they, they don't find the same problems that with what they found before, the fabric is very stable, very consistent. Stable, consistent is as, as expected. There is not nothing that surprises them.

Most of the things they're dealing with is maybe access to, to servers, uh, low balancers files, physical, physical stuff that is going on in the data center, but not from a, a design or, or, or a routing or, or this kind of, uh, perspective. So it, it shifts, it shifts their, their, their efforts, you know, away from debugging, you know, lower level Sure. Details that the fabric should, should take care of.

So it's a, it's a different, different type of challenges, but much, much less than before, much less before. So that's a great example of the tooling decisions that you make, really having an impact on your operations team. Right.

And you're dropping 80% of your tickets. Um, that's, um, and, and I know, um, you know, your leadership has, has cited the same statistic, you know, 80% reduction in tickets. That's, that's huge.

That's certainly impactful. Didn't you also make some decisions on how to, um, implement e dda? Like you could have gone with a local install for EDA, but you opted to go with the SaaS option.

What were, what were some of the thoughts you had to, to weigh there and why did you ultimately choose the, you know, ADA SaaS version? Okay, so, so the ADA SaaS really, uh, we're, we as a network and, you know, network team, we're not in the business of running edda, you know, or, or we want to make use of it. Sure.

We want to architect around it. So, so we offloaded that, that effort to the I team where they, they can implement it in the cloud, whatever, what, whatever cloud they want, they want to go to. Sure.

To GKE. They want to go Google or AWS whatever they want. We don't care.

We just want to connectivity to it. We want, you know, the upgrades to happen. We want them to monitor the health of IDA itself.

You know, uh, maybe their, their, I comes with many extra add-ons, you know, with RCA, uh, you know, correlation. Uh, they do some kind of AI into, into giving you in, you know, analysis of anything that happens. So, so that's, that's also a plus that comes with it.

We really didn't want to, to think about IDA too much. We wanted to rather use IDA architect around IDA and, you know, think about our, our architecture more and building more enhancements to the solution itself. So ED SA in that perspective, uh, saved us a lot of effort and, and the team there was very helpful for us.

So we, we liked that. We, we, we were, we were glad we went that way. Not in the business of actually running edda.

You just want it to work. Right. So that's a great encapsulation of that.

Very good. Yes. Well, what else is in store in the future here?

You know, you've, you've laid some really important foundations here for, you know, making real improvement for the resiliency of the network and the lives of the operators. Um, what, what's coming down the pike? What, what are you gonna be able to do in 2026 that you couldn't do in 2025?

I think, I think now concentrating on enhancing, enhancing the solution using maybe more AI that is native, you know, native to either, either is coming up with lots of capabilities mm-hmm. That are AI related, that we can chat, we can chat with either, we can talk to it, we can tell it what went wrong, what, what's happening. So that part, you know, we used to actually, we build in our solution, but a way or around IDA to, to, to fill in that gap.

But I think in, in the next release, we we're gonna be merging some of our tools with IDA and maybe merging our automation into Edda itself. IDA has the capability to write your own apps. Sure.

We would, I, I think that's something we would like to do is, you know, bring in our, our automation and pipelining to, to, to be within ida, to be within, to be need IDA native. So the user doesn't really have to think, um, dealing with Git. I'm dealing with either.

Maybe we can merge something together there. And also more on the operations aspect to get, to make operational RCA more intelligent, which either will add and we'll see what it adds and try and fill in the gaps there. As well as, as you know, we're still Nokia's growing.

Mm-hmm. We've got, we've got acquisitions and stuff like that. So there will be more data centers and, and as I said, our, our architecture now is very modular.

It's not flat. It's not like it doesn't look like a data center. It looks like many small mini data centers connected together.

Sure. So we are able to absorb, absorb those changes. And that's, I think will be a main task for us next year.

Ahed, thanks so much for talking with us today. It's been a pleasure. I look forward to hearing how things progress in 2026.

Thank you very much for having me. It is very exciting for me and I'm very passionate to, to, to talk about our work. 'cause it's, it really is exciting and interesting.

It comes through in every conversation I've had with you. So thank you. Thank you for sharing that passion.

Thank you. And turning it into real concrete, you know, this is what you're actually experiencing in the new, uh, the new network infrastructure in, um, Nokia Enterprise. It.

Thank You very much. Thank you for having.