 Hello, hi, I'm Olivier and I'm going to talk to you about the next cloud proof of concept And at the end we'll take questions. So there this is our agenda today So what is a next cloud proof of concept first? It's a great opportunity to actually use next slide in your own environment connected to your own infrastructure It's also a great way to understand the technology and how it's going to use this infrastructure You will have an opportunity to understand the way information flows through the system to build processes on top of it very early on and Finally, this is going to be a Great opportunity to discuss your requirements with an excellent engineers We also want to highlight what it is not so as to avoid any misunderstandings so It's not a full solution rollout that you take into production We just want to be clear on that we can work on a roadmap, but this is not going to you're not going to take this concept and Take it away with your all your users Right away It's also not a migration project if you've been using a Competitors product we can help you define a migration path, but we're not going to actually do it during the proof of concept It's also not a scalability study we won't be a clusters doing that phase and Yeah, would be too long, but you're welcome to test your storage strategy You can connect various back ends to the next cloud and you're very welcome to it Also, it is not training sessions You will learn a lot from us of course during the process, but we don't want to train a whole department for example on how to use next cloud And finally, yeah, this is not an opportunity to get certified as a partner for example There's more to it than just going through a proof of concept to get that certification So we're talking to customers. We actually got lots of similar requests and we defined a standardized process Which then became our standard offer? so what we do is give you access to our resources during 30 days and We provide up to two mandates of remote assistance The process is kick-started by a Workshop where we define the proof of concept and We also defined what we make this project a success That would be beneficial for both of us at the end of the proof of concept We also do an architecture compatibility assessment What this means that we look at all your systems for example and how they can communicate with next cloud But what we'll definitely not do is be able to connect us so that you can connect them during the proof of concept This is can always be a separate consulting project if you need it for example But what we definitely do is help you on integrating your user system your user management system and So LDAP and active directory will be integrated so you can see how it behaves We also offer an appliance to get you on your up on your feet running very quickly and Yes, let's not forget this is a standard offer, but if you need something a custom proof of concept this can be defined for you We open to suggestions Yeah, that's what the initial workshop is for so we can really define the scope of what you want to test and then We can work together, but we have to not forget that as part of us You know standard offers only could going to be two mandates of remote assistance and it's 30 days So usually if you need to get a lot of your team involved in the process is going to take probably longer So you may require something, you know Different a custom proof of concept But for a lot of people what they need is something that can quickly set up put a few users on it Test if one or two system work because those are the essential features they need Test if you use cases and then they say yeah, this is what we can go with and then then of course you go through staging Well, yes, there's a the initial workshop is for that yeah What want to standardize is really the the time length and the effort we put into the proof of concept So what are the advantages of working with us on that proof of concept? So basically you validate your high-level requirements with a against a running installation instead of using the demo and again Because we've defined that in the initial workshop, then you know if those requirements are met You can test performance That will help you define the hardware requirements for production for example And be better at capacity player planning later on You will learn about best practices from us which will be gathered from similar situations. We were in with various customers Also A very good advantage is that you're going to solve some of the issues by working with customers with our engineers directly very early on in the process ironing out all these issues before you actually go into staging or into you know production requiring support and Because of the Compatibility assessment performed that described earlier you'll be able to have a Better view of the gap between your to be architecture and what you have right now and you can synchronize The effort you have a successful rollout and I'll have you know systems rolling out in isolation and have many issues down the line There are more advantages One is because we would have been working with you on that proof of concept We will know about your system and the specificities of your environment and that will help us Support you better and you transition quicker to production Mention also that you have access to an excellent support resources So you don't rely solely on community support. You're treated as if you were a customer And because we're guiding you is going to require a minimum amount of effort from your IT resources, especially if you're using an appliance So I think this sums up all the advantages I can see for For the proof of concept and I'm handing over to Morris. I will now show you how we do the support process at next cloud and If you think about support a process you think about something like this On the left side you have the customer Who asked some questions and those questions usually? come up at a Support team a dedicated team that's completely isolated from from the engineering team because engineering is doing the product and support is helping the customer Usually the support team has given knowledge about the software and has access to internal resources to documentation and tries to get an answer for the customer with all those resources combined and Tries to get back to the customer with this answer and satisfies the request for the customer The only issue is that from time to time your support team isn't able to fix an issue or to point a Customer to how to fix the issue themselves or provide Additional documentation links or something like that and then the support team needs to go to the engineering team and ask questions and this is often followed by a back-and-forth between support and engineering team and They are often some some issues arose Something like yeah, the support team has somehow Misunderstood the customer and communicates the wrong stuff to the engineering team and the engineering team then Can't even get the proper answer because it's not perfect 100% perfectly that what the customer wants or the engineering team misunderstood the support team while even communicating and all the back and forth Yeah, simply takes time and the customer noticed this Because the response takes longer and we thought yeah we need to address this somehow because the engineering team has a huge knowledge and a huge expertise and We want to bring this Faster to the customer because this also means the support case Doesn't take that long. It doesn't take that much resources Don't scroll over hundreds of open customer requests because you can answer them fast and close them fast and make the customer Yeah, satisfied because you just have the right answers and Another issue you have with this is if support has a solution for For a given a given problem It doesn't even come to the engineering point and support needs actively give feedback to say okay 50% the customers asking for this specific thing we fix this with that workaround and communicate as always back to the customer But at the end it would be maybe better to just fix it on the engineering side and never have the issue pop up again So what we think is how a support Psychic should look like is something like that You have some supporting people in a in a support Team but most of the time also engineering is involved into this process because engineering builds a product that somebody uses and What would be the best way to yeah know what your customers or users are doing then just talk to them so Here you clearly see there is not that much ping-pong between a support member and the engineering team member because There is no need to have this proxy through a support team, but it's simply solved by engineering directly and This also has the advantage does Yeah, something like this but down the lane doesn't have that much effect. You can't misunderstood Man in the middle that just simply translated something wrongly or the missile misunderstood something so it's a It's it's good for both sides the customer has faster and Better higher quality feedback and responses and on our side We have fewer requests because we understood how our customers and users use our projects What are the the points where they have problems and? Maybe how we could adjust the product slightly to match better the use cases that are that occur in the wild And to understand is a bit better. I have an exam. Oh, yeah, that's that's the sum up of all of this and I have an example This is the screen you see when you share Why are a public link and hide the file listing? That's an anonymous upload you can send around this link to five people that can upload fires and They pop up in the folder, but the people can't see the content of this folder that's the device drop feature and One of the most requests we got from users and customers is We have some data policies here and we want to add a disclaimer to this to this page because We as a company need to guarantee that the data is not somehow Has not no rights reserved somehow or that there are no copyright Violations happening with this fires because the fires in the end lend on our server and we need to take care of this So they request that there should just be a little a little text that is shown to the uploader and Yeah, how you would do it usually from a support point of view you say to the customer Yet you can use that page copy it over to the theme directory add your text in line hard-coded and That's it. The support case is closed the customer satisfied because this feature is now built in on Their instance it's themed But it has a huge disadvantage because now you moved the maintenance factor to the customer The customer needs on every update needs to check if the theme still applies if everything still works they only tested some cases and not a huge range of use cases and in the end it's bad for both sides because After an update, maybe this page is broken and not noticed right after the update but two weeks later and nobody knows why it's broken suddenly and This Looks like the product is buggy and doesn't support this probably and on the other side the product itself Can't be a The cause because it's just fuming and we said yeah, you need to maintain your female self so What we did here in this case We just thought yeah would be as simple to add for the for the sharing section a Default disclaimer that is shown if it's configured the admin can say show this text all the time It is well integrated now in the in the product itself It is it is tested on our our testing or by our testing team We we have built into the product and understand how it works we can properly handle the upgrades and There is no maintenance cost at the customer side or for the customer admin The users are more satisfied the admins lasted and we also have fewer requests in the future so This is one example of how this new process is better for both sides We as we as a team understand how the product is used and What yeah paper cuts are in the product that usually gets solved by some workarounds, but maybe should be fixed properly and Yeah, we just make it make the whole process easier for Thanks for your attention. Do you have questions? Yes Like Regarding a future request for the for the versions or for what? Yeah, usually those those features Where we collect usually we collect this all and get up my stones and then Compiler list out of this on stairs a release With the if the latest RC. There's also a forum post via we we encourage everybody to to test new release candidates and There's also a compiled list with what was fixed in there and that's also then the case for for future releases So this is then also listed in there Thanks