Video: Community Call: Meet Lenovo STEP - Specialist Presales Support for Partners | Duration: 2812s | Summary: Community Call: Meet Lenovo STEP - Specialist Presales Support for Partners | Chapters: Welcome and Introduction (2.63s), Platform Housekeeping (28.415s), AI Express Program (163.175s), Florin Introduction (303.265s), Mission and Scope (383.725s), Partnership Scope Boundaries (500.725s), Engagement Scope (648.8s), Support Request Workflow (827.46s), Effective Request Guidelines (981.565s), Common Request Issues (1219.62s), Step Request Form (1435.475s), Submitting Step Request (1712.01s), Case Management Portal (1869.575s), STEP Team Support (1984.175s), Website and Support (2152.69s), Portal Support Process (2282.395s), Feature Request Process (2461.23s), Q&A and Wrap-Up (2506.975s), Closing & Next Steps (2598.27s), Closing Remarks (2720.6s)
Transcript for "Community Call: Meet Lenovo STEP - Specialist Presales Support for Partners": Actually, let me know if it's weird in terms of tattooing everything. Good afternoon, everyone, and thank you so much for joining us today for our community call. It's the first one for October. We've got quite a busy October. I'll give you a rundown of what's coming up in later sessions this month at the end of the presentation. Today, we're gonna hear about Lenovo Step, which is our new specialist presale support team for partners. And we look forward to learning more about that and how they can assist you in in closing business together. Right? Just the usual housekeeping slide. For those of you new to the platform, to the top right, there's a there's a little square dialogue box there. There's a chat option. You're welcome to to discuss things and have a chat in there. We kinda like to start this off by asking everyone from asking everyone what countries they're from. So drop your countries in. I see we're getting a nice mix of people, from one end of Africa all the way up through into Europe. So thanks for that. There's a document section. Here you can download files. So I put up a few things there. There's a copy of the presentation we're gonna give to you today. There's a link to an exciting announcement we made today. As always, please go click on the survey link and fill that out for you. And then there's a fourth document, which for the moment escapes me, but it's there for you ready for the download. Next little tab across the top there's for questions and answers. Any questions you have during the course of the presentation, please type them in there. And, I'll come back at the end of the presentation, and we'll discuss and talk through the options with the event for today. If English isn't your first language, you you can switch on closed captioning, and that will display what we're saying at the bottom of the screen. And then you've also got the option next to that to do translation. So you could change it to another language, if that's helpful to you. Or maybe you you... You're learning a new language on Duolingo and you want this as a a backup learning tool, so that's for you as well. And then the last button there is to make the screen... Is to make the presentation screen full size for you. So if you... If something's a bit small in the in the in the webinar deck, in the webinar's window, you can click that. It will make the presentation full screen. And then escape will bring you back to, escape will bring you back to the normal full window. The session is recorded. You can use the same link you used to join this session to get to the recording if you wanted to. You'll also get a link in an email to the recording. If you scan that QR code, you can jump to the survey and fill that out for us, please. That was the other thing in the link. Under docs is the link to the survey. So, yeah, please, if you could just take a few minutes and fill that survey out for us, it helps us it helps us understand what you're looking for, what you enjoy about these sessions, maybe what you don't enjoy about these sessions. We've added in some questions about the step team so we can get some feedback from you about what you'd like to see with them. So, yeah, please just grab a few seconds and do that. And then something slightly different this, this time around this week. Today, Lenovo announced the Lenovo three sixty AI Express program. Now I'm excited about it. You'll know about Top Choice Express and how we're using that to to deliver solutions to you really quickly. And we're pleased to be able now to be able to extend that into our AI portfolio. So it's about having validated AI configurations suitable for small customers to large customers. As I said, validated, ready for you, nice and simple way of doing things. We do it in kind of free t shirt sizes, a small, medium, and large. And it depends, you know, what what what type of demand your customer's going for. What size is the... How many how many parameters is their model size? How many users do they want? The kind of levels of of trans... Of tokens per seconds that are acceptable to you. And as you scale that and look at different types of workloads, we've got the small offering based on our our two u six fifty a, dual socket server there with two RTX pro GPU GPUs. And we jumped to a midsize with our $666.75. That's a three year box. We got some more space for GPUs. We could be up to eight, RTX pros there. And then on the high end, our SR six eighty eight a, which supports the the NVIDIA HGX v three hundreds. So really nice underlying hard... Hardware, validated configurations for you. And the key thing is is is really great, delivery times. On the small side, from about a 15... Fifteen days some time of order, to the larger systems at twenty five days. There is a... There is one thing to note here. These GPUs, they're really high in systems we're shipping you here, and the the GPUs are controlled. So we do have to go through end user verifications. We have to know... We just have to go through that step, and that... Those number of days kicks in from that point. So depending on what you're looking to do, whether it's focused AI inferencing, where you need high throughput inferencing or perhaps a genetic AI, where you need to go to full blown generative AI, these AI Express solutions are really, really nice for you. And, again, in the docs link, there's a link to the section in the Nova partner hub, which will give you all the details behind this, this presentation decks, this flies, etcetera. And then late October, early November, I'm gonna be joined by my colleague who's the project... Product manager for this, and we'll talk you through this in some detail. But, yeah, the exciting thing, go click on the link, have a look at it. I'm really excited. I think it adds some really interesting options for us. So hopefully you... Hopefully, it works for us all well. Thank you. And with that, let me introduce you to my colleague, Florin. Florin is our manager for the. Lenovo step team. There you go. He's been in the industry for about twenty odd years, and he started at a company called Blade Network Technologies. And And for some of you, a bit older like me, might have been around in the early days of IBM Blade Center. These were the... Blade Network Technologies is the company which made the network switches for those products. So long, long lineup with a long history with Lenovo and, and IBM in those days. And, yeah, Stellian joined Lenovo about six months ago and heads up the new step team. So, Flora, without any further noise from me, let me hand over to you, and and thank you. Yep. Thank you. Thank you very much, Bevan. Hello, everyone. As, as Bevan mentioned, I'm, Florian Steljan. I'm, managing the the step team, which is a technical presales center, covering Europe and Meta. Now for the next, few minutes, I'm going to go over who we are, what we do, and how you can engage, with us. And at the end... Towards the end, we're also going to have a short demo on how you can open a ticket with, with the step team. Okay. Now let's start with the step center, mission, scope, and operating model. So we're we're a centralized, technical presales group. All my team is based in, in Romania, and we're providing technical presales, support for Europe and, and meta regions. So if we are to look at the... But our audience, so, we're servicing Europe and Meta ISO, ISG markets. So this is exclusively for ISG product lines. And we're servicing internal, internal customers, so account managers, specialists, presale specialists from from the markets and, of course, the channel partner community. Now how we can support? Now, we're talking about two areas that you will see here. So I'm referring to the first one as the, let's say, the legacy support, which, which has the technical questions, technical guidance. We can be talking about sizing solutions, configuration reviews, bond validations, and, and so on. And, of course, best practice, recommendations for solutions offer... Offered to the to the customer. In terms with, with the times and also in relationship to what Bevan was mentioning earlier, we've also expanded into the AI space. So, we're offering, right now support for AI optimized servers and computes, AI factories. So starting from the scales that were mentioned earlier, going up to larger scales of, I don't know, thousands and tens of thousands of, of GPUs. Of course, this comes together with networking. We can... We... We're covering more and more complex integrated solutions, and we are developing internally, more AI enabled service tooling to to help us. Direct liquid cooling is linked to the, let's say, to the... To GPU heavy configs, so that, that comes as natural. Of course, it's worth mentioning, what we are not covering. So something important, it's, HPC related, let's say, questions and cases, and these are these are being handled by a separate central support team. We do not own, customer RFPs, and the reason for that is the the commercial judgment and the customer context, which we do not have. And there... There's a differentiation here, and it's important to know we do not own them. That doesn't mean that we will not engage in, items that are in relationship with RFPs, with RFIs. So there may be questions. There may be validations. There may be sizings, where, you need help with, and, of course, we can definitely help with that. But not having the context means that we will not be we will not be owning the final solution. And, of course, it's worth mentioning that we are not here to replace local presales or partner autonomy. Okay? So it's still... Everyone is still, free to, let's say, configure and do everything on their own, but we are here to, we are here to help. Moving to the next part on where where we partner. So, again, as I mentioned a bit earlier, the partner owns the customer discovery and solution strategy. Right? Because customer interacts with the customer all the time, so they know the requirements, the opportunities, and what they are and what they want. Now where we come, we come to add the, let's say, the expertise and guidance and or validation to the to the solution. So we can be considered in a way as, as an extension of the of the partner's technical, technical team. And we are adding, extra capacity to validate, let's say, solutions and configs to Lenovo's, best practice best practice organization. So, again, we're a complement. We're not a replacement to, I don't know, any other, any other organization. Okay. When should you engage with us? That's that's an interesting question. Of course, as mentioned before, you need an answer to a technical technical question. So you're not sure about, I don't know, some coverage or there are things that are are not clear. That's definitely in scope for, for our team. When it comes to guidance on, I don't... Selecting the proper solution or sizing or any of these, again, this is, this is in scope, or we can be talking about reviews to a solution that you want to you want to propose to your to your customer. And that key... Can be, I don't know, BOMS configurations, validations, different types of, of options. And in general, when you, you need expertise for integrated opportunities for... And, of course, potentially, more complex ones. And it's worth mentioning that we're especially valuable for, I don't know, complicated solutions spanning multiple technologies. Of course, if, you do not have special... Specialized expertise locally, if you require additional validation or you just need some, some checking against, against the Lenovo standards. Okay? That's pretty much when we should, we we should be engaged. What can we support with? Again, we talked about legacy support. We talked about expanded capabilities. And looking at the legacy, so think systems, servers, infrastructure, storage. We can be talking about the hyperconverged infrastructure, so Nutanix related, VMware, Azure related. That's also within our scope. SAP infrastructure, systems management, so exclarity related, I don't know, questions, guidance, what's in, what's out, what's, what's coming, and, of course, technical sizing guidance and, and validations. We are... We have been expanding over the past past few months. We have been taking on more and more, AI related questions and validations and helping with, with different, RFI, RFP in the in the AI, AI space. Again, starting from small configurations to rather large, large AI factories, which, of course, come together with, the networking part, come together with, with the cooling part, of course, liquid or, liquid or air, and, of course, not limited to to AI. So there are complex, solutions spanning the ACI space or even three tier architectures with, with servers, with networking, and with with storage. Moving a bit, let's see how how how we work and how the how the interaction how the interaction goes. Of course, first logical step, the partner identifies the the need. Right? You're discussing with with the customer or you're you're looking over some documentation and technical questions or different, I don't... Areas are of, of interest where we could we could help. The next step is to submit a request through the step portal. And a bit later, I will also, show you how this can be be done. It's quite quickly. It only takes, takes a few minutes. Again, it's very important when you submit a ticket through the portal to include as much detail as you have, like, I don't know, requirements, configurations, relevant files, required dates. So, again, the more the more, the better. It helps us deliver the answer or the solution to you faster. From the step portal, this, of course, the step portal is a front end to our, to our database. Our team receives the receives the the ticket, and somebody from the team picks it up and sends, sends a response. So we're checking the request. We're flagging, of course, missing information if there is missing information, and we are providing findings or recommendations. In some cases, of course, if we need to involve additional internal resources, we reach out internally so that for you, pretty much the step team is the... Or a member of the step team is, the person you will be, you will be interacting with. The communication... So once the ticket has been opened through the through the portal, the communication occurs over emails. You will be receiving first an automated email, and then a person from from our team will be contacting you directly and providing questions or, responses relevant to, to your case. Now, of course, once this has been has been solved, the partner, goes back with the information from us and completes, completes the the opportunity. Again, mentioning here, so partner retains, ownership of the final design engagement and commercial, commercial decisions. Okay. Now, again, we've been talking about the step and how you can engage with us, and it's worth mentioning what should be included in a in a good request and what makes a good request. A good request is a request that after it's being taken by an engineer from our team, that engineer has enough information to be able to reply... To to give you, let's say, a solution or guidance without coming back with, additional, questions or reducing them as much as possible. So, of course, it's worth including clear description of, of requirements. What is the workload? What is the intended use case? This goes back to what we were discussing earlier about the customer interaction which you have and you know all of these, all of these context. Our engineers work on hundreds of cases each month, so they do not have this context that you have. Of course, you you you would need as much as possible or if, if needed to attach the proposed configuration, the proposed BOM, mention areas where you need review or validation, Mention constraints, dependencies, where they are. And, of course, it it... It's important to, to mention a completion date. If, I mean, if something is time sensitive, it's always worth, worth flagging. Okay? Of course, supporting documents configuration files, that's that's that's normal. If you're referencing something, please make sure that you are, you're attaching the configuration files. Things to avoid, of course. It's, quite the opposite of what you need to to include. So avoid requests without, without customer requirements. Just check this or stuff like that. I'm I'm going to show you a bit later some good ones and bad ones. So... But avoid request without, customer requirements or, configurations without explanation on what we need to what we need to check, what we need to validate. Commercial or pricing questions, you can ask them, but we will not be the the right people to to answer this. So avoid, asking asking this. And as we mentioned earlier, we do not own opportunities, so avoid asking these kinds of, these kinds of things for, for our team. Now I gather here a list of some examples of good good requests. And, actually, these are literally copy paste from some, some actual, actual requests. So for example, for for the questions, does the s 4,300 support l l t o 10 warm media, and are there any drive or formal prerequisites? This is a good, is a good example because you see the product media. You see you see what is being asked. And, of course, these examples are the shorter ones. In many cases, they are much, much longer. Or the second one, confirming if trans... If a transceiver is required or provide equivalents or not. So they... They're they're clear. They provide the stage. They set, they set the the expectation in, in each, in each case, okay, even for verification. And review the attached and verify, I don't know, compatibility or sizing or support risk, not just verify. Okay? You need... I mean, it's better to, let's say, point us to what, what you are looking for, specifically. Now if we move to common issues seen by, by the team, so that's, pretty much the the opposite of the previous, previous slide. We've what we've seen in the past few months, we've grouped them into three large areas which are occurring, more often. We're talking about ambiguous expected output, missing or incorrect source files, or insufficient work... Workload detail. And taking them one by one, of course, for the first one, it makes things unclear what we should do. Should we build? Should we review? Should we change? What elements are in scope? And, again, the short example is an actual example from from a request, re... Review attached configuration and share your guidance. Okay? And, of course, we we could guide in, I don't know, few different directions. And if you do not provide specifics, either we will come back asking for specifics or maybe provide guidance in a direction other than what you are, what you are looking for. In both cases, time is being, is being lost on both sides. Again, missing or incorrect source files, that's... That will trigger, in most of the cases, it it will trigger a response from, team member from from my team asking, okay. Can you please, can you please attach the files or you reference some files that, that that are not are not in there? Same result. Time is being, time is being lost on, on both sides. For insufficient workload, workload detail, it's always... I mean, it's understandable. Everybody, when you work on something important, you have all the context in your head and you imagine that everybody has it. What my suggestion is before opening any case, I mean, read the description and put yourself in the shoes of the receiver. If you were the receiver, would you understand what needs to be done? A request like sizing assistance for the s 7,200 without anything else is... There's not much that we can do to to help in, in cases like, like this. So try to add preciseness. Try to add as much information as as possible. You will see... I mean, those of you who haven't used it will see that the form is quite easy to fill in. If you've used it, you know this already. Okay. Now it's time for, it's time for the demo. So I'll start sharing my screen. And I will walk you through the steps to open a new request. Okay. So this this can be done from, from two parts. First of all, is the step.lenovo.com website. So it's step.lenovo.com, which takes you here. And you can also have the link from the Lenovo Partner Hub. So if you go to products and services, additional tools, infrastructure solutions, presale support via step, Both of you take you to the same, to to to to the same link. You click on Lenovo partner, and that should load you in with the same credentials as the, Presta, Lenovo or Lenovo partner hub. Okay. Once you're here, big red button, new step request. Click here. Select the region, Europe and Meta. This should be prepopulated with your name, email address, and, and country of residence. Now you would fill in your phone. I don't think this is a mandatory field. So you may want to do this your role, so distributor or reseller. And what would you like help with? So, again, the options are validate the configuration, ask the technical question, and, and sizing. So you select one that's the most relevant to your, to your case. And pretty much these are the two most important fields. The first one is the summary where you specify, okay, what do you want? Need help validating this solution. Best. I'm flagging this as a test because my team will actually be getting this, this ticket, so they need to know that they should ignore it. And here, of course, add as much detail. Detail one, two, three, four. So anything that you need to put in here, just just add the add the information, add the context, add, I don't know, whatever you consider is relevant for the for the case or for the validation that that needs to be done. If it's a technical question, provide the context and, what you're asking. And, of course, if there's some information that you find, it's worth, mentioning the the source of the of the information. Next, you can, provide the the topics and subtopics. For example, it's a systems. So when you click each of these, you will see that subtopics open for each one of them. So see, here is SAP and the ones related to it. And you can select multiple. So for example, you can say systems. I have a rack system, and I also have storage. So... And if you click on storage, you will see that another one comes here at the at the bottom. So I have, I don't know, DG storage. Okay? And, of course, you can select multiples, and you can click on the topics and subtopics as you as you wish. This helps a lot with categorization and also with, within the team, we have, engineers specialized on different areas. So they will be picking it up. Of course, if you make it... I mean, if you make a mistake, it's not that your ticket will be will be ignored, but it's always a good solution. I mean, a good, let's say, recommendation to add the proper topics, subtopics, and, and so on. Then you go to the priority part. I would recommend... So unless it is, I don't know, super urgent and so on, stay with, with the standard standard priority. Okay? Of course, if it's time sensitive and so on, you can, increase the the priority to high priority or business critical. Preferred language, it's, English is the is the only option. Now this being said, if there are some, documents, that are relevant and are in a different language, do attach them. Everybody has, I don't know, LLMs these days. They can translate from any language to any language. So you can please feel free to attach, supporting documentation in languages other than English. Just be advised that response of our team will be, will be in English. Uploading files. Again, it's optional, but recommended wherever, this is, this is needed. You select choose files. You select the files that you want. You click... You can select multiple, by the way. And you will see you will see here how many files you attached and the names of the files. Okay? So when... If you want to attach multiples, just make sure in the choose files, you select all that you want attached. And after you've, you've done add, make sure that they are, they are listed here as the as the selected selected files. Additional information, opportunity size, if you have it, the win chance, the customer name, and country. And here, it's also important include colleagues. So email... Colleagues' email. So for example, you are the one opening the the request, but there are another, I don't know, two or three people from, from the company working on this, on this opportunity or or working on... Interested in this topic as well. Add their names as well. What will it mean? It will mean that our engineers, when they reply, they will be replying to you and to all the people from this, from this, email addresses. Okay? Now additional additional options, if it's related to global accounts, if it's for an RFP, if it's a true scale opportunity, and so on. Warranty related, related options, if you want to keep your driver, any of these warranty term systems management, checkboxes. You will see that some of them are, by default, on. You can unselect them if, if you want to. Okay? Other requirements, honestly, that's not being used a lot. So if you're adding all the information needed here, you shouldn't need to add anything else, in this, in this area, in the other requirements, tab. After you're done with everything, create a customer name. Yeah. I have not... I need the customer name. Customer country. Let's push. You've seen that the errors were being, were being flagged. So the fields that you should have selected and were not selected are being flagged even here as well. Please select one of these options. It's not. Create my step request. Click on it. Wait a few seconds, and you will get a message. You will get a notification, step request, and this is the this is the reference of the of the step request. It says it has been created successfully. So right now what it means, the front end communicated with, with our database, this case, has been opened, and it will be in the queue for somebody from, our team to to pick it up. As I mentioned earlier, what you what you will see... Let me see if I can open this because it's it's important. You you you will be receiving an email, an automated email. The request has been created and with, with the summary of, of all all all your requests. And you will be able to see all of this, all of this information. Here here is the email. Yeah. Thank you for submitting. Somebody will respond. Here is where you can check. And as a reminder, here is a summary of your of your request, of your request details. Now, additionally, what you can do, you can look at my cases here directly from the portal and see all the cases you've opened. At any given time, you may have more than one one case open. So you may want to you may want to see, okay, let's look at everything that that I've opened. You can click on it, and you can see what the status is and, I don't know, when you opened it, created, modified, and so on. After it's done, you will be able to provide, to provide feedback. So satisfaction, speed of response, quality of, quality of technical, technical response. As I mentioned earlier, once this is done, somebody from my team will contact you via email. So from here on, the communication will will occur over, over email. Okay? Now this, is pretty much, the presentation. So we're going back to the questions part. Helps if I unmute myself. Thanks, Florian. We've got some great questions coming in. The the first one, which we kind of expected, was, I used to work with the lead team. Now there's a step team. Is... What's the relationship between the two? What's happening? Yes. So let... Let's let's team has, indeed been around for, for many years, and, the step team has been live since July... End of July. And we are sort of an, of an evolution to the to the last team. So you will see some... The the service that you were getting from the last team. You will continue to get it from, from the step team. And we have added, additional, let's say, capabilities mainly in the AI related, related area. We've spoken quite a bit about, I don't know, a factory or GPU heavy design. So this this is an, let's say, an added capability from the from the staff team. From the, let's say, opening cases and workflow that pretty much, stays the same. So we used to have lets.lenovo.com, now it's step.lenovo.com. But if I'm not mistaken, lets.lenovo.com still works, so it will redirect to step. If you have it bookmarked, you can go to lets.lenovo.com. You click it and it automatically takes you to step.lenovo.com. Okay. Great. So it's a... It's... As you said, it's an evolution of the Let's team, and it it takes over the functionality and the services. provided by the. the Let's team. You mentioned service. So here's a question for you. If as as a pawn, I come and, I I log a request with you, how far should I expect the response? the the SLA for the responses is, one business day. So what does it mean for... So we are our... We're working Monday through Friday, regular working hours, so nine to nine to six. Okay? So for example, if you're work... If you're opening a ticket today at 09:30AM, you will most likely get a reply in the same working day. As per the SLA, you should expect no later. So if you opened it at twelve today, no later than 11:59 tomorrow. You should you should be getting your, your response. So the general SLA is, is one day. There might be delays sometimes when the load is, I don't know, very large, but generally in 95% of the cases, this is what you should see. Okeydoke. One unrelated question was that, in the presentation handout, I never included my one page on AI Express. I have now loaded that up as a separate slide. So if you wanna see that, it's now available under docs. There was a question regarding the the functionality of the website. So for example, there used to be a dedicated q and a page where we could find useful information. So instead of having, like, a support ticket, you kinda go through the information and and, find it yourself there possibly. Will that be coming back to the site? Is it there? Did we just miss it? Currently, you're right. It's it's not, it's not already more. We're not sure whether we are going to bring it back or not. What we try to do, we try to, let's say, streamline the streamline the website and maintain the engineers' focus on, I don't know, responding and, replying to all of this. Anything that is manual labor requires, requires maintenance. So right now, you're right. That one has been has been taken out because we want to keep on the site stuff that's up to date and that's... That is maintainable. Right. Another question. The Let's team used to participating in meetings with clients. Is that still something which could be could be arranged? By default, the step team does not have direct customer interaction. This is by default. And we mentioned it, throughout my my presentation that, our customers, to put it this way, are partners and our internal folks. Now this being said, if there is a requirement and... I don't know. We need to... Adding a person from my team helps, shorten the time to resolution significantly, of course. It's... I mean, this is, this is doable. But I wouldn't take it as a default option. I mean, always you go with the customer. I do not care what you talk there. Just solve my case. It's not within the purpose of the team. Yeah. But the... And the the... Our policy could obviously leverage the Lenovo tech sellers and and solutions architectures to help architects to help them. As you said, you'd back them up and give them information they need for that. Got a comment that there's a a link on the step portal for submitting a request to the briefing center. There was a question about how that worked, or what was the Briefing center. yeah. So the the the question reads, I saw a link on the step portal for submitting a request to the briefing center. How does this resource work? I I do not know our you. basing Okay. We'll we'll check that out and get back to you... Back. to the question. answer on that one. There you go. Are there other ways I can open a case for STEP other than through the portal? For example, can I email people? I would not recommend the emailing people. And, of course, over time, you will be you will be interacting with, different people from, from my team. And, of course, you will have their, their their emails. I firmly recommend that opening the tickets be with the with the step portal, and there are a few reasons for it. First of all, we're talking about, I don't know, areas of expertise. If you open it through the portal, more than one person sees it. Right? So it's being seen by all the team, and the person who has the most time availability and the best knowledge will pick it up. Right? So you will get faster reply, and you may even get better reply. If you just send an email, Unicast, to me, for example. Let's say, you know you've been working with me on five, six, six cases and you send email to me. Maybe I'm on PTO for the week. Maybe I'm busy with something else. There is a good chance that the response will be delayed. And, again, it may get lost along other other emails and communication. So my recommendation is to always open it through the through the portal. You have. something... An an older ticket that you want to reference reference the number of the ticket in there. So while they use the use the protocols, then it's scheduled. It goes to a queue, and you'll get quicker re... Quicker access to resource. And and it it roughly takes... You've seen it takes, what, five minutes to open a case. It's not it's not very time intensive. Yeah. I'm just looking through the questions coming in. Thanks to. everyone for asking the questions. Lots of feedback on the old list portal, the technical information which was there. So that might be something we need to look at and think about. Let me see what else. We need to check for you on the the... So it wasn't the briefing center. It was innovation center, which the link refers to. We'll just have to check on that and see see what the back end is. We'll resolve. We'll go back to you on that. Yeah. So step replaces let. So send your send your, send your, request through the steps portal. Yep. Everything you've been getting through the through through the labs team, you can get now through the through the step team. And we've we've spoken about the inclusions and exclusions. So, again, except for HPC, anything that is in relationship to ISG, escalate. It's in scope. There's one other question which is whether... If if... Whether people could, submit requests through the Let's team for for new features. So for example, you wanted something new next priority one, if if you could submit that request through, Lenovo Step. I think that the better way to do it would be through your your... Either your partner account manager or the technical person, and they can speak to the relevant product manager. Correct. Got. it. Let me just... I'm scrolling through questions here, just making sure that I've covered everything. There are some messages saying that the links aren't working. We've double checked them. I've got people external to Lenovo to check them. It might be a it might be a it might be a local block on your side. For the LPH link, you'd obviously have to have an LPH sign up to be able to get to that. But if you can't get the document, you want it, just drop me an email, and I'll send it to you directly. I'll put my email in the... I'll put my email into the chat for you if you wanna... If you're missing any of the documents and you can't get at them. Just having a quick scroll through here. There's lots of comments, lots of questions, but I think we've addressed all the main I think we've addressed main... Any of the main points. We will go through the questions afterwards, and if there's anything we feel we haven't answered for you, we'll get back to you here... To you. Yeah. There was also a question if we shall stop asking let's. So again, let's.lenovo.com is step.lenovo.com. So it... It's it's... From your point of view, nothing changed. Okay? So what you are getting from, from the let's team, you will be getting from the you will be getting from the the step team and, again, with, with the additions of the of the new technologies. Got it. Thanks everyone who's giving me feedback on the on the website and some of the resources you'd... You'll see there. We'll share the comments and, and, Lauren and Lauren and the team will have a look at it and see what we can do on that side for you. But, yeah, we we we we see your comments on that. Thank you. Quick reminder from my side, please complete the survey for us. If there any other further questions or or follow ups that you wanna do, you could drop into the survey link for you as well. We do go through all of it and review it, and it it helps helps us evolve this program and make it more valuable to you. Next up. Just a reminder of what's coming up. So remember the, there's the LinkedIn Lenovo partner site. The the QR code at the top right there, if you if you scan it on your phone, it'll take you to that link, and you can you can see the page directly. So as we announce new events, it's published on that site for you. Also, be published in Lenovo partner hub for you. Next week, we do a storage update. There's some new ThinkSystem storage announcements happening. So Rob Brazier, who some of you know from some earlier calls, will be joining us, and he'll talk you through what the he'll talk us through what the new what the new ThinkSystem storage product updates are happening, the new announcements there. And we're also joined by, one of our colleagues on our support business to talk about premier support plus for storage. So how we can wrap those storage solutions with a great support offering. So that's next week. And then I made a mistake on the slide, but the October 14 is a is a Wednesday, not a Thursday. Just checking you're paying attention there. So on the fourteenth, we're gonna do it a a day earlier, and we're gonna be joined by Veeam. And we're gonna talk through some of the sales plays, some of the partner benefits, and the promotions we're running with them at the moment, as we look to address that market. And, yeah, the QR codes on that side are are... Take you to the registration pages for those two for those two offerings. I've maybe gone a bit crazy with QR codes on on this side. Hopefully, they're useful, though, and it's a quick way of doing things. And then that leaves me with just one more slide, which is to thank everyone for attending. So, we appreciate everyone who joined the call today. We had a really nice turnout. I appreciate all the feedback in the comments in the in the chat window and under the q and a. It helps us do a better job, helps us provide a better service to you, so we appreciate that support. And then, Florim, first time on the community call. Trust it won't be the last time. Thank you so much for joining us, for giving us an overview of the of the step team and. and and where we are and where we're going with it. And, Thank you for having to, Don. inviting you look forward to inviting you back again at some point. Thanks, everyone. Hopefully, see you next week to be deep diving some storage options, some on our on our on our ThinkSystem storage offerings. So join us then, and have a great week. And we're gonna give you back fifteen minutes today, so use it use it wisely. Go look at AI Express. That'd be my my recommendation. Thanks, everyone, and have a great day. And and we'll see you next week. Thank you. Goodbye.