Winning with Analytics
September 06, 2017
Melanie Karunaratne | Senior Manager, Product Marketing | Ivanti
Nick Gehr | Manager, Enterprise Application and Support Services | Aviall, Inc.
Christy Phongsavanh | Warehouse Operations Control Center Specialist | Aviall, Inc.
Are you surviving on adhoc excel spreadsheet reporting or relying on word of mouth data points to make decisions? Everyone is searching for those best practices to turn metrics into meaningful reports. So, how do you get immediate, targeted, analytics for different informational needs and decisions?
Join Ivanti customer Aviall, and hear how they solved their reporting visibility challenges. Learn how they went from manual reports to daily dashboards in their Control Center. Hear how they answered important questions about customer experience and delayed order shipments. See how they use Ivanti Xtraction to improve operational control and on-time shipping.
Moderator: So just to let you know that this webinar is all about how Aviall has solved their reporting challenges, and they'll show a little bit of their reports and what they've done. And then if there's time at the end, we'll get to your questions and answers, but we have muted the lines for the comfort of everyone listening. If you do miss anything or if you want to pass this on, then we are recording this webinar, and we will be sending this out and putting it online. So what I'm going to do now is ask Christy to take the ball. And while she's doing that, I want to ask Nick to introduce yourself and tell us a little bit about your role.
Nick: My name is Nick Gehr [SP]. I'm the manager of the enterprise application support services team here at Aviall. I manage everything from the end user computer experience all the way down to the application layer stacks that our users interface in from a day in, day out basis. Aviall itself is the world's largest diversified aircraft parts distributor, delivering aviation parts and repair services globally. We have over 25,000 customers. We serve over 240 OEM products. We have over two million part numbers, 40 global stocking locations, and have over 1,400 employees.
Moderator: Wow. That's a lot of numbers, a lot of parts, and a lot of things that you need to keep track of. I can understand why you need reporting. So thanks for that, Nick. Christy, let's go to you. Tell us a little bit about your role and what you do.
Christy: Hi, my name is Christy Phongsavanh [SP]. I'm here with Aviall as the operations control or the warehouse specialist. So in here, operations control, you think a lot of things, right? Heart and brain. You think the central command. You think the place that you have to contact to get anything done, to ask your questions, to [inaudible 00:02:18] any requests. Our objective is just that we are the eyes and ears of Aviall CDC or Central Distribution Center or the one point of contact in warehouse globally. All the numbers you just heard just now, we get in our email queue or now, ticketing system with [inaudible 00:02:37].
So a small breakdown. Just a few of our tasks, and we do a lot more, but to give you a little bit of a scope, a small breakdown is we expedite shipping inbound and outbound. We problem-solve, and we release waves or orders to the outbound processes, so to give others work, and we have to monitor just about a lot, right? Everything now looks a little different. This is how it looks now. We do have Xtraction displayed on a projector. The smaller monitors do have individual metrics from Xtraction as well.
So before Xtraction, a lot of people asked, "How did you manage to see your work?" Or, "How did you know to give others work? What did you do?" Well, I was really was a little bit handicapped. You know, for the longest time, we only had one report to work out of and that only showed step one out of the many steps just mentioned. And that only shows us to release work. A little hard. The manual way was to literally go out into the warehouse and look at the pack line. Oh, there's many boxes. And that's about it. Our other formers include this. This is called The Missed Details Report. So we got that about two years after the first report. Still didn't show everything that we needed to see. This was only a way for us to see possible missed shipment that didn't go out that door, but still didn't help us see problem solving. So it didn't help us to see the physical amount of shipments outside. So it didn't help us to see what we had done for the day.
And last but not least, our last report that we ever got before Xtraction was The Aged Orders Report. This only shows just shipments that didn't go out. I still have the full cycle of my work that I still didn't get to see.
Moderator: Okay. That's great, Christy. I remember you saying that you...if someone asked you a question, it could take up to 30 minutes to research. So with those reports, I can understand why. You've got a lot on your plate. So let's talk a little bit about the Xtraction. Where did you hear about Xtraction?
Christy: I attended Interchange 2016. I took about...I wanna say about two labs and [inaudible 00:05:20] classes on Xtraction, how to report, how to use it, hands-on labs. I loved...I fell in love with the product. I fell in love that I can just create reports out of a whim, what we need to see. I fell in love with just that. I can now see the other questions that I can answer. I can, like, "Okay, yeah, here's what we did. I mean, yeah, we got 80 tickets that last hour, but this is what the team did." "Who's working on your ticket? Just this person here." And we got to see the different statuses. We got to see what's awaiting in response, what's resolved. Before, we didn't get to see that. Interchange definitely gave me a big help.
Moderator: That sounds great. So you just...with things and daily dashboards here, you mentioned that that was one of your pain points previously. So talk us through this, if you can.
Christy: Definitely, definitely. I can do just that. So what I'm about to play, so I just click Xtraction video just to show these tiny reports that you see here up close just a little bit, and I'll explain as we see them.
Moderator: Okay, sounds great.
Christy: All right. So what you just saw was our daily dashboard. You see the assigned group. You see the person who's [inaudible 00:06:42], you see how many have you gotten. Here, you would see the person who's working your ticket. And zoom that, you'll see their statuses, if they're responding, and then CPIs, of course, and then our aged. So here, you see our AIG to OCC. AIG means aircraft on ground, scary situation. Before we literally had to check if our email queue was red, and that's how we knew. Now we can see our names. This is just canceled tickets. A lot of mess, as you can see here. We canceled 400 of someone of an email and so that gets a little crazy. That's a little bit of clogging up of our email queue, right? And so that's our dashboards in depth.
Moderator: Wow, that's good. And, obviously, we're seeing a video. You're not going through and drilling down, but clearly, you can pull those, pull whatever you need for whoever needs to see them from different data sources, I'm guessing. So, and actually, speaking of data sources, Nick, can I ask you what data sources we're using at Aviall at the moment?
Nick: Yes. Currently today we are using Ivanti's DesktopNow data source. We're also interfacing with Ivanti's Endpoint Manager, Ivanti ServiceDesk, Ivanti Patch for Windows Server, Ivanti Xtraction, and Ivanti Avalanche.
Moderator: Great. So you're pulling in data from these separate applications into the dashboards that Christy is showing.
Nick: That is correct, yes. We're able to pull from multiple different data sources and combine them either in a single dashboard, or go ahead and separate them out and parse them however the data makes sense to the particular individual that needs to see it.
Moderator: Okay. And that's something you guys are able to do without kind of going in the backend and all that kind of stuff.
Nick: Absolutely. I don't have time to try and hunt down a data analyst every time that we're needing to get something built. That's why a tool like Xtraction is enabled to enable the end user or the business or the IT specialist to go ahead and create the kind of relevant data that they need to see at any given point in time on a whim.
Moderator: Sounds great. And we had a chat the other day, and you had mentioned that you were looking at other connectors or other data sources because clearly Ivanti is not only application that you have in-house.
Nick: Oh, absolutely. That's the beauty of the way that Xtraction works because you can connect it to multiple data sources, it's not just one of the two of the Ivanti product suite. You can take the data connector. You can build it. You can apply it towards whatever makes sense, everything from the most basic spreadsheet up to the backend SQL database, an Oracle database. You name it.
Moderator: Sounds good. I'm glad you're a fan, Nick.
Moderator: Okay. Great. So we talked about the fact that, you know, you're using it. You're using the connectors. You're seeing your dashboards quickly. You're seeing the benefits from your end. We had a chat the other day about the fact that you, Christy, as business team people, you used Xtraction first, and then actually, it was IT that came in after that and wants to use it, and you guys trained them on. So a bit of a kind of a backward situation. And we've got Lee on the phone as well, I believe. Lee, if you're there, we'd like to introduce Lee Burns, who's our enterprise support and technician from Aviall. And I think, Christy and Lee, do you want to talk a little bit more about the benefits that you've found?
Lee: Yeah. So being a technician here at Aviall, we deal with a lot of data. So at first, we didn't have any ways of tracking what our team was doing or just a way to look at the data that was out there. So when I was introduced to Xtraction, it was just the way to look at what was there in a queue, what is the status of a request, like iPhones or iPads are going. We could track the laptops and the desktops that needed to be built for the end user at that point. We also have personal data for our teams to see how our queues are looking. And this is just a dashboard here that we deal with the SLT, the senior leadership here, and what needs that they might also have. So Xtraction has come in handy along the way of actually learning how to build these dashboard [inaudible 00:12:01] and how to point towards the right data, so we can...so what we need. And I worked alongside with Christy, who helped me figure out how to connect all of these.
Christy: How were the challenges that Xtraction solved for you?
Lee: Like, it solved the... It made things... It was just easier to track the data that was out there that we weren't seeing.
Nick: I think one of the biggest challenges Lee ran into was that on any given day, I would come to him and I'd ask him to speak to something in particular, and he wouldn't necessarily have that type of data in front of him. Once we started working with Christy, we were able to start formulating these dashboards to really start to be able to have the relevant conversations about what was due, what was where, what was when, and being able to speak to things in a moment's notice, being able to glance up at the wall, and just like you saw on the picture earlier where all those dashboards are up and visible. You know how many sitting and stuck on one particular thing, what we're waiting for, being able to track what's going on and where, knowing where a data element is at any particular point in time, just being able to speak to the data when it's relevant in the conversation.
Moderator: Sounds great, guys. And, Lee, you mentioned that you have dashboards for senior management. And, Nick, you mentioned that you... And, Christy, you're showing your control center. So, Nick, you've got dashboards, the different types of views or different types...or different people, I should say, not...
Nick: We've got them broken down based on each individual analyst and technician, depending on the role that they're working in, showing what their daily queues are, what their monthly queues are, and when. We're also taking it down to other request level and breaking it down so you can see what are the particular items that we wanna protect, parse specifically. So whether or not how many desktops are being deployed throughout the year, how many desktops are being requested throughout the year, how many phones, how many iPads? What are the MiFis that are moving, and what...where are those at?
Big thing that we use around here is for multifactor authentication. So we require token distribution to go out there for that. So we track those as well, trying to know how many are sitting out there in our request status that are waiting. So those are people we can't currently do anything. And then how many have closed out, so we can understand how many people are still sitting out there in a status where they technically can't do anything until we get that delivered.
Moderator: Okay, that sounds great. Sounds like a lot of things, lot of challenges solved there. So, Lee, is there anything else that you want to add before we move on?
Lee: No. I think Nick hit the nail... That's basically it.
Moderator: Fantastic. Okay, all right. So thanks for that. So we've heard from Lee in IT. We've heard from Christy, who's a business analyst. We've heard from Nick. So, Christy, talk us through what you... You know, we heard some of the general benefits. Talk us through about the kind of higher level benefits this has brought to you, if you can.
Christy: Oh, definitely. We saw a huge improvement. This slide here 315 minutes isn't the best time, 16 hours to respond to something [inaudible 00:16:15] is not the best as you can kind of see, right? So the numbers to the left show three Xtractions and early, early, early service desk, but numbers to the right show current day, kind of present day. And you can see there is a bit of a drop.
Moderator: Just a little bit.
Christy: [crosstalk 00:16:40] just a little bit. It's not much, right? You don't really notice it. These numbers we can report out to senior leadership. These numbers we can report out in meetings. These numbers we can report out to our managers and just [inaudible 00:16:57] just like, "Hey, look at what we've done."
Moderator: That's great. So you've got accountability on what's going on. They can see at glance because it's real time. So that's really impressive. And we talked about the fact that you no longer have to wander around the warehouse, so although your Fitbit steps have probably dropped, your productivity is clearly going up.
Christy: Yes, I was platinum for years, but I do have visibility now.
Moderator: All right. Okay. And, Nick, how is this helping with the decision-making? Has it become more data-focused or...
Nick: Yeah, it's definitely helping us drive more data-driven decisions. I mean, in the agile workforce that we're all living in today, we have to be able to make decisions on a moment's notice, but we need to have the right data at any given point in time to make those types of decisions. I don't wanna just make it on gut feeling. I don't think we can survive anymore on those types of scenarios. You know, you'll hear one thing, but data speaks other. So being able to have that data when it makes sense, you know, getting ambushed and being able to send that elevator conversation and having those boards resident, you know, and being able to access that from any time, any place, that's really key to be able to have the appropriate conversations when they matter.
Moderator: Great. Okay. And I can see a slide that's up here now. Incidents. This is something to do with your compliance, right?
Nick: Absolutely. This one is, as it says right in the middle, it's critical. This one ties back to a compliance control in how we're doing on a particular thing and how it affects, you know, ultimately our ERP, and then...and that's big time auditable. So we have to be able to stay on top of that and be able to speak to those things. In the moment, there is a ridiculous SLA that's wrapped around this, so I need to know when this is happening and in that moment. So that critical piece is literally, you know, in the last 24 hours where I'm tracking that. So I need to be...I literally have this on a monitor that sits in my office on a wall, and I'm watching this more than I probably ever want to, but it's one of the more critical pieces that I need to be aware of at any given moment.
Moderator: Okay. And if you didn't have this, when we talk about compliance and what happens, what's the impact?
Nick: It's not good. Yeah, that means the sad part is, without this, I'd probably have to have somebody babysitting this or monitoring this, but now with a tool like Xtractions monitoring this for me, when this occurs, I'm able to get a report out. I'm able to get an email. I'm able to, you know, glance up at the wall and see, "Oh, man, this is happening. I need to be...I need somebody on this, and I need them on there fast."
Moderator: Right. Great. So that helps a lot from that perspective. And we just bounced around a bit, Christy, and then we talked about some of the benefits. Is there anything that you wanted to add around that in general?
Christy: The benefits, I'll add to that. We display Xtractions everywhere, literally everywhere in the room, [inaudible 00:20:18] personal laptops, computers. I have...in my team, we have two people that sit out in the warehouse. So, you know, they're not in office or anything, but I give them the link and the ability to see what they're doing and that gives them drive. Probably, it's just a global thing. We have different people that are just really interested in Xtraction and what it can do. And so we're just trying to display it loud and proud with all the benefits given us, especially the time that it's reduced for us. There's not much more to say about it. It just absolutely saved us. It's like our crutch now, right? It holds us up.
Moderator: Well, that's good to hear, kind of, I think.
Christy: Well, yeah.
Moderator: That's okay. All right. So we talked a lot about the challenges that you've had. You've talked about how the difference that Xtraction is making at the moment, and quickly, we've gone through this impact, and from these numbers, you can see really see that is has made an impact. Nick, what the future hold for you? What are the challenges that you need to solve? How is Xtraction going to help? What are you looking at next? If you can tell us as much as you can tell us in the boundaries of confidentiality of the 100-plus participants on this call.
Nick: One of the areas that we're looking to apply it next is being able to read into our SDLC environment and understand what's going on there, tie that back from a relational aspect into our day-to-day IGSM environment and understand where those are staying in lockstep so we can make sure we're displaying the right data elements. Tie it together so the correct decisions can be made in those wins and, you know, trying to move forward with an agile presence and have the right data present when it matters. That's one of the bigger places where we're looking to push for next.
Moderator: Sounds interesting. And I know, you know, we're chatting constantly with you about your world and how we can help you there, so that's great stuff. Okay, all right. I think we have one or two questions coming in. And anyone who wants to ask questions of the Aviall team, please use the chat facility, and we will get to them. But let me just see what's coming in at the moment. We have got one here. Hold on a sec. Right. This is...oh. Okay. I have... Erica, I don't know if you can unmute and read out the question because I have just lost control, unfortunately.
Erica: Absolutely. Here is a question from Donald. By tracking data that you weren't seeing, do you mean you were answering questions that you didn't even know that you needed to ask?
Moderator: Okay. Nick, does that make sense? Do we need to get some clarifications?
Nick: Yeah, it makes sense. Yes. To answer simply, yes. We were seeing different data elements that we weren't understanding if there was a relational component to that, and how those tied back into the way various things were being submitted. So it was giving us visibility to that aspect, where we didn't even realize this was a problem, but we started to see trends that were taking place. And depending on where it came in from an intimate management perspective, we were seeing things that this was a clear evident piece of, hey, there's a lack of documentation out there. There's a lack of user training. There's a lack of, you know... They were making us more aware of things that we didn't even necessarily know were problems. So that's...I hope I answered the question in that regard, yeah.
Moderator: Great. Okay. Thanks. If the caller wants more clarification, just use the chat facility. Okay, so back on [inaudible 00:24:44]. Thank you very much. I can see another question coming in, and probably let's get... I think, Nick, you touched on this with the connectors, but someone's asking what does it entail to configure the connectors? You know, straight from the horse's mouth rather than me as an Ivanti person saying. What does it take for you to configure?
Nick: It really was not that hard at all. I mean, you get the information from your Ivanti salesperson and work with your Ivanti team related to Ivanti products, that is. Beyond that, when you're working with an alternative, when Ivanti has a number of connectors that they've already prepared out of the box as well, it's pretty quick. We had...everything that we've got up and going, I would say up and going in less than 20 minutes, really, and then minor tweaking here and there based on the data elements.
Moderator: Wow, that's great, and hopefully it's giving you that time for your day. Either set the team off completely mad because I think you'd get up at 5:30 every morning and are always working, but hopefully that's great for you. Okay, we have another question coming in. So someone who's actually just started with us, a new Ivanti customer who's just learning the ins and outs of Xtraction, just starting to understand it and wants to know...wants a bit of better...what's meant by the different parts. Okay. Sorry, I'm reading as we go. That may be one, Jessica, that we need to take offline because that's a less...that was a specific thing that we can answer. If you want to use the chat, we will try and answer that one for you. In the meantime, the next question. Have you looked at using time lock and ticket to generate employee utilization metrics? Is that a road you've gone down, Christy or Nick or Lee?
Nick: I'll go ahead and take this one. Yes, we're currently using it today to track agent utilization. So we are tracking time and ticket, understanding to build a trend line based around a specific CPI so we can understand how long this particular type of incident, once its been classified, takes to execute. So we kind of have a baseline to model against.
Moderator: Great. Okay, hopefully, that answers your question, David. I've got another one coming up here. Hold on a second [inaudible 00:27:23]. Okay, so if you are to compare it against... I don't know if you have any experience of Power BI tools, but if you did, what would you say the main advantages are? Or would you have them working side by side? That...
Nick: I apologize, but I've never used that tool.
Moderator: Okay. All right. So we can probably answer that one offline. Okay, more coming in. What type of skill sets...just wondering... Sorry. Let me... Oh, did you do training to understand the usage of the product, DBI programming, etc.?
Nick: Hey, Lee, I'll let you run with this one. How much training have you had? How much formalized training have you had on Xtraction?
Lee: I didn't. At first, I didn't have any formalized training. I just picked it up and ran with it and learned from Christy, who was using it at that time. So there was no formalized training. It was just that easy to pick up and learn.
Moderator: So Christy was either a really good trainer and Xtraction is a really good product. So you got two [inaudible 00:28:58].
Christy: Yeah. [inaudible 00:29:00] was interchanged, and after that, we got the product a couple of months later, and I was like, "I got to figure out how to use this again." And that was it.
Moderator: Good job. Okay. Great. Okay, question here that I can probably answer. Does the product, is it interactive, and can you drill down? Yes, you absolutely can drill down, and you can filter so that you can see certain areas. That's not something we could show here. Guys, I don't know if you're using much of the drilling into your dashboards or looking at the underlying data or looking at the underlying applications at all.
Okay. Okay. So what sort of background would a person need in order to... Oh, I'm missing part of the question here. Sorry. I think we might have cover this one. What sort of background would a person need to be [inaudible 00:30:06] the product? Would they need DBA or programming skill? So, Nick, Christy, Lee, what kind of programming skills do you three have?
Nick: I've done a little bit of PowerShell in my past, but that's about it. Christy, how long have you been a DBA, or a Oracle, or a SQL analyst?
Christy: Negative zero minutes. I am literally just with operations and I work with sales mainly, but that's about it.
Moderator: Great. Okay. And I don't know whether you guys were involved in the installation of Xtraction, but someone is asking about whether...how straightforward it is. I know from other customers' experience, it can be ran up pretty quickly. What was the experience like for you guys?
Nick: It was not bad at all. I think it took longer to get the system requirements from the various teams that we needed the resources from, as opposed to actually getting the installation completed.
Moderator: Okay. And that's a good point. And that's not a question that's come up here, so I'm throwing this one at you. What sort of,...you know, there's a lot of people on here, who either starting with Xtraction or thinking about looking at it. What sort of advice would you give them, not necessarily about the product, if they're about to start a project like this? We just talked about requirements. What gadgets or things would these guys need to think about?
Nick: Think about what you wanna look at first. Understand the data elements and where they're coming from, and if you can formalize logic to reason, like, "This plus this equals blah. This divided against this equals X." Understand how you might get to that and where those data elements are coming from before you go into it. Otherwise, you're gonna kind of...you're gonna have so much data thrown at you at once. Now you're gonna try to figure out how to parse it. If you're already doing it today in a spreadsheet, odds are, you got those data elements and you're pulling it from somewhere, but go into it understanding what you wanna get out of it. Otherwise, the sky's gonna be your limit, and that's gonna become overwhelming very quickly.
Moderator: Okay. Great stuff. Question here, does it only extract data from approved sources and add ons? So we have a whole bunch of connectors that you can see on our website. It's on ivanti.xtract.com/xtraction. There's a list of those there, but it's not limited to those at all. They're just the ones that get you up and started quickly. If you have other applications, in-house data, etc, etc, then all things are possible. Nick, you mentioned the Ivanti Connect because I don't know if you're looking at anything beyond what we're showing there, but it certainly is possibility.
Nick: I've been exploring, interfacing it with our telephoning system as well. There's some good data elements in there that would be nice to see it parsed against. That's another one that's on my roadmap.
Moderator: Okay. Sounds good, and certainly we got a whole team Xtraction specialists. Some of them are on the call, who can also help. So if there are other data sources out there that we are...you think we're missing or that are local to you that you'd like to connect to, then certainly have a conversation with us because it's certainly not limited by what we are showing at the moment. And the other thing to note is in some cases or many cases from what I've seen so far, we pull the data that's required for the dashboards out, but we are not, you know...so security-wise, you're not opening up the application unless you need to. But you can click through to the underlying application if you need to.
Okay. I've got another question here. [inaudible 00:34:26] what systems can you extract from? So, Rob and everyone else, just, again, just to let you know, there's a whole bunch of the Ivanti solution. So from the service management side, the asset management side to our endpoint manager, to even our supply chain avalanche, all have connectors. If you go to ivanti.com/xtraction, there is a link to the list of current connectors that are there. And, as I said, if you're not [inaudible 00:35:00] please don't think that we cannot connect to that. We certainly can. It's not limited to Ivanti products by any means. Okay. We have another customer who's saying we recently built a display for us... Oh, gosh. I'm not seeing the full question again. Erica, I don't know if you can.
Erica: Yes. Which question did you need?
Moderator: Jay. We recently built a display for our call...and then I'm getting a cut out, unfortunately.
Erica: Hmm. I'm not seeing it on my end. Let me...
Moderator: Sorry about this, guys. I'm certainly experiencing a little bit of the normal WebEx chat issue.
Erica: Yes. I'm sorry, I'm not seeing that question either on my end.
Moderator: No. Okay. Let me...I'm having a bit of issue with the chat now, unfortunately. Other times integrate... No. Misbehaving. Okay, here's one I can see. Sorry about that. What's the time from implementation to getting real data that can be presented to leadership? Again, Nick, Christy, what was your timeline?
Nick: I know when I initially [inaudible 00:37:11], Lee with creating dashboards. He had them up and going for me in less than 30 minutes. I know he sat with Christy for about half an hour, and he was able to start cranking them out for me. Guys, what's the longest you've ever spent on a dashboard?
Lee: The longest I spent building out a dashboard, 20 to 30 minutes. But now I can build within 5 to 10.
Moderator: Wow. Good guy. Okay. All right, someone is asking about integration of Ivanti [inaudible 00:37:52]. Yes, we can do that. Please, if you would like to come chat us about this, we can talk to you more about that one. Can you connect us? So we don't currently have a connector [inaudible 00:38:10], but certainly, we'll [inaudible 00:38:12] possible. So, again, please contact us and let's talk more about that one. And, sorry, Jay, I'm still only seeing half the message. We recently built a call something, unfortunately.
Nick: I think I can see it. We recently built a display for our call center display. Because IPCM reports to SQL every 15 minutes. Is it possible to see IPCM real time in Xtraction?
Moderator: So, in real time, it isn't a problem, Jay. Yes, absolutely. The data is...you can put it on a refresh thing. So I guess you guys use [inaudible 00:39:03] real time displays, or Lee, too.
Nick: We have display here that rotate between different data sources. They're set up with countdown timers on them, and that's highly configurable down to the seconds, and they'll refresh and rotate.
Moderator: Great. Okay, someone's asking for some more information on Xtraction. Absolutely, Steven, we can get that to you for sure. Okay. All right, I'm not seeing any more questions coming through. So what I would say, because certainly some of you guys have been asking about the connectors and about Xtraction, there's actually a free trial that you can avail yourselves off if you go to ivanti.com/xtraction. You just need to register. We do need to know the server that you need to put it on. And also on that page, you will see the list of connectors as we mentioned before. And anyone who wants more information about the features, there is also a data sheet on there that we will absolutely send out, any information that anyone requires.
So we are in the last few...well, 15 minutes. So if we don't have any more calls at the moment, what I would definitely like to do is say thank you so much to the team of Aviall. So to Nick, to Christy, and Lee, it was fantastic having you on. I hope you enjoyed the experience. Hopefully, we'll get some more questions in, and when I come back to you in the future and ask you to pop on again if that's okay. But otherwise, we will say thank you to everyone who participated. If you are interested, please do contact us, and we'll see you in the next webinar. Thanks a lot, guys. Bye.