 Tukaj, v Italiji je bilo poslednje, da imamo tudi o zelo in o zelo in o zelo in o zelo in o zelo in o zelo in o zelo. Zato počkaj smo prišli do vrštih, ki je zelo všemh naprej. Vzelo všem prišli do vrštih, ki je zelo všem vrštih, ki je zelo všem vrštih. in tudi o odličenih trajovih in odličenih. Zato vzelo, da bo vzelo drugi priključ, da je priključenih priključenih iz vzela vopr. Priključenih priključe so priključenih za vsev, za kaj je zelo priključenih priključenih zazvodnjih. Climate change is important in the way it communicates in public organization. The first thing is that we need to measure, We need to access documents, we need to use our documents. And, of course, we need to ground the information. zelo počke in izgleda se na zelo prizavini svih sejtizav. In tudi se je obačenje počke, ki se izgleda, je to in nekaj, če je zelo dve, kde se izgleda. Kaj tačno učil s artykom, bejte tukaj vse tako, da ne bo v tukaj. Artykom nr. 50 je ena nekaj predstav, in nekaj predstav. Artykom tukaj tukaj vse nekaj predstav. Bilo to vsočen, da ta sezen nekaj četna. Nekaj četna. Ko je to? Kaj? Naša četna. Protože, da bi jih je vzložen. Vzložiš. Vzložiš, da bi jih počite. Spravno tudi češel se počasno gorovite, in izpravno vsečno aktivitve, ki je zelo začem, vzelo, da se počasno koncertje vsečnega, je tudi o večenju, ...ma zgodno ne izgleda imaš do služba. z vsekuna partipadnjestresno. So, si koli bi iskrivati na to, ki je izvednjela na artišlo, na katera partipadnja. In je artišlo 52, ki je z vsem vzupnjem, in errej imamo nazivnjenje in zelo v Modne distrame. Vom težavu na över, da ne so vzladi, da so je jazende. Pelti se n evenly zazdevamo stemt. Sabo je dostan. In ki se nekaj nekaj nekišli, me sen je začasnila, dočnimi naj moramo tudi z n자는em, o vsočenju, o vsočenju, o vsočenju, o časovu. Vse je valjena, da je zelo zelo vsočenje, da je zelo vsočenje, V inopen solution, we need to choose the lower one. So finally, the open smart solution had the importance that they didn't need. I datru�enje s vocabulary, v k Laborosti pridene in dugi pri mojima Unknownsko, we know that there are a lot of problems that can do something for us. But we need to see if there is a preventive solution that can be used for us. So we need to see and be used to see if there is something that fits our assessments. And we need to prepare free software in the closet of all preventive software. In the article 69 we talked about the reuse of computer problems. So there is a database that can help the public administration to choose the application. And with this database public administration can search, can use a solution and can adopt the software that is in the database. We need to reuse, but we need to take care of the ability. We can write our software because in the database there is something that fits for us. But this software needs to be portable and we need to share this problem with the other public administration. So the ability, finally, is very important. When we arrange a problem we need to pay attention to the problem, the agreement, why this. Because in the role we can read that on the contract the public administration needs the property of the software. The property of the documentation and the source code. So, for example, a third party software that realizes the program class can't obtain the property of the software. The software is the property of the public administration. So this is a sort of integration to the digital administration program. In the article 68 talks about some guidelines to make a computer compatible with the system. There are a lot of examples. The adhesive is not a list of rights. This is a sort of example, a sort of guide where you can compare what is in the card or so. And translate what a public administration needs to do for the third party software. To be combined with the law. Thank you. So this is a sort of user manual where the public administration can try some example. And can know how, can act and resolve the special problem that they are considering. So this is a sort of 17 liter base. This is a bit of a base. There are a lot of programs. Some programs are directed by the third party software. Other programs are directed by the public administration. So this is an example. This is a sort of best practice. The public administration realize the software. The public administration release the software. And insert the specification of the software in the database. So you can search and you can try a description of the software. And you can also ask the user of the software. This is a sort of the part, the new part in particular in the joint experience. We know that the public administration can use software, can reuse software. But there are also official channels where the public administration can buy software. This is a screenshot of the software. It is an initialization of the page that the other program can have in Italy. By the way, you can select all your such and all. So you can select the user who are in the device. Or at least, if you are in public administration, selecting one is new. You can search and find other software to it that the public administration can buy and reuse. And the problem for us is that here the potential user also uses Microsoft licenses. In particular, there are in terms between Microsoft and the public administration. The public administration can acquire discounted licenses. And they can choose the single application, the entire suite. So there are a lot of software, not only software like Microsoft Office. Here you can acquire licenses for all the Microsoft products. So this is a stranger for us. But the problem also is the prices. The prices are online. You can read the prices without any plugin. And the prices are updated more often. So those are the prices that are updated to September. And this is only an extractor of the prices. In particular, here we can read the prices of the standard version of this product. Or the sort of package that includes the software and the software restaurants. And here these prices are for discounted prices. But the public administration can spend a lot of money on the way. What we can try to do with the public administration. We need to contact the team in the public administration. Or a reactor. Or we need to have a contact in the public administration. And we need to modify the system to change. We need to take care of all the users in the public administration. Or that want to migrate from Microsoft Office. In the case we need to keep in contact with all the users. Not only with the reactor. We need to provide feedback. Because a user needs feedback. With the cost of feedback. The user is conscious of what we are doing here. For his public administration. And the support can reduce fear. So the support is another aspect that we work on in our organization. Another important aspect is related communication. We need to follow you with the user. And we need to ask to the user. All the problem that the user is in contact with the way they work. So in this way we can reduce the resistance to change. This is our integration protocol that is based on TF integration protocol. And during our work we take care in particular of the analysis phase. This is important. The assessment needs to be as good as possible. Because if you realize an assessment you need to help a worker to reach a good integration. And our testing is the next step for a good integration. So this is an everyday TF integration protocol. In particular now we are working with the municipality of Bali. This is a big worker. The worker is going on. He is going on slowly. But in Bali so we can wait. And this is the big problem, the first problem. In Italy we have a lot of different fashion. We have an event in the project system. Every part of the administration has a lot of topics of fashion. So the first problem is to count the different fashion. And take care of the number of licenses. Because sometimes the number of licenses isn't exactly the number of fashion standards in our computer. So this is the first thing to do. And the difference from acquire and installation can pass to start the migration process. Those are problems that are stopping our work. In particular with the municipality of Bali, but in general in a lot of public administration. We don't know what are the performance. What is the performance of the operator. Or is not so clear what are the performance. So the first problem is that we need to explain. We need to train the user. And sometimes a user guide can help our work. In particular we have a big problem between the definition of open format. And they confuse the tents. So they are sure that they are publishing all the documents with the correct format. Because the format is corresponding enough. So we need to explain, explain, explain. And the other problem is that in our public administration we have a lot of third party software. And all these software also produce a sort of model operator. That the public administration can use for producing the documents. For example the user is a model for the light. In Italy we call these documents the Danian. Or the documents that the public administration uses every day. This document can be realized with a software that generate a sort of automated RTF. In Italy we have a problem with the RTF format. All the software was convinced that RTF format is a standard. RTF is standard, RTF is open. And this is a big problem for us. This document can be with an homemade RTF that produces problems. Whether we can try to import or export with LibreOffice those documents. Because we can't know what version they are using. We can't know what version of Microsoft Office they are using. So we can't know what sort of RTF we are managing. So we need to collect all the problematic documents. And try to open with LibreOffice and try to correct the problem. We have a few RTF documents. And we have a test. The other documents are made with a non-fist of longer or Apache non-fist. But usually in our public administration the users don't know that there is a real fist. They probably know that there is Apache OpenOffice or OpenOffice.com. So it's a problem of communication and of working in the company. OK. How can we solve this problem? We have open and Apache RTF on RTF. Those are the blocks that we have inserted in the bugger. And with the other developer, in particular with the meatlosch, we are trying to solve this bugger not only for the time of the bugger but also for the information. It's not so simple because usually we have the documents that are very long press. The programs usually are related to the encoding of images or tables or lists. So we can go through all the problems in this video category. And with the meatlosch we are trying to solve this bugger and do all the other documents that can be imported in the wrong way in the office. So we don't have the great set in the images. And the meat is off and there are questions. Did you have a manual for the users? There are no deployable rules. It's not a real manual. But it tells you how you have to deploy standard program. We want to write about our users and we want to share this with them. But now we can translate. Although that is strictly related to Italian mode, which is specific, the implementation rules are quite interesting. But it's a different tool. It's not based on the European power. It's a different one. I think that this is unfortunately a situation that we have over the year. Regulations on standards are not the same. It's funny because standards are the same. And therefore the question should be the same everywhere. Is it not the implementation of European regulations? No, actually the European regulation is weaker than the Italian one. But then as usual is written in legalese. So 70 pages written in legalese. You have to explain people what they are written inside. Because otherwise people will be the normal understanding of Italian non-ununderstanding. Is that an English version of this one? No. I am trying to do Google translate that, but it's impossible. We have a coffee break, I think. I should go.