Transcript
specialist business units ranging across fit-out, partnerships and construction services. Because of our divisions and the different services they offer, he's trying to accommodate them all into what they need and what they want out of the business. Varying processes, standards, so trying to keep it as standardised as possible. Also, allowing for some flex to business needs is a massive challenge. Cloud is the way forward for us, it's that reliability and flexibility of cloud systems, so that was already an avenue we were heading anyway, but then I think the product library that we've got in Ivanti allows us to be a bit vendor and system agnostic. So, we don't like to have a one-fit-all, we need some flex, so having something that meets the needs but still interfaces nicely in and out to varying systems we've already got. The EPM solution was an example, it worked fine, but we needed something that could expand then into the self-healing and taking away some of that grunt work as admin. We've got your Intune, we've got your Azure attendance. On the old EPM solution, they were all separate with neurons, and as an example, it's all centralised and consolidated and curated data, so like I say, that was a win for us. DEX is going to be the next area, like I say, it comes with it, we've got it pulling in, but it's now on the case of, right, what do we want to do with it? It's setting us up for further enhancement, basically. We want to reduce that classic, bring DEX, and they'll try and fix it. We want to take some of that grunt back onto the system, let the system look at things that are happening, hard drives failing, batteries failing, things like that. Let neurons and DEX give us that information, then we can build upon it. So, the user's having a bad experience, we can set things in place that automatically start to remediate that, rather than putting all that pressure on an external third party. The service catalogue, the self-service function, I felt like was a good win for them. We could handle all the approvals, the costs, patch sorters, notifications, like emails in and out, tasks to different teams, so Newstart as an example. Previously, it was all done on like an old Word document, or something like that. Now, we can have it all logged online, and it can dish out relevant tasks, let people know that they need a license, send some tasks to the desk, send some tasks to our internal teams. It's the flexibility of it, and the customizability of it. We start off with just a request format for a new starter, but then you have to branch it out eight different ways. It allows us for that. And the business like that, we can do whatever we need it to do. I've not hit a roadblock yet. Our user and customer experience is always at the top. And my boss, the IT director, will say the same. His first thing for new users coming into the business is he doesn't want a bad thing about IT. So he wants their onboarding to be excellent. He wants them to have a laptop day one, phone, keyboard, and again, log in a request. It needs to be seamless. It needs to be quick, fast, get there, to get done. Everybody's got jobs to do. I try and say to the business, keep it all in the Avanti areas as best you can, because it'll just work better. And touch It has been up to there.
