Welcome to today's webinar on IT as a value driver: how to communicate the value of tech initiatives to executive leaders. So, good morning/good afternoon, everyone. I certainly hope the next 30 to 40 minutes helps provide some valuable insight into this topic. I think as we are all IT leaders one of the things that we are continually trying to do is not only demonstrate the value of it and our investments in those resources, not only to the leaders within our department, but to leaders outside of our department from a cross-functional standards.
And so, it's one of the key areas that we're going to talk about today. We're going to talk about some challenges along those lines, as well as some potential solutions. And with me today. And just to introduce myself, first of all so on Jason Coari, VP of Product Marketing and Strategy at Lakeside Software. I've been with the company for about a year and a half. I've got several experience years’ experience in the EUC space, and an entire career within both software and hardware and the technology. Accompanying me on the Lakeside team is John Oglesby. John Oglesby is a Product Marketing Manager, and he's been at Lakeside for over five years. And he actually came to us within a solutions engineering team. So, John has a great understanding of what our product does, especially in the application of that product to a wide variety of customers across Europe. And then finally we have one of our most mature and top customers in the space, William Smierciak. He's IT manager at Florida Blue. William has been at Florida blue for quite some time. I think it's over 10 years and William has really done some tremendous things in, not just helping Florida Blue maintain business continuity with the new way of working of employees going above and beyond that and ensuring that it is positioned not just to ensure that business is continuing, but it's actually maximizing the employee workforce from a remote setting.
And I think he's going to give some great observations and reactions to the various things that we're going to share in this presentation. So, here's our agenda today. We're going to talk and start off the presentation a little bit around digital employee experience itself. Why does it matter so much?
Why does it matter in today's modern working environment? And then we're going to go into the next section and talk a little bit about. Common challenges that IT leaders are facing in today. When we think about how do you take some of the sub optimal ways of working? Some of that is actually reflected on the, it that's provisioned to those employees, you know, what are the challenges and just, you know, very easily making that better and shining a light on those because once we shine a light on those challenges, obviously we can talk a little bit more about the solution.
We're going to share a little bit of where we next taking the evolution of our digital experience cloud to particularly solve some of the challenges that we're speaking about today. And we're going to get William's reaction to some of those, those introductions, those new features, those unique capabilities how he sees, they may be able to benefit him in a, in a, when you're one of our more mature customers, when it comes to digital employee experience.
Why does digital employee experience matter? So, the first thing that we're definitely recognizing out there is hybrid work is here to stay, you know, 50% of all knowledge workers across the US and the UK globally will be remote workers by the end of 2022.
A basic foundational point that we need to make an assumption that whatever we're doing from IT, it needs to work, and it needs to be relevant to this new way of working, because it's not just going to be employees coming back into the office and as the employees are working remotely, then the thing that we're finding is that they're more reliant on technology more than ever before.
You know, if you think about it from a standpoint of collaboration, if you're not able to walk down the hall, you have to use your devices, you have to use your applications, your collaboration applications, if that's not running correctly it's, it's difficult to maintain the same levels of productivity.
So overall technology is becoming an increasingly important role. I also might as well share. And when it comes to understanding what digital employee experience is, it's pretty simple. It, when you think about employee experience of which, you know, the constituent parts are what is the work-life balance, right?
What is their compensation? What is their workload management structure technology and the techno the role technology plays to influence that employees experience? That is what we talk about when digital, what is digital employee experience. And we estimate that to be at about 30% of overall employee experience, but, you know, most employees do agree that it just plays this, you know, outsize role.
So, the issue is though, is that when we've asked employees based on the current digital employee experience that they were having, how productive were they? And they said they were only working really at 60% of their productivity. What this tells me is that there's a lot of opportunity for improvement.
I think there's a lot of reasons why this is happening. Some of which I think are in our control, some are not in our control, but you know, if we think about, you know, the, the adoption of technology, when we think about digital friction as a concept, you know, as we provision technology to those employees are redoing it in a way that is as seamless as possible for those employees to make the most of that technology.
Just thinking about how we structure our service desk how we roll out deployments, how we think about digital transformation initiatives. These are all various areas that I think it touches that can over time, you know, basically improve this. Now this translates into are a few important things.
So, one of the things that is directly responsible for it and actually responsible to the extent that it's, you know, simply an indicator, something that we could be doing better. So, on average when we conducted some market research with 600 employees and IT leaders around the globe, they send their, are losing about an hour a week and productivity to the technology issues.
If you're a part of an organization, that's 5,000 employees or 10,000 employees, and you multiply this out by, you know, 48, you know, working weeks per year or so, you know, those numbers start to become really large. And it's something that, you know, I think will never go away completely, but it's something that, you know, certainly could be optimized over.
The other thing that I wanted to share, and this also came from some new market research that we commissioned is that there's a correlation between. Having higher levels of digital employee experience maturity, you know, when you think about what you've done in the organization to turn reactive operations into more proactive or preventative operations, or more siloed workflows into more integrated workflows or having really better visibility, we think of those organizations of which, you know, we tend to think Florida Blue is one as more of our DEX leaders, but of course, on the flip side you have DEX laggards and you know, those laggards with lower levels of digital employee experience maturity.
Well, they have four times as much productivity. As our leaders do. So, there's a direct correlation there, and you can see what this actually translates into, you know, 266,000 hours of lost productivity for an organization of 10,000 employees. And, you know, for an average employee, it's going to be a four times greater impact to their personal productivity and overall level of work frustration if they are able to optimize digital employee experience.
So, I think this is a great time to pause. And I think this sets the tone of the overall importance. But what we also have seen in this category is that there's a long way for full adoption of, you know, solutions that really do optimize this current challenge. So, you know, I think William, maybe you want to comment on your journey as a customer and how you were able to maybe overcome that initial challenge of, how do you make this a priority within the organization?
So, one of the key pieces that I find really interesting are the stats that you've got here based on the technical loss or the loss of time due to technology and the impact that it has on the individuals and the organization as a whole. And one of the key components that we are looking at on a regular basis is how much time is lost due to our technology.
That goes from everything as basic as the simple boot up process, all the way through to application. Latency network latency local device systemic problems or individualized problems. And it's been impressive from the utilization of subtract from what we've grown it to today, within our environment, that we've been able to pinpoint a lot of the, not necessarily the low-hanging fruit, but some of the easier gets to have the smaller wins to build up to the much larger, more organizational wide or systemic solutions.
So Our looking into the data loss or the time lost at the date of loss, are looking into the, the technical time lost that some of these individuals, whether they're technical people or they're non-technical end users, administrators, and other leaders in the organization we can easily identify a lot of those opportunities and have slowly started in our best efforts to improve those instances where it may gain a minute in a day, but across the multitude of opportunities to make that when we're working really, really hard to get our way back to that 54 minutes of lost to bring that down to a much more manageable and acceptable number.
That's right. Yes, it is. It's a challenge that needs to be solved and it's not just one thing that can be done it's it needs to be. As you articulated William a holistic approach to solving these kinds of challenges.
If I was to ask a follow-up question, you know, was there something that tipped the scales so to speak when it, you know, led you to start really thinking about, you know, this challenge needs to be solved? Was it, you know, was it around the pandemic time? Was it that switch to remote working? Any, any thoughts there?
Sure. Actually, the scale tipped of almost immediately after we had SysTrack installed in the environment across the entire enterprise and was pulling in that data, we knew the user experience was suffering, but everything was almost pure speculation. There there's some windows things that you can pull to pull some basic data without a whole lot of in-depth or at least most of the time, not without a lot of Microsoft support and pulling in logs and reading those logs and regurgitating back to you, you know, the information that apparently, sometimes they can only see here that they have the much better skillset to, to identify. When we started looking at all of the systemic problems within this, this track agent, and it was probably a year, year, and a half before everybody went home full time, roughly.
That's when we were really seeing a lot of like I said, some of the little, a little bit more of a lower hanging fruit that we can take advantage of to try to identify why is this happening the way that it is.
So, a perfect example: our average boot time on a workstation was run around six minutes. That’s a long time. We couldn't figure out why, before the user gets a usable screen, the average was six minutes. There were people waiting up to 20 minutes. What we ended up finding out through triage and a lot of effort with multiple teams being involved was there was a domain controller that had legitimate problem when they shut that domain controller off and took it out of the network login times dropped to right around three, or I'm to boot up times for usable control of delete, ran to about three minutes or less.
So again, sometimes it's an easy win relatively. There are things that we look at specifically with applications that is a little bit more convoluted, takes a little bit more time and digging, but you know, a mix of the SysTrack agent across all the devices, all the reports and data that we get and the technical teams that have the ability to stop.
They're not dealing with production issues every day. They're not dealing with user issues every day. Their focus is to remediate or at least identify and plan and work with teams to remediate these opportunities for improvement. That's where the real success for us is started to really show its value.
One of the things that we've noticed specifically with this product is if you put it in and you have your technical people who are chasing tickets all day long, and they're trying to shoehorn time in with the SIS track agent and the management of the environment and the proactiveness it becomes a little more complex.
So, I was fortunate enough to take one individual out and place them in that spot. And now their job is just to proactively go and do this work. And that has been where we've really seen a lot more growth in ours. Very interesting. You, you highlighted a couple areas that I was going to bring up right here in some of the unique challenges of it leaders and you know, in some ways it's, it's good to know that we are, you know, seeing the challenges you know, as peers and aligning in that instance you know, Brie, you brought up just this, this lack of visibility, right?
Thinking about observability, having, you know a single source of truth, right. Versus just guessing what's going on. There, there definitely seems to be a huge array of consistency between the remarks you shared William. And now what we're seeing and the other area that you saw with users and their willingness to just deal with these issues without reporting them to it.
It's. You know, I don't want to overuse the word, but it's, it's frightening in a way, you know, six minutes, 20 minutes you know, I think various employees have different levels of confidence within it. I thought, I think also certain employees just want to work more autonomously. And I think, you know, we must have mechanisms to support both, you know, situations because every, every employee is an individual, right.
And they're going to have been on a different spectrum of their willingness to engage with technology or engage with the organization. If something doesn't go. . Yeah. So yeah, so just this, you know, this idea, this, this concept of what is the health of my environment what is the influence of the resources that I'm allocating or the technology that I'm provisioning on my users from not really like an inside out perspective, but really an outside in perspective, the user centric perspective.
So that really understands better. If you have that user centric better, you can start turning it back to productivity and that's, that's what it's all about, right? I mean, at the end of the day we are a support function for overall employee productivity and therefore having that metric to. You know, characterize what that is in a quantifiable sense is critical.
So that's, that's definitely a challenging one. I think challenge two, it speaks a little bit to, to this call and I think it's one of the reasons why we've evolved our solution to this next level, which is how do we measure our own impact as an IT organization all the time, all the resources, all the budget that we're spending to support, what really is becoming a much more comprehensive estate of services and devices and applications.
Trying to understand that as one thing but trying to optimize it and manage it is another. And you know, you need better benchmarking, right? You need to understand more about what's happening today and then tomorrow and trying to track progress. You perhaps even need a way to start. Grouping employees or environments in certain ways that helped you either better pre prescriptively deliver services or a better track, you know, what's going on in different environments, perhaps you want to do AB and testing.
You know, most of the, our organizations that we serve have offices all around the globe. And so, it sets up a situation where, you know, it's easier to track what's happening and compare one set its delivery services and maybe SLS versus others. So that's happening. You know, and then, you know, something I know that you can comment as well about William is just this work from anywhere devices online and offline, the particular challenges of just this hybrid working world you know, there's new challenges, there's some unique challenges. So, anything that you'd like to say willing to react to this, or you know, anything that you'd like to.
Just short little quips here and there. From the end user productivity downtime and the outside, looking in one of the key pieces that I'll say it wasn't the top, but it was definitely one of the key pieces that subtract really we were hoping was really going to bring home for us.
Was the user experience grading. We don't know specifically what the user's experience is on their particular asset. You have a multitude of models and variations of hardware across the entire enterprise of 13,000 or so devices. So. Two people in the same teammate experience based on two different assets for two different device types, with different hardware, for whatever particular reason could be very well drastically different just between the two people within the same department, just using two separate devices.
And so, one of the key components that we've been touching on has been trying to start the method of determining as part of what we talked about a moment ago, what the user experiences and basing that grade, or that value against some of the lower hanging fruit or the easier wins that will help increase some of those experiences for everybody across the board.
While when people are green, right? Are there, they have a great experience from the workstation perspective making some of those easy wins just adds to it, but for some of those that are in yellow or red, pumping them up a level as minimal as it is from us looking at, you know, At the insight and at the details of all of the problems, those little wins sometimes while they're not recognized, they are noticed.
So, and in random hallway conversations or, or side conversations, I'll be told by individuals like, hey, I noticed this is working better. Did you guys make a change? Like, yeah, we're, we're trying to improve it the best we can. Which is nice to hear. Right. And we, we usually in it, we get all the bad stuff when we get the good stuff and we get the, you know, nice job or I've recognized this and the effort behind it.
It's, it's definitely appreciated. So, the second piece specifically about what we're doing to our own devices. We are a lot of times our own worst enemies to our machines, as well as others. Think of all the components and security products that we run in, in large organizations and, and any organization, really.
But typically, you'll find a multitude. You can have the caffeine CEP and carbon black, possibly other applications as well, doing other data loss prevention or other security components. And then as you add on more agents for other things, any scanning agents, any compliance agents, government agents that come in and have their scans and the things they do as an individual, it's a death by a thousand cuts situation, because what ends up happening is, is everyone says, well, it's just a small agent.
It just runs 150 megs of data. And it only scans every 30 minutes or every two days or, or whatever. But when you mix that across 15,000 end points, and you've got an acre sitting on 11 agents today on our devices Realistically to the point of on usability and some systems. And so, we've been fortunate enough to identify some of those agents and what they're doing and reporting and pulling it out of SIS track and reporting back to all of the individuals, stakeholders, as well as other teams who are asking for root cause and providing this agent ran for 12 minutes, it's consuming 100% of CPU for that solid 12 minutes.
It's consuming 800 megs of Ram and it's utilizing 10% of their network bandwidth. So, here's the data. We need you to figure out how to not do this or not do this during production hours. So, in those situations we have a need, or we have a desire as it to make sure you know, all the system checks it's, it's all the dash light at the dashboard lights that we want to see, come on.
If something goes bad, but what we don't realize is it's. It's all linked to one device. And so that device really takes a beating, and we are able to prove that, and at least have those talks with those engineers or those teams that own those agents and say, can we please not do this? The last fees, the inability to monitor work from anywhere devices.
We don't, while we do monitor things in a particular way, we don't monitor them really to an extremist amount. We do get the, the, the details. So, if they're offline, they're doing something, they have a problem. We've loved SysTrack can provide us a lot of that detail at that time, even though they're not online.
So, when they check in, we get all the updates and we see all the information it's beautiful because I can see the error and the user can just say, well, it was sometime between 10 30 and 10 45, and this is what. You don't have to be online at that exact moment, watching that user's machine, I can see whatever was going on with that system at that moment, and then provide feedback, whatever the solution is.
The, the ability to monitor them from our perspective, there are only VPN connected devices. So, if they're not on net on the VPN, they're not going anywhere. So, we still track the data through SysTrack and a number of other agents, as I mentioned earlier. So, we see everything that they're doing and then once they connect their online.
So, the monitoring has been nice from our troubleshooting and support perspective. And it's been really, really helpful for offline situations where, as I mentioned earlier, before we got sidetracked, we had no idea. We relied on the user detail as basic as it was, because a lot of times they don't break the air down or to print screens. So, this has proven to be incredibly.
That's really interesting, William, I think thank you for sharing that, that use case it's, it's a good example of, you know, I think taking this data collection ability, you know, and the, the depth and the breadth of, of all of this data and really maximizing the utility and the value of it through, you know, ways of prioritization because you have, we do have finite resources at our disposal. So, we do want to really see even almost down to the user level, you know, which of my decisions will make the greatest impact. And in even thinking about. Enhancing the value in making sure that even the other technology that you're deploying is working together with one another. You know, I almost think of what you share around agents as you know, SysTrack being able to watch the watchers, right.
And so, you know, understand, and optimize, you know, those other agents that are on those devices. And I'm sure many enterprise leaders like yourself. It is always something that you're trying to balance completeness and what you're trying to do to that end point with limitations of not actually getting in the way of the overall productivity of that end point.
So that's great. The other thing that I just want to share from a challenges standpoint is, and it's something that. I think in today's working world, we need to be very cognizant of is that there is still this war for talent out there. And you know, this can be our own teams, you know, as IT leaders on this call, I'm sure we have teams ourselves, but it's also when we really think about our organizations and competitive advantage of our organizations, you know, we need to do everything that we can to ensure that our organizations are as competitive and productive as possible.
And that's driven by people. Our research has indicated that a number of employees have considered leaving their employer because of poor digital experience. 36% in fact have, and 14% did leave because they didn't have, you know, the proper digital employee experience. So, you know, this is whether you want to think about this some more, you know, personal terms in your own team, you know, or more organization wide terms.
It doesn't matter. It's still, you know, a really critical aspect to ensuring we, we start tackling this challenge. So, let me let me pivot into what do we do all about this? And I wanted to share just a quick look at our digital employee experience cloud. Before I turn this over to John, John's actually going to walk us through three different areas of the tool, but just, just to level set everyone for those of you that might not be familiar with our digital experience cloud.
So, you know, what we do is we collect data from a variety of, of it instances and endpoints across applications and devices and networks. We do that, whether it's a physical device or a virtual device, whether it's a mobile device, even IOT, we collect this quantify data and we can also super impose that through engagements and collect sentiment data.
So, you have really both a quantitative and qualitative view of what's going on with that, in particular. We do this through what we call our intelligent edge. This is the, basically the entity of our platform that reaches out to your, you know, probably very highly distributed workforce gives you the ability to look at both real-time data.
We're collecting 10,000 data points, every 15 seconds, but also looking at historical data, you know, over the previous three years. So, you can really get a really good contextual understanding of what's going on at the time. But with that end point, at the time of a particular incident, we are GDPR compliant.
You know, we certainly take privacy and anonymous, you know, aspects of, you know, your employees or your users are of great concern. We have a lot of intelligent analytics that are part of our platform features, you know, with sensors and our embedded expert logic. You know, we take this large array of data.
But we help make sense of it automatically. Right? We do that within the tool. You know, we do those insights. Those are manifest out through a variety of dashboards. We allow you to we, it automatically provides health scores as well. And we do that across a variety of use cases. So, we're going to share a little bit on this call around executive insights that overarching visibility, you know, this really unique single pane of glass that gives you a really good understanding of your entire estate, but we also do a variety of things on it.
Service delivery, whether it's L1, L2 and an all one workspace with automatic diagnosis and fixes, or more complicated root cause analysis, or even looking proactively around what can I do. To optimize in my environment. When my users aren't actually telling me what's going wrong.
And then on the other side, digital workplace optimization, if you're doing digital transformation, endpoint migration, maybe some of you on the call are starting to get more serious about windows 11. Or you want to do some element of right-sizing, whether it's focused more on devices or on applications and ensuring your devices are actually supporting your applications.
You know, these are various areas that we can help you manage and optimize. So, with that, let's switch gears a little bit. And Jon, you want to take everyone through a few areas newer areas of our solution.
Absolutely. Thank you, Jason.
So, the first area I'd like to share with you today is the executive insight. So, what this does is it uses the information that we've collected in our intelligent edge. We've processed it. And we brought it through, into a screen that allows us to see at a high level KPI and assigning to that KPI.
Excellent, good, fair, or poor to interpret it for you. And it's tracking that on a day-to-day basis. So, we can see here a recent history showcasing that KPI. We have the headline figure of 68%, but we can also see the distribution here so we can see the potential systems which are in those excellent, good, fair, poor categories.
So, we know our challenges that we have ahead. We can also see the impact that, that KPI effectively. As an average hours per week for the users and to gain, we can track that historically over time, as well as seeing a real time figure that what we can do as well is it's great to know this, but how does that compare to other companies in the same industry?
We can see that down the bottom right here, but we can also look at it on a regional basis and we can also compare it to both companies. So, you have a right at the get-go, you have an easy comparison to know where you are, what you ratcheting to focus on at a high level and the impact it's having for your, for your users.
Additionally, we can look at subsets of the data so we can, for example, look at the technologies. Maybe look at the desktops, for example, or laptops, we could look at a department lead. So, for, in this case, we're looking at finance or we can look at a geographical, but for this case, we're looking at maybe the U S devices versus at other areas, you can in fact set up any of these groups that you'd like with a tool.
And when we do that, we're able to look at those again time as well. So, if we go for the finance, for example, we're able to track over time that that KPI, if we want to look at the desktop, we can see, we have a lot of volatility here, but on average, we actually have a higher level of KPI.
So, with that what's your thoughts on this screen?
So, this is incredibly impressive. Seeing all of this and a single pane of glass. It really does provide the first holistic view which SysTrack has some other capabilities like this, but seeing the overall health, especially from an executive dashboard really does provide a nice and clear understanding of where we are, especially with comparing to all the other companies based on industry region, et cetera. So that's, that's impressive to see.
That's great, great, William, and we know in the tool, we're able to action on these. We have other areas within the tool, which will well not covering as much detail today where you'll be able to take this information, drill down and get to the root causes, which are impacting these KPIs. We can actually do something about it. So, there's one thing measured. But then there's another is having the data to be able to affect that, that measurement. And that's something we can, we can certainly do with the tool. And Jason, thanks, Jason.
I appreciate your comment, William. I think, in so many ways we want to help the users and the people who are leveraging the value of our solution.
We all want to be a hero in our, on our job. And so, to track that progress and have an in-product representation of that progress, that's easily exportable into a report and allows you to customize the report to grouping that can help you better refine whatever future state you want to get to.
And the mechanisms that you're leveraging in different areas. We certainly do hope that that that would be valuable.
So, thank you, Jason. So a native feature for our software is the ability to deep dive on a web application.
Not only the usage, but the statistics about those web applications. So, one of the key things that we do here is rather than just look at a technical URL of a web application, we have a screen to map those through, to the business name of the application. And in some cases that that may be a whole server for one business application.
In some cases, it may be sub folder within that that website. And we're able to then look at a few key metrics. So, I'm showing you this here by looking through for a specific user are looking at their device. They're looking at the web app. And from there, I'm able to pull up both cards as well details, which shows per web application.
the average click to render in seconds. So, what does click to render mean? It's the time between the request from the user. And through the device, it's going to the server it's time for the server to process the response and the time it takes for the client to process the return data and show it to the screen.
So, in fact, it's an end-to-end timing of that web application, but what you can also see from this is a breakdown of different aspects of that click to render time. So, we're able to see an average of the network latency. So that's the time it takes for the request to be sent from the client and the time it takes for the server to respond and the average processing time as well for that response from the server.
So, you may have a very quick network and a very fast cloud service or whatever that's producing this, but it may be such a complex layout on the screen that it takes your web browser, an inordinate amount of time to convert that into something that can be shown on the screen. So, we were able to break these down on average per web application.
And then we can, we can see that. So, this user, for example, is using the web version of Microsoft Excel. And we can see they are having issues with the rendering, but we can see them straight away. That is due to the processing of the data. That's the office 365 sending and getting; it's the time it takes to get it onto the screen.
It's not a network issue- straight away, you can see that. And it's not an issue with the actual servers that are the cloud which is hosting the excel. Similarly for other applications as well. So, we have like Salesforce here seismic word SharePoint on here, Microsoft outlook or web based as well.
And then we have some of our internal site as well as our HR site as well. So, we're able to compare those on a per user per device, per web app basis. We also have other things as well. So, we're able to see the errors as well, if there are any, and we're able to see that usage statistics as well. So, we, for example, can feed the number of visits total time spent in minutes. And then the average time per visit, we get to understand the usage of these web applications, which is something again, if you've got a web application, which are a hundred percent cloud hosted, you now have metrics into the usage of those as well. So, William, I would be interested to know your reaction to the web apps, and how that would work within your organization.
So, unfortunately there's no heart monitor on here. The web application piece is going to be huge for us. We are a medical insurance company, a number of our applications specifically to service. All our members are web apps, and we are constantly barraged by what is perceived to be latency at the workstation level causing internet Explorer on edge and Google Chrome.
Being the excuse as to why some of these web applications act the way they do. And having this broken out detail is going to be massively appreciated, not only by the technical teams, but also by the teams who own these web applications.
Maybe it is the network latency in between, or maybe it is them and they need to identify or understand what their baseline is. Because everyone has an idea that it should just be immediate, like going to Google.com. And unfortunately, how the sausage is made behind the scenes, it becomes a very different understanding as to the technical requirements and the system utilization and all the components it's got to reach out and get, build, and provide back to the user.
So, while 17, in this example, on your Excel, while 17.3, three seconds might be a high number in our eyes, maybe that is the baseline for that application. And that just needs to be set and that's, that's fine. It doesn't have to be. The best answer, but as long as it is the definitive answer, we can start there.
And then when we see it climb to 20, 25, 30, 35 seconds, that's where we can say, all right, this is an actual problem. We know the baseline 17 but splitting this out in this way for any of our internal web applications where we get calls on latency problems or the systems acting slow, this is, this is going to be huge for my team. This is absolutely going to be a game changer for them.
That's fantastic. And I, at least from my, from my own interactions with customers as well the baseline that you mentioned is a really, really useful points because you, you often see with these, that there's two types of challenges you can have, like, it can suddenly go wrong and then that's one type of issue, but you can have the other one where it's starts to get slower and slower and slower, especially if it's a cloud service where it gets updated.
So, you can then start to manage the vendor, the site. Now you've gone beyond what we're happy with. You need to address this in the next release. Then you can track whether they've done what you wanted based on actual data. And that prevents you getting to that. So, is it preventative maintenance or a way of stopping those issues happening in the first place? So, no.
Oh, you're welcome. And thank you. This is, this is absolutely awesome. I'm excited to see this.
Great that Jason, anything to add on?
No, I it's great. I mean, this was really in response to customer's requests and the extending, the capability that we had around root cause analysis and applying that sophistication to more web apps and the tools that employees were just using more these days.
As we all know, time is money. And so, if we can more quickly understand what's happening, what the issue is, and we can more quickly find that resolution. So yeah, so that's great, John, please go ahead and share the last insights around green IT.
So, our green IT DEX Pack allows us to load in screens that enable us to see data relating to monitoring things like energy consumption.
How consumption by model and things like printing and the impact of that. And it also covers virtual machine energy consumption as well. So, the way this works is we have a nice overview screen and it's fully interactive. And as we mentioned before, we, we can actually do things like exporting these high-level objects. If we wanted to put them in our own reports and things on that, what we can also do is drill down here. So, we can either double down or click the button here and we can go there. And so, if I go into the first one, which is the energy consumption, it allows us to pick a country so we can benchmark against different geos, we can decide whether we want to include that in physical servers or not.
And we've got a nice explanation here as to what this is doing, but we can see several types of data on here. We can see the electricity that's used in kilowatts. So, you'll be able to multiply that by the actual charge that you're getting charged from your electricity company. We'll be able to see the CO2 produced as well in kilograms.
And then we can see also wasted electricity as well. So, an example of wasted electricity is someone's rushed with desktop device on design, actually doing stuff, but it's just switched on and it's, its consuming electricity, as an example. And again, the CO2 as well, the way we do this is actually quite an interesting way, so where we're actually breaking it down and I'll cover that in a moment when we cover it by model -- and the mechanisms we use to get these overall results.
But one of the cool things we can do here, and we touched on it earlier in the demo is we have different types of groups that we can set up. So, I think we covered the physical systems. We had an early one on desktop as well and finance, but we can just pick these from the list here. So we can go ahead and say, I want for example, to see all US devices, I'll be able to chart that one out here with the same data points, but specific for the three.
So, we allow you to see here four groups at the same time to do a comparative biomimetics. So that's that one. And then I just wanted to show you how by delving into a little bit more detail when we look at the power by model, what we are able to do here is for example, we take a desktop or a laptop. We can actually go down, we can actually see here, the individual devices, and we actually are looking up from those devices based on their usage and based on their resource consumption, or actually calculating the energy usage for those individual devices. And then we're actually adding that up. And that's how we get the energy consumption figures for this and similar for printing as well: we're actually tracking the number of patients. And we can look at that data in several ways. We can look at it and ways of, for example, number of prints per user, but also per region. Or we can also know the application that causes prints as well. So, there's multiple ways you can start to address that.
And that goes way beyond the old batch print solutions. They have two flaws: they only work in offices and we're in hybrid working now. And they don't really address the root cause, which is it’s the application that makes the use of print. It's not necessarily the app, the user that decides to print something all the time. So, we can look at this in a different way as well.
So, William I know this, this will be something that within the organization, someone will be having to pay that electricity bill. Is this, is this something that would help your organization?
It would because we're constantly being asked to provide any input, just recently, on what the manufacturer's consumption of electricity is.
I'll be honest. I don't recall being asked about the CO2 produced on that. It doesn't mean they didn't ask and I'm just unaware, but we are regularly, probably yearly asked what the electricity consumption of each of the models of, of workstations we have, but more interestingly and I, I find it funny, we've run into a few people who tell us at night, they turn off their windows devices because they don't want to waste electricity at home and raise their electrical bill. And it's hard to argue that with individuals, especially because at night is when we have our maintenance windows to do our patch deployments and other updates as such.
And something like this would be incredibly helpful just to maybe ease a little bit of minds to say, if you leave it on once a week, just one night a week, this is the impact of, you know, if you leave it on, as it is your electrical bill, shouldn't be at all noticeably different or a laptop or a workstation being left on once. But from the electrical standpoint, absolutely. In the office they're always looking for ways to determine how we can save obviously, utility, electrical water, everything else. So, this definitely be helpful for someone to leverage on a, on a dashboard.
That's fantastic. And my work in some of the finance sector as well, and this was definitely more back in the more office centric days, but if you have a floor full of desktops, there's heat produced by those and dependent on the layout of the building and sunshine and so on. Yeah. That has an impact on the AC. And then that's a whole, whole extra layer of savings that can be had.
Now that you've mentioned the heat aspect of it, it did ask us one of the questions they did ask for us to provide, we had to go to the vendors was the rough output of, of the temperature, but not, I don't remember the exact detail of it. I'd never heard of that before. It never put the correlation together until they explained to me why. So definitely a lot of pieces go together.
I don't think we can see the usage of the device. So, we know the loading and we know the fans and the heat gets, it gets more when the loadings height, so we can correlate all of that together.
Very impressive. Thank you.
Thank you very much, William and Jon. I think with, with green IT in many ways, Lakeside is working to get in front of an emerging trend. We know as more of the enterprise is in the success that an enterprise is based on digitization and technology, the energy footprint of technology becomes a greater part of the whole, but at the same time, the trend is we all know energy prices are rising. We know that more enterprises and public firms out there have environmental sustainability and governance officers and accountability. And this is again, just another way where there's a mechanism of which we can take IT from backstage and put us right in center stage, right in the front office of the organization, which is, I think where we're all headed.
So let me wrap up. I want to thank William, for all your participation and your really valuable comments around, contextually, how the solution would work and sharing what's happening in your environment. And John, thank you very much for a great explanation of our new features. So, and of course, thank you to the audience for participating and listening. I certainly hope that what you heard today, you can take away a few valuable insights, and if you have any further questions please do let us know, reach out.
We'd love to help you understand how Lakeside can add value to your business. Thank you everyone and have a great rest of your day.