 Hello, so it's 1 past 3, so we are in Switzerland and I'm German, I've been wandering after 3 o'clock. So, hello, my name is Sotka Rigger. I want to tell you something about migration, migration or issue which was coming up in the concrete study we made for customers, I'll tell you later a little bit around. And I want to tell you the story of how get they be scared. Because they took the security for a political discussion. If they should, or could, migrate to the office or not. And then we tell you about which certain senses around come to this scene. And how we tried to solve this issue. And I think it covers all the issues in the discussions for migration which when you face when you come to a customer. They put everything in this security. So let me put a look on the slides. Cox is a website, a platform we are trying to promote for information to get around. Even for a free office. So, first of all, as Carlo mentioned yesterday, there's methodology for migrations. And to frame a particular part of it where we are going. It was very in the front of migration methodology. We were in the feasibility study which is in the front of every migration or rollout deployment. Where we have to define targets, what do you want in the migration. Where we have to do inventory for software and hardware. Which applications are integrated with the office to define migration strategy. What you are doing with the old documents. Should they go on to the new document format. What's another tool or automation to calculate total cost of ownership. Is it really for financial benefit for the customer to migrate. And bring this to the decision maker in the company. Which decide hey we go to the office or we go to another office. So, in this story we are in the very first part where we do software and hardware inventory. And as you see in the next slide it was not such a big customer. It was 250 clients in a tool manufacturer for automotive industry. What they are doing is they do physical tools with which cars are combined or produced. So it's a manufacturer. So not all of 250 clients are daily office users. But around 120 of them they are doing their work dealing with the office of others. Just for filling in some forums for the personal department for the administrative department. So we were doing such interviews with different people. We have an interview and we came in in late April I think. It was mid or late April. I come in and heard something. Hey there is a particular alarm. And I've heard upbeat for this interview day. But I was not bringing this together with migration to people. As you know upbeat was the leak which was found in the open SSL algorithm made by a German student in it. And it made them sensible for security issues. They were feared about the fact that they could get an open source office suite where such a thing like heartbeat could also be integrated. So this was the main issue and the discussions going around. And they took this issue to say this could not be an office suite which we want in our company. Of course they could be risks, security risks when we use it and so on. And it was used by maybe by sex persons where we have the interviews on that day. And what we later understand was that these discussions came from a very specific point. But this we will understand later. They don't tell us this the day. That people were scared due to the experience of document issues in Microsoft Office. By one big customer it is a huge German automotive producer. And they have to give their offers for their product in a defined form. In a defined document. Every thing in this document is defined. They are the formats and so on. And they had huge discussions with them to bring it into Microsoft Office. And what they fear was if they get a new office suite. They have to discuss this with them again. New discussions, new work to do a new form. And perhaps that all of this will be. This is the favor, fear of a sex person. If there is something between me and deal it must go aside. So this was the real fear, the real issue which was behind. But it was the mid of April and there was upbeat. So as everybody should know who do migrations in this area. You have to take care about this fears. Don't say this is not a security issue. Go away, you have technical problems in the industry. You have to care about this. So what did you do? You went to the IT guy and asked him, hey, we need two more days for the physicality story. He asked me why. Because we want to go with you in a workshop. Not just in days, but what we work on most of the days. And define something, one of the security demands for you. We have an office suite. What are your security demands on it? And spontaneously agreed and said, okay, how do we do this? And we take the sex persons together, not in a face to face interview, but in a group. And asked them to give some inputs for the workshop we later made with other key persons. One of the same advice was with it. And here is what they formulated as security issues with the office suite. First of all, they know that's a technical issue. So I have to formulate. No technical vulnerability. So the real security issue, well, that's a wide range of issues. And no response. Another answer is coming later. Something to do with creating. Second function of completeness even in the future. Or the feeling of trust that I have the right to even for future demands. Even if I don't know it now, I need a specific function. It will be in the future. Someone was informed about intellectual property issues. So when everybody could throw them in this code, there could be a content drawing or something. Where we get forward to the call. This is not a security movement. The first one I write, you will not be able to prove it's a bruiser. What he meant was if I go to work with other people, even outside of the company, I want to handle that. So my initial question was, hey, wasn't he the secure man in the world? Yeah, the IT leader said, hey, costs and follow-up costs. Costs I can estimate or whatever follow-up costs. I'm insecure or want to have trustworthy about follow-up costs. Zero and so on. And this is a support theme. If I get a job, who could help me answer? So this was a list of the main issues of this. Which was made initially on that day, where the inventory interviews were originally planned. And beside that, you have to go a little bit more in detail. And we arranged, nowadays for the workshop, with five people to go in detail. We managed that we could have another technical guy with me. And that we could take some issues of that and show them directly what is the answer to the bruiser for that. Not all of these are technical issues we have seen, so we have discussions. But especially some of it should be shown directly to them that they are secure. They could have trust. So in the real technical security issue they formulated, well, they could have some source proteins. What am I doing with the source proteins? But this was not the example which we could give them in the workshop. But I took that because it's a very good example of the last week. Even though it's not the source proteins, but it handles CSB issues, I think. There is a backverted security fix for version 4.2.6. So there was the first version of 4.2.6 and they had a backfix in it for CSB filters. So we can show LibreOffice community and others, or their part of the community, are aware of security issues. And they are reacting. Then they asked about Microsoft, Microsoft killer macros, macro viruses and so on. And we showed them the security center of LibreOffice showed them, hey look, we have the same security levels with macro handling as in Microsoft Word. Passwords on documents or parts of it. And this was even a funny point because first we discussed, hey, passwords could be dragged and are not safe, are not safe encrypted and they are doing rumors that you can break Microsoft Word passwords and so on. So is it a good encryption algorithm in LibreOffice for passwords? And we showed them in LibreOffice there's the same or quite better encryption rules with it than they have in their old Microsoft version. Okay, to a final minute. In other words, hey, what's the point when my guy is done with the password? I want to know the content of the document and we decide that this is not the issue which is differential, Microsoft people always allow for speed, but it isn't the issue. But it is security for them. Another big point was the online update. Every activity going via the internet to someone else, giving data or something like this for update for these, they know the UI, feedback system what they are doing and so on. And they don't have any shock in the options that you could say yes or no and you could give a level of what is going out of my client to a person. And even we showed them that they can use it for their own. That they can use the online update process in LibreOffice on their own server. That you can link these automatic online updates to a source in your environment where you can decide now I want to update my version that they couldn't take it out from me. This was the first time they said, oh, there's more that they have before. So this question we were hearing two or three times is another question about Microsoft with these permanent catch demands what you have to do. What is the binary document format? You don't know what is in there. With the password agreement I've had to explain which runtimes and DLNLs are in the Microsoft Office which we use, the control and transparency about the data which is storing over the internet and so on. And this was the first time they get interested in it. There was a little much more of such details. I've mentioned feedback pressure reports, the registration process. When they started to work with the quick start theme we showed that they can turn off it. There was a few what it was that the process was doing on my computer. So I turned it off and there were four problems. Those of data in my office very strong. This was a functional issue because of the architecture of repo office. If one module of repo office grays, the whole process is graced. So the other modules are graced. We have to do the document recovery process for all kinds of modules. And now we are studying a little bit away from the technical security issue and coming to the soft parts of it. Just the duration of the life cycle of a suite. It means that they use office much longer than one version of Microsoft Office longer than five years. And they want to have this decision to set it sustainable. This is an absolute right decision point. With this question there was how often do I have to have a new training? How often is UI changing? This is one of the big arguments for repo office. About the duration of the life cycle, is there a sustainable software development process behind repo office? So are we getting bug fixing and support? How is it organized? Could I see some fog lists and see the process in which the issues are fixed? And we showed them a little bit of the organization of the TNAF engineering team which decides about the release cycle. We showed them that there is an engine version engine for still and for fresh to get new functions and to be secure with stable versions. And so on that there are hunting sessions and so on. And we discussed the duration of the open source engines. They asked if the community is ready what will be with the product. And I asked, okay, even if it's not very, probably, a problem, that Microsoft will go away and don't deploy a new Microsoft. But what is if Microsoft says no, we are doing no more office suites. And this is what I call the open source. And it is shown by repo office. There will be, because of the open source issue, there will be another community or supporter and so on, which takes the open source and made it a value for them. And it goes off. So this is an issue which is positive against Microsoft. So the question, what about Microsoft? Just the function and completeness is the question, do I get all modules functions in the faces? I mean, if you try explaining this in the fourth screen, what did we show them? We showed them the modules. We showed them that they get desktop database for free for all clients because they have a two version strategy in the company. Some guys have access. They did have access and some not. And they get a free for all clients. Besides this version, which is good. We showed them that the face is okay. The UI, that is similar to what they know. That there is a fall down to the add-on on the Microsoft website with extensions. There are sources to get extensions for free or for paid license. The only thing that was a little bit problematic that the, technically the main client, the example of the main client, that this was not bundled in the repo office suite. But you know the answer. Take from the word that you have two different admin search processes to install. So this was one point we said, okay. In the pure repo office suite, there is no main client. I asked about for the future of the browser office. We could give them some hints. Especially in the get now, you know that there is something going around the country. All the tools, which are based on the repo office with the same look and feel in Lola.com and so on. We gave them a feeling that there are solutions like Microsoft Office 365. Another big point was collaboration. Collaboration features. Yes, we discussed a little bit about SharePoint protocol. And that repo office is already able to take the SharePoint protocol. Even with other Microsoft Office suites. But if you're honest, you have to say this is 60 to 70% of the functionality which SharePoint is giving in the Microsoft Office suite. It's a little integration issue. So, even in this point, the question, and what about Microsoft Office? A lot of property variations. Packaging of Microsoft Office inversions. You have different look and feel. The answer to the rest of the database. What is about the changes in the PBA object model? You have to migrate even if you go to another Microsoft Office suite. You might call, you might propose your application spirit on the PBA object model. What actually will be the user interface? Ribbons and so on. We will know these issues without finding it. Trusts in inter-authorability and connectivity. Well, something out of this slide. You have even heard this. This is in the talks yesterday in the professional business talks. I do not want to be honest with you though. Can I collaborate with external suppliers, customers, effectively? It's really about document formats, layout, fidelity to see the same and the same layout. Even in the exchange of functionality, one of the main ports, formats and modules, that we can do both on both sides. And the convergence synchronous and asynchronous. And what we did is that we showed them. There was another part of the story that the managing director was using heavily his tap and keyboards and so on. Working with the e-box format, document format, and we showed him a document with e-box and he was flashed about this. So we showed them the e-filters, the in-end export filters of e-box and proof that this is a clear advantage in comparison to the next one. Clear advantage. Behavior in the front window, I don't have to say a lot of it, but this is the part where that's even what Vitalyom mentioned, that you have to tell something about the organization around e-box. The document foundation, how it works, that there are no dependencies to main responders, the license issues. And there is a foundation around the TDF, especially for this kind of fears that somebody could take it and take the new processor, the project or the product and bring it to another way to bring up follow-up costs and so on. So here was some information about TDF and some technical issues, common interfaces and using of common interfaces and formats and the send-outs. I think this is the worst to compare this with Microsoft, this is a clear advantage of e-box. And so on, by time and so well. So, if you get the job, I can... From summary, there were three clusters of fears which they summarized around the worst security, the real technical security issues, security of the product care, how the product is developed and some convention, security, fears, total cost of ownership, which I mentioned in this talk, not so much. So, security and trustworthiness is present and possible if you use e-box. This is a passage that we get. There's no proper mark, there's no proper to ask for. So take the fears of the users, give information, information, information. This is the key point here. But in such discussions, be honest. If there's something not quite comparable with Microsoft Office, tell it and you've got to trust it. And yes, afterwards... 4.2 points, I think it's 5 or 6. The lag is 6. They have to do the security checks, but... So, this is the amount that you have to pay for security. I want to give you a hint to our products. This is the least one recap and I won't get it, there's a conversion. Another point, I want to show you something out of my home country. This is what I've pushed up in talks with the people, not for fees. This is the RSB social and 3.19, what they are doing is hardware refreshing. They buy from the customer hardware, laptops, servers and so on and refurbish them as disabled persons. There's a tariff that they have 50% of the hired people who are disabled persons and they also have access points for laptop and work. I think most of you will know that you can do such a similar thing for pure schools. They do it here and there. Now, if you buy as a private person or a company, if you buy hardware by then you can say, no, I don't want to turn off Microsoft Office Suite, but I don't want to have to leave Microsoft Office Suite. The argument behind this, the most hardware things they are selling are laptops, laptops around 150 and 200 euros and it's quite the same above for a Microsoft Office Suite. A lot of people say, no, I'm not right to buy for the same price so I can't buy or I can't get any more. I want to promote this little thing, so if you have to buy it. Thank you.